Re: SIGABRT on fetching mail
Charles Cazabon <[email protected]>
| Newsgroups | gmane.mail.getmail.user |
|---|---|
| Message-ID | <[email protected]> |
Peter Nabbefeld <[email protected]> wrote: > > I'm usually running getmail sufficiently with dovecot for some months, > but now it seems some message is blocking my chain again, causing SIGABRT: > SimpleIMAPSSLRetriever:[email protected]@imap.gmx.net:993: > msg 1/1 (38176 bytes) delivered, deleted > getmailrc: operation error (child pid 2995 killed by signal 6) The *child* was killed by SIGABRT, which happens when it calls abort(3). That child has to be your dovecot `deliver` process; you don't have any other external programs invoked in your config: > destination: MDA_external(allow_root_commands="False", > arguments="('-e', '-d', '[email protected]')", command="deliver", > How can I find out, *which* message is blocking? Probably I can just > drop it, if I know ... It isn't getmail having a problem with the message. Try looking in the logs for the deliver command to find out why it's killing itself messily. If it is just some message content it doesn't like, those logs might give you a clue as to the content, so you can delete the message in your web client. Another possibility would be to temporarily change your delivery method to getmail's native maildir, so it bypasses dovecot entirely. Once you have the problematic message, you can switch back. Charles -- ----------------------------------------------------------------------- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ -----------------------------------------------------------------------