Tag Info

New answers tagged


Unfortunately, it's a well-known fact that DMARC and some mailing lists are effectively incompatible. The same problems originally stemmed from SPF itself, and have prompted mailing lists (as well as forwarding services) to implement a feature known as SRS (Sender Rewriting Scheme), which is a feature that must be implemented by the mailing list operators. ...


Solution: As @masegaloeh said dkim-milter discontinue. Just installed OpenDKIM and problem has been resolved.


I just check the authenticated_sender variable when setting the dkim_domain. dkim_domain = ${if def:authenticated_sender {DKIM_DOMAIN}} This includes both SMTP authenticated clients and local users. You could put that condition around any of the mandatory DKIM options, including dkim_domain, dkim_selector or dkim_private_key. You could also build a more ...


Tell your support engr to read the RFC. That will keep them busy while you solve the problem yourself. ;) DNS RFC does not allow underscore in host names: http://www.zytrax.com/books/dns/apa/names.html But underscore certainly should be allowed in the subdomains. Here is a blurb on it: http://domainkeys.sourceforge.net/underscore.html Back to your ...


Try changing ex-mail.com to ex-mailer.com in your key file.


In regard to question #1, it is something of a judgement call, but I'd probably create keys for all the domains being used in the From addresses, and sign emails with the appropriate DKIM key. This approach means that the From address and the DKIM authentication will be aligned. That makes it easy to turn on DMARC at some point in the future. As for ...


DKIM does not fully mitigate this kind of attacks, but plays an important role. By checking the DKIM signature it is possible to detect changes to the message on the transport from the original sender to the receiver. It is not possible for the receiver to find out if the message should have a DKIM signature, because the receiver does not know the selector ...

Top 50 recent answers are included