headers
attila.bruncsak | 4 Jun 2007 11:19
Favicon

RE: version 4.0a4 aborts with message: "mg_setreply(): invoked twice"

> What about this fix?
> 
> Index: milter-greylist.c
> ===================================================================
> RCS file: /cvsroot/milter-greylist/milter-greylist.c,v
> retrieving revision 1.188
> diff -U2 -r1.188 milter-greylist.c
> --- milter-greylist.c   30 May 2007 23:32:06 -0000      1.188
> +++ milter-greylist.c   31 May 2007 23:38:02 -0000
>  <at>  <at>  -2904,8 +2904,8  <at>  <at> 
>  
>  	if (priv->priv_sr.sr_msg_x != NULL) {
> -		mg_log(LOG_ERR, "%s: mg_setreply(): invoked twice",
> -		     priv->priv_queueid);
> -		exit(E _SOFTWARE);
> +		free(priv->priv_sr.sr_msg_x);
> +		priv->priv_sr.sr_msg_x = NULL;
>  	}
> +
>  	priv->priv_sr.sr_msg_x =
>  		fstring_expand(priv, rcpt, priv->priv_sr.sr_msg);
> 

I have applied the patch, and there is no problem for the time being.

Bests,
Attila

 
Yahoo! Groups Links
(Continue reading)

Permalink | Reply | 0 comments |
headers
manu | 4 Jun 2007 21:42
Picon

milter-greylist 4.0 alpha6 is available

Here is our alpha6

ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-4.0a6.tgz
MD5 (milter-greylist-4.0a6.tgz) = fb469a3947a6821519a62644a4128Â27

Changes since alpha5:
        Avoid GeoIP reporting "--" for broken domain (Bernhard Schneider )
        Fix run-away string (AIDA Shinra)
        Check for libbind9 if libbind cannot be found (Fabien Tassin)
        Document ACL on TLS DN (Fabien Tassin)
        Avoid spurious exit on DATA stage ACL match for multiple recipients

--

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

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/milter-greylist/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/milter-greylist/join
    (Yahoo! ID required)
(Continue reading)

Permalink | Reply | 5 comments |
headers
Alan Clifford | 8 Jun 2007 00:39
Favicon

Delivery attempt every second or so


Below is the log which I happened to be watching with a tail -f.   Is this 
an anti-greylisting strategy? It continued for the full 5 minutes that I 
have greylisting set for and then it was gobbled by Spam Assassin so I 
don't suppose it really matters.  I wonder if it would continue for hours 
if I had greylisting set up like that.

Hmm, I just noticed that it started 3 minutes after the first attempt and 
then it was continuous for the full 5 minutes.

One thing I find slightly disconcerting is that the number in square 
bracket was the same for the whole 5 minutes, viz [13989].  I assume this 
is the sendmail process id and I should have thought it would be different 
for each attempt?

Jun  7 23:03:17 malander milter-greylist: l57M3GxK013975: addr 
mta10.adelphia.net[68.168.78.202] from <conactme@...> to 
<alan@...> delayed for 00:05:00 (ACL 128)
Jun  7 23:03:17 malander sm-mta[13975]: l57M3GxK013975: Milter: 
to=<alan@...>, reject=451 4.7.1 Greylisting in action,
please come 
back later
Jun  7 23:03:17 malander sm-mta[13975]: l57M3GxK013975: 
from=<conactme@...>, size=1597, class=0, nrcpts=0,
proto=ESMTP, 
daemon=MTA, relay=mta10.adelphia.net [68.168.78.202]
Jun  7 23:06:43 malander milter-greylist: l57M6gvn013989: addr 
mta7.adelphia.net[68.168.78.193] from <conactme@...> to 
<alan@...> delayed for 00:05:00 (ACL 128)
Jun  7 23:06:43 malander sm-mta[13989]: l57M6gvn013989: Milter:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Brian W. Antoine | 8 Jun 2007 01:55
Favicon

RE: Delivery attempt every second or so

> Below is the log which I happened to be watching with a tail  -f.   Is
this 
> an anti-greylisting strategy? It continued for the full 5  minutes that I 
> have greylisting set for and then it was gobbled by Spam  Assassin so I 
> don't suppose it really matters.  I wonder if it would  continue for hours

> if I had greylisting set up like that.

  That looks like your typical maliciously clueless cable company.  They've
decided that a Temp Failure means they should hammer your server into the
ground until it becomes a Permanent Failure or you accept their spam.

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/milter-greylist/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/milter-greylist/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:milter-greylist-digest@... 
    mailto:milter-greylist-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Federico Giannici | 8 Jun 2007 10:30
Picon

Re: Crash of 4.0a [Was: Errors in sendmail with 4.0a1]

manu@... wrote:
> 
> Federico Giannici <giannici@...
<mailto:giannici%40neomedia.it>> 
> wrote:
> 
>  > The OS is OpenBSD 4.1, both i386 and amd64.
>  > No (unusual) error message is logged before the crash.
>  > No coredump is generated.
>  > What else I can look at?
> 
> You can run the milter within gdb, with the -D flag. When it crashes,
> issue the bt command to get a backtrace. It may help.
> 
> Indeed 4.0 alpha series have a bug somewhere. Nobody have been able to
> find it yet. Probably a race condition.

In case it could be useful, I have restricted the range of time the bug 
has been introduced: the problem IS present in version 3.1.3 and IS NOT 
present in 3.1.1.

Bye.

--

-- 
___________________________________________________
     __
    |-                      giannici@...
    |ederico Giannici      http://www.neomedia.it
___________________________________________________
(Continue reading)

Permalink | Reply | 14 comments |
headers
Mart Pirita | 8 Jun 2007 20:00
Picon

Invalid helo strings check support?.

Tere.

Postfix includes good helo check options 
(http://www.postfix.org/uce.html#smtpd_helo_restrictions):

smtpd_helo_restrictions = reject_non_fqdn_hostname, 
reject_invalid_hostname, reject_unknown_hostname

And sendmail does not, which is sad as this is quite efficient, 
especially when unknown_hostname_reject_code is set to 550.

One way to implement it somehow into sendmail is using milter-regex 
(http://www.benzedrine.cx/milter-regex.html), but as this is again 
another milter and as milter-greylist also includes regular expressions 
support, then maybe is possible to to add invalid helo strings check 
directly into milter-greylist?

--

-- 
Mart

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/milter-greylist/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
(Continue reading)

Permalink | Reply | 13 comments |
headers
manu | 13 Jun 2007 07:47
Picon

Re: Invalid helo strings check support?.

Mart Pirita <sysadmin@...> wrote:

> One way to implement it somehow into sendmail is using milter-regex 
> (http://www.benzedrine.cx/milter-regex.html), but as this is again 
> another milter and as milter-greylist also includes regular expressions
> support, then maybe is possible to to add invalid helo strings check 
> directly into milter-greylist?

My concern is always limitting the config file mess.

We can already set an ACL clause on HELO against a substring or a regex.
How do you imagine the syntax for performing a DNS check?

--

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

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/milter-greylist/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/milter-greylist/join
    (Yahoo! ID required)
(Continue reading)

Permalink | Reply | 11 comments |
headers
Mart Pirita | 13 Jun 2007 11:16
Picon

Re: Invalid helo strings check support?.

Tere.
>
> My concern is always limitting the config file mess.
>   
:).
> We can already set an ACL clause on HELO against a substring or a regex.
>   
Hmm, didn't know, any example how to do it?

> How do you imagine the syntax for performing a DNS check?
>
>   
Like dnsbl maybe?

--

-- 
Mart

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/milter-greylist/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/milter-greylist/join
    (Yahoo! ID required)
(Continue reading)

Permalink | Reply | 10 comments |
headers
manu | 13 Jun 2007 13:57
Picon

Re: Invalid helo strings check support?.

Mart Pirita <sysadmin@...> wrote:

> > We can already set an ACL clause on HELO against a substring or a regex.
> Hmm, didn't know, any example how to do it?

In 4.0 beta:
racl blacklist helo /domain\.com/ msg "go away!" 

> > How do you imagine the syntax for performing a DNS check?
> Like dnsbl maybe?

An example.

--

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

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/milter-greylist/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/milter-greylist/join
    (Yahoo! ID required)
(Continue reading)

Permalink | Reply | 8 comments |
headers
Fabien Tassin | 14 Jun 2007 14:04

Re: milter-greylist 4.0 alpha6 is available

According to manu@...:
> 
> Here is our alpha6
> 
> ftp://ftp.espci.fr/pub/milter-greylist/milter-greylist-4.0a6.tgz
> MD5 (milter-greylist-4.0a6.tgz) = fb469a3947a6821519a62644a4128Â27
> 
> Changes since alpha5:
>         Avoid GeoIP reporting "--" for broken domain (Bernhard Schneider )
>         Fix run-away string (AIDA Shinra)
>         Check for libbind9 if libbind cannot be found (Fabien Tassin)
>         Document ACL on TLS DN (Fabien Tassin)
>         Avoid spurious exit on DATA stage ACL match for multiple recipients

there's an issue with configure. I've already faced it with libbind, that why
I've initially proposed the patch mentionned above, but it's a more general
issue.

On a new server, I've compiled m-g as I usually do, so on my cmd line,
I used (amongst other things) --with-libcurl=/usr.

Configure stopped there:

checking for pthread_create in -lpthread... no
checking for pthread_create in -lc_r... no
checking for pthread_create in -lpthreads -lpthread... no
Required libpthread not found. Use --with-libpthread

that was unexpected on Debian.
Looking at config.log, I found out this has nothing to do this pthread:
(Continue reading)

Permalink | Reply | 4 comments |

Gmane