Re: SeaMonkey seems not to post to NNTP using auth
NoOp wrote: On 11/03/2009 09:34 AM, Bill Davidsen wrote: NoOp wrote: ... So not sure what the issue could be on your system. However, for the sake of keeping this thread to a minimum, I'll be happy to test other scenarios if you'll contact me directly (just drop the .invalid from the email address & keep the same subject so that I don't automatically drop the msg in the spam filters). I can test on linux (ubuntu 9.04 & 9.10 - gnome only, I'm alergic to kde), WinXPPro & Win2KPro (both fully updated). I noted the test I made, new profile, new install with no migration, even new Fedora in a fresh virtual machine. All behave the same. No clue... :-( Could it be that the VM is the issue? Do you experience the same on a non VM? Yes, I even tried creating a whole new user on a machine I just built, installed SM2.0 (not one of the snapshots), no add-on or themes, and it still happens. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
chicagofan wrote: u...@domain.invalid wrote: chicagofan wrote: Did you see Gabrielle's message which said, her problems went away after she deleted her existing news account, and set it up again? Have you tried that? I have the same problem with my upgrade using news.ett.com.ua - and this is a test on news.mozilla.org so if you can read this, then using a new news server does not cause problems which are there for an old news server (pre-upgrade). Reading you just fine. :) I'm not following what you are saying about "causing" problems, but I understood Gabrielle to have solved her problems by re-creating the accounts and newsgroups she needed, with 2.0... after the migration. Yes, my post was not a model of clear communication. If you're saying mozilla.org worked on your previous version, and also works in 2.0, but ett.com does not, I get it. :) I'm just guessing, but it seems like the varying methods ISPs or news servers use for log in are throwing SM a curve. I did not have mozilla.org set up in the 1.x version. But I added it in 2.0 and it works fine. I did have ett.com set up in the 1.x version, and obviously it worked, but I cannot post in SM 2.0. As I am more of a reader than a poster it's not really a big deal for me. I am using a relay for SMTP and I have a password and "Use secure authentication" checked. But that is between me and my ISP isn't it. I wish I had the answer, but other than verifying that server settings are correct for each server used, and checking the SMTP settings, I'm at a loss. Have you checked with ett. com for some suggestions? I'm worried about what may happen to me this month, when my ISP makes some changes to my sign on [for security purposes they say]. We are going to have to add our zip code to the sign in. That should be interesting. :( bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
u...@domain.invalid wrote: chicagofan wrote: Did you see Gabrielle's message which said, her problems went away after she deleted her existing news account, and set it up again? Have you tried that? I have the same problem with my upgrade using news.ett.com.ua - and this is a test on news.mozilla.org so if you can read this, then using a new news server does not cause problems which are there for an old news server (pre-upgrade). Reading you just fine. :) I'm not following what you are saying about "causing" problems, but I understood Gabrielle to have solved her problems by re-creating the accounts and newsgroups she needed, with 2.0... after the migration. If you're saying mozilla.org worked on your previous version, and also works in 2.0, but ett.com does not, I get it. :) I'm just guessing, but it seems like the varying methods ISPs or news servers use for log in are throwing SM a curve. I wish I had the answer, but other than verifying that server settings are correct for each server used, and checking the SMTP settings, I'm at a loss. Have you checked with ett. com for some suggestions? I'm worried about what may happen to me this month, when my ISP makes some changes to my sign on [for security purposes they say]. We are going to have to add our zip code to the sign in. That should be interesting. :( bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
On 11/03/2009 09:34 AM, Bill Davidsen wrote: > NoOp wrote: ... >> So not sure what the issue could be on your system. However, for the >> sake of keeping this thread to a minimum, I'll be happy to test other >> scenarios if you'll contact me directly (just drop the .invalid from the >> email address & keep the same subject so that I don't automatically drop >> the msg in the spam filters). I can test on linux (ubuntu 9.04 & 9.10 - >> gnome only, I'm alergic to kde), WinXPPro & Win2KPro (both fully updated). >> > I noted the test I made, new profile, new install with no migration, even new > Fedora in a fresh virtual machine. All behave the same. No clue... :-( > Could it be that the VM is the issue? Do you experience the same on a non VM? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
NoOp wrote: On 11/01/2009 05:36 AM, Bill Davidsen wrote: NoOp wrote: ... Not sure what the issue might be Bill. I've migrated 4 machines (linux) from 1.1.18 to 2.0 and _all_ have no issues accessing news.eternal-september.org (port 563/SSL). I've 2 test machines that have yet to be migrated & I'll see if I can get them done this weekend & let you know if they have issues. Have you tried from a different profile? Yes. Tried different profile, machine, etc. Works from 1.1.18 every time, not from 2.0 any time. Bill, getting back to why I think it's a profile issue; just tested SM 2.0 w/new install on a machine that never had SM installed on it previously - no issues. You'll find my test post (along with the Windows one) in eternal-september.test - news.eternal-september.org: "Test from SM 2.0". Windows: From: NoOp Newsgroups: eternal-september.test Subject: Test from SM 2.0 Date: Sat, 31 Oct 2009 20:26:12 -0800 ... Message-ID: ... User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 Linux: From: NoOp Newsgroups: eternal-september.test Subject: Re: Test from SM 2.0 Date: Mon, 02 Nov 2009 12:12:42 -0800 ... Message-ID: References: ... User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 So not sure what the issue could be on your system. However, for the sake of keeping this thread to a minimum, I'll be happy to test other scenarios if you'll contact me directly (just drop the .invalid from the email address & keep the same subject so that I don't automatically drop the msg in the spam filters). I can test on linux (ubuntu 9.04 & 9.10 - gnome only, I'm alergic to kde), WinXPPro & Win2KPro (both fully updated). I noted the test I made, new profile, new install with no migration, even new Fedora in a fresh virtual machine. All behave the same. No clue... :-( -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
LR wrote: On Nov 1, 5:59 pm, chicagofan wrote: lr...@superlink.net wrote: I have a problem that has the same symptoms that started after I installed SM 2.0. I had to sign on to my google(tm) account to post here. Suggestions? I think maybe I spoke too soon now, although I have read many users posting that have nntp access on Linux and Windows with no problems. :\ What messages are you getting? Same as the OP? Yes. It seems like I have the same behavior. What news servers aren't working for you? I'm trying to post using newsread.uslec.net Do you have any extensions or security programs that might be interfering? I have Zone Alarm running. Seemed ok with the previous version I had installed which was, I think, 1.1.18. What O/S or platform are you using? Win XP. Check to make sure all your news server settings are correctly set, individually [i.e., I have 2 news server that require no authentication, but one does]. I've tried both ways. BTW, when I first installed 2.0 I had to fiddle with the settings for email, unchecking the user name and password setting for the outgoing SMTP server. I seem to remember that I had a similar problem with mail connections, after my *first* update to SM 2.0 beta. Something had changed my outgoing SMTP settings to require secure settings. I think what I just described above. Plus, you should add your experience w/ more details to the bug that has been filed by Bill Davidsen: https://bugzilla.mozilla.org/show_bug.cgi?id=525649 Ok, I did that too. LR Did you see Gabrielle's message which said, her problems went away after she deleted her existing news account, and set it up again? Have you tried that? bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
On Nov 1, 5:59 pm, chicagofan wrote: > lr...@superlink.net wrote: > > On Oct 31, 1:40 pm, chicagofan wrote: > >> NoOp wrote: > On 10/30/2009 02:50 PM, Bill Davidsen wrote: > > Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS > > (563 with SSL) with this message: > >http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png > > > And my first test post to this server failed silently as well. WTH? > > > NOTE: since tested on another server with auth, fails there as well. > > news.eternal-september.org works just fine for me. Server settings 563 > SSL/TLS 'Always request authentication when connecting to this server- > outgoing server is the same as this email account. > > >> It's working fine for me too, on Port 119, as news.eternal-september.org, > >> with the "Always request authentication" box checked under the news server > >> settings. Note, my setup isn't using SSL [Port 563] though. > > >> Hope something works for you, but I don't think it's a SM 2.0 problem. :) > > > I have a problem that has the same symptoms that started after I installed > > SM 2.0. I had to sign on to my google(tm) account to post here. > > Suggestions? > > I think maybe I spoke too soon now, although I have read many users posting > that have nntp access on Linux and Windows with no problems. :\ > > What messages are you getting? Same as the OP? Yes. It seems like I have the same behavior. > What news servers aren't working for you? I'm trying to post using newsread.uslec.net > Do you have any extensions or security programs that might be > interfering? I have Zone Alarm running. Seemed ok with the previous version I had installed which was, I think, 1.1.18. What O/S or platform are you using? Win XP. > > Check to make sure all your news server settings are correctly set, > individually > [i.e., I have 2 news server that require no authentication, but one does]. I've tried both ways. BTW, when I first installed 2.0 I had to fiddle with the settings for email, unclicking the user name and password setting for the outgoing SMTP server. > > I seem to remember that I had a similar problem with mail connections, after > my > *first* update to SM 2.0 beta. Something had changed my outgoing SMTP > settings > to require secure settings. I think what I just described above. > Plus, you should add your experience w/ more details to the bug that has been > filed > by Bill Davidsen: https://bugzilla.mozilla.org/show_bug.cgi?id=525649 Ok, I did that too. LR ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
On 11/01/2009 05:36 AM, Bill Davidsen wrote: > NoOp wrote: ... >> Not sure what the issue might be Bill. I've migrated 4 machines (linux) >> from 1.1.18 to 2.0 and _all_ have no issues accessing >> news.eternal-september.org (port 563/SSL). I've 2 test machines that >> have yet to be migrated & I'll see if I can get them done this weekend & >> let you know if they have issues. Have you tried from a different profile? >> > Yes. Tried different profile, machine, etc. Works from 1.1.18 every time, not > from 2.0 any time. Bill, getting back to why I think it's a profile issue; just tested SM 2.0 w/new install on a machine that never had SM installed on it previously - no issues. You'll find my test post (along with the Windows one) in eternal-september.test - news.eternal-september.org: "Test from SM 2.0". Windows: From: NoOp Newsgroups: eternal-september.test Subject: Test from SM 2.0 Date: Sat, 31 Oct 2009 20:26:12 -0800 ... Message-ID: ... User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 Linux: From: NoOp Newsgroups: eternal-september.test Subject: Re: Test from SM 2.0 Date: Mon, 02 Nov 2009 12:12:42 -0800 ... Message-ID: References: ... User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 So not sure what the issue could be on your system. However, for the sake of keeping this thread to a minimum, I'll be happy to test other scenarios if you'll contact me directly (just drop the .invalid from the email address & keep the same subject so that I don't automatically drop the msg in the spam filters). I can test on linux (ubuntu 9.04 & 9.10 - gnome only, I'm alergic to kde), WinXPPro & Win2KPro (both fully updated). Gary ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
Gabriele wrote: chicagofan ha scritto: lr...@superlink.net wrote: I have a problem that has the same symptoms that started after I installed SM 2.0. I had to sign on to my google(tm) account to post here. Suggestions? I think maybe I spoke too soon now, although I have read many users posting that have nntp access on Linux and Windows with no problems. :\ What messages are you getting? Same as the OP? What news servers aren't working for you? Do you have any extensions or security programs that might be interfering? What O/S or platform are you using? Check to make sure all your news server settings are correctly set, individually [i.e., I have 2 news server that require no authentication, but one does]. [cut] Hello, as I posted a few hours ago, I had the same problem with a non-auth news server. I deleted it, and created a new news account: now it's working, so the problem is probably related to some bug in the migration step. bye, Gabriele Apparently... let's hope your experience will be helpful to others. :) bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
chicagofan ha scritto: lr...@superlink.net wrote: On Oct 31, 1:40 pm, chicagofan wrote: NoOp wrote: On 10/30/2009 02:50 PM, Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. news.eternal-september.org works just fine for me. Server settings 563 SSL/TLS 'Always request authentication when connecting to this server- outgoing server is the same as this email account. It's working fine for me too, on Port 119, as news.eternal-september.org, with the "Always request authentication" box checked under the news server settings. Note, my setup isn't using SSL [Port 563] though. Hope something works for you, but I don't think it's a SM 2.0 problem. :) I have a problem that has the same symptoms that started after I installed SM 2.0. I had to sign on to my google(tm) account to post here. Suggestions? I think maybe I spoke too soon now, although I have read many users posting that have nntp access on Linux and Windows with no problems. :\ What messages are you getting? Same as the OP? What news servers aren't working for you? Do you have any extensions or security programs that might be interfering? What O/S or platform are you using? Check to make sure all your news server settings are correctly set, individually [i.e., I have 2 news server that require no authentication, but one does]. [cut] Hello, as I posted a few hours ago, I had the same problem with a non-auth news server. I deleted it, and created a new news account: now it's working, so the problem is probably related to some bug in the migration step. bye, Gabriele ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
NoOp: >Harmut filed mailto:4a20de79.5010...@hfigge.myfqdn.de but no clue what >that is as you can't search this group with that info. Harmut, how about >providing a link to the msg? 'mailto:' isn't correct, should be 'news'. Required by some RFC. But 'news:'' is a dangerous thing for mozilla based NUAs. Very old bug. Nevertheless, MIDF shows, that this posting was not catched by google. But it can be found on newsservers or here: http://de.nntp2http.com/comm/software/mozilla/nightly-builds/2009/05/09818ed83092721eab8ea2f226a86e00.html This bug is fixed for my SM 2.1. Hartmut ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
On 11/01/2009 05:36 AM, Bill Davidsen wrote: > NoOp wrote: ... >> Not sure what the issue might be Bill. I've migrated 4 machines (linux) >> from 1.1.18 to 2.0 and _all_ have no issues accessing >> news.eternal-september.org (port 563/SSL). I've 2 test machines that >> have yet to be migrated & I'll see if I can get them done this weekend & >> let you know if they have issues. Have you tried from a different profile? >> > Yes. Tried different profile, machine, etc. Works from 1.1.18 every time, not > from 2.0 any time. I'll see if I can try a few more test cases (linux) over the next few days. As you can see from my test posts on news.eternal-september.org (support and test) the Win2KP test profile had no issues, but the default/existing profile did - as in your case. > > I notice that 2.0 unchecks my "ask about more than 500 messages" box, > although > it seems to ask. Ideas? Different thread/issue; see: "SM 2.0 RC2: News server setttings don't hold" https://bugzilla.mozilla.org/show_bug.cgi?id=523958 dupe of: https://bugzilla.mozilla.org/show_bug.cgi?id=457882 Harmut filed mailto:4a20de79.5010...@hfigge.myfqdn.de but no clue what that is as you can't search this group with that info. Harmut, how about providing a link to the msg? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
lr...@superlink.net wrote: On Oct 31, 1:40 pm, chicagofan wrote: NoOp wrote: On 10/30/2009 02:50 PM, Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. news.eternal-september.org works just fine for me. Server settings 563 SSL/TLS 'Always request authentication when connecting to this server- outgoing server is the same as this email account. It's working fine for me too, on Port 119, as news.eternal-september.org, with the "Always request authentication" box checked under the news server settings. Note, my setup isn't using SSL [Port 563] though. Hope something works for you, but I don't think it's a SM 2.0 problem. :) I have a problem that has the same symptoms that started after I installed SM 2.0. I had to sign on to my google(tm) account to post here. Suggestions? I think maybe I spoke too soon now, although I have read many users posting that have nntp access on Linux and Windows with no problems. :\ What messages are you getting? Same as the OP? What news servers aren't working for you? Do you have any extensions or security programs that might be interfering? What O/S or platform are you using? Check to make sure all your news server settings are correctly set, individually [i.e., I have 2 news server that require no authentication, but one does]. I seem to remember that I had a similar problem with mail connections, after my *first* update to SM 2.0 beta. Something had changed my outgoing SMTP settings to require secure settings. I didn't know if my ISP had changed something, but I had not... and expected my old SM settings to be the same, and work as before. Anyway [though it is probably TOTALLY unrelated to this problem], I edited the settings under my Outgoing SMTP server, and unchecked the box ... for name and password, and that corrected my connection problem. Note that was 2.0b1, and regarding *mail* problems, but it's worth checking your SMTP settings, until someone comes along with the right answer about 2.0. :) Plus, you should add your experience w/ more details to the bug that has been filed by Bill Davidsen: https://bugzilla.mozilla.org/show_bug.cgi?id=525649 bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
Bill Davidsen ha scritto: Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. Reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=525649 if anyone else seeing this would please confirm, vote, etc. Hello, I have the same problem using my ISP news server! I don't think it's a matter of authentication or not, cause I've tried all kind of settings and the error it's the same as yours. I can post using news.mozilla.org (which apparently works through giganews), but no way to send using the other news server (which is news.mclink.it which was working since I upgraded to SM 2.0). I will try now to delete the news server and retry. Stay tuned! bye Gabriele ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
NoOp wrote: On 10/31/2009 09:12 AM, Bill Davidsen wrote: Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. Reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=525649 if anyone else seeing this would please confirm, vote, etc. This is kind of blocking migration from 1.1.18 for several groups with a customer support news server. Not sure what the issue might be Bill. I've migrated 4 machines (linux) from 1.1.18 to 2.0 and _all_ have no issues accessing news.eternal-september.org (port 563/SSL). I've 2 test machines that have yet to be migrated & I'll see if I can get them done this weekend & let you know if they have issues. Have you tried from a different profile? Yes. Tried different profile, machine, etc. Works from 1.1.18 every time, not from 2.0 any time. I notice that 2.0 unchecks my "ask about more than 500 messages" box, although it seems to ask. Ideas? -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
On 10/31/2009 09:12 AM, Bill Davidsen wrote: > Bill Davidsen wrote: >> Server: news.eternal-september.org >> Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: >> http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png >> >> And my first test post to this server failed silently as well. WTH? >> >> NOTE: since tested on another server with auth, fails there as well. > > Reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=525649 if > anyone else seeing this would please confirm, vote, etc. > > This is kind of blocking migration from 1.1.18 for several groups with a > customer support news server. Not sure what the issue might be Bill. I've migrated 4 machines (linux) from 1.1.18 to 2.0 and _all_ have no issues accessing news.eternal-september.org (port 563/SSL). I've 2 test machines that have yet to be migrated & I'll see if I can get them done this weekend & let you know if they have issues. Have you tried from a different profile? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
On Oct 31, 1:40 pm, chicagofan wrote: > NoOp wrote: > >> On 10/30/2009 02:50 PM, Bill Davidsen wrote: > >>> Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS > >>> (563 with SSL) with this message: > >>>http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png > > That's the same message I get *anytime* ES has too much traffic or they are > doing maintenance, etc., which is not uncommon. Is this the only message you > have gotten, besides not being able to connect, of course? > > >>> And my first test post to this server failed silently as well. WTH? > > >>> NOTE: since tested on another server with auth, fails there as well. > > >> news.eternal-september.org works just fine for me. Server settings 563 > >> SSL/TLS 'Always request authentication when connecting to this server- > >> outgoing server is the same as this email account. > > It's working fine for me too, on Port 119, as news.eternal-september.org, with > the "Always request authentication" box checked under the news server > settings. > Note, my setup isn't using SSL [Port 563] though. > > Hope something works for you, but I don't think it's a SM 2.0 problem. :) > bj I have a problem that has the same symptoms that started after I installed SM 2.0. I had to sign on to my google(tm) account to post here. Suggestions? LR ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
NoOp wrote: On 10/30/2009 02:50 PM, Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png That's the same message I get *anytime* ES has too much traffic or they are doing maintenance, etc., which is not uncommon. Is this the only message you have gotten, besides not being able to connect, of course? And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. news.eternal-september.org works just fine for me. Server settings 563 SSL/TLS 'Always request authentication when connecting to this server- outgoing server is the same as this email account. It's working fine for me too, on Port 119, as news.eternal-september.org, with the "Always request authentication" box checked under the news server settings. Note, my setup isn't using SSL [Port 563] though. Hope something works for you, but I don't think it's a SM 2.0 problem. :) bj ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. Reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=525649 if anyone else seeing this would please confirm, vote, etc. This is kind of blocking migration from 1.1.18 for several groups with a customer support news server. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SeaMonkey seems not to post to NNTP using auth
NoOp wrote: On 10/30/2009 02:50 PM, Bill Davidsen wrote: Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS (563 with SSL) with this message: http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png And my first test post to this server failed silently as well. WTH? NOTE: since tested on another server with auth, fails there as well. news.eternal-september.org works just fine for me. Server settings 563 SSL/TLS 'Always request authentication when connecting to this server- outgoing server is the same as this email account. I have tried 119 (no SSL) and 563 (with SSL), "always authenticate" check or not checked (which asks for auth, so it still should work), and since I have no idea what "outgoing server is the same as this email account" means, I have tried with accounts called just "eternal-september" (the original) and "news.eternal-september.org" in case that's what you meant. The outgoing SMTP host name is the same as all other accounts, which have no auth and work fine. Here's the positive indication of a problem: I ran tcpdump to see if SM was using the open socket or starting a new one, possibly without auth, and it is *not* generating any packets at all! WTH can that indicate, other than some internal sanity check is failing? I've tried with migrated accounts, and with newly created accounts, tried fresh profiles, it really looks as if there's a bug here in in accounts requiring auth (not just e-s). A rethink is requested, WFM doesn't fix the problem and others are reporting it as well. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
