Recent changes to bugs

error introduced with 1.3.0 and >

Ivan Jenkins — Mon, 22 Oct 2007 21:56:04 -0000

[qmhandle-1.2.3]# ./qmHandle -S"failure notice"
Qmail isn't running... no need to stop it.
Looking for messages with Subject: failure notice
No messages matching Subject "failure notice" found in the queue!
Qmail wasn't running when qmHandle was started, so it won't be restarted.

[qmhandle-1.3.0]# ./qmHandle -S"failure notice"
Qmail isn't running... no need to stop it.
Looking for messages with Subject: failure notice
Deleting message: 19211843
Uncaught exception from user code:
cannot open message 15/4767225! Is qmail-send running?
at ./qmHandle line 246
main::getSubject('15/4767225') called at ./qmHandle line 699
main::DelMsgSubj('failure notice') called at ./qmHandle line 171

These where run seconds apart, on the same queue. The message 4767225 doesn't exist, nor did it exist when qmHandle 1.3.0 or 1.3.2 were executed. Not sure where it picked up that number.

subject with multi line

Anonymous — Wed, 19 Sep 2007 02:28:46 -0000

can not get the right subject when the subject have multi lines.

Can't exec "pidof"

Andrew Liles — Wed, 25 Jul 2007 23:52:06 -0000

This is for the information of others; there is perhaps a documentation issue here.

In version 1.2.0 the configuration of qmHandle has these two options for determining the pid of qmail-send:

# Enter here the system command which returns qmail PID. The following
# should work on most Unixes:
#my ($pidcmd) = 'pidof qmail-send';
my ($pidcmd) = 'svstat /service/qmail-send | sed -e \'s/.*(pid //\' | sed -e \'s/) .*//\'';

In version 1.3.2 the code is:

#####
# Enter here the system command which returns qmail PID. The following
# should work on most Unixes:
my ($pidcmd) = 'pidof qmail-send';

On machines with pidof support you get the error
Can't exec "pidof"

A recent machine build of FreeBSD 6.1 (May 2006)
pidof
is not installed by default. It can installed using the Port sysutils/pidof

If qmail-send busy, qmHandle should wait

Andrew Liles — Wed, 25 Jul 2007 23:40:33 -0000

Issue 1:
qmHandle should check to see if qmail (send) is running, and if it is, stop it. I find that some email (typically spam bounces) cause the qmail-remote processes that qmail-send spawns run for a long time. Often then, you issue qmail-send to terminate (gracefully) and it just waits for all its spawned processes to complete.

I think qmHandle should WAIT until qmail-send terminates gracefully, and then manipulate the queue. Or perhaps kill the long-running qmail-remote processes.

Issue 2:
When trying to terminate qmail-send, I get this error:

Calling system script to terminate qmail...
svc: warning: unable to chdir to /service/qmail-deliver: file does not exist

then the system hangs until qmail-send does terminate naturally, and then it errors on the message that was being processed but has now gone:
Uncaught exception from user code:
cannot open message 14/359! Is qmail-send running?
at /var/qmail/bin/qmHandle line 246
main::getSubject('14/359') called at /var/qmail/bin/qmHandle line 701

I use daemontools, and have used the default:
my ($stopqmail) = '/usr/local/bin/svc -d /service/qmail-send';
(and that command on its own works fine)

so where does /service/qmail-deliver come in to it??

(I have v1.3.2)

my $version not updated in 1.3.2

BJ Dierkes — Thu, 19 Jul 2007 20:27:20 -0000

--- qmhandle-1.3.2/qmHandle.ver 2007-07-15 10:46:28.000000000 -0500
+++ qmhandle-1.3.2/qmHandle 2007-07-15 10:46:36.000000000 -0500
@@ -11,7 +11,7 @@
use warnings;
use diagnostics;

-my $version = '1.3.1';
+my $version = '1.3.2';

#################### USER CONFIGURATION BEGIN ####################

Global symbol "$rmsg" requires explicit package

Andrew Liles — Tue, 10 Jul 2007 21:24:34 -0000

With version 1.3.1 I get the following error when I execute:
./qmHandle
but if I use version 1.2.0 there is no error on the same machine.

# ./qmHandle
Global symbol "$rmsg" requires explicit package name at ./qmHandle line 299.
Global symbol "$rmsg" requires explicit package name at ./qmHandle line 300.
Global symbol "$dir" requires explicit package name at ./qmHandle line 300.
Global symbol "%type" requires explicit package name at ./qmHandle line 300.
Execution of ./qmHandle aborted due to compilation errors (#1)
(F) You've said "use strict vars", which indicates that all variables
must either be lexically scoped (using "my"), declared beforehand using
"our", or explicitly qualified to say which package the global variable
is in (using "::").

Uncaught exception from user code:
Global symbol "$rmsg" requires explicit package name at ./qmHandle line 299.
Global symbol "$rmsg" requires explicit package name at ./qmHandle line 300.
Global symbol "$dir" requires explicit package name at ./qmHandle line 300.
Global symbol "%type" requires explicit package name at ./qmHandle line 300.
Execution of ./qmHandle aborted due to compilation errors.
at ./qmHandle line 854

Not showing message numbers

Anonymous — Mon, 02 Jul 2007 12:24:38 -0000

./qmHandle -R
Return-path: anonymous@******
From: *****
To: *****
Subject: Grant / Donation.
Date: 28 Jun 2007 18:03:14 +0100
Size: 6906 bytes

Return-path: *****
From: *****
To: ****
Subject: Grant / Donation.
Date: 29 Jun 2007 04:50:47 +0100
Size: 7361 bytes

Shouldn't there be message numbers here?

Queue display transposed

Anonymous — Sun, 22 Apr 2007 17:58:15 -0000

qmHandle -R and qmHandle -L now appear to display the wrong queues. i.e. qmHandle -L displays the remote queue, not the local as it should.

Delete messages in the bounce queue

oldtedt — Tue, 15 Aug 2006 10:34:46 -0000

Many thanks, used qmHandle to sucessfully delete 8,000+
spam messages in the local and remote queues. How can I
delete these messages in the bounce queue - is it
simply a case of deleting the message in the bounce
directory?

Error on execution

Parag — Tue, 23 Nov 2004 04:18:44 -0000

On executing qmHandle 1.2.0 we get the following message:

[root@xxxxxxx qmhandle]# sh qmHandle
qmHandle: line 10: use: command not found
qmHandle: line 11: use: command not found
qmHandle: line 12: use: command not found
qmHandle: line 14: my: command not found
qmHandle: line 20: syntax error near unexpected token
`$queue'
qmHandle: line 20: `my ($queue) = '/var/qmail/queue/';'

We have verified that the path /var/qmail/queue is correct.
Have no idea about the other errors.

PS: I am not a technical person, but was interested in
applying this utility. Any help would be appreciated.

Thanx.
Parag.