Does anyone know how I disable emails for an account on Cpanel? They host their own emails but we host their site and currently, every time we try to mail them, it just stays within the server and doesn't get to them.
I used to use Plesk and it was as easy as flicking a switch to turn emails off but I can't see that in cPanel. I've tried setting their package to 0 emails in WHM but I'm suspecting that's not going to work.
-James
if the domain example.com are pointed to your DNS
login to WHM and go to Main >> DNS Functions >> Edit MX Entry for the example.com
and when Edit the example.com choose "Remote Mail Exchanger" this will Configure server to not accept mail locally and send mail to the lowest MX record.
so double check the example.com MX records to make sure the MX records set to the valid Mail Server.
if example.com are NOT pointed to your dns and just use IP forwarding to run on your server you can remove the dns entry for example.com by delete the dns zone for example.com as it not used.
If you are trying to send mails from same cpanel server where the website hosted then mail server trying to resovle that domain locally. check the domain entry in /etc/localdomains and remove or comment that entry and you can add that domain in /etc/remotedomains.
Related
I have a scenario that gives me headache for a while now. I bought a domain on Namecheap, hosting on Godaddy cpanel, but later decided to host on Aws ec2 instance, but I don't want to use the SES service from Amazon. Now that was successful.On trying to setup the email account on the Godaddy cpanel, I can only send emails , but not receive. I tried several mx record settings, but none worked.
Domain from Namecheap --- works
Email service - Godaddy Cpanel email -- can only send, no receipts.
Website hosting - Aws ec2 ----works
I would like to know the correct setup for this. Any help would be appreciated.
What is that you are trying to host on EC2? Is it an application?
Where is your Email Hosting done? Is it in GoDaddy?
In order to do that you have to change your MX Record entries in your DNS.
You have to add the MX entry provided by the cpanel for that particular domain in your dns to get your incoming emails service working.
You are able to send emails because there is no need of MX when you are sending mails. You are using SMTP for sending mails out from your server.
Your website should be working if you have added your amazon ec2 instance public ip in your DNS.
You can make things simpler by moving your dns to cpanel i.e. on godaddy server by changing nameservers in your name cheap panel which is given by godaddy guys. You then have to add A record which must be pointing to your AWS ec2 instance public IP and your MX must be set bydefault in your cpanel server.
My client is currently hosting his site on a shared GoDaddy hosting plan, an also his emails accounts. Question is... how can I migrate his website to Digital Ocean and keep the emails on GoDaddy?
I had an recently where I could not receive emails on my goDaddy account once I have moved the nameservers to DO. For anyone facing this issue, the below steps should fix it.
To migrate hosting from goDaddy to DO, follow the below link
https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars
Once you have pointed nameserves, your traffic will be redirected to DO. Now if you want to use the email service provided by goDaddy, you will need to point your DO "MX" records back to godaddy.
First you will need to know the goDaddy incoming email server details. To obtain this, you will need to go to email server settings within your goDaddy Dashboard. The server details will look something like
Incoming server (IMAP):
imap.secureserver.net
Incoming server (POP3):
pop.secureserver.net
You will then need to add these details as MX Records in your Digital ocean domain DNS settings page. DO will then route emails to your goDaddy email service.
These details will take time to reflect. For me it took a day to start receiving emails on goDaddy.
Hope this helps!
Yes, you could just change your zone records to reflect what you want to do. Presumably you want to transfer the DNS zone to Digital Ocean and only keep the email at Godaddy.
In Godaddy's domain name manager you can change over to the Digital Ocean name servers.
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
Check things out:
dig ns example.com
and
whois example.com
The name servers should be the above DO name servers.
The only thing you need to point back at Godaddy will be Goddady's MX records. unless, of course, you're using Office 365 email, which a lot of Godaddy's customers seem to use, in which case lookup the appropriate MX records for Office 365.
I hope this helps.
This is possible, recently I did the same with Hostgator and GCP ( Mail service from webmail and app in Google Cloud ). These are the steps I followed.
1) Add new A record ( if possible/allowed add with name # ) in your
shared/hosting/cpanel service, and point it to your cloud providers
IP(the IP on which your app is running).
2) Add another A record with name www and point it to the IP of your
service running in the cloud.
3) Delete the CNAME record called mail.
4)Add new A record with name mail and point it to your cpanel /
webmail service providers IP.
5)Add MX record and point it to destination mail.yoursitename.tld and
set the priority as 0
By this point, you will be able to send mail.
6) Add SPF record ( TXT record ) or go to Authentication settings in
the Email section in your cpanel and enable SPF.
7)Go to Email Routing in the Email section in your cpanel and select
your domain then choose Local Mail Exchanger under Configure Email
Routing. That's it now you will be able to receive emails also.
Link to my original answer
We have a client with a website hosted on AWS and he is using Google apps to send notification emails. These emails are marked as spam/junk.
We have set an SPF record as per Google's documentation. Clicking on view messege source I found SPF:softfail. From what I understand, setting up reverse DNS/PTR record can also help, but we have 2 production instances behind an ELB and we're not sure how to set that up as it doesn't have a public IP.
This is how our Route53 setup looks:
example.com A ALIAS ***.elb.amazonaws.com.
example.com MX 1 ASPMX.L.GOOGLE.COM.
example.com TXT "v=spf1 include:_spf.google.com ~all"
mail.example.com CNAME ghs.googlehosted.com
Apparently, the client was sending all of his emails through local smtp without using Google Apps. I've added his IP to the SPF record temporarily until he moves the emails over to go through google. We have also set a DKIM record.
PTR records and ELBs had nothing to do with it.
I am having a client who want to keep his website and mails in two separate server. Both are having cpanel hosting. So can someone help me with step to step changes what I need to do ?
Now www.example.com is having cpanel and works fine.
Have another cpanel hosting ready, So what all things I need to do ?
You need to host example.com in two different server, one for website and another for mail service ?
If this is your question, please follow the below steps.
Login to your first cPanel of example.com (for website)
Upload all the files here.
Then, click "Simple DNS Editor" in the same cPanel.
Under "Add an A Record"
Name:mail.example.com
Address :your_mail_server_ip address (ask your mail service provider for this)
And click "Add a Record".
Once this record added.
Goto "MX Entry"
Choose "Remote Mail Exchanger"
Click Change.
Then delete the previous MX record.
Now Add mail.example.com in Destination, Priority is 0 (zero).
Click "Add New Record"
That's it.
Solution No.2:
Upload your contents in cpanel used for website.
Now, Login to your another cPanel used for mail service.
Go to "Simple DNS Editor" under Add an A Record
Name: example.com
address : A record IP address of your website server.
Create email id in email server (cPanel) and start using the mails and website in different server.
Hope this helps you.
Solution No.3:
If this confusing you. contact your hosting provider with MX record and its IP address.
Ask them to update that MX record from their end.
Is there any way to redirect HTTP requests that go to mail.example.com (which is my mail server) to go to the webmail interface, example.com/webmail? I've tried to create a subdomain called mail.example.com, but it conflicts with my mail server and cPanel won't allow me to create it. Any ideas?
there are bunch of sub-domains CPanel creates for each domain. for example if you register example.com , CPanel creates:
ftp.example.com
mail.example.com
cpanel.example.com
vhm.example.com
by default all these sub-domains point at current server, so If you want to use FTP, there is no difference between example.com or ftp.example.com. Both will work.
So, for your mail sub-domain you can set a document root for it(e.g your webmail interface directory). and because SMTP and POP3 are on diffrent ports, it will work fine with mail clients like Thunderbird.
For setting document root to mail.example.com login to your CPanel and go to Advanced DNS editing part and delete mail.example.com. Then create sub-domain with this name.
You can set document root to webmail interface or redirect users to example.com/webmail.
that's your call.
Note: I haven't tested it my self but I tested such thing for FTP. Let me know if it fails.