User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Fedora/1.7.12-1.5.1 When composing a "Reply All" message with both email and news-group destinations, the 'Send' operation fails with the following popup- Send Message Error !Sending of message failed. The message could not be posted because connecting to the news server failed. The server may be unavailable or is refusing connections. .... OK A tcpdump trace of the traffic between my Linux desktop machine and the news server shows that Mozilla is trying to open a TCP connection to port 25 (SMTP) when it should be connecting to port 119 (NNTP)! The news server is quite correctly rejecting this connection attempt. Mozilla is 'confused' w.r.t. where the SMTP server is located even tho both Mail and News are CORRECTLY configured to point to their respective servers. Reproducible: Sometimes Steps to Reproduce: 1.Open up a newsgroup or read a email (IMAP) 2.Compose a "Reply All" response 3.Click on "Send" Actual Results: The post fails and clicking the OK button on the error popup discards the newly composed reply message. Expected Results: Both post the reply to the target Newsgroup: group(s) and send it as emails to the designated mailboxes as identified in the To: and Cc: addressing lines. I don't know if some other email/news (eg a 'doze system) application is creating a message that is confusing Mozilla, but the "Reply All" send failure only occurs under circumstances that I can't yet determine. If either ALL of the email addresses, or alternatively ALL of the Newsgroups are removed as destinations then the post succeeds. It's only when a combination of the two exist that Mozilla gets confused with where the SMTP agent lives and tries to connect to it on the news server!
worksforme with linux seamonkey trunk 2005120701 please try a newer build: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8/ http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ Mozilla 1.7.x is only taking security fixes. Also please test with a build from .mozilla.org before filing a bug. Otherwise file a bug with Red Hat (https://bugzilla.redhat.com/bugzilla/
Version: unspecified → 1.7 Branch
I believe this is related to Bug 100522 and / or Bug 142409 as I had a user recently have this problem with Thunderbird 1.0 (20041206) on WXP SP2. Both are marked as NEW and are assigned to sspitzer@ (who I contacted, and said he's "not actively working on tbird these days".) The situation is that she has an e-mail that is from a mailing list, but also CC'd to a newsgroup (news://). If she hasn't done anything with the NNTP account lately (e.g., clicked on any of the 'folders' that represent a newsgroup), when she hits 'reply all' (and the newsgroup is one of the receiptients) and then hits 'send' the operation fails. When the user then clicks on the newgroup folder (which causes Thunderbird to re-establish a TCP connection), and then tries hitting 'send' on the reply (the window with the text is still there), the reply can now be sent in both SMTP and NNTP. I'm curious to know if this is still an issue in newer versions of Thunderbird, as I don't want to have the user upgrade her installation if it doesn't do anything to fix the problem.
(In reply to comment #2) > I'm curious to know if this is still an issue in newer versions of > Thunderbird, as I don't want to have the user upgrade her installation if it > doesn't do anything to fix the problem. Bug 304853 was a TB-specific version of this bug, and when I tested with a 1.5 build of TB it seemed to no longer be a problem. Have you updated your user, and did it work for her?
Works for me. Depending on which account is current, the mail/news client will do one of the following: - do it OK (if the current account is my one News account) - fail with error popup (if the current account is a Mail account) saying this account cannot post newsgroup messages. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008032107 SeaMonkey/2.0a1pre - The latest comment before this one is more than one year old. - The only comments mentioning the bug as present in a well-defined build are comment #2 (Tb 1.0, W32, 20041206) and comment #0 (MozS 1.7.12, Linux-i686, 20050923). The most recent of these is 2½ years old. I'm resolving this WORKSFORME; if you see it on a recent build, please file a new bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.