Yahoo Groups archive

Milter-greylist

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

Message

RE: [milter-greylist] Time-based greylisting?

2005-05-28 by Howard Picken

This all seems to going messy.  John, having read what's come through on
this thread, it seems that there two
options available to you.
 
1. Stop sendmail from running at night (as below).  Because sendmail is not
running some of the spam originators will time out after
trying so many times to send the mail.  Of course the flaw with this is that
you can't send email either and it also means that legitimate mail can also
time out and not be received.
 
2. As suggested earlier in the thread create another sendmail.cf file
without the milter-greylisting options in it say sendmail.nogrey.cf.  Using
cron you can start sendmail at 7am with the sendmail.nogrey.cf then stop
sendmail at 7pm and restart it with the normal sendmail.cf (or visa versa).
This is the option I'd use because you then greylisting when you want it and
when you don't. Either way sendmail is still running.
 
Either way will do the job but "I" would definitely use the second.
 
Howard


manu@... wrote:
> John Goggan <jgoggan@...> wrote:
> 
> 
>>>Yes, that will work. You can even stop sendmail at night, that will
>>>produce the same result. 
>>
>>I'm confused what you mean by that.  How would stopping sendmail at night
>>produce the same result?
> 
> Run sendmail without milter-greylist during the day, no mail will be
> delayed. Shut down sendmail at night, and you'll refuse all the mail
> coming from spam engines that don't retry sending. 

Yes, but that is not at all "the same result" as running sendmail with the 
milter-greylist all night.

In fact, I'm not sure if you are making a joke with me and being sarcastic
or 
I'm just missing something.  Isn't your suggestion basically not using the 
greylist EVER?  You are suggesting sendmail during the day without the 
greylist and nothing at night.  So -- when would I be using the greylist at
all?

  - John...

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.