Trying to get Greylisting setup & now no longer accepting emails from external domains.

Submitted by DenisCroombs on Sun, 01/29/2012 - 13:43 Pro Licensee

I have had to reinstall my virtualmin pro system and am trying to get Greylisting setup, it always worked for me before but now when I try and enable it, I get:- Enabling Greylisting

Enabling Postgrey at boot time .. .. already enabled

Starting Postgrey server .. .. started OK

Configuring Postfix to use Postgrey .. .. configured to use port

<- Return to greylisting options

When I select return to greylisting options I get:-

Email Greylisting

Greylist is a technique to reduce spam by initially rejecting email the first time another mail server tries to contact your server. Real mail servers will re-try after a short delay, but those operated by spammers typically will not. Thus legitimate email still gets delivered, but spam does not.

Greylisting is not currently fully enabled on your system. Click this button to have Virtualmin configure it.

Operating system CentOS Linux 5.7 Perl version 5.008008 Path to Perl /usr/bin/perl BIND version 9.3.6 Postfix version 2.3.3 Mail injection command /usr/lib/sendmail -t Apache version 2.2.3 PHP version 5.1.6 Webalizer version 2.01-10 Logrotate version 3.7.4 MySQL version 5.0.77 ProFTPd version 1.33 SpamAssasssin version 3.3.1 ClamAV version 0.97.3

Virtualmin 3.89 (installed 23/Jan/2012) which has been fully updated with all available updates.

Any clues why this may be not working for me as it is driving me nuts? Thanks Denis

I have also now realised that the server is no longer accepting emails fromoff the server but is sending them, so far no boundbacks to test emails I have sent to the server, help the /var/log/maillog is also emply for this week so far !

Status: 
Active

Comments

Submitted by andreychek on Sun, 01/29/2012 - 13:50

Howdy -- it sounds like Postgrey is working, but that Virtualmin isn't seeing it enabled at bootup.

If you go into Webmin -> System -> Bootup and Shutdown, is Postgrey set to start at bootup?

Submitted by DenisCroombs on Sun, 01/29/2012 - 13:51 Pro Licensee

Hi

Thanks, let me check, 2 secs

Denis

Submitted by DenisCroombs on Sun, 01/29/2012 - 13:54 Pro Licensee 

postfix     Yes     Postfix is a Mail Transport Agent, which is the program that moves mail from one machine to another.
postgresql  No  Starts and stops the PostgreSQL backend daemon that handles all database requests.
postgrey    Yes     Postfix Greylisting Policy Server

So it looks correct ?

(cut from menu)

Denis

Submitted by DenisCroombs on Sun, 01/29/2012 - 13:56 Pro Licensee

I just tried to re-start postgrey

Executing /etc/rc.d/init.d/postgrey restart ..

Stopping postgrey: [FAILED] Starting postgrey: no connection to syslog available - /dev/log is not a socket at /usr/lib/perl5/vendor_perl/5.8.8/Net/Server.pm line 1267 [ OK ]

Was the result

Denis

Submitted by DenisCroombs on Sun, 01/29/2012 - 14:20 Pro Licensee

Hi

I have been digging deeper and just tried a boot,no change and my /var/log/procmail.log has below

Folder: /home/croombs/homes/denis/Maildir/new/1327865452.13370_0.sue 1453 Time:1327865452 From:root@sue.justemail.org To:denis@croombs.org User:denis.croombs Size:1507 Dest:/home/croombs/homes/denis/Maildir/new/1327865452.13370_0.sue.justemail.org Mode:None From MAILER-DAEMON Sun Jan 29 14:44:07 2012 Subject: Undelivered Mail Returned to Sender Folder: /home/billing/homes/tgarcia/Maildir/new/1327866247.14522_1.s 2720 Time:1327866247 From:MAILER-DAEMON@sue.justemail.org To:tgarcia@jdtmedicalbilling.com User:tgarcia.jdtmedicalbilling Size:2766 Dest:/home/billing/homes/tgarcia/Maildir/new/1327866247.14522_1.sue.justemail.org Mode:None From overton-biodiversity@sue.justemail.org Sun Jan 29 15:16:02 2012 Subject: Cron <overton-biodiversity@sue> /home/overton-biodiversity/.usermin/m Folder: /home/overton-biodiversity/Maildir/new/1327868162.2202_1.sue 939 Time:1327868164 From:root@sue.justemail.org To:overton-biodiversity@sue.justemail.org User:overton-biodiversity Size:1010 Dest:/home/overton-biodiversity/Maildir/new/1327868162.2202_1.sue.justemail.org Mode:None

