From: "Adam Sjøgren via info-gnus-english" <info-gnus-english@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: fcc with nnml mail spool
Date: Sun, 25 Jul 2021 23:09:07 +0200 [thread overview]
Message-ID: <87zguagky4.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87bl6qunu5.fsf@gnu.org>
Roland writes:
> How can one achieve the same thing with the nnml mail spool?
I use the archiving functionality in Gnus for this. It adds a
(Gnus-specific) header to news articles like this:
Gcc: nnml+archive:news-2021
For email I have configured it to add this:
Gcc: nnml+archive:news-2021
I have set gnus-message-archive-method in .gnus to this:
'(nnml "archive"
(nnml-directory "~/Mail/archive")
(nnml-active-file "~/Mail/archive/active")
(nnml-get-new-mail nil)
(gnus-search-engine gnus-search-notmuch)
(nnml-inhibit-expiry t))
and then I have:
(setq gnus-message-archive-group
'((if (message-news-p)
(concat "news-" (format-time-string "%Y"))
(concat "mail-" (format-time-string "%Y")))))
which does the {news,mail}-{year} part.
I also set gnus-gcc-mark-as-read to t, because I want the archived
messages to be marked as read automatically.
(I guess you could just set your archive method to be your regular
nnml-method - I'm not sure why I split them back in ancient times.)
I hope this helps!
Best regards,
Adam
--
'It's pulled, and it's fine, but there's clearly a Adam Sjøgren
balance between "octopus merges are fine" and asjo@koldfront.dk
"Christ, that's not an octopus, that's a Cthulhu
merge".'
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-07-25 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 20:42 Roland Winkler
2021-07-25 21:09 ` Adam Sjøgren via info-gnus-english [this message]
2021-07-25 21:11 ` Adam Sjøgren via info-gnus-english
2021-07-26 1:43 ` Roland Winkler
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=87zguagky4.fsf@tullinup.koldfront.dk \
--to=info-gnus-english@gnu.org \
--cc=asjo@koldfront.dk \
/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).