From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: "no process" gnus bug when moving messages from nnml to imap folder
Date: Fri, 04 Feb 2011 12:02:45 -0600 [thread overview]
Message-ID: <8762szisoq.fsf@lifelogs.com> (raw)
In-Reply-To: <87bp2skwok.fsf@gnus.org>
On Fri, 04 Feb 2011 00:53:31 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> I've verified that putting a single NUL character into any mail and then
LI> trying to move it to Gmail will make Gmail hang up the connection.
LI> So the Gmail IMAP servers just aren't compliant -- the IMAP RFC says
LI> that all IMAP servers should be able to take binary data after APPEND, I
LI> seem to recall.
LI> The question is -- what should nnimap do about that? Introduce a
LI> "quirks mode" for Gmail that just strips all NUL characters?
I would ask the use how to treat the NULs, similarly to how Gnus asks
about unprintable characters in an outgoing e-mail.
Ted
next prev parent reply other threads:[~2011-02-04 18:02 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
2011-02-04 8:50 ` Giorgos Keramidas
2011-02-04 8:53 ` Lars Ingebrigtsen
2011-02-04 18:02 ` Ted Zlatanov [this message]
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=8762szisoq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).