Milter-greylist

Using 

------------------
# milter-greylist -r
milter-greylist-1.7.5
sdstern@...:/root/download/milter-greylist-1.7.5 Sat Jan 29
18:37:05 CST 2005

run as

 /usr/local/bin/milter-greylist -P /var/run/milter-greylist.pid -u root -p
/var/milter-greylist/milter-greylist.sock

/etc/mail/greylist.conf specifies a retry interval of 30s, but it appears
senders are being given semi-random intervals:
-----------------------------------
# How long a client has to wait before we accept 
# the messages it retries to send. Here, 1 hour.
# May be overridden by the command line argument "-w xxx".
greylist 30s 

-----------------------------------
Jan 31 04:17:46 ciscy sendmail[11051]: j0VAHM41011051: Milter:
to=<steve@...>, reject=451 4.7.1 Greylisting in action, please come
back in 00:30:00
Jan 31 05:33:33 ciscy sendmail[11298]: j0VBXWcS011298: Milter:
to=<marilyn@sterndata.com>, reject=451 4.7.1 Greylisting in action, please
come back in 00:30:00
Jan 31 05:33:35 ciscy sendmail[11302]: j0VBXY7P011302: Milter:
to=<marilyn@...>, reject=451 4.7.1 Greylisting in action, please
come back in 00:29:58
Jan 31 05:50:58 ciscy sendmail[11367]: j0VBouYP011367: Milter:
to=<marilyn@...>, reject=451 4.7.1 Greylisting in action, please
come back in 00:12:35
Jan 31 06:25:55 ciscy sendmail[11535]: j0VCPs4q011535: Milter:
to=<eng@...>, reject=451 4.7.1 Greylisting in action, please come
back in 00:30:00
Jan 31 06:40:28 ciscy sendmail[11592]: j0VCeQVc011592: Milter:
to=<eng@...>, reject=451 4.7.1 Greylisting in action, please come
back in 00:30:00
Jan 31 06:47:46 ciscy sendmail[11610]: j0VCljFX011610: Milter:
to=<ms-partner@...m>, reject=451 4.7.1 Greylisting in action, please
come back in 00:30:00
Jan 31 06:48:46 ciscy sendmail[11620]: j0VCmkA5011620: Milter:
to=<ms-partner@...>, reject=451 4.7.1 Greylisting in action, please
come back in 00:29:00
Jan 31 06:49:48 ciscy sendmail[11624]: j0VCnlTI011624: Milter:
to=<ms-partner@...>, reject=451 4.7.1 Greylisting in action, please
come back in 00:27:58
Jan 31 07:09:07 ciscy sendmail[11817]: j0VD91La011817: Milter:
to=<eng@...>, reject=451 4.7.1 Greylisting in action, please come
back in 00:01:21
Jan 31 07:09:49 ciscy sendmail[11838]: j0VD9mgv011838: Milter:
to=<ms-partner@...>, reject=451 4.7.1 Greylisting in action, please
come back in 00:07:57
Jan 31 07:24:24 ciscy sendmail[12046]: j0VDON84012046: Milter:
to=<sysop@...>, reject=451 4.7.1 Greylisting in action, please come
back in 00:30:00

-- 
  Steve

Steven Stern <subscribed-lists@...> wrote:

> /etc/mail/greylist.conf specifies a retry interval of 30s, but it appears
> senders are being given semi-random intervals:

How is it a problem?

-- 
Emmanuel Dreyfus
Un bouquin en français sur BSD:
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@...

It's a problem because it's not doing what it's supposed to be doing. With
version 1.6, it said "come back in 00:00:30", as specified in the conf file.
With 1.75, it uses random times. I don't know if the sending server cares...
but it appears that something is not functioning properly in 1.75

Quoting manu@...:

>
> Steven Stern <subscribed-lists@...> wrote:
>
>> /etc/mail/greylist.conf specifies a retry interval of 30s, but it appears
>> senders are being given semi-random intervals:
>
> How is it a problem?
>
> --
> Emmanuel Dreyfus
> Un bouquin en français sur BSD:
> http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
> manu@netbsd.org
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>

<subscribed-lists@...> wrote:

> It's a problem because it's not doing what it's supposed to be doing. With
> version 1.6, it said "come back in 00:00:30", as specified in the conf file.
> With 1.75, it uses random times. I don't know if the sending server cares...
> but it appears that something is not functioning properly in 1.75

Ah, ok. I see what you mean.

Jan 31 05:33:33 ciscy sendmail[11298]: j0VBXWcS011298: Milter:
to=<marilyn@...>, reject=451 4.7.1 Greylisting in action,
please come back in 00:30:00
Jan 31 05:33:35 ciscy sendmail[11302]: j0VBXY7P011302: Milter:
to=<marilyn@...>, reject=451 4.7.1 Greylisting in action,
please come back in 00:29:58

The time here is not random: the sender retired after 2 seconds, so
instead of 30 mn, there is 30 mn - 2 s to wait.

-- 
Emmanuel Dreyfus
Un bouquin en français sur BSD:
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@...

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.
-- 
  Steve

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

Steven Stern wrote:
> On Thu, 03 Feb 2005 08:19:59 -0600, Steven Stern
> <subscribed-lists@...> 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            
> 

Do the entries that are not 00:30:00 match up with a previous entry? 
I've seen a few overzeleous mail servers that are retrying every minute, 
and each time they get a 'please come back in [time remaining]' 
incremented for the time they have left.

At 08:22 AM 2.3.2005 -0800, Mike Robinson wrote:
>
>> 
>
>Do the entries that are not 00:30:00 match up with a previous entry? 
>I've seen a few overzeleous mail servers that are retrying every minute, 
>and each time they get a 'please come back in [time remaining]' 
>incremented for the time they have left.
>

That's what I thought about this one. Look & compare the header & message
ID, etc.


Happy trails,
Jack L. Stone

System Admin
Sage-american

On Thu, 03 Feb 2005 08:22:24 -0800, Mike Robinson <mrobinson@...> wrote:

>Do the entries that are not 00:30:00 match up with a previous entry? 
>I've seen a few overzeleous mail servers that are retrying every minute, 
>and each time they get a 'please come back in [time remaining]' 
>incremented for the time they have left.

Not all of them.... but I've set the interval to 30 seconds.
-- 
  Steve

On Thu, 03 Feb 2005 11:43:12 -0600, "Jack L. Stone" <jacks@...m>
wrote:

>
>At 08:22 AM 2.3.2005 -0800, Mike Robinson wrote:
>>
>>> 
>>
>>Do the entries that are not 00:30:00 match up with a previous entry? 
>>I've seen a few overzeleous mail servers that are retrying every minute, 
>>and each time they get a 'please come back in [time remaining]' 
>>incremented for the time they have left.
>>
>
>That's what I thought about this one. Look & compare the header & message
>ID, etc.

Indeed, they were working off an old delay.

On the 30 minutes vs 30 seconds issue, 
   -w 30s
on the command line generates the correct interval, but

   greylist 30s

in greylist.conf seems to be the same as 30m.
-- 
  Steve

Steven Stern <subscribed-lists@...> wrote:

> Indeed, they were working off an old delay.
> 
> On the 30 minutes vs 30 seconds issue, 
>    -w 30s
> on the command line generates the correct interval, but
> 
>    greylist 30s
> 
> in greylist.conf seems to be the same as 30m.

That should be easy to track down and fix. Will you contribute a fix for
it?

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

On Fri, 4 Feb 2005 00:12:16 +0100, manu@... wrote:

>
>Steven Stern <subscribed-lists@...> wrote:
>
>> Indeed, they were working off an old delay.
>> 
>> On the 30 minutes vs 30 seconds issue, 
>>    -w 30s
>> on the command line generates the correct interval, but
>> 
>>    greylist 30s
>> 
>> in greylist.conf seems to be the same as 30m.
>
>That should be easy to track down and fix. Will you contribute a fix for
>it?


It looks like all time values get parsed in humanized_atoi(), but I think that
code is right because it works with the -w command. I'm looking around, and I
think it's in conf_yacc.c, so now I'm trying to understand the yacc lexicon.
Elegant code, but hard to trace.
-- 
  Steve