Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: (file-error "writing to process" "bad address" #<process imap>) when Gcc-ing a group
Date: Mon, 09 Feb 2009 17:37:31 +0100	[thread overview]
Message-ID: <873aenr2gk.fsf@thinkpad.tsdh.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]

Hi all,

some time ago (message <87k5bqv5bc.fsf@thinkpad.tsdh.de> on ding) I had
problems when sending mails with big attachments (> 1 MiB or so).  To be
precise, the sending via SMTP works just fine, but I get the error from
the subject when Gnus tries to upload the message to my local IMAP
server because of the Gcc header.

In the thread starting with <87k5bqv5bc.fsf@thinkpad.tsdh.de> I said
that turning off imap logging (nnimap-debug, imap-log, imap-debug all
set to nil) solves the issue for me, but sadly that's not true.

I still get that error and for me its perfectly reproducible.  Here's an
example backtrace.

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (file-error "writing to process" "bad address" #<process imap>)
  process-send-region(#<process imap> 1 8337045)
  imap-send-command(("APPEND \"" "INBOX" "\" " #<buffer  *acc*>) nil)
  imap-send-command-wait(("APPEND \"" "INBOX" "\" " #<buffer  *acc*>))
  imap-message-append("INBOX" #<buffer  *acc*> nil nil " *nnimap* Uni")
  nnimap-request-accept-article("INBOX" "Uni" t)
  gnus-request-accept-article("nnimap+Uni:INBOX" "nnimap:Uni" t t)
  gnus-inews-do-gcc()
  gnus-agent-possibly-do-gcc()
  run-hooks(message-sent-hook)
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit nil nil)
--8<---------------cut here---------------end--------------->8---

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?

Bye,
Tassilo

Gnus v5.13
GNU Emacs 23.0.90.1 (x86_64-pc-linux-gnu, GTK+ Version 2.14.7)
 of 2009-02-08 on thinkpad
200 cache.uni-koblenz.de InterNetNews NNRP server INN 2.4.2 ready (posting ok).


[-- Attachment #2: User settings --]
[-- Type: application/emacs-lisp, Size: 12882 bytes --]

             reply	other threads:[~2009-02-09 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 16:37 Tassilo Horn [this message]
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
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=873aenr2gk.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --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).