Editorial and corrections policy
Useful guidance should expose its assumptions and its limits.
Sourcing
Technical guides link to protocol specifications and official provider guidance where relevant. A specification describes protocol behavior; provider documentation describes that provider's implementation. Older RFCs may have updates or successors, so their RFC Editor status pages should be checked before relying on a detail for production work.
Original preparation and AI assistance
The guides on this site were prepared with AI assistance for this publication. They are explanatory articles, not copied provider manuals or accounts of tests we did not perform. A command example is an illustration unless a test is explicitly described with its environment and result. AI-assisted text can contain errors; the source links and verification steps are provided so readers can examine the reasoning.
Authorship and dates
Inbox Scaling is the publishing identity shown in guide bylines. We do not imply that this is a certified individual or a large editorial team. Updated dates record a substantive revision to a guide. They are not automatically advanced simply to make a page appear recent.
Recommendations and boundaries
We explain why an operational sequence is recommended, including cache timing, dependencies and rollback. Provider-specific settings must be checked against current provider guidance. We avoid universal propagation deadlines and claims that authentication guarantees inbox delivery.
Corrections
Use the Contact page with the page URL, the disputed claim and a primary source or reproducible explanation where possible. Omit passwords, private keys, subscriber data and confidential logs. A correction should revise the affected content and its update date. No response-time promise is made.
Advertising and conflicts
Advertising, when enabled, must be identifiable as advertising. Payment does not establish the correctness of an operational recommendation. This release contains no sponsored guide or affiliate recommendation. Advertising and cookie handling are explained in Privacy & cookies.