Hello Matt, Thanks for your prompt reply.
I've removed all whitelist_from entries from configuration files, even those from user_prefs files. I've already tried to run SA with -D option, but got no answer at all... This start happening just after the upgrade. Please note that I've read several times the INSTALL and UPGRADE instructions before do the upgrade... Best regards -- Marcos Saint'Anna [EMAIL PROTECTED] You wrote: MK> At 08:42 PM 10/9/2004 -0300, Marcos Saint'Anna wrote: >>SPAM... So I noticed that almost all headers had a "USER_IN_WHITELIST" >>in it. >> >>--- >>X-Spam-Status: No, hits=-88.6 required=5.0 tests=BR_RECEIVED_SPAMMER, >> >> FORGED_MUA_OUTLOOK,FORGED_OUTLOOK_HTML,HTML_FONT_BIG,HTML_MESSAGE, >> HTML_TAG_EXIST_TBODY,INVALID_DATE,MIME_BASE64_TEXT, >> >> MIME_BOUND_NEXTPART,MIME_HTML_ONLY,PLING_PLING,USER_IN_WHITELIST >> autolearn=no version=3.0.0 >>--- >> >>I've checked every configuration file as so user_prefs files and >>didn't found any whitelist entry. MK> Did you find *any* whitelist statements at all? MK> Also be sure to scrutinize ALL the message headers when trying to check MK> which statement is at fault. MK> SA's whitelisting system honors more than just From: in whitelist_from*. It MK> honors Return-Path, Sender, Resent-From and more-or-less any origin MK> indicating header.
