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
Amavis error after clean setup modoboa #3116
Comments
@doker445 Do you have more logs to show? |
In error log always get next event: In mail.log: |
@doker445 My guess is that the generated password contains strange characters... Can you check amavis configuration file? (/etc/amavis/conf.d/50-user) |
Or it might also be an issue with the content amavis is trying to store in the database... |
Password look like ok. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is present in my logs today after fresh install on top of fresh Debian 12 OS install Saturday evening. No strange characters in my password either. |
Good morning, I have confirmed in my logs that this is happening anytime there is an email with emojis in the subject. I found this which is same error but in the iRed mail forums: With the answer being: Re: AMAVIS: ERROR sql_storage: too many retries on storing final ok, it's clear caused by emojis. USE amavisd; Let me know how it works. Of course the database for Modoboa is amavis, not amavisd so don't copy and paste that command as it will fail as written. Can anyone from Modoboa chime in on this and confirm its safe to apply to Modoboa and that it will fix the issue? Regards, |
@layer3-fl That's something you can try but I can't guarantee it will fix your issue since the error in your logs is not exactly the same |
Thank you and understood, |
It won't corrupt the installation. |
Thanks for the response. As written above I get syntax error near MODIFY. After a little googling specifying Postgres, I tried: After more googling I found references to not being able to perform this modification in Postgres if there is existing data in the column. A new column has to be created as type VARBINARY(255), use UPDATE statement to add data to new column, drop VARCHAR(MAX) column and rename VARBINARY(255) column to the name the VARCHAR(MAX) column had been. Not being a DB admin this has gotten past my "pay grade" so to speak. My mail is working and I receive the emails with emoji's in the subject, there are just errors in the logs. Not knowing what the actual repercussions of the errors are if any, I am going to let it be unless someone more knowledgeable in SQL than I am can provide syntax to perform the conversion. Perhaps this can be addressed in a later version if it is actually causing any harm or preventing a function from being properly performed. Thanks again! |
Impacted versions
Steps to reproduce
Clear setup and try to get email.
Current behavior
Get following error in mail.log:
Nov 8 16:41:05 mail2 amavis[11816]: (11816-04) (!)WARN save_info_final: sql exec: err=, , Wide character in subroutine entry at (eval 123) line 169.
Nov 8 16:41:08 mail2 amavis[11816]: (11816-04) (!)WARN save_info_final: sql exec: err=, , Wide character in subroutine entry at (eval 123) line 169.
Nov 8 16:41:11 mail2 amavis[11816]: (11816-04) (!)WARN save_info_final: sql exec: err=, , Wide character in subroutine entry at (eval 123) line 169.
Nov 8 16:41:14 mail2 amavis[11816]: (11816-04) (!)WARN save_info_final: sql exec: err=, , Wide character in subroutine entry at (eval 123) line 169.
Nov 8 16:41:14 mail2 amavis[11816]: (11816-04) (!!)ERROR sql_storage: too many retries on storing final, info not saved
Expected behavior
Video/Screenshot link (optional)
The text was updated successfully, but these errors were encountered: