You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2018. It is now read-only.
I've never bothered training my spam filter. If you think it's worth having those features, I can look into integrating them (of course PRs are also welcome :))
Yes I believe it is worth to train your rspamd. Eventually #61 will take care of the training with imap_sieve.
But as far as I understand it, this only works for new mail moved to the Junk mailbox. For the initial import you'd still have to resort to using the command line. And for this maybe a wiki page would be nice. You planned on putting the big readme.md into the wiki anyway, right?
You are correct, this is the plan. Feel free to create a wiki
page / snippet on how to do the command line training. I'll make sure
people can find it.
On 02/28, Philipp Dörfler wrote:
Yes I believe it is worth to train your rspamd. Eventually #61 will take care of the training with imap_sieve.
But as far as I understand it, this only works for new mail moved to the Junk mailbox. For the initial import you'd still have to resort to using the command line. And for this maybe a wiki page would be nice. You planned on putting the big readme.md into the wiki anyway, right?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#91 (comment)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We neither use the dovecot antispam plugin nor do we use imap_sieve.
So how does one tell rspamd that a mail is spam or ham? Other than of course running the commands in the terminal. We should at least document that.
The text was updated successfully, but these errors were encountered: