Could you sent a complete example message? The example DATA portion (below) you show seems not to separate the headers and body. Is that intentional?
Martijn Brinkers On Wed, 2008-08-27 at 16:24 -0400, Vance, Trevor K. wrote: > Just to satisfy the issue... I installed JAMES on a separate system, > modified the config.xml file for the gateway to be the same as our > production server and tested. > > The results were the same. So, an "out of the box" install of JAMES, > does not handle an attachment that is uuencoded. It handles base64 > without any issue. > > Either I need to setup a custom mailet or use mime4j(?) or some other > config.xml change. I'm entirely open to suggestions. > > This is an example of the DATA portion of the SMTP conversation. > blat.exe body.txt -to tvance[munged] -subject test1 -attach test.txt > -uuencode > >>>putline>>> DATA > 354 Ok Send data ending with <CRLF>.<CRLF> > <<<getline<<< 354 Ok Send data ending with <CRLF>.<CRLF> > Date: Wed, 27 Aug 2008 15:44:18 -0400 > From: tvance[munged] > To: tvance[munged] > X-Mailer: Blat v2.6.2 w/GSS encryption, a Win32 SMTP/NNTP mailer > http://www.blat.net > Message-ID: > <[EMAIL PROTECTED]> > Subject: test1 > test > begin 644 test.txt > &=&5S=`T* > ` > end > . > 250 2.6.0 Message received > <<<getline<<< 250 2.6.0 Message received > > When the same email is sent through a different SMTP server (i.e. not > JAMES), the attachment is preserved. > > Kind regards, > Trevor > > > -----Original Message----- > From: Norman Maurer [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 26, 2008 12:37 PM > To: James Users List > Subject: Re: A problem with uuencoded attachments > > Hi, > > do you use any custom mailet ? > > Cheers, > Norman > > Am Dienstag, den 26.08.2008, 01:23 -0400 schrieb Vance, Trevor K.: > > 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] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
