Title: invalid address
Last modified: January 16, 2023

---

# invalid address

 *  Resolved [jillc](https://wordpress.org/support/users/jillc/)
 * (@jillc)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/invalid-address-4/)
 * I’m trying to set up Fluent SMTP – looks okay but then I go to test email and
   it shows: Invalid address: (From): contact@https://www…((mydomain))
 * Is this a conflict with another plugin?

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [Amimul Ihsan](https://wordpress.org/support/users/amimulihsanmahdi/)
 * (@amimulihsanmahdi)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/invalid-address-4/#post-16387993)
 * Hello [@jillc](https://wordpress.org/support/users/jillc/),
 * Can you please mention which email sending service you have configured in Fluent
   SMTP?
 * Let me know the update.
 * Thank you
 *  Thread Starter [jillc](https://wordpress.org/support/users/jillc/)
 * (@jillc)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/invalid-address-4/#post-16391403)
 * Thanks Amimul, I found the problem in functions.php – all working properly now.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘invalid address’ is closed to new replies.

 * ![](https://ps.w.org/fluent-smtp/assets/icon.svg?rev=2458343)
 * [FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider](https://wordpress.org/plugins/fluent-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fluent-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fluent-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/fluent-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fluent-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fluent-smtp/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [jillc](https://wordpress.org/support/users/jillc/)
 * Last activity: [3 years, 6 months ago](https://wordpress.org/support/topic/invalid-address-4/#post-16391403)
 * Status: resolved