Don Walters wrote:
<snip>
Content-Type: multipart/mixed; boundary="-"
This is a MIME encoded message from FutureLynx. Decode it with "munpack" or any other MIME reading software. Mpack/munpack is available via anonymous FTP in ftp.andrew.cmu.edu:pub/mpack/ ---
Enclosed is a message that you requested to be forwarded. The time and date appear as the messages time and date.
-- Content-Type: application/octet-stream; name="V1227751.wav" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="V1227751.wav" Content-MD5: g/hwyjB4WknpNji6sscrQw==
UklGRnDkBgBXQVZFZm10IBAAAAABAAEAESsAABErAAABAAgAZGF0YUzkBgCAgICAgICAgICA gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA
< snip about 8300 lines of gibberish similar to the above>
</snip>
Here is a segment of an older email of mine that went through without a problem:
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0032_01C3F3D4.BC2280E0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <[EMAIL PROTECTED]>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on localhost.myserver.com
X-Spam-Level: **
X-Spam-Status: No, hits=2.2 required=6.0 autolearn=no version=2.60
This is a multi-part message in MIME format.
------=_NextPart_000_0032_01C3F3D4.BC2280E0
Content-Type: text/plain;
charset="iso-8859-1"Content-Transfer-Encoding: 7bit
~50 lines of letter
------=_NextPart_000_0032_01C3F3D4.BC2280E0
Content-Type: image/jpeg;
name="pic.JPG"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="pic.JPG"/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAsICAoIBwsKCQoNDAsNERwSEQ8PESIZGhQcKSQrKigk JyctMkA3LTA9MCcnOEw5PUNFSElIKzZPVU5GVEBHSEX/2wBDAQwNDREPESESEiFFLicuRUVFRUVF ................. ................. .................
Based on the differences between the 2, I would suspect a problem with the way his software is generating the MIME boundary tag. Ask him if he can define in the program script or code
to use a different boundary definition such as:
Content-Type: multipart/mixed; boundary="------=NextPart"
This would hopefully stop the text boundaries of -- and --- from being intrepreted as MIME boundaries
Hope that helps. Bob J
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
