Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Gcc fails with "writing to process: bad address, imap"
Date: Thu, 30 Oct 2008 09:46:15 +0100	[thread overview]
Message-ID: <87k5bqv5bc.fsf@thinkpad.tsdh.de> (raw)

Hi all,

Whenever I attach a big file (1MB) to a mail the gcc to the local imap
group fails issuing the message in the subject.  It's sent out by the
SMTP server, though.

And afterwards, the connection the the imap server is hosed.  It shows
up as open in the server buffer, but hitting RET on it will freeze
emacs.  I interrupted with C-g and tried to close the connection with C.
But that freezes emacs, too.  So the only think I can do is killing
emacs.  Quitting Gnus freezes Emacs, I guess because it tries to close
the broken connection...

The imap server is a locally running dovecot (1.1.4).  I have two
accounts on it.  Only the account which holds the gcc-ed group is
broken.  The other one works normally.

(add-to-list 'gnus-secondary-select-methods
	     '(nnimap "Fastmail"
		      (nnimap-address "localhost")
		      (nnimap-stream network)
		      (nnimap-authenticator login)))

(add-to-list 'gnus-secondary-select-methods
	     '(nnimap "Uni"
		      (nnimap-address "localhost")
		      (nnimap-stream network)
		      (nnimap-authenticator login)))

Below are the relevant debug messages.  In that case, the Uni accound is
the broken one.  Please tell me if you need more.  The problem is
absolutely reproducible.

Gnus v5.13
GNU Emacs 23.0.60.1 (x86_64-pc-linux-gnu, GTK+ Version 2.14.4)
 of 2008-10-29 on thinkpad

That's what's in *Messages*.

--8<---------------cut here---------------start------------->8---
Sending...
The message size is too large, split? (y or n) 
Sending via mail...
220 deliver.uni-koblenz.de ESMTP Postfix
250-deliver.uni-koblenz.de
250-PIPELINING
250-SIZE 70000000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250 8BITMIME
250 Ok [2 times]
354 End data with <CR><LF>.<CR><LF>
250 Ok: queued as 095F6789A835
221 Bye
20081030T092829.578> nnimap: Updating info for nnimap+Uni:INBOX...
20081030T092829.701> nnimap: Updating info for nnimap+Uni:INBOX...done
ad-Orig-imap-send-command: writing to process: bad address, imap
--8<---------------cut here---------------end--------------->8---

That's what's in *nnimap-debug*:

--8<---------------cut here---------------start------------->8---
| 2 -> nnimap-possibly-change-group: group="INBOX" server="Uni"
| | 3 -> nnimap-possibly-change-server: server="Uni"
| | 3 <- nnimap-possibly-change-server: " *nnimap* Uni"
| 2 <- nnimap-possibly-change-group: "INBOX"
| 2 -> nnimap-before-find-minmax-bugworkaround: 
| 2 <- nnimap-before-find-minmax-bugworkaround: t
| 2 -> nnimap-find-minmax-uid: group="INBOX" examine=t
| 2 <- nnimap-find-minmax-uid: (594 1 872)
1 <- nnimap-request-group: t
======================================================================
1 -> nnimap-request-accept-article: group="INBOX" server="Uni" last=t
| 2 -> nnimap-possibly-change-server: server="Uni"
| 2 <- nnimap-possibly-change-server: " *nnimap* Uni"
--8<---------------cut here---------------end--------------->8---

And the same for *imag-debug*:

--8<---------------cut here---------------start------------->8---
| | 3 <- imap-message-map: (872 872)
| | 3 -> imap-mailbox-get: propname=exists mailbox=nil buffer=nil
| | 3 <- imap-mailbox-get: 594
| 2 -> imap-current-mailbox: buffer=" *nnimap* Uni"
| 2 <- imap-current-mailbox: "INBOX"
| 2 -> imap-mailbox-unselect: buffer=" *nnimap* Uni"
| | 3 -> imap-capability: identifier=UNSELECT buffer=nil
| | 3 <- imap-capability: (UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 STARTTLS AUTH=PLAIN)
| | 3 -> imap-send-command-wait: command="UNSELECT" buffer=nil
| | | 4 -> imap-send-command: command="UNSELECT" buffer=nil
| | | | 5 -> imap-send-command-1: cmdstr="186 UNSELECT"
| | | | 5 <- imap-send-command-1: nil
| | | 4 <- imap-send-command: 186
| | | 4 -> imap-wait-for-tag: tag=186 buffer=nil
| | | | 5 -> imap-arrival-filter: proc=#<process imap> string="186 OK Unselect completed.
"
| | | | | 6 -> imap-find-next-line: 
| | | | | 6 <- imap-find-next-line: 29
| | | | | 6 -> imap-parse-response: 
| | | | | | 7 -> imap-parse-resp-text: 
| | | | | | | 8 -> imap-parse-resp-text-code: 
| | | | | | | 8 <- imap-parse-resp-text-code: nil
| | | | | | 7 <- imap-parse-resp-text: nil
| | | | | 6 <- imap-parse-response: nil
| | | | | 6 -> imap-find-next-line: 
| | | | | 6 <- imap-find-next-line: nil
| | | | 5 <- imap-arrival-filter: nil
| | | 4 <- imap-wait-for-tag: OK
| | 3 <- imap-send-command-wait: OK
| 2 <- imap-mailbox-unselect: t
| 2 -> imap-message-append: mailbox="INBOX" article=#<buffer  *acc*> flags=nil date-time=nil buffer=" *nnimap* Uni"
| | 3 -> imap-send-command-wait: command=("APPEND \"" "INBOX" "\" " #<buffer  *acc*>) buffer=nil
| | | 4 -> imap-send-command: command=("APPEND \"" "INBOX" "\" " #<buffer  *acc*>) buffer=nil
| | | | 5 -> imap-send-command-1: cmdstr="187 APPEND \"INBOX\" {2187179}"
| | | | 5 <- imap-send-command-1: nil
| | | | 5 -> imap-wait-for-tag: tag=187 buffer=nil
| | | | | 6 -> imap-arrival-filter: proc=#<process imap> string="+ OK
"
| | | | | | 7 -> imap-find-next-line: 
| | | | | | 7 <- imap-find-next-line: 7
| | | | | | 7 -> imap-parse-response: 
| | | | | | 7 <- imap-parse-response: "OK"
| | | | | | 7 -> imap-find-next-line: 
| | | | | | 7 <- imap-find-next-line: nil
| | | | | 6 <- imap-arrival-filter: nil
| | | | 5 <- imap-wait-for-tag: INCOMPLETE
--8<---------------cut here---------------end--------------->8---
-- 
Richard Stallman  doesn't use web  browsers. Emacs connects  directly to
the network driver and he reads and writes TCP/IP himself.



             reply	other threads:[~2008-10-30  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  8:46 Tassilo Horn [this message]
2008-10-30  8:58 ` Tassilo Horn
2008-10-30 11:20   ` Andreas Seltenreich
2008-10-30 11:36     ` Tassilo Horn
2008-10-30 12:12       ` Andreas Seltenreich
2008-10-30 15:41         ` Tassilo Horn
2008-10-30 23:40 ` Jason Riedy

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=87k5bqv5bc.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).