| To: | qmail@list.cr.yp.to |
|---|---|
| Subject: | Re: Filtering Mail Already In Queue |
| From: | Kyle Wheeler <kyle-qmail@memoryhole.net> |
| Date: | Sun, 12 Aug 2007 00:26:32 -0600 |
| Comment: | DomainKeys? See http://domainkeys.sourceforge.net/ |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| Dkim-signature: | v=0.5; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=received:received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; q=dns/txt; s=default; bh=L7l5kMzaigYMyfhtgIxwBom+0rg=; b=Iu/pILEuBAsx8KRxr0jgDnehNyqhu6DmfXD4T7SCFf70h2ILob5D8WrEnjZ2nZ7osX6ja32Eob7+uhd5/kUyOnjupb2St2wCAEjKvZHo+tFxGeqS11gozjGSjuypdKu2EmqQuwT+mVjQjSQtujmEJL4lbfknUVAPLkH+7fuDAMo= |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=Wq+N4uzUS0WuRwTZCr17RPR4cM9EuLpE4ujABOlxCzl+AFcWfi9PtC7E1vKmp+Qwm3ZrclTv1Tb+a9FcBMTzIH/XQN33cR41zpHrWmWzYDOSzZPNZkdR8oKCx8/FDg8i3I3ARN6gffN2KISiyQ/GmIYAkSnsqzyDIkM441zIXik=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent; |
| Domainkey-status: | good |
| In-reply-to: | <95137d3a0708112220g3e11daa2u2f4f5a164270ce50@mail.gmail.com> |
| Mail-followup-to: | qmail@list.cr.yp.to |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <95137d3a0708112220g3e11daa2u2f4f5a164270ce50@mail.gmail.com> |
| User-agent: | Mutt/1.5.16 (2007-07-09) |
On Sunday, August 12 at 12:20 AM, quoth Aaron Goldblatt: messages in queue: 665789 messages in queue but not yet preprocessed: 250985 Yikes! Most of this is incoming spam from a catch-all that's been open for many years. I know at some point I need to get around to closing it (and this situation is exactly why), but for the moment I have a different issue. Honestly, no, closing it is the first issue. Your statement reads something like this: "my boat is sinking; I have a hole in the boat that is filling the cabin with water, and I know at some point I should plug the hole, but for the moment I want to figure out how to pump out the water first." The answer is: no, plug the hole first. THEN pump out the water. So my question is, is there a way to spam filter or recipient filter this garbage and remove it from the queue? Even a curses-based mass delete thing would be okay with me at this point. It seems to me that most stuff available at qmail.org is based on filtering before stuff hits the queue, which isn't the issue here. This stuff is already in queue. ...curses based? HAH! You're pretty funny. No, there is nothing so fancy available.However, all is not lost, if you're willing to "stoop" to the level of a shell script. First, turn off qmail (stop qmail-send AND qmail-smtpd). Then:
find /var/qmail/queue/mess -type f -exec \
bash -c 'spamc -c $1 || qmHandle -d`basename $1`' {} \;
Of course, that requires qmHandle, but you get the idea.
The point of using `find`, of course, is to avoid potential filecount
limitations in shell scripts, otherwise, you could do this:
for F in /var/qmail/queue/mess/*/* ; do
spamc -c $F || qmHandle -d`basename $F`
done
~Kyle
--
If Tyranny and Oppression come to this land, it will be in the guise
of fighting a foreign enemy.
-- James Madison
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Filtering Mail Already In Queue, Aaron Goldblatt |
|---|---|
| Next by Date: | Re: Filtering Mail Already In Queue, Aaron Goldblatt |
| Previous by Thread: | Filtering Mail Already In Queue, Aaron Goldblatt |
| Next by Thread: | Re: Filtering Mail Already In Queue, Aaron Goldblatt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |