Container restart breaks email sending

Question

Container restart breaks email sending

tpimh opened this issue 2 years ago · comments

I have been testing this image for a while, and it seems to work just fine. However, if the container is stopped, then started again, it causes the outgoing mail to fail with error 451 4.3.0 Temporary lookup failure. I'm not really sure what exactly is causing this, so could anyone please try to reproduce it like this:

Create new iRedMail container
Send test email (should be fine)
Restart the container
Send test email (should fail with error 451)

If the container is removed, then a new container is created with the same persistent volumes, sending emails is possible again until next restart.

tensor5g · Answer 1 · Mon Apr 04 2022 23:09:57 GMT+0800 (China Standard Time)

I have noticed this too. You always have to delete/start the container. Restart never works.

Adam Roth · Answer 2 · Sun Aug 21 2022 03:15:27 GMT+0800 (China Standard Time)

It looks like it's because of random password generation after each start of the container.
I found that vmail db password is not updated in some (maybe all) postfix configuration.

Adam Roth · Answer 3 · Mon Aug 22 2022 05:38:50 GMT+0800 (China Standard Time)

I defined all passwords in ENV vars and it works as long as you start amavis manually (#113).

iRedMail · Answer 4 · Sat Aug 27 2022 10:58:37 GMT+0800 (China Standard Time)

Could you please give me a detailed step-by-step instruction (with each shell commands you ran) to reproduce this issue? @tpimh @tensor5g

I don't know how to reproduce it, hence cannot "fix" it at all.

Teresa · Answer 5 · Mon Oct 03 2022 01:45:56 GMT+0800 (China Standard Time)

It appears the same problem is happening to me too.
Basically just use this guide https://hub.docker.com/r/iredmail/mariadb
and restart the container using
docker restart containerId
and in the built in roundcube you should observe "failed to add recipient: temp look up failure" when sending the email

Ricahrd Fan · Answer 6 · Thu Oct 20 2022 15:05:29 GMT+0800 (China Standard Time)

Hi, I have the same problem. could you please help

iRedMail · Answer 7 · Thu Oct 20 2022 15:29:29 GMT+0800 (China Standard Time)

Does using fixed SQL passwords fix the issue?

Ricahrd Fan · Answer 8 · Thu Oct 20 2022 19:13:02 GMT+0800 (China Standard Time)

Does using fixed SQL passwords fix the issue?

i set the VMAIL_DB_PASSWORD and it's ok now

homuraLan · Answer 9 · Thu Aug 24 2023 11:23:41 GMT+0800 (China Standard Time)

Could you please give me a detailed step-by-step instruction (with each shell commands you ran) to reproduce this issue? @tpimh @tensor5g

I don't know how to reproduce it, hence cannot "fix" it at all.

I know this error, it should be caused by Postfix being unable to connect to the database. I filtered the logs once, but now I forget how to proceed https://serverfault.com/questions/506347/postfix-temporary-lookup-failure

tobiasfaust · Answer 10 · Sun Feb 18 2024 19:09:01 GMT+0800 (China Standard Time)

seems like #23 and #123
I have the exactly same problem. I want this fency feature to use new passwords after a container reboot.
New passwords can be found here: /root/.my-cnf-*
But all vmail passwords in /etc/postfix/mysql/* are NOT updated.
Amavis password in file /etc/amavis/conf.d/50-user also not

So i have to do that manually :( I think thats an mistake in iredmail docker code??

tobiasfaust · Answer 11 · Sat Jun 08 2024 17:23:07 GMT+0800 (China Standard Time)

Hi @iredmail
any news on it? today we had a power shutdown and after reappear the power and restarting the container all passwords are randomly changed. New passwords are in in sync at:

nano /docker/entrypoints/settings.conf
/root/.my-cnf-*
So far, so good....

But all passwords in /etc/postfix/mysql/* are NOT updated.
Amavis password in file /etc/amavis/conf.d/50-user also not