Doug Traylor wrote: > Excellent, although I have been a little leary to use too many regex's due > to fear of the unknown. What, please, is the key to that one that > identifies a uuencoded email? >
The keys are the "begin", "end", and the character lengths in between. It has been a while since I looked into it, but when I did - I researched the spec on uuencoding, and a worked with multiple examples of various size uuencoded attachments to make a RegEx that worked properly. > I believe I could get away with that too. > I'm 99.9% positive that anyone can. I've dealt with being sent automated emails with attachments from mainframes, and they weren't using uuencoding either. Its an old standard that isn't actually a standard any longer. > Correction, Outlook Express, potentially the most common email client in the > world, doesn't use uuencode by _default_. It is very easy to turn it on and > I do see email come through that appears to be from valid sources, with > uuencoding. > Granted, the ability to be backward compatible exists in most modern applications. But its off by default across the board. Choosing to block uuencoding is a choice. But its a choice I cannot imagine anyone having an issue with. Anyone intentionally having a need to uuencode will very likely have a greater understanding of email, and will know how to deal with the situation. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
