[Mimedefang] mimedefang and milter-ahead

[John Nemeth]

On Nov 8, 12:11pm, George Roberts wrote:
}
} 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.

     You can do anything in MIMEDefang that you can figure out how to
program (or pay someone to program for you); it doesn't have any
inherent limitations.

} 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.

     Anyways, your problem has to do with the milter API.  It is
defined that as soon as any milter rejects a message, processing
stops.  There is nothing that can be done about this on the MIMEDefang
side.

     BTW, your MUA is severely broken.  It doesn't know how to wrap
lines properly.  That is extremely annoying.  It also doesn't do
replies properly.  Top posting is extremely bad form, and generally not
appreciated on technical lists.

} -----Original Message-----
} 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.
} 
} Regards,
} 
} David.
} 
}-- End of excerpt from George Roberts