From: Giorgos Keramidas <gkeramidas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: "no process" gnus bug when moving messages from nnml to imap folder
Date: Thu, 24 Feb 2011 12:59:31 +0100 [thread overview]
Message-ID: <xeia39nd8wyk.fsf@kobe.laptop> (raw)
In-Reply-To: <xeiawrlbhefm.fsf@kobe.laptop> (Giorgos Keramidas's message of "Mon, 07 Feb 2011 10:45:01 -0800")
On Mon, 07 Feb 2011 10:45:01 -0800, Giorgos Keramidas <gkeramidas@gmail.com> wrote:
> On Mon, 07 Feb 2011 03:42:16 -0800, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>>Giorgos Keramidas <gkeramidas@gmail.com> writes:
>>> Completion offers both `nnimap:gmail' and `nnimap:imap.gmail.com' as a
>>> valid `B c' destination, but they both respond that the newly created
>>> imap buffer has no connection when I move or copy messages from an nnml
>>> source folder.
>>
>> These are just two names for the same server, probably.
>>
>>> Whatever the problem is with `B c' and `B m' it seems specific to using
>>> an imap folder as the destination of the messages.
>>
>> No, as I said previously, it's a bug in Gmail. It fails when accepting
>> articles that contain NULs. I've now added a quirk for this in nnimap.
>
> Ok, thanks. Is the quirk in the bzr repo? If yes, my daily fetch from
> the git mirror will pick it up and I'll give it a spin again :)
Ok, I've rebuilt Emacs and Gnus from a later version [GNU Emacs
24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.20.1) of 2011-02-11
on gkeramidas-glaptop].
It still fails to copy my old archived messages to Gmail imap, though.
The message that fails this time is (copied straight from my nnml folder
file at `~/mail/mail/archive/2001/3138'):
http://people.freebsd.org/~keramida/3138.nnml
When I try to 'B c' this message to `nnimap+gmail:archive/2001' Gnus
fails to copy the message, but there are no NUL bytes in the message
itself.
So as an experiment I saved this message typing `O m' to `~/foo.mbox'
and used Mutt to copy the same message to:
imaps://gkeramidas@imap.gmail.com/archive/2001
and the copy worked fine. So I'm not sure if there's something wrong
with the message. There's definitely something wrong with Gnus when I
try to open a local nnml groupand send messages to imap though.
next prev parent reply other threads:[~2011-02-24 11:59 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
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 [this message]
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=xeia39nd8wyk.fsf@kobe.laptop \
--to=gkeramidas@gmail.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--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).