Meanwhile you can try this :

 

Cut’n’Paste from http://www.kabewm.com/pages/projects/qmailtoaster/faq.php#question_21

 


Q. I can't send or recieve zip files

In a text editor open /var/qmail/control/badmimetypes and put a # in front if the MyDoom rule. The result should look like this:

# MyDoom (*.zip)
# UEsDBAoAA

Then execute /var/qmail/bin/qmail-badmimetypes to regenerate the cdb file. This filter doesn't always work correctly and may incorrectly block zip files. I believe this will be the new default on the next version of the qmailtoaster.

 

 


Fra: Ole Johansen [mailto:[EMAIL PROTECTED]
Sendt: 20. mars 2006 21:25
Til: [email protected]
Emne: SV: [qmailtoaster] PERM_FAILURE: SMTP Error

 

Hello,

 

Do you have any logs of these events and OS/QT version type.?

 

Have you done something special who can explain this?

 

At first glance, Clamav usual never make troubles regarding this issue but..,

Anyway - qmail-smtpd will send a SMTP 554 Error Reply under the following conditions:

  • a badmimetype was encountered, see /var/qmail/control/badmimertype
  • a badloadertype was encountered,  see /var/qmail/control/badloadertype
  • a Virus was found via an external AV Scanner,  check your virus scanner log
  • the email exceeds the hop count.

 

B/R Ole J

 

I assume that you run the same as I do – Centos 4.2 with latest QT – basic configurations but with updated Clamav, Spam control files, RBLS

 


Fra: Joshua Hopkins [mailto:[EMAIL PROTECTED]
Sendt: 20. mars 2006 20:45
Til: [email protected]
Emne: [qmailtoaster] PERM_FAILURE: SMTP Error

 

I started getting this error message from my qmail server.  Everything has been working fine for the last 8 months.  A vendor was trying to send us some documentation in .doc (MS Word) format.  There were 5 attachments total adding up to 543kb in size.  They got back the following error:

 

Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 12): 554 invalid message content  (#5.3.2)

 

If they send the same message but without the attachments it comes through just fine.  We are now getting the same errors from other vendors and customers in regards to other attachments i.e. gzip, tar, zip, rar, pdf, gif, jpg, png, xls, and many others.  It does not seem to happen to all messages with attachments though. 

 

I am assuming that I need to adjust what is filtering the message content.  First I thought that would be ClamAV or Spamassassin, but that would give a different error message.  Where do I need to look to adjust what is filtering the message content?  Has anyone else seen this kind of problem before or can point me in the right direction?

 

Thanks,

 

 

 

Joshua Hopkins

 

Reply via email to