[Mimedefang] Intermittent case of SA not groking correct configuration?

This intermittent problem is manifested by spam that comes through without the Subject: header being rewritten and tagged with **SPAM**. The other symptom is the X-Spam-Status: header which doesn't seem right, especially given the X-Spam-Score: header content :) I've included an example

[Mimedefang] Re: milter-greylist

To my inexperienced eye it seems extremely elegant/sensible to separate this functionality out of MimeDefang - gives MimeDefang less to do, simplifies filters, etc. Does anyone know better? The very first greylisting implementation that I used was milter-greylist, but I found that some virus

[Mimedefang] Log reason for tempfail?

Hello. Does anyone know a way to log the reason for a message being tempfailed? I have some messages getting tempfailed, but I can't see the reason why. Thank you Dan ___ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list

[Mimedefang] Max recipient

Hi, I want set mimedefang for max recipients with ingoing mail, when the number of recipients is more than 5, then mimedefang? reply with a message, for example: our server not admit more than 5 recipient, Is it posible? Best Regards Pablo ___

RE: [Mimedefang] Max recipient

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew.van.Eerde wrote: No need for Mimedefang-ery. You can do this in Sendmail directly by defining the SMTP_MAILER_MAXRCPTS option in your .mc file. http://www.sendmail.org/m4/ostype.html#SMTP_MAILER_MAXRCPTS Er, actually for non-ancient

[Mimedefang] greylisting and pop-before-smtp don't play together

Hi all, I'm looking for suggestion to get pop-before-smtp (actually imaps-before-smtp) and greylisting to play nicely together. The pop-before-smtp implementation I'm using is from http://popbsmtp.sourceforge.net/. It creates a popauth.db {Berkeley DB (Hash, version 7, native byte-order)} file

Re: [Mimedefang] greylisting and pop-before-smtp don't play together

On 31 Aug 2004 at 16:31, James Miller wrote: The problem is the greylisting function doesn't know about and/or doesn't exempt the newly authenticated imap clients and when they try to send a message they get the '4.3.0 message to try again in 1min'. As other messages have pointed out,

Re: [Mimedefang] Inoffizial MIME-tools-5.411a-RP-Patched-05 available (includes a new data corruption fix)

On Tue, 31 Aug 2004, Martin Blapp wrote: - MS Outlook quoted printable encoded files were corrupted (carriage returns missing) if they were decoded by MIME-Tools. This version contains a workaround so action_rebuild() should be safe again (for PDF files). (patch partly from MailScanner) This

[Mimedefang] Virus sneaking through

All, We noticed a new virus sneaking through our filter today. Attachment is called foto.zip or fotos.zip. Clamav detects it as Trojan.Dropper.Small-11 (scanned mimedefang ./Work dir). I turned on ScanMail in clamav but it still gets through. Anyone seen this before? Is this a case for