New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0013854: Can't update Email Accounts without Sieve Server #6851

Open
Gloirin opened this Issue Jun 9, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@Gloirin

Gloirin commented Jun 9, 2018

Reported by psieg on 3 May 2018 16:07

Version: 2018.02.3 Community Edition

I am unable to update the email account of a user in a setup that does not use sieve.
Hitting save results in

Tinebase_Exception::logExceptionToLogger::133 Felamimail_Exception_Sieve -> Could not authenticate with user XXX (cannot write - connection closed?).

because the sieve server hostname is "".
The sieve notification email is empty. Debugging leads to
Felamimail/Controller/Account.php line 452:

452 if ($updatedRecord->sieve_notification_email != $currentRecord->sieve_notification_email) {

In this case, the left side was "" but the right side was NULL, leading this function to believe a valid sieve configuration exists and should be updated, which fails, lacking a sieve server.

I am not sure if this difference is due to an update, but I did not manually change the database.

Steps to reproduce: * Setup an email account with IMAP/SMTP but no sieve (before an update?)

  • Try to change the IMAP password later

Expected: Password change
Actual: Error message about connection that does not hint at Sieve being the problem

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by psieg on 3 May 2018 16:08

Of course the original line contains !==. As a workaround, I used !=, which allowed me to update the account in question.

Gloirin commented Jun 11, 2018

Comment posted by psieg on 3 May 2018 16:08

Of course the original line contains !==. As a workaround, I used !=, which allowed me to update the account in question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment