Milter-greylist

Well,
That would be a fairly cool thing!
What I would be a bit concerned a bit is that in our case the
milter-greylist is running in de-militarized zone on the MTA. On our LAN
we have Microsoft AD domain which could be potentially used to store
greylisting data, but MTA could be potentially compromised and thus
expose the whole Active Directory to the attacker...
Ondrej

Emmanuel Dreyfus wrote:
>
> On Mon, Mar 03, 2008 at 09:47:38AM +0100, Ondrej Valousek wrote:
> > Automated solution - that the target we are all aiming for.
> > Unfortunately you will never find one, it is impossible - unless you
> > willing to pay for some outsourced commercial solution.
>
> Well, there are still cool stuff that can be done with free tools: At
> mine, milter-greylist looks up per-recipient settings in an LDAP
> directory. Settings include whether greylisting is enabled, for what
> delays, what DNSRBL to use, blacklist and whitelist.
>
> Users have access to a web application which enable them to access
> and modify their personnel filtering settings. The application also
> shows them all milter-greylist activity collected through the stat
> feature: they can see what delivery attempt was accepted, temporary
> rejected, or permanently rejected, and for what reason.
>
> No filtering is enabled by default. Users that complain about spam are
> directed to this tool, and they do use it to perform filtering. As the
> only filtering done is what they have configured, there is no room
> for lost mail complaints, and there is no administrative overhead.
>
> -- 
> Emmanuel Dreyfus
> manu@... <mailto:manu%40netbsd.org>
>
>