[email protected] wrote:
On Oct 31, 1:40 pm, chicagofan<[email protected]> 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
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
