On Thu, Oct 06, 2005 at 05:36:46PM -0700, Daniel Burrows wrote:
> Package: maildrop
> Version: 1.5.3-2
> Severity: normal
>
> Maildrop randomly and mysteriously fails to deliver some messages. I
> have attached a specimin and my .mailfilter file. In this case, message
> delivery fails as follows:
>
> [EMAIL PROTECTED]:/tmp$ maildrop < 1128616898.8306_5.jester\:2\,S && echo
> true || echo false
> maildrop: error writing to mailbox.
> maildrop: Unable to deliver to mailbox.
> false
>
> The log file contains the following stanza:
>
> Date: Thu Oct 6 09:48:15 2005
> From: Nigel Cunningham <[EMAIL PROTECTED]>
> Subj: Re: [Suspend2-users] Log file does not generate in
> !Err: |/usr/bin/lbdb-fetchaddr
> (13128)
>
> So the error occurs trying to pipe the message to lbdb-fetchaddr.
> However, if I feed the message into lbdb-fetchaddr by hand, everything
> works fine -- indeed, if I replace lbdb-fetchaddr with "/bin/true", I
> get the same response. So the problem is not that lbdb-fetchaddr fails;
> something is going wrong inside maildrop while it tries to deliver to
> lbdb-fetchaddr.
I tried this with maildrop 2.0.2 (from unstable) now, but it works fine.
Looking at the 1.5.3 code, the same write error can occur if any of
mio.write(), mio.flush(), and fsync(mio.fd()) die in maildrop/formatmbox.C.
The same code remains in 2.0.2. Can you reproduce the bug with the new
version?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
