Yahoo Groups archive

Milter-greylist

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

Thread

milter-greylist-1.6rc1 released

milter-greylist-1.6rc1 released

2004-11-28 by manu@netbsd.org

Today I branched the new stable branch for upcoming milter-greylist-1.6.
Here is version 1.6rc1, which is likely to become 1.6 if nobody find an
horrible bug in it.

ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-1.6rc1.tgz
MD5 (milter-greylist-1.6rc1.tgz) = a86a59bf8c4e33534c04be94d467e5b7

Now it's branched, I'm ready to take new features in the developement
branch (the upcoming 1.7.1)

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-11-29 by S L

On Sun, Nov 28, 2004 at 06:46:12PM +0100, manu@... wrote:
> 
> Today I branched the new stable branch for upcoming milter-greylist-1.6.
> Here is version 1.6rc1, which is likely to become 1.6 if nobody find an
> horrible bug in it.
> 
> ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-1.6rc1.tgz
> MD5 (milter-greylist-1.6rc1.tgz) = a86a59bf8c4e33534c04be94d467e5b7
> 

Emmanuel, I moved from 1.4 to 1.6rc1. 
I'm running "test mode" (only activating milter-greylist for
some domains).
On one machine I did not remove the greylist.db and once again 
faced some errors with some entries with [ ] characters in the 
email part :

Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "@" line 16325, skipping
Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "[" line 16326, skipping
Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "]" line 16326, skipping

Example of such lines : 
82.231.118.33              <O[5-]@...>             <janssf1@...>   

A vi or sed call are needed to clean the greylist.db .. 

IMHO the following code in except.c  :
               syslog(LOG_INFO, "%s: testmode: skipping greylist "
                   "for recipient \"%s\"", queueid, rcpt);

is too verbose when running testmode. 
Can we remove it or changed it to LOG_DEBUG for 1.6 ?

Regards, 

SL/

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-11-30 by Christian Pelissier

>
>Emmanuel, I moved from 1.4 to 1.6rc1. 
>I'm running "test mode" (only activating milter-greylist for
>some domains).
>On one machine I did not remove the greylist.db and once again 
>faced some errors with some entries with [ ] characters in the 
>email part :
>
>Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "@" line 16325, 
skipping
>Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "[" line 16326, 
skipping
>Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "]" line 16326, 
skipping
>
>Example of such lines : 
>82.231.118.33              <O[5-]@...>             
<janssf1@...>   
>

I also have entries with [ ] in my greylist.db :

<I[5-]@...>
<P[5-]@...>

Such entries are used to made regular expression debugging harder for
based on regex filters.
I used that in the past :-)

^From: .*<[-A-Za-z_.]+[0-9]+[-A-Za-z_.]+.*@msn\.com>

>A vi or sed call are needed to clean the greylist.db ..
 
Waiting a monday morning to upgrade with a new greylist.db seems better


--
Christian Pélissier
Office National d'Études et de Recherches Aérospatiales BP 72 92322 Chatillon
Tel: 33 1 46 73 44 19, Fax: 33 1 46 73 41 50

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-11-30 by manu@netbsd.org

S L <milter@...> wrote:

> Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "@" line 16325,
> Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "skipping [" line
> Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "16326, skipping
> Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "]" line 16326,
> Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "skipping
> 
> Example of such lines : 
> 82.231.118.33              <O[5-]@...>      <janssf1@...>
> 
> A vi or sed call are needed to clean the greylist.db .. 

milter-greylist refuses to restart? I expect it to just skip the sick
lines and go ahead. 

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-11-30 by S L

On Tue, Nov 30, 2004 at 06:03:16PM +0100, manu@... wrote:
> 
> S L <milter@...> wrote:
> 
> > Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "@" line 16325,
> > Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "skipping [" line
> > Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "16326, skipping
> > Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "]" line 16326,
> > Nov 29 20:01:00 mailgate4 milter-greylist: unknown token "skipping
> > 
> > Example of such lines : 
> > 82.231.118.33              <O[5-]@...>      <janssf1@...>
> > 
> > A vi or sed call are needed to clean the greylist.db .. 
> 
> milter-greylist refuses to restart? I expect it to just skip the sick
> lines and go ahead. 
> 
> -- 
Clearly, milter-greylists did start. But I prefered removing the
entries to avoid any futur similar warnings ... 


PS : there was a similar problem on another machine with entries such
as : <\z-.u@b> and  <a\nsales@...>


Regards, 

SL/

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-12-01 by manu@netbsd.org

S L <milter@...> wrote:

> Clearly, milter-greylists did start. But I prefered removing the
> entries to avoid any futur similar warnings ...

The rotten entries are not reloaded, so you won't have more warnings
after you reload.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-12-02 by S L

On Sun, Nov 28, 2004 at 06:46:12PM +0100, manu@... wrote:
> 
> Today I branched the new stable branch for upcoming milter-greylist-1.6.
> Here is version 1.6rc1, which is likely to become 1.6 if nobody find an
> horrible bug in it.
> 
> ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-1.6rc1.tgz
> MD5 (milter-greylist-1.6rc1.tgz) = a86a59bf8c4e33534c04be94d467e5b7
> 
> Now it's branched, I'm ready to take new features in the developement
> branch (the upcoming 1.7.1)
> 

Emmanuel, 

I now want to only add a report header to delayed messages.
I run milter-greylist in test mode(-T) and so set "report delays"
in the config file.
I don't get the header X-Greylist

I though get a sendmail log  line :

Dec  2 12:04:32 mailgate milter-greylist: iB2B4TaD025598: addr
x.x.x.x from <C.P@...> rcpt <me@...>: autowhitelisted for
more 24:00:00

but this message did not get the Milter-greylist header

The code however says clearly :

  533         if (conf.c_report & C_DELAYS)
  534                 smfi_addheader(ctx, HEADERNAME, hdr);

Did I missed up something ?
Logic problem ?

SL/

Re: milter-greylist-1.6rc1 released

2004-12-02 by eugene_kurmanin

Program work correct.
"autowhitelisted for more" is mean that message don't delay, milter-
greylist is seen this message and delay it early :)

just set "reports all" and you will see.

--- In milter-greylist@yahoogroups.com, S L <milter@f...> wrote:
Show quoted textHide quoted text
> I now want to only add a report header to delayed messages.
> I run milter-greylist in test mode(-T) and so set "report delays"
> in the config file.
> I don't get the header X-Greylist
> 
> I though get a sendmail log  line :
> 
> Dec  2 12:04:32 mailgate milter-greylist: iB2B4TaD025598: addr
> x.x.x.x from <C.P@d...> rcpt <me@o...>: autowhitelisted for
> more 24:00:00
> 
> but this message did not get the Milter-greylist header
> 
> The code however says clearly :
> 
>   533         if (conf.c_report & C_DELAYS)
>   534                 smfi_addheader(ctx, HEADERNAME, hdr);
> 
> Did I missed up something ?
> Logic problem ?
> 
> SL/

Re: [milter-greylist] milter-greylist-1.6rc1 released

2004-12-02 by Christian Pelissier

>Did I missed up something ?
>Logic problem ?
Sendmail syslog level not the same on the test machine ?


--
Christian Pélissier
Office National d'Études et de Recherches Aérospatiales BP 72 92322 Chatillon
Tel: 33 1 46 73 44 19, Fax: 33 1 46 73 41 50

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.