Submitted by DenisCroombs on Sun, 01/29/2012 - 14:27 Pro Licensee

I have also now found out that webmail users are getting the error:-

Error connecting to IMAP server: localhost. 111 : Connection refused

Any clues?

PS I have not make any changes recently since I tried the postgrey setup

Thanks Denis

Submitted by DenisCroombs on Sun, 01/29/2012 - 14:35 Pro Licensee

HI

OK, I now fixed the "Error connecting to IMAP server: localhost. 111 : Connection refused" issue as dovecot was not setup tostart fromboot. But other issues still exist

Denis

Submitted by andreychek on Sun, 01/29/2012 - 14:37

It sounds like you're getting some unusual errors when trying to launch Postgrey.

Are you using a dedicated server, or a VPS?

And how much RAM do you have? You can determine that by running "free -m".

One thing that may help is to restart Syslog.

But if that doesn't do the trick, I may need to log in myself and take a look to try and determine what's going on.

Submitted by DenisCroombs on Sun, 01/29/2012 - 14:46 Pro Licensee

Dedicated server with 2gb ram

[root@sue log]# service syslog restart Shutting down kernel logger: [FAILED] Shutting down system logger: [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ]

So syslog was not running & was not setup tostart on boot,now that is fixed.

and my maillog is now filling up :-Jan 29 15:41:31 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:31 sue postfix/smtpd[4753]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:31 sue postfix/smtpd[4754]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:31 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4747]: connect from 87-205-190-16.adsl.inetia.pl[87.205.190.16] Jan 29 15:41:32 sue postfix/smtpd[4745]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4751]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4749]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4752]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4753 exit status 1 Jan 29 15:41:32 sue postfix/master[2991]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Jan 29 15:41:32 sue postfix/smtpd[4750]: connect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:32 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4754 exit status 1 Jan 29 15:41:32 sue postfix/smtpd[4750]: disconnect from ng3-ip8.bullet.mail.ne1.yahoo.com[98.138.215.133] Jan 29 15:41:33 sue postfix/smtpd[4750]: connect from qmta08.westchester.pa.mail.comcast.net[76.96.62.80] Jan 29 15:41:33 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4745 exit status 1 Jan 29 15:41:33 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4751 exit status 1 Jan 29 15:41:33 sue postfix/smtpd[4750]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:33 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4749 exit status 1 Jan 29 15:41:33 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4752 exit status 1 Jan 29 15:41:34 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4750 exit status 1 Jan 29 15:41:34 sue postfix/smtpd[4747]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:35 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4747 exit status 1 Jan 29 15:41:38 sue postfix/smtpd[4748]: fatal: 127.0.0.1:: missing service information Jan 29 15:41:39 sue postfix/master[2991]: warning: process /usr/libexec/postfix/smtpd pid 4748 exit status 1

If you wish to login please let me know

Thanks for all of the help

Denis

Submitted by DenisCroombs on Sun, 01/29/2012 - 14:55 Pro Licensee

Ok, now I have been able to get Greylisting working using the UI and email now flowing. But now I am confused why these services were notstarting up on re-boot when I have never hadtochange these settings before.

But It now looks like i have a working system, thanks for the great assistance as always.

Denis

Submitted by andreychek on Sun, 01/29/2012 - 15:41

By default, all those services should start up by default. Are you seeing any errors during the bootup process?

Also, if you look in /var/log/maillog after restarting Postfix (/etc/init.d/postfix restart), does it start up okay, or are you seeing errors?

Submitted by DenisCroombs on Sun, 01/29/2012 - 15:52 Pro Licensee

Hi

Having started syslog, postfix, postgrey & dovecot all started working. I have now gone through and verified that all are now set to start on boot and all looks good, I am just a bit confused as I have never had to do this on other virtuilmin server installs.

But thanks for your great help

Denis

Submitted by andreychek on Mon, 01/30/2012 - 19:14

I'm glad that's all setup correctly now!

I'm not sure how that might have occurred though, the default on a new installation would be for all those to be setup to boot by default.

The only other thought I have, did your default run level by chance change?

You can determine the current run level by running this command:

ps auxw | grep init

On CentOS 5, I believe the default run level would be 3.