To support both Cypht 1.4 (which uses tls:// prefixes for Sieve hostnames) and newer versions (which omit tls://), we’ve implemented an automated way to determine the correct Sieve hostname format using Nux_Quick_Services. Here's how it works:
Automatic Host Detection: The code checks Nux_Quick_Services to retrieve the correct Sieve host for each service. For example, for migadu, it will use domain.com:port.
Version Compatibility: If the running version is Cypht 1.4, it will prepend tls:// to the hostname (e.g., tls://domain.com:port). For newer versions, it uses the plain hostname format (domain.com:port).
Seamless Integration: This ensures compatibility with both Cypht 1.4 and newer versions without manual configuration changes, reducing user setup errors and simplifying support.
Related comment from @marclaporte : https://avan.tech/item119173#threadId81209
To support both Cypht 1.4 (which uses
tls://prefixes for Sieve hostnames) and newer versions (which omittls://), we’ve implemented an automated way to determine the correct Sieve hostname format usingNux_Quick_Services. Here's how it works:Automatic Host Detection: The code checks
Nux_Quick_Servicesto retrieve the correct Sieve host for each service. For example, formigadu, it will usedomain.com:port.Version Compatibility: If the running version is Cypht 1.4, it will prepend
tls://to the hostname (e.g.,tls://domain.com:port). For newer versions, it uses the plain hostname format (domain.com:port).Seamless Integration: This ensures compatibility with both Cypht 1.4 and newer versions without manual configuration changes, reducing user setup errors and simplifying support.