* From a post last week on AOL’s blog about how they have addressed their massive e-mail hack problem…

Today we moved to change our DMARC policy to p=reject. This helps to protect AOL Mail users’ addresses from unauthorized use.

It also stops delivery on what previously would have been considered authorized mail sent on behalf of AOL Mail users via non-AOL servers. If you’re a bulk sender on behalf of AOL addresses, that probably includes mail sent from you.

This can include but is not limited to:

Email service providers (ESP) sending mail on behalf of businesses using AOL addresses
Websites with “Share with a friend” functionality, sending mail using AOL addresses
Small businesses using other 3rd party services to send mail and communication between their employees and / or customers
Services used to forward mail
Mailing lists (listservs)
Mail sent on behalf of AOL Mail users to DMARC-compliant domains will be rejected by those domains unless the mail passes SPF and/or DKIM authentication checks AND the domain(s) used in those checks match aol.com.

We recognize that some legitimate senders will be challenged by this change and forced to update how they send mail and we sincerely regret the inconvenience to you.

That policy change meant I had to change the e-maill address from which the subscriber version of Capitol Fax is sent. I dumped CapitolFax@aol.com and changed it to RichMiller@CapitolFax.com.

This won’t impact most subscribers, but I anticipate some won’t receive it today.

* So, if you’re a subscriber and didn’t receive today’s edition, check your spam e-mail folder. If it’s not there, then you’ll have to instruct your IT folks to “white list” the new RichMiller@CapitolFax.com address.

If neither of those two fixes work, send me an e-mail and we’ll figure it out.