On Mon, Apr 12, 2004 at 04:46:45PM -0700, Dave Tweten wrote: > I'm tired of dealing with people who misconfigure their mail user agents > to use x-uuencode instead of base64 as the Content-Transfer-Encoding for > their MIME attachments.
I am completely ignorant here. What exactly is wrong with uuencode as long as it is announced in the header? > I'm hoping for a technological solution (i.e., capitulation). Is > there some way to stitch public domain uudecode into exmh so it can > handle these non-compliant attachments? And wouldn't this fit rather on some mailing list related to uuencode or exmh? Andre'
