Skip to main content
Solved

mail connector has time-out failure code 4

  • November 20, 2025
  • 8 replies
  • 71 views

Forum|alt.badge.img+1

in our proces flow we use a taask to fill a column which is used as the body of an email that is then send via the email connector.

proces flow monitor is all ok, until the actual sending of the email, then the time-out occurs.

credentials are checked and ok, smtp server is functioning.

 

any tips on what could be causing this issue?

Best answer by Mike Heijstee

Hi Jochem,

 

my apologies!

 

turns out my azure provider had tested, concluded it worked and closed the port again on the VM where i did my test 🤐

 

with port open it works!

 

kind regards, Mike

8 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Mike,

According to the Docs:

-4 - Unsuccessful (error while sending the email to the email server. Check the Indicium error log.)

Process flow connectors | Thinkwise Documentation

Could you inspect the Indicium log to see there is any additional information?


Forum|alt.badge.img+1
  • Author
  • Sidekick
  • November 24, 2025

Hi Mark,

 

this is the text of the live error log:

 

at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 105
at Indicium.Shared.ProcessFlows.SystemActions.EmailConnector.StartInternal(ReadOnlyDictionary`2 inputParameters) in C:\azp\agent\_work\1\s\src\Indicium.Shared\ProcessFlows\SystemActions\EmailConnector.cs:line 317


Forum|alt.badge.img+1
  • Author
  • Sidekick
  • November 24, 2025

and this one from the error log

 


Forum|alt.badge.img+1
  • Author
  • Sidekick
  • November 24, 2025

System.Exception: Failed to send email.
 ---> System.TimeoutException: The operation has timed out.
   at MailKit.Net.SocketUtils.ConnectAsync(String host, Int32 port, IPEndPoint localEndPoint, Int32 timeout, CancellationToken cancellationToken)
   at MailKit.MailService.ConnectNetworkAsync(String host, Int32 port, CancellationToken cancellationToken)
   at MailKit.Net.Smtp.SmtpClient.ConnectAsync(String host, Int32 port, SecureSocketOptions options, CancellationToken cancellationToken)
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.sendMailAsync(SmtpClient client, ISmtpSettings settings, MimeMessage message) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 157
   at Indicium.Shared.Utils.SlidingExpObject`1.performLease(Func`2 onLeased) in C:\azp\agent\_work\1\s\src\Indicium.Shared\Utils\SlidingExpObject.cs:line 114
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 98
   --- End of inner exception stack trace ---
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 105
   at Indicium.Shared.ProcessFlows.SystemActions.EmailConnector.StartInternal(ReadOnlyDictionary`2 inputParameters) in C:\azp\agent\_work\1\s\src\Indicium.Shared\ProcessFlows\SystemActions\EmailConnector.cs:line 317
2025-11-24T13:01:52.1532140+00:00 40000052-0001-ec00-b63f-84710c7967bb [ERR] Process action "email_connector" in process flow "closure_new_customer_email" in application 375 threw an exception. (dedd009e)
 


Forum|alt.badge.img+1
  • Author
  • Sidekick
  • November 24, 2025

the 2525 port has been checked and is working.


Jochem Pieper
Moderator
Forum|alt.badge.img+3

Hi Mike,

What is stated underneath this error log message? 

2025-11-24T13:01:52.1532140+00:00 40000052-0001-ec00-b63f-84710c7967bb [ERR] Process action "email_connector" in process flow "closure_new_customer_email" in application 375 threw an exception. (dedd009e)


That information might be useful to see if the error is occuring from the process flow.

Thanks!


Forum|alt.badge.img+1
  • Author
  • Sidekick
  • November 25, 2025

Hoi Jochem,

 

hierbij het hele bericht

 

at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext context)
   at Indicium.Middleware.Security.AuthenticationHeadersMiddleware.InvokeAsync(HttpContext context) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Authentication\AuthenticationHeadersMiddleware.cs:line 47
   at Indicium.Middleware.Security.SecurityHeadersMiddleware.InvokeAsync(HttpContext context, ContentSecurityPolicyBuilder cspBuilder) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Security\SecurityHeadersMiddleware.cs:line 54
   at Indicium.Middleware.Messages.TSFMessagesMiddleware.Invoke(HttpContext context, IRootApplicationLoader rootApplicationLoader, TSFRequestContext requestContext) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Messages\TSFMessageMiddleware.cs:line 44
   at Indicium.Middleware.Telemetry.ServerTimings.ServerTimingsMiddleware.InvokeAsync(HttpContext context, ServerTimingsBuilder serverTimingsBuilder) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Telemetry\ServerTimings\ServerTimingsMiddleware.cs:line 49
   at Indicium.Middleware.ExceptionHandlingMiddleware.Invoke(HttpContext context, TSFRequestContext requestContext) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\ExceptionHandlingMiddleware.cs:line 34
