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:28:43 -0600 [thread overview]
Message-ID: <87wrlfhcx0.fsf@lifelogs.com> (raw)
In-Reply-To: <87oc6r3c5z.fsf@gnus.org>
On Fri, 04 Feb 2011 10:08:40 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I would ask the use how to treat the NULs, similarly to how Gnus asks
>> about unprintable characters in an outgoing e-mail.
LI> But only for Gmail servers, I guess? None of the other I've tried seem
LI> to have any problems with NULs.
Sure. It may not work to autodetect gmail.com with Google Apps, if
those support the IMAP access, since they run under another domain name.
Can someone knowledgeable about that comment? If my suspicion is right,
it would have to be a backend slot variable.
Ted
next prev parent reply other threads:[~2011-02-04 18:28 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 [this message]
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=87wrlfhcx0.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).