1.22 wasn't quarantining the messages, trying to get the client to send it again.... off the server
I don't understand this... You get a notify but the mail it is not quarantined? Have you search the logs (qmail-queue.log) for that message?
Is perlscanner running before Clamscan?
my $BAD_MIME_CHECKS='2'; is set
just updated to 1.22st big question is, can I white list that domain, without having to set Mime checks to '0"
Well, if you read the docs you will find ...
c) BMC_WHITELIST="on"
Set this enviroment variable in tcp.smtp to disable BAD_MIME_CHECKS for some servers. It's a little bit hard to mantain...
But you can set it only "FOR IPs" not for domains.
Fighting with lag on SA again... 8-30 seconds, and using up all the SMTP session on this box right now... At least this mail server waiting til I finished with one of my Other Mail Servers before going to hell
I'm not sure but maybe there is a problem in the tcpserver that doesn't limit the incoming smtp connections... I'm tracking this.
Good luck
Salvatore
Salvatore Toribio wrote:
At 10:43 -0400 4-08-2004, Robert Mudryk wrote:
Direct Mail Pcs Disallowed MIME boundary found in attachment - potential virus
Disallowed MIME boundary found in attachment - potential virus clamscan: 0.73. spamassassin: 2.63
You might send more information... (mail client...)
You can disable this check setting to '0' the following variable
#Try to fix bad MIME messages before passing to MIME unpacker my $BAD_MIME_CHECKS='2';
But I don't think it is a good idea to do it...
ST
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
