I recently updated the # record of a website and nothing else so as not to interrupt their emails. I'm somewhat familiar with DNS settings but when it comes to emails I'm pretty lacking in knowledge. Anyways, after updating the # record my client could no longer receive emails. They are able to send, however. The new website itself is on another server (which I pointed the # record to), while the emails and (old) website are on another. I specifically set the new web server's email to Remote.
Is this just an issue with propagation? It was changed a day ago and everything else went smoothly.
You must check the MX records for the domain in DNS zone. They should point to the correct server for ensuring to receive emails.
Related
I've searched all around, made several changes over the past two weeks, and still no luck so here I am.
We just put up a new site, and there are 3 different forms. Each form sends to a different email of theirs, a forwarder that sends to the same email of theirs (I had to make this after I figured out there was a problem with them not receiving emails from the website), and one of our emails.
Currently, they use office 365 for their email. A few days ago I figured out to change the SPF record, so I added the IP of their current website.
Here is the current SPF record:
v=spf1 include:spf.protection.outlook.com ip4:23.229.157.193 a ~all
I'm stumped. I've sent test submissions, and they receive the forward, and I receive it from my email, but the email that it's supposed to be sent to doesn't receive it.
I don't have access to their office 365 account. I tried a different option of sending the emails through swiftmailer, but GoDaddy doesn't allow me to connect to their smtp details, so that's a bust.
Has anyone encountered this problem before and know of a solution? All help is greatly appreciated.
THE SOLUTION:
After hours of calling, I was able to get the problem solved. I should have edited this earlier, but better late than never. In cPanel, there is an area for routing mail. It was set to local, rather than remote. Every email that came through went to the local emails, and since their were none, they were discarded. After changing the option to remote, the emails started flowing through. After the 3rd or 4th call, I reached someone who's actually dealt with this problem because he explained what was happening and the fix in under two minutes, unlike the others. I hope this helps anyone in the future with the same problems I encountered.
If you've configured SPF on your sending smtp server, you can configure a _dmarc
DNS record with an email address for the receiving server to send mail reports to...
Better yet, if this 'new' server is not required to be fully operational while you set up everything - you can set the _dmarc record to tell the receiving server to reject anything that doesn't pass the SPF test.
In any case, if you are setting up an email server that will send messages to any outside Internet address, and you have the ability to install software on the server - you should install and configure:
SPF, DKIM, and have a dmarc DNS record.
If you don't have these items, it's very likely much of your site's notification email will end up in the subscribers' spam box, or worse rejected by the receiving server.
Several good websites that have helped me:
unlocktheinbox.com
dmarcian.com
emailsecuritygrader
protodave.com dkim key checker
appmaildev.com domainkeys test
gettingemaildelivered.com
Having problems with setting up my website to use MS Exchange to send emails. I dont want to use the hosts email system.
The MS Exhange has been set up, with email addresses created.
My webpages are using Persits.MailSender which the host supports.
Do i need to change MX records? A records?
Sorry, im not clued up with network side of things, any help would be appreciated
When i email direct, the email address on the exchange picks up the emails. BUT if i email through the website, it goes to the annoying webmail the host is provinding, and not to the exchange
I find this strange, the same email address receiving emails at different places!
Im using ASP, and I have a website set up, which has been sending emails for the last 12 months, the host has messed up (again) somewhere, but doesnt know what is wrong (as usual)
There are no errors, the email always gets sent.... but to the wrong place.
I would look into actually trapping and knowing your errors. That way you can see precisely why it fails and have something to work with. As it stands, your question isn't really answerable. No language nor framework is provided. We don't know if the mail server is confirmed to be working or accessible outside your netowrk; we don't know how your are referencing it or if you are passing user credentials; we don't know what error you're getting...
At this point, you're not debugging, you're just sort of swinging in the dark. Find the point of failure and then research that data point to get a solution. Debug, catch errors, log, step through your code. All good ideas.
Ok i figured it out, I deleted the mail domain on the host as that was the first place the website looks to send an email. Once the mail domain was deleted the emails were sent to the external hosted mailserver MS Exchange email address. Yay!
I am helping a friend set up a website at Drupal Gardens. The domain is www.fromtheheartyoga.com. Previously the site was hosted at Modwest. While at Modwest I set them up with gmail/Google Apps for business (free version), so they could use the #fromtheheartyoga.com emails with gmail.
A few days ago I moved hosting from Modwest to Drupal Gardens. In order to get the domain working correctly I had to set up a CNAME record at DirectNIC (the domain provider) to point the domain "www.fromtheheartyoga.com" at the Drupal Garden site "fthy.drupalgardens.com". In order to do this I had to upgrade the DirectNIC account to a hosted account.
When I created the CNAME record, email stopped working. I later went in and updated the MX records at DirectNIC with all of the relevant Google Mail MX information. Email still didn't work. DirectNIC sait it could take as long as 48 hour for these changes to propagate. Thing is, when I updated the CNAME record, the domain began pointing to the new hosting environment almost immediately. Not so with the email.
That was Friday. As of today, none of the email addresses using the #fromtheheartyoga.com (gmail) have received any email. Every email I send from another account disappears into the internet. For the emails I send from my personal gmail account, I occasionally get a transfer update which includes, among other things the note that "The recipient server did not accept our requests to connect".
I can still send from the #fromtheheartyoga gmail account. Replies to emails sent from there also disappear.
I have had no luck with Google searches, unless the answer is right in front of me and I simply don't know enough about the issue to recognize it. Likewise here at StackOverflow. Any insights would be greatly appreciated
-John Winkelman
For compatibility reasons, you can't put a CNAME in the root domain; doing so will break email.
Use an A record instead.
Just make an A record for fromtheheartofyoga.com. The old BIND4 CNAME for a domain directive really wasn't right even back then. It's just more records to edit should you move again, who cares.
Edit to add: I don't know whether you get a definite IP address with your hosting service, you would have to know that for this to work.
Regards,
Brian in CA
Just rebuilt a companies website, updated their A records to point to it's new server location but kept their email function as was.
Sending from the server works fine, and they receive mail from elsewhere fine but now when trying to send forms as emails to their existing addresses they never arrive.
For example trying to send an email (more specifically a Drupal Webform) from domain.com from Server 1 to email#domain.com on Server 2.
I've tried adjusting the send address from Server 1 which doesn't change anything. I think their IT person said something about receiving email at an exchange (Microsoft?) but I'm not savy this area at all.
Any ideas about this? I guess something is stopping it before it gets delivered (no spam) and the domains are conflicting, had a Google about but it's one of those where I'm not quite sure how to phrase the question. Thanks
SOLVED! In my CPanel I just needed to change my MX Entry to Remote Mail
Server Exchanger
I have a domain, call it mydom.com.
A while ago I started using Google App's email server. I set up MX and the rest of the stuff records as Google wanted, and all is working well since.
On www.mydom.com I have a website, DNS and still running mail server (which basically doesn't do much).
Among other things, on www.mydom.com, I have some contact form - basic php page that takes user's input and sends it to predefined email address at mydom.com. It sends it with php's sendmail function.
My issue is - all those email that get sent from localhost to *#mydom.com (by php's function, or possible by some cron jobs reporting some issues) DO NOT go to Google's email servers but instead get picked up by localhost and it's mail server.
So far, I was resolving this issue by setting up a new mail account at Google account, which was basically calling my local mail server by it's IP address, logging into old, abandoned email account and pulling those misplaced emails to the new, #mydom.com account at Google App.
Obviously I'm missing some entry either in local DNS, host file or something..
Does anyone know how do I fix it?
Hey, the same question was asked here: https://serverfault.com/questions/102647/sendmail-to-local-domain-ignoring-mx-records-part-2
and the answer to it works for me, don't forget to include the dot after the domain!
If it doesn't work to the test call and see how the mail traces.
best of luck, svullo