Since that is an email/dkim discussion and this is not the right forum for it I
will not argue it here. I will also not be changing my p= value. Noone should
forward an email message with unmodified headers in 2023. Encapsulate it rather
than forging my domain.
I'd like our chairs to stop usi
It appears that Paul Vixie said:
>-=-=-=-=-=-
>
>i don't know why it was rejected as spam but his sysadmin might.
>
It's because redbarn.org has a p=reject DMARC policy.
To summarize a lot of prior discussion, "don't do that".
R's,
John
___
DNSOP mai
Thank you Paul.
The problem seems to be with DKIM and header rewriting by
ietfa.amsl.com. We are in contact to resolve this, but it doesn't seem
easy. Turning off DKIM on my side doesn't seem like an option, but we're
working on an alternative solution.
If anyone else has this problem using
i don't know why it was rejected as spam but his sysadmin might.
--- Begin Message ---
This is the mail system at host ietfa.amsl.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail
