Yahoo Groups archive

Milter-greylist

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

Message

Re: [milter-greylist] random "come back" interval

2005-02-03 by Steven Stern

On Thu, 03 Feb 2005 08:19:59 -0600, Steven Stern
<subscribed-lists@sterndata.com> wrote:

>
>
>I found my problem. There was an error in one of my whitelist lines. When I
>converted to 1.75, I edited the conf and had a syntax error.  When an error is
>found, it looks like milter-greylist falls back on defaults.  IAC, I fixed the
>error, ran milter-greylist -c with a good result, and it's now working as
>expected and desired.

Turns out that wasn't it.  The first couple of incomings got the "wait
00:30:00 ". Then it went random again:

My greylist.cnf file says:

greylist 30s

but.... this is in the log

please come back in 00:30:00 
ome back in 00:30:00         
please come back in 00:30:00 
please come back in 00:29:58 
please come back in 00:30:00 
please come back in 00:29:56 
 back in 00:30:00            
please come back in 00:30:00 
please come back in 00:30:00 
 back in 00:30:00            
please come back in 00:27:58 
please come back in 00:27:38 
please come back in 00:30:00 
please come back in 00:01:00 
please come back in 00:25:12 
 back in 00:24:58            
 back in 00:23:36            
please come back in 00:22:23 
please come back in 00:22:21 
please come back in 00:01:00 
please come back in 00:01:00 
please come back in 00:22:49 
please come back in 00:20:04 
please come back in 00:21:33 
please come back in 00:17:56 
 back in 00:18:31            
please come back in 00:16:36 
please come back in 00:14:08 
please come back in 00:14:03 
please come back in 00:14:02 
please come back in 00:14:02 
please come back in 00:14:01 
please come back in 00:14:00 
please come back in 00:15:18 
please come back in 00:12:40 
please come back in 00:15:02 
please come back in 00:12:26 
 back in 00:13:29            

-- 
  Steve

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.