Hacker News new | ask | show | jobs
by colimbarna 793 days ago
Forwarding traditionally looked like this:

1. I tell my email client from colimbarna@fine.server.example to send an email to eisenstein@old.server.example using my.correctly.configured.smtp.server.example

2. my.correctly.configured.smtp.server.example looks up the records for old.server.example and contacts the SMTP server that is sitting there.

3. old.server.example accepts the email and checks its rules for what to do with it: and it is supposed to forward it to eisenstein@new.server.example.

4. old.server.example looks up the records for new.server.example and contacts the SMTP server that is sitting there. It forwards the email basically unchanged - this isn't something where it's from:eisenstein@old.server.example to:eisenstein@new.server.example subject: Fwd - old subject, it's just saying "here's an email to eisenstein@old.server.example, please deliver it to eisenstein@new.server.example". Remember that the "to" address isn't necessarily the person the email is getting delivered to, because you might be in a cc or even bcc list.

5. new.server.examples accepts the email and checks its rules for what to do with it: and it supposed to put it into eisenstein's inbox.

The change here is to steps 3 and 5: "server accepts the email". Instead of simply accepting the email, the SMTP server will checks to make sure that the server which is sending the email is allowed to send the email on behalf of that email address.

So in step 3, old.server.example will check to make sure that my.correctly.configured.smtp.server.example is allowed to send emails on behalf of fine.server.example. It will see that it is, and the email will continue.

But then in step 5, new.server.example will check to make sure that old.server.example is allowed to send emails on behalf of fine.server.example. And it will see that it is not, and it won't accept the email.

Now, your situation is probably different. Instead of steps 3-5, you probably have gmail checking to make sure the sender is allowed to send the email, and if so it checks its rules for what to do with it: and it is supposed to put it into eisenstein's inbox. It's not actually forwarded, it's just that there's more than one email address that gets delivered into the one inbox. (This assumes you have your domain correctly configured for delivery to a gmail address. It's worth double checking, especially if you set it up longer ago than you care to remember.)