https://bugs.kde.org/show_bug.cgi?id=349852
Bug ID: 349852 Summary: Sieve doesn't connect to Sieve server when using a Sieve server address different from IMAP server Product: kmail2 Version: 4.14.7 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: stef...@as-lehmann.de No connection attempt will be made to Sieve server when using a Sieve server address different from IMAP server. Reproducible: Always Steps to Reproduce: 1. Configure an IMAP access (STARTTLS, DIGEST-MD5 or CRAM-MD5) 2. Configure "The server supportes Sieve" 3. Configure an alternative address for the ManageSieve server, different from the IMAP server address. This ManageSieve server servers uses a certificate which is signed by an unknown cert authority. 4. Configure "Authentication using IMAP login and password" and save configuration. 5. Open the "Manage Sieve scripts" dialogue Actual Results: No connection attempt will be made to the ManageSieve server Expected Results: The ManageSieve server will be connected, the login procedure succeeds with both, CRAM-MD5 and DIGEST-MD5, authentication methods. Maybe it happens after a failed login to ManageSieve made earlier (using CRAM-MD5/DIGEST/MD5) Maybe it happens after a TLS certificate check failed once (but was accepted, I'm using my own self-signed certificate where the certificate name doesn't match the server name) In order to investigate this problem, I can provide you with a test account. I'm using KMail version 4.14.9 (unfortunately, this version is not selectable in the "version" selection box, see above). -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs