Eric Shubert wrote:
[email protected] wrote:
Quoting Eric Shubert <[email protected]>:


I think this is more complicated than it needs to be, and not any more
efficient than the qtp-prune-graylist script
(http://qtp.qmailtoaster.com/trac/browser/bin/qtp-prune-graylist). The
script is admittedly a little i/o intensive, but a) some of it is
typically cached, and b) it's not all that slow. Besides which, what's
the problem? It's typically run once a day, and I don't see it impacting
the performance of anything else.
Depends on the scale of your mail server. See this entry from the ChangeLog:

  NOT BACKWARDS COMPATIBLE: Changed the graylist system to create a deeper
directory structure by creating folders for the senders' domain names. This
     will allow busy servers to use graylisting even when the number of sender
     addresses could exceed the number of entries allowed in a folder.  Thanks
     to Trog for suggesting this one.

My mail servers graylisting was hitting filesystem limits in less than 24 hours.

Which limit(s) of which filesystem?

The qtp-prune-graylist script would take much longer than a day to run on my mail server.

Did you run it?
In 'silent' mode?

The first large server it ran on, it processed over 1.1M entries. I don't recall the run time, but I believe it was less than an hour. This was on a filesystem that had run out of inodes.

I'd basically have to run it continuously on my server - it would certainly impact performance.

How many graylist entries do you have?

Eric,
Here are those results after using the script.. It was still running after 10pm but it got the job done it looks like.
qtp-prune-graylist processing graylist tree at /var/spamdyke/graylist ...
qtp-prune-graylist pruning entries older than 1209600 seconds ...
qtp-prune-graylist processing domain hhinc.net ...
qtp-prune-graylist hhinc.net - 80118 entries found
qtp-prune-graylist hhinc.net - 75815 entries removed
qtp-prune-graylist hhinc.net - 56689 empty directories removed
qtp-prune-graylist hhinc.net - 4314 graylisting entries remain
qtp-prune-graylist processing domain test.com ...
qtp-prune-graylist test.com - 1 entries found
qtp-prune-graylist test.com - 1 entries removed
qtp-prune-graylist test.com - 1 empty directories removed
qtp-prune-graylist test.com - 0 graylisting entries remain
qtp-prune-graylist processing domain wletc.com ...
qtp-prune-graylist wletc.com - 1164192 entries found
qtp-prune-graylist wletc.com - 1127660 entries removed
qtp-prune-graylist wletc.com - 439585 empty directories removed
qtp-prune-graylist wletc.com - 37315 graylisting entries remain
qtp-prune-graylist processing domain localhost ...
qtp-prune-graylist localhost - 0 entries found
qtp-prune-graylist localhost - 0 entries removed
qtp-prune-graylist localhost - 0 empty directories removed
qtp-prune-graylist localhost - 0 graylisting entries remain
qtp-prune-graylist total - 4 domains processed
qtp-prune-graylist total - 1244311 entries found
qtp-prune-graylist total - 1203476 entries removed
qtp-prune-graylist total - 496275 empty directories removed
qtp-prune-graylist total - 41629 graylisting entries remain

The wletc domain is my largest domain.

I am having trouble with a customer who was using smtp-auth to send a 1MB attachment and it is timing out. Typically only takes a few seconds and its done but this is the first I have seen this.
We are sending someone  to  check it  out  from  his end  to see whats up.
Have any ideas on where I should check to see why its timing out. Sometimes they will send but its taking a long time around 8mins or more.

--Dave

_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to