-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <[email protected]
il.com>, Douglas Foster <[email protected]> writes

>Richard, I am severely disappointed by your critique.

I think that's to be expected :)

>It misses the conclusion, which is that we have a missed opportunity
>because SMTP state is not preserved in the Received header field.

as you observed yourself ... the relevant WG took the view that it was
not realistic to attempt to address the wide variation of validly
formatted (but super-hard to parse) Received header fields. I concur
with that view.

>   This
>can change by convincing the relatively small number of MTA software
>providers to alter how they construct a Received header field.

we think the number of markedly distinct DKIM codebases out there is
probably less than 20 ... because most people started from one of the
libraries that were implemented at an early stage

If there are less than 1000 distinct SMTP codebases I would be rather
surprised. This is of course relatively small compared with the half
million or so systems that regularly send email. But it is still quite a
substantial number of cats to shepherd

>An overly-broad SPF policy is a problem, but it can be corrected by local
>policy that limits acceptable results to a smaller set of source servers.
>  This is not much different than using local policy to correct a published
>SPF policy from "IP:address" to "IP4:address" to avoid a PermError result.

I have never tried to do that ... do you have much success. The main
reason that people set their SPF to be "anywhere in this cloud" is
because they are spinning resources up and down according to demand and
so they truly do not know where they will be sending from next

[...]

>we routinely receive ARC
>sets which indicate that a message was signed after failing SPF, DKIM, and
>DMARC,   We hope that the outbound gateway authenticated the client by some
>method other than SPF, DKIM, and DMARC, but we cannot know.

I think some examples would assist this WG in understanding how
successful the ARC experiment has actually been. Some people have been
lauding its value to them == perhaps they don't get email from the
relevant senders, or perhaps they have been fooled !

>There are other problems with DKIM.

which is relevant to this WG in what way ?

- -- 
richard @ highwayman . com                       "Nothing seems the same
                          Still you never see the change from day to day
                                And no-one notices the customs slip away"

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBah2IRWHfC/FfW545EQIrKACgz6F+boS7SNGFRAHhWzvWkjrbGpQAoPJd
n2qh8I4AzaMarnk2jl06mxOr
=M7q4
-----END PGP SIGNATURE-----

_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to