mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 13:05:53 +03:00
[GH-ISSUE #1153] Sieve - can't make it work #586
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#586
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.."

On stalwart mail server, below is the sieve config

On snappymail webmail, the sieive config works

On cypht env file, below is the 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.

I'm not sure what I did wrong. (I enable sieve on Settings/Site/Enable sieve filter)
@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?@europacafe commented on GitHub (Aug 9, 2024):
I did try that too. Not working as well.
@marclaporte commented on GitHub (Aug 9, 2024):
Please try Cypht master
@europacafe commented on GitHub (Aug 9, 2024):
How? (with docker compose)
@marclaporte commented on GitHub (Aug 9, 2024):
@jonocodes This is not yet coded, right?
@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
@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 theresame behavior for both tls://mail.mydomain.com:4190 and mail.mydomain.com:4190
@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:
@europacafe commented on GitHub (Aug 11, 2024):
I did open 4190 port on my pfSense. Here is the test result

As mentioned earlier, my snappymail webmail can connect to sieve.
@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.
@europacafe commented on GitHub (Aug 15, 2024):
My cypht is always running as a container, and the suggested openssl test was carried out inside cypht container.
@europacafe commented on GitHub (Aug 19, 2024):
With docker image v2.2.0, this is still an issue
@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)?
@Shadow243 commented on GitHub (Aug 20, 2024):
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.
@marclaporte commented on GitHub (Sep 28, 2024):
Is still an issue with Cypht 2.4.0?
https://hub.docker.com/r/cypht/cypht
@europacafe commented on GitHub (Sep 28, 2024):
Yes.
@Shadow243 commented on GitHub (Sep 28, 2024):
Will be solved here https://github.com/cypht-org/cypht/pull/1199
@Shadow243 commented on GitHub (Oct 27, 2024):
@europacafe please confirm on your side.
@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.
@Shadow243 commented on GitHub (Oct 28, 2024):
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.
@europacafe commented on GitHub (Oct 28, 2024):
Great. I may build it from the master and try it. Will feedback later.
@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.
@marclaporte commented on GitHub (Sep 1, 2025):
@europacafe we need you :-)
@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