Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics

Dashboard
Notifications
Mark all as read
Q&A

I don't want to setup DKIM, SPF and to do SMTP authentication ; an hosting-provider-email-box solves this but what if I want a domain-registrar-email-box instead?

+0
−0

On a shared hosting (CentOS-Bash) I have a website with a backend (PHP) - frontend CMS-agnostic contact form.

I need to transfer emails sent via this contact form directly to an email address (I don't save anything in my website's database).

I don't want to setup DKIM, SPF and to do SMTP authentication because for me it's an overkill --- I don't send emails to anyone from my website domain - but to myself. I also don't want to use PHPmailer ; I use a simple PHP mail() directive set.


If I create an email address on my hosting provider's end than I should have no technical problem;
The hosting domain and the website domain will match, DKIM/SPF are set and SMTP/MTA are configured and I could also have an aesthetic address such as [email protected] without fearing that such an address being already in use in generally every third party email service provider.


At least I might want to use third party email provider.

  • Large-gratis email service providers such as Baidu, Gmail, Hotmail and Yandex are quite strict in their spam or alleged-as-spam filtering and I am afraid that if I would work with one of them but would make even the slightest configuration mistake on my hosting environment (and I think there is a lot to configure with emails and much potential for mistakes) I could lose many potential customers.

  • I thought about buying an email box from my domain registrar, than I could also have an aesthetic name such as [email protected] without such an address being already in use but my main problem with that approach is that I don't know what to expect; my domain registrar is also a huge company with potentially millions of customers and might have ardent spam or alleged-as-spam filtering so buying an email address from it might end in similar problems to those I could experience with the large-gratis email service providers such as those mentioned above.

Can I still easily use an email address outside of my hosting account domain (in this case, in my domain registrar)?

"easily" here means "without configurations at all - something that 'just works'".

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

6 comments

I would go with "buying an email box from my domain registrar" because it seems to be the easiest + safest solution. As long as the contact form is not abused, I do not think you will ever run into trouble with the spam filters. You did not mention, but is the destination an e-mail address on your domain registrar? Alexei‭ 18 days ago

Hello Alexei ! I would go with "buying an email box from my domain registrar" because it seems to be the easiest + safest solution why should it be easier and safer than using an email box of the hosting provider? JohnDoea‭ 18 days ago

You did not mention, but is the destination an e-mail address on your domain registrar? Currently the destination email is my own private Gmail account; I wonder if it should be an email box in the hosting environment or an email box in the domain registrar. JohnDoea‭ 18 days ago

I am a fan of keeping things simple. If there is no strong reason to rely on something else, why not have everything provided by the same provider: the client accesses the form hosted on example.com (your provider), fills the form and your script running on example.com sends an e-mail to your [email protected] e-mail address using a mailbox configured to use the same example.com domain. No e-mails over the Internet (source and destination on the same domain), no worries about spam filtering. Alexei‭ 18 days ago

I always prefer to have a domain registrar and an hosting company different; it makes migrations, if needed from whatever reason, easier. If I understand you correctly you support the idea of hosting the emails on a separate database (not the website's database) but also on the hosting company's environment. If so, yes, I can do that, but my main concern is that if tomorrow I want to change my hosting provider to another, it might be a pain to migrate emails to the new hosting provider. JohnDoea‭ 18 days ago

Show 1 more comments

0 answers

Sign up to answer this question »