As consumers, we all have at least one free webmail address – when not several for the geekiest of us. Webmail providers like Gmail, Yahoo, AOL, Orange or Outlook are a convenient and powerful way to get a personal email address. A lot of users are even so fond of their webmail address that they sign up for Mailjet using it, rather than a corporate one!
One of the biggest threats when it comes to email, and especially for webmail, is Spam. These providers were at the forefront of this fight, providing users with advanced spam filters to lower the number of unsolicited emails or phishing attempts. While the spam volume decreased in 2015, it’s still high and email industry leaders, including Mailjet, are hard at work to make email a safer medium.
The email community battle against spam
One method to improve your email delivery rates is to incorporate SPF (Sender Policy Framework), and DKIM (Domain Keys Identified Mail), into your DNS settings. With this addition to your DNS entries, you’re telling recipients that you’ve authorized Mailjet to send emails on your behalf.
To further protect your brand from phishing attempts, DMARC (Domain-based Message Authentication, Reporting & Conformance) can be implemented in conjunction with SPF and DKIM.
DMARC is a policy that tells the recipient servers how to react if they receive an email that appears to be sent by you or any “@yourdomain.com” address, when it’s actually not. You can set your DMARC policy to simply monitor the mail being sent using your domain, or you can tell mailbox providers to quarantine it to the spam folder, or reject unauthenticated emails completely.
Yahoo and AOL already implemented a strict DMARC policy (that asks to reject non-identified emails) back in April 2014. Yahoo extended this on 62 ADDITIONAL domains recently, and Google announced that it will do the same later in the year with gmail.com.
What does it mean for Mailjet users?
In other words, if you are using Mailjet to send out emails with a Yahoo email address, or a Gmail one after June 2016, it will bounce – it will be rejected and not even make it to the spam folder. Your recipient’s email server will detect that it is not coming from a legitimate Yahoo or Gmail email server and will refuse it – it’s not even gonna make it to the spam folder. In the near future we expect inbox providers to begin filtering senders that don’t have a DMARC policy protecting their domain. You will not regret being ahead of the curve on this.
Since we have always recommended to use an email address on a customer-owned domain, few of our clients will be impacted by this change. But we want to use this occasion to re-emphasize on the fact that email is a serious aspect of your communication and should be done on domains that you own.
What to do to make sure your sendings are safe?
Head out to your account, in the Sender domain & addresses menu and make sure you don’t have a webmail email address registered in your email addresses list. If you do so, we advise you to make sure it is not in use.
If you do not own an email with your own domain, we strongly advise you to register your own domain, create an email address on this domain, publish your SPF and DKIM records and add this domain and address in your sender domains and addresses list.
We are also working on an alternative solution to enable new users, low-IT resourced clients and infrequent senders to continue sending without going through the hurdle of managing their own domains, and will introduce it pretty soon.
In the meantime, feel free to contact our support team if you need more guidance – we’ll help you make sure the transition to your own sending domain is as smooth as possible.