Milter-greylist

Hi,

  We've got milter-greylist working on 5 servers.  Recently, we went
from a whitelist default policy to a blacklist policy.  

  A few weeks before, we realized that we didn't need to restart
milter-greylist after each change to the config file, so we don't
restart it after each change anymore.

The problem is that it comes back to the default config, once in a
while, w/o obvious reason. How can I tell?  The default delay comes
back to 30m (we're using 1m) "delayed for 00:30:00", also, we usually
use the quiet option, but milter greylist starts saying 'come back in
30:00'.

I thought, at first, that it was a syntax error in the config, but
we're now checking the config file everytime we sync it, so it
shouldn't be the case.

Here is what I found in the logs:

lots of :

milter-greylist: greylist, mi_rd_cmd: read returned -1: Connection
reset by peer

A few of these:

milter-greylist: Unexpected reply "105" from peer 10.20.20.50 closing
connexion (0 entries queued)

Anyone experiencing a similar problem?

Thanks,

Ugo

--
Disclaimer: I'm still getting to know this package so forgive me if my
observations or conclusions are completely off base.
--

Sort of.  I've reported recently that I've seen milter-greylist crash
after such an error in the log file.  It usually seems to come after a
connection is reset while the milter is trying to do something with the
socket.

I have also noticed that the milter seems to operate on the default policy
while it's starting up and still reading in the config file and
greylist.db

I don't suppose you have your milter-greylist instance set up to be
started up again automatically if it crashed?

Cheers.

-- 
      /"\    Happiness Will Prevail! <mblake@...>   \      oo
     /   \                                                    \____|\mm
     \   /   GAT d- s-:++ a? C+++ UL++++ P+ L+++ E--- W++     //_//\ \_\
      \ /    N+ o-- K--- w--- O- M V-- PS+ PE Y+ PGP t++     /K-9/  \/_/
       X     5+ X+ R tv+ b+++ DI++ D+ G-- e h--- r+++ y+++  /___/_____\
      / \                                                   -----------
                ASCII Ribbon Campaign Against HTML Mail

On Wed, November 29, 2006 12:03 pm, Ugo Bellavance wrote:
> Hi,
>
>   We've got milter-greylist working on 5 servers.  Recently, we went
> from a whitelist default policy to a blacklist policy.
>
>   A few weeks before, we realized that we didn't need to restart
> milter-greylist after each change to the config file, so we don't
> restart it after each change anymore.
>
> The problem is that it comes back to the default config, once in a
> while, w/o obvious reason. How can I tell?  The default delay comes
> back to 30m (we're using 1m) "delayed for 00:30:00", also, we usually
> use the quiet option, but milter greylist starts saying 'come back in
> 30:00'.
>
> I thought, at first, that it was a syntax error in the config, but
> we're now checking the config file everytime we sync it, so it
> shouldn't be the case.
>
> Here is what I found in the logs:
>
> lots of :
>
> milter-greylist: greylist, mi_rd_cmd: read returned -1: Connection
> reset by peer
>
> A few of these:
>
> milter-greylist: Unexpected reply "105" from peer 10.20.20.50 closing
> connexion (0 entries queued)
>
> Anyone experiencing a similar problem?
>
> Thanks,
>
> Ugo
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

Sort of.  I've reported recently that I've seen milter-greylist crash

 after such an error in the log file.  It usually seems to come after a

 connection is reset while the milter is trying to do something with the

 socket.

 

> Ok


 I have also noticed that the milter seems to operate on the default policy

 while it's starting up and still reading in the config file and

 greylist.db


> Ok
 

 I don't suppose you have your milter-greylist instance set up to be

 started up again automatically if it crashed?

 

> No, it is not started automatically when it crashes.  I don't see it crash really often.

Ugo


 




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Hi, I am so Brazil and I finished to install greylist in my server of email. which is the best configuration for greylist.conf  in /etc/mail/greylist.conf ? 

--- In milter-greylist@yahoogroups.com, "Rildo" <delpino@...> wrote:
>
>  
> Hi, I am so Brazil and I finished to install greylist in my server of
> email.

Hi.

>  which is the best configuration for greylist.conf  in
> /etc/mail/greylist.conf ?

First, please avoid hijacking a thread.  If you have a new subject,
don't just reply to a message.

For your question, the info is in the README file contained in the
package.

Regards,

Ugo

>  
>  
>  
> Thank you
>  
> Sorry by my english 
>  
>  
>  
> -----Mensagem original-----
> De: milter-greylist@yahoogroups.com
> [mailto:milter-greylist@yahoogroups.com] Em nome de Ugo Bellavance
> Enviada em: quarta-feira, 29 de novembro de 2006 18:03
> Para: milter-greylist@yahoogroups.com
> Assunto: [milter-greylist] milter-greylist 2.0.2 resetting to default
> automatically
>  
> Hi,
> 
> We've got milter-greylist working on 5 servers. Recently, we went
> from a whitelist default policy to a blacklist policy. 
> 
> A few weeks before, we realized that we didn't need to restart
> milter-greylist after each change to the config file, so we don't
> restart it after each change anymore.
> 
> The problem is that it comes back to the default config, once in a
> while, w/o obvious reason. How can I tell? The default delay comes
> back to 30m (we're using 1m) "delayed for 00:30:00", also, we usually
> use the quiet option, but milter greylist starts saying 'come back in
> 30:00'.
> 
> I thought, at first, that it was a syntax error in the config, but
> we're now checking the config file everytime we sync it, so it
> shouldn't be the case.
> 
> Here is what I found in the logs:
> 
> lots of :
> 
> milter-greylist: greylist, mi_rd_cmd: read returned -1: Connection
> reset by peer
> 
> A few of these:
> 
> milter-greylist: Unexpected reply "105" from peer 10.20.20.50 closing
> connexion (0 entries queued)
> 
> Anyone experiencing a similar problem?
> 
> Thanks,
> 
> Ugo
>  
> 
> ----------------------------------------------------- 
> Mensagem verificada pelo software Anti-Virus McAfee. 
> FAMERP - STI 
> 
> --------------------------------------------------------- 
> Mensagem verificada pelo software de Anti-Virus McAfee.
> FAMERP - STI
>

Hi, I am so Brazil and I finished to install greylist in my server of email. which is the best configuration for greylist.conf  in /etc/mail/greylist.conf ?