Hi,

running latest version of dkim-filter on two systems:

System 1 (MX value 20): running Postfix 2.6.5 and latest version of 
dkim-filter on Ubuntu server:

dkim-filter: Sendmail DKIM Filter v2.8.3
        Compiled with OpenSSL 0.9.8g 19 Oct 2007
        Supported signing algorithms:
                rsa-sha1
                rsa-sha256
        Supported canonicalization algorithms:
                relaxed
                simple
        Active code options:
                _FFR_DKIM_REPUTATION
                _FFR_MULTIPLE_SIGNATURES
                _FFR_PARSE_TIME
                _FFR_STATS

System 2: (MX value 10): running Sun Java System Messaging Server 7.0 
update 3, with latest version of dkim-filter on RedHat EL 5:

dkim-filter: Sendmail DKIM Filter v2.8.3
        Compiled with OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
        Supported signing algorithms:
                rsa-sha1
                rsa-sha256
        Supported canonicalization algorithms:
                relaxed
                simple

Today I discovered that dkim-milter rejected messages, while I have (as 
far as I know) no configuration settings that would explain this rejection.

AFAICS there are three settings in dkim-filter.conf that could make a 
message be rejected:

ADSPDiscard
ADSPNoSuchDomain
RequiredHeaders

Default for all of them is 'no' which means: do not reject. In my 
configuration I did not explicitely define them, so they should not be 
responsible for the reject action (correct?).

The two most recent log entries on system 1 are:

Dec 16 23:11:09 lynx postfix/cleanup[21219]: A600B70395: milter-reject: 
END-OF-MESSAGE from russian-caravan.cloud9.net[168.100.1.4]: 4.7.1 
Service unavailable - try again later; 
from=<[email protected]> to=<[email protected]> 
proto=ESMTP helo=<russian-caravan.cloud9.net>
Dec 16 23:27:24 lynx postfix/cleanup[21347]: 3224870395: milter-reject: 
END-OF-MESSAGE from 128-220.colo.introweb.nl[84.241.128.220]: 4.7.1 
Service unavailable - try again later; from=<[email protected]> 
to=<[email protected]> proto=ESMTP helo=<lisa.crolox.nl>

The most recent log entries on system 2 are:

16-Dec-2009 23:08:44.88 tcp_internet              JE 0 
31:[email protected] 7:rfc822; 0: 0: 3:msg 
52:russian-caravan.cloud9.net ([unknown] [168.100.1.4]) 33:451 4.3.2 
Milter rejected message
16-Dec-2009 23:25:01.10 tcp_internet              JE 0 
25:[email protected] 7:rfc822; 0: 0: 3:msg 43:lisa.crolox.nl 
([unknown] [84.241.128.220]) 33:451 4.3.2 Milter rejected message

Please note: the timestamps do correlate, although it seems they do not; 
one of the systems is running NTP and the other does not yet).

What can dkim-milter make reject a message in this way?

/rolf


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss

Reply via email to