[Mimedefang] mimedefang and milter-ahead
groberts at purity.net
Fri Jun 18 20:35:29 EDT 2010
Because it just isn't full-featured enough for what we need. milter-ahead caches both good and bad senders to reduce the amount of lookups on the recipient servers. It also uses the built-in sendmail mailertable for its lookups, so we don't have to do any additional configuration for it above and beyond what we already do for the domains we support.
We handle mail for over 50,000 domains going to 800+ different mail servers. :)
If I have to, I'll just modify the source for milter-ahead to do the statistics reporting. I'm trying to avoid that if I can, since our other stats reporting is done within mimedefang and I'd prefer to keep it all in one place if I can.
From: mimedefang-bounces at lists.roaringpenguin.com [mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of David F. Skoll
Sent: Friday, June 18, 2010 7:10 PM
To: mimedefang at lists.roaringpenguin.com
Subject: Re: [Mimedefang] mimedefang and milter-ahead
George Roberts wrote:
> I'm using milter-ahead to call ahead to the recipient mail server to
> see if the receipient(s) of the message exist.
> It appears that if milter-ahead rejects the message due to the user
> not existing on the recipient server that milter processing just ends
> ... what I really want to be able to do, if possible, is have
> mimedefang do some processing if milter-ahead rejects the message.
Rather than using milter-ahead, why not do your call-aheads from MIMEDefang itself, using the md_check_against_smtp_server function? That way, you have full control from your Perl filter.
NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
More information about the MIMEDefang