Path: csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.glorb.com!usenet.stanford.edu!not-for-mail From: Bob Proulx Newsgroups: gnu.utils.bug Subject: Re: Upgrading from RHEL5x to RHEL 7x Date: Mon, 4 Apr 2016 11:26:25 -0600 Lines: 68 Approved: bug-gnu-utils@gnu.org Message-ID: References: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1459790796 23369 208.118.235.17 (4 Apr 2016 17:26:36 GMT) X-Complaints-To: action@cs.stanford.edu Cc: "bug-gnu-utils@gnu.org" To: Prasad Kumar Envelope-to: bug-gnu-utils@gnu.org Mail-Followup-To: Prasad Kumar , "bug-gnu-utils@gnu.org" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 96.88.95.61 X-BeenThere: bug-gnu-utils@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU utilities List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.utils.bug:2200 Prasad Kumar wrote: > We are upgrading from RHEL 5.x to RHEL 7x. >... > Now even after we installed uuencode from shareutils , the same > command is not working in RHEL 7 linux. > > We get attachment as Junk Characters in the Email body for any > attachment we send. This is happening with mail command used like > below. > > $ uuencode Attachement_file.pdf Attachements.pdf |mail -s "This is Attachment Mail" prasad_kumar@... I don't have easy access to test systems for RHEL 5 and 7 and therefore can't easily try to recreate this problem. But it seems likely to me that the problem may just as easily be in the mail part of the command. > Can some one let me know what is this issue and how to resolve this. Please reduce the problem size. Please try uuencoding a small test file on both systems and comparing the output produced. Then if the output is the same you know the problem is not the uuencode but the mail side of things. On the other hand if they are differen then there will be a very small test case that can be shared in which to further debug the problem. umask 02 echo "Now is the time" > testfile1 uuencode testfile1 testfile1 > output1 cat output1 begin 664 testfile1 03F]W(&ES('1H92!T:6UE"@`` ` end Hopefully a small test like that on both systems will show that the output of uuencode is the same on both systems. If not then we would want to know the versions of each. Additionally to look only at the mail side of the problem you can test by creating a test file to mail using your problem file on your working RHEL 5 system. uuencode Attachement_file.pdf Attachements.pdf > uuencode.data1 md5sum uuencode.data1 ... save this ... Mail it from the RHEL 7 system. mail -s "This is Attachment Mail" prasad_kumar@... < uuencode.data1 Then copy that file to the RHEL 7 system that you suspect of problems. Verify that the copy is correct be comparing the md5sum. Then mail it from there. ...copy file to RHEL 7 system ... md5sum uuencode.data1 ... compare to verify that the copy was identical ... mail -s "This is Attachment Mail" prasad_kumar@... < uuencode.data1 If this second mail message is corrupted as you describe then again you know the problem is in the mail side of things and not the uuencode side of things since the file will have been identical in both places. Bob