Milter-greylist

Hello,

A user of ours asked for something I will here call reverse
auto-whitelisting, that is to generate an automatic whitelist entry when
an email is sent from our MTA. There recipient and sender will of course
be reversed and any IP will do for the reply message. That way when the
off-site recipient replies to our on-site user, it will pass through
immediately.

For example:

A mail from me (me@...) to my friend (friend@...) from
our MTA (192.168.0.1) would create a reverse auto-whitelist entry that
looks like this:

* <friend@...> <me@...> 1155024907 AUTO # 2006-08-08
11:15:07

Does this sound useful to anyone else? Anyone already working on
something like it?

Cheers,
Fredrik Nyberg

--- In milter-greylist@yahoogroups.com, Fredrik Nyberg <nba@...> wrote:
>
> Hello,
> 
> A user of ours asked for something I will here call reverse
> auto-whitelisting, that is to generate an automatic whitelist entry when
> an email is sent from our MTA. There recipient and sender will of course
> be reversed and any IP will do for the reply message. That way when the
> off-site recipient replies to our on-site user, it will pass through
> immediately.
> 
> For example:
> 
> A mail from me (me@...) to my friend (friend@...) from
> our MTA (192.168.0.1) would create a reverse auto-whitelist entry that
> looks like this:
> 
> * <friend@...> <me@...> 1155024907 AUTO # 2006-08-08
> 11:15:07
> 
> Does this sound useful to anyone else? Anyone already working on
> something like it?
> 
> Cheers,
> Fredrik Nyberg
>
  Sounds very good to me, if the programmers could allow for manual
entries of addresses I think even I could come up with a script to
parse the maillog to do this. This way I could limit which users have
their recipients whitelisted.

I would also like a way to tell which version of milter-greylist is
installed and/or running.

On Mon, Jul 03, 2006 at 04:08:37PM +0300, Fredrik Nyberg wrote:
> Does this sound useful to anyone else? Anyone already working on
> something like it?

I thought about this one, but there is a problem: you cannot take for
granted that the remote site MX is also the source SMTP server.

-- 
Emmanuel Dreyfus
manu@...

Emmanuel Dreyfus wrote:
> On Mon, Jul 03, 2006 at 04:08:37PM +0300, Fredrik Nyberg wrote:
>> Does this sound useful to anyone else? Anyone already working on
>> something like it?
> 
> I thought about this one, but there is a problem: you cannot take for
> granted that the remote site MX is also the source SMTP server.

No, you would have to accept for _any_ remote IP (*, recipient, sender).

Cheers,
Fredrik Nyberg

On Tue, Jul 04, 2006 at 03:09:23PM +0300, Fredrik Nyberg wrote:
> > I thought about this one, but there is a problem: you cannot take for
> > granted that the remote site MX is also the source SMTP server.
> No, you would have to accept for _any_ remote IP (*, recipient, sender).
 
Don't you fear that would make spammers life really easier?



-- 
Emmanuel Dreyfus
manu@...

Emmanuel Dreyfus wrote:
> On Tue, Jul 04, 2006 at 03:09:23PM +0300, Fredrik Nyberg wrote:
>>> I thought about this one, but there is a problem: you cannot take for
>>> granted that the remote site MX is also the source SMTP server.
>> No, you would have to accept for _any_ remote IP (*, recipient, sender).
>  
> Don't you fear that would make spammers life really easier?

Evan Harris proof-of-concept implementation relaydelay
(http://projects.puremagic.com/greylisting/), from which I switched to
milter-greylist from, has this feature. It did not seem to let a lot of
spam through, but surely some will slip in. My users are more concerned
about getting mail late or not at all due to braindead MTA's out there
than about if they get an occasional spam.

Cheers,
Fredrik Nyberg