MC_Will

Hi Alex,

Sure, please check this blog post:
https://blog.mandrill.com/own-your-wordpress-email-with-mandrill.html

It has many interesting hacks, including many templates related.

Hi Scott.

Sorry for the delay! It was solved in v1.26

Right now, there’s no way we can filter by API key, not in the plugin but in our API.

I’ve added this request to our road map but I don’t know if it will be available anytime soon.

I’ll keep this thread updated.

Yes Sir!

In the meantime you can use Austin’s hack.

Thanks for keeping an eye on this!

@ovidiu: Sorry, It’s not possible at the moment.

Hi Mediavolt,

You will need to do some PHP code in order to find what’s going on.

The programer will need to:
– Find what’s exactly doing the process that sends the New Job Posting email (what headers are being sent, how is it being sent…)
– Creates a function that logs the parameter to a log file (could be the regular WP log file) and attach it to a wordpress filter called mandrill_payload so it gets triggered every time an email is sent through WP.
– And finally, check that log file.

It’s probably a good idea to get in touch with us at https://help.mandrill.com/home

Hello Mediavolt.

Seems that whatever process that is sending the New Job Post notifications is doing something wpMandrill doesn’t like… and it is sending the email through the native wp_mail function.

One of the reasons why this is probably happening is because the process is adding headers not recognized by wpMandrill, is adding an illegal attachment, using a template the plugin can’t find or something like that.

I’d check what is doing that process exactly in order to send the email, then I’d log the payload to a log file (using the mandrill_payload filter) and see what I cam find there.

Feel free to post the payload here (removing any sensitive information so we can work on it.

Hi Biswajit Ghosh,

I understand. I also understand that when you deactivate BrightCove, everything works as you want.

Problem is BrightCove and wpMandrill are “fighting” to take control of a WordPress function that can only be “owned” by one process: Either BrightCove, Mandrill, or WordPress itself.

There’s no way both plugins can work together. Cart66 had the same problem and we worked together so both plugins could work together. Probably the same solution could be adopted by the developers of BrightCove.

Hi Biswajit Ghosh,

If you are using SMTP to send your email, you should deactivate wpMandrill. They can’t live together.

Hello,

Thanks a lot for your suggestions!

– If the plugin can’t find CURL it tries with fsock* functions. Anyway, we didn’t include any WP function in mandrill.class.php because this class is used in more than one project, most of them not WP-related. I’ll check if it is being used in a WP environment and act accordingly though. Thanks again.
– Many many thanks for the textdomain hint.
– Will clean up all those unused variables.

All the best,
Will

Hey,

Let us know if it gets solved after deactivating the WP Better Emails plugin.

Hi!

Sorry for the delay.

Actually, you can inject code in more than one section. The main one is just the default.

This blog post will probably help you:
https://blog.mandrill.com/own-your-wordpress-email-with-mandrill.html

Hello,

Yes, the plugin will work fine with that load. However, your Mandrill account will have a Sending Hourly Quota based on your “Account Reputation” so the actual number of emails sent within an hour will be limited to that threshold. Additional emails will be queued and sent the next hour so no email will be lost.

You can find more about reputation and quotas here:
https://help.mandrill.com/entries/22038718-how-does-the-account-reputation-and-hourly-quota-system-work

Hey,

This API call is a mirror of the Mandrill send-template call:
https://mandrillapp.com/api/docs/messages.html#method=send-template

If you were using more than one “editable zone” within your template, it would make more sense.