Yahoo Groups archive

Milter-greylist

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

Thread

negative numbers in log

negative numbers in log

2013-07-11 by Rudolf Gabler

Hello,

I'm a newby to this group and using 4.4.3 I'm getting negative numbers like 

Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.83 from <newsletter@sender> to <tony@...> valid for 23:13:37
Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.140 from <owner-clash@sender> to <stollo@...> valid for 05:43:23
Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.140 from <owner-clash@sender> to <einer@usm.lmu.de> valid for 05:43:21
Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.179 from <info@sender> to <babion@...> valid for 187:32:17
Jul 11 10:33:50 mailer milter-greylist: created:  2702:f8b0:400c:c01::22f from <charitarthvyas@sender> to <uleguay@...> delayed for -119:-57:-13
Jul 11 10:33:50 mailer milter-greylist: created:  1.2.3.122 from <bounce@sender> to <hren@...> delayed for -119:-54:-57
Jul 11 10:33:50 mailer milter-greylist: created:  2702:f8b0:400e:c01::232 from <fner@sender> to <bastian@...> delayed for -119:-51:-12
Jul 11 10:33:50 mailer milter-greylist: created:  1.2.3.82 from <danielle@sender> to <heskelt@example.com> delayed for -119:-47:-31

when kilter-greylist restarts. The AUTO (whitelisted) entries seems to be o.k. but the greylisted are with random negative numbers. In my greylist.conf I'm using 8m for delay, which is definitely not seen with these numbers.

Anyone here with a tip what happens?

Kindly, Rudi Gabler

Re: [milter-greylist] negative numbers in log

2013-07-11 by Johann Klasek

On Thu, Jul 11, 2013 at 06:48:19PM +0200, Rudolf Gabler wrote:
> 
> I'm a newby to this group and using 4.4.3 I'm getting negative numbers like 
> 
> Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.83 from <newsletter@sender> to <tony@...> valid for 23:13:37
> Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.140 from <owner-clash@sender> to <stollo@...> valid for 05:43:23
> Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.140 from <owner-clash@sender> to <einer@...> valid for 05:43:21
> Jul 11 10:33:50 mailer milter-greylist: created: AUTO 1.2.3.179 from <info@sender> to <babion@...> valid for 187:32:17
> Jul 11 10:33:50 mailer milter-greylist: created:  2702:f8b0:400c:c01::22f from <charitarthvyas@sender> to <uleguay@...> delayed for -119:-57:-13
> Jul 11 10:33:50 mailer milter-greylist: created:  1.2.3.122 from <bounce@sender> to <hren@...> delayed for -119:-54:-57
> Jul 11 10:33:50 mailer milter-greylist: created:  2702:f8b0:400e:c01::232 from <fner@sender> to <bastian@...> delayed for -119:-51:-12
> Jul 11 10:33:50 mailer milter-greylist: created:  1.2.3.82 from <danielle@sender> to <heskelt@...> delayed for -119:-47:-31
> 
> when kilter-greylist restarts. The AUTO (whitelisted) entries seems to be o.k. but the greylisted are with random negative numbers. In my greylist.conf I'm using 8m for delay, which is definitely not seen with these numbers.

Please provide more information on the system and environment you are using.
What OS? Version? 
Package from a distribution (which?) or compiled from source?

> Anyone here with a tip what happens?

Looks like a byte-order problem or a library/header include file mismatch (regarding
the the type or size in case of parameter or return value passing) to me ...


JK

Re: [milter-greylist] negative numbers in log

2013-07-11 by Jim Klimov

Is everything okay with your system and/or milter-executing user
account clock/timezone? In the database file typically named like
/var/milter-greylist/greylist.db you can see the timestamps in
plaintext; do they make sense related to your system's current
time?

HTH,
//Jim

Re: [milter-greylist] negative numbers in log

2013-07-12 by manu@...

Rudolf Gabler <rudolf.gabler@...> wrote:

> Anyone here with a tip what happens?

You are certain your systel clock did not have been wandering in the
future, then reset? 

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

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.