Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now

New answers tagged

1

That implies, that 8 reported mails from same source server failed both DKIM and SPF check and 57 failed only SPF check. So not all mails are DKIM signed (or not correctly or not sufficiently "relaxed" but the repor implies they do not have a syntactical correct signature as no selector is mentioned for the failed, left byside the fact that the ...


-1

I know it's late but it is failing because of what you see in this line: Received: from mail.morpheu5.net ([172.18.0.14]) by 6c01c2ccb641 with LMTP Specifically the by 6c01c2ccb641 with LMTP If you can match it so that 6c01c2ccb641 also shows up as mail.morpheu5.net , it will work just fine.


0

I had the same problem too - turned out to be a typo (on Ubuntu 16 - did not work after upgrade from 14). I missed the "inet" part of the adress (also given in original question, I just hat "8891@localhost" and not "inet:8891@localohst") from the /etc/default/opendkim. Also, I had the very same setting in the /etc/opendkim.conf before, which seems to be ...


0

DKIM signing doesn’t make a lot of sense for locally delivered mail - the server assumes it can trust itself. Try sending mail to an external domain and look at those headers instead.


0

After a bit of more tweaking I finnally got it to work. Here is an explanation of what is going on. Z-push is written in PHP and what I could find on the Internet, was that PHP mail settings is controlled via php.ini. In php-ini-file you will be told that the only option available when sending mail is through sendmail and therefore all received mails ...


1

The following will trigger on any message which lacks a DKIM-Signature: header. There is no attempt as such to validate the DKIM signature (which would make more sense to perform on the mail server anyway; I'm guessing yours might already be doing this.) :0 * ! ^DKIM-Signature: .spam In Procmail terminology, this is saving (or sorting or storing) the ...


1

It seems to me that the -all "hard fail" for Microsoft SPF could be the cause. If the receiving system has a mechanism for enforcing BOTH SPF and DMARC, then the SPF "hard fail" would cause this message to fail, even though DMARC would pass it due to the DKIM pass. Remember, SPF is it's own thing and was around before DMARC. One of the problems with using it,...


Top 50 recent answers are included