Hi All,
While trying to help a customer that was having trouble receiving specific
attachments through our mailserver, but which seemed to be received ok
through another ISP's mailserver, I came across an interesting thing....
It turned out that the troublesome attachments were in UUENCODE format, and
something about the way the customers own mailserver/client machines were
set up were causing them problems...
The strange thing was, that the same message sent through another well
known ISP was being received, seemingly with no problems getting the
attachment.
A bit of investigation found that while our server was passing the
UUENCODE'ed attachment through as-is, the other ISP is decoding the
UUENCODE'ed attachment, and re-attaching it in the more common BASE64 Mime
attachment type.
Now I havn't looked through RFC's exhuastively, but I was under the
impression that although mailservers are allowed to add their own Headers,
etc, they must NOT alter the message body of a message. (Or at least,
"Should not")
Is this decoding of attachments and re-encoding/attaching them in a
different format breaking the RFC's ?
Just wondering... :)
Regards,
Simon Byrnand
iGRIN Internet
