Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

antispam question #897

hanoii opened this issue Jan 28, 2019 · 4 comments · Fixed by #1351

antispam question #897

hanoii opened this issue Jan 28, 2019 · 4 comments · Fixed by #1351
type/enhancement Enhances existing functionality type/question


Copy link

hanoii commented Jan 28, 2019

I am confused on something related to the rspamd

From #859 (comment) I learned that it's not optional, but then, on each user edit account you have an option to disable it:

screen shot 2019-01-28 at 12 03 34

However, on rspamd history which I could access from #887 I still see actions taken on mails on the accounts I disabled antispam, how does that work?

@muhlemmer muhlemmer changed the title antispam quesiton antispam question Feb 12, 2019
Copy link

All mails go through antispam, which sets some headers to the mail. It is up to Dovecot to decide what to do with the actual mail. So the setting is checked in the default.sieve script template (served by admin):

{% if user.spam_enabled %}
if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "{{ user.spam_threshold }}"

Copy link

Mh … something just came to my mind while reading that — does that mean that antispam hard-drops, where rspamd doesn’t even hand the mail further to dovecot, still affect users with spam_enabled = False?

Copy link

hanoii commented Feb 18, 2019

@Nebukadneza yes, exactly. There are hard drops - I noticed specially while doing a few telnet smtp tests.

Copy link

kaiyou commented May 7, 2019

Indeed, we should make more clear that disabling the antispam will actually stop mails from being moved to the spam directory. It does not disable the dirst-trashing part of rspamd, which simply drops the mail before it can even reach Dovecot.

@kaiyou kaiyou added the type/enhancement Enhances existing functionality label May 7, 2019
@kaiyou kaiyou mentioned this issue Feb 7, 2020
2 tasks
bors bot added a commit that referenced this issue Feb 8, 2020
1351: Add some faq entries r=mergify[bot] a=kaiyou

## What type of PR?


## What does this PR do?

Add missing faq entries

### Related issue(s)
- Closes: #853 
- Closes: #897 
- Closes: #1090 
- Closes: #1315

## Prerequistes
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.

- [x] In case of feature or enhancement: documentation updated accordingly
- [x] Unless it's docs or a minor change: add [changelog]( entry file.

Co-authored-by: kaiyou <>
@bors bors bot closed this as completed in #1351 Feb 8, 2020
@bors bors bot closed this as completed in 770d09b Feb 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
type/enhancement Enhances existing functionality type/question
None yet

Successfully merging a pull request may close this issue.

4 participants