From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: (file-error "writing to process" "bad address" #<process imap>) when Gcc-ing a group
Date: Mon, 09 Feb 2009 18:02:01 +0100 [thread overview]
Message-ID: <m2ab8vsfw6.fsf@randomsample.de> (raw)
In-Reply-To: <873aenr2gk.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Mon, 09 Feb 2009 17:37:31 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
> The local IMAP server hosting the Gcc-ed group is Dovecot v1.1.11. I'm
> not sure if part of the problem is on its side, but at least I can say
> that it has no problems when offlineimap synces big messages from my
> IMAP accounts to the local dovecot.
>
> When the Gcc-upload fails, dovecot logs a line like this:
>
> dovecot: Feb 09 17:14:51 Info: IMAP(uni): \
> Disconnected in APPEND bytes=1992955/1144675
>
> Could somebody please help me with this?
I'm using Dovecot (on a remote server, though) and don't have any
problems appending large messages using Gnus.
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?
If you cannot use IMAP debugging in Emacs, you can use the Dovecot's
"rawlog" utility: http://wiki.dovecot.org/Debugging/Rawlog . Maybe that
can shed some light on the issue.
-David
next prev parent reply other threads:[~2009-02-09 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:37 Tassilo Horn
2009-02-09 17:02 ` David Engster [this message]
2009-02-09 17:19 ` Tassilo Horn
2009-02-09 17:58 ` David Engster
2009-02-09 19:38 ` Tassilo Horn
2009-02-09 23:04 ` David Engster
2009-02-10 9:35 ` Tassilo Horn
2009-02-10 10:02 ` David Engster
2009-02-10 13:51 ` David Engster
2009-02-10 15:26 ` Tassilo Horn
2009-02-10 15:38 ` David Engster
2009-02-10 16:58 ` Tassilo Horn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ab8vsfw6.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).