Loading...
Answers
MenuWhat would cause messages from my new email address to go to some recipients junk folder? It's a new domain name. Anything I can do on my end?
This question has no further details.
Answers
I have a tremendous amount of experience sending emails from new domains - perhaps 2,000,000 emails per year - and the long and short of it is this: email deliverability is tremendously complex.
Why? For one thing, because of the constant battle between spammers, ISPs, ESPs and other players, among other things. Also, because email still uses some very old and outdated protocols that make this all more difficult.
If your business is going to rely heavily on email, I would encourage to educate yourself now so that you won't be stymied as you grow. Many of the things I learned were through trial and error - which can be excruciatingly frustrating.
Just a few of the things you should immediately begin working on: proper SPF, SenderID, DKIM compliance along with solid DNS set up. Additionally, if you will use email heavily, I would start now putting the pieces in place for later white labeling aa nd possible dedicated IP sending. In terms of the actual email content itself, that is another subject you will want to investigate.
I'm not saying these things to discourage you - but rather to help you avoid the mistakes we made in the past.
If you need a hand getting a little grip on this I probably can steer you in the right direction pretty quickly.
Wish you the best in your endeavor!
Adam
The server could be one item as mentioned already. You can check your domain and server against spam records via http://mxtoolbox.com/.
If you have access to WHM you can make sure there is a TEXT record in DNS for SPF. That is one way email is authenticated as having permission to be sent from an ip.
There are a lot of factors at play when getting caught in the junk folder. Long term, send quality content to trusted emails. In the short term, make sure the URLs you are sending people to match the domain you are sending from? Also, what subject line were you using? Also, what vendor are you sending from?
Related Questions
-
What is the most effective way to store emails prelaunch?
My first question is, how did you get these email addresses? If they physically entered them, simply store them in an encrypted spreadsheet or database for importing into a platform. Of course, the best method is utilizing an email service to initially collect those addresses.PH
-
How do I improve email deliverability from a neglected domain?
It always starts with the list. You mention 'non opt-in' lists, which is certainly more troublesome than any domain name. Your best course of action is to get a new domain, re-confirm the lists you have (requiring the subscriber to click through in order to stay on), and only accept confirmed opt-in lists moving forward. It will decimate your mailing list in the short term, but long-term eliminate your deliverability concerns and improve ROI.BI
-
What should I consider when deciding between building a foreign data center or using a CDN service to improve response time in other countries?
Back in 2010 we went through exercise of first using a local data center and then using a CDN in a different country. Interestingly enough using a remote CDN had much smaller latency. After doing an in depth analysis this is what we discovered. There are two factors that influence your latency: throughput of the pipe and speed of the physical server. Let's start with throughput. Consider two scenarios. In the first one you're using CloudFront from Amazon (or any other big name CDN) which probably has direct connection (or near direct) to the continents fiberoptic pipe. The second scenario is if you build a data center in the country. In this case you will be removed from the main pipe by several hops through internet providers which in turn will narrow the throughput after every hop. Unless you are willing to pay very expensive bill for the access to continents, or at least contries main pipe the latency will be higher than from big name CDN's. The second aspect deals with the type of servers involved in servicing GET requests. You need to install top notch hardware with very speedy SSD hard drives and extremely fast networking cards. You can go as far as start optimizing bus speeds between the components. All that leads to increase in price per server. If you're using a CDN then you're much better off because all of that is taken care of for you and you constantly run on latest and greatest hardware that you don't need to upgrade. Count in the amount of time/money need to be spend to service a data center. From my experience the companies that do administration on demand are slow for near 100% uptime requirements so you will need to hire and staff to do monitoring and maintenance. Also never forget about redundancy that also needs to be provided as your server will fail and will go down. Security is also a concern. My conclusion from the the evaluation done in 2010, which is much stronger today, go with CDN unless you're a Fortune-500 company and need a dedicated special use data center. Current CDN's usially offer multiple data centers at different continents for your disposal that can further shrink your response time. Good luck! Denis.DD
-
What platform does clarity use for autogenerated emails? Should we be building that content and have that setup within our app programming?
You could ask Vincent http://clarity.fm/vincentroy if you have anything further to discuss.. but here's the short version. We built custom code for all our trigger emails & notifications, and use www.sendgrid.com for SMTP API. We looked at others, but I'm friends with the founder at SendGrid and like them personally. For free, you can use Google Mail api (if you send less then 500 messages per day I believe). It's simple / and gets great deliverability. Hope that helps. P.S. The emails I write, hence the personal feelings .. it actually comes from me.DM
-
Which CDN would you recommend for bot detection?
Distil Networks is more like a CDN (Content Delivery Network), so every traffic to customers website should pass through Distil server. In other words you have to point your DNS to their CDN (that can potentially bring down your site). They keep analyzing your website through out and if the traffic is found malicious they block. As you asked about competitors, ShieldSquare as a potential alternative, offers following benefits over Distil: Non-intrusive API integration that will not affect your website performance and uptime. Zero False Positives that will ensure that your genuine users are never troubled. I can offer more direction if I know more about your environment. Best Regards, StevenSP
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.