mardala

I see this often relating to wordpress and cloudflare so thought I’d add this info in case its relevant.

The fix I use for enabling SSL and not running into redirect issues is a bit of a hack, but it works – to ensure the site is forced to SSL I add this before the DB settings in my wp-config:

$_SERVER[‘HTTPS’] = ‘on’;
define(‘WP_HOME’, ‘https://www.yourdomain.com/’);
define(‘WP_SITEURL’, ‘https://www.yourdomain.com/’);

The server var saying https on is what fixes the redirect loop if you are forcing your domain to https. I’ve used this on cpanel servers and our company that uses aws servers behind elb’s.

Regarding ttoomey’s issues, I am guessing if you do the inverse of setting it to empty and forcing the domains to non https you should fix the other redirect issue.

using wp-cli this is what I upgraded from -> to:

| wp-mail-bank | 2.0.10 | 2.0.12 | Updated |

Still an issue. The settings keep getting removed. Just upgraded a site and the smtp domain went blank and I had to re enter the info and save and test again. Kind of an issue when you run large batches of sites.

Something I noticed when a few sites I upgraded – the SMTP settings had to all be re entered. It defaulted back to the email of the admin user (not the email required as the From for the smtp server) and the SMTP server domain was removed.

@Tech-Banker – Everything is ok now. I just disabled and enabled the plugin and that installed the missing table. All settings were kept intact. I already have them set to not auto update so if this is fixed we should be good.

Thanks!

@Tech-Banker – thanks for the fast reply. I just disabled then re-enabled the plugin and that fixed the error.

Fyi – the issue was you changed the database schema but since it auto updated if hosed the site(s) with a SQL error about the missing table mail_bank_meta.

I like the plugin and the new update looks great. But if you can put plugin update in control of the site owner and not the plugin you would save us all a big headache.

We run it, network activated, on a decent sized mutlsite network without any issues.

How are you sending email? ie where are your contact forms sending to? A lot of mail providers (gmail, outlook, yahoo, etc.) are getting very strict about where and how email is formatted.

How are you formatting your from mail header? Mail providers are pretty strict now on origin and dmarc rules etc. I also noticed you don’t have an spf record for that domain. You may want to set one up. Since it looks like both your domain and mail are on the same server you can add a new txt record, something like this:

“v=spf1 ip4: 74.124.210.68 ~all”

How are you formatting the email you are sending? This might be an issue with not formatting your mail according to dmarc specs. Can you get a mailchimp account or something and setup smtp and see if that resolves the issue? I believe you can send for free up to a certain amount.

I think it tries to run an update when activating. Which is why I am noticing activating this plugin on our large multi site network takes a really long time.

To the plugin author – I’d turn this “feature” off. Let updates happen normally and not try to force an update on the admin.

@neilcford – I am getting the same notifications on those files. If you update doing something like wget .. tar xzvf .. then you won’t delete those files if they existed in a previous version of wordpress. Which is my case.

@wfmattr – as a suggestion, maybe checking the files and in the notification mention they were previously part of wordpress core but no longer and mentioning that in the notification? You should be able to md5sum the files and determine if they are part of some exploit or old wordpress core.

I’ll submit to your link as well.

“Although I would strongly advise not doing this and try and find a solution where you set the From and Reply-To correctly.”

The situation is like this FROM email is [email protected] which is routed thru an SMTP server so leads make it to the clients destination since its an email service that requires verification. Then the responding email is set thru the header No-Reply: .. This is valid and used all over the place.

We do have it set correctly. Not every shoe fits every situation. Our clients don’t host their email on the same network / servers their websites are hosted on. When you have thousands of websites running off a cluster of web servers, clients use gmail, outlook, exchange, their own setup, their isp etc for email. We control the DNS but none of their email is on the same domain as the server so we have to use a smtp server for sending. Requiring us to setup an email then an smtp confirmation for thousands of websites is not practical.

Anyways.. not a big deal. But as others have said its just a nagging message that doesn’t go away without disabling it.

I wish this could be turned off. There are so many situations where having a different FROM address is 100% valid, such as what I am dealing with. I can turn it off by commenting out that section in the plugin file that has that error, but thats not the most elegant solution.

@geniecommands its not ISP’s in bed with anti-virus writers. Its because 9 out of 10 email sent is spam. To combat that mail providers are getting very strict on the origin of email. E.g. if you sent a leads form with the FROM address as your gmail address and send to someone who has a yahoo email. Yahoo will notice the from email domain does not match a valid gmail server. So you need to setup the reply-to field as the actual email you want people to respond do, the from email should match the server.

In our case, and as others have mentioned, we have a huge number of sites on a multisite who have leads forms. Since the client domains can have n number of possible email providers we don’t run email off a webserver. To send leads we use an AWS smtp server with a no-reply email from our domain the server runs from. But the CF7 thinks this is invalid when its a very common and valid scenario.