Hi,

Yesterday I fell victim to the maildrop bouncing messages when MySQL was unavailable issue. While doing some db maintenance, I managed to hopelessly lock up MySQL.

The next thing I knew, Maildrop had bounced 7 legitimate messages before I shut down the MTA.

I've been using Maildrop 1.6.2, and am aware of Chris Master's patch for this issue, sent to the list on October 15.

I downloaded 1.6.3, but couldn't figure out how to get "patch" to automatically update the source from the diff file Chris sent. So I manually edited the source, and made the changes listed in the diff. But it wouldn't compile.

Can someone update this patch for 1.6.3, and explain how to apply it?

One other issue. I next tried to compile 1.6.3 as is, with exactly the same configure options as I'd used for 1.6.2:

./configure --enable-maildropldap --enable-maildropmysql \ --enable-maildirquota --enable-trusted-users="root dspamcgi mail"

I set the binary to setUID root, changed it to the ownership of the 1.6.2 version, but the new binary immediately started bouncing messages again with this in my maillog:

status=bounced (user unknown. Command output: Invalid user specified. 11176: [Fri Dec 5 11:46:21 2003] LDA returned error, exit code: 67, LDA command line: /usr/local/bin/maildrop -d ma...@freelock.com )

I get the same result when I pipe a mail into the binary from the command line. The user account is in MySQL, and none of the configuration settings have changed. Fortunately, replacing it with the previous binary restored my mail system.

So what has changed between 1.6.2 and 1.6.3 that would break mail delivery to MySQL users? I tried commenting out mailstatus_field in /etc/maildropmysql.config, but that just made both versions generate:

Invalid user specified.

when I piped messages through maildrop. The exact same message piped to the old version works again when I uncomment the mailstatus_field.

Thanks for your help...