Re: [DNSOP] can someone forward this to benno?
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 using .forward files and /etc/aliases, or change email vendors, or change mailbox providers. This email behavior is unbecoming. p vixie On Apr 26, 2023 12:04, John Levine wrote: 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 mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] can someone forward this to benno?
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 mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] can someone forward this to benno?
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 dnsop-cha...@ietf.org and gets a message back saying the email could not be delivered, please email me directly. It will arrive. (At least one other IETF participant experienced the same problem and contacted me.) Best, -- Benno On 26/04/2023 18:49, Paul Vixie wrote: i don't know why it was rejected as spam but his sysadmin might. ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] can someone forward this to benno?
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 to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system (expanded from ): host mx.soverin.net[185.233.34.143] said: 554 5.7.1 Spam message rejected (in reply to end of DATA command) Reporting-MTA: dns; ietfa.amsl.com X-Postfix-Queue-ID: EAF7AC1519A1 X-Postfix-Sender: rfc822; paul@redbarn.org Arrival-Date: Wed, 26 Apr 2023 08:56:51 -0700 (PDT) Final-Recipient: rfc822; benno@NLnetLabs.nl Original-Recipient: rfc822;expand-dnsop-chairs@virtual.ietf.org Action: failed Status: 5.7.1 Remote-MTA: dns; mx.soverin.net Diagnostic-Code: smtp; 554 5.7.1 Spam message rejected --- Begin Message --- Shumon Huque wrote on 2023-04-26 08:43: I support adoption too. As I've mentioned earlier, this mechanism is widely deployed and needs a published specification. Adopting the work will also allow us to formally specify an accurate NXDOMAIN signal (and work out its related details more fully). Shumon. +1. On Sun, Apr 16, 2023 at 8:54 PM Tim Wicinski ... Please also indicate if you are willing to contribute text, review, etc. willing to contribute and review. -- P Vixie --- End Message --- --- End Message --- ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
