RE: 501 Badly structured mime attachment

[Alex Kramarov]

John Logiudice wrote :   >I've recently set up a server on Linux using qmail 1.03.  Several = >different users here received bounces like this one when sending mail: >>  Hi. This is the qmail-send program at opalgroup.net. >>  I'm afraid I wasn't able to deliver your message to the following = >addresses. >>  This is a permanent error; I've given up. Sorry it didn't work out. >> >>  <[EMAIL PROTECTED]>: >>  209.116.174.162 failed after I sent the message. >>  Remote host said: 501 Badly structured mime attachment.   I have also encountered this, sending some stationaries (html formatted mail) with attachments  from express to sendmail (and only sendmail) servers - this happends not only from qmail - i tried to send from other servers too with the same result. anybody knows if this can be fixed from the sending server side (qmail in this case), so complicated mime-structured mail would be sent successfully to sendmail ?   Alex   Incredimail Admin. -----Original Message----- From: John Logiudice [mailto:[EMAIL PROTECTED]] Sent: Monday, December 18, 2000 11:35 PM To: [EMAIL PROTECTED] Subject: 501 Badly structured mime attachment Hello, I've recently set up a server on Linux using qmail 1.03.  Several = different users here received bounces like this one when sending mail: >  Hi. This is the qmail-send program at opalgroup.net. >  I'm afraid I wasn't able to deliver your message to the following = addresses. >  This is a permanent error; I've given up. Sorry it didn't work out. > >  <[EMAIL PROTECTED]>: >  209.116.174.162 failed after I sent the message. >  Remote host said: 501 Badly structured mime attachment. Most attachments are going through fine, and the same users were able to = send attachments to other recipients.  The attachments that had this = trouble ranged in size from a 128kb .DOC file, to a 4mb .EPS file. =20 Although not a major problem -- yet -- I'd like to know if there is some = configuration issue on my end that will prevent this.  All the users who = had this trouble are using Outlook Express 5. Please let me know if there is any more info I should supply. Thanks, John