Sergio Manzi
Regular Pleskian
... and.... is it working?I've tried it with DMARC on and off, SPF on and off, and DKIM on and off, and have settled on this:
-----------------
@Giuseppe too had to turn off incoming DMARC checking or he had issues sending inter-domain messages on the same server. At this time I don't have enough information for understanding the reasons of this... will dig.
I am not sure if turning off incoming DMARC checking has any negative impact on forwarders from/to domains that have DMARC enabled. Only thing I can say is that with my configuration I don't have any problem, everything is working, and therefore I'm pushing you in the same direction.
If you have inter-domain issues with DMARC checking turned on, I'll concentrate on understanding why this is happening: is it a DKIM failure? Is it an SPF failure? There shouldn't be any other possible reason...
Someone (was it you GJ?) noticed that I have a very permissive policy (p=none) in my domains DMARCs: this is probably a mistake that I should correct. I've now changed it to p=reject for a couple of domains and will make tests with them (have to wait for TTL of the old policy to expire... give me some time...)
There is anyway one thing I noticed in the headers of my inter-domain-same-host messages: there is no DMARC there! DKIM is checked, SPF is implicitly pass because the sender is authenticated (Received-SPF: pass (mail.example.com: connection is authenticated)), but there is no trace of DMARC, while I see it in mail sent from an external domain to my host and I see it in the external domain when sent from my host. I think DMARC is not checked/enforced within the same host, but this is something that must be verified.
I'll let you know more when my DMARC p=reject will be in effect...