Philippe Ratté skrev den 2013-02-19 16:15:
1: spamassassin 2>&1 -D --lint | less
2: perldoc Mail::SpamAssassin::Plugin::SPF
could still be relevant problem if its added remotely and not
localy,
but this is why i asked 1: on above, can you post it to pastebin and
give a link here ?
http://pastebin.com/xErBy0ej
Feb 19 10:02:25.354 [19195] dbg: spf: cannot get Envelope-From, cannot
use SPF
is this why whitelist_from are the only one that works ?
first get it to work from local.cf, if this is working move the same
rule to sql is the right way to test
if envelope-from is non default, then set it in local.cf, info here
perldoc Mail::SpamAssassin::Conf
postfix is using Return-Path, if you are using another mta you may
change this in the settings so spf does not say it does not find
envelope-from as above
2: is just informative to you what to configure in local.cf
Ok, will try whitelist_from_spf
i noticed you are using openprotect rule set with 99% depricated rule
sets :(
why not just use spamassassin rule sets ?
and a side note:
dont loadplugin from an cf file, use pre files for loadplugin, see
freemail error in your pastbin its gets loaded twice :(
if you can add the missing perl modules then do it, but i cant remember
if it solves problems, it depends on what to test
for the sql whitelist use same preferences as it would be in
local.cf,
and btw have you multiple sql users preferences or just one ?, is it
really checking the right user ?
Just one user prefs in the DB for this user, how can't I be sure that
it's checking the right user? Other whitelist_from all work
lets solve envelope sender first
