Sieve not configured properly

sovereign / sovereign

A set of Ansible playbooks to build and maintain your own private cloud: email, calendar, contacts, file sync, IRC bouncer, VPN, and more.

Other

10.41k stars 827 forks source link

Sieve not configured properly #647

Open JGjorgji opened 7 years ago

JGjorgji commented 7 years ago

15-lda.conf says the settings apply to lmtp too however mail is not processed by sieve rules, this needs to be added so it works:

protocol lmtp {
  # Space separated list of plugins to load (default is global mail_plugins).
  mail_plugins = $mail_plugins sieve
}

I've added this in a separate lmtp conf file and it works fine, also the firewall needs to open a port for managesieve, port 4190 which is not opened.

neuhaus commented 7 years ago

If you manage sieve using the sieve plugin for Roundcube you don't need to open the port in the firewall so it makes sense to keep it that way as a secure default.

JGjorgji commented 7 years ago

That makes sense guess i was using thunderbird and didn't consider that. It would be useful to have this mentioned someplace in case someone wants to use it in this way too.

How about the filtering is it working for you by default?

neuffer commented 7 years ago

On 31.01.2017 20:14, Gjorgji Jankovski wrote:

That makes sense guess i was using thunderbird and didn't consider that. It would be useful to have this mentioned someplace in case someone wants to use it in this way too.

Maybe this information could be added to the project wiki ?

bjdeliduka commented 7 years ago

I just did a fresh install of sovereign on a linode running Debian 8 and noticed the following:

roundcube lacks a method of changing the mailbox/user password.
there is a filter set named "managesieve" with a filter named #1 that checks message headers for "x-dspam-result" values matching a regular expression. matches are to be marked as Read and moved to a folder named Spam
the Spam folder does not exist
messages do not contain "x-dspam-result"
test email messages from http://www.emailsecuritycheck.net/ all pass through to the inbox without any flagging as spam not warnings about "viruses" that should be triggered by the test content.

I have not checked the above change to see if it fixes the spam / sieve issue. (manually creating the Spam folder does not have any impact on the functionality of this. Saving the filter requires setting a valid name (it is blank by default)

Did I miss something?

neuhaus commented 7 years ago

Thanks for your report!

The only supported way to change a user's mail password is to change it in the group_vars/sovereign file. If you change it in some other way it will get overwritten the next time sovereign is run.

Given that the spam folder doesn't exist - will sieve create it when moving a message into it?

dspam was replaced by rspam. This configuration needs to be updated.