Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

Problem with a uunet relay server

Problem with a uunet relay server

2004-06-17 by Brian Snead

I was seeing an interesting chain events with two relay servers owned by uunet. My client was sending a message to 4 people in my office. The first uunet server would connect and the first recipient would temp fail properly. I would see no reference to the other 3 recipients. Next, the second server would connect about a minute later. It reject period has not expired, so it is told to come back on the first recipient. I use a 5 minute wait period.

Next, the first server would connect again. Still in the timeout period, I would tell to go away. The customer then receives a non delivery notice with a 553 unauthorized relay traffic prohibited.

Then, about a half hour later, I would see the connect again. The first recipient is autowhitelisted now, so the second recipient sets off the whole process again. etc etc etc.

Are these server giving up when the first recipient temp fails? Milter-greylist would accept all recipients and temp fail each, right?

Does this server pair need to be added to the whitelist?

Thank you,

Brian.

Re: [milter-greylist] Problem with a uunet relay server

2004-06-17 by manu@netbsd.org

Brian Snead <BSnead@...> wrote:

> Are these server giving up when the first recipient temp fails?
> Milter-greylist would accept all recipients and temp fail each, right?

I wonder what software those uterly broken MTA run
 
> Does this server pair need to be added to the whitelist?

Yes. Generally speaking, you should add as much known addresses to the
whitelist as you can. There is no need to greylist mail that is coming
from a real MTA. It will give you delay and the mail will get through
whether it is spam or not.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.