Re: [ietf-smtp] [Emailcore] Proposed ESMTP keyword RCPTLIMIT

Dave Crocker writes:

> Most of the time, enhancement mechanisms, like this, already have  
> significant adoption barriers.  So keeping them as simple as possible is to  
> be highly preferred, over making them more nuanced.
That's my take too. I am not sure what I'll gain from doing this in the  
first place, not to mention any extra complexity of this sort.
Without explicitly defined limits: I'm just picking a reasonable cap and  
duplicating each message, so their number of recipients is under the cap.  
This happens much earlier in the processing, even before attempting to find  
a willing MX to talk to.
MXes which do not announce their limits are going to dominate for some time.  
So, I still need to do this for the foreseeable time. So, what does this  
SMTP extension buy me? The only thing I can think of: not duplicating  
messages when I don't need to.
But the thing is: I don't recall anyone raising this to me, as a problem.  
This is not on my radar screen as a problem that wants to be solved.

pgpi2agOYnHGq.pgp
Description: PGP signature

_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp