Hello,
thanks for reading. When sending out messages with an attachment on a Mac client (6.0.2CF2) thru a Windows 6.0.3 server on W2K, the last two bytes of the file attachment are missing.
To reproduce:
Outbound attachment encoding method:
Base64
Outbound Macintosh attachment conversion:
AppleDouble (Base64 only)
-
create message on Mac, attach RTF file with MIME options AppleDouble (not Binhex)
-
send SMTP message thru 6.0.3
-
file compare sent file on the receiver side with original file (good ol’ DOS : fc originalfile.rtf receivedfile.rtf) or use hex editor
The last two bytes are missing ( }} ). Hence, the file is not readable on the receiving side.
Temporarily, I have reactivated another 5.0.9 Server. When messages are routed from 6.0.3 using NRPC routing to 5.0.9 and then out to the Internet, message integrity is maintained and the file attachment is OK. So this is clearly a R6 issue.
Troubleshooting this has costed me more time I am willing to admit here. I fail to understand how such a fundamental problem could slip thru QA, but maybe there is an undocumented INI setting (NotesFixForToNextLoopMinus1 ?) to fill up the missing bytes 
or I am just plain stupid (always a possibility) and need a good whack on the head.
On another note, mails stored in the Sent view will lose their attachment on some Macs on some OS versions on some days on some occassions depending on the phase of the moon. I have been pulling out all my hair (and replaced nearly all of the network infrastructure) to get down to this one to no avail. The attachments are stored as graphic icons, double clicking on them will result in “Notes item not found”. I find this a severe bug as well rendering the Mac client next to useless. Harsh, but true.
