On 16. feb. 2015 00.59.42 Alex Regan <mysqlstud...@gmail.com> wrote:

Hi,

>> Could this somehow be related to the SVN spamassassin?
>> Ideas greatly appreciated.
>
> check *.pre files or install mail-dkim in feodore, possible make a bug
> in feodore if not working, was mail-dkim not suggest rpm package when
> instaling ?
>
> possible test "spamassassin 2>&1 -D --lint | less" see if more rpm
> modules are missing, if so report to rpm maintainer
>
> this is not a upstream bug

lint shows no errors. It also appears to not use DKIM or SPF because it
isn't a real message, however:

Feb 15 18:51:50.500 [22703] dbg: spf: cannot get Envelope-From, cannot
use SPF

set envelope_sender_header in local.cf to what your mta uses

for postfix its Return-Path


It does load them during lint however:

Feb 15 18:51:22.935 [22703] dbg: diag: [...] module installed:
Mail::SPF, version v2.009
Feb 15 18:51:22.935 [22703] dbg: diag: [...] module installed:
Mail::DKIM, version 0.4

seems ok


I've done a little more testing, and it certainly sounds like a local
configuration issue, but it only happens on mbox files. The ones I've
tested have only one message.


imho unrelated

I've now built the latest from svn and using it for testing here.


okay as long you only have one installed, and make sure all deps are fine

Tests on a few other mbox messages have produced similar errors for SPF
as well as DKIM.

you have spf configured to use Recieved-SPF


# spamassassin -t --mbox -D < mymbox 2>&1 | less
Feb 15 18:44:41.340 [16434] dbg: spf: checking to see if the message has
a Received-SPF header that we can use
Feb 15 18:44:41.383 [16434] dbg: spf: cannot load Mail::SPF module or
create Mail::SPF::Server object: Insecure dependency in require while
running with -T switch at
/usr/share/perl5/vendor_perl/Mail/SPF/Server.pm line 28.
Feb 15 18:44:41.383 [16434] dbg: spf: [...] BEGIN failed--compilation
aborted at /usr/share/perl5/vendor_perl/Mail/SPF/Server.pm line 28.
Feb 15 18:44:41.383 [16434] dbg: spf: [...] Compilation failed in
require at /usr/share/perl5/vendor_perl/Mail/SPF.pm line 29.
Feb 15 18:44:41.383 [16434] dbg: spf: [...] BEGIN failed--compilation
aborted at /usr/share/perl5/vendor_perl/Mail/SPF.pm line 29.
Feb 15 18:44:41.383 [16434] dbg: spf: [...] Compilation failed in
require at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/SPF.pm
line 500.
Feb 15 18:44:41.383 [16434] dbg: spf: attempting to use legacy
Mail::SPF::Query module instead
Feb 15 18:44:41.383 [16434] dbg: spf: cannot load Mail::SPF::Query
module: Can't locate Mail/SPF/Query.pm in @INC (you may need to install
the Mail::SPF::Query module) (@INC contains: lib
/usr/share/perl5/vendor_perl /usr/local/lib64/perl5
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5
/usr/share/perl5) at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/SPF.pm line 528.
Feb 15 18:44:41.383 [16434] dbg: spf: one of Mail::SPF or
Mail::SPF::Query is required for SPF checks, SPF checks disabled


try remove mail-spf, and install mail-spf-query, report the above upstream in fedora if it happend with spamassassin with rpm install

However, if I run it on a non-mbox message, it invariably passes without
any problems loading SPF and DKIM support.

irelevant


Feb 15 18:54:55.121 [22868] dbg: spf: checking to see if the message has
a Received-SPF header that we can use
Feb 15 18:54:55.175 [22868] dbg: spf: using Mail::SPF for SPF checks
Feb 15 18:54:55.176 [22868] dbg: spf: already checked for Received-SPF
headers, proceeding with DNS based checks

see this is a plugin configure to reuse that header, so here sa does not do it self

Feb 15 18:54:55.224 [22868] dbg: rules: ran eval rule SPF_HELO_PASS
======> got hit (1)

Feb 15 18:54:54.923 [22868] dbg: rules: ran header rule __DKIM_EXISTS
======> got hit: "<YES>"
Feb 15 18:54:54.923 [22868] dbg: rules: ran header rule __HAS_DKIM_SIGHD
======> got hit: "<YES>"
Feb 15 18:54:55.090 [22868] dbg: dkim: using Mail::DKIM version 0.4
Feb 15 18:54:55.113 [22868] dbg: dkim: VALID DKIM,
i=@sendreceivenow.com, d=sendreceivenow.com, s=lm2, a=rsa-sha256,
c=relaxed/relaxed, key_bits=1024, pass

Thanks,
Alex

more then one issue to resolve :)

Reply via email to