Email Invoices from Paperless Office with Attachments 2019

SOLVED

Hi!

We upgraded our client to Sage 100 2019 so that we can take advantage of the new feature that allows for additional attachments when emailing invoices with Paperless Office.  However, we are receiving a Chilkat error where everything seems fine until the end and just up from the bottom is:

SMTP failed when receiving the DATA terminator response

smtpRcvFinal Response: Socket operation timeout

It says that the email Failed but it actually went through with the invoice and the attachment to all recipients.  However, this was just a test for one invoice - what will happen when we send 100?

Does anyone have a suggestion regarding how to correct this?

Thanks.

Janette Marootian

  • 0

    I have the same issue with a client, although they've been live on 2019 for more than a week, today was the first time this error occurred. If anyone has a solution, please let us know.

    John

  • 0
    SUGGESTED

    What is the size of the attachment? What is the SMTP that it is sending to? I believe when chilkat (what Sage 100 uses to send the emails) sends the email it has finished and it doesn't get the terminator response to tell it that everything is done. Looking at their forum, this happens and can be random. Could be that it took too long to respond to the system and it timed out. It could be that the response was sent but it was dropped on the network for some reason. You could try different SMTP servers. I have had some users use SendGrid as the smtp to have email tracking and be able to verify that the email was sent. Some of these hosted SMTP services perform better than a Exim hosted SMTP Server.

  • 0 in reply to T-Man

    The attachment isn't large, the last test that failed the attachment was a purchase order, with two vendor email addresses and the send from email included. It does take a long time to process the email addresses and I think that might be why there's a time out. The SMTP settings are controlled by an a server on the clients domain: mail.clientsname.com on port 25. with company maintenance smtp encryption set to none. The SMTP server is old and that may also be part of the problem.

  • +1 in reply to Johnbhoy
    verified answer

    See if you can test with another SMTP to determine if the issue follows the new SMTP or not. This will help determine if it is an SMTP issue (still could be an internet connection issue, monitor your connection during this time to see if you have drops or delays to the destination)