You are viewing limited content. For full access, please sign in.

Question

Question

Unable to send an email. Please contact your system administrator. [LFF2000-EmailSubmissionFailure]

asked on June 19, 2022

we receive an error when trying to send e-mail notification as following:

Unable to send an email. Please contact your system administrator. [LFF2000-EmailSubmissionFailure] 

even when we test sending e-mail from inside (Laserfiche Forms Configuration)

the event log:

[500]: One or more errors occurred.

Stack Trace:
Caught exception: System.AggregateException
Message: One or more errors occurred.
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at Laserfiche.SignalR.Client.LFHubProxy.Connect()
   at Laserfiche.SignalR.Client.Factories.LFHubProxyFactory.Create(HubEndPoint hubEndPoint)
   at Laserfiche.PushNotificationService.Master.Services.RegisterService.Register(PushServiceRegisterRequest registerData)
   at Laserfiche.PushNotificationService.Master.PushNotificationService.Register(PushServiceRegisterRequest registerData)
   at SyncInvokeRegister(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Inner exception: System.Net.Http.HttpRequestException
Message: An error occurred while sending the request.


Inner exception: System.Net.WebException
Message: The underlying connection was closed: An unexpected error occurred on a send.
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)

Inner exception: System.IO.IOException
Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
   at System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)
   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)

Inner exception: System.Net.Sockets.SocketException
Message: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state)
   at System.Net.Sockets.NetworkStream.BeginRead(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)

0 0

Replies

replied on June 21, 2022

We are having this same issue trying to use Office365 to send emails.  Office 365 requires STARTTLS and that, I don't think, is available in forms or workflow.  Assistance would be greatly appreciated on this one.  Currently we are using an exchange server, but that won't last forever, and we cannot send to a shared email address.

0 0
replied on June 21, 2022

Xiuhong addressed the original issue below. But for other people who may be reading this thread, both Forms and Workflow do issue StartTLS when connecting to Office365 (or any other SMTP server) when "use SSL" (or "use TLS") is checked in the connection to the mail server.

" Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. " is usually an indication that the protocols are mismatched on the client (Forms/WF) and server (Office 365) sides.  Office 365 requires TLS 1.2. For older versions of Workflow and Forms, you will have to follow the steps in https://support.laserfiche.com/kb/1013919/configuration-information-for-tls-1-2  to configure them to use TLS 1.2 rather than one of the lower protocols. Forms and Workflow 11 will automatically use the OS settings (which is not to say that the OS wouldn't still need to be configured to disable the lower TLS protocols)

0 0
replied on June 21, 2022

I can send email successfully using Office365 with Forms 11.0.2201.20436. Can you run "telnet smtp.office365.com 587" from command prompt on the Forms server to check whether the port is open?

0 0
replied on June 21, 2022

I still get Unable to send an email...

When I use the telnet smtp.office365.com 587, I get this: "220 BLAP220CA0022.outlook.office365.com Microsoft ESMTP Mail Service ready at .... 

Should I do something after that?  I got a message 451 4.7.0 Timeout waiting for client input after that.

0 0
replied on June 21, 2022

That shows the port is open. You can just close the command prompt after that. I suspect it is just some configuration issue on the Office 365 account. Have you checked whether SMTP auth is enabled for your office365 account, you can refer to https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission#enable-smtp-auth-for-specific-mailboxes.

0 0
replied on June 22, 2022

Dears

 

We checked that TLS 1.2 is configured correctly on the Laserfiche apps.

and we checked also that the SMTP auth. is enabled in O365 sender email 

but we still face the same problem when try to send email notifications

laserfiche.PNG
laserfiche TLS.PNG
laserfiche.PNG (28.91 KB)
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.