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: Tue, 10 Feb 2009 11:02:54 +0100 [thread overview]
Message-ID: <kzocxay5gx.fsf@randomsample.de> (raw)
In-Reply-To: <87fxim8wi9.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Tue, 10 Feb 2009 10:35:42 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
> David Engster <deng@randomsample.de> writes:
>> I have no idea if this is a problem with Dovecot or maybe a bug in
>> process-send-region or in send-region (I don't see how any other Gnus
>> or Emacs code could be involved in this).
>
> `send-region' is only an alias for `process-send-region'.
Sorry, I should have said "send-region in process.c". The file-error is
thrown there, in the C source.
> Maybe we could create an isolated test case which doesn't involve gnus
> and dovecot. I tried to create such a case, but I don't have enough
> time right now. Basically it should be possible to load a big file
> into a temp buffer and use it as input to a `cat' process, or
> something like that and then compare if the result equals the input.
I'd be surprised if the error is that general; much more people would
have to see it in this case. I just tried again at work, and here it
doesn't cause any problems, even with a 10MB attachment. I know you're
getting the error while posting to a local IMAP server, but in my case
it looks like a speed/timing issue.
-David
next prev parent reply other threads:[~2009-02-10 10: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
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 [this message]
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=kzocxay5gx.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).