From: Steven L Baur <steve@miranova.com>
Subject: Re: M-g and nnmail-spool-file
Date: 22 Jan 1996 14:40:59 -0800 [thread overview]
Message-ID: <m2ka2jg8ec.fsf@miranova.com> (raw)
In-Reply-To: Kai Grossjohann's message of 22 Jan 1996 02:05:05 -0800
>>>>> "Kai" == Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de> writes:
Kai> I use sgnus-0.29 on Emacs 19.30. When I enter a group and do a M-g
Kai> from the Summary buffer, mail is read from the files in
Kai> nnmail-spool-file and added to the current group. I would expect
Kai> nnmail-spool-file not to be read at all, but if it is read, I would
Kai> expect the mail to go to mail.misc (or somewhere else, according to
Kai> nnmail-split-methods).
Kai> My setup: nnmail-spool-file is a list, nnmail-use-procmail is set to
Kai> t, nnmail-split-methods is (("mail.misc" "")).
Kai> Things have been this way for a LONG time now, since the time of
Kai> (ding) Gnus.
Kai> Anybody seen this, too?
One man's bug is another man's feature. I need and use this feature.
As an example:
If you have nnml groups nnml:pgp and nnml:alt.security.pgp and long
filenames. Gnus will erroneously take messages alt.security.pgp.spool
and put them in nnml:pgp. This is a bug.
The only way to get messages from alt.security.pgp.spool to go into
nnml:alt.security.pgp.spool is to M-g on the group name.
Basically whenever you have a procmail spool file named
some.miscellaneous.group.name.spool, and nnml group
nnml:some.miscellaneous.group.name.spool, then collected mail from the
spool file should go into the exact name match rather than to
nnml:name, or some such.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
next prev parent reply other threads:[~1996-01-22 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-22 10:05 Kai Grossjohann
1996-01-22 22:40 ` Steven L Baur [this message]
1996-01-24 13:37 ` Kai Grossjohann
1996-01-25 20:08 ` Lars Magne 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=m2ka2jg8ec.fsf@miranova.com \
--to=steve@miranova.com \
/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).