Clarify what happens to rejected and oversized messages - #77
Merged
Conversation
Support questions keep coming in about where a message goes when it's rejected. Explain that an oversized message is rejected during the SMTP conversation so the sending server generates the bounce, that the HTTP status we get back is translated into an SMTP reply code rather than causing us to retry the POST, and that attachments are already uploaded to cloud storage by the time your endpoint is called.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prompted by Zendesk 16227, where a customer asked whether an oversized message was bounced or "lost in limbo", and then whether a 404 means the attachment is still written to their bucket. Both answers were already true of the system but not written down anywhere.
Explains that an oversized message is rejected during the SMTP conversation so the sending server generates the bounce, that the HTTP status you return is translated into an SMTP reply code rather than causing us to retry the POST, and that attachments land in cloud storage before your endpoint is called, so rejecting afterwards doesn't remove them. The attachment storage page cross-links back for the same point.