Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] username match, broken MTAs, timeout

2005-03-18 by manu@netbsd.org

Jack Olszewski <jacek@...> wrote:

> greylisting seems to apply not only to the addresses:
> 
> anna@...
> asia@...
> 
> but also to addresses where the username contains anna or asia, eg:
> 
> hanna@xxx.yyy.zz
> kasia@...

Will be fixed in next release. In the meantime, you can use
/^anna@.../ as a workaround
 
> The default greylist.conf included in the tarball contains a list of
> broken MTAs, some Yahoo groups servers included but not all. My
> attempt at joining this list resulted in greylisting of 66.94.237.28
> from which a reply to my joining message came and was tempfailed. No
> attempt to repeat its delivery was ever made.
> 
> Then, I noticed other Yahoo groups servers from 66.94.237.* network
> sending messages to addresses in our domain, tampfailed as well.
> 
> That has prompted me to append the following line to greylist.conf:
> 
> addr 66.94.237.0/24
> 
> Are there any other broken MTAs this group knows of?
> Is there any place where a current list of broken MTAs is maintained?

I take the list from
http://cvs.puremagic.com/viewcvs/greylisting/schema/whitelist_ip.txt
 
> Question 3. timeout
> -------------------
>  
> The following item in greylist.conf is not quite clear to me:
> 
> # How long will the greylist database retain tuples
> #timeout=5d
> 
> Does it concern any tuple, or greylisted, or whitelisted? If:

It's the lifetie of a greylist tuple.
 
> autowhite=5d
> timeout=3d
> 
> does a whitedlisted tuple remain in the data base for 5 days?

Yes

-- 
Emmanuel Dreyfus
Publicité subliminale: achetez ce livre!
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@...

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.