1 (edited by Akiba 2020-01-17 21:45:10)

Topic: "SOLVED" Postmaster unreachable on Iredadmin

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.0
- Deployed with iRedMail Easy or the downloadable installer? Installer
- Linux/BSD distribution name and version: Linux mail 5.0.0-37-generic #40~18.04.1-Ubuntu
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No.
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
postmaster@mydomain.com is unreachable on Iredadmin. I am able to login and use iredadmin with another user on a different domain who has admin privileges.
Possible hints:
• I have a long password for the postmaster account.
• Failed postmaster login attempts are not registered on the iredadmin log panel.
• systemctl status iredapd.service shows:
iredapd.service: Can't open PID file /run/iredapd.pid (yet?) after start: No such file or directory
• fail2ban is not logging new events to /var/log/fail2ban.log; last logs on fail2ban.log1 are more than a week old
• clamav.log, iredapd.log are zero-length
Everything was working OK until I had to restart services having changed some max email size settings. Services are not starting normally. I have to restart amavisd-new on every reboot or it shows errors.
I'm not sure what is happening. I've been trying to follow advice on this forum and have upgraded to iredapd 1.0.

----

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

2

Re: "SOLVED" Postmaster unreachable on Iredadmin

- How much memory does this server have?
- Does (failed) postmaster account have special characters in password? How about reset its password to a simple one just for testing purpose (and reset it to a strong one after test)?
- About the empty log files, please restart "rsyslog" service to fix it.

3 (edited by Akiba 2020-01-02 04:48:19)

Re: "SOLVED" Postmaster unreachable on Iredadmin

Thank you @ZhangHuangbin — I can login with postmaster now

ZhangHuangbin wrote:

- How much memory does this server have?

              total        used        free      shared  buff/cache   available
Mem:           3.8G        1.6G        1.1G         16M        1.2G        2.2G
Swap:          3.0G          0B        3.0G
ZhangHuangbin wrote:

- Does (failed) postmaster account have special characters in password? How about reset its password to a simple one just for testing purpose (and reset it to a strong one after test)?

Yes, it did have special chars, so I have removed them from the password. It's still long, but no special chars. After changing pswd I managed to log in. I am not sure what eventually did the trick, because I had disabled the throttle plugin and restarted some services before checking again. Or it just the fact that the password was changed. My other account uses a password with special characters (a little shorter though) and there isn't a problem. I can't use a short password for a user with known name, because it's a security risk. Ideally, admins should be able to name their global admin user at install. What's the best way to replace postmaster? Would it be OK to demote postmaster to ordinary user status and give global admin privileges to another user?

ZhangHuangbin wrote:

- About the empty log files, please restart "rsyslog" service to fix it.

before restarting it showed:

Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
Dec 31 21:44:23 mail rsyslogd[774]: action 'action 6' suspended (module 'builtin:omfile'), next retry is Tue Dec 31 21:44:53 2019, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
Jan 01 06:26:04 mail rsyslogd[774]:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="774" x-info="http://www.rsyslog.com"] rsyslogd

Now status shows:

Jan 01 19:34:37 mail systemd[1]: Starting System Logging Service...
Jan 01 19:34:37 mail systemd[1]: Started System Logging Service.
Jan 01 19:34:37 mail rsyslogd[28514]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.32.0]
Jan 01 19:34:37 mail rsyslogd[28514]: rsyslogd's groupid changed to 106
Jan 01 19:34:37 mail rsyslogd[28514]: rsyslogd's userid changed to 102
Jan 01 19:34:37 mail rsyslogd[28514]:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="28514" x-info="http://www.rsyslog.com"] start

But the following logs are still 0-length in /var/log: alternatives.log, fail2ban.log, kern.log, clamav/clamav.log, dovecot/dovecot.log, dovecot/sieve.log, iredapd/iredapd.log, mlmmjadmin/mlmmjadmin.log. I will look tomorrow. On the other hand journalctl -u fail2ban.service is working well.

4

Re: "SOLVED" Postmaster unreachable on Iredadmin

Akiba wrote:

What's the best way to replace postmaster? Would it be OK to demote postmaster to ordinary user status and give global admin privileges to another user?

postmaster@ is normally used in MTA notification emails as contact of server issue, so it's not recommended to remove it. But you're free to add more admin accounts.

5

Re: "SOLVED" Postmaster unreachable on Iredadmin

Having rummaged the system for any possible or imaginary errors and having corrected many an error, I have just stumbled upon the solution:

there was one letter missing in the postmaster's email address

It's f---ing solved.
One of those moments you feel both mad and happy.