Should seive / managesieve work out of the box?

andrewnewby · December 13, 2022, 7:36am

Hi,

Should managedsieve work out of the box? I’m trying to get it working. I can see:

hestiacp/hestiacp/blob/main/install/common/dovecot/sieve/20-managesieve.conf

##
## ManageSieve specific settings
##

# Uncomment to enable managesieve protocol:
protocols = $protocols sieve

# Service definitions

service managesieve-login {
  inet_listener sieve {
    port = 4190
  }

  #inet_listener sieve_deprecated {
  #  port = 2000
  #}

  # Number of connections to handle before starting a new process. Typically
  # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0

This file has been truncated. show original

Looking on my server in /etc/dovecot/sieve , I can see 20-managesieve.conf etc. However, it doesn’t seem to be doing anything. What am I missing? I’ve looked around at loads of posts (not on here), and they say about enabling LMTP, and things like that - but the fact you have those files in the installer makes me think it should be simpler than that to get going?

FWIW, this is what I get from:


dovecot -n | grep pro
protocols = imap pop3 sieve imap lmtp sieve pop3
ssl_min_protocol = TLSv1.2
protocol imap {
protocol pop3 {

Thanks!

Andy

eris · December 13, 2022, 8:58am

Add -Z yes during the install or run:

github.com

hestiacp/hestiacp/blob/main/install/upgrade/manual/install_sieve.sh

#!/bin/bash
# info: Install / remove  sieve / manage-sieve for Dovecot
#
# Thos function installs manage-sieve functionality for dovecot.

#----------------------------------------------------------#
#                    Variable&Function                     #
#----------------------------------------------------------#

# Includes
# shellcheck source=/etc/hestiacp/hestia.conf
source /etc/hestiacp/hestia.conf
# shellcheck source=/usr/local/hestia/func/main.sh
source $HESTIA/func/main.sh
# load config file
source_conf "$HESTIA/conf/hestia.conf"
source_conf "$HESTIA/install/upgrade/upgrade.conf"

#----------------------------------------------------------#
#                    Verifications                         #

This file has been truncated. show original

andrewnewby · December 13, 2022, 9:48am

Amazing! Thanks! I wish I’d seen that option when installing. That seems to have done most of it. I have setup a filter in Roundcube:

Then sent an email from the said test filters account. It comes through ok, but ends up in the Inbox still. Is there any manual steps I need to take? I can see the /home/xxx/mail/xxx.com/test/sieve/managesieve.sieve file exists

require ["fileinto"];
# rule:[SPAM]
if header :contains "X-Spam-Flag" "YES"
{
	fileinto "INBOX.Spam";
}
# rule:[dsfsdfsdf]
if allof (header :contains "from" "[email protected]")
{
	fileinto "bla";
}

Yet it doesn’t seem to do it?

UPDATE: Scrap that - it works! Not sure why my last test didn’t, but the one I just did works perfectly now. Thank you so much! I must have spent 12 hours trying to get that going over the last couple of days!

system · January 12, 2023, 9:48am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.