MC_Will

Hello guys,

Are you sure wpMandrill is correctly set up? If you try to perform a Password Recovery, the email you got is sent by Mandrill (check full headers)?

We released a new version of wpMandrill last week so we probably broke something somewhere.

I got it. Thanks.

Oh I see… Seems that I need to update Cart66 in my box now ??

Sure, submit a request on https://help.mandrill.com/ and ask them to forward it me.

Hi,

I think it has nothing to do with Cart66. I’ve used them together with no problem at all.

It seems that you have another plugin/process installed that is overriding the wp_mail function so wpMandrill can’t (yeah, they are that jealous!).

I’d recommend you to deactivate all your plugins but wpMandrill… and perform a password reset in your wp blog. if it works, start activating your plugin one at a time until you find the culprit.

If wpMandrill didn’t work even with no other plugin activated, probably your theme has a process running that override the wp_mail function.
Try activating a default theme.

If none of this work, can you tell me a little bit about your installation? OS, Server, WP Version, where is your wp hosted? …

Hello,

Automatic tagging of emails is part of the features of wpMandrill.

This process is done by analyzing the stack trace of calls made by the time wp_mail is called.

So this is why you have tags like wp_retrieve_password wp_newuser_notification, etc.

Sometimes, wpMandrill can’t find the exact function used to call wp_main. In this case, wpMandrill uses ‘wp_call_user_func_array’.

You can change this behavior by using the wp_mandrill_payload wordpress filter. Remove, add or change any tag you want or need. The ‘tag’ parameter of the payload, is an array of three values: General, Automatic and User.

I hope it helps,
Will

Hello,

The process to generate the content parts of the emails is something like this:

– The plugin receives your content once wp_mail is used.
– The process use this content as the HTML part of a email.
– The process generates the TEXT part of the email based on the HTML part.

Optionally, if you have clicked on the NL-to-BR switch, it will replace every New Line character for a BR HTML tag. This is probably the part that is messing with your content.

So the advice is:

If you are sending HTML content, left that NL-to-BR unchecked.

If you are sending PLAIN content (WP default), check that switch.

If you have a mix of HTML and PLAIN emails, leave the switch unchecked and use the filter to create the appropriate content (if you set a TEXT part for your email, it won’t be overwritten).

I hope it helps!

Excellent! Glad it worked!

Uhmm… Please, make sure that the domain of the email address you are using as FROM_EMAIL and REPLY-TO in GF are listed as valid outgoing domains in your Mandrill account.

Did you set WP_DEBUG to true in your wp_config file?

Here’s a nice article about logs. Basically, it depends on how your server is configured:

https://wpmu.org/wordpress-troubleshooting-basics-how-to-check-your-error-logs/

Hello Matt,

I just tested wpMandrill on a vanilla wp installation and GravityForm worked fine for me.

You can set WP_DEBUG to true in your wp_config.php file and see if you find something useful in your logs.

It could be a bug I recently found and that haven’t pushed the fix yet. If you send more than one attachment in an email, it will fail.

This will be fixed in 1.13.

Remember that whenever wpMandrill fails to send the email, it silently defaults to the native wp_mail function. It leaves a message in the log, though.

The only way wpMandrill modify your content is when you activate the NL-to-BR switch.

As the comment beside it states, this switch should only be activated if you are using text-only emails. If you are using HTML it will insert BR tags in your HTML.

if you are sending a mix of text-oly and HTML emails from your installation, you will need to 1) Deactivate the aforementioned switch, and 2) Use the wordpress filter provided by the plugin to decide which emails must be parsed and which not.

What you mean by bad?

Probably you might need to use a template (or at the very least to activate the LF-to-BR switch of the plugin).

Let me know if v1.12 solved the problems you mentioned.

If so, I’ll appreciate if you mark this thread as solved.

Hi

v1.12 might have addressed this issue for you.