CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • improving deliverability with SPF, DomainKeys, and/or DKIM sender authentication
Pages: [1]

Author Topic: improving deliverability with SPF, DomainKeys, and/or DKIM sender authentication  (Read 3100 times)

Sean Madsen

  • I post occasionally
  • **
  • Posts: 98
  • Karma: 5
  • CiviCRM implementer/developer
    • Bikes Not Bombs
  • CiviCRM version: 4.6
  • CMS version: Drupal 7
improving deliverability with SPF, DomainKeys, and/or DKIM sender authentication
March 24, 2010, 04:11:23 pm
I am about to start using CiviMail to send out some mailings to our list of about 10,000 subscribers, and before I switch over I'd like to make sure that the proper systems are in place to ensure optimal deliverability.

Here is my setup:
  • CiviCRM 3.1.1 & Drupal 6.9 with PHP 5.2.10 & MySQL 5.1.37 running on a VPS that I have full control over
  • CiviMail configured (and working correctly) with CiviSMTP
  • (Also) staff personal email accounts hosted with gmail through Google Apps

I have sent a test mailing to several test email addresses that I set up with Gmail, Yahoo, Hotmail, and AOL, and a couple of shared hosting servers. All went well except that my message ended up in the Yahoo test user's spam folder.

From the research I've done, it seems like I should set up some sort of sender authentication. What is the best way to proceed?
  • SPF seems easy to set up, so I'm planning to do that using this guide: http://www.kai-mai.com/node/154 Does anyone have any further advice?
  • DomainKeys and DKIM seem slightly different than SPF, and it seems like I should to to implement DomainKeys and/or DKIM in addition to SPF. However DomainKeys and DKIM seem similar to each other and I've read some guides that recommend to only set up one of them. Does that make sense? Which one should I try to set up? Both of these authentication schemes seem to require that the email headers be modified for each message that is sent, which makes me think that the CiviMail application would need to be made aware of this authentication scheme and properly configured to use it. Is that really the case? If so, then is it even possible for me to set up DomainKeys and/or DKIM with my current set up?


xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: improving deliverability with SPF, DomainKeys, and/or DKIM sender authentication
April 01, 2010, 03:07:03 am
Quote from: Sean Madsen on March 24, 2010, 04:11:23 pm
Here is my setup:
  • CiviCRM 3.1.1 & Drupal 6.9 with PHP 5.2.10 & MySQL 5.1.37 running on a VPS that I have full control over
  • CiviMail configured (and working correctly) with CiviSMTP
  • (Also) staff personal email accounts hosted with gmail through Google Apps

For your information, we have pushed (for the next version of civicrm) an improved CRM/Mailing/BAO/Mailing.php
http://issues.civicrm.org/jira/browse/CRM-5957 that adds a Precedence:bulk header that should help being less identified as a spam. If you feel comfortable backporting, might be worthwhile (that's a simple change)

If I'm correct, it means that you are using the smtp servers provided by CiviSMTP to send the emails, right ?

Quote from: Sean Madsen on March 24, 2010, 04:11:23 pm

I have sent a test mailing to several test email addresses that I set up with Gmail, Yahoo, Hotmail, and AOL, and a couple of shared hosting servers. All went well except that my message ended up in the Yahoo test user's spam folder.

yahoo tend to be quite a pain indeed. Finding why it got caught is a bit of black magic, it might simply be because too many mails sent via civismtp have been marked by yahoo as spam.

Are you overriding the VERP ? In my experience, works better (and if you don't want to automatically handle the  "human" replies from within civicrm, then override as it has no impact on the bounce).

Quote from: Sean Madsen on March 24, 2010, 04:11:23 pm

From the research I've done, it seems like I should set up some sort of sender authentication. What is the best way to proceed?
  • SPF seems easy to set up, so I'm planning to do that using this guide: http://www.kai-mai.com/node/154 Does anyone have any further advice?


Worthwhile, you have to include both the ones from gmail and the servers from civismtp (and any other mail server you might use to send emails). Ask them about what is the right configuration.

Quote from: Sean Madsen on March 24, 2010, 04:11:23 pm

  • DomainKeys and DKIM seem slightly different than SPF, and it seems like I should to to implement DomainKeys and/or DKIM in addition to SPF. However DomainKeys and DKIM seem similar to each other and I've read some guides that recommend to only set up one of them. Does that make sense? Which one should I try to set up? Both of these authentication schemes seem to require that the email headers be modified for each message that is sent, which makes me think that the CiviMail application would need to be made aware of this authentication scheme and properly configured to use it. Is that really the case? If so, then is it even possible for me to set up DomainKeys and/or DKIM with my current set up?



if you are using the smtp server from civismtp, that's not something you can change, that's on their side.

Otherwise, no big differences between the two if I recall properly

FYI, I'm using DKIM, mostly because there is a package on debian that interfaces easily with postfix. You don't have to change anything on civicrm, that's something postfix (trying to send the messages from civicrm) does and add the right headers (DKIM-Signature) directly.

Good luck

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

shayaknyc

  • I post occasionally
  • **
  • Posts: 74
  • Karma: 0
Re: improving deliverability with SPF, DomainKeys, and/or DKIM sender authentication
January 07, 2011, 06:58:57 am
Quote from: xavier on April 01, 2010, 03:07:03 am

FYI, I'm using DKIM, mostly because there is a package on debian that interfaces easily with postfix. You don't have to change anything on civicrm, that's something postfix (trying to send the messages from civicrm) does and add the right headers (DKIM-Signature) directly.

Good luck

X+

I'd be really interested in learning more about how you implemented DKIM on postfix so that I could potentially use DKIM on CiviMail from one server, while I use Google Apps (which now supports DKIM) on the same domain name for regular email.

Thanks!

--S

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • improving deliverability with SPF, DomainKeys, and/or DKIM sender authentication

This forum was archived on 2017-11-26.