1

Topic: After a reboot, email is no longer received

==== Provide required information ====
- iRedMail version and backend (LDAP/MySQL/PGSQL):
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

iRedMail-0.8.1 MySQL
CentOS 6
Linux galeweb.utahgale.com 2.6.32-220.23.1.el6.x86_64 #1 SMP Mon Jun 18 18:58:52 BST 2012 x86_64 x86_64 x86_64 GNU/Linux

With much help from this site, I was able to receive and deliver email.  Then after a reboot, email stopped being received.

When I send emails to the server, they appear to be sent and no undeliverable email messages are received.  No errors are appearing in the maillog or messages files.  It is like they are not reaching the server.  However when I can the ports on the server, I get the following:

207.108.170.78 is responding on port 110 (pop3).

207.108.170.78 is responding on port 143 (imap).

207.108.170.78 is responding on port 993 (imaps).

207.108.170.78 is responding on port 995 (pop3s).

207.108.170.78 isn't responding on port 2000 (sieve).

Any ideas?

----

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

2

Re: After a reboot, email is no longer received

Emails that are being sent are no longer being delivered to the server.  No errors are being reported on the sending side or in my logs.

I created another post since this issue does not seem to be related to different versions of plugins.  The new post is "After reboot, email is no longer received".  We can continue to use this thread if you like or switch to the new one.  I will post this to both.  Your choice which one we use.

iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
fail2ban-dovecot  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 80,443,25,587,110,995,143,993,4190
fail2ban-postfix  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 80,443,25,587,110,995,143,993,4190
fail2ban-ssh  tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:22
fail2ban-roundcube  tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 80,443,25,587,110,995,143,993,4190
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:21
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:80
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:137
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:138
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:139
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:445
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:631
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:631
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpt:1194
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 25,110,143,443,587,993,995,2000,10000
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           multiport dports 25,110,143,443,587,993,995,2000,10000
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         state NEW udp dpt:5353
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpts:5800:5802
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpts:5800:5802
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpts:5900:5902
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           state NEW udp dpts:5900:5902
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain fail2ban-dovecot (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-postfix (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-roundcube (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain fail2ban-ssh (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

3

Re: After a reboot, email is no longer received

I have started to get failure emails from yahoo from emails I tried to send yesterday indicating that it was unable to make an SMTP connection.  I have re-installed since then but even a failure gives some information.

Sorry, I wasn't able to establish an SMTP connection. (#4.4.1)
I'm not going to try again; this message has been in the queue too long.

4

Re: After a reboot, email is no longer received

- Any log in Postfix log file (/var/log/maillog)?
- Is Amavisd service running? Check it with below command:

# /etc/init.d/amavisd status

- Is iRedAPD service running? Check it:

# /etc/init.d/iredapd status

- Is Policyd running? Check it:

# /etc/init.d/policyd status

5

Re: After a reboot, email is no longer received

amavisd is running

/etc/init.d/amavisd status
amavisd (pid 2995 2994 2018) is running...

/etc/init.d/iredapd status
iredapd is running.

/etc/init.d/policyd status
policyd (pid  2583) is running...

6

Re: After a reboot, email is no longer received

Port scans show that my server is not listening (responding) on port 25.  I have checked and rechecked the configuration and it certainly looks like it should.  I found that my ISP was doing port 25 filtering but I have had that turned off with no change.  I have verified that my router is allowing port 25 traffic and the iptables are configured to allow port 25 traffic.

Any suggestions?

7

Re: After a reboot, email is no longer received

Dear galew,

You forgot the most import thing mentioned in my previous reply:

- Any log in Postfix log file (/var/log/maillog)?

8

Re: After a reboot, email is no longer received

Sorry I haven't seen any errors in maillog.  The only messages that keep coming up that I'm not sure of are:

Jul  4 12:02:06 galeweb postfix/smtpd[28461]: connect from unknown[207.108.170.78]
Jul  4 12:03:21 galeweb postfix/smtpd[28461]: disconnect from unknown[207.108.170.78]
Jul  4 12:06:41 galeweb postfix/anvil[28465]: statistics: max connection rate 1/60s for (smtp:207.108.170.78) at Jul  4 12:02:06
Jul  4 12:06:41 galeweb postfix/anvil[28465]: statistics: max connection count 1 for (smtp:207.108.170.78) at Jul  4 12:02:06
Jul  4 12:06:41 galeweb postfix/anvil[28465]: statistics: max cache size 1 at Jul  4 12:02:06

201.108.170.78 is the external IP address for my server.

Should port scans of my server show port 25 listening?  I always thought that port 25 was used for outgoing email but apparently it is required for smtp connections from other email servers.  I am checking with my ISP to make sure that it is actually open.

9

Re: After a reboot, email is no longer received

My ISP has verified that port filtering is off and that when it is on, it only affects outgoing traffic.  So I am back where I started.  I am still receiving emails from yahoo indicating that they are unable to establish an SMTP connection.

10

Re: After a reboot, email is no longer received

Solved:  Apparently my ISP did change the filtering after upgrading my service.  When I changed it back, the information never got communicated to my DSL modem.  I powered off the modem and the router and when I turned them back on, everything worked fine.

Thanks for all your help.