The message corpus found on dkim.org contains messages with illegal
expirations like "x=-1019102801;".
I'll be correcting these in the revised corpus I'm working on.
However, there is a question for the base spec: what should be done when
faced with an invalid expiration date such as that? Ignore it? Treat it
as a signature failure? Treat the message as always expired?
Tony Hansen
tony(_at_)att(_dot_)com
_______________________________________________
NOTE WELL: This list operates according to
<http://dkim.org/ietf-list-rules.html>