|
Jake, you should run your own rbl and return a 553
message back to the sender. Since you are running a dns caching anyway it
isn't hard to setup. I think the one we have a work contains several
hundred entries now (some of /19 and /20 networks)
George Sweetnam
----- Original Message -----
From: Jake Vickers
Sent: Thursday, September 21, 2006 9:12 AM
Subject: Re: [qmailtoaster] messages stuck in the queue The queue lifetime controls how long a message sits in the queue before it gets sent to /dev/null. It's controlled by the /var/qmail/control/queuelifetime file, and needs to have a value in it of how long you'd like the threshold to be. This number is in seconds. I'm using 10800 for a value on one of my machines (I happened to be logged into it while typing this). And yes, I meant blacklists. While not extremely effective, they will stop SOME spammer's bad IP addresses from connecting. It's a little bit of work, but you may check your logs to see what IP addresses the messages are coming from. I've found that whenever I got a "storm" like this, 80%-90% would be from a single IP trying to relay through me and I just add an entry in my iptables to deny connections. |
- [qmailtoaster] messages stuck in the queue Steve Ingraham
- Re: [qmailtoaster] messages stuck in the queue Jake Vickers
- RE: [qmailtoaster] messages stuck in the queue Steve Ingraham
- Re: [qmailtoaster] messages stuck in the queue Jake Vickers
- Re: [qmailtoaster] messages stuck in the queu... George Sweetnam
- [qmailtoaster] URGENT !!! '553 sorry, tha... Bilgehan POYRAZ
- Re: [qmailtoaster] messages stuck in the ... Jake Vickers
- RE: [qmailtoaster] messages stuck in the queue Steve Ingraham
