8

SparkPost is great, but the UI is a little lacking, but as far as sending is concerned, it works great. My company also just developed and extension for processing bounces from SparkPosts in Civi. https://github.com/proexchange/com.pesc.sparkpost


7

I was asked to post a roundup of a variety of alternatives--the writeup is here: https://civicrm.org/blog/andrewhunt/alternatives-to-mandrill Tommy also suggested I build a calculator to compare costs. [edit follows] We also have some clients using SendGrid, which has worked fairly nicely. An extension by IMBA is available on GitHub (mentioned in the blog ...


5

I'm reasonably sure that if you don't have a valid mail server, the mail will be lost. I mitigate this by installing a mail server (Postfix) on the same server as CiviCRM, and use that to relay to the third-party server. Not only is this more robust - Postfix will hold the e-mails that don't go through while your main mail server is down for testing - but ...


3

The symptom as you describe it seems to be that any mail sent via CiviMail will fail immediately and will cause the recipient to be marked as bounced. CiviMail knows when the remote mail system rejects an email, so if that remote system doesn't work as configured, this is the expected behaviour (frustrating as it must be). You need to understand why ...


3

We did experience that for specific mail providers. Local delivery and most mail providers were fine or not having any non 7bit encoded characters. We ended up forcing a downconversion to 7bit encoding on our MTA prior to signing with DKIM as described here for postfix: http://postfix.1071664.n5.nabble.com/On-DKIM-and-Content-Transfer-Encoding-tp68767p68769....


3

We are using mailjet and it works fine, but they are VERY cautious (eg. they threatened to block us because our spam rate came around 0.08% in three separate mailings, where we are normally < 0.01%) . The main reason we use mailjet is that it's based in the EU, so for privacy reason and with the problems around the safe harbour agreement, we preferred ...


2

You should consider how long the outage will be: if it's more than a day, you may actually want to not send messages during that time if you know they'll arrive well after they're intended. It would be embarrassing to remind people about an even after the fact, for example. If you disable the scheduled jobs for scheduled reminders and outbound CiviMail, ...


2

Setting up GSuite/Gmail as your CiviMail Provider. Decide if Gmail/G Suite is right for you. The limits for GSuite users is 2000 sent messages sent per rolling 24 hour period. Regular @gmail.com users are limited to 500 sent messages per rolling 24 hour period. If you are an organization with less than 1000 email list contacts and you have Gsuite - this ...


1

you could have a look at an extension called CiviProxy we developed a while ago. The major focus is on security as it enbables you to run CiviCRM without having to make your environment publically available. However, most interesting for you is probably the fact that it enables pass-through of tracking data on opening and click-through rates as well as Sign-...


1

1,000 recipients max? I could see how just about any org will quickly run into that limit! We end up using CiviSMTP: http://www.civismtp.com/drupal/ Or SparkPost: https://www.sparkpost.com And that's just two examples - there are many other SMTP options.


1

In my experience, reading the Bcc field is not a reliable source of information, because there is not always available data. Thanks to your question I checked the RFC in response to your question and learned why! What's happening See https://tools.ietf.org/html/rfc2822#page-22 The "Bcc:" field (where the "Bcc" means "Blind Carbon Copy") contains ...


1

Your error is mail() returned failure. That strongly suggests an error outside the PHP stack. Check your SMTP logs; there should be a good clue there. You can also specify an alternate SMTP server if one is available to you.


1

As Mark said this is a known regression and we are looking at an expedited release. However as i can feel even a release this coming US Wednesday may be a bit late. What i would advise you to do is to if you cannot wait make a patch to the file vendor/pear/net_smtp/Net/SMTP.php along the lines of https://github.com/civicrm/civicrm-core/pull/10622/files. ...


1

A good alternative is SendinBlue, because they offer a free plan allowing you to send up to 9k emails/month forever. And the same account can be used to send both transactional emails and newsletters. Plus they have some interesting plugins (WP, PrestaShop,..)


1

We use sendgrid, simple to setup for the entire server. It is free if you have less than 12,000 emails a month. We are moving to 4.7 the sendgrid extension does not support it yet.


1

SparkPost has pretty amazing pricing and is apparently the only alternative Mandrill refer to. Anyone have experience with them?


1

That is disappointing news from Mandrill! I have set up a Mailgun account and done some testing, and the SMTP functionality seems to work fine. I haven't tested this extension (found with a Google search, I don't know anything else about it): https://github.com/teamsinger/uk.teamsinger.civicrm.mailgun "Mailgun bounce processing for CiviCRM"


1

Do you have DKIM keys on your domain? Yahoo and gmail get fed up real quick with poorly structured headers... You could also switch to a service like sendgrid... and manage your reputation there. They will help you with that. You can also easily set up dkim keys to their server so they can be verified as sending email on your domain's behalf...


Only top voted, non community-wiki answers of a minimum length are eligible