2025-11-25T08:59:52.4568194+00:00 4000002a-0003-fa00-b63f-84710c7967bb [ERR] Process action "email_connector" in process flow "closure_new_customer_email" in application 333 threw an exception. (dedd009e)
System.Exception: Failed to send email.
 ---> System.TimeoutException: The operation has timed out.
   at MailKit.Net.SocketUtils.ConnectAsync(String host, Int32 port, IPEndPoint localEndPoint, Int32 timeout, CancellationToken cancellationToken)
   at MailKit.MailService.ConnectNetworkAsync(String host, Int32 port, CancellationToken cancellationToken)
   at MailKit.Net.Smtp.SmtpClient.ConnectAsync(String host, Int32 port, SecureSocketOptions options, CancellationToken cancellationToken)
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.sendMailAsync(SmtpClient client, ISmtpSettings settings, MimeMessage message) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 157
   at Indicium.Shared.Utils.SlidingExpObject`1.performLease(Func`2 onLeased) in C:\azp\agent\_work\1\s\src\Indicium.Shared\Utils\SlidingExpObject.cs:line 114
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 98
   --- End of inner exception stack trace ---
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 105
   at Indicium.Shared.ProcessFlows.SystemActions.EmailConnector.StartInternal(ReadOnlyDictionary`2 inputParameters) in C:\azp\agent\_work\1\s\src\Indicium.Shared\ProcessFlows\SystemActions\EmailConnector.cs:line 317
2025-11-25T08:59:52.4573979+00:00 4000002a-0003-fa00-b63f-84710c7967bb [ERR] Process action "email_connector" in process flow "closure_new_customer_email" in application 333 threw an exception. (dedd009e)
System.Exception: Failed to send email.
 ---> System.TimeoutException: The operation has timed out.
   at MailKit.Net.SocketUtils.ConnectAsync(String host, Int32 port, IPEndPoint localEndPoint, Int32 timeout, CancellationToken cancellationToken)
   at MailKit.MailService.ConnectNetworkAsync(String host, Int32 port, CancellationToken cancellationToken)
   at MailKit.Net.Smtp.SmtpClient.ConnectAsync(String host, Int32 port, SecureSocketOptions options, CancellationToken cancellationToken)
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.sendMailAsync(SmtpClient client, ISmtpSettings settings, MimeMessage message) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 157
   at Indicium.Shared.Utils.SlidingExpObject`1.performLease(Func`2 onLeased) in C:\azp\agent\_work\1\s\src\Indicium.Shared\Utils\SlidingExpObject.cs:line 114
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 98
   --- End of inner exception stack trace ---
   at Indicium.Messaging.Email.SMTP.TSFSmtpClient.SendMail(EmailTemplate emailTemplate, IEnumerable`1 toRecipients, IEnumerable`1 ccRecipients, IEnumerable`1 bccRecipients) in C:\azp\agent\_work\1\s\src\Messaging\Email\Indicium.Messaging.Email.SMTP\TSFSmtpClient.cs:line 105
   at Indicium.Shared.ProcessFlows.SystemActions.EmailConnector.StartInternal(ReadOnlyDictionary`2 inputParameters) in C:\azp\agent\_work\1\s\src\Indicium.Shared\ProcessFlows\SystemActions\EmailConnector.cs:line 317
 


Jochem Pieper
Moderator
Forum|alt.badge.img+3

Hi Mike,

Thanks for the additional information. Could you verify that the mail server credentials are 100% correct?
It appears that the current timeout might be related to the accessibility of the server or the server being unable to process the credentials, causing the timeout. Have you tried using these credentials in an email client to confirm that they work correctly?

Best regards,
Jochem


Forum|alt.badge.img+1
  • Author
  • Sidekick
  • Answer
  • November 25, 2025

Hi Jochem,

 

my apologies!

 

turns out my azure provider had tested, concluded it worked and closed the port again on the VM where i did my test 🤐

 

with port open it works!

 

kind regards, Mike