I have encountered a problem with the office 365 scan to email. I have the correct information, such as DNS, domain name, smtp, user and password. The problem has occurred on every Versalink machine that I have to install, I was wondering if anybody here is expierencing the same problem. Thanks.
Solved! Go to Solution.
You know you have to actually state what the issue is right?
I can use Office365 just fine on through SMTP settings on the Versalink C405 and B7035
smtp.office365.com on port 587 using STARTTLS
I can also use the Office365 app from App Gallery without issue.
Sorry, I'm not much for SMTP servers, I thought running a Connecter would be essentially running a relay server, which I very much am not doing since I used SMTP.office365.com. So my answer there is either No or I don't know.
Newest firmware is nearly useless as a term, there is the newest available on Xerox.com, the newest available within the printer when you check for upddates and the newest spar version, and all 3 are and can be different. Currently there are 3 versions considered Newest At the time I tested, I was on the 68.10.71 PL1-R1 release
027-779, = Invalid SMTP auth (Usually means you picked the wrong option at the bottom [device vs network])
027-778, = Incorrect SMTP auth (it's a login failure)
016-781= Absolutely no connection and should only be seen in cases where you used an IP address, not a hostname like I did.
it seems the problem comes with the current Firmware 68.10.91 !!
Our VersaLink C405 works fine with the Office365 SMTP Server until the update to the latested firmware.
So we need a fix or i have to make a downgrade if this is possible.
A fix would be yet another spar, which I cannot do here on the forum (I'm not officially here, I just try to keep my skills sharp and find out issues before I have to handle them at my *real* job which is 2nd level support) So you would need to call it in.
A downgrade can be done, but unlike the Connectkey family, Versalink can't just downgrade, you lose settings, and after looking up the method to do so in the service manual, there is just no way I can post it here on the forum without risking more than I'm willing. Sorry. Tech would be needed it seems.
I looked at the release notes for the 2 versions, and it is indeed true, fixes from the older are not in the newer. Which is something that has happened previously, and I will now explain why it happens occasionally.
There are 2 types of release, these are
While some say Spar means Beta, it is absolutely not that, how it works is this.
A General release is tested quite thoroughly for stability, it is tested for months and everything is thrown at it, but that in no way means they test every feature itself, Say they test making a Booklet, they may test that it can make when on Tabloid, but they may not test it for every paper size, and every single submission method etc etc. It is stability testing, as in "Did it crash or print the book?". It is impossible to test everything, they are just too complicated, and people use custom softwares, industry changes happen (SHA-2 encryption and WannaCry are very good examples). So BUGS absolutely can happen, so they make a patch to fix the bug, then when the patch works, they incorporate it into the firmware itself, which is the SPAR release
The Spar release is the General release with the patch added. So, to use the SHA-2 example, all the SMTP servers were upgraded about 2 years ago to use SHA-2, but almost all our printers used and supported just SHA-1, so when the rollover happened, the printers all just stopped, and most of them would display the Generic " I have no idea what the server just said to my login name attempt, but it sure wasn't a language I know, and it won't let me try my password" code (017-714). So Xerox created a patch, tested it worked, rolled it into the firmware, tested that it still worked for email, but did not necessarily make sure that printing a booklet would still work the same, because they never touched the print engine, they don't need to, It isn't impossible that the book code got pooched, but it sure isn't likely either.
So General can gets months of testing, and spars can get hours/weeks, because they just test what has been changed.
And that introduces the problem here, while the General release was in testing, new fixes were still being added to the Launch/General release, and due to the testing taking less time for the spar, the new General release missed a patch or two that is in the spar, because technically, the spar is newer code than the General releases code that came after it, but the release date was earlier for the newer release (spar)
And that is my long winded, hopefully understandable explanation as to how you got new/old release.
the new Spar Release 68.11.12 fixes the Office 365 Mail Problem !!
Installed the Release this morning and now Scan2Mail with smtp.office365.com works again !!
Joe thanks for the screenshot above. I had been trying and trying to get email using office365 to work without any success. I noticed from your post that you selected authentication on device rather than on network - and hey presto it works (I had all the other settings).
Thanks and posting in case anyone else has a similar problem. None of the other solutions I found online worked.
I do not understand why xerox do not go through these settings in detail in their documentation. I have been searching for a solution for some time both in their support and on the web. I now have two colour xerox laser mfp's but will not purchase xerox again. They are currently too difficult to configure. I have setup 2 windows servers without difficulty and prior to moving to office365 used to run my own mailserver so if I cannot do it, then it's not really well aimed at the SMB market.
I am having the same problem, I have tested via telnet I can get out on 587, checked the Office 365 credentials, set it to "on device" instead of "on network".
I was also on 68.10.91 but now have upgraded to the SPAR of 68.11.23.
We are using STARTLS and SMTP AUTH.
When a user does a test scan we get 027-504.
Any help would be greatly appreciated.
Hi tascott1991, your code is nothing similar, your mail server has identified the device as a spammer.
Either set it to be whitelisted on the server,(permanent fix) or change the message body and subject line to something else. (Temporary at best)