Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Issues with the dmarc/dkim plugins
2 views
Skip to first unread message
salv...@gmx.ch
Jan 3, 2015, 8:15:02 PM1/3/15
to qps...@perl.org
I'm having a fatal issue with the dmarc plugin: when it's enabled then I get "Out of memory!" when trying to receive mail from
-- gmail
-- check...@verifier.port25.com
-- check...@auth.returnpath.net
I'm not passing any parameters to dmarc, and upping the memory limit from 128MB to 196MB in the xinetd configuration file has not made any difference. This occurs with all of the following versions:
-- ee01a07 (2014-12-22 15:01:12 -0800),
-- a515e2b (2014-12-30 13:58:21 -0800), and
-- HEAD
Seeing that there were changes in dkim/dmarc between ee01a07 and a515e2b, I've decided to try the latter and that one still advertises "AUTH". This puts the AUTH breakage into the last 10 commits.
There's a minor issue with dkim, too: check...@verifier.port25.com reports "permerror (no usable key records)". However, it also says:
NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions. If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.
The other two test hosts say "pass", so I'm not sure where the problem is.
-- gmail
-- check...@verifier.port25.com
-- check...@auth.returnpath.net
I'm not passing any parameters to dmarc, and upping the memory limit from 128MB to 196MB in the xinetd configuration file has not made any difference. This occurs with all of the following versions:
-- ee01a07 (2014-12-22 15:01:12 -0800),
-- a515e2b (2014-12-30 13:58:21 -0800), and
-- HEAD
Seeing that there were changes in dkim/dmarc between ee01a07 and a515e2b, I've decided to try the latter and that one still advertises "AUTH". This puts the AUTH breakage into the last 10 commits.
There's a minor issue with dkim, too: check...@verifier.port25.com reports "permerror (no usable key records)". However, it also says:
NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions. If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.
The other two test hosts say "pass", so I'm not sure where the problem is.
Hans Salvisberg
Jan 4, 2015, 12:45:02 PM1/4/15
to Matt Simerson, qps...@perl.org
I've set rlimit_as=UNLIMITED (8GB in the host) and this hasn't made any difference.
Actually, the culprit is not dkim but dmarc. Commenting out dmarc lets the mails come in.
(I can't try it the other way around, because dmarc crashes if dkim isn't active.)
Hans
Gesendet: Sonntag, 04. Januar 2015 um 03:21 Uhr
Von: "Matt Simerson" <ma...@tnpi.net>
An: "salv...@gmx.ch" <salv...@gmx.ch>
Cc: "qps...@perl.org" <qps...@perl.org>
Betreff: Re: Issues with the dmarc/dkim plugins
Von: "Matt Simerson" <ma...@tnpi.net>
An: "salv...@gmx.ch" <salv...@gmx.ch>
Cc: "qps...@perl.org" <qps...@perl.org>
Betreff: Re: Issues with the dmarc/dkim plugins
DKIM needs more RAM, bump up to at least 256MB.
Matt
Matt
0 new messages