User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 Build Identifier: Mozilla Thunderbird 0.2 (20030901) News sending fails if there is more than one news account with same subscribed newsgroups and there is problem with connection to earlier news server. Problem is that when reading news it reads it to right server, but when you send message it sends it to wrong server if there is same newsgroup subscribed to that server too. This occurs if you have connection problem to this wrong server. Reproducible: Always Steps to Reproduce: 1. make subscription to several news servers with same newsgroups subscribed 2. get a connection problem to one of them (upper in list) 3. try to send message to newsgroup server that does work. Actual Results: Message fails to send with message "connection to server <server with connection problem> timed out" and "sending of message failed" (with explanation that connection failed) Expected Results: send message to the news server where message should have been send.
My provider has netscape.public.test on his news server "newsall.dti.ne.jp". I tested with netscape.public.test on both "newsall.dti.ne.jp" and "news.mozilla.org", using Mozilla 2003091609-trunk/Win-Me. "newsall.dti.ne.jp" is defined first, then "news.mozilla.org". Following is the result of X-Mozilla-News-Host: header in message source saved as Draft. (1) Click netscape.public.test on "newsall.dti.ne.jp" X-Mozilla-News-Host: newsall.dti.ne.jp (2) Click netscape.public.test on "news.mozilla.org" X-Mozilla-News-Host: news.mozilla.org (3) Click usual mail folder and compose with To:netscape.public.test X-Mozilla-News-Host: newsall.dti.ne.jp After unsubscribe of netscape.public.test on newsall.dti.ne.jp, (I also terminate and restarted Moziila) (4) Click usual mail folder and compose with To:netscape.public.test X-Mozilla-News-Host: news.mozilla.org This indicates posting news server is determined on composing. If posting failed on first news server, re-composing for another news server seemes to be required. This can be done, I think, by above procedure (2). Will procedure (2) work on your case? If not, will procedure (4) after unsubscribe work?
I've also had this problem with normal smtp mail accounts. I have a number of different accounts all of which require dialing up through the isps own servers. In order to send mail I have to keep disconnecting and reconnecting to the different accounts in order that I chose to 'send later' on the messages. TB needs to attempt sending the next message in the unsent messages folder even if the previous message has failed to send.
do you still see this problem using a current version?
(In reply to comment #2) > TB needs to attempt sending the next message in the unsent messages folder even > if the previous message has failed to send. if this is the main issue, then the bug is a dupe
Timo could answer to comment #3, please? Using TB 3.x your issue is gone?
(In reply to comment #5) > Timo could answer to comment #3, please? Using TB 3.x your issue is gone? I'm currently on vacation, and I wont ruin my home machine with TB3.0, and 3.1 isn't ready yet (no critical to me add-on compatibility, still bad default settings in beta). I might try testing on my workplace virtual machine once vacation is over. Home machine will not be downgraded to TB3 from perfectly working TB2. Problem is that I don't know how to actually test that. But I think of it. Maybe setting security settings so that connection no more works...