Gnus development mailing list
 help / color / mirror / Atom feed
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 00:04:56 +0100	[thread overview]
Message-ID: <87y6wf43fr.fsf@randomsample.de> (raw)
In-Reply-To: <87ab8v7651.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Mon, 09 Feb 2009 20:38:18 +0100")

Tassilo Horn <tassilo@member.fsf.org> writes:
>> 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.

I tried it again at home over my slow DSL line, and now the exact same
thing happens here. I enabled all logs and used tcpdump to record the
traffic to the IMAP server, but to no avail. The imap-log doesn't help
since the buffer which is sent to the IMAP server is simply included
there before process-send-region is called.

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). It'd be interesting to know if
the problem also occurs in Emacs 22. Maybe I have time over the weekend
to test this further...

-David



  reply	other threads:[~2009-02-09 23:04 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 [this message]
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=87y6wf43fr.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).