From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68261 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.gnus.general Subject: Re: (file-error "writing to process" "bad address" #) when Gcc-ing a group Date: Mon, 09 Feb 2009 20:38:18 +0100 Message-ID: <87ab8v7651.fsf@thinkpad.tsdh.de> References: <873aenr2gk.fsf@thinkpad.tsdh.de> <87tz73plyd.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1234208379 9774 80.91.229.12 (9 Feb 2009 19:39:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 9 Feb 2009 19:39:39 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M16701@lists.math.uh.edu Mon Feb 09 20:40:52 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LWbzo-00082M-JK for ding-account@gmane.org; Mon, 09 Feb 2009 20:40:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1LWbxc-0005Hf-1X; Mon, 09 Feb 2009 13:38:28 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LWbxa-0005HK-JI for ding@lists.math.uh.edu; Mon, 09 Feb 2009 13:38:26 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LWbxX-00088V-IL for ding@lists.math.uh.edu; Mon, 09 Feb 2009 13:38:26 -0600 Original-Received: from out1.smtp.messagingengine.com ([66.111.4.25]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LWbxr-0001zf-00 for ; Mon, 09 Feb 2009 20:38:43 +0100 Original-Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id E59FB28FFD6 for ; Mon, 9 Feb 2009 14:38:21 -0500 (EST) Original-Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 09 Feb 2009 14:38:21 -0500 X-Sasl-enc: KKVQo2lVJ3xlO3izhUGOgleAsJqW+7z6sABHN5SIYdMi 1234208301 Original-Received: from thinkpad.tsdh.de (p54AF2BAE.dip0.t-ipconnect.de [84.175.43.174]) by mail.messagingengine.com (Postfix) with ESMTPA id 0C0C630DEA for ; Mon, 9 Feb 2009 14:38:20 -0500 (EST) In-Reply-To: (David Engster's message of "Mon, 09 Feb 2009 18:58:05 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.90 (gnu/linux) Mail-Copies-To: never Mail-Followup-To: ding@gnus.org X-Spam-Score: -3.6 (---) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68261 Archived-At: David Engster writes: Hi David, > Does it also sometimes fail for smaller attachments? Hm, at least I don't remember. For big attachments it always fails. > I just wonder if this is a size or timing issue. I cannot tell, but bigger messages would increase the probability of timing issues, so it's even harder to distinguish. >>> 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? >> >> No, I only run offlineimap in a cron job, but that shouldn't cause >> any harm, right? > > The above error message from Dovecot says that the connection was > closed during the APPEND. Offlineimap should not be able to do that (I > stress "should"). I disabled the cron job, but still the APPEND fails. >>> If you cannot use IMAP debugging in Emacs, >> >> I can. See the logs I posted in that old message. > > Ah, OK. But could you enable imap-log instead of imap-debug? I always > find the latter a bit hard to parse... I can do that later, if the rawlog doesn't help. > 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. Bye, Tassilo