Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@mit.edu>
Subject: Re: what mail source nnml correspond?
Date: Wed, 17 Aug 2005 12:06:58 -0400	[thread overview]
Message-ID: <y68acjgbl99.fsf@mint-square.mit.edu> (raw)
In-Reply-To: <ddvi5q$84t$1@mail.cn99.com>

xFire <all_is_free@hotmail.com> writes:

> i mean how to read the nnml dirctory with other mail back end?

The one disadvantage of nnml is that Gnus is the only program that
uses it.  It's very similar to other file-per-message backends, like
maildir and MH, though, and you can look at the nnml directory and
read the messages directly outside of Emacs (heresy!).  The big
difference is a file called .overview that contains the information
needed for the summary buffer; this means that nnml is "fast" because
it only needs to read the .overview file and not dig through
individual messages.

I do sometimes dig through the files directly if I need something
quickly and starting Emacs is too much of a pain (heresy!).  grepping
the .overview file will give me a message number, and then I can cat
that file directly.

Since you mentioned "mail source" in the message line, it's also worth
mentioning that if you're using nnml you're probably pulling mail off
of your mail server, and it's gone from there.  If you have an IMAP
mail source you can configure it to not delete messages (see
:fetchflag in info://gnus/Mail+Source+Specifiers).  For POP3 it's
harder but asked often enough that Google should be able to tell you.

HTH,

  --dzm


  reply	other threads:[~2005-08-17 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 14:23 xFire
2005-08-17 16:06 ` David Z Maze [this message]
2005-08-18  4:03   ` xFire
2005-08-18 14:46     ` David Z Maze
2005-08-18 23:16 ` xFire
2005-08-19  6:26   ` Martin Monsorno

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=y68acjgbl99.fsf@mint-square.mit.edu \
    --to=dmaze@mit.edu \
    /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).