Hello,

Recently I started to get signal 0x19 when trying to deliver using maildrop (it worked before ;-). I am using maildrop for making copies of sent messages, so I have in /var/qmail/alias/.qmail-msglog:

# This alias control file is processed on EVERY SINGLE message. # ***THINK*** before you do this as it can put extra load on your system. # # Several things can be done here: # 1. Record EVERY single message in a mailbox file. # *** ARE YOU SURE YOU ***REALLY*** WANT TO RECORD EVERY SINGLE MESSAGE!!!??? # EXAMPLE: #./msglog # # 2. Record Message-IDs for later tracking. # EXAMPLE: #| awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]-/ { print }' # | maildrop -d vpopmail

My maildrop binary is setuid root. /etc/maildroprc contains just lines like:

if (/^From:.*use...@domain.com/) to /home/vpopmail/domains/domain.com/backup/Maildir/.user1.Sent if (/^From:.*use...@domain.com/) to /home/vpopmail/domains/domain.com/backup/Maildir/.user2.Sent

It has no default delivery or smth, just pairs of lines like that. The problem is, some messages are delivered, and some are not. What could be a problem?

I searched google and found out that signal 0x19 can occur if maildrop's log file is over 50 MB, but I don't have logging enabled; also that optimizations over -O2 are dangerous, but I tried even with -O0. My system is Fedora Core 2, tried a few last maildrop versions, including latest devel. I configure it with --enable-trusted-users='alias'.

Regards, Nerijus