4 ms·
Bouncing on the other end has nothing to do with running your own mail domain. In e-mail, sending and receiving are decoupled. Some people use the same local ma
by kazinator 4y ago
Bouncing on the other end has nothing to do with running your own mail domain. In e-mail, sending and receiving are decoupled. Some people use the same local mail server to do both: to relay outgoing mail and to receive. But these are independent functions, and you don't have to send mail through your server. You can configure your mail client(s) with the SMTP credentials from you mail provider (such as your ISP). That's used for sending. For receiving, you connect to your own server via IMAP4.
Basically your sending side (if you choose to) can be essentially unrelated to your self-hosted mail receiving infrastructure except in the small fact of using your sending identity in the From: headers of your e-mails: you@yourdomain.com.
- bongobingo1 4y agoDoesn't that depend on my ISP running basically an open relay, if I'm trying to mail from me@hn.com and they only provide me@isp.net? Always figured they'd just dump the request with a "i don't know you".
- kazinator 4y agoNo because relays can be closed, and usually are. Your ISP's SMTP server requires authentication, using the credentials they gave you, and almost certainly uses TLS also. Your me@isp.net address (or perhaps the me part of it) is used for authenticating, along with the password. It will likely be used as your envelope address when sending; the SMTP command will be MAIL from: me@isp.net, though there could be flexibility there to accept other sending envelope identities. In any case, your mail's From: header will have the me@hn.com. If the ISP were to filter on the From: addresses after receiving the content of the e-mail, you'd have to negotiate something with them.
- bongobingo1 4y ago> using the credentials they gave you, and almost certainly uses TLS also Ah yes, doh.