[GH-ISSUE #1153] Sieve - can't make it work #586

Open
opened 2026-02-25 21:35:26 +03:00 by kerem · 24 comments
Owner

Originally created by @europacafe on GitHub (Aug 9, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1153

Originally assigned to: @Shadow243 on GitHub.

💬 Question

Mail server: stalwart + snappymail webmail ---> tls sieve work (mail.mydomain.com, ssl/tls, 4190)
Cypht 2.1.0 + stalwart --> tls sieve setting does not work, can't save server config

When opening a mail content, it always reports "Sieve: invalid config host for ....my mailbox name.."
cypht_sieve_invalid_config

On stalwart mail server, below is the sieve config
stalwart_sieve_tls_config

On snappymail webmail, the sieive config works
snappymail_sieve_config

On cypht env file, below is the config:
cypht_sieve_env_config

When I tried to enable sieve on one of my IMAP accounts as below, after saving the config, the screen froze for over 10 secs and came back with an offline label and it didn't save.
image
I'm not sure what I did wrong. (I enable sieve on Settings/Site/Enable sieve filter)

Originally created by @europacafe on GitHub (Aug 9, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1153 Originally assigned to: @Shadow243 on GitHub. ## 💬 Question Mail server: stalwart + snappymail webmail ---> tls sieve work (mail.mydomain.com, ssl/tls, 4190) Cypht 2.1.0 + stalwart --> tls sieve setting does not work, can't save server config When opening a mail content, it always reports "Sieve: invalid config host for ....my mailbox name.." ![cypht_sieve_invalid_config](https://github.com/user-attachments/assets/72f28639-d098-4a71-bdf1-4c43d28a3481) On stalwart mail server, below is the sieve config ![stalwart_sieve_tls_config](https://github.com/user-attachments/assets/d91123bb-190c-4133-88b8-2287a073c628) On snappymail webmail, the sieive config works ![snappymail_sieve_config](https://github.com/user-attachments/assets/320d895f-c9db-42e0-bfd2-0ccbff6d0d26) On cypht env file, below is the config: ![cypht_sieve_env_config](https://github.com/user-attachments/assets/0821f0ce-0f2a-488b-b857-ecab47ac9de4) When I tried to enable sieve on one of my IMAP accounts as below, after saving the config, the screen froze for over 10 secs and came back with an offline label and it didn't save. ![image](https://github.com/user-attachments/assets/7113de0d-a7c1-4191-a442-8a6c8d378171) I'm not sure what I did wrong. (I enable sieve on Settings/Site/Enable sieve filter)
Author
Owner

@josaphatim commented on GitHub (Aug 9, 2024):

@europacafe thank you for reporting this. What if you remove the protocol in sieve host input mail.brhofen.com:4190 ?

<!-- gh-comment-id:2277376377 --> @josaphatim commented on GitHub (Aug 9, 2024): @europacafe thank you for reporting this. What if you remove the protocol in sieve host input `mail.brhofen.com:4190` ?
Author
Owner

@europacafe commented on GitHub (Aug 9, 2024):

I did try that too. Not working as well.

<!-- gh-comment-id:2277517313 --> @europacafe commented on GitHub (Aug 9, 2024): I did try that too. Not working as well.
Author
Owner

@marclaporte commented on GitHub (Aug 9, 2024):

Please try Cypht master

<!-- gh-comment-id:2278323743 --> @marclaporte commented on GitHub (Aug 9, 2024): Please try Cypht master
Author
Owner

@europacafe commented on GitHub (Aug 9, 2024):

How? (with docker compose)

<!-- gh-comment-id:2278412574 --> @europacafe commented on GitHub (Aug 9, 2024): How? (with docker compose)
Author
Owner

@marclaporte commented on GitHub (Aug 9, 2024):

How? (with docker compose)

@jonocodes This is not yet coded, right?

<!-- gh-comment-id:2278642019 --> @marclaporte commented on GitHub (Aug 9, 2024): > How? (with docker compose) @jonocodes This is not yet coded, right?
Author
Owner

@marclaporte commented on GitHub (Aug 10, 2024):

Please try this: https://github.com/cypht-org/cypht/pull/1135/files (just manually modify the file)

Here is an known issue: https://github.com/cypht-org/cypht/issues/931

<!-- gh-comment-id:2278939405 --> @marclaporte commented on GitHub (Aug 10, 2024): Please try this: https://github.com/cypht-org/cypht/pull/1135/files (just manually modify the file) Here is an known issue: https://github.com/cypht-org/cypht/issues/931
Author
Owner

@europacafe commented on GitHub (Aug 10, 2024):

just manually modified it to $server = Hm_IMAP_List::get($imap_server_id, true);, restarted cypht container, rechecked the change was still there
same behavior for both tls://mail.mydomain.com:4190 and mail.mydomain.com:4190

<!-- gh-comment-id:2278960597 --> @europacafe commented on GitHub (Aug 10, 2024): just manually modified it to `$server = Hm_IMAP_List::get($imap_server_id, true);`, restarted cypht container, rechecked the change was still there same behavior for both tls://mail.mydomain.com:4190 and mail.mydomain.com:4190
Author
Owner

@Shadow243 commented on GitHub (Aug 10, 2024):

@europacafe have you checked that the server firewall gives access to 4190 on your server ?

you can use this command to check if sieve is enabled:

openssl s_client -connect mail.mydomain.com:4190 --starttls sieve
<!-- gh-comment-id:2282301107 --> @Shadow243 commented on GitHub (Aug 10, 2024): @europacafe have you checked that the server firewall gives access to 4190 on your server ? you can use this command to check if sieve is enabled: ``` openssl s_client -connect mail.mydomain.com:4190 --starttls sieve ```
Author
Owner

@europacafe commented on GitHub (Aug 11, 2024):

I did open 4190 port on my pfSense. Here is the test result
image

As mentioned earlier, my snappymail webmail can connect to sieve.

<!-- gh-comment-id:2282333660 --> @europacafe commented on GitHub (Aug 11, 2024): I did open 4190 port on my pfSense. Here is the test result ![image](https://github.com/user-attachments/assets/fd48165f-9a79-4cf1-b634-147e7e3ab6c1) As mentioned earlier, my snappymail webmail can connect to sieve.
Author
Owner

@jonocodes commented on GitHub (Aug 14, 2024):

Yes, I would think you could use the docker compose setup to test this.
Also check the cypht service logs to see if there are any errors.

<!-- gh-comment-id:2289932220 --> @jonocodes commented on GitHub (Aug 14, 2024): Yes, I would think you could use the docker compose setup to test this. Also check the cypht service logs to see if there are any errors.
Author
Owner

@europacafe commented on GitHub (Aug 15, 2024):

Yes, I would think you could use the docker compose setup to test this. Also check the cypht service logs to see if there are any errors.

My cypht is always running as a container, and the suggested openssl test was carried out inside cypht container.

<!-- gh-comment-id:2290144592 --> @europacafe commented on GitHub (Aug 15, 2024): > Yes, I would think you could use the docker compose setup to test this. Also check the cypht service logs to see if there are any errors. My cypht is always running as a container, and the suggested openssl test was carried out inside cypht container.
Author
Owner

@europacafe commented on GitHub (Aug 19, 2024):

With docker image v2.2.0, this is still an issue

<!-- gh-comment-id:2297701216 --> @europacafe commented on GitHub (Aug 19, 2024): With docker image v2.2.0, this is still an issue
Author
Owner

@jonocodes commented on GitHub (Aug 20, 2024):

Do we know that this works as expected when not using docker (using php locally without any container)?

<!-- gh-comment-id:2299209539 --> @jonocodes commented on GitHub (Aug 20, 2024): Do we know that this works as expected when not using docker (using php locally without any container)?
Author
Owner

@Shadow243 commented on GitHub (Aug 20, 2024):

Do we know that this works as expected when not using docker (using php locally without any container)?

Yes we were able to connect not using docker, I'm going to try this one with the same server that worked but using docker instead.

<!-- gh-comment-id:2299216319 --> @Shadow243 commented on GitHub (Aug 20, 2024): > Do we know that this works as expected when not using docker (using php locally without any container)? Yes we were able to connect not using docker, I'm going to try this one with the same server that worked but using docker instead.
Author
Owner

@marclaporte commented on GitHub (Sep 28, 2024):

Is still an issue with Cypht 2.4.0?
https://hub.docker.com/r/cypht/cypht

<!-- gh-comment-id:2380378722 --> @marclaporte commented on GitHub (Sep 28, 2024): Is still an issue with Cypht 2.4.0? https://hub.docker.com/r/cypht/cypht
Author
Owner

@europacafe commented on GitHub (Sep 28, 2024):

Yes.

<!-- gh-comment-id:2380384324 --> @europacafe commented on GitHub (Sep 28, 2024): Yes.
Author
Owner

@Shadow243 commented on GitHub (Sep 28, 2024):

Will be solved here https://github.com/cypht-org/cypht/pull/1199

<!-- gh-comment-id:2380578671 --> @Shadow243 commented on GitHub (Sep 28, 2024): Will be solved here https://github.com/cypht-org/cypht/pull/1199
Author
Owner

@Shadow243 commented on GitHub (Oct 27, 2024):

@europacafe please confirm on your side.

<!-- gh-comment-id:2440222784 --> @Shadow243 commented on GitHub (Oct 27, 2024): @europacafe please confirm on your side.
Author
Owner

@europacafe commented on GitHub (Oct 28, 2024):

With cypht 2.4.0 docker container, it is still not working at all, with Stalwart mail server.

Fyi. With snappymail web client, Sieve works only with ssltls, but not starttls. They are working on the issue.

<!-- gh-comment-id:2440234235 --> @europacafe commented on GitHub (Oct 28, 2024): With cypht 2.4.0 docker container, it is still not working at all, with Stalwart mail server. Fyi. With snappymail web client, Sieve works only with ssltls, but not starttls. They are working on the issue.
Author
Owner

@Shadow243 commented on GitHub (Oct 28, 2024):

With cypht 2.4.0 docker container

2.4.0 is not yet compatible; it will work with the master branch. Full compatibility will come with version 2.5.0, not 2.4.0.

<!-- gh-comment-id:2440237231 --> @Shadow243 commented on GitHub (Oct 28, 2024): > With cypht 2.4.0 docker container 2.4.0 is not yet compatible; it will work with the master branch. Full compatibility will come with version 2.5.0, not 2.4.0.
Author
Owner

@europacafe commented on GitHub (Oct 28, 2024):

Great. I may build it from the master and try it. Will feedback later.

<!-- gh-comment-id:2440240071 --> @europacafe commented on GitHub (Oct 28, 2024): Great. I may build it from the master and try it. Will feedback later.
Author
Owner

@cptsanifair commented on GitHub (Oct 31, 2024):

@europacafe u can try to connect with this tool https://github.com/thsmi/sieve to test the connection and sieve.

<!-- gh-comment-id:2449624122 --> @cptsanifair commented on GitHub (Oct 31, 2024): @europacafe u can try to connect with this tool https://github.com/thsmi/sieve to test the connection and sieve.
Author
Owner

@marclaporte commented on GitHub (Sep 1, 2025):

I may build it from the master and try it. Will feedback later.

@europacafe we need you :-)

<!-- gh-comment-id:3240668043 --> @marclaporte commented on GitHub (Sep 1, 2025): > I may build it from the master and try it. Will feedback later. @europacafe we need you :-)
Author
Owner

@marclaporte commented on GitHub (Sep 1, 2025):

@europacafe @jonocodes @cptsanifair
The monthly Cypht community meetings are a great opportunity to show bugs: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings

<!-- gh-comment-id:3240692763 --> @marclaporte commented on GitHub (Sep 1, 2025): @europacafe @jonocodes @cptsanifair The monthly Cypht community meetings are a great opportunity to show bugs: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#586
No description provided.