On Fri, 6 Apr 2007, william(at)elan.net wrote:
you implimnent it, I'd suggest that instead of using BASE16 it be done
as BASE32 (but not BASE64 since email address is not case-sensetive)
and timestamp id could be smaller in BASE32 as well.
Actually, localpart is *supposed* to be case *preserving* according to
rfc2821. Systems may or may not be case sensitive for their own mailboxes, but
they should never alter the case in the localpart. There are some super
braindead systems out there, however, that smash case in the localpart.
I've gone back and forth. When signing/fowarding with SRS the sig is base64.
Sometimes I just block bounces with smashed case - if the MTA is that
braindead, the bounce probably isn't useful. But if you really want
the bounces (e.g. to blacklist the original sender that I've coded in
there ;-), then you have accept a case-insensitive match of the sig.
The domain part, OTOH, is not case sensitive.
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
please go to http://v2.listbox.com/member/?list_id=735