Greetings,
This is a bit strange and i'm not sure why it's happening. I'm using postfix and
maildrop together and i've configured maildrop via mailbox_transport in main.cf.
It sends mail just fine. It's only when mail is sent to a user that's generated
a receipe via SqWebMail that it gets weird. The rule does execute; however, the
message is deferred and hangs in the queue:
Feb 1 19:59:54 asche postfix/qmgr[16219]: $ID: from=<me@myfqdn>,
size=575, nrcpt=1 (queue active)
Feb 1 19:59:54 asche postfix/local[19345]: $ID: to=<test@myfqdn>,
relay=local, delay=85, delays=85/0/0/0.1, dsn=4.3.0, status=deferred (temporary
failure. Command output: maildrop: signal 0x06 )
mailq:
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
$ID 570 Thu Feb 1 21:53:00 me@myfqdn
(temporary failure. Command output: maildrop: signal 0x06)
test@myfqdn
The rule is simply to send a message to test@myfqdn and that message is copied
into another folder. I can use postsuper to flush the queue ID and the rule
executes again.
Signal 6 is ABORT on NetBSD. I saw a lengthy discussion in the archive about
this problem and also someone running NetBSD/alpha 3.0 had a similar issue with
maildrop and 0x06. I did some tests with maildrop and gdb and those weren't much
help in finding what was causing maildrop to abort. More info:
% uname -a
NetBSD asche 3.1 NetBSD 3.1 (ASCHE.MP) #0: Sat Nov 18 16:53:13 UTC 2006
root@asche:/usr/src/sys/arch/alpha/compile/ASCHE.MP alpha
% maildrop -v
maildrop 2.0.2 Copyright 1998-2005 Double Precision, Inc.
GDBM extensions enabled.
Courier Authentication Library extension enabled.
Enabled Berkeley DB instead of GDBM extensions.
Maildir quota extension enabled.
This program is distributed under the terms of the GNU General Public
License. See COPYING for additional information.
% g++ -v
Using built-in specs.
Configured with:
/home/nick/work/netbsd/src/tools/gcc/../../gnu/dist/gcc/configure
--enable-long-long --disable-multilib --enable-threads --disable-symvers
--build=i386-unknown-netbsdelf2.0. --host=alpha--netbsd --target=alpha--netbsd
Thread model: posix
gcc version 3.3.3 (NetBSD nb3 20040520)
Any ideas or any other information that would be helpful in diagnosing this?
Thanks,
!tr