Bill Davidsen wrote:
I have put my full config up as screen shots:
http://www.tmr.com/~davidsen/Private/E-S_post_bug_SM2/
Note that SeaMonkey sends *no packets* to the NNTP host, other than
"always offer auth" my working server definitions, those without auth
needed, are identical.
I have "Fails for me" about 2:1 over "Works for me," but obviously it
works for someone.
Linux, Fedora-11, updated a few days ago.
It seems that a fix is available for this problem, assuming you are willing to
build your own SeaMonkey from source. Bug #484656 seems to change the "You have
your config wrong" to "we were parsing your config wrong." In any case the
problem is identified, and *maybe* this will be in 2.0.1 as a fix.
I can find no reliable way to avoid this, creating a new account may work, or
not. I think part of the problem is related to there being no machine by the
name news.eternal-september.org, but instead that returns a list of IPs, all of
which resolve to other names.And if you use SSL, the certificate is for
news.eternal-september.org, so you can't just plug in the real name of the
server you want, even for test. The other account I have which shows the same
problems also has funky naming, all of which works perfectly in 1.1.18.
Until/unless the patch is adopted it looks bad for the good guys.
--
Bill Davidsen <david...@tmr.com>
"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
