How an email finds an inbox

When you send a message, your mail program hands it to your provider’s server. That server looks at the domain, the part after the @. It asks the domain name system where mail for that domain should go. The answer is the address of a mail server, not the laptop of the person you wrote to.

The two servers talk, using a long-standing protocol for handing mail across. If the recipient’s server accepts the message, it stores it in a mailbox. If it refuses, or if nobody answers, your server may retry for a while and then send you a bounce. The bounce is how you learn the address was wrong or the far end was down.

The half after the @

The mailbox is a queue of files on that server. It is not instantly on the recipient’s screen. Their mail program fetches it, either by pulling new mail at intervals or by a push from the server. A phone in a tunnel fetches nothing until it has a connection again.

Spam filtering and a quarantine sit in that path. A message can be accepted by the server and still not reach the inbox you look at, because a filter filed it elsewhere. The sending server thinks it succeeded. The reader has to check the other folder.

Store, then fetch

Encryption, where it is used end to end, scrambles the contents so the servers in the middle carry a file they cannot read. Most ordinary mail is protected in transit between servers and is readable by the providers at each end. That is a different, weaker arrangement, and it is the common one.

The address is the only routing instruction that matters. A display name beside it is a label for humans. The servers follow the address. A mistyped domain is a letter posted to a street that is not there.

The half after the @

An email is a small file passed from one mail server to another. The address after the @ sign is how the first server finds the second. When you send a message, your mail program hands it to your provider’s server. That server looks at the domain, the part after the @.

Put those two statements side by side. The first sets the condition. The second says what happens once that condition is met. How an email finds an inbox needs both. Drop the first and the second has nothing to explain. Drop the second and the first is only the scene.

Store, then fetch

That server looks at the domain, the part after the @. It asks the domain name system where mail for that domain should go.

The order is the explanation. What the first sentence names has to be there before the result in the second sentence can show up. The piece does not ask you to accept the result first and hunt for a cause afterwards.

A check you can make

It asks the domain name system where mail for that domain should go. The answer is the address of a mail server, not the laptop of the person you wrote to.

A fair check is sequential. Confirm the first statement. Then see whether the second is the result of it, rather than a separate fact parked in the same piece. If the result shows up without the condition, this account does not cover what you are looking at.

The limit of the claim

The answer is the address of a mail server, not the laptop of the person you wrote to. The two servers talk, using a long-standing protocol for handing mail across.

The two statements do different jobs. One says what is there, what it is made of, or what acts on it. The other says the change that follows. The title names the change. It is not an inventory of parts.

The same steps, in order

The two servers talk, using a long-standing protocol for handing mail across. If the recipient’s server accepts the message, it stores it in a mailbox.

Nothing in the second statement cancels the first. It carries the first forward or marks the limit of it. Remember only the result, and the cause goes missing. Remember only the cause, and you will not know what the piece says happens next.

Why the order matters

If the recipient’s server accepts the message, it stores it in a mailbox. If it refuses, or if nobody answers, your server may retry for a while and then send you a bounce.

Read them as one path. Start at the first full stop and do not skip to the outcome. The words between the two statements are the mechanism. The title is the name of that path, not a second claim.

Condition, then outcome

If it refuses, or if nobody answers, your server may retry for a while and then send you a bounce. The bounce is how you learn the address was wrong or the far end was down.

The first statement can be true and still not finish the job. The second statement is the job finishing. Hold both, and the paragraph above stops being a list. It becomes the reason the title is worded as it is.

What the title is naming

The bounce is how you learn the address was wrong or the far end was down. The mailbox is a queue of files on that server.

If you wanted a shorter version, it would be those two sentences and nothing else. Everything added around them is there so the dependence is obvious: the second does not happen unless the first has happened.

What has to come first

The mailbox is a queue of files on that server. It is not instantly on the recipient’s screen.

Put those two statements side by side. The first sets the condition. The second says what happens once that condition is met. How an email finds an inbox needs both. Drop the first and the second has nothing to explain. Drop the second and the first is only the scene.

The result that follows

It is not instantly on the recipient’s screen. Their mail program fetches it, either by pulling new mail at intervals or by a push from the server.

The order is the explanation. What the first sentence names has to be there before the result in the second sentence can show up. The piece does not ask you to accept the result first and hunt for a cause afterwards.

A check you can make

Their mail program fetches it, either by pulling new mail at intervals or by a push from the server. A phone in a tunnel fetches nothing until it has a connection again.

A fair check is sequential. Confirm the first statement. Then see whether the second is the result of it, rather than a separate fact parked in the same piece. If the result shows up without the condition, this account does not cover what you are looking at.

The limit of the claim

A phone in a tunnel fetches nothing until it has a connection again. Spam filtering and a quarantine sit in that path.

The two statements do different jobs. One says what is there, what it is made of, or what acts on it. The other says the change that follows. The title names the change. It is not an inventory of parts.

The same steps, in order

Spam filtering and a quarantine sit in that path. A message can be accepted by the server and still not reach the inbox you look at, because a filter filed it elsewhere.

Nothing in the second statement cancels the first. It carries the first forward or marks the limit of it. Remember only the result, and the cause goes missing. Remember only the cause, and you will not know what the piece says happens next.

Why the order matters

A message can be accepted by the server and still not reach the inbox you look at, because a filter filed it elsewhere. The sending server thinks it succeeded.

Read them as one path. Start at the first full stop and do not skip to the outcome. The words between the two statements are the mechanism. The title is the name of that path, not a second claim.

Condition, then outcome

The sending server thinks it succeeded. The reader has to check the other folder.

The first statement can be true and still not finish the job. The second statement is the job finishing. Hold both, and the paragraph above stops being a list. It becomes the reason the title is worded as it is.

What the title is naming

The reader has to check the other folder. Encryption, where it is used end to end, scrambles the contents so the servers in the middle carry a file they cannot read.

If you wanted a shorter version, it would be those two sentences and nothing else. Everything added around them is there so the dependence is obvious: the second does not happen unless the first has happened.

What has to come first

Encryption, where it is used end to end, scrambles the contents so the servers in the middle carry a file they cannot read. Most ordinary mail is protected in transit between servers and is readable by the providers at each end.

Put those two statements side by side. The first sets the condition. The second says what happens once that condition is met. How an email finds an inbox needs both. Drop the first and the second has nothing to explain. Drop the second and the first is only the scene.

The result that follows

Most ordinary mail is protected in transit between servers and is readable by the providers at each end. That is a different, weaker arrangement, and it is the common one.

The order is the explanation. What the first sentence names has to be there before the result in the second sentence can show up. The piece does not ask you to accept the result first and hunt for a cause afterwards.

A check you can make

That is a different, weaker arrangement, and it is the common one. The address is the only routing instruction that matters.

A fair check is sequential. Confirm the first statement. Then see whether the second is the result of it, rather than a separate fact parked in the same piece. If the result shows up without the condition, this account does not cover what you are looking at.

The limit of the claim

The address is the only routing instruction that matters. A display name beside it is a label for humans.

The two statements do different jobs. One says what is there, what it is made of, or what acts on it. The other says the change that follows. The title names the change. It is not an inventory of parts.

The same steps, in order

A display name beside it is a label for humans. The servers follow the address.

Nothing in the second statement cancels the first. It carries the first forward or marks the limit of it. Remember only the result, and the cause goes missing. Remember only the cause, and you will not know what the piece says happens next.

Why the order matters

The servers follow the address. A mistyped domain is a letter posted to a street that is not there.

Read them as one path. Start at the first full stop and do not skip to the outcome. The words between the two statements are the mechanism. The title is the name of that path, not a second claim.

Condition, then outcome

When you send a message, your mail program hands it to your provider’s server. That server looks at the domain, the part after the @.

The first statement can be true and still not finish the job. The second statement is the job finishing. Hold both, and the paragraph above stops being a list. It becomes the reason the title is worded as it is.