[TriLUG] Another seal not yet broken... using Greylisting
dave at logicalgeek.com
Mon Jan 29 10:33:45 EST 2007
I've got mine set to 30 seconds and the longest delay I've seen during
testing was about 5 minutes. I can say that I have not seen any problems
with large server farms (google, hotmail, yahoo, mindspring) dealing
with the greylist. Nor have I seen issuse from my work, or the various
state agency servers I get mail from friends from. (I'm using the
greylist-milter with Sendmail if that matters.)
To borrow an old line ... You can have my greylist-milter when you pry
it from my cold dead server.. (apologies for the drama) ;-)
Douglas Ward wrote:
> I implemented greylist.pl in my environment (~25k messages per day) and
> found it to not work well. Many of the large isp's have multiple
> e-mail servers which results in the following scenario:
> Server 1 attempts to deliver from somebody at test.com and is greylisted.
> After defined pause Server 2 attempts to deliver from
> somebody at test.com and
> is greylisted again.
> After another defined pause Server 3 attempts to deliver from
> somebody at test.com and is greylisted again.
> I imagine this is three entries in the database file for future messages.
> The end user's message never delivers and they freak out. I know the
> is to probably whitelist these domains but I didn't have the time to
> keep up
> with it.
> Another issue that I ran across was even though I had set the greylist to
> accept after 30 seconds the sending server would wait much longer to try
> again (sometimes a half day or more).
> Do you see this behavior on your side? I would love to turn the rule
> on but it caused too many interruptions. YMMV though. Thanks!
More information about the TriLUG