Eric,

Where can one obtain the magic graylist trimming script and what time frame 
would you suggest for running it? Weekly perhaps?

Thanks,
Scott


On Jul 1, 2010, at 4:23 PM, Eric Shubert <e...@shubes.net> wrote:

> There is another aspect to graylist-max-secs. This parameter limits the time 
> that a graylist entry is valid. See 
> http://spamdyke.org/documentation/README.html#GRAYLISTS at the end of the 
> section.
> 
> You should also note that spamdyke itself does not provide for cleaning up 
> graylist entries. You should install the qtp-prune-graylist script as a cron 
> job to keep your graylist tree trimmed. ;) I hope at some point to modify the 
> qtp-install-spamdyke script to include this.
> 
> -- 
> -Eric 'shubes'
> 
> Martin Waschbuesch wrote:
>> On a server I use it on, I have left the default settings intact. The timing 
>> settings you posted look like the default to me, so, I think all is in order.
>> You just have to be aware that graylisting causes delays.
>> Note: If you look at the graylist-max-secs=2678400, that means 44640 minutes 
>> or 744 hours or 31 days. You can be pretty sure that any normal mail server 
>> would have retried well before that time runs out.
>> Martin
>> Am 01.07.2010 um 16:42 schrieb Thiago - TI - Realeza:
>>> Yes... could make sense....
>>> 
>>> Do you think that I have to change max/min secs from graylist?
>>> 
>>> Thanks Martin
>>> 
>>> Thiago
>>> 
>>> -----Mensagem original-----
>>> De: Martin Waschbuesch [mailto:mar...@waschbuesch.de] Enviada em: 
>>> quinta-feira, 1 de julho de 2010 11:36
>>> Para: qmailtoaster-list@qmailtoaster.com
>>> Assunto: Re: [qmailtoaster] Spamdyke Graylist Delay
>>> 
>>> Hi there,
>>> 
>>> This is very normal behaviour. Graylisting not only depends on your server's
>>> timing settings, but on the behavior of the sending MTA. If that MTA does
>>> not retry within a given time (that is what you can configure) the mail will
>>> not be delivered, but regarded as spam. However, the time the sending server
>>> waits before resending is not something you can configure.
>>> 
>>> That means that as long as the sending server's reply in a timeframe defined
>>> by your graylist-min-secs and graylist-max-secs, the mail will be delivered
>>> with exactly the retr delay that the sending server's admin had configured.
>>> 
>>> Makes sense?
>>> 
>>> Martin
>>> 
>>> 
>>> Am 01.07.2010 um 16:22 schrieb Thiago - TI - Realeza:
>>> 
>>>> Hello all
>>>> 
>>>> I have some “trouble” here.
>>>> 
>>>> For example, when I receive a message and spamdyke graylist it, I have an
>>> delay about 20 minutes to the message be delivered on my mailbox.
>>>> Here is a log
>>>> 
>>>> 07-01 10:37:50 spamdyke[17408]: DENIED_GRAYLISTED from:
>>> mailerweb.boletim.geh...@gehaka.com.br to: rodrigo.so...@domain.ind.br
>>> origin_ip: 201.6.108.170 origin_rdns: mail.gehaka.com.br auth: (unknown)
>>>> 
>>>> The message was delivered on my server at 10:37AM but was in my mailbox
>>> 20 minutes later. It happens with all messages that are graylisted.
>>>> I have ‘played’ with this conf a lot, mostly with graylist options. Read
>>> all documentation on spamdyke site and look for something here on list.
>>>> Someone have an trick ? Or it´s just normal? Remember, all messages get
>>> the same time to be delivered on mailboxes when graylisted.
>>>> Thanks!
>>>> 
>>>> Here is my spamdyke conf:
>>>> 
>>>> dns-blacklist-entry=zen.spamhaus.org
>>>> dns-blacklist-entry=bl.spamcop.net
>>>> graylist-dir=/var/spamdyke/graylist
>>>> graylist-level=always
>>>> graylist-max-secs=2678400
>>>> graylist-min-secs=180
>>>> greeting-delay-secs=5
>>>> idle-timeout-secs=60
>>>> ip-blacklist-file=/etc/spamdyke/blacklist_ip
>>>> ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
>>>> ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
>>>> ip-whitelist-file=/etc/spamdyke/whitelist_ip
>>>> local-domains-file=/var/qmail/control/rcpthosts
>>>> log-level=info
>>>> log-target=stderr
>>>> max-recipients=50
>>>> #policy-url=http://my.policy.explanation.url/
>>>> rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
>>>> rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
>>>> recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
>>>> reject-empty-rdns
>>>> #reject-ip-in-cc-rdns
>>>> reject-missing-sender-mx
>>>> reject-unresolvable-rdns
>>>> sender-blacklist-file=/etc/spamdyke/blacklist_senders
>>>> sender-whitelist-file=/etc/spamdyke/whitelist_senders
>>>> tls-certificate-file=/var/qmail/control/servercert.pem
>>> 
>>> --
>>> "The nice thing about being a celebrity is that when you bore people, they
>>> think it's their fault."
>>> 
>>> Henry Kissinger
>>> 
>>> 
> 
> 
> -- 
> -Eric 'shubes'
> 
> 
> ---------------------------------------------------------------------------------
> Qmailtoaster is sponsored by Vickers Consulting Group 
> (www.vickersconsulting.com)
>   Vickers Consulting Group offers Qmailtoaster support and installations.
>     If you need professional help with your setup, contact them today!
> ---------------------------------------------------------------------------------
>    Please visit qmailtoaster.com for the latest news, updates, and packages.
>         To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>    For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 
> 

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.

      To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
     For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


Reply via email to