SCIENTIFIC-LINUX-DEVEL Archives

December 2012

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steven Haigh <[log in to unmask]>
Reply To:
Steven Haigh <[log in to unmask]>
Date:
Sat, 22 Dec 2012 16:14:09 +1100
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (3202 bytes) , smime.p7s (4 kB)
Hi Pat and co,

Just wondering if anything happened with this?

-- 
Steven Haigh

Email: [log in to unmask]
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

On 31/10/2012 12:35 AM, Pat Riehecky wrote:
> Sorry for the delay,
>
> I've been out of the office.
>
> I'll take a closer look at this patch some time this week.
>
> Pat
>
> On 10/30/2012 07:46 AM, Andrew Schretter wrote:
>> On 10/29/2012 08:08 PM, Steven Haigh wrote:
>>> On 27/10/2012 1:36 PM, Steven Haigh wrote:
>>>> On 27/10/2012 10:58 AM, David Sommerseth wrote:
>>>>>> Content-Type: application/octet-stream
>>>>>                   ^^^^^^^^^^^^^^^^^^^^^^^^
>>>>> This is somewhat odd, I'd expect this to be text/plain or 
>>>>> something in
>>>>> that direction.  But that's set based on the data the mailer 
>>>>> receives.
>>>>> If it contains some control characters or other binary bytes, it 
>>>>> might
>>>>> flip over to octet-stream.
>>>>>
>>>>>> Content-Transfer-Encoding: base64
>>>>>                                ^^^^^^
>>>>> The mail is encoded as base64.  At first glance, the mail headers 
>>>>> looks
>>>>> appropriate to me.  Which makes me wonder what kind of mail client 
>>>>> you
>>>>> use?
>> The problem is caused by bad RPMs that write out text during 
>> install/update/etc
>> and that text happens to contain non printable ASCII characters (like 
>> a carriage
>> return character or some garbage like that).  The mail program on 
>> linux sees
>> these characters and automatically converts the mail to base64 before 
>> sending
>> it.
>>
>> The patch I have to fix it is to put a " /usr/bin/tr -cd 
>> '\11\12\40-\176' " to
>> filter the yum response before it is mailed.  Works for me :
>>
>> --- /etc/cron.daily/yum-autoupdate.bak  2012-09-10 10:25:37.000000000 
>> -0400
>> +++ /etc/cron.daily/yum-autoupdate      2012-09-25 14:55:11.535869852 
>> -0400
>> @@ -322,7 +323,7 @@
>>                                                          echo " Mail 
>> Needs To Be Sent"
>>                                                          echo " 
>> /bin/mail -s \"YUM:$HOSTNAME:$TODAY\" $MAILLIST "
>>                                                  fi
>> -                                               cat $TEMPMAILFILE | 
>> /bin/mail -s "YUM:$HOSTNAME:$TODAY" $MAILLIST
>> +                                               cat $TEMPMAILFILE | 
>> /usr/bin/tr -cd '\11\12\40-\176' | /bin/mail -s
>> "YUM:$HOSTNAME:$TODAY" $MAILLIST
>>                                          fi
>>                                  else
>>                                          if [ "$DEBUG" = "true" ] ; then
>> @@ -330,7 +331,7 @@
>>                                                  echo "   Mail Needs 
>> To Be Sent"
>>                                                  echo " /bin/mail -s 
>> \"YUM:$HOSTNAME:$TODAY\" $MAILLIST "
>>                                          fi
>> -                                       cat $TEMPMAILFILE | /bin/mail 
>> -s "YUM:$HOSTNAME:$TODAY" $MAILLIST
>> +                                       cat $TEMPMAILFILE | 
>> /usr/bin/tr -cd '\11\12\40-\176' | /bin/mail -s
>> "YUM:$HOSTNAME:$TODAY" $MAILLIST
>>                                  fi
>>                          fi
>>                  fi
>>
>
>




ATOM RSS1 RSS2