When do you need to manually decode an attachment? If you get a message that has a
large batch of random digits, characters, and apostrophes in 80-characters-per-line format,
that??™s probably an undecoded attachment. If you see a line at the top of the randomness
with a filename, you definitely have an undecoded attachment. See the section ???Using
UUDeview to Decode a File Attachment??? to know what to do with it.
NOTE
Microsoft Exchange Servers use a proprietary format to attach files to Outlook
messages. This format, the Transport Neutral Encapsulation Format (TNEF), is read
beautifully in Outlook itself, but other clients (regardless of OS) sometimes have a
problem with attachments being labeled with a generic winmail.dat filename.
Progress has been made in viewing these files in Linux mail clients. KDE (and KMail)
has a built-in TNEF viewer. Other clients can use the shell utility TNEF to view these
files. This utility is available through YaST.
BinHex
Apple Macintosh users have long used the BinHex format to wrap files. This hasn??™t
changed with the advent of the FreeBSD-based OS X.
Pages:
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604