Re: [dmarc-ietf] RFC 7489 on Domain-based Message Authentication, Reporting, and Conformance (DMARC)

2015-03-18 Thread Murray S. Kucherawy
On Wed, Mar 18, 2015 at 1:19 PM, Tim Draegen t...@eudaemon.net wrote: Hi Murray Elizabeth, thanks for wrestling this through the process. The Working Group can now adopt this as input. /goes off to figure out which buttons need to be pushed =- Tim I have to resubmit it as

Re: [dmarc-ietf] Next steps for RFC 7489 (DMARC)

2015-03-18 Thread Douglas Otis
Dear DMARC WG, Now that RFC7489 has been published, there remains several unresolved problems this WG is charted to resolve, primarily-- 1. Addressing the issues with indirect mail flows These are reviewed by https://tools.ietf.org/html/draft-dmarc-interoperability-00

Re: [dmarc-ietf] Next steps for RFC 7489 (DMARC)

2015-03-18 Thread Terry Zink
Based upon the almost complete lack of interest of bulk email providers at promoting a solution, it seems the path forward is to define a new non-aligned header field able to retain the author role information, otherwise the From is likely overwritten as the only practical means of ensuring

[dmarc-ietf] Fwd: RFC 7489 on Domain-based Message Authentication, Reporting, and Conformance (DMARC)

2015-03-18 Thread Murray S. Kucherawy
FYI: -- Forwarded message -- From: rfc-edi...@rfc-editor.org Date: Wed, Mar 18, 2015 at 1:04 PM Subject: RFC 7489 on Domain-based Message Authentication, Reporting, and Conformance (DMARC) To: ietf-annou...@ietf.org, rfc-d...@rfc-editor.org Cc: drafts-update-...@iana.org,

Re: [dmarc-ietf] RFC 7489 on Domain-based Message Authentication, Reporting, and Conformance (DMARC)

2015-03-18 Thread Tim Draegen
Hi Murray Elizabeth, thanks for wrestling this through the process. The Working Group can now adopt this as input. /goes off to figure out which buttons need to be pushed =- Tim On Mar 18, 2015, at 4:08 PM, Murray S. Kucherawy superu...@gmail.com wrote: FYI: -- Forwarded

Re: [dmarc-ietf] Formal specification, URI

2015-03-18 Thread Murray S. Kucherawy
On Tue, Mar 17, 2015 at 8:23 AM, Alessandro Vesely ves...@tana.it wrote: Right, which is why things like semi-colon don't need to be percent-encoded; they're already special characters in the context of a URL. So are comma and exclamation. What puzzles me is that DMARC spec treats them