This is filling our error logs lately:
PHP Warning: compact(): Undefined variable $cc
PHP Warning: compact(): Undefined variable $bcc
in wp-mail-api.php line 569
Line 569 is a compact() call, but it seems $cc and $bcc are only declared if $headers is not empty for some reason.
]]>When setting the Mailgun API key from a define statement in wp-config.php it would be helpful if the API key was not even shown on the admin page, but rather was just dots. One reason to set the API key like this is to hide it from view on the admin so that folkks can’t change or see it, but you’ve only gone halfway. This is especially a good idea for agencies.
]]>Looks like the GitHub version is up to 2.1.1 and has been for a month now. But the version here is still 2.1.0.
When will the plugin be updated here?
[04-Sep-2024 13:08:41 UTC] PHP Warning: Undefined array key "SERVER_NAME" in /www/public/wp-content/plugins/mailgun/includes/admin.php on line 85
[04-Sep-2024 13:08:41 UTC] PHP Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /www/public/wp-content/plugins/mailgun/includes/admin.php on line 85I’m running version 2.1.0.
]]>There is a version 2.0, but no changelog. What has changed? I want to read over the changelog fior such a major version bump before installing it.
]]>We are facing a problem where the emails to the admin are being sent late as opposed to being sent immediately when the order is placed.
]]>Dear Mailgun,
As a long time user can; you please provide some details on why the plugin was closed? I like many others around the world heavily rely on this plugin for email. Closing with minimum information sends the signal there was a data breach. Please address your users, so they know whats going on. Thank you for understanding the severity of you actions.
]]>You can add the following to wp-config.php to force the tracking settings:
define( 'MAILGUN_TRACK_CLICKS', 'no' );
define( 'MAILGUN_TRACK_OPENS', 'no' );
But the related settings on the settings page are not disabled, like they are for the other things you can define. This seems like an oversight.
]]>1.9.9 is out, but changelog only shows up to 1.9.8
]]>Dear Mailgun dev,
Since the last update we get the following notice in all our updated sites/shops.
Warning: Undefined global variable $_SESSION in?/xxxxx/wp-content/plugins/mailgun/includes/admin.php?on line?340
Warning: Trying to access array offset on value of type null in?/xxxxx/plugins/mailgun/includes/admin.php?on line?340
WP_DEBUG is switched off, this notice only appears on the WP backend, on top of every page.
We use version: 1.9.8 for all sites that have the display of this warning.
]]>I noticed that the reply-to headers are removed when using the Mailgun WordPress plugin.
If I deactivate the Mailgun plugin reply-to headers work fine.
Is there a way around this?
Thank you,
Joseph
]]>
I have some issues here, the image above is one and the other is im trying to fill the fields fom WordPress but there are a few things that im not sure about like:
<span style=”color: rgb(29, 35, 39); font-size: 14px; font-weight: 600; white-space-collapse: collapse; background-color: rgb(240, 240, 241);”>Mailgun Domain Name</span>?where is this?
Thanks a lot.
]]>Line 340 of /includes/admin.php could use an error check if the value is null. Currently if the plugin cannot fetch the session var, it throws an error. Suggested modification, change this:
if ($_SESSION['settings_turned_of'] === false && ($apiActiveNotConfigured || $smtpActiveNotConfigured) ) { ?>to this:
if (isset($_SESSION['settings_turned_of']) && $_SESSION['settings_turned_of'] === false && ($apiActiveNotConfigured || $smtpActiveNotConfigured)) { ?>Hi there,
This morning, an error has suddenly occurred and I’m assuming it’s to do with a plugin update 3 hours ago.
Thanks for any help you might have.
Cheers,
Wayne
Here’s part of the Warning:
Warning: Undefined variable $_SESSION in /home/48807-43020.cloudwaysapps.com/tnjttnxrku/public_html/wp-content/plugins/mailgun/includes/admin.php on line 340
Call Stack
My website is hacked, and the Mailgun plugin sent out thousands of emails from the client domain linked to Mailgun.?
I reset the key; however, it’s still sending emails. The only way to stop this was to disable the plugin.
How do I fix this? What should I do?
We are having an issue with our password reset functionality. When WooCommerce Memberships is activated, the reset url uses our mailgun domain (mg.hockeyplayersinbusiness.org) instead of the site url (hockeyplayersinbusiness.org). When we disable the Mailgun for WordPress plugin, it works fine. Same as if we activate the Mailgun plugin and disable the WooCommerce Memberships… works fine. When both are activated, however, it does not work. WooCommerce has looked into it and has asked us to reach out to Mailgun… Any suggestions?
]]>Hi,
We use content notify plugin that allow user to subscribe for post .when the post is published/ update it send mail to users. The mail is not receiving for post update.
User receive email for post published but when post update the email are not receiving. But when it tested in local environment the post update mail is working. We asked our hosting as we use mailgun they ask to check with you.
Can you please help us with guidance what might be the issue.
Thanks
]]>This notice appears at the top of wp-admin:
Mailgun now supports multiple regions! The U.S. region will be used by default, but you can choose the EU region. You can configure your Mailgun settings in your wp-config.php file or?here
It is dismissable, for that page, but it re-appears on EVERY. SINGLE. DASHBOARD. PAGE!
Make it stop please! Very annoying to take up that real estate on every single page load.
I do see where you haven’t updated the plugin in 4 months, but this only started appearing in the last week or so. No other notices are behaving this way, so perhaps it has something to with how your notice is hooking into the dashboard notices?
]]>Your plugin has a logo in the top right, but it’s broken, and has been for over a year: https://www.metsquare.com/wp-content/plugins/mailgun/assets/icon-128×128.png
]]>After updating to the latest version of Mailgun on a site where FluentSMTP is also activated, requesting a new password causes a critical error. Disabling Mailgun solves the problem.
I have them both installed because I build new sites with a script that configures the Mailgun plugin during setup. I then set up FluentSTMP manually once the site has been build. In the past there was no issue with Mailgun being active at the same time as FluentSMTP.
The solution for me is obviously to disable Mailgun after configuring FluentSMTP but fixing the issue so it doesn’t happen in this scenario would be better.
]]>It states here that you get 200 mails per day, but when you go to signup it asks you for card details, and then if you don’t it says you only get free emails on a Sandbox.
Please clarify?
Simon
]]>Hi,
Mails have not been sent out since the 27th March. It looks like 1.9.1 broke something (1.9.2 doesn’t work either), rolling back to 1.9 fixes the error for now.
I updated the API key and checked everything over, the only thing that resolved the issue was rolling back the plugin.
Here’s the error on the newer versions when using the test button in the settings area:
Mailgun HTTP API Test Failure; status “400 – Bad Request”
Please advise.
]]>For the ‘From Address’ field in the plugin settings, should I be entering the address like: [email protected] or [email protected] or does it even matter? Thanks!
]]>Hi Guys,
There’s an issue that may have recently been introduced where the “To” address gets added as (an additional) reply-to address on outgoing emails.
The headers definition in the below code block seems to be where the issue originates in plugins/mailgun/includes/wp-mail-api.php:
if (isReplyToOverride()) {
$headers[‘Reply-to’] = $fromString;
}
isReplyToOverride() is defined in plugins/mailgun/includes/mg-filter.php:
function isReplyToOverride() {
$mg_opts = get_option(‘mailgun’);
return (bool)($mg_opts[‘override-from’] ?? false);
}
As a result, headers on incoming emails reveal distinct “Reply-to” and “Reply-To” attributes. It doesn’t seem intuitive that override-from is linked to Reply-to in this way and is causing all sorts of CC-related issues for our clients on replies to form submissions from their website.
If you could please comment on the introduction of this code change I’d appreciate it.
]]>When “Override “From” Details” is selected Yes in the Mailgun settings page, “reply-to” in email clients we have the From Address email id too, eg: no-reply@mg.*****.com, So when we hit reply, mail bounces. Noticed this after the 1.9.1 update. If we set “NO” for Override “From” Details setting, Reply-to don’t have the email id given in the “From Address” setting.
Here is the screenshot from the Gmail: https://snipboard.io/oJTcNs.jpg
]]>I believe there is a bug in wp-mail-api.php line 381. The Content-Type header will never be set because it’s removed from the $headers array earlier on and the isset($headers['Content-Type']) check will always return false.
// Set the content-type and charset
$charset = apply_filters('wp_mail_charset', $charset);
if (isset($headers['Content-Type'])) {
if (!strstr($headers['Content-Type'], 'charset')) {
$headers['Content-Type'] = rtrim($headers['Content-Type'], '; ') . "; charset={$charset}";
}
}I’m trying to set the content type to text/html; charset=UTF-8 but the email is being delivered with text/html; charset=ascii – I presume Mailgun server is automatically adding the header but with the wrong charset.
Can the code producing an error log on the line above be removed, assuming it is handled with the code that was added – or at least add a new?else if ('multipart/alternative' === $content_type)?option on line 314?
With this in place, logs are filling up with output such as below:
[mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternative [mailgun] Got unknown Content-Type: multipart/alternativeHi, i have installed the latest plugin version, created the key from Domain settings > sending api key
I’m steel getting Mailgun HTTP API Test Failure; status “401 – Unauthorized”
]]>Hi, we are switching our WordPress site to use MailGun in the near future, and we want to use the “Batch sending” feature. I understand that we have to implement the mg_use_recipient_vars_syntax filter for this.
Question: is the below ‘minimal’ implementation (e.g. in functions.php) sufficient for this ($recipients being a list of email addresses)?
add_filter( 'mg_use_recipient_vars_syntax', function( $recipients ) { return true; } );
The recent release removed a critical “apply_filters” call from your plugged wp_mail() override. As a result other plug-ins that rely on the “wp_mail” filter to modify message data are being ignored. This affects plug-ins like “Email Templates” which make changes to the message body and/or headers prior to delivery.
]]>