I have the DIVI theme installed in WordPress where I made 2 forms:
Take the turn in the START section
Check in the CONTACT section
I also configured that the automatic response is sent to the users that there is a delay in responding.
These 2 forms if completed arrive at a single email, but I also receive automatic responses that should not happen.
How can I solve that?
Thank you.
I tried to test configuring the forms with DIVI with a single email and the autoresponder appears on the hosting.
Related
I have a client with a Wordpress website. The contact form stopped sending, so I found a plugin called Mail Integration for Office 365/Outlook that could use his MS365 email to send all email from the website using that account.
I installed the plugin and followed the instructions to create an Azure AD App Registration and configure the plugin with the appropriate data from the App Registration. I tried submitting the contact form and there were no errors on the page (it gave me a success message), but the email never arrived in my inbox (yes, I checked spam). I installed a different form plugin, WP Forms, and put it on a test page. The call to admin-ajax appears to be going through successfully, receiving json with success and a confirmation message (which it outputs to the page).
So I searched the plugin's support forum where the creator mentioned using the plugin Check & Log Email to test that the emails are sending. I installed/activated the plugin and sent a test email. It shows it as sent successfully. It never arrived in my inbox (yes, I checked spam).
I have checked the error logs and didn't see anything helpful.
To fix the issue, I first need to find it:
Do I need to complete additional configuration that I've just missed?
How do I find out if the plugin can even connect to the App Registration? It doesn't have a Test Connection feature, which it clearly needs. The reviews on the plugin page are all positive and recent, so it's working for other people.
How do I troubleshoot this from the Azure Active Directory side to make sure it's receiving data?
Please help! Thanks.
I am trying to set up emails on my WordPress website using the WP Mail SMTP plugin and the Gmail API. (WordPress version 5.5.1; WP Mail SMTP Version 2.4.0)
The website I am trying to set this up on, https://souheganvalleychorus.org/ is part of a GSuite for non-profits domain.
I have followed the WP Mail SMTP setup instructions on:
https://wpmailsmtp.com/docs/how-to-set-up-the-gmail-mailer-in-wp-mail-smtp/
with meticulous care. However, when I get to the final step, where I click on the WP Mail SMTP plugin's setup page, and click on "Allow plugin to send emails using your Google account", get prompted with some dialog boxes, choose the email address that I used to set up the Gmail API, it finally comes back with a webpage that says simply:
Unauthorized
Back {a link}
the URL for this page is:
https://souheganvalleychorus.org/wp-admin/options-general.php?page=wp-mail-smtp&tab=auth&code=4/4AEw2mlaJPMgOg7boWHzLLDIJdg0Gwb98vGyJfrteQXcOE5cnL1HMj5wX6QSRZQ0x2rhrbxlzqKPBsF7uokdWCg&scope=https://mail.google.com/
I have been pulling my hair out trying to figure out what is happening, and what I can do to fix it. The 'Unauthorized' provides absolutely no additional information.
I have previously set up the WP Mail SMTP plugin to use the Gmail API, on another website (also a GSuite for non-profits domain, but a different one), and succeeded in that case. I seem to recall having had some problems setting that one up, too, but don't remember how I resolved the issue. When you do something (especially with such an arcane interface as the Google API interface) once in a blue moon, you tend to forget the details. I have tried to compare the two Gmail API setups, and can find no difference that would explain the failure in the current case.
I sure would appreciate anyone's help in resolving this. Until I do, I can't send email from the website. I've also tried using WP Mail SMTP's "Other SMTP" option, with the Gmail SMTP credentials, but that fails to authorize, so I'm stuck...
Help! (and thanks!)
I have just today realised that the authorisation emails sent from my perfectly legitimate Firebase backend are being flagged as malicious by Microsoft Outlook's "Advanced Threat Protection"
There is no reason for this other than perhaps it was flagged during development due to me sending myself repeated confirmation emails in order to test the functionality.
This warning does not show up in regular hotmail/outlook accounts, but I am an Office 365 subscriber so it appears as though I am lucky enough to get this "advanced" protection which protects me from my own completely non-malicious website.
Should I contact Microsoft or Firebase for a solution?
Thanks a lot!
Update: I contacted Firebase support and received the following:
My name is XXXX from Firebase Support, thank you for reaching out to us, problems on Microsoft services such as this “Advanced Threat Protection” is not in my area or expertise, I would suggest to open a ticket with Microsoft for this issue, I see that there is already a topic on Stack Overflow, please be sure to check other Firebase community channels as well.
I understand that this isn't Google's problem to solve, but it would seem any Firebase app using email verification is going to run into trouble with Microsoft email systems. Which is a lot of corporate and government systems...
Any suggestions on how to get some attention paid to this from either Google or Microsoft?
Cause
This error is caused by having inconsistent domains in the email. By default, user management emails link to the default action handler, which is a web page hosted at a URL in your project's Firebase Hosting domain ([project].firebaseapp.com), rather than the the same domain you may be sending emails from (veritification#yourdomain.com).
Solution
Make this “action link” go directly to your website. This will solve the outlook warning, and also make it less likely you'll end up in spam filters in general. On your website, you have 2 options for how to handle the actual validation.
Both solutions below require your domain to be authorized.
This can be done under Authentication -> Sign-In Providers -> Authorized Domains
Option 1 - Use Custom Email Action Handlers (Hard option)
You can setup a custom email action handler so that these actions take place directly on your website, rather than on the firebase hosted page. This is a more integrated experience.
This can handle
Resetting passwords
Revoking email address changes—when users change
their accounts' primary email addresses, Firebase sends an email to
their old addresses that allow them to undo the change
Verifying email addresses
1. Create your custom email handler page
custom email action handler page - firebase docs
2. Update Email Template In Firebase
This can be done under Authentication -> Templates -> Email Address Verification -> Customize Action URL
Option 2 - Just Redirect (Easy option)
Link the email back to a page on your website, that will immediately perform a javascript redirect to the [project].firebaseapp.com authentication page, carrying through the URL parameters required to perform necessary verifications and changes.
For Example
action url for email template: https://www.yourdomain.com/account-action (firebase will attach the appropriate params to the url automatically)
Javascript redirect on your website goes to ”https://project-name.firebaseapp.com/__/auth/action?” + params
I recommend ensuring you implement the continueUrl in your verification email delivery so that the user can easily get back to your website.
If you're using Firebase hosting, and you're serving from their built-in your-project.web.app address, then you can simply use the other built-in, your-project.firebaseapp.com, as your site address instead -- no configuration needed.
The .web.app address is a bit sexier, but the various action emails are actually sent from the .firebaseapp.com, and Outlook is suspicious of the mismatch. Having users originate from the .firebaseapp.com address solves the issue.
I opened a GitHub issue about this: https://github.com/firebase/firebase-js-sdk/issues/5021][1]
I am using "RealHomes Theme" for my project but the problem is while registering as a new user it is successfully adding but unable to get an email verification for the user.
Try disabling all of your plugins and using the default theme.
If you're able to register and get the email, turn on all plugins and try again.
If you still get it, it's an issue with the theme and you should take it up with the developer.
If not, disable all plugins and change back to your RealHomes theme.
If you get it from there, it's a plugin conflict and you'll have to diagnose that and remove/fix the plugin causing the issue.
However, if you can't get it at all, even with the theme/plugins disabled; it's probably because all-to-often WordPress emails get sent into spam or the void, and it's then an email issue which is harder to diagnose (is it your server, potential blacklisting [use MXToolbox to confirm], email provider issue?).
We had this issue a lot, and to mitigate we started to use wpMandrill and enabled DKIM and SPF on all domains we send from which increased out WP email delivery rate to almost 100%.
Make sure you have DKIM and SPF records for your domain, and are sending from an account that exists on the same domain such as:
https://example.com/ should be sending emails from something like WordPress#example.com
I have used contact form 7 (WordPress plugin) for some forms in my website. Now I receive all email forms in info#mysite.com, which is okay. But, there are another option in contact form 7 which is autoresponder (Mail 2). I want to use no-reply#mysite.com email here.
This means that, when people send me an email using my website contact form then they will immediately got reply from no-reply#mysite.com and this email must have to avoid spam folder. If you have any idea about this please share with me.
TIA
You can setup multi smtp servers by using this plugin.
Demonstration:
Here you go with the screen shot. Install this plugin. Go to the multi smtp section. Now put your first smtp server detail and you are done. After that another section will appear for Server 2
demonstration image