I recently updated to /e/OS 2.9-t-202503211478215-official-FP5.
Since that update I am no longer able to fetch emails from my mail-server. I regularily get an “Authentication failed” message when I try to update emails.
I can then set the correct password in the settings of the email-account and the emails are fetched. Until 5 minutes later the same “Authentication failed” message pops up.
When viewing the password in clear text I realized that it wasn’t the password of the email-account but of the murena account that somehow was displayed - and I assume also used to authenticate against the IMAP-server.
The odd thing is that only one of two accounts are affected.
The settings of the incoming server in the fetching-settings of the affected account are as follows:
IMAP Server: mail. example. com
Security: SSL/TLS
Port: 993
Username: andreas@example. com
Authentication: Normal Password
Password: P@ssw0rd
Client Certificate: No client certificate
The “Murena” account should be set up as follows
Server: cloud. example. com
Username: Andreas
Password: MySecretNextCloudP@ssw0rd
Yes: That is an account on a self-hosted Nextcloud instance running NextCloud Hub 31.0.2. (There are some issues with the Calendar Sync but that seems to be related to that NextCloud Version - different story!)
The email-address behind that Nextcloud-user is andreas@example.com
So my main question is: How can I stop the mail-app from replacing the provided password with a different one?
For now I will move to K9 to get my emails back onto my phone…
Edit: All links without the spaces. But it looks like as a new contributor I can only provide 2 links. and FQDNs seem automatically be considered as “links”…