1

Topic: Mail Server Stuck

==== Required information ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version: Red Hat
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- Related log if you're reporting an issue:
====

Hello we are experiencing a weird issue that we have had before that resolved itself last time.

Our installation has been working fine since January/February but just now the server has become unresponsive. I have to restart the server fully (as in complete reboot) for it to become responsive. Which it does for a couple of minutes and then stops working again until I restart the server again.

Does anyone know what this could be or how to fix it? You would be an absolute hero if you can help.

We have other servers (just running either MySQL/Apache) in the same datacentre that are unaffected.

----

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

2

Re: Mail Server Stuck

*) It's unclear what you mean "unresponsive". HTTP service (webmail, etc)? IMAP? POP3? SMTP? Or all of them?

*) If all services are not responsive, check iptables firewall, make sure your client IP addresses are not blocked.

*) Is it a busy server with many IMAP users? If so, try to increase the concurrent IMAP processes like below:

service imap-login {
    ...
    process_limit = 1000
    ...
}

3

Re: Mail Server Stuck

Hello, thanks for your quick response.

It was everything that was unresponsive. It looks like for some reason our IP address is blocked as it can be accessed from other internet connections.

Is there a way to whitelist IP addresses so they won't be blocked?

4

Re: Mail Server Stuck

daveis.91 wrote:

Is there a way to whitelist IP addresses so they won't be blocked?

Add your IP address(es) and IP network in /etc/fail2ban/jail.local (Warning: not jail.conf), restarting fail2ban service.