At 06:08 PM 1/5/2004, SAtalk Mail User wrote:
This is the output of maillog from when I receive an email message.

Jan 5 15:54:54 elmo sendmail[26923]: i05LsrU6026923: from=<[EMAIL PROTECTED]>, size=11575, class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>, bodytype=7BIT, proto=ESMTP, daemon=MTA, relay=xxxxxx.xxxxxxx.com []
Jan 5 15:54:54 elmo spamd[26916]: logmsg: connection from localhost.localdomain [127.0.0.1] at port 54468
Jan 5 15:54:54 elmo spamd[26916]: connection from localhost.localdomain [127.0.0.1] at port 54468
Jan 5 15:54:54 elmo spamd[26930]: debug: retrieving prefs for root from SQL server
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: report_header^I0
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: defang_mime^I0
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: blacklist_from
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: blacklist_from
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: bayes_learn_to_journal^I1
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: bayes_auto_learn_threshold_spa^I7.5
Jan 5 15:54:54 elmo spamd[26930]: debug: Failed to parse line in SpamAssassin configuration, skipping: bayes_auto_learn_threshold_non^I0.5
Jan 5 15:54:54 elmo spamd[26930]: logmsg: processing message <[EMAIL PROTECTED]> for root:800.

Dear gods.. it looks like your SQL'ed user_prefs (or your local.cf) is full of gobbldy gook... did you do something foolish like edit it on a windows box?


Those ^|'s should not be there. Fix all those broken lines that contain them.

Also the empty blacklist_from statements need to go... that's broken.

also, get rid of "defang_mime". That command is gone and is now illegal to in a SA configfile... It died a loooong loooong time ago when 2.50 was released..

Any "failed to parse line" error messages are an extraordinarily bad sign, and it means that the config line quoted is somehow mangled or illegal.



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to