shinerweb
Forum Replies Created
-
Post SMTP has no interaction with the receiving mail server at all.
The client must have a filter or a server misconfiguration that is placing those emails into the sent box.Check your form “Email & Action” settings, or, do you have another plugin that is forcing the email address to be used (thus overriding what is being set within Ninja Forms).
Try installing Post SMTP (https://wordpress.org/plugins/post-smtp/) and switching on Debug so you can see the emails going out.
Does your site use the native PHP Mailer or did you already have an SMTP plugin installed?
99.99 out of 100, the emails are sent to whatever you have set the “Emails & Actions” settings to. If the emails are not being sent to the address in your To: field, then it can only be another plugin, or your webhost is forcing the Native PHPmailer to not be able to set the TO: field (I have only seen this on rare occasions and is not likely).
It is more than likely going to be another plugin OR you have the wrong (or no) value stored in your “Emails & Action” step responsible for sending that email.
What plugin or tool/feature are you using to create and send the email.
What do you have within the field, or what creates that field.
@erjjio If you use the ‘old’ method of username and passwords to access a Google mail account, then you do indeed need to have the “enable less secure apps” access to your account” setting enabled.
It’s the same if you set up say a mail client like Thunderbird to access your Gmail account using username and passwords.Google applies the label of “less secure app” to ALL apps that use a password/username to access the account, rather than the more secure method.
A better method is rather than use the actual password for that account, create a unique password just to be used by that app.
Read more here: https://support.google.com/accounts/answer/185833Using this method you would create a password for Thunderbird, a password for SMTP (i.e. for any less secure app).This lets you keep your main Google Email password secret from the other 3rd party apps.
It does mean that you need to switch on 2FA on your Google Account, but that should be done anyway in this day and age (IMHO).A shortcut to App passwords once you’ve switched on 2FA is: https://myaccount.google.com/apppasswords
Regards
Chris
- This reply was modified 6 years, 11 months ago by shinerweb. Reason: added more detail to reason for using App Passwords
You don’t appear to have added an SMTP account with which to send mails and are probably relying on the default PHPMailer functionality.
If you check the email log for the failed mail sending, you should see errors being returned from the attempt to send the email.
It’s likely that your host has disabled PHP Mail functions, changed default ports, or blocked certain ports.
Using an SMTP account or a 3rd party mail provider (such as GMail API, Mandrill, Sendgrid, Mailgun) is the preferred option primarily because it is much more reliable than using the default PHP Mailer functionality.I bet my mortgage on it being the Contact Form because Post SMTP has no ‘logic’ that would cause it to send anything twice.
Post SMTP simply replaces the WP PHPMail function and then sends whatever it is told to send.Check for a BCC in one of your forms, or an additional action if you are using something like Gravity/Ninja/CF7 type form plugin.
Caveat… the latest versions of Post SMTP does have a fallback method that if the sending of the email by the primary method fails, then a secondary backup solution is used. If for some reason an error is being reported by the first mail provider, but the email is still being sent, there is a chance that the backup email would cause a 2nd email to be sent. But that would have been obvious by the two different senders and the only thing you said you saw different was an ID. The different ID suggests two separate emails.
I can’t speak for Caldera forms with any certainty, but I can confirm all is well with Divi forms.
Don’t forget, Post SMTP is basically transparent to any other plugins and themes (other than those that contain their own mailing functions).The idea of Post SMTP is to replace the in-built PHP Mailer functions that a basic WordPress installation would use. PHP Mailer uses your servers PHP to act like a mail server, which can cause issues as these are often abused, so mail sent this way can be treated as spam by recipients.
Using Post SMTP allows you to override the WordPress PHP Mailer function and replace with a number of different ways of sending emails. (i.e. SMTP server where you specify the mail server, username,password, or Gmail/SendGrid/Mailgun etc etc).
Those are much more reliable ways to send emails (providing you have them set up correctly that is – using SPF/DKIM records).The use of Post SMTP is 100% transparent to all other plugins. The other plugins just create an email and send it to WordPress for sending, if Post SMTP is installed, that sends the email instead of the inbuilt WordPress method. As I mentioned above, the one caveat is IF the other plugins have their own mailing functions built in (i.e. it has its own SMTP method to override PHP Mailer).
Post SMTP would not touch another plugins settings. It is more than likely a part of Mandrill’s deactivation routine in that it clears up after itself.
Far too often removing a plugin leaves behind orphan data that after a while can build up. Hence why it’s always best to take a backup of the database and plugins before you remove or disable something.As for Post SMTP picking up Mandrill’s settings, whilst I can’t speak for Yehuda (the post SMTP developer), that would be difficult to maintain. Given you should ideally remove the Mandrill plugin (or any other mailer/SMTP type plugin) before installing Post SMTP (to avoid conflicts), if Mandrill was written correctly, it would have removed its settings so there would be nothing for Post SMTP to read.
However, one suggestion you could make to the Post SMTP developer is the ability to import settings. You could then export your settings from Mandrill (and perhaps later other plugins) and then run an import tool within Post SMTP. That does however assume that Mandrill and perhaps other plugins have a settings export tool! But in Post SMTP’s defence, we’re not talking a ton of variables to import, so for the sake of 2-4 variables, is it worth the hassle?
But just to summarise, I don’t believe Post SMTP removed the settings, I’m 99.9% certain Mandrill probably cleaned up after itself.
Not a problem. (Forgot to mention you were using Post SMTP version 1.7.7 which is some way behind the latest version of 2.0.2 )
First off, you appear to have WP Mail SMTP and Post SMTP installed at the same time.
I’d remove WP Mail SMTP first, and I’d also switch off the Set Email Sender plugin until you’ve sorted this out.You also seem to have a phpmailer_init Action(s)cn_wpplug_setemailsender, email_configuration_mail_bank which I’m not sure where that’s coming from. That suggests it’s playing with the mail settings in some way.
Hopefully disabling both of the above plugins might move that away.You’re also running a very old version of PHP (5.4). Any chance of upgrading to a 7.x version (7.1, 7.2 work for me, I’ve had minor issues with 7.3).
Also, if this is a production site that is live and viewable to the world, I’d remove the “Better Search Replace” plug-in. That plug-in shouldn’t be left on a WordPress install once you’ve done all your searching and replacing. There aren’t known ‘hacks’ but it has the potential to be ‘abused’.
Let me know when you’ve disabled those two plugins and see what happens when you try to send a test email. (On the same screen as the Diagnostic link).
Regards
Chris
Click on Post SMTP in the left hand side bar.
That will bring up the main Post SMTP Setup page.
In the 3rd column, Troubleshooting, click the 2nd option down, “Diagnostic Test”
Copy the information in the panel and paste here.
(If you are worried about having your domain on show, first paste in a Notepad type app and search and replace your domain and replace with something like yourdomain.tld)It doesn’t contain any passwords, or other personal identifiable information.
Can you output your diagnostics here (obfuscating any personal information as required)
Have you set up SPF/DKIM records?
Are you using SMTP or native PHP Mailer?
Can you post the output of your Diagnostics (sanitize any personal data)
The Sender is set by the email address Envelope-From Email Address in the Transport Settings on the Account tab.
The reason being, you could log into your gmail account/SendGrid/MailGun or a different SMTP account domain and send the emails, but setting the Envelope-From Email Address as “website@yourdomain.com”, the MAIL FROM: as “contact-form@yourdomain.com” and the Reply-To: as “sales@yourdomain.com”
This is likely to cause emails to be marked as spam, unless you authorise the email transport to be approved to send email on behalf of “yourdomain.com” (by correctly setting up SPF, DKIM etc).
You cannot change the Envelope-From Email Address on the fly.
The From: and Reply-To: can be set by your plugin and it is those values which are used to send replies to.
You can however set it to something more meaningful, i.e. in the Envelope-From Email Address set it to “outbox@yourdomain.com” or “do_not_reply@yourdomain.com”.
So long as the address here matches the domain in the Authentication, or you have correctly filled out the SPF/DKIM in your domains control panel/zone file, it’ll be fine.