287735 - "Send if going online" is always displayed

Status: RESOLVED DUPLICATE of bug 274280

(Thunderbird :: Mail Window Front End, defect)

Description

[Carsten Breuer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0

Thunderbird allways ask for "send if going online" even if all prefs
are saying "go online". I dont find any pref that can kick off this anoying
message. It is allways displayed. I dont have an offline mode and i dont want
to. This should be IMO disabled by default! Im verry concerned about the new
politics to play with the GUI. Why are the developer take the risk to loose the
respect they have wone. The offline message and the new find dialog are IMO good
examples how to make good things worse. SCNR.

Reproducible: Always

Steps to Reproduce:
1. Start Thunderbird.

Actual Results:  
2. MessageBox "Möchten Sie Nachrichten automatisch versenden bei einem Wechsel
zu Online". English: Do you want to sent messages automaticly after going to online"
(Sorry for my bad english).


Expected Results:  
No anoying messagebox. If the prefs say "yes, go online" it should go online and
not ask for it.

Comment 1

[David :Bienvenu]

it sounds more like a bug than politics, if I understand you correctly. Are you
saying this happens when you startup? It sounds like we think you have unsent
messages. Have you looked in Local Folders | unsent messages, to see if there
are any unsent messages?

Comment 2

[Mike Cowperthwaite]

I think this is a dupe of bug 274280

Comment 3

[Carsten Breuer]

(In reply to comment #2)
> I think this is a dupe of bug 274280

Yes you are right. This sounds the same.
Nonetheless the bug is NOT FIXED, as mentioned there.
I use Thunderbird 1.0. I dont have any unsended messages!
I start thunderbird, use it and close it if mail is done.

Comment 4

[Mike Cowperthwaite]

(In reply to comment #3)
> (In reply to comment #2)
> > I think this is a dupe of bug 274280
> 
> Yes you are right. This sounds the same.
> Nonetheless the bug is NOT FIXED, as mentioned there.

No, this bug's symptoms still exist in current builds; it was something else 
that was described as fixed, at that bug.


*** This bug has been marked as a duplicate of 274280 ***