-----Original Message-----
From: owner-ietf-smtp(_at_)mail(_dot_)imc(_dot_)org
[mailto:owner-ietf-smtp(_at_)mail(_dot_)imc(_dot_)org] On Behalf Of Claus
Assmann
Sent: Thursday, October 13, 2011 10:22 AM
To: SMTP Interest Group
Subject: Re: SMTP traffic control
It would be nice to have a standard for a server to tell a client
which restrictions it triggered, what the limits are, and what it
should do to avoid this from happening again. For example:
- number of sessions per time unit
- concurrent number of sessions
- number of transactions per session
...
It would also be helpful to have an enhanced status code that tells
a client: "don't even try one of the other MXs, it will reject you
too." That can be rather helpful for greylisting and for systems
that share traffic control information.
Anyone interested in specifying this?
Knowing which MTAs you represent, I'm curious: Are these napkin scratchings of
things that might be neat or useful to have, or are you responding to consumer
pain points?
If the latter, knowing the background of these ideas might go a long way to
justifying the work and, of course, having faith that there will be a ton of
interoperability shakedown, which makes for a solid specification.
-MSK