-
STARTTLS support *should* have been working for Cyrus-imapd 2.3.11 and above, so I don't know why this didn't work for you. Perhaps you can supply me with the full output from "sivtest -t "" -m plain -u user -a user server".
I have just committed a fix for starttls behaviour to trunk. It would be useful if you could test whether that works for you with use_starttls => true.
2009-11-23 15:45:08 UTC by stephengrier
-
I've committed a fix for this to the subversion trunk.
SmartSieve now defaults to expecting a CAPABILITY response following a successful STARTTLS. It will disable this behaviour for Cyrus-imapd version before 2.3.11, so all recent managesieve servers should continue to work, and STARTTLS should now work correctly for dovecot.
For servers where SmartSieve still gets it wrong, there is now a...
2009-11-23 15:38:01 UTC by stephengrier
-
I've committed a fix for this to the subversion trunk.
SmartSieve now defaults to expecting a CAPABILITY response following a successful STARTTLS. It will disable this behaviour for Cyrus-imapd version before 2.3.11, so all recent managesieve servers should continue to work, and STARTTLS should now work correctly for dovecot.
For servers where SmartSieve still gets it wrong, there is now a...
2009-11-23 15:37:57 UTC by stephengrier
-
stephengrier committed revision 423 to the SmartSieve SVN repository, changing 4 files.
2009-11-23 15:26:13 UTC by stephengrier
-
Sections 1.7 and 2.2 of draft-martin-managesieve-12 demand managesieve servers to issue a CAPABILITY response following a successful STARTTLS. SmartSieve 1.0-RC2 does not expect this by default, so STARTTLS support is broken for servers that do comply with the spec like dovecot.
SmartSieve should default to complying with draft-martin-managesieve-12 and expect a CAPABILITY response following...
2009-11-23 15:23:40 UTC by stephengrier
-
Fix committed to trunk.
2009-11-16 12:28:48 UTC by stephengrier
-
stephengrier committed revision 422 to the SmartSieve SVN repository, changing 2 files.
2009-11-16 12:27:50 UTC by stephengrier
-
It is not possible to save a custom rule when it is the first rule in a script. Clicking "Save Changes" generates a "You must supply an argument for this action" error.
This is caused by line 128 of rule.php which initializes a new custom rule if empty($ruleID). But if the rule is the first in the script $ruleID will be 0, and empty($ruleID) will be true.
The following patch fixes.
---...
2009-11-16 12:10:34 UTC by stephengrier
-
this line for config/servers.php fixed it:
'use_starttls' => false.
2009-11-04 13:57:27 UTC by stephan_r
-
I should of course mention that the sieve login works perfectly fine, too. We have verified this using sieveshell:
# sieveshell -u testbp -a testbp localhost
connecting to localhost
Please enter your password:
Please enter your password:
> list
ListKnownEmails
smartsieve quit.
2009-11-04 13:02:59 UTC by stephan_r
