1 Topic by ThermalSloth (edited by ThermalSloth 2012-03-22 17:16:28)

  • ThermalSloth
  • Member
  • Offline
  • Registered: 2012-03-22
  • Posts: 4

Topic: Can't receive e-mail, greylisting disabled, MX records set properly.

Hello,

I installed iRedMail a while back on my Ubuntu server, and it worked fine.
However, I switched to Debian 6.0 not too long ago, and when I installed iRedMail I noticed that I couldn't receive e-mails anymore.

My MX records are set properly (I didn't change them, and they worked fine when running on Ubuntu 10.04 LTS).
I'm currently running Debian 6.0 with iRedMail 0.7.4, on a MySQL backend.

I can send e-mails just fine,
but whenever I try to send an e-mail to my server, after (half) a day I'll get a reply with 'undelivered mail returned to sender'.

I'm really hoping you can help me, and thank you in advance.

edit:
I should also add that I disabled greylisting.

----

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: 30,787

Re: Can't receive e-mail, greylisting disabled, MX records set properly.

Any related log in Postfix log file (/var/log/mail.info)?

3 Reply by ThermalSloth (edited by ThermalSloth 2012-03-22 20:12:57)

  • ThermalSloth
  • Member
  • Offline
  • Registered: 2012-03-22
  • Posts: 4

Re: Can't receive e-mail, greylisting disabled, MX records set properly.

After a 'cat /var/log/mail.info | grep "Mar 22" > mail.log' ...

Attached to my post.

Post's attachments

mail.log 132.56 kb, 2 downloads since 2012-03-22 

You don't have the permssions to download the attachments of this post.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,787

Re: Can't receive e-mail, greylisting disabled, MX records set properly.

Please, try to find out related log yourself, don't be lazy.

Just checked last 10 lines in your log file, it says:

Mar 22 13:07:46 ks384120 postfix/smtpd[16166]: warning: connect to 127.0.0.1:10031: Connection refused

That means you don't have Policyd running. Please start it and test again.

# /etc/init.d/postfix-policyd restart

5 Reply by ThermalSloth (edited by ThermalSloth 2012-03-23 22:54:55)

  • ThermalSloth
  • Member
  • Offline
  • Registered: 2012-03-22
  • Posts: 4

Re: Can't receive e-mail, greylisting disabled, MX records set properly.

ZhangHuangbin wrote:

Please, try to find out related log yourself, don't be lazy.

Just checked last 10 lines in your log file, it says:

Mar 22 13:07:46 ks384120 postfix/smtpd[16166]: warning: connect to 127.0.0.1:10031: Connection refused

That means you don't have Policyd running. Please start it and test again.

# /etc/init.d/postfix-policyd restart

Heh, sorry, I'm at my internship right now, and I'm doing all the commands through my phone, which is a pain in the bottom..

I'll restart the service and let you know if it fixed it.

edit:
I'm being a derp.

# /usr/sbin/postfix-policyd restart
starting policyd v1.82
Segmentation fault

6 Reply by ThermalSloth

  • ThermalSloth
  • Member
  • Offline
  • Registered: 2012-03-22
  • Posts: 4

Re: Can't receive e-mail, greylisting disabled, MX records set properly.

Shameless bump, I still need help solving this issue..
Google hasn't helped me any further than I am right now.


# /usr/sbin/postfix-policyd restart
starting policyd v1.82
Segmentation fault

7 Reply by robert

  • robert
  • Member
  • Offline
  • Registered: 2012-07-01
  • Posts: 17

Re: Can't receive e-mail, greylisting disabled, MX records set properly.

I had the same problem and I believe that it is now solved.  Here is what i did.

---I have a fresh install using the directions at this link:
http://www.howtoforge.com/iredmail-0.7. … an-squeeze

---I believe that policyd is turned off as it is commented out in /etc/postfix/main.cf
#
# Uncomment the following line to enable policyd sender throttle.
#
#smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10032


---However when I look at the /var/log/mail.log:
Jun 30 12:23:25 mail postfix/smtpd[31140]: warning: connect to 127.0.0.1:10031: Connection refused
Jun 30 12:23:25 mail postfix/smtpd[31140]: warning: problem talking to server 127.0.0.1:10031: Connection refused

---Tried to reinstall policyd with no affect
apt-get --reinstall install postfix-policyd

---I have rremoved (database and all) and reinstalled policyd
apt-get remove postfix-policyd
apt-get install postfix-policyd

---Restart policyd
/etc/init.d/postfix-policyd restart
Restarting Postfix greylisting policy daemon: postfix-policyd.

This had no other output

---Restarted it directly and got the segmentation fault
/usr/sbin/postfix-policyd restart
starting policyd v1.82
Segmentation fault

---upgraded
apt-get update
apt-get dist-upgrade

---rebooted all the iRedMail processes
for i in rsyslog  apache2 postfix mysql slapd postfix-policyd dovecot amavis clamav-daemon clamav-freshclam cron iredapd iptables; do /etc/init.d/${i} restart; done
Stopping enhanced syslogd: rsyslogd.
Starting enhanced syslogd: rsyslogd.
Restarting web server: apache2 ... waiting .
Stopping Postfix Mail Transport Agent: postfix.
Starting Postfix Mail Transport Agent: postfix.
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld.
Checking for corrupt, not cleanly closed and upgrade needing tables..
Stopping OpenLDAP: slapd.
Starting OpenLDAP: slapd.
Restarting Postfix greylisting policy daemon: postfix-policyd.
Restarting IMAP/POP3 mail server: dovecot.
Stopping amavisd: amavisd-new.
Starting amavisd: amavisd-new.
Stopping ClamAV daemon: clamd.
Starting ClamAV daemon: clamd .
Stopping ClamAV virus database updater: freshclam.
Starting ClamAV virus database updater: freshclam.
Restarting periodic command scheduler: cron.
Stopping iredapd ...
Starting iredapd ...
Flushing firewall rules: iptables.
Setting chains to policy ACCEPT: filter.
Unloading iptables modules.
Applying iptables firewall rules:.

---I now get
lsof -i :10031
COMMAND   PID    USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
postfix-p 532 policyd    6u  IPv4  81563      0t0  TCP localhost:10031 (LISTEN)