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:
Subject: FTP Report 20150716 hou
begin 644 hou.ftpreport.20150716
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2T*1E10(%)E=')I979A;"!297!O<G0@
M9F]R(&%R=&AU<FAO=2!F;W(@9&%T92`R,#$U,#<Q-@HM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+0HM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0IA8F9U;FM`9VUA
<snip>
%.#='0@H`
`
end
However, if I use 'mutt' and use the '-a [attachment]' things work as
expected.
Can anyone think of what could be causing this? I'd like to get it fixed,
mainly because I'm afraid it might be a symptom of a larger issue with
regards to attachments. I know I can always update the cron jobs to use
'mutt' but that doesn't solve the underlying issue with the mail server not
handling the uuencoded attachment in the expected manner.
Thanks in advance for your help.
Tony
