NoOp wrote:
On 11/24/2009 10:20 AM, Bill Davidsen wrote:
Jens Hatlak wrote:
Bill Davidsen wrote:
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.
Since comm-1.9.1 (the base of 2.0.x releases) branched after the fix for
that bug was checked in it already contains that fix. IOW, it's already
fixed in 2.0.1pre nightlies (which you can get without building from
source) and will be fixed in 2.0.1. :-)
Huzzah! I hate to run a work in progress in production, but that might be the
best solution.
Thanks for the info, now the next question is why it works for anyone with the
official 2.0 release.
This may be a bit late, but taking a hint from Harmut on how to capture
logs for various sessions, I set a log for nntp and logged into
news.eternal-september.org using port 563/ssl. I then sent a test msg on
the eternal-september.test group. The results are here:
http://pastebin.com/m7bf6e673
You can do the same by adding a few lines to your 'seamonkey' shell
script. Here is what I added to mine (preceded by ++ so you can see
which lines were added, of course don't include ++ in your script &
modify '$HOME/<pathtoSeaMonkey>' to suit your needs):
Thank you for this information, I've been busy the last few days and haven't
read the group much if at all. Good info for the future, I added it to my tips
file. Since there's a patch, I'm considering the problem both real (code rather
than user problem) and solved.
#uncomment for debugging
#set -x
++# keep a log
++# For bash shell (the default shell on most GNU/Linux systems):
++#export NSPR_LOG_MODULES=nntp:5
++#export NSPR_LOG_FILE=$HOME/<pathtoSeaMonkey>/nntp.log
++#export NSPR_LOG_MODULES=pop3:5
++#export NSPR_LOG_FILE=$HOME/<pathtoSeaMonkey>/pop3.log
++#export NSPR_LOG_MODULES=smtp:5
++#export NSPR_LOG_FILE=$HOME/<pathtoSeaMonkey>/smtp.log
When I want to enable the log, I simply uncomment (remove the #) before
starting SeaMonkey. For example, for nntp:
export NSPR_LOG_MODULES=nntp:5
export NSPR_LOG_FILE=$HOME/<pathtoSeaMonkey>/nntp.log
Perhaps from the log on the failing/problem build you can see the
difference between your log and the log I've posted.
Log refs:
http://kb.mozillazine.org/Session_logging_for_mail/news
https://wiki.mozilla.org/MailNews:Logging
--
Bill Davidsen <[email protected]>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
