Re: error when getmail calls maildrop
On Sat, Aug 01, 2015 at 01:47:11PM -0500, rlharris@oplink.net wrote:
> This post to debian-user concerns the same problem which I described
> in a recent post to the getmail list. This posting provides greater
> detail.
I couldn't find a similar e-mail in the getmail mailing list archives:
https://marc.info/?l=getmail
Perhaps you were referring to this thread on the maildrop one?
http://markmail.org/message/527fsm7albpvmh6x
If so, was your question answered successfully? It looks like an
entirely different question, but one which depends on your maildrop
setup being in basically working order.
On Sat, Aug 01, 2015 at 01:47:11PM -0500, rlharris@oplink.net wrote:
> THE PROBLEM: getmail sees the messages but cannot pass them to
> maildrop. The getmail log reports an error, but nothing is written to
> the maildrop log. The log files are extant; they are located in:
> ~/mail/logs/getmail ~/mail/logs/maildrop.
>
> The error message is:
> ----------------------------
> 2015-08-01 04:07:47 Delivery error (command maildrop 3808 error (75,
> /usr/bin/maildrop: Unable to open mailbox.))
>
> 2015-08-01 04:07:47 msg 2/1373 (16327 bytes) msgid 000007da53c4329f
> from <SRS0+e50bb6a0873f79ec=B6=cs.foobar.com=bounce@mx25.net>
>
> 2015-08-01 04:07:47 2 messages (47056 bytes) retrieved, 0 skipped
> ----------------------------
>
> The set of maildirs is extant; they were created with the command:
> mkdir -vp /path/new-maildir-name/{cur,new,tmp}
I grepped the maildrop source code, and it looks like the string "Unable
to open mailbox" only turns up in two places. Both are within a logical
branch which depends on the destination being a mailbox file, as opposed
to a Maildir, which doesn't seem to jive with what you are attempting to
do.
On Sat, Aug 01, 2015 at 01:47:11PM -0500, rlharris@oplink.net wrote:
> As a test, I changed the [destination] from
> ----------------------------
> type = MDA_external
> path = /usr/bin/maildrop
> unixfrom = true
> ----------------------------
> to
> ----------------------------
> type = Maildir
> path = /home/rh/maildir-test/
> ----------------------------
> With this change, message delivery takes place without error.
Maybe another test could be to replace the contents of ~/.mailfilter
with:
DEFAULT="/home/rh/maildir-test/"
And then see if delivery takes place without error. If it does, perhaps
you could post some snippets of your real ~/.mailfilter and we could go
from there.
Reply to: