Regardless that it's for custom domains, the smtp server will call itself "mx.pawnmail.com" during the SMTP protocol negotiation.
The parent comment is not correct in thinking that matters, but they are correct that it will be identified as pawnmail, just not as part of the email address itself.
Irrespective of whether users use their own domain, email sent through the pawnmail service will be associated with the pawnmail domain via their MX records.
Using a custom domain doesn't necessarily mean using a custom mail server, they can point to a really common mail server such as gmail for instance. This is how a lot of business emails are set up.
That's actually a much more logical explanation than I've heard before, but it seems to be based on a potential misunderstanding of who is using the service -- maybe it is mostly giant companies, but I bet there are a lot of tinkerers who just like having the custom email domain.
I am aware. Was speaking colloquially. Maybe “custom domain name with email” would be better. But I was on my phone and just trying to get the point across.
It’s worth noting that while my email does use a .com as a backup, it’s primary is a gtld .email
There was a time, when the Internet didn't look much like it does today - especially when UUCP reigned supreme - when nearly all email domains did not have associated IP addresses. Local ISP's that give custom email addresses to their users also nearly always do the same thing. If you want to go down a rabbit hole, look up how to do bang path email routing. It still works today, even if nobody does it.
The only part that matters is that the sending mail server can find an MX record for the receiving domain's mail server. There is no requirement for the named domain to have its own IP address as long as whatever domain the MX points to knows where to send the incoming mail.
It was the other way around for me. But regardless, the best part of owning your own domain - if you don't like your mail provider, just change the MX records to a new one.
Heck, I could run my own mail server if I wanted (been there, don't want to go there again, but could if I really HAD to).
When you create an account there is a page called domains, it provides instructions on how to add the correct MX record to your custom domain in order to allow the server to handle inbound emails.
> They offer a 30 day trial to check it out (without custom domain part for the trial), after that you can upgrade it to a full paid account, which supports custom domains.
From their features page.
> With the trial product You can use your own domain name or use a free sub-domain of servermx.com which will be assigned to you at subscription time.
Or did you mean they don't offer "Custom Web mail URL - Your domain name can be used for your web email client (example http://webmail.yourdomainname.tld)" during the trial?
Thanks for the heads up, I'll have to look into them as I'm getting bored of maintaining my own mail server and €24 isn't bad for a year. I'll have to look into them a bit more before taking the plunge though.
I think people who get their email on their own domain generally consider it as their permanent home and don’t think about what will happen when the domain no longer is registered to them. Using the apartment rental analogy works up to a point. With an apartment you can get the postal service to forward your mail to a new address. With a domain name there is no way to get this to happen. Whoever holds the registration controls the MX record and can do whatever they want.
The parent comment is not correct in thinking that matters, but they are correct that it will be identified as pawnmail, just not as part of the email address itself.
reply