How about "DKIM-Cooperative"?
I'd suggest DKIM aware, unless you think there are list operators who are
actively DKIM hostile.
{{ I'd have thought that citing the l= capability here would be appropriate,
for
completeness. }}
I think it was there in earlier versions but was removed because the WG
generally dislikes use of "l=" for the reasons specified in the base
document. It also only handles appended text, but not prepended text,
for example.
Please leave it out -- the cases it covers are such a small fraction of
the ways that a list will break a signature that it just confuses the
issue.
If an author knows that the MLM to which a message is being sent is a
non-participating resending MLM, the author SHOULD be cautious when
deciding whether or not to send to the list when that mail would be
I'd prefer taking entire section out, unless we want to make a deep dive
into the swamp of offering advice to work around the ways we think that
other people's software is broken. Just sign your fripping mail.
arrives via a list to a verifier that applies ADSP checks which fail,
the message SHOULD either be discarded (i.e. accept the message at
the [SMTP] level but discard it without delivery) or rejected by
{{ Is this describing anything different than would/should take place for
mail
that did NOT go througha list? The text seems to be describing a special
case
but in fact it isn't. It's just an ADSP failure. }}
The alternative suggestion is that if it has a sufficiently credible
signature, accept it and forget about ADSP. See above-mentioned swamp.
{{all messages are from the author. what distinctive condition is this
trying
to describe? messages signed with the author domain? I don't understand the
point of the "As such" sentence. The rest of the paragraph is also
confusing to
me. I'm not sure what to suggest to make it clearer. }}
This came from a use case John submitted.
A and C are subscribed to B. A sends to B, which goes to C. But C
doesn't want to be on the list anymore and can't seem to unsubscribe.
In frustration, C begins reporting B traffic as spam, which begins to
negatively affect the reputation of A's signed mail.
I definitely get FBL reports from Yahoo for mail I've sent to lists. It's
really not an author issue as much as an original ADMD vs. list's ADMD
issue.
Regards,
John Levine, johnl(_at_)iecc(_dot_)com, Primary Perpetrator of "The Internet
for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html