Email and domains
The address people write to, and the mail the site sends.
Two different things that share a name. Mail your team reads, and mail the site sends on its own — receipts, password resets, notifications. Both hang off your domain, and the domain is the part that has to be set up correctly for either to work.
What we need from you
- Access to the domain's records, or somebody who has it
Usually whoever registered the domain. Where nobody is certain who that is, establishing it is the first task rather than a detail to sort out later.
- The addresses you want to receive at
Including the shared ones, and who should be able to read each of them. A shared address that everybody can read is a decision, not a default.
- Which address the site should write as
The address receipts and notifications come from. It should be one somebody actually monitors, because people reply to it.
What is true once it is in
- Mail from the site that arrives rather than filtering
Sent through a provider, with the domain set up to authorise it — which is the specific thing that keeps automated mail out of spam folders.
- Addresses on your own domain, not a provider's
So the address survives changing email provider, changing host, or changing who builds your website.
- A change of provider later without changing your address
The domain is yours and its records point wherever you decide, which makes a provider a supplier rather than something you are tied to.
Fun fact
The first .com domain was registered on 15 March 1985, to a computer manufacturer in Massachusetts called Symbolics. The company itself is long gone, and the domain is still there.
The other connections
Get in touch
Every one of these reaches us directly, and is answered by a person.
A new project, a quote, or a question about one that is running.
- Reaches us at
- +355 69 752 2209
- Carries
- Messages