Sage 100

v5.10.4 user is able to send emails from the ""test"" button in Company maintenance (tested and confirmed), but when trying to send direct deposit forms get an 'error on send mail'. Any ideas on what would be preventing the payroll from sending properly?

Had a similar problem once. I believe there is an issue with the ""send from"" regarding security. Maybe someone else can add more detail.

We looked at that, but from what we can tell, all rights are there. And if it was a send from issues, wouldn't it have failed on the test as well?

Found the thread. Look for a posting from Bruce Kern on 6/5/2014.

will do, thanks @Jon

Is this the one you're talking about @JonParkinson ? https://90minds-com.socialcast.com/messages/20623184

Thanks @RobertWood . I Checked on the Exchange server and the user (on the domain) and the account listed in Company maintenance all have ""Send As"" privileges for the email account being used. I am not an exchange guru by any means, but unless I am checking the wrong places they are set up as they should be. I checked with IT and they agreed that the users have the rights they should based on all the info from that thread. Is there a chance this could be related to the chilkat files???

Logon denied. Check username, password, and domain NTLM authentication failed Failed to login using NTLM method --SMTP_Connect checkOrMakeSmtpConnection: Elapsed time: 5007 millisec --SmtpConnect Failed. Can we safely assume this is NOT a sage issue?

Ran into this exact issue on a 4.3 to 2014 PU4. The only changes I recall we made on the Sage end were to change SMTP encryption from NONE to TL/STARTTLS. It's possible that the IT department (difficult to deal with / outsourced ) also made some changes on Exchange. My original theory is that login to Exchange was timing out because the process of emailing the stubs took several minutes. IT swore that it couldn't be that. Strangely we were able to test emails just fine. I know there was an update to the underlying paperless technology that drives the emailing and I think that may have occurred around 4.4 but not 100%.

Exchange will block SMTP relay by default which is how Sage is sending. If IT has configured a receive connector in MS Exchange server for the sending workstation's IP (or maybe fore the entire LAN's IP) you DO NOT need a login name and password for Exchange. Depending on the Exchange server version you will need to play with the SMTP encryption - usually TLS/StartTLS works. I NEVER configure any send as.

While I agree with the ""send as"" issues - I've always observed that the error log will provide information such as ""can't relay or invalid user"" type errors. When you can test the email but the final send doesn't work - I've found it's another issue (wish I knew exactly what).

We tried changing the encryption from none to TL/STARTLLS but didn't have any luck. @JonParkinson are you saying we should clear out all the username/domain info in company maintenance?

Yes - try it with NO user name and password

Ok I will connect up and report back!

@MaryMays Oops, I tagged Jon and not you! That worked!!! You are my hero!