535439 - upgrading to Thunderbird 3.0 turns on "always return acknowledgement receipts" without user knowledge

Status: RESOLVED INCOMPLETE

(Thunderbird :: Installer, defect)

Description

[Drew Devereux]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0

I prefer not to return acknowledgment receipts telling email senders that I have opened their emails. I consider these acknowledgment receipts an impost upon my privacy.

Upgrading to Thunderbird 3.0 altered my settings without my knowledge, causing my client to send acknowledgement receipts, and I didn't find out about this until I had sent one out.

Marking this major because of the privacy implications.

Reproducible: Always

Comment 1

[rsx11m]

Don't see this with my profiles migrated from 2.0.0.23 to 3.0 (WinXP), I have "Never send a return receipt" marked in the global settings, which was retained during migration. All other settings are at "Ask me" for the global settings.

In the Account Settings, "Use my global return receipt preferences for this account" is checked for all accounts.

Are you talking about the global settings or the account-specific settings?

Comment 2

[Drew Devereux]

The behaviour for the account in question was "ask me". I don't know what my previous settings were, so I can't tell you whether that behaviour was due to local or global settings.

After migration, the local setting for the account was "ask me" but the account was set to use the global settings not the local settings.

I guess the most likely scenario is
1. Global setting was and is "send receipt"
2. Local setting was and is "ask me"
3. Account was previously set to use its local setting, and migration switched it over to use the global setting.

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to comment #2)

> I guess the most likely scenario is
> 1. Global setting was and is "send receipt"
> 2. Local setting was and is "ask me"
> 3. Account was previously set to use its local setting, and migration switched
> it over to use the global setting.

Just tried that, I'm being asked before the receipt is send. 
Do you use extensions ?

Comment 4

[Jazmin]

The same happened to me when upgraded from version 2.
The configuration WASN'T changed. It's still on ASK ME
But TB is sending the Return Receipts without asking.

I've set the individual accounts to try to prevent that.

Comment 5

[Ludovic Hirlimann [:Usul]]

(In reply to comment #4)
> The same happened to me when upgraded from version 2.
> The configuration WASN'T changed. It's still on ASK ME
> But TB is sending the Return Receipts without asking.

Is it the return receipt or the delivery receipt that you are getting ?

Comment 6

[Jazmin]

I can't say exactly what happened, since I will not be able to reproduce it now.

The only way I can explain it is with the events that happened.

1) I've sent a mass (not spam) Christmas greeting.
2) Some messages bounced
3) I got messages that bounced that instead of the Greeting e-mail where the bounce of MY acknowledge of the return receipt.

Meaning that I had something like "Undeliverable messsage yada yada..."
With text "Your message xxxx can't be delivered.... *something* Original text: Your e-mail xxxxx was read at: [time][date]"

So with that and some other things that happened I can say that TB sent the Return Receipt Acknowledge.

Since I had some many e-mails I've cleaned up the Inbox and Sent so I don't have examples and I don't know if there were Acknowledge e-mails on the Sent folder.

Comment 7

[Mark Banner (:standard8)]

I've just tried this with 2.0.0.23 and updating to 3.0.2pre. All went well and I was asked for a return receipt. I don't think there's anything we can do here unless we get some clear confirmation and steps to repeat.

Comment 8

[Wayne Mery (:wsmwk)]

Jazmin, can you reproduce this on current version ??  (updating from version 9 to 10 for example)

Comment 9

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error please respond to this bug with your reasons why.