Not possible to send mail from Roundcube as alias

[psychofaktory]

The error in Roundcube when filling in the To: field is still present in v60.3 (since v60.2). Application Error (700): Addressbook source (carddav_2) not found! However, contacts can be found via the existing address books.

It is still possible to send an e-mail if you answer an email. But if I try to send a new e-mail as alias I got the error: Verbindungsfehler (Fehler beim Erreichen des Servers)!

Originally posted by @psychofaktory in https://github.com/ddavness/power-mailinabox/issues/82#issuecomment-1283102842

[ddavness]

That's a strange one. Been playing around with aliases here and nothing out of the ordinary (you can send new mail as alias as long as you own that alias, otherwise it will naturally spew an error). Asking a few probing questions to see if I can get closer to the root of the issue:

• The second error translates roughly to Connection error (failed to reach server)! Did you by any chance set Roundcube to German (just because it'd be weird if there happened to be a German error message in English)?
• What's the distribution being used? Different versions of PHP could yield the error;
• Have you seen anything strange during the setup process during the Roundcube step? (warnings, errors, setup time being abnormally long/short...)

[psychofaktory]

The aliases were created as before: As an admin, a new alias was created which then forwards to my mailbox. In the Roundcube, the alias address was then stored as a new identity in the settings -> Identities. When I sent a new email, I could then select the new alias as the sender and send it without errors.

Yes, Roundcube was set to German. That's probably why the error message was in German. Whereas the other error message mentioned appeared in English.

This distribution is used: Operating System: Ubuntu 20.04.5 LTS Kernel: Linux 5.4.0-131-generic Architecture: x86-64

The box was installed in December 2021 with Ubuntu 20.04 LTS and Power-Mail-In-A-Box v55.1. Since then, all available updates have been applied regularly.

During the installation, there were no warnings, errors or other anomalies (apart from the doveconf warnings already mentioned).

[ddavness]

As an admin, a new alias was created which then forwards to my mailbox. In the Roundcube, the alias address was then stored as a new identity in the settings -> Identities. When I sent a new email, I could then select the new alias as the sender and send it without errors.

Yeah, that seems right. Did it stop working since v60.0?

[psychofaktory]

Did it stop working since v60.0?

Yes, exactly.

[ddavness]

Anything in the logs that could give us any more useful info? (The log files are at the /var/log/roundcubemail/ folder)

[psychofaktory]

Anything in the logs that could give us any more useful info? (The log files are at the /var/log/roundcubemail/ folder)

In the 'errors.log' there are a lot entries like this: [31-Oct-2022 09:12:27 +0100]: <bo8q1m90> PHP Error: Addressbook source (carddav_2) not found! in /usr/local/lib/roundcubemail/program/include/rcmail.php on line 376 (POST /mail/?_task=mail&_unlock=loading1667203944401&_framed=1&_action=send)

[ddavness]

I wonder where the 2 in carddav_2 comes from. Question - when you go into Contacts on Roundcube webmail, do you see an extra addressbook other than these? Does it happen to give you an error when trying to go into this page?

[psychofaktory]

do you see an extra addressbook other than these?

No, there are just the default adressbooks:

I can open all entries without getting an error message.

[psychofaktory]

OK. That took me in the right direction!

• "Standardadressbuch" was set to "Persönliches Adressboch". I changed it to "ownCloud (Kontakte).
• "Empfänger ausgehender E-Mails speichern in" was set to "---". I changed it to "Gesammelte Empfänger".

Now I can sent Mails without an error again!

[ddavness]

Ah, so finally we found the problem*

But we haven't found the cause of the problem. How did the update break this?

[psychofaktory]

That's the question.

I didn't changed any settings manualy there since the update. So something must have changed here with the update.

I may have been wrong here, and the problem was not that I had tried to send via an alias, but that the recipient had never been sent an email before.