Windows issues following Core Agent 2.7.6 and Intercept X 2.0.17 update. See KBA 135504 for more information.
We'd love to hear about it! Click here to go to the product suggestion community
I have a XG 115 at a remote office connected to XG 210 at main office via SSLVPN.
The XG 210 is a SMTP mail relay which works fine. (both are up-to-date as at last night).
There is a MFD at the remote office that has STARTTLS as an option and it can scan-to-email using no-auth.
I have just added another MFD which DOES NOT have STARTTLS as an option, and I cannot get it to scan-to-email. "Please check your SMTP settings"
The SMTP protocol options for SMTP over SSL/TLS are:
(Verify Server Certificate (on/off))
What do I need to do to allow the new MFD to connect to the SMTP Relay?
Thanks in advance,
Njernda Aboriginal Corporation
Hi David Wain As per the post and details, one MED is located at the remote end, what is the location for newly placed MED. It would be great if you could explain the traffic flow and relay communication through, it would help us to assist you better.
In reply to Keyur:
Both printers are at the same location (remote).
Device 1 (can send emails)
Gateway 192.168.6.254 (XG115)
Device 2 (cannot send emails)
Only SSL or TLS available
Main Office Location
Gateway 192.168.10.254 (XG210)
Email Relay allows 192.168.6.0/24
The issue is that Email Relay on the XG210 seems to only allow STARTTLS.