451 4.7.1 Service unavailable

2,939 views
Skip to first unread message

L V Lammert (Omnitec Corp)

unread,
Dec 29, 2011, 2:41:49 PM12/29/11
to mailserv
Our 'problem child' mailserv installation started rejecting all
incoming email this morning - it appears that the milter-greylist is
not working properly [on 9323].

All incoming mail gets the 451 error, .. and maillog shows:

Dec 29 13:34:57 mail postfix/smtpd[25430]: NOQUEUE: milter-reject:
RCPT from <domain>.com[70.43.38.82]: 451 4.7.1 Service unavailable -
try again later;

I have tried rebooting the machine, same problem; do not see anything
indicative of an error in messages - how to isolate the problem???

Lee

Johan Allard

unread,
Dec 29, 2011, 3:20:56 PM12/29/11
to mail...@googlegroups.com
Hi Lee,

Are you sure this is updated to Mailserv properly?

milter-greylist was used in the last commercial mailserver but was ditched because of this flakiness. Mailserv uses sqlgrey instead that seems to be much more stable.

Cheers

Johan

L. V. Lammert

unread,
Dec 29, 2011, 3:24:00 PM12/29/11
to mail...@googlegroups.com
On Fri, 30 Dec 2011, Johan Allard wrote:

> Hi Lee,
>
> Are you sure this is updated to Mailserv properly?
>

Sorry, forgot to mention that this is a 4.7.6 paid installation.

> milter-greylist was used in the last commercial mailserver but was
> ditched because of this flakiness. Mailserv uses sqlgrey instead that
> seems to be much more stable.
>

They have not wanted to upgrade yet, .. but may have to if we can't get
this problem fixed.

Thanks!

Lee

Marcus Bointon

unread,
Dec 29, 2011, 3:36:41 PM12/29/11
to mail...@googlegroups.com, mail...@googlegroups.com
I had exactly this problem too. I disabled greylisting altogether until I migrated to 4.8, which at least allowed deliveries to work.

Sent from my iPhone

L. V. Lammert

unread,
Dec 29, 2011, 3:39:53 PM12/29/11
to mail...@googlegroups.com
On Thu, 29 Dec 2011, Marcus Bointon wrote:

> I had exactly this problem too. I disabled greylisting altogether until
> I migrated to 4.8, which at least allowed deliveries to work.
>

How can that be accomplished without breaking clamav? This appears to be
the section in main.cf:

milter_default_action = tempfail
milter_connect_macros = j {daemon_name} v _
milter_header_checks = pcre:/etc/postfix/milter_header_checks
header_checks = pcre:/etc/postfix/header_checks.pcre
smtpd_milters =
inet:127.0.0.1:9323
unix:/tmp/clamav-milter.sock


Would it be as simple as commenting out the 9323 line?

Lee

L. V. Lammert

unread,
Dec 29, 2011, 3:59:04 PM12/29/11
to mail...@googlegroups.com
On Thu, 29 Dec 2011, L. V. Lammert wrote:

> On Thu, 29 Dec 2011, Marcus Bointon wrote:
>
> > I had exactly this problem too. I disabled greylisting altogether until
> > I migrated to 4.8, which at least allowed deliveries to work.
> >
>

Actually, after killing the processes again and restarting with "-v" it
seemed to come back!!

Guess we will upgrade as soon as 5.0 is stable.

Thanks!

Lee

Marcus Bointon

unread,
Dec 29, 2011, 4:18:46 PM12/29/11
to mail...@googlegroups.com
On 29 Dec 2011, at 21:59, L. V. Lammert wrote:

> Actually, after killing the processes again and restarting with "-v" it
> seemed to come back!!

You'll find it will fail again.

> How can that be accomplished without breaking clamav? This appears to be
> the section in main.cf:
>
> milter_default_action = tempfail

I don't have the config any more, but I think it may have involved changing this default action to allow, rather than tempfailing (which is what the 4.7.1 errors are). I don't recall what I set it to, but it will be in the docs.

Marcus

Kasparens

unread,
Dec 30, 2011, 1:11:44 AM12/30/11
to mailserv
I have the same problem in 4.7.6 some time ago, and just disable
greylisting to continue work.I don't want to upgrade too but time
goes, everything changes and decided to upgrade on next week.

Happy New Year to all!!!!

David Gnojek

unread,
Jan 10, 2012, 2:03:38 PM1/10/12
to mail...@googlegroups.com
Hi,

yes there was problems with milter-greylist on Mailserver. In Mailserv vas replaced with
sql-grey. The easiest way is to disable it in the version 4.7.x  rather than continuosely restart mail services via god.
Reply all
Reply to author
Forward
0 new messages