Reject messages at the API & SMTP level when send limit is exceeded

[adamcooke]

It should be possible for servers to electively choose whether messages should be 'accepted and held' or 'rejected' when a server's send limit has been exceeded.

At present, all messages will be accepted.

• The SMTP server should fail to authenticate requests where the server's send limit has been exceeded.
• It should also verify the limits at the end-of-data to verify that the limit hasn't been exceeded during the pipelining of multiple messages following authentication.
• The API should return an error if the limit is reached.

[olegbliaher]

And while we're at it, add a monthly send limit, if possible :)

[sandrovenezuela]

I personally don't think returning an error via the API is a good idea.

I think one option could be "accept and delete" in addition to "accept and queue".

Amazon SES, for example, does this. Anything that exceeds the limit is deleted, but an error is never returned.

[adamcooke]

I personally don't think returning an error via the API is a good idea.

This would be optional. You don't have to enable it.

[sandrovenezuela]

Perfect, I understand.

So I think the options could be "accepted and held" or "accept and delete" or "rejected". Do you think it is interesting?