Home › Forums › Quform WordPress › PHP Fatal error: Uncaught exception 'phpmailerException' with message …
- This topic has 7 replies, 2 voices, and was last updated 10 years, 9 months ago by Ally.
- AuthorPosts
- January 25, 2014 at 5:16 pm #8458camel79Participant
Hi,
I get the message “An error occurred submitting the form” when I submit a form. I’m trying to use Gmail as the SMTP server. I followed the steps you show to solve the problem but I still can’t solve the problem.
I also received an email from no-reply@accounts.google.com. The subject of the email is “A suspicious attack was avoided”. The content says “recently, someone signed in with your password to try to access your Google account. This persons used an application, like an email client or mobile device.”
I’ve tried several ways to solve this problem but I can’t. Please let me know how to solve it.
The debug error message is the following:
[25-Jan-2014 14:14:53] PHP Fatal error: Uncaught exception 'phpmailerException' with message 'SMTP Error: Could not authenticate.' in /var/www/html/mydomain.com/wp-includes/class-phpmailer.php:1087
Stack trace:
#0 /var/www/html/mydomain.com/wp-includes/class-phpmailer.php(971): PHPMailer->SmtpConnect()
#1 /var/www/html/mydomain.com/wp-includes/class-phpmailer.php(845): PHPMailer->SmtpSend('Date: Sat, 25 J...', '--b1_b0f029bb56...')
#2 /var/www/html/mydomain.com/wp-includes/class-phpmailer.php(763): PHPMailer->PostSend()
#3 /var/www/html/mydomain.com/wp-content/plugins/iphorm-form-builder/includes/common.php(769): PHPMailer->Send()
#4 /var/www/html/mydomain.com/wp-content/plugins/iphorm-form-builder/includes/common.php(483): iphorm_process_form()
#5 [internal function]: iphorm_process_form_ajax('')
#6 /var/www/html/mydomain.com/wp-includes/plugin.php(429): call_user_func_array('iphorm_process_...', Array)
#7 /var/www/html/mydomain.com/wp-settings.php(368): do_action('wp_loaded')
#8 /var/www/html/mexico in /var/www/html/mydomain.com/wp-includes/class-phpmailer.php on line 1087
January 27, 2014 at 12:25 pm #8462AllySupport StaffYou don't have permission to view this content. Please log in or register and then verify your purchases to gain access.
January 27, 2014 at 1:01 pm #8464camel79ParticipantHi Ally,
Thanks for your response.
Your suggestion solved the problem.Have a great day.
Regards,Fuad
February 3, 2014 at 5:31 pm #8549camel79ParticipantHi Ally,
The solution you gave me was working without problems. However, today I started to make more tests and the same problem showed up again. Same debug error message.
I can follow the same steps you gave me last time to solve the problem, but what if it continues to happen? How can I stop this problem from repeating?
Thanks in advance.
Regards,
Fuad.February 3, 2014 at 5:40 pm #8550camel79ParticipantHi again Ally,
I solved the problem again following your instructions from last time. The problem is that I don’t want this to happen every other day.
Again I received an email from google telling me someone tried to access my account. The access attempts where made from the following locations:
January 25, 2014
IP Address: 192.119.147.187
Location: Wasaga Beach, ON, CanadaFebruary 03, 2014
IP Address: 2607:bd00:0:3::8b9:2cb3
Location: IndonesiaI don’t know what does it mean. Maybe I’m using smtp from your application which is located in Canada and/or Indonesia. I am in Mexico.
Please let me know your comments.
Regards,
FuadFebruary 4, 2014 at 11:41 am #8587AllySupport StaffYou don't have permission to view this content. Please log in or register and then verify your purchases to gain access.
February 6, 2014 at 6:25 pm #8655camel79ParticipantHi Ally,
Thanks again for your response.
My server is located in Dallas, Texas.I created an application-specific password on Google. It seems to be working fine in QuForms. Here are the steps to create an application-specific password on Google.
Regards,
FuadFebruary 7, 2014 at 10:35 am #8658AllySupport StaffYou don't have permission to view this content. Please log in or register and then verify your purchases to gain access.
- AuthorPosts
- You must be logged in to reply to this topic.