Greetings,
I have several Unix hosts sending mail with uuencoded attachments
through James v2.3.1 as a SMTP relay. Mail with no attachments work
great, Windows hosts sending mail w/attachments work great, other Unix
hosts sending base64 attachments works great. If I take James out of
the mail routing, it works well. Adding James back into the routing and
it fails.
The failing messages have the message body as
begin 644 test.png
MB5!.1PT*&@[EMAIL PROTECTED])4"`(```!UT1*\`````7-21T(`KLX<
MZ0````1G04U!``"[EMAIL PROTECTED]>B8``("[EMAIL PROTECTED]@``'4P
[EMAIL PROTECTED]/```DC9)1$%4>%[MO7GXI45YY]WO?^\U\SJO\\[,
.
.
.
end
Which leads us to the failing messages do not have the message headers
that a successful message has:
Content-Type: image/png; name="test.png"
Content-Disposition: attachment; filename="test.png"
Content-Transfer-Encoding: uuencode
Therefore, I'm fairly confident something in my configuration is wrong.
I've been beating my head against this thing far too long.
Thanks for your consideration.
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
