Hi Guy

I have a spamming problem, i have check my qmail stat and there are over 0.5 million emails in queue, further investigations show that the email being sent has the following header

--------------------------
Received: from punt-2.mail.demon.net by mailstore for x
id 1012803278:20:15964:20; Mon, 04 Feb 2002 06:14:38 GMT
Received: from [x13.2x9.x9.90] ([x13.2x9.x9.90]) by punt-2.mail.demon.net
id aa2111996; 4 Feb 2002 6:14 GMT
Received: (qmail 17956 invoked by uid 10046); 4 Feb 2002 02:47:07 -0000
Message-ID: <20020204024707.17955.qmail@localhost.xcom>
To: x <x>
From: nickmela47@yahoo.com <nickmela47@yahoo.com>
---------------------------------

( i have replaced some IP digits with x for security )

Now does the qmail 17956 invoked by uid 10046 mean that this email was sent via a form and if so, how can i use this uid to determine which users account the spammers are using,

I have tried deleting the emails from queue using the application qmail-remove but its taking for ever an i keep getting errors after its been running for a while.


So how can i manually purge the queue or to even delete ALL messages from the queue altogether.

I appreciate your help

I once got spam to qmail. The first thing I did was stopping qmail. The second , run qmail-remove. it will delete 1xxx messages at one time so you should run it several time.

qmail-remove -p 'nickmela47@yahoo.com' -r

Thnaks, i have already tried qmail-remove but its taking too long eta over 48hrs none stop deleting

A kludgy way of doing it is to stop qmail, delete the queue, create a new one with queue-fix, restart qmail.

It's quick and dirty but it'll do in a pinch.

As far as I know, you can delete all of the files in the qmail queue directories without breaking the queue.

Stop qmail, then run:

find /var/qmail/queue -type f -exec rm -f {} \;

Worked for me last time I had to clean out the queue rather fast. Of course you're going to lose every message, and it's still going to take awhile if you have .5 million messages.

So the quickest way would probably be to use blazarium's method, although I recommend queue-repair over queue-fix.