Skip to main content
Question

I can send email with the Emailer transformer, but not with the notification/subscription service

S
Forum|alt.badge.img

Hi,

I have FME Server 2018.1.1.1 - Build 18578 - win64 running on an Amazon EC2 instance and I want to use my company's Amazon SES service to send emails. When using the Emailer transformer, I can send emails without any problems. But using the exact same details (host, username, password, port, etc.) when I try to setup email notification, I just get error messages saying "SSL error occurred. Ensure connection security and port are correct " when trying the "SSL/TLS" option, and "Unable to connect to the email server. Ensure account and password is correct" when trying the "StartTLS" option.

The only difference between the Emailer transformer and the notification setup screen, is that I have to explicitly set encryption to TLS for the Emailer to work. But for the notification setup screen, I can only choose between "SSL/TLS" and "StartTLS" -- not just TLS.

Are there any log files I could read to find more detailed or specific errors on what went wrong when attempting to setup my notification with Amazon SES? Is there any way I can explicitly set the encryption for notifications to use TLS instead of SSL, like I have to do to make the Emailer transformer work? My FME Server engines service is running with a different log-on user than the other FME services, could that be the issue?

3 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+34

Hi @skagen,

Take a look at the Resources>Logs>core>current>subscribers>fmeservercore_email.log file.

 

 

It should have a little more info coming back from AWS. It could be encryption related but it shouldn't be related to the User Account Running the service.

 

 

I've had problems trying to send emails using an SES Email, however, it was because the email I was using in the FROM field wasn't registered with the SES Service. We use the SSL/TLS connection security and it works no problems (We are still on FME 2017.1 though).

 

 

S
Forum|alt.badge.img
  • skagen
  • Author
  • January 4, 2019

Hi,

Thank you @virtualcitymatt

All the details are identical to the details I used for the Emailer transformer, including the "From" address. The only difference between the Emailer transformer and the notification service is the encryption type, where the Emailer transformer has to be set to "TLS" for it to work, but none of encryption options for the notification service seems to work.

The closest thing I could find was "C:\\ProgramData\\Safe Software\\FME Server\\resources\\logs\\core\\current\\subscribers\\email.log" (slightly different file name), but all it contains is this:

 

Fri-04-Jan-2019 10:19:29.791 AM INFORM main 801024 : SMTP Server : email-smtp.eu-west-1.amazonaws.com:587

Fri-04-Jan-2019 10:19:29.792 AM INFORM main 801025 : SMTP Account : censored

Fri-04-Jan-2019 10:19:29.793 AM INFORM main 801026 : Connection Security : STARTTLS

Fri-04-Jan-2019 10:19:29.793 AM INFORM main 801013 : Default Recipients : skjalg.axelsen.skagen@bym.oslo.kommune.no

Fri-04-Jan-2019 10:47:27.164 AM INFORM main 801024 : SMTP Server : email-smtp.eu-west-1.amazonaws.com:587

Fri-04-Jan-2019 10:47:27.164 AM INFORM main 801025 : SMTP Account : censored

Fri-04-Jan-2019 10:47:27.165 AM INFORM main 801026 : Connection Security : STARTTLS

Fri-04-Jan-2019 10:47:27.165 AM INFORM main 801013 : Default Recipients : skjalg.axelsen.skagen@bym.oslo.kommune.no

Fri-04-Jan-2019 10:47:32.261 AM INFORM main 801024 : SMTP Server : email-smtp.eu-west-1.amazonaws.com:587

Fri-04-Jan-2019 10:47:32.261 AM INFORM main 801025 : SMTP Account : censored

Fri-04-Jan-2019 10:47:32.267 AM INFORM main 801026 : Connection Security : STARTTLS

Fri-04-Jan-2019 10:47:32.276 AM INFORM main 801013 : Default Recipients : skjalg.axelsen.skagen@bym.oslo.kommune.no

 

(and so on)

Do I have to turn on verbose somewhere in any of my config files to get more details in this log file?

virtualcitymatt
Celebrity
Forum|alt.badge.img+34
skagen wrote:

Hi,

Thank you @virtualcitymatt

All the details are identical to the details I used for the Emailer transformer, including the "From" address. The only difference between the Emailer transformer and the notification service is the encryption type, where the Emailer transformer has to be set to "TLS" for it to work, but none of encryption options for the notification service seems to work.

The closest thing I could find was "C:\\ProgramData\\Safe Software\\FME Server\\resources\\logs\\core\\current\\subscribers\\email.log" (slightly different file name), but all it contains is this:

 

Fri-04-Jan-2019 10:19:29.791 AM INFORM main 801024 : SMTP Server : email-smtp.eu-west-1.amazonaws.com:587

Fri-04-Jan-2019 10:19:29.792 AM INFORM main 801025 : SMTP Account : censored

Fri-04-Jan-2019 10:19:29.793 AM INFORM main 801026 : Connection Security : STARTTLS

Fri-04-Jan-2019 10:19:29.793 AM INFORM main 801013 : Default Recipients : skjalg.axelsen.skagen@bym.oslo.kommune.no

Fri-04-Jan-2019 10:47:27.164 AM INFORM main 801024 : SMTP Server : email-smtp.eu-west-1.amazonaws.com:587

Fri-04-Jan-2019 10:47:27.164 AM INFORM main 801025 : SMTP Account : censored

Fri-04-Jan-2019 10:47:27.165 AM INFORM main 801026 : Connection Security : STARTTLS

Fri-04-Jan-2019 10:47:27.165 AM INFORM main 801013 : Default Recipients : skjalg.axelsen.skagen@bym.oslo.kommune.no

Fri-04-Jan-2019 10:47:32.261 AM INFORM main 801024 : SMTP Server : email-smtp.eu-west-1.amazonaws.com:587

Fri-04-Jan-2019 10:47:32.261 AM INFORM main 801025 : SMTP Account : censored

Fri-04-Jan-2019 10:47:32.267 AM INFORM main 801026 : Connection Security : STARTTLS

Fri-04-Jan-2019 10:47:32.276 AM INFORM main 801013 : Default Recipients : skjalg.axelsen.skagen@bym.oslo.kommune.no

 

(and so on)

Do I have to turn on verbose somewhere in any of my config files to get more details in this log file?

Hmmm,

 

 

Yeah that's pretty unhelpful but that was the log I was thinking of. Have you tried to test the topic anyway? That might shed a little more light.

 

 

For the SSL/TLS the port needs to be 465 and for StartTLS it needs to be 587 (as you have it). I tested the StartTLS and SSL/TLS on my machine and had no trouble at this end.

 

 

Perhaps it is a frewall issue...The application/service is different so you may need to add the FME Server Core to allow traffic though the specified port?

Reply


Helpful Members This Week

Community Stats

30,894
Posts
117,082
Replies
38,700
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.