Sage 100

MAS 200 v4.45 (SQL) - Client changed email providers and switched to hosted Exchange / Microsoft 365 (without my knowledge). Email from MAS doesn't work Went into LM Company maint and configured and tested. The following occurs during a test email: Error on 'SendMail'. ChilkatLog: SendEmail: SMTP_Connect: Connecting to SMTP server smtp.office365.com:587 smtp_host: smtp.office365.com smtp_port: 587 domain: abcmfg.com smtp_user: tonyp login_method: NONE or already authenticated CONNECTED to ESMTP server smtp.office365.com:587 subject: test from: tonyp@abcmfg.com 530 5.7.1 Client was not authenticated Failed when sending MAIL FROM:<tonyp@abcmfg.com> 220 CO1PR02CA005.outlook.office365.com Microsoft ESMTP MAIL Service ready at Mon, 17 Jun 2013 18:19:01 +0000

Looks like you don't have a validated user name and password. I have gotten Outlook365 to work on V4.40 so it does work.

Users can successfully email from workstations in Outlook. Tried a different email address and password and didn't work. Looking at Exchange proxy server settings to see if ip relays are allowed.

have you tried taking the user name and password out completely? if authentication is turned off, even a valid username and password will cause the e-mails to fail. doesn't seem likely with office 365 but ............

@DavidOverholt - I tried removing the user name and password and it still didn't work. Exchange is using TLS encryption. I am waiting on the client's outside IT firm that set up Exchange. They are supposed to be ""researching something"". I am beginning to think they don't have a clue.

Be sure the email account is the primary or admin at least for testing. We had a similar issue, took a month to work through. They can only email with the one from address for now. (note from IT during update -- significance is that he's the administrative email for their office 365 environment )

We worked with Microsoft to see if we could get Sage 100 4.50 to work with our Exchange Online (Office 365). Microsoft tech said it wasn't compatible because it didn't have settings for Basic Authentication with TLS encryption.

@RonGouveia - Thank you for the heads up. Unfreaking believable - you'd think someone would ask me to check the compatibility before forging ahead with a new email system without my knowledge.

I was able to get it to work on V4.40 . Without basic authentication. Although we have to set outlooks to accepts.

@JimWoodhead - What specifically did you do to get it to work?

What I remember is that we set up a special new user Masmail and then we specified that account and password in email setup in company Maintenance

FWIW - I passed this to one of my network techs. His response: I have yet to encounter an application that supports Office 365's authentication protocol. This, like everything else, has to be configured with an internal SMTP relay, configurable through IIS 6 on a Windows server.

@ScottHickman - This is exactly what we did. We set up an SMTP server on the internal server. The email passes to the internal SMTP server and is relayed using TLS encryption to the office 365 SMTP server. This seemed like the only way around it as Sage 100 doesn't support TLS. I am testing it right now.

@doughiggs, do you have it working? What version of MAS? v2013 does support TLS/SSL.

@BrettZimmerman , It's working now. The version is MAS 200 v4.45 SQL. We set up an SMTP server on the internal server. The email routes to an internal SMTP server and is relayed using TLS encryption to the office 365 SMTP server.

Cool, thanks!