sieve login does not work if plain login is only available under a layer (gosa bug 1175)
The sieve protocol allows to disable the login mechanism until a TLS session is established. In a regular setup the sieve server responds like this:
"IMPLEMENTATION" "Cyrus timsieved v2.2.13-Debian-2.2.13-19+squeeze3" "SASL" "LOGIN PLAIN" "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex" "STARTTLS" OK
if we disable unencrypted plain text logins the sieve server only accepts the plain login after a STARTTLS:
"IMPLEMENTATION" "Cyrus timsieved v2.2.13-Debian-2.2.13-19+squeeze3" "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex" "STARTTLS" OK
Further documentation and a complete example could be found in RFC 5804 under chapter 2.1 (the example could be found at http://tools.ietf.org/html/rfc5804#page-15).
GOsa² first checks for the PLAIN login mechanism, if this could not be found the login is aborted. To meet the RFC requirements this should be changed so that in case of TLS there is no requirement for any authentication mechanism. If attached a possible and working patch for the sieve implementation.
(from redmine: issue id 1029, created on 2012-06-09, closed on 2013-04-12)
- Changesets:
- Revision f7a5d6ed by Benoit MORTIER on 2012-06-09T11:19:01.000Z:
Fixes: #1029 sieve login does not work if plain login is only available under a layer (gosa bug 1175)
- Custom Fields:
- Bug in version: 1.0.3
- Uploads: