uuencoded file sent by mail shows up (wrongly) as attachment
Mihai Matei
mihaimilk at yahoo.com
Wed Jun 18 17:37:36 UTC 2008
Hi,
I want to send an uuencoded file as the body of an email messsage like this:
uuencode /myfile myfile | mail -s TEST myaddress at test.com
On SuSE the resulting mail message has:
_________________________________
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
_________________________________
and the uuencoded file is in the body of the message.
On RedHat 3 and 4, the message body is blank, and the uuencoded file is an attachment:
______________________________________________
...
--_76d2268d-69f1-4e7c-a3e9-db07e547d666_
Content-Type: text/plain
--_76d2268d-69f1-4e7c-a3e9-db07e547d666_
Content-Transfer-Encoding: uuencode
Content-Disposition: attachment; filename="/myfile"
Content-Type: application/octet-stream;
name="/myfile"
...
_______________________________________________
Is the content automatically recognized as an uuencoded file by the mail client? Then why is it changing the "Content-Type" to "application/octet-stream" ? Due to this, the receiver of the mail cannot process it successfully.
Is there any way I can send the uuencoded file in the body of the message, and not as an attachment?
Thanks.
More information about the redhat-list
mailing list