Milter-greylist

> with an rfc2822.From header field address that is subscribed to the...
But that is a data stage, isn't it?
You can not do anything at the data stage but plain accept or hard fail.

Ondrej


Dave Crocker wrote:
>
> --- In milter-greylist@yahoogroups.com
> <mailto:milter-greylist%40yahoogroups.com>, Emmanuel Dreyfus
> <manu@...> wrote:
> > So, what's the most-wanted-but-easy-to-implement features?
> ...
> > More ideas? Opinions? Thoughts?
>
> Hi. I'm new to this list (subscription still pending) and new to
> milter-greylist. I did look around postings over the last 2 months,
> and apologize if I'm raising something that has already been resolved,
> but I didn't see anything exactly like this (but did see some close.)
>
> The greylisting delay can hurt legitimate users, if they are part of
> collaborative group. Milter-greylist has various features to permit
> configured whitelisting, but it doesn't seem to have the one I'm think
> would help my system:
>
> Most of the people sending mail to that system are participating in
> some (mailman-based) mailing lists. They send from different
> machines; even the same person does. Worse, the membership of the
> mailing lists varies over time.
>
> This means that members of pre-approved communities -- by virtue of
> their mailing list subscription -- are regularly having the postings
> delayed. In an active group discussion, having random postings show
> up 30 minutes late can make a difference.
>
> I am thinking that it would be good to have milter-greylist able to
> query the membership of a mailing list and automatically accept mail
> with an rfc2822.From header field address that is subscribed to the
> destination mailing list. This needs to be a dynamic query, in order
> to guarantee that the subscription membership that is used is accurate.
>
> Comments?
>
> /Dave
>
>