Laposte.net will be requiring all email be authenticated

Starting on September 9th laposte.net will begin requiring email to have valid, aligned authentication. Mail that isn’t authenticated will start to be delivered to the spam folder or rejected at delivery time.

Full details should be published on Laposte’s postmaster page in the next few days but the gist of it is that you must have either SPF that passes and is aligned with the 5322 From: header or a DKIM signature that validates and is aligned with the 5322 From: header.

(Or both. Both is good.)

This will apply to most email, not just bulk email.

If you’ve already done the work to follow Gmail and Yahoo’s requirements for bulk senders then you’re already in compliance at laposte.

Yahoo's mailboxes are full
Changes happen, even if you don't keep up

Related Posts

DNS for white label authentication with SproutDNS

I wrote last year about using “stunt” nameservers for customer subdomain authentication – i.e. dynamically generating all the authentication records needed in DNS for each customer as needed.

Read More

Wildcards and DKIM and DMARC, oh my!

If you’re an ESP with small customers you may have looked at the recent Google / Yahoo requirements around DMARC-style alignment for authentication and panicked a bit.

Read More

Cost of authentication

At the end of last year, Steve wrote a post about the different types of authentication. I thought I’d build on that and write about the costs associated with each type. While I know a lot of my readers are actually on the sending side, I’m also going to talk about the costs associated with the receiving side and a little bit about the costs for intermediaries such as CRM systems or ESPs.

Read More