I have had users complaining that Sage 100 takes a long time to send emails. We use our own sendmail server as an email server. Upon investigating the logs on the server I noticed some strange behaviour from Sage 100. According to my logs it opens an SMTP connection but does not send an email, 5 second later it does this again. After a few attempts the email is finally sent. To see what I am talking about here is a snippet of my server logs  from when I used the test email function (with identifying information removed):

May 8 13:37:09 myserver sm-mta[18659]: STARTTLS=server, relay=[IP Address of Sage 100], version=TLSv1, verify=NO, cipher=AES256-SHA, bits=256/256
May 8 13:37:09 myserver sm-mta[18659]: w48Hb8sb018659: [IP Address of Sage 100] did not issue MAIL/EXPN/VRFY/ETRN during connection to TLSMTA
May 8 13:37:14 myserver sm-mta[18660]: STARTTLS=server, relay=[IP Address of Sage 100], version=TLSv1, verify=NO, cipher=AES256-SHA, bits=256/256
May 8 13:37:15 myserver sm-mta[18660]: AUTH=server, relay=[IP Address of Sage 100], authid=sage100, mech=LOGIN, bits=0
May 8 13:37:15 myserver sm-mta[18660]: w48HbElS018660: [IP Address of Sage 100] did not issue MAIL/EXPN/VRFY/ETRN during connection to TLSMTA
May 8 13:37:20 myserver sm-mta[18661]: STARTTLS=server, relay=[IP Address of Sage 100], version=TLSv1, verify=NO, cipher=AES256-SHA, bits=256/256
May 8 13:37:21 myserver sm-mta[18661]: w48HbKuH018661: [IP Address of Sage 100] did not issue MAIL/EXPN/VRFY/ETRN during connection to TLSMTA
May 8 13:37:26 myserver sm-mta[18662]: STARTTLS=server, relay=[IP Address of Sage 100], version=TLSv1, verify=NO, cipher=AES256-SHA, bits=256/256
May 8 13:37:26 myserver sm-mta[18662]: AUTH=server, relay=[IP Address of Sage 100], authid=sage100, mech=LOGIN, bits=0
May 8 13:37:27 myserver sm-mta[18662]: w48HbQ0a018662: [IP Address of Sage 100] did not issue MAIL/EXPN/VRFY/ETRN during connection to TLSMTA
May 8 13:37:32 myserver sm-mta[18663]: STARTTLS=server, relay=[IP Address of Sage 100], version=TLSv1, verify=NO, cipher=AES256-SHA, bits=256/256
May 8 13:37:32 myserver sm-mta[18663]: AUTH=server, relay=[IP Address of Sage 100], authid=sage100, mech=LOGIN, bits=0

After that the logs show the normal fair with DKIM signing and relaying the message to its destination. The end result is that it has taken 22 seconds to send a 4kb email. Other clients don't have similar issues, Outlook, Thunderbird and even Gmail can send the first time every time. Because of this I believe the issue is with Sage 100 and not my server, but I haven't the faintest clue how I would go about remedying the situation.