Could this be related to the TNEF issue in Microsoft Outlook/ Exchange
systems?

A simple test would be to set a sender and a recipient mail client to text
only & send an attachment.

see (http://support.microsoft.com/default.aspx?scid=kb;en-us;241538) or
search on TNEF on Microsoft's website.
Doug


Doug Wheeler
Sr. Technical Analyst
Georgia-Pacific Corporation
Neenah, WI
voice : 920.729.8178 fax : 920.729.8164
email : mailto:[log in to unmask]
Intranet: http://neenah.srv.gapac.com | Internet: www.gp.com


-----Original Message-----
From: Ben Parker [mailto:[log in to unmask]]
Sent: Monday, April 05, 2004 1:31 PM
To: [log in to unmask]
Subject: Re: Attachments don't work


On Mon, 5 Apr 2004 10:39:29 -0600, Chad Robinson <[log in to unmask]>
wrote:

>Is it possible the problem lies with LSMTP rather than Listserv?

No.  LSMTP does no encoding/decoding or modification of MIME headers, etc.
in
any messages.

Exactly what is the problem you are asking about?  Based on your message:

"...but if you try to send an attachment it embeddeds it as garbage
(encoded?)
text."

you seem to think the problem is that the binary attachement is encoded.
This
is not a problem.  All binary attachments are always encoded.  This is
normal.