# SMTP configuration

**URL:** <https://forum.inductiveautomation.com/t/smtp-configuration/67918>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 22, 2022, 10:41am UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918 "2022-12-22T10:41:33Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pierre-Yves\_Burosse](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Pierre-Yves\_Burosse](https://forum.inductiveautomation.com/u/Pierre-Yves_Burosse)\
**Post date:** [December 22, 2022, 10:41am UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/1 "2022-12-22T10:41:33Z")

</div>

Hello,

I am having a problem regarding the usage of an SNTP server with Ignition.  
We opended a email account on our mail provider, with our company main domain, "domainA", and we connected Ignition using the credential from that account. It might be worth noting that the server running Ignition is behind another domain name, "domainB".

Now, whenever Ignition try to send mails, through a notification pipeline or with the test mail function, the message only goes through when it is send to a domainA adress, or to a service by our server provider that we use to send SMS (basically, we send a mail to that service and it sends an SMS to the number specified in the mail object). Every other mail we tried, we have an error "Relay Access denied".

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/5/b503fc5032a803c8797e24f27f0f0b2b6a6ec769.png)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 22, 2022, 4:51pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/2 "2022-12-22T16:51:18Z")

</div>

Sounds like a configuration issue on the SMTP server more than an Ignition issue.

---

<div class="post-metadata">

**Author:** ![Pierre-Yves\_Burosse](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Pierre-Yves\_Burosse](https://forum.inductiveautomation.com/u/Pierre-Yves_Burosse)\
**Post date:** [December 23, 2022, 8:16am UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/3 "2022-12-23T08:16:21Z")

</div>

Well that's what I thought, but when we connect to the very same email account through a regular client, we can send email just fine.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 23, 2022, 1:32pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/4 "2022-12-23T13:32:40Z")

</div>

Your screenshot shows `gmail.com`. Gmail is special.

[https://forum.inductiveautomation.com/search?q=SMTP%20gmail](https://forum.inductiveautomation.com/search?q=SMTP%20gmail)

---

<div class="post-metadata">

**Author:** ![Pierre-Yves\_Burosse](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Pierre-Yves\_Burosse](https://forum.inductiveautomation.com/u/Pierre-Yves_Burosse)\
**Post date:** [December 23, 2022, 1:50pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/5 "2022-12-23T13:50:46Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/6/a6dc5be90dd2a2fcde7a4ee0ebe17d53ab7a5b56.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/8/68c9e65feff7ef282388608ef11b04f3bb01785f.png)  
Maybe, but it isn't the problem here

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 23, 2022, 2:06pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/6 "2022-12-23T14:06:58Z")

</div>

Relay access denied is a common error in mailservers when authentication fails, or perhaps, isn't even attempted. Are you sending through an intermediate mail server? Can you see its logs?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 23, 2022, 2:08pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/7 "2022-12-23T14:08:34Z")

</div>

You don't show the email profile settings. You are also obscuring domain names that might be relevant. You might want to have IA support look over your shoulder.

---

<div class="post-metadata">

**Author:** ![Pierre-Yves\_Burosse](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Pierre-Yves\_Burosse](https://forum.inductiveautomation.com/u/Pierre-Yves_Burosse)\
**Post date:** [December 23, 2022, 2:25pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/8 "2022-12-23T14:25:50Z")

</div>

I don't think I can see the logs for the SMTP server. Whenever a domain name is obscured, it's my company private domain. It is a domain hosted by OVH (french hosting company). They host both our ignition VM, and our SMTP server (which are on different domains). Here is the SMTP config :

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/2/228189655349a943b6f896d56995404c9ba79ee9.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 23, 2022, 2:29pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/9 "2022-12-23T14:29:02Z")

</div>

Many services won't accept authentication in plaintext connections (port 25). Try turning on TLS or STARTTLS.

I bet your working email client is submitting on port 465 or 587, with encryption.

---

<div class="post-metadata">

**Author:** ![Pierre-Yves\_Burosse](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Pierre-Yves\_Burosse](https://forum.inductiveautomation.com/u/Pierre-Yves_Burosse)\
**Post date:** [December 23, 2022, 2:44pm UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/10 "2022-12-23T14:44:22Z")

</div>

Oh, I got it !  
I turned on TLS and STARTTLS, change it to port 465, and change the hostname address to another I found that supports the SSL configuration. I did not think of looking this way because since it connected and I could send some mail, I thought the configuration was correct.  
Thank you very much for pointing me in the right direction !

---

<div class="post-metadata">

**Author:** ![Lavis\_sim](https://avatars.discourse-cdn.com/v4/letter/l/e8c25b/32.png) [@Lavis\_sim](https://forum.inductiveautomation.com/u/Lavis_sim)\
**Post date:** [November 20, 2024, 7:03am UTC](https://forum.inductiveautomation.com/t/smtp-configuration/67918/11 "2024-11-20T07:03:30Z")

</div>

To fix the "Relay Access Denied" error, you might want to consider using a reliable SMTP server like **SMTPmart** , **Google’s Gmail SMTP** , **SMTPget** , **Mailgun** or **Amazon SES**.
