On Sun, Oct 23, 2011, Murray S. Kucherawy wrote:
From: Claus Assmann
Sent: Thursday, October 13, 2011 10:22 AM
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:
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?
I like to implement things that I consider useful, I don't need to
have some marketing research group to tell me what to do.
Currently we have some document that lists restrictions imposed by
several ISPs and I have to create default setups based on those.
Instead of having a static document with limits that apply to
everyone, it is obviously much more efficient to have (dynamic, per
client) limits that are announced when the service is actually used.