Question

Email Archive: Unable to read data from the transport connection

Import Agent Version 10 Administration

Updated November 8, 2019

asked on November 1, 2019

Hello,

I have installed Import Agent and configured the O365 mail rule and connector to BCC the desired messages to the address generated in the Email Archive profile.

I see the process failing from both the Import Agent server side and the O365 admin side.

Event error on the Import Agent server:

Connection unexpectedly lost. 127.0.0.1:55328

System.IO.IOException

Message: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.

StackTrace: at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at Laserfiche.SMTPServer.MIME.StringReaderStream.ReadLine()
at Laserfiche.SMTPServer.BaseConnection.ReadLine()
at Laserfiche.SMTPServer.RawLineDecoder.ProcessCommands()

O365

Status

Office 365 received the message that you specified, but couldn't deliver it to the recipient (***** autogen email from Email Archive) due to the following error:

Error: 501 5.1.6 Recipient addresses in single label domains not accepted

0 0

Answer

SELECTED ANSWER

replied on November 7, 2019

Hi Kristy,

Do you have a Send Connector configured scoped to the laserficheemailarchiveserver.com domain? That error would suggest that the connector either doesn't exist or isn't configured correctly. To my knowledge Exchange only does a DNS lookup for mail routing flow if the domain in question is not scoped in a connector.

Here's an example from Exchange 2016.

Here's a link to Microsoft's documentation on setting up said connectors in Exchange Online: Scenario: Conditional mail routing in Exchange Online

In their Step 5, you would select "Only when email messages are sent to these domains" and enter "laserficheemailarchiveserver.com"

In their Step 6, you would enter the accessible FQDN of the server you're running Email Archive on.

0 0

Replies

replied on November 1, 2019

Hi Kristy,

It appears Email Archive's auto-generated addresses have a "single label domain" or SLD in the form of <randomString>@LaserficheEmailArchiveServer. See: What Is a Single Label Domain Name?

Simply put, they do not have a domain suffix such as ".com", which can cause issues such as the one you encountered.

Fortunately the fix is easy - add ".com" to the end of the address throughout all relevant Exchange and Email Archive configurations so it reads @LaserficheEmailArchiveServer.com.

I'll file a task to add a domain suffix to the auto-gen'd addresses.

Cheers,

Sam

1 0

replied on November 7, 2019

Hi Sam,

Thanks so much! I'm going to test it out.

Kristy

0 0

View 2 previous replies

replied on November 7, 2019

Hi Sam,

I updated the email address in both Email Archive and the relevant Exchange settings and now see this error in O365 Mail Flow:

Error: 550 5.4.310 DNS domain laserficheemailarchiveserver.com does not exist [Message=InfoDomainNonexistent] [LastAttemptedServerName=laserficheemailarchiveserver.com] [SN1NAM04FT034.eop-NAM04.prod.protection.outlook.com], InfoDomainNonexistent

0 0

SELECTED ANSWER

replied on November 7, 2019

Hi Kristy,

Here's an example from Exchange 2016.

Here's a link to Microsoft's documentation on setting up said connectors in Exchange Online: Scenario: Conditional mail routing in Exchange Online

In their Step 5, you would select "Only when email messages are sent to these domains" and enter "laserficheemailarchiveserver.com"

In their Step 6, you would enter the accessible FQDN of the server you're running Email Archive on.

0 0

replied on November 8, 2019

Hi Sam,

I had the connector configured, but just realized I could modify the full domain portion of the Email Archive auto-gen address to match the externally accessible domain name for the server on which it is running.

It's working now! Thanks so much for your help. I'm super pumped.

1 0

replied on November 8, 2019

You're welcome - great to hear it's working!

I'm actually working on an overhaul to the Email Archive documentation right now. We want it to better reflect how people are using the service and speak to the business use cases.

Are you willing to share what you're using Email Archive for and how that fits into a broader Laserfiche solution?

Specific examples can help us improve the service!

1 0

replied on November 8, 2019

Sure thing!

Our business uses a monitoring system for which our only really 'connection' is through automated emails. Those emails contains data and / or attachments that our team uses as input to an ERP or to initiate a communication string with timed follow ups. It's all quite manual right now: copying and pasting, manual entry. All textbook swivel chair processing.

Having the ability to build Workflows with this input opens up a world of possibilities to us. I'm still discovering the specifics, but am excited to dig in.

2 0

You are not allowed to follow up in this post.

Question

Question

Email Archive: Unable to read data from the transport connection

Answer

Replies

Sign in to reply to this post.