Email periodically failing to send

Rebecca Maude

Hi,

 

I was wondering if anyone else has faced a periodic issue with email simply failing to send from Metastorm?

 

It's not limited to one process, but across all of our processes we occasionally (starting to be more frequent though - we had 7 occurrences last week) get an error in the log "Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out" and the process moves along to the next step without the email being sent. We rely fairly heavily on email for our processes so it's a bit of a worry that we can't guarantee that they will send. Has anyone else faced this issue? Do you have any pointers for things we can check?

 

Finally, what mechanism does Metastorm use to send email? Is it just SMTP or does it use TLS or something else?

 

Thanks,

Rebecca

Jacob_Eastman

This isn't a failure in BPM sending but into your SMTP server. It looks like when BPM tries to connect to your SMTP server it times out occaisionally:

 

Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out

 

It's possible there were too many connections to your SMTP server at that time for it to respond or it was under heavy load.

 

While BPM has a built in SendEmail() method which is configurable in the following registry key:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Metastorm\e-work\Engine\SMTP

 

Process Designers are free to use C# or other languages in almost any way they choose including coding in their own SMTP methods. So it is possible your email is being sent by a custom (in your process design) email method.