Tony Stocker:
> Quick background, we recently shifted from a very old mail server running
> Postfix (~2.2.10) to a newer, though not cutting edge, one also running
> Postfix (~2.6.6). As much as practical the configuration files from the
> old server were used to provision the new server. For the most part
> everything seems to be working normally.
>
> However we have one oddity that we've noticed so far. We have several
> systems that use 'uuencode' and 'mailx' to send reports through the mail
> server, the basic format of the cron job that does these is like so:
>
> /usr/bin/uuencode "/logs/system/reports/${system}/ftpreport.${yesterday}"
> "${system}.ftpreport.${yesterday}" | /bin/mailx -s "FTP Report ${yesterday}
> ${system}" astocker
>
> These worked fine with the old server, the emails would arrive and have a
> file attachment, appropriately named '"${system}.ftpreport.${yesterday}"'.
>
> However the new server does not appear to be "attaching" the file to the
> email, but instead outputting the uuencode directly to the mail body. For
> example:
Postfix does not convert uuencoded content into an attachment. It
never did, and it never will. There simply is no code to do such things.
I recall that some MAIL READING programs will fake an atachment when
they see "begin xxx filename..." in an email message.
Wietse
