Re: Getting greylisting going on a new Debian

If its is not broken, can you explain this?

The first email goes out fine as I sent to the receipiant earlier, the second temp fails....

If I remove the milter from sendmail.mc and re-compile email works fine, so its not sendmail as far as I can tell.

Could it be the database not responding fast enough? which would be strange as this is a lot faster machine than the old...

hermes:/etc/mail# tail -f /var/log/mail.log
Jun 27 10:30:30 hermes sm-mta[15524]: restarting /usr/sbin/sendmail-mta due to signal
Jun 27 10:30:30 hermes sm-mta[12534]: starting daemon (8.13.8): SMTP+queueing@00:10:00
Jun 27 10:31:10 hermes fetchmail[21303]: awakened at Fri 27 Jun 2008 10:31:10 NZST
Jun 27 10:31:14 hermes fetchmail[21303]: sleeping at Fri 27 Jun 2008 10:31:14 NZST for 900 seconds
Jun 27 10:31:36 hermes sm-mta[12551]: m5QMVa5J012551: from=<[email protected]>, size=410, class=0, nrcpts=1, msgid=<[email protected]>, proto=ESMTP, daemon=MTA-v4, relay=[192.168.1.108]
Jun 27 10:31:36 hermes sm-mta[12551]: m5QMVa5J012551: Milter add: header: X-Virus-Scanned: ClamAV 0.93.1/7574/Fri Jun 27 09:01:05 2008 on hermes
Jun 27 10:31:36 hermes sm-mta[12551]: m5QMVa5J012551: Milter add: header: X-Virus-Status: Clean
Jun 27 10:31:42 hermes sm-mta[12555]: m5QMVa5J012551: to=<[email protected]>, ctladdr=<[email protected]> (1000/1000), delay=00:00:06, xdelay=00:00:06, mailer=esmtp, pri=120410, relay=vuwunicomx00002.vuw.ac.nz. [130.195.86.22], dsn=2.0.0, stat=Sent (2.0.0 m5QMT8V5003004 Message accepted for delivery)
Jun 27 10:32:05 hermes sm-mta[16829]: m5QMW4RO016829: Milter: to=<[email protected]>, reject=451 4.7.1 Please try again later (TEMPFAIL)
Jun 27 10:32:07 hermes sm-mta[16829]: m5QMW4RO016829: from=<[email protected]>, size=339, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=[192.168.1.108]