From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
emacs-devel@gnu.org, cyd@stupidchicken.com, rms@gnu.org,
ams@gnu.org
Subject: Re: Recognize mbox files?
Date: Wed, 11 Feb 2009 20:59:20 -0500 [thread overview]
Message-ID: <jwvy6wca02s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <umycsybff.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 11 Feb 2009 22:18:44 +0200")
>> > I normally use *.xmail for these files.
>> > I think others use *.mbox.
>> > But the general idea would work.
>>
>> As long as Rmail munges the file without asking
> It just adds one or two X-SOMETHING headers, that's all.
The problem is if this detection is not 100% reliable, this may actually
have a serious consequence, especially if you don't notice it.
>> Otherwise, Rmail will have to be considered risky for use by mail
>> admins.
> Heh, what it does nowadays is nothing compared with what it did before
> the mbox merge: it would convert the file to Babyl! How's that for
> ``risky''?
But *when* did it do it? Would it do it, just by C-x C-f <somemboxfile> RET?
Stefan
next prev parent reply other threads:[~2009-02-12 1:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 18:38 Recognize mbox files? Alfred M. Szmidt
2009-02-10 1:34 ` Stefan Monnier
2009-02-10 9:36 ` Eli Zaretskii
2009-02-10 20:02 ` Richard M Stallman
2009-02-11 0:34 ` Chetan Pandya
2009-02-11 20:58 ` Richard M Stallman
2009-02-11 4:51 ` Stephen J. Turnbull
2009-02-11 20:18 ` Eli Zaretskii
2009-02-12 1:59 ` Stefan Monnier [this message]
2009-02-12 4:09 ` Eli Zaretskii
2009-02-12 5:15 ` Stefan Monnier
2009-02-12 2:40 ` Stephen J. Turnbull
2009-02-11 20:59 ` Richard M Stallman
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 16:57 Alfred M. Szmidt
2009-02-17 23:55 Xavier Maillard
2009-02-17 23:55 Xavier Maillard
2009-02-17 15:27 Alfred M. Szmidt
2009-02-17 16:36 ` Stefan Monnier
2009-02-18 3:27 ` Stephen J. Turnbull
2009-02-18 3:39 ` Miles Bader
2009-02-18 4:18 ` Stephen J. Turnbull
2009-02-18 12:10 ` Richard M Stallman
2009-02-18 12:09 ` Richard M Stallman
2009-02-17 13:10 Alfred M. Szmidt
2009-02-17 14:17 ` Stephen J. Turnbull
2009-02-18 12:10 ` Richard M Stallman
2009-02-16 16:12 Alfred M. Szmidt
2009-02-17 12:13 ` Richard M Stallman
2009-02-14 21:52 Alfred M. Szmidt
2009-02-14 21:25 Xavier Maillard
2009-02-14 22:51 ` Stefan Monnier
2009-02-16 15:40 ` Richard M Stallman
2009-02-14 21:25 Xavier Maillard
2009-02-13 8:25 Alfred M. Szmidt
2009-02-12 8:16 Alfred M. Szmidt
2009-02-13 6:33 ` Richard M Stallman
2009-02-12 7:45 Alfred M. Szmidt
2009-02-10 7:36 Alfred M. Szmidt
2009-02-09 5:31 Richard M Stallman
2009-02-09 18:17 ` Chong Yidong
2009-02-09 19:09 ` Harald Hanche-Olsen
2009-02-09 21:26 ` Reiner Steib
2009-02-09 22:06 ` Eli Zaretskii
2009-02-09 22:35 ` Reiner Steib
2009-02-10 8:34 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvy6wca02s.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ams@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stephen@xemacs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).