Sage 100

Continuing to have issues with a Sage 100 ERP 2014 upgrade from 4.3 when sending Direct Deposit stubs. Have all the normal constituents (Sage, IT) pointing fingers. What I think is happening is that the DD stubs take 10-15 minutes to create. Then when they go to be emailed I'm thinking maybe the login credentials have timed out or expired Error on 'SendMail'. ChilkatLog: SendEmail: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: xxxx Architecture: Little Endian; 32-bit Language: ActiveX recipients: TO:xxxxx totalCount: 1 --recipients renderToMime: createEmailForSending: xSigningAlg: sha1 Auto-generating Message-ID --createEmailForSending renderToMime: Elapsed time: 0 millisec --renderToMime SmtpConnect: SmtpHost: 192.168.1.6 SmtpPort: 25 SmtpUsername: xxxxx SmtpSsl: 0 StartTLS: 0 Need new SMTP connection checkForExistingConnection: Elapsed time: 0 millisec SMTP_Connect: Connecting to SMTP server 192.168.1.6:25 smtp_host: 192.168.1.6 smtp_port: 25 domain: xxx smtp_user: xxx 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.1.6 myIP_3: 192.168.1.35 myPort_3: 51555 connect successful (2) socketConnect: Elapsed time: 0 millisec InitialResponse: 220 xxxMicrosoft ESMTP MAIL Service ready at Tue, 13 Jan 2015 09:36:23 -0500 initialResponse: Elapsed time: 0 millisec sendingHello: EHLO NBEMS-DES sendEhlo: Elapsed time: 0 millisec helloResponse: 250-xxxHello [192.168.1.35] 250-SIZE 30720000 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-AUTH GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250 CHUNKING helloResponse: Elapsed time: 0 millisec login_method: NTLM Using Microsoft SSPI NTLM. response: 535 5.7.3 Authentication unsuccessful Logon denied. Check username, password, and domain NTLM authentication failed Failed to login using NTLM method --SMTP_Connect checkOrMakeSmtpConnection: Elapsed time: 5008 millisec --SmtpConnect Failed. --SendEmail --ChilkatLog

I can test email ok

Long shot but any chance you see MS Sans Serif bold font on the specific RPT file for Direct Deposits

This is a real tough nut to crack. Substitute Gmail as the SMTP and it will stop you after 41 employees then pops up with SMTP Error 454 4.7.0 Too many login attempts, please try again later. Gmail probably works ok for one by one paperless forms delivery but when you have 60+ employees it will anti-spam and cut you off.

Does anyone have an email provider that will not limit the outgoing emails (it looks like Gmail stops at 40 ).

On the phone for almost 4 hours with an end user who upgraded from 4.3 EES to 2014 and they certainly are not pleased that email delivery that worked on 4.3 suddenly does not work with their Exchange Server on 2014 and that we've contacted Sage and their IT department and are no closer to a resolution other than advising to use some type of (yet unknown) SMTP service that will not rate limit them when they need to send 60+ email stubs consecutively. What a nightmare.