Hi, lots of customers are calling in, many versalinks / altalinks are not mailing anymore with the setup like
smtp.office365.com 587 , ttls if avaible (check on/off) auth enabled
"message failed to send"
if we setup mailprotection on port 25 , no issues
its related to TLS 1.2 i think
alreayd tried loading new SPAR firmwares on versalink/altalink, doesnt help
is this a know isse with microsoft in combination with xerox mfp smtp clients?
I can confirm this issue. I have also a few customers with this issue. Sidenote: It seems to be only a Xerox Altalink issue.
I've ask some customers to try relaying, maybe thats an option.
The problem seems to be there randomly, a restart of the MFP will help and scan 2 email is available until the problem randomly appears.
I did also check Office365 changelogs but can't find more information.
I can also confirm that the firmware level of the devices where the problem exist doens't matter. Some of them are running older (SPAR) firmware and i just checked the lastest SPAR release from Juni, but can't find any issues with Office365.
Hopefully there is a solution available.
its indeed strange that we dont have any confirmation yet from Xerox
and indeed its only altalink
there will be a new spar today or tomorrow, allthough i doubt it will be an solution, since spar was already build before
will be release xxx.14010
Fabio, there might be a fix in the new release. But it's only for Xerox Altalink C8030/35
EAP-TLS Certificate issue
Did you see that as well?
do you mean this release? 103.xxx.010.14010
is it already out?
also, if there is indeed 8030/35 in spar descrition, ignore that, its fixed for all models
It means the escalation log nr, was againts a 8030/35
also, today i installed 3 x other 8030 machines, no problems!!
i use the same mailbox on a 8055 , same issue again! :)
seems not yet released, but coming soon!!
do you already have SPAR notes, or where do you have that text coming from?
There you go Fabio. This is FW for Altalink C8030/35
This is a file for UPGRADING. not reloading.
Performed some tests with one of our customers which was having the issue at that moment.
I noticed the following unusual behavior:
- Looking at the time, I noticed Daylight saving time wasn't applied. This means the time on the machine was 1 hour earlier than the actual time.
The machine was set to synchronise over NTP and the time zone is set correctly.
- Looking at the SMTP server settings I noticed the IPv4-option was greyed out. The only available option was Hostname. I expected IPv6 to be grayed out, as we disabled this protocol. But IPv4 should be possible to enable.
- Looking at a netwerk troubleshooting log I noticed that the machine didn't even try to contact the SMTP server when I used the Test configuration button.
The page just started to load, but in the network log not a single line showed that the machine tried to send something. (no DNS, no SMTP).
--> Neither did the machine after I changed the SMTP server to something else. (tried gmail and just a random host name) The network log didn't show any traffic to the configured server.
After a reboot of the machine, IPv4 was back available and the network log showed traffic.
Do you see some of the same things at your customer?
No, thats different in your case;, i actually have traffic to smtp
here also ipv6 disabled, NTP settings are correct, already checked that, also tried manually setting up time
if we use the test button, we actually receive an error on the page, like, failed to send message with a red error