Gnus development mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Giorgos Keramidas <gkeramidas@gmail.com>
Cc: larsi@gnus.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: "no process" gnus bug when moving messages from nnml to imap	folder
Date: Fri, 04 Feb 2011 10:38:57 +0200	[thread overview]
Message-ID: <83d3n8b3dq.fsf@gnu.org> (raw)
In-Reply-To: <xeiaipx0iz0a.fsf@kobe.laptop>

> From: Giorgos Keramidas <gkeramidas@gmail.com>
> Date: Thu, 03 Feb 2011 13:33:57 -0800
> Cc: ding@gnus.org, emacs-devel@gnu.org
> 
> On Thu, 03 Feb 2011 13:00:45 -0800, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> > I've verified that I can reproduce the error, but I'm not quite sure
> > what the solution is.  The message is really corrupt (ending in a lot of
> > NUL characters), and Gmail just seems to close its connection.  Does
> > their IMAP server segfault?  I have no idea.
> >
> > Moving the same message to a Dovecot server works perfectly, so it seems
> > likely that it's just another shoddy Google product.
> >
> > Obviously the error message in this case would be better than a
> > backtrace, and I'll fix that at least.
> >
> > If anyone has any input on whether Gnus should try to, er, encode the
> > message in some way before pushing it to Gmail, I'm all ears.
> 
> I think there are two slightly related problems at work here.  One of
> them is that Gmail disconnects after we send NUL characters so we can't
> move the message and we throw a backtrace.

Don't some network-related functions return null characters if you try
to read from a socket after the connection is closed?



  parent reply	other threads:[~2011-02-04  8:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <xeia1v3p8n5p.fsf@kobe.laptop>
     [not found] ` <8762t1dww9.fsf@gnus.org>
     [not found]   ` <xeia62t0x4f7.fsf@kobe.laptop>
     [not found]     ` <871v3orhhw.fsf@gnus.org>
     [not found]       ` <xeiavd10j1ug.fsf@kobe.laptop>
2011-02-03 21:00         ` Lars Ingebrigtsen
2011-02-03 21:33           ` Giorgos Keramidas
2011-02-03 21:39             ` Giorgos Keramidas
2011-02-03 21:42               ` Giorgos Keramidas
2011-02-04  8:38             ` Eli Zaretskii [this message]
2011-02-04  8:50               ` Giorgos Keramidas
2011-02-04  8:53               ` Lars Ingebrigtsen
2011-02-04 18:02                 ` Ted Zlatanov
2011-02-04 18:08                   ` Lars Ingebrigtsen
2011-02-04 18:28                     ` Ted Zlatanov
2011-02-04 19:14                       ` Lars Ingebrigtsen
2011-02-04 19:26                         ` Ted Zlatanov
2011-02-07 10:49                           ` Lars Ingebrigtsen
2011-02-04  8:58             ` Lars Ingebrigtsen
2011-02-04 18:23               ` Giorgos Keramidas
2011-02-07 11:42                 ` Lars Ingebrigtsen
2011-02-07 18:45                   ` Giorgos Keramidas
2011-02-14  3:09                     ` Lars Ingebrigtsen
2011-02-24 11:59                     ` Giorgos Keramidas
2011-02-25  4:53                       ` Lars Ingebrigtsen

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=83d3n8b3dq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=gkeramidas@gmail.com \
    --cc=larsi@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).