The company where I work runs Crystal Reports Server. I am certainly not an expert in this software, but this ended up on my desk so I will do my best to solve the problems.
We have a couple of scheduled reports (scheduled in InfoView) which are supposed to be emailed to a list of recipients when they are run.
We have just migrated to Office365, which has forced us to switch smtp servers. There are some problems related to this, since the Office365 smtp server does not allow non-TLS connections. Please note that these issues are solved. I am running stunnel on a local server, and have verified this setup with several other email clients. Sending emails is not an issue.
The problem comes when I try to get the Crystal Reports Job Server to send the reports. I have configured everything:
Domain: blank
Server name: The IP of the machine running stunnel
Port: 25
Authentication: Login (I have verified that the Office365 smtp uses Login)
User name/password: the same as when testing with other clients
From: The same as user name
When the report is run I get the error message login error. CrystalEnterprise.Smtp: SMTP_E_AUTH_FAILED(535)
I ended up using Wireshark to capture the unencrypted traffic between the mail client (Job Server / other client) and stunnel.
I started by capturing traffic from another client (used jbmail plus at the moment). I retrieved the base64 username and password and decoded them and could verify that they were sent correctly to the smtp server.
I then did the same with the Crystal Reports Job Server and noticed that the username and password are corrupted. It seems like a binary 0 (NUL char) is added to both the password and the username. I am 99% sure that this is the cause of my problems. Does anyone else have any experience with this?