Repository navigation
docs: clarify SMTP acceptance and sending results - #65
Merged
Merged
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one): 1
Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
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
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.
This candidate adds direct SMTP acceptance and delivery guidance to current Docs main and includes refreshed PR64 connection recovery in one combined product update. The SMTP guide explains that direct submissions using send-only keys or owner-approved Sending-resource tokens can be accepted during occupied sending capacity after storage and required credit reservation. SMTP
250confirms acceptance for background sending, delivery can still fail, and452 4.3.1 Insufficient credits.means the message was not accepted.This is a source-only candidate. The announcement date remains
<<TBD: verified publication date>>; merge and publication remain held until the release owner binds the deployed source, relevant live acceptance, verified publication date/order and exact publication approval. Present-tense draft copy does not qualify current live behaviour.PR65 retains PR64 as an ancestor and adds to the same update; no duplicate changelog entry, replacement PR or force-push. Current hotfix/history, existing guide/frontmatter/links/icons, API snapshots and generated collections remain unchanged.
Validation results and exact hosted CI/review status accompany the owning reconciliation receipt. Historical public-readback font
ERR_ABORTEDSTOP/UNKNOWN and raw-network export restriction remain separate; local source preview is not public acceptance.