1) Signature Validates:
2) Signature fails to validate because the originator screwed up
3) Signature fails to validate because the sender screwed up
4) Signature fails to validate because of an intermediary acting for the
recipient (mailing list, forwarder, etc.).
The first case is success, the second and third cases are self healling.
Its only the fourth case that leads to an issue and it is easy for Cisco to
fix. They simply issue a separate email address for receiving mail from mailing
lists. Many of them seem to do this already. I note that Michael is one of them.
Speaking as a real live, currently employed, sysadmin (numbers bigger
than all the scientists in the entire world put together --- just
kidding with you Phillip)... "Yikes!"
Do I need a separate email for when I am living out of a suitcase for
6 months at Holiday Inn too? (I know I can use the same one as my
mailing list address) Now the guy I emailed is using that address in
his address book. Note to self, email him and get him to change it.
Can we figure something else out that doesn't require me (or my 200k+)
users to have to remember two separate addresses, the cases to use
each, and remember what the second one is the first time they have to
use it in 5 years?
Regards,
Damon Sauer
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html