DMARC with internet providers

If your provider has set up DMARC, you unfortunately can no longer use that email address in our application.

DMARC (Domain-based Message Authentication, Reporting & Conformance) is a security standard that helps to protect email domains against exploitation, such as phishing and spoofing. You can read here what exactly DMARC is and how it works.

Internet providers

More and more internet providers are setting up DMARC, to prevent phishing email being sent in their name. As a consequence you can no longer use addresses from such providers like Gmail, Ziggo, or Telenet to send digital newsletters through our application. That is because, when you send a newsletter with Laposta, you are using a different emailserver than your provider's official server.

This causes problems for the following reasons:

SPF-fail: The provider has an SPF record that indicated which servers can send emails on behalf of these email addresses. If you send a newsletter through a different server, the server does not comply with the SPF rules of your provider, and the recipient can decide to mark the email as spam or block it entirely.
DKIM-fail: The newsletter server does not have access to your provider's private DKIM key, which makes it unable to sign the email with a valid DKIM signature.
DMARC-fail: Because the newsletter server does not comply with your provider's SPF and DKIM rules, the DMARC verification will fail. This leads to your email being rejected or marked as unsafe.

Which email addresses can't you use as the sender address?

As far as we know, it concerns the following domains:

@casema.nl
@ezorg.nl
@freedom.nl
@gmail.com
@hccnet.nl
@home.nl
@icloud.com
@mac.com
@me.com
@online.nl
@pm.me
@proton.me
@protonmail.com
@proximus.be
@quicknet.nl
@skynet.be
@solcon.nl
@telenet.be
@tutanota.com
@upcmail.nl
@vodafone.nl
@vodafoneziggo.com
@yahoo.com
@ziggo.nl

What can be done about this?

Unfortunately, we have no influence over this, because the domain's settings are managed by the provider. The only option is to add a different sender address to you account.

It's best to use your own domain for this, preferably the domain where you would (potentially) find your website. If you have your own domain, you only have to authenticate it by adding to records to the DNS-settings. You then comply with DMARC-security rules, which increases the chance of your emails safely reaching the recipients, and not getting marked as spam.

You could also use a different (free) email address that is not in the list above. Because you cannot set up an authentication for this email address, there is a somewhat higher chance that using this email address lands your newsletter in your subscriber's spam folder.