From: hput <hputn3@zohomail.com>
To: ding@gnus.org
Subject: make gnus split only /var/spool/mail/USER
Date: Mon, 29 Nov 2021 21:45:11 -0500 [thread overview]
Message-ID: <87mtlms6o8.fsf@local.lan> (raw)
This is being resent... the previous attempt with headers as below
seems not to have reached the group.
,----
| From: hput <hputn3@zohomail.com>
| Subject: make gnus split only /var/spool/mail/USER
| Newsgroups: gmane.emacs.gnus.general
| Date: Sun, 21 Nov 2021 11:09:48 -0500 (1 week, 1 day, 10 hours ago)
| Message-ID: <8735nplcc3.fsf@local.lan>
`----
So a second attempt below:
First, sorry to blabber and wonder as below but finding it difficult to
say what I'm after briefly.
I've been using the following `sources' setup to have gnus deliver
mail from /var/spool/mail/USER and procmail created mbox style mail
/spool/in/ ... mbox style groups with *.in suffix
(setq mail-sources
'((file :path "/var/spool/mail/reader")
(directory :path "/spool/in/"
:suffix ".in")))
So procmail does the heavy work and gnus only delivers *.in mboxes to
similarly named nnml groups.
All good so far.
I'd like to have gnus split `file :path "/var/spool/mail/USER"'
but continue delivering the `name.in' mboxes as it now does.
I haven't been able to google up an example of such a thing.
I'm guessing it would be something like:
(setq mail-sources
'((file :path "/var/spool/mail/USER"))
SPLITTING code here .. connected to only
`this mail-sources')
Using larsi's example here but don't know how to connect it only to
the mail-souces above :
(setq nnmail-split-methods
'(("mail.cron" "^From:.*Cron Daemon")
("mail.NOTcron" "")))
But cut down for my use and connected to above `mail-sources'.
Or something like that. . . . .
------- ------- ---=--- ------- -------
How to connect `mail-sources' and `nnmail-split-methods' above
But still have the delivery code below not be run thru splitting.
(setq mail-sources
'((directory :path "/spool/in/"
:suffix ".in")))
NO SPLITTING HERE
reply other threads:[~2021-11-30 16:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mtlms6o8.fsf@local.lan \
--to=hputn3@zohomail.com \
--cc=ding@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).