Mailbox refresh hang forever after migration from 1.1.4 to 1.3.2

[doc75]

Expected behavior

Mailbox opened without any issue and list of mail appears after a couple of seconds

Actual behavior

list of message never appear, the refresh circle stays forever

Here is the error log (mail address have been removed and replaced by <text explaining the content remove and approximate length>:

error_clean.log

Seems related to mail with a lot of recipients.

Mail app

Mail app version: 1.3.2 (right after migration from a 1.1.4 which was working like a charm)

Mailserver or service: Dovecot (personal installation, the same one used with 1.1.4)

Server configuration

Operating system: Alpine Linux (official Nextcloud docker image)

Web server: Nginx

Database: PostgreSQL

PHP version: 7.3.16

Nextcloud Version: 17.0.25 (official docker image)

Client configuration

Browser: Firefox 75.0

Operating system: Ubuntu 18.04

[ChristophWurst]

Seems related to mail with a lot of recipients.

Do you know the specific message that causes this? Mind sending an exported .mbox (via Thunderbird or Evolution) to my email? I would like to inspect that header. I think it's malformed.

The app inserts one entry per recipient. But somehow in your case many of them are crammed into a single item. Thus the error

"Message": "Sync failed for 1:INBOX: An exception occurred while executing 'INSERT INTO \"oc_mail_recipients\" (\"message_id\", \"type\", \"label\", \"email\") VALUES(?, ?, ?, ?)' with params [310, 1, <list of mail address separated by 2 commas and the last one surrounded by double quotes (number of char in the string is about 1900)>]:\n\nSQLSTATE[22001]: String data, right truncated: 7 ERROR:  value too long for type character varying(255)",

[FleischKarussel]

I can confirm the hanging of Mail 1.3.2 with mailbox.org as IMAP provider (with a lot of emails in Inbox and multiple folders), when it was working with an older release, don't know the previous release.
GMX IMAP with just one email in the Inbox, works fine. ( I know, not a good comparison.)
I am a bit clueless what's the error log OP attached.
Is this a stripped nextcloud.log?

Using Docker Nextcloud 18.0.3 and Mail 1.3.2 with Docker PGSQL 11.x

[ChristophWurst]

confirm this

what exactly are you confirming?

[doc75]

Do you know the specific message that causes this? Mind sending an exported .mbox (via Thunderbird or Evolution) to my email? I would like to inspect that header. I think it's malformed.

Mail sent with information.
Thanks.

[zpintar]

@ChristophWurst This is exactly the same error what we are getting in our log.
Our admins try to check dbase's configs, but without success.
Not all mailboxes are affected. Only these with many e-mails in inbox.
We are using Nextcloud 18.03.

[ChristophWurst]

Another suggestion: enable query logs on the database. Once the error returns inspect the SQLs issued before the aborted transaction.

[ChristophWurst]

Ah I possibly mixed a few tickets. @zpintar are you also affected by the insert failing due to a very long recipient?

[zpintar]

Ah I possibly mixed a few tickets. @zpintar are you also affected by the insert failing due to a very long recipient?

I'm not sure that I understood this? What is "very long recipient? e-mail with long name or e-mail with long message(s), or many e-mail in receive inbox?

[ChristophWurst]

is String data, right truncated: 7 ERROR: value too long for type character varying(255) the error you're experiencing?

I'll see if I can reproduce the problem locally with @doc75's email

[ChristophWurst]

Okay, I can actually not. The email imports just fine. The recipients are correctly treated as multiple, hence no error when inserting.

[zpintar]

I noticed our server admins to this thread, so they will communicate with you about this problem. I'm only power user. ;)

[zpintar]

Hmm, maybe this is something useful?
"File":"/var/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php","Line":117,"Previous":{"Exception":"OCA\\Mail\\Exception\\ServiceException","Message":"Sync failed for 25:INBOX: An exception occurred while executing 'INSERT INTO \"oc_mail_recipients\" (\"message_id\", \"type\", \"label\", \"email\") VALUES(?, ?, ?, ?)' with params [581675, 0, \"\\x73\\x74\\x72\\x75\\xe8\\x6e\\x6f\\x67\\x40\\x69\\x70\\x7a\\x2e\\x68\\x72\", \"\\x73\\x74\\x72\\x75\\xe8\\x6e\\x6f\\x67\\x40\\x69\\x70\\x7a\\x2e\\x68\\x72\"]:\n\nSQLSTATE[22021]: Character not in repertoire: 7 ERROR: invalid byte sequence for encoding \"UTF8\": 0xe8 0x6e
Something with UTF8 encoding??

[ChristophWurst]

Yeah, I'm almost confident that this is the root of all these errors.

0xe8 0x6e

Is that the full sequence? Because if so, that isn't valid utf8 according to https://onlineutf8tools.com/convert-hexadecimal-to-utf8

It would mean that the problem actually is the same as in #2925. But just with a different database type.