1 Topic by Stephen77

  • Stephen77
  • Member
  • Offline
  • Registered: 2018-07-30
  • Posts: 19

Topic: Have just done upgrade to latest EE 1.4 and now cant send emails

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 20250701101
- Deployed with iRedMail Easy or the downloadable installer? EE
- Linux/BSD distribution name and version: Ubuntu 22.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): NGinx
- Manage mail accounts with iRedAdmin-Pro? EE
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Have just upgraded to the latest version of EE1.4 and now am unable to send emails from any account.  It is saying wrong username and password but I don’t believe that is the vase as is receiving emails fine.  I think it might be to do with the new dkim feature so turned that off and restarted server but still unable to send.  Can we downgrade to the prior version?  What email do I use for support?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,409

Re: Have just done upgrade to latest EE 1.4 and now cant send emails

Any related error in /var/log/syslog and /var/log/milter/milter.log?

3 Reply by ChrisHodg

  • ChrisHodg
  • Member
  • Offline
  • Registered: 2016-08-11
  • Posts: 12

Re: Have just done upgrade to latest EE 1.4 and now cant send emails

Seeing the same here.

milter.log is showing

2025-07-11 10:17:49 ERROR listen tcp 127.0.0.1:7791: bind: address already in use

netstat shows 7791 being used by

tcp        0      0 127.0.0.1:7791          0.0.0.0:*               LISTEN      889/uwsgi

syslog shows

2025-07-11T10:20:02.196761+01:00 mail systemd[1]: milter.service: Scheduled restart job, restart counter is at 77.
2025-07-11T10:20:02.213367+01:00 mail systemd[1]: Started milter.service - milter - iRedMail Milter.
2025-07-11T10:20:02.424974+01:00 mail systemd[1]: milter.service: Main process exited, code=exited, status=255/EXCEPTION
2025-07-11T10:20:02.425074+01:00 mail systemd[1]: milter.service: Failed with result 'exit-code'.

4 Reply by ChrisHodg

  • ChrisHodg
  • Member
  • Offline
  • Registered: 2016-08-11
  • Posts: 12

Re: Have just done upgrade to latest EE 1.4 and now cant send emails

As a temporary fix so the server sends and receives email again, I have done the following to change the port for the new milter

Edit /opt/milter/settings.json and change the port

"listen": "127.0.0.1:7799",

You will of course need to tell postfix too.

Edit /etc/postfix/main.cf

smtpd_milters = inet:127.0.0.1:7799
non_smtpd_milters = inet:127.0.0.1:7799

Restart services
sudo systemctl restart milter.service
sudo systemctl restart postfix


This is what worked for me while I have a better look at things.

Worth pointing out I'm now setting other errors in
/var/log/milter/milter.log

2025-07-11 11:02:05 ERROR Error while applying plugin dkim: Error 1146 (42S02): Table 'vmail.dkim' doesn't exist






ChrisHodg wrote:

Seeing the same here.

milter.log is showing

2025-07-11 10:17:49 ERROR listen tcp 127.0.0.1:7791: bind: address already in use

netstat shows 7791 being used by

tcp        0      0 127.0.0.1:7791          0.0.0.0:*               LISTEN      889/uwsgi

syslog shows

2025-07-11T10:20:02.196761+01:00 mail systemd[1]: milter.service: Scheduled restart job, restart counter is at 77.
2025-07-11T10:20:02.213367+01:00 mail systemd[1]: Started milter.service - milter - iRedMail Milter.
2025-07-11T10:20:02.424974+01:00 mail systemd[1]: milter.service: Main process exited, code=exited, status=255/EXCEPTION
2025-07-11T10:20:02.425074+01:00 mail systemd[1]: milter.service: Failed with result 'exit-code'.

5 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,409

Re: Have just done upgrade to latest EE 1.4 and now cant send emails

ChrisHodg wrote:

Worth pointing out I'm now setting other errors in
/var/log/milter/milter.log
2025-07-11 11:02:05 ERROR Error while applying plugin dkim: Error 1146 (42S02): Table 'vmail.dkim' doesn't exist

This is a bug, please fix it with steps below:

1) Run command to stop and disable "iredadmin" service which is listening on port 7791

systemctl disable --now iredadmin

2) Rename all "*.pem.bak" files under /opt/iredmail/custom/amavisd/dkim/ back to "*.pem".
3) Re-download EE v1.4.0 and re-perform the full deployment ("Deployments" -> "Re-perform full deployment").

If you're not familiar with above operations, contact us to get it done via ssh, reach us via the ticket on iRedMail Store website:
https://store.iredmail.org/

I will login from static IP 139.162.146.87 with ssh public key:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFxyXNDgR+hyH99430eBMmTK+/Y9DwLZdPfWYU5P1iyM zhb@iredmail.org

6 Reply by subarticThrone (edited by subarticThrone 2025-07-11 23:26:34)

  • subarticThrone
  • Member
  • Offline
  • Registered: 2025-02-26
  • Posts: 13

Re: Have just done upgrade to latest EE 1.4 and now cant send emails

ZhangHuangbin wrote:
ChrisHodg wrote:

Worth pointing out I'm now setting other errors in
/var/log/milter/milter.log
2025-07-11 11:02:05 ERROR Error while applying plugin dkim: Error 1146 (42S02): Table 'vmail.dkim' doesn't exist

This is a bug, please fix it with steps below:

1) Run command to stop and disable "iredadmin" service which is listening on port 7791

systemctl disable --now iredadmin

2) Rename all "*.pem.bak" files under /opt/iredmail/custom/amavisd/dkim/ back to "*.pem".
3) Re-download EE v1.4.0 and re-perform the full deployment ("Deployments" -> "Re-perform full deployment").

If you're not familiar with above operations, contact us to get it done via ssh, reach us via the ticket on iRedMail Store website:
https://store.iredmail.org/


I will login from static IP 139.162.146.87 with ssh public key:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFxyXNDgR+hyH99430eBMmTK+/Y9DwLZdPfWYU5P1iyM zhb@iredmail.org



Huangbin - I too am having the same type of issues; I followed the steps suggested above however I am not seeing any resolution even after a reboot. I tried this about 2 hours ago without success.

7 Reply by ChrisHodg

  • ChrisHodg
  • Member
  • Offline
  • Registered: 2016-08-11
  • Posts: 12

Re: Have just done upgrade to latest EE 1.4 and now cant send emails

Thank you Zhang.

Everything is working correctly now.

Cheers

Chris