Martijn, I think this should satisfy. Though I believe the issue is still in my James config, and not in the mailer. My reasoning here is that if I send the same file/command to a different SMTP server, the attachment comes through preserved.
Kind regards, Trevor superDebug: Attempting to send 6 bytes: superDebug: 00000 44 41 54 41 0D 0A DATA.. >>>putline>>> DATA superDebug: Received 44 bytes: superDebug: 00000 33 35 34 20 4F 6B 20 53 65 6E 64 20 64 61 74 61 354 Ok Send data superDebug: 00010 20 65 6E 64 69 6E 67 20 77 69 74 68 20 3C 43 52 ending with <CR superDebug: 00020 4C 46 3E 2E 3C 43 52 4C 46 3E 0D 0A LF>.<CRLF>.. <<<getline<<< 354 Ok Send data ending with <CRLF>.<CRLF> superDebug: Attempting to send 344 bytes: superDebug: 00000 44 61 74 65 3A 20 57 65 64 2C 20 32 37 20 41 75 Date: Wed, 27 Au superDebug: 00010 67 20 32 30 30 38 20 31 38 3A 30 32 3A 35 36 20 g 2008 18:02:56 superDebug: 00020 2D 30 34 30 30 0D 0A 46 72 6F 6D 3A 20 74 76 61 -0400..From: tva superDebug: 00030 6E 63 65 40 6E 61 72 2E 63 61 70 67 65 6D 69 6E [EMAIL PROTECTED] superDebug: 00040 69 2E 63 6F 6D 0D 0A 54 6F 3A 20 74 76 61 6E 63 i.com..To: tvanc superDebug: 00050 65 40 6E 61 72 2E 63 61 70 67 65 6D 69 6E 69 2E [EMAIL PROTECTED] superDebug: 00060 63 6F 6D 0D 0A 58 2D 4D 61 69 6C 65 72 3A 20 42 com..X-Mailer: B superDebug: 00070 6C 61 74 20 76 32 2E 36 2E 32 20 77 2F 47 53 53 lat v2.6.2 w/GSS superDebug: 00080 20 65 6E 63 72 79 70 74 69 6F 6E 2C 20 61 20 57 encryption, a W superDebug: 00090 69 6E 33 32 20 53 4D 54 50 2F 4E 4E 54 50 20 6D in32 SMTP/NNTP m superDebug: 000A0 61 69 6C 65 72 20 68 74 74 70 3A 2F 2F 77 77 77 ailer http://www superDebug: 000B0 2E 62 6C 61 74 2E 6E 65 74 0D 0A 4D 65 73 73 61 .blat.net..Messa superDebug: 000C0 67 65 2D 49 44 3A 20 3C 30 31 63 39 30 38 39 30 ge-ID: <01c90890 superDebug: 000D0 24 42 6C 61 74 2E 76 32 2E 36 2E 32 24 61 39 37 $Blat.v2.6.2$a97 superDebug: 000E0 63 65 36 63 39 24 31 31 64 63 65 66 65 32 32 39 ce6c9$11dcefe229 superDebug: 000F0 63 36 40 6C 6F 63 61 6C 68 6F 73 74 3E 0D 0A 53 [EMAIL PROTECTED]>..S superDebug: 00100 75 62 6A 65 63 74 3A 20 74 65 73 74 31 0D 0A 0D ubject: test1... superDebug: 00110 0A 54 68 69 73 20 69 73 20 61 20 31 20 6C 69 6E .This is a 1 lin superDebug: 00120 65 20 62 6F 64 79 2E 0D 0A 0D 0A 62 65 67 69 6E e body.....begin superDebug: 00130 20 36 34 34 20 74 65 73 74 2E 74 78 74 0D 0A 28 644 test.txt..( superDebug: 00140 23 30 49 54 39 37 2D 54 23 30 48 0D 0A 60 0D 0A #0IT97-T#0H..`.. superDebug: 00150 65 6E 64 0D 0A 2E 0D 0A end..... superDebug: Received 28 bytes: superDebug: 00000 32 35 30 20 32 2E 36 2E 30 20 4D 65 73 73 61 67 250 2.6.0 Messag superDebug: 00010 65 20 72 65 63 65 69 76 65 64 0D 0A e received.. <<<getline<<< 250 2.6.0 Message received superDebug: Attempting to send 6 bytes: superDebug: 00000 51 55 49 54 0D 0A QUIT.. >>>putline>>> QUIT -----Original Message----- From: Martijn Brinkers [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2008 2:54 PM To: Vance, Trevor K. Cc: James Users List Subject: RE: A problem with uuencoded attachments Well it's kind of strange that there is no separating line between the headers and the body because that would mean that all lines are considered to be headers. Now it could be that the CR-LF is there but the logger doesn't show it but I do think the CR-LF is missing. Now it could be that some mailers are 'smart' and add the CR-LF seperator when they see a line that is not a valid header but James does not afaik. So, I think you should first me 100% certain that the CR-LF between the headers and body is added. Martijn On Wed, 2008-08-27 at 17:43 -0400, Vance, Trevor K. wrote: > Martijn, > > This is interesting that you have success. What more can I share > regards to my config? I don't think the missing empty line is really > the issue. > > Trevor > > -----Original Message----- > From: Martijn Brinkers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 27, 2008 2:29 PM > To: James Users List > Cc: Vance, Trevor K. > Subject: RE: A problem with uuencoded attachments > > Sending a uuencoded message seems to work with my setup. > > What I still don't get is why there is not an empty line (ie only > CR-LF) between subject and body? see your log > > Martijn > > On Wed, 2008-08-27 at 16:53 -0400, Vance, Trevor K. wrote: > > >From: Martijn Brinkers > > >Sent: Wednesday, August 27, 2008 1:44 PM > > >To: James Users List > > >Cc: Vance, Trevor K. > > >Subject: RE: A problem with uuencoded attachments > > > > > >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 > > > > I was only showing a portion of the conversation. Here's the entire > > output. > > > > Regards, > > Trevor > > > > > > Checking option -attach > > Checking option -uuencode > > Blat v2.6.2 w/GSS encryption (build : Feb 25 2007 12:06:19) > > > > Checking option -to > > Checking option -subject > > Checking option -attach > > Checking option -uuencode > > superDebug: init_winsock(), WSAStartup() returned 0 (?) > > superDebug: Hostname <localhost> resolved to ip address 127.0.0.1 > > superDebug: Official hostname is [munged] > > superDebug: Attempting to connect to ip address 127.0.0.1 > > superDebug: Received 102 bytes: > > 220 [munged] SMTP Server (JAMES SMTP Server 2.3.1) ready Wed, 27 Aug > > 2008 15:44:18 -0400 (EDT) > > <<<getline<<< 220 [munged] SMTP Server (JAMES SMTP Server 2.3.1) > > ready > > > Wed, 27 Aug 2008 15:44:18 -0400 (EDT) > > superDebug: Attempting to send 39 bytes: > > EHLO [munged] > > >>>putline>>> EHLO [munged] > > superDebug: Received 124 bytes: > > 250-[munged] Hello [munged] (127.0.0.1 [127.0.0.1]) 250-PIPELINING > > 250 > > > ENHANCEDSTATUSCODES <<<getline<<< 250-[munged] Hello [munged] > > (127.0.0.1 [127.0.0.1]) <<<getline<<< 250-PIPELINING <<<getline<<< > > 250 > > > ENHANCEDSTATUSCODES Sending test.txt to tvance[munged] > > Subject: test1 > > Login name is tvance[munged] > > Attached binary file: test.txt > > superDebug: Attempting to send 38 bytes: > > MAIL FROM:<[EMAIL PROTECTED]> > > >>>putline>>> MAIL FROM:<[EMAIL PROTECTED]> > > superDebug: Received 48 bytes: > > 250 2.1.0 Sender <[EMAIL PROTECTED]> OK <<<getline<<< 250 2.1.0 Sender > > <[EMAIL PROTECTED]> OK > > superDebug: Attempting to send 36 bytes: > > RCPT TO:<[EMAIL PROTECTED]> > > >>>putline>>> RCPT TO:<[EMAIL PROTECTED]> > > superDebug: Received 51 bytes: > > 250 2.1.5 Recipient <[EMAIL PROTECTED]> OK <<<getline<<< 250 2.1.5 > > Recipient <[EMAIL PROTECTED]> OK > > superDebug: Attempting to send 6 bytes: > > DATA > > >>>putline>>> DATA > > superDebug: Received 44 bytes: > > 354 Ok Send data ending with <CRLF>.<CRLF> <<<getline<<< 354 Ok Send > > data ending with <CRLF>.<CRLF> > > superDebug: Attempting to send 323 bytes: > > Date: Wed, 27 Aug 2008 15:44:18 -0400 > > From: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > 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 > > . > > superDebug: Received 28 bytes: > > 250 2.6.0 Message received > > <<<getline<<< 250 2.6.0 Message received > > superDebug: Attempting to send 6 bytes: > > QUIT > > >>>putline>>> QUIT > > superDebug: Received 63 bytes: > > 221 2.0.0 [munged] Service closing transmission channel > > <<<getline<<< > > 221 2.0.0 [munged] Service closing transmission channel > > > > > > > > > > -------------------------------------------------------------------- > > - 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]
