Path: csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.glorb.com!usenet.stanford.edu!not-for-mail From: Prasad Kumar Newsgroups: gnu.utils.bug Subject: Re: Upgrading from RHEL5x to RHEL 7x Date: Mon, 4 Apr 2016 20:41:04 +0000 Lines: 161 Approved: bug-gnu-utils@gnu.org Message-ID: References: , <20160404111348680849282@bob.proulx.com> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1459803682 30195 208.118.235.17 (4 Apr 2016 21:01:22 GMT) X-Complaints-To: action@cs.stanford.edu Cc: "bug-gnu-utils@gnu.org" To: Bob Proulx Envelope-to: bug-gnu-utils@gnu.org Thread-Topic: Upgrading from RHEL5x to RHEL 7x Thread-Index: AQHRjiV+kOntMhBZgkaabSS3xyose596Ee+AgAAt9ms= In-Reply-To: <20160404111348680849282@bob.proulx.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=softfail (sender IP is 25.152.200.59) smtp.mailfrom=hotmail.com; gnu.org; dkim=none (message not signed) header.d=none; gnu.org; dmarc=fail action=none header.from=hotmail.com; received-spf: SoftFail (protection.outlook.com: domain of transitioning hotmail.com discourages use of 25.152.200.59 as permitted sender) x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [v3BZWd8y9Q0dHxYGpBXLsTCRvAgO0TRs] x-eopattributedmessage: 0 x-forefront-antispam-report: CIP:25.152.200.59; IPV:NLI; CTRY:GB; EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:MA1IND01HT014; H:BM1PR01MB0068.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:SoftFail; MLV:ovrnspm; MX:1; A:1; LANG:; x-ms-office365-filtering-correlation-id: a5b2c64c-bfc5-43d0-6b91-08d35cc9719f x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5061506196)(5061507196); SRVR:MA1IND01HT014; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:MA1IND01HT014; BCL:0; PCL:0; RULEID:; SRVR:MA1IND01HT014; x-forefront-prvs: 0902222726 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2016 20:41:04.5857 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: MA1IND01HT014 X-OriginalArrivalTime: 04 Apr 2016 20:41:09.0263 (UTC) FILETIME=[517881F0:01D18EB2] X-detected-operating-system: by eggs.gnu.org: Windows 7 or 8 [fuzzy] X-Received-From: 65.54.190.144 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:2201 Hi Bob, First I want to Thank you for looking into my issue. Firstly uuencode versions of RHEL7 uuencode --version uuencode (GNU sharutils) 4.13.3 Copyright (C) 1994-2013 Free Software Foundation, Inc., all rights reserved= . This is free software. It is licensed for use, modification and redistribution under the terms of the GNU General Public License, version 3 or later uuencode versions of RHEL5 uuencode --version uuencode (GNU sharutils) 4.6.1 Copyright (C) 1994, 1995, 1996, 2002, 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Test Cases are Below ---------------------------- 1. Created Script in RHEL7 and RHEL 5 Instance for umask 02 echo "Now is the time" > testfile1 uuencode testfile1 testfile1 > output1 Got Same output in both Instance. begin 664 testfile1 03F]W(&ES('1H92!T:6UE"@`` ` end 2. Created Script in RHEL5 uuencode Attachement_file.pdf Attachements.pdf > uuencode.data1 md5sum uuencode.data1 Sent mail from RHEL5 ( the Attachment was good no Issues) mail -s "This is Attachment Mail" prasad_kumar@hotmail.com < uuencode.data= 1 =20 Saved and transfered the uuencode.data1 to RHEL7=20 Sent mail from RHEL7 (Attachment is Corrupted) 1. mail -s "This is Attachment Mail" prasad_kumar@hotmail.com < uuencode.da= ta1 The Attachment is not there instead I get Junk in Body of the mail. begin 660 Attachements.pdf M)5!$1BTQ+C0*)*QDI8CD[)' M-.F5=3D8QP#\;>7'O8+WG9M:KRHC=3DGLZF4I925A_S]=3D..8DUK9RG#M*I,?B,%\ M:#0:W8WVIY@F+*;XUW]^N.E>_IS&O_ZG^ZF+6&6,QFFJ:7SW2_RW^+:;)3K^ MK_V)QC^_ZS(F 2. I sent mail with -a option echo "uuencode testing"|mail -s "This is Attachment Mail" -a uuencode.data1= prasad_kumar@trimble.com I got attachment uuencode.data1 to the mail but cannot open the file 3. Compared the md5sum uuencode.data1 in both Systems RHEL 5 and RHEL 7=20 md5sum uuencode.data1 Got Same result RHEL5>$md5sum uuencode.data1 caed0be19f6903c899ffc077b1fa8edc uuencode.data1 RHEL7>$ md5sum uuencode.data1 caed0be19f6903c899ffc077b1fa8edc uuencode.data1 Thanks and Regards Prasad Kumar ________________________________________ From: Bob Proulx Sent: Monday, April 4, 2016 10:56 PM To: Prasad Kumar Cc: bug-gnu-utils@gnu.org Subject: Re: Upgrading from RHEL5x to RHEL 7x 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 Attac= hment 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=