From: Iain Parris <ipv2.lst@parris.org>
To: Robert Winkler <robert.winkler.mail@gmail.com>
Cc: The Sup email client <supmua@googlegroups.com>
Subject: Re: [sup] SpamAssassin (Spam/Ham) support for Sup
Date: Wed, 08 Jul 2020 19:53:19 +0100 [thread overview]
Message-ID: <1594233819-sup-5407@ceres> (raw)
In-Reply-To: <5048bacc-c026-45c3-b145-52226916491co@googlegroups.com>
Hi Robert,
Excerpts from Robert Winkler's message of 2020-07-08 10:06:55 -0700:
> Thanks, Good hint, Iain!
Thank you!
> I want to move the mails in a second step (yet to be resolved).
>
> Any hints on possible external programs/ scripts for moving mails with a
> particular label to a special /Maildir folder (e.g.
> ~/Maildir/SpamAssassin/Spam)?
Question: do the mails need to be moved, or can they be copied?
(Side note: Sup should de-duplicate copies of mails that appear in more
than one source, i.e., should recognise that it is a duplicate of the
same message, and not show it twice. Or for simplicity, don't tell Sup
to index the SpamAssassin Maildirs!)
If making a copy is sufficient, then you can write the email to a new
file in the appropriate Maildir (since a Maildir is just a collection of
files, with each file being one email). All you need is a random
filename. For example, you could pipe to cat to create with a random
filename (a UUID), using something like:
cat >~/Maildir/SpamAssassin/Spam/$(cat /proc/sys/kernel/random/uuid)
Kind regards,
Iain
next prev parent reply other threads:[~2020-07-08 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 18:36 Robert Winkler
2020-07-06 23:27 ` [sup] " Iain Parris
2020-07-08 17:06 ` Robert Winkler
2020-07-08 18:53 ` Iain Parris [this message]
2020-07-09 22:20 ` Robert Winkler
2020-07-10 20:26 ` Iain Parris
2020-07-10 20:29 ` Iain Parris
2020-07-10 21:58 ` Robert Winkler
2020-07-11 13:48 ` Iain Parris
2020-07-24 10:38 ` Robert 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=1594233819-sup-5407@ceres \
--to=ipv2.lst@parris.org \
--cc=robert.winkler.mail@gmail.com \
--cc=supmua@googlegroups.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