Re: (file-error "writing to process" "bad address" #<process imap>) when Gcc-ing a group

[Tassilo Horn <tassilo@member.fsf.org>]

David Engster <deng@randomsample.de> writes:

Hi David,

> Does it also sometimes fail for smaller attachments?

Hm, at least I don't remember.  For big attachments it always fails.

> I just wonder if this is a size or timing issue.

I cannot tell, but bigger messages would increase the probability of
timing issues, so it's even harder to distinguish.

>>> Are you using the Gnus demon, e.g. for regularly checking your
>>> INBOX?  Could it be that the demon changes the mailbox while the
>>> APPEND is still running?
>>
>> No, I only run offlineimap in a cron job, but that shouldn't cause
>> any harm, right?
>
> The above error message from Dovecot says that the connection was
> closed during the APPEND. Offlineimap should not be able to do that (I
> stress "should").

I disabled the cron job, but still the APPEND fails.

>>> If you cannot use IMAP debugging in Emacs,
>>
>> I can.  See the logs I posted in that old message.
>
> Ah, OK. But could you enable imap-log instead of imap-debug? I always
> find the latter a bit hard to parse...

I can do that later, if the rawlog doesn't help.

> If there's nothing to see, the rawlog utility should tell you what
> happens before the connection gets closed.

See http://www.tsdh.de/~heimdall/dovecot.rawlog.tar.gz for zipped rawlog
directory.  I deleted all files in there and then sent the big mail, so
no irrelevant stuff is included.

In one file you can see the APPEND, then comes the message header and
body, followed by the base64 encoded attachment, or better part of it.
Then there's a NOOP and that's it.

Bye,
Tassilo