cPanel Mailing Lists Not Delivering Emails

I am a member of the board of directors for a non-profit. Since last year I have intermittently receiving emails, as the treasurer of the organization, it would like to see emails, specially those that require my attention. Long story short, the email administration fell on my lap and tired of people giving me funny looks over emails I did not get, I decided to take a look at the email settings

Emails to the board list are forwarded to our personal email accounts and that could be: gmail, yahoo, hotmail, aol (yes…), earthlink (I know..), or whatever else people have.

I ran a trace report on several emails and I discovered I was not the only one – relief or horror? God knows what we missed..

Bounces

Below you can see some of the errors  found for different domains:

RC4-SHA:128: SMTP error from remote mail server after end of data: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html
AES256-SHA:256: SMTP error from remote mail server after end of data: 550 5.7.0 (BAY004-MC2F20) Unfortunately, messages from (208.76.245.163) on behalf of (aol.com) could not be delivered due to domain owner policy restrictions.
Domain s243.c4.crucialx.net has exceeded the max emails per hour (200/200 (100%)) allowed. Message discarded.
RC4-SHA:128: SMTP error from remote mail server after end of data: 550-5.7.1 [208.76.245.163 12] Our system has detected that this message is\n550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail,\n550-5.7.1 this me
Obviously our issue was the settings of the distribution list.  The mailing list failed one or more of the following authentication checks used by the email providers to verify emails are truly sent from the domains they claim to originate from.

cPanel provides options to comply with this protocol

I changed the settings from no (for anonymous lists) to wrap message

dmarc

No
Do nothing special. This is appropriate for anonymous lists. It is appropriate for dedicated announcement lists, unless the From: address of authorized posters might be in a domain with a DMARC or similar policy. It is also appropriate if you choose to use dmarc_moderation_action other than Accept for this list.

Munge From
This action replaces the poster’s address in the From: header with the list’s posting address and adds the poster’s address to the addresses in the original Reply-To: header.

Wrap Message – this worked best
Just wrap the message in an outer message with the From: header containing the list’s posting address and with the original From: address added to the addresses in the original Reply-To: header and with Content-Type: message/rfc822. This is effectively a one message MIME format digest.

We are now receiving all our emails.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s