Re: Content-Transfer-Encoding
[EMAIL PROTECTED] said: ... wouldn't this fit rather on some mailing list related to uuencode or exmh? Obviously, you are right. A fit of brain-fade on my part caused me to send to the wrong list. My apologies to all for wasted bandwidth. -- M/S 258-5|1024-bit PGP fingerprint:|[EMAIL PROTECTED] NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416 Moffett Field, CA 94035-1000| 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377 Not an official NASA position. You can't even be certain who sent this!
Re: Content-Transfer-Encoding
[EMAIL PROTECTED] said: ... wouldn't this fit rather on some mailing list related to uuencode or exmh? Obviously, you are right. A fit of brain-fade on my part caused me to send to the wrong list. My apologies to all for wasted bandwidth. -- M/S 258-5|1024-bit PGP fingerprint:|[EMAIL PROTECTED] NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416 Moffett Field, CA 94035-1000| 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377 Not an official NASA position. You can't even be certain who sent this!
Re: Content-Transfer-Encoding
[EMAIL PROTECTED] said: >... wouldn't this fit rather on some mailing list related to uuencode or exmh? Obviously, you are right. A fit of brain-fade on my part caused me to send to the wrong list. My apologies to all for wasted bandwidth. -- M/S 258-5|1024-bit PGP fingerprint:|[EMAIL PROTECTED] NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416 Moffett Field, CA 94035-1000| 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377 Not an official NASA position. You can't even be certain who sent this!
Re: Content-Transfer-Encoding
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'
Re: Content-Transfer-Encoding
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'
Re: Content-Transfer-Encoding
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'
Content-Transfer-Encoding
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'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? Help, and even commiseration, will be appreciated. -- M/S 258-5|1024-bit PGP fingerprint:|[EMAIL PROTECTED] NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416 Moffett Field, CA 94035-1000| 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377 Not an official NASA position. You can't even be certain who sent this!
Content-Transfer-Encoding
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'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? Help, and even commiseration, will be appreciated. -- M/S 258-5|1024-bit PGP fingerprint:|[EMAIL PROTECTED] NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416 Moffett Field, CA 94035-1000| 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377 Not an official NASA position. You can't even be certain who sent this!
Content-Transfer-Encoding
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'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? Help, and even commiseration, will be appreciated. -- M/S 258-5|1024-bit PGP fingerprint:|[EMAIL PROTECTED] NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416 Moffett Field, CA 94035-1000| 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377 Not an official NASA position. You can't even be certain who sent this!
