Sage 100

Sage 100 2015 - Paperless office emailing working great. Then last week something happened and now getting this confusing error (aren't they all). Where do I point the IT gurus toward to fix whatever needs to be fixed???? They of course don't think they did anything.... Unable to login to SMTP connection. ChilkatLog: VerifySmtpLogin: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: MASSERVER:jschwenk Architecture: Little Endian; 32-bit Language: ActiveX Need new SMTP connection checkForExistingConnection: Elapsed time: 0 millisec SMTP_Connect: Connecting to SMTP server 192.168.0.253:2525 smtp_host: 192.168.0.253 smtp_port: 2525 smtp_user: sbsadmin ConnectTimeoutMs_1: 30000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. This is an IPV4 numeric address... AddrInfoList: AddrInfo: ai_flags: 4 ai_family: 2 ai_socktype: 1 ai_protocol: 0 ai_addrlen: 16 ai_canonname: (NULL) --AddrInfo --AddrInfoList Connect using IPV4. ipAddress1: 192.168.0.253 myIP_3: 192.168.0.249 myPort_3: 52434 connect successful (2) socketConnect: Elapsed time: 0 millisec InitialResponse: 220 SBS2012.pmw-dom.local Microsoft ESMTP MAIL Service ready at Tue, 16 May 2017 10:39:20 -0500 initialResponse: Elapsed time: 0 millisec Sending STARTTLS after hello. sendingHello: EHLO MASServer sendEhlo: Elapsed time: 78 millisec helloResponse: 250-SBS2012.pmw-dom.local Hello [192.168.0.249] 250-SIZE 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-X-ANONYMOUSTLS 250-AUTH 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250-XEXCH50 250-XRDST 250 XSHADOW helloResponse: Elapsed time: 47 millisec Sending STARTTLS (2)... SmtpStatus: 500 SmtpResponse: 500 5.3.3 Unrecognized command Failed to receive STARTTLS response --SMTP_Connect Failed to connect to SMTP server. Failed. --VerifySmtpLogin --ChilkatLog

What user are they using for login to SMTP in company maintenance? If a person, did they change their password?

The STARTTLS command is being rejected by 192.168.0.253, port 2525. That's probably not the right port for TLS (it looks like an unencrypted obfuscation of SMTP's port 25).

Good thought, but they deny changing it (the admin PW). Issue occurred ""about"" the time when they renewed their SSL(?) certificate from GoDaddy.

I don't think the engine looks to see if the certificate is expired, just that one is there (though I'm not sure about that). I would have them confirm 2525 is the correct port, and then maybe turn off SMTP Encryption as a first test.

The error is occurring before credentials are passed, so it wouldn't be a password issue, at least not yet...

I had a customer with GoDaddy email account for ppo. When they emailed invoices via ppo, and hit the magic 250 sends in one batch, GoDaddy shut down the account, claiming it looked like spam. Might contact GoDaddy.

Errors out with I am testing the connection in company maintenance. I don't think this is a GoDaddy email account but rather the company exchange server. GoDaddy was just used to obtain the SSL certificate.

Like Steve said, STARTTLS is being rejected which probably means Exchange Server rule is not setup for TLS anymore or not using the TLS port. What happens if in Email tab you set SMTP Encryption = None

Same sort of error

And if you change the port to 25 (with Encryption off)?

The next test after that would be SSL/TLS with port 587, but I'm also wondering why STARTTLS doesn't appear in the list. I wonder if IT set up or upgraded their anti-spam package and forgot to re-open 2525...

Thanks all. Turned it over to their IT to research. It looks like they sent it to another SMTP address as a remedy.

Did anyone ever found a solution for this error???? Getting various customers with it...but it sends some of the payroll stubs and gets the error on some others. They are not using GoDaddy....they are using gmail accounts. Is there a limit in gmail that anyone is aware of????

FYI, there was a very extensive conversation about slow direct deposit stub printing in payroll - here - https://90minds-com.socialcast.com/messages/19835391?ref=stream I'm not sure if it ever fully resolved but if you read down to where I started talking about Chris Powers spearheading the problem I think that's where the more relevant information begins.

My customer eventually dropped Sage payroll and went to an outside service. I am not sure what choice they have when they're paying 200 employees weekly and the deposit stubs are taking an hour to grind away on the desktop. From memory, I got a lot of deer-in-headlight responses from Sage.

thanks,,,