Is managed sieve working? #3653

jessec · 2023-11-23T12:43:42Z

jessec
Nov 23, 2023

0.0.0.0:25->25/tcp, :::25->25/tcp, 0.0.0.0:143->143/tcp, :::143->143/tcp, 0.0.0.0:465->465/tcp, :::465->465/tcp, 0.0.0.0:587->587/tcp, :::587->587/tcp, 110/tcp, 995/tcp, 0.0.0.0:993->993/tcp, :::993->993/tcp**, 4190/tcp**

I can't seem to get managed sieve working. I see only 1 port is it possible the sieve deamon is not running?

Answered by polarathene

Nov 24, 2023

and inside the docker mailserver container I see this:
root@lopkyhj:/etc/dovecot# ls /etc/dovecot/protocols.d/
imapd.protocol lmtpd.protocol managesieved.protocol.disab pop3d.protocol.disab
managesieved.protocol.disab
is it still disabled?

It doesn't seem like the ENV logic ran for you?

docker-mailserver/target/scripts/startup/setup.d/dovecot.sh

Lines 52 to 57 in 2a716cf

     # enable Managesieve service by setting the symlink  
   # to the configuration file Dovecot will actually find  
   if [[ ${ENABLE_MANAGESIEVE} -eq 1 ]]; then  
   _log 'trace' 'Sieve management enabled'  
   mv /etc/dovecot/protocols.d/managesieved.protocol.disab /etc/dovecot/protocols.d/managesieved.pr…

View full answer

polarathene · 2023-11-23T19:34:13Z

polarathene
Nov 23, 2023
Maintainer

You should provide more context (compose.yaml + other config to reproduce), have you tried :edge tag? There was sieve fixes added there that will be part of the soon to release v13.

0 replies

jessec · 2023-11-24T02:56:02Z

jessec
Nov 24, 2023
Author

I followed the documentation and I opened the 4190 port. Is there a way to identify if the sieve plugin is loaded and working? Maybe with a ps | grep "sieve" ???

I also can't telnet into the port:

$ telnet  15.45.219.48 4190
telnet: connect to address 15.45.219.48:  Connection refused

and inside the DMS container I see this:

root@lopkyhj:/etc/dovecot# ls /etc/dovecot/protocols.d/   
imapd.protocol	lmtpd.protocol	managesieved.protocol.disab  pop3d.protocol.disab

managesieved.protocol.disab

is it still disabled?

`compose.yaml`

ports:
  - "4190:4190"
environment:
  - ENABLE_MANAGESIEVE=1

2 replies

polarathene Nov 24, 2023
Maintainer

and inside the docker mailserver container I see this:
root@lopkyhj:/etc/dovecot# ls /etc/dovecot/protocols.d/
imapd.protocol lmtpd.protocol managesieved.protocol.disab pop3d.protocol.disab
managesieved.protocol.disab
is it still disabled?

It doesn't seem like the ENV logic ran for you?

docker-mailserver/target/scripts/startup/setup.d/dovecot.sh

Lines 52 to 57 in 2a716cf

    
           # enable Managesieve service by setting the symlink 
        
           # to the configuration file Dovecot will actually find 
        
           if [[ ${ENABLE_MANAGESIEVE} -eq 1 ]]; then 
        
             _log 'trace' 'Sieve management enabled' 
        
             mv /etc/dovecot/protocols.d/managesieved.protocol.disab /etc/dovecot/protocols.d/managesieved.protocol 
        
           fi

That should have renamed it to enable it.

We have an incredibly basic test for the Manage Sieve feature, but it does check that it is running AFAIK. Thus it should have caught any problem you're experiencing and I think this is a configuration issue on your end?

Please make sure your config changes are applied with a fresh container instance, not a restarted/resumed one. Try with docker compose up --force-recreate.

If this still doesn't resolve the issue, you should raise a bug report. I'm presently short of time to reproduce and investigate if there is an actual bug on our end.

Answer selected by polarathene

jessec Nov 26, 2023
Author

Yes I had to recreate that was the problem thanks!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker Mailserver

Is managed sieve working? #3653

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

	# enable Managesieve service by setting the symlink
	# to the configuration file Dovecot will actually find
	if [[ ${ENABLE_MANAGESIEVE} -eq 1 ]]; then
	_log 'trace' 'Sieve management enabled'
	mv /etc/dovecot/protocols.d/managesieved.protocol.disab /etc/dovecot/protocols.d/managesieved.pr…

Docker Mailserver

Is managed sieve working? #3653

Uh oh!

Uh oh!

jessec Nov 23, 2023

Replies: 2 comments · 2 replies

Uh oh!

Uh oh!

polarathene Nov 23, 2023 Maintainer

Uh oh!

Uh oh!

jessec Nov 24, 2023 Author

compose.yaml

Uh oh!

polarathene Nov 24, 2023 Maintainer

Uh oh!

jessec Nov 26, 2023 Author

jessec
Nov 23, 2023

Replies: 2 comments 2 replies

polarathene
Nov 23, 2023
Maintainer

jessec
Nov 24, 2023
Author

`compose.yaml`

polarathene Nov 24, 2023
Maintainer

jessec Nov 26, 2023
Author