I'm using uuencode to email an attachment using sendmail (this option cannot change) and on the test system, it sets the mode as 0 in the begin line, instead of the same as the file permissions (which is set to 666):
begin 0 Report.txt
On production, the file permissions on the file are 664, and it creates the following:
begin 666 Report.txt
Now, the versions of uuencode are different on the test vs production.
Test - $Revision: 92453-07 linker linker crt0.o A.10.44 951205 $
Prod - $Revision: 92453-07 linker linker crt0.o B.11.16 000601 $
(not sure how else to get the version of uuencode)
Is there some kind of known issue or something that the mode in the begin line of the encoded text does not match exactly the file's permissions? Or maybe we aren't using uuencode correctly, or are missing a setting, etc... The production begin line we can live with, since at least the users can still decode the email attachment, but the 0 does not decode at all. Any help is appreciated. Currently, we are scanning the encoded text for the begin line with the 0 and replacing with 666 so as to get it to work, but would like to do this the right way, instead of a hack :)
Let me know if any additional info is needed.