We support the basic e-mail protocols that you expect. SMTP, IMAP, POP3. We support mail forwarding (aka aliasing), and plus addressing. We offer Roundcube in webmail client.
We’ve mostly taken IP reputation off of the table by using a high reputation pool of IP addresses. If an e-mail fails delivery due to IP reputation, we send again, and again, until we get it right. It’s not your problem and we know that.
We offer a fully featured control panel where you can add domains and e-mail accounts. You can also manage your DKIM keys, setup forwarders, customize your inbound spam filters, and much more.
What sets us apart from the competition is that we are dedicated to the price/quality ratio of our products.
We're always looking to improve every aspect of our business like adding more features to our products.
If you don't find the right plan for you, we are there to listen and to find a solution to suit your needs.
We've gained a reputation as a reliable and honest company with most of our customers coming from referrals.
We take support one step further by tailoring our replies to suit your knowledge, expectations and personality.
If for any reason you are not satisfied with our products then we have a 30 day money back guarantee available for you.
The setup is instant. An email will be sent to you containing all the information.
We accept payments via PayPal, credit/debit cards and bitcoin.
If you’re sending emails to a recipient that uses Office 365 / Hotmail / Outlook / Exchange and they are not receiving your email, this is actually a fairly common report.
When these variables align, we notice a 100% success rate in our response being the same: We delivered it successfully, their mail server accepted it, and whether or not the end user has it in their mailbox (inbox or spam folder) is not within our knowledge or influence. They will need to reach out to their IT department.
This is because Microsoft is the only well known email provider that is also well known to accept email and then not deliver it. They’ve been doing this for years. They will not acknowledge it, they will not admit to doing it. Yet, you can plainly see that they do. Take a look for yourself:
Mail not received, outlook.com response to sending server with Queued – Microsoft Community
Email accepted by hotmail but not delivered – Microsoft Community
Messages reported as 250 queued for delivery, but never received when – Microsoft Community
Sendgrid says emails Delivered but customers with – Microsoft Community
Email accepted by hotmail but not delivered – Microsoft Community
We could go on all day, but the pattern is clear. It doesn’t matter that these emails come from us, or from anywhere in particular. This happens without any clear reason, without any error being given, and without any insight from the recipient provider who will not even acknowledge that it happens. So while we want you to let us prove to you that we did our job, we want to prepare you for the extreme probability that we’ll tell you we did and that we have no ability to influence it beyond that point.
If you’re sending an email and immediately get the response “No such recipient here” there could be multiple answers to what happened. However, the answer we’re going to give here would cover 100% of all instances that users have reported this in the last year.
Most likely you just moved your domain to us and tried to send an email from one user to another inside of that same domain, or you moved more than one domain to us and tried to send an email between the domains. The “No such recipient here” error means you didn’t create that email address yet on our server. But, you might ask, why isn’t it trying to deliver to your previous email host instead of ours? That’s because our servers attempt local delivery first, for domains that are hosted on each server. If the domain exists on that server, it attempts to send locally. If the recipient doesn’t exist locally, it fails.
So now you have to ask yourself some questions:
Is it really worth sending this test email before you finish moving your mail over? Are you okay with making a change to our server’s configuration, which will cause our server to reject inbound mail for your domain if you forget to reverse it after changing your MX records to point to our server, just to send a test email?
If it is worth it, or you don’t intend to move one or more of those domains to have it’s inbound hosted on our servers, then the answer is simple. Log in to DirectAdmin, click on E-mail Manager, click on Email Routing, and uncheck the box that says “Use this server…” next to it. Mission accomplished.
If you change your MX records to point to us later, you’re going to have to reverse that setting or you’ll end up receiving another common error.
If you’re forwarding to Gmail or importing via POP3 to Gmail, you can’t send a test email from the same Gmail account that the email will end up at and expect it to pop up as a new email in your inbox. Gmail doesn’t work that way.
If you have an email at a Gmail account and you need it to end up at that same Gmail account, and you send it from that Gmail account, you already have a copy of it. So then why does it need to be at the top of your inbox? It doesn’t because you’ve already read it (because you sent it), so the test isn’t a real world use case.
This is a common issue with Office 365 / Hotmail / Outlook. You’re in good company in their spam folder. To test out delivery to their service, we created an Office 365 account ourselves. On first login, we found an email that they sent us welcoming us to the service. Guess where that email was? The spam folder.
We wish we were lying about this.
How can you expect any consistency in arriving in the inbox when the people who made the inbox can’t even get their emails there? You can’t, but there are things you can do to help your chances.
You do your best by making sure that you get a 10 out of 10 score from mail-tester.com. It’s simple: Go to mail-tester.com, copy the email address given to you, send an email to it, wait a few seconds, then click the button to check your score. We can’t help your content or domain reputation, but your DNS can get a 10 out of 10 by using our DNS tutorial at https://www.favehosting.com/knowledgebase/4991/DNS-Records.html.
Microsoft has an article published about reporting false positives to them: https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/submit-spam-non-spam-and-phishing-scam-messages-to-microsoft-for-analysis?view=o365-worldwide
If you see this error, let me outline the most likely scenario:
Let’s say you’ve added two domains:
Now you also have yourfirstdomain.com hosted at another service, and you haven’t moved it here yet. You did, however, finish moving yourseconddomain.com to our server.
Now you sent an email from the old email provider for yourfirstdomain.com, to yourseconddomain.com, and received this error back.
This is because our server says “You told me I host this domain. I don’t deliver email from domains that I host without password authentication.” Obviously, your old host isn’t sending a password to our server to authenticate as yourfirstdomain.com, so “Sender verify failed.”
Option 1: Just don’t use this weird transition period to test your email using that specific scenario. You’re only sending test emails anyway, right? Almost every single person that contacts us about this is just “testing” after moving one of their domains to us. If that’s you, it likely isn’t worth you taking the second choice for a “test” just to have to reverse it later (and forget you did it, leading to another common error 550 Authentication Required).
Option 2: Disable the inbound email for the domain you were sending FROM (in our example it was yourfirstdomain.com) via DirectAdmin on our server.
Option 3: Remove the domain from DirectAdmin. If you don’t intend to host it here, no need to have it on the server.
The mildly destructive fix
This is the #2 option from above.
Step 1: Login to DirectAdmin.
Step 2: Click “E-mail Manager“ on the left side.
Step 3: Click “Email Routing” under that.
Step 4: Uncheck “Use this server to handle my e-mails.”
Step 5: Click Save
You need to reverse that checkbox if you move that domain to us later.
This error means that the server which received your email has not been configured to accept email for the recipient domain. That can come from many reasons. If your DNS has been configured for at least an hour and you are consistently receiving this message when sending to your domain, from multiple locations, most likely this article explains the fix.
First, log in to DirectAdmin. Next, select the domain in question from the dropdown box at the top right of the screen. After doing that, look in the menus on the left side for “Email Routing” Click that, and look for a checkbox that says “Use this server to handle my e-mails” next to it. Put a check in the box. This should solve the issue.
When sending an email, you may receive this error:
Your domain has been blocked from sending mail due to failure to comply with SPF policy. If you receive this, it means we sent you a warning and you did not comply. We manually blocked your domain in our outbound filters. Most likely you were sending emails to someone who declined them because your SPF record didn’t match our policy, and when reviewing reasons for failed deliveries your domain came up in our list.
We absolutely require that you use our SPF record to send email through our service. We may not notice if you are not, unless your emails are being declined due to it. Failed deliveries can impact IP reputation, and your failure to take proper measures to ensure that delivery from your domain is possible is not appreciated.
Please don’t test a Gmail forwarder by sending an email to yourself from the Gmail account that you are forwarding to. For example:
If I forward email from email@example.com to firstname.lastname@example.org, and I test this forwarder by sending an email to email@example.com from firstname.lastname@example.org, this will not appear in my inbox at email@example.com. Google conversation view doesn’t allow this to appear like any normal email, because you already have a copy of it in your Sent folder. Test the forwarder from a different email account that isn’t the one you are forwarding to.
Powered by WHMCompleteSolution