From: forrie on
This morning I reviewed my logs to find a couple of sites being
rejected with this error:

Milter: data, reject=451 4.3.2 Please try again later

One was from aol.com. I checked my milter timeouts, connection rates,
etc., and nothing seems out of the ordinary. Other mail got through,
which I thought was interesting (from an .edu site).

I ultimately rebooted the system, which didn't make any difference.
I'm very puzzled! Does anyone have a clue about what's triggering
this?

I'm running sendmail-8.13.8, SpamAssassin/Milter, ClamAV/Milter ...
it's basically the same general config I've been running for years,
and I've never seen that error appear in my logs before.


Thanks.
From: mikea on
forrie(a)gmail.com <forrie(a)gmail.com> wrote in <dd1b8a38-e4b7-4357-8db3-a99bb6e03e7b(a)q15g2000yqj.googlegroups.com>:
> This morning I reviewed my logs to find a couple of sites being
> rejected with this error:
>
> Milter: data, reject=451 4.3.2 Please try again later
>
> One was from aol.com. I checked my milter timeouts, connection rates,
> etc., and nothing seems out of the ordinary. Other mail got through,
> which I thought was interesting (from an .edu site).
>
> I ultimately rebooted the system, which didn't make any difference.
> I'm very puzzled! Does anyone have a clue about what's triggering
> this?
>
> I'm running sendmail-8.13.8, SpamAssassin/Milter, ClamAV/Milter ...
> it's basically the same general config I've been running for years,
> and I've never seen that error appear in my logs before.

I suspect that you need to look into, and possibly instrument, the milter
that is issuing the message setting the "REJECT" flag. This most probably
is not an issue with sendmail itself, but with the milter.

Certainly the information in the error message is insufficient for real
problem determination to be carried on, but equally certainly it is a
notice that problem determination needs to be done.

--
Mike Andrews, W5EGO
mikea(a)mikea.ath.cx
Tired old sysadmin
From: forrie on
At first, I suspected Spamassassin might be the culprit -- someone
decided to write a spamass-milter-wrapper script in the distribution,
which adds another level of complexity, so I double-checked the
permissions -- ultimately, I tested spamd without the wrapper, and I'm
still getting the same problems. Curiously, it only seems to be from
certain sites thus far. Here is a complete log that I'm seeing:


Apr 2 12:20:11 mail sendmail[4776]: o32GK58f004776: from=<notification
+y_zs00c(a)facebookmail.com>, size=2093, class=0, nrcpts=1,
msgid=<1a8b74333840f2dbb4abcf71097852e2(a)api.facebook.com>,
proto=ESMTP, daemon=MTA, relay=outmail021.snc1.tfbnw.net
[69.63.178.180]
Apr 2 12:20:11 mail spamd[3968]: spamd: connection from mail
[127.0.0.1] at port 47133
Apr 2 12:20:11 mail spamd[3968]: spamd: processing message
<1a8b74333840f2dbb4abcf71097852e2(a)api.facebook.com> for [omitted]:503
Apr 2 12:20:12 mail spamd[3968]: spamd: clean message (2.6/10.0) for
forrie:503 in 1.1 seconds, 2458 bytes.
Apr 2 12:20:12 mail spamd[3968]: spamd: result: . 2 -
AWL,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_LOW,SARE_UN4,SARE_UNSUB13,SPF_PASS
scantime=1.1,size=2458,user=[omitted],uid=[omitted],required_score=[omitted],rhost=mail,raddr=127.0.0.1,rport=47133,mid=<1a8b74333840f2dbb4abcf71097852e2(a)api.facebook.com>,autolearn=no
Apr 2 12:20:12 mail sendmail[4776]: o32GK58f004776: Milter: data,
reject=451 4.3.2 Please try again later
Apr 2 12:20:12 mail sendmail[4776]: o32GK58f004776:
to=<forrie(a)forrie.com>, delay=00:00:01, pri=32093, stat=Please try
again later
Apr 2 12:20:12 mail spamd[3966]: prefork: child states: II


As you can see, the error is very ambiguous. I've not changed
anything in my sendmail.mc configuration -- I double checked the
timeouts on the INPUT_* and all is fine.

Could this somehow be a DNS related matter? The two sites that are,
thus far, having the problem are aol.com and facebook.com.

I guess the next step would be to remove the milters and see what
happens then. There are no other error messages being generated from
these incidents, so it's difficult to track down. It just started
showing up today. This system literally sits there and delivers
mail, and does nothing more -- it has been doing so just fine for
months.


Thanks...

From: forrie on
At first, I suspected Spamassassin might be the culprit -- someone
decided to write a spamass-milter-wrapper script in the distribution,
which adds another level of complexity, so I double-checked the
permissions -- ultimately, I tested spamd without the wrapper, and I'm
still getting the same problems. Curiously, it only seems to be from
certain sites thus far. Here is a complete log that I'm seeing:


Apr 2 12:20:11 mail sendmail[4776]: o32GK58f004776: from=<notification
+y_zs00c(a)facebookmail.com>, size=2093, class=0, nrcpts=1,
msgid=<1a8b74333840f2dbb4abcf71097852e2(a)api.facebook.com>,
proto=ESMTP, daemon=MTA, relay=outmail021.snc1.tfbnw.net
[69.63.178.180]
Apr 2 12:20:11 mail spamd[3968]: spamd: connection from mail
[127.0.0.1] at port 47133
Apr 2 12:20:11 mail spamd[3968]: spamd: processing message
<1a8b74333840f2dbb4abcf71097852e2(a)api.facebook.com> for [omitted]:503
Apr 2 12:20:12 mail spamd[3968]: spamd: clean message (2.6/10.0) for
forrie:503 in 1.1 seconds, 2458 bytes.
Apr 2 12:20:12 mail spamd[3968]: spamd: result: . 2 -
AWL,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_LOW,SARE_UN4,SARE_UNSUB13,SPF_PASS
scantime=1.1,size=2458,user=[omitted],uid=[omitted],required_score=[omitted],rhost=mail,raddr=127.0.0.1,rport=47133,mid=<1a8b74333840f2dbb4abcf71097852e2(a)api.facebook.com>,autolearn=no
Apr 2 12:20:12 mail sendmail[4776]: o32GK58f004776: Milter: data,
reject=451 4.3.2 Please try again later
Apr 2 12:20:12 mail sendmail[4776]: o32GK58f004776:
to=<forrie(a)forrie.com>, delay=00:00:01, pri=32093, stat=Please try
again later
Apr 2 12:20:12 mail spamd[3966]: prefork: child states: II


As you can see, the error is very ambiguous. I've not changed
anything in my sendmail.mc configuration -- I double checked the
timeouts on the INPUT_* and all is fine.

Could this somehow be a DNS related matter? The two sites that are,
thus far, having the problem are aol.com and facebook.com.

I guess the next step would be to remove the milters and see what
happens then. There are no other error messages being generated from
these incidents, so it's difficult to track down. It just started
showing up today. This system literally sits there and delivers
mail, and does nothing more -- it has been doing so just fine for
months.


Thanks...

From: Bruce Esquibel on
forrie(a)gmail.com <forrie(a)gmail.com> wrote:

> This morning I reviewed my logs to find a couple of sites being
> rejected with this error:

> Milter: data, reject=451 4.3.2 Please try again later

> One was from aol.com. I checked my milter timeouts, connection rates,
> etc., and nothing seems out of the ordinary. Other mail got through,
> which I thought was interesting (from an .edu site).

> I ultimately rebooted the system, which didn't make any difference.
> I'm very puzzled! Does anyone have a clue about what's triggering
> this?

Best guess from me is it's grey listing. I think that
"Please try again later" is standard issue for smf-grey, isn't it?

-bruce
bje(a)ripco.com