Configuring IFS Connect's Mail Sender for Office 365's authenticated SMTP (needed after moving an older environment, like Apps9, into Azure, since Azure blocks unauthenticated SMTP) fails with a TLS error insisting TLS 1.2 be used as default — caused by an old bundled Java Mail library on the Middleware Server that doesn't support TLS 1.2, with no clear supported way to upgrade that library in place.

All FAQ questions / Integrations and APIs

Answer

This is a real limitation on older releases with an outdated bundled Java Mail library — there's no confirmed, supported way to manually upgrade just that library to get TLS 1.2 support without risking the wider Java Mail integration. The practical workaround that's actually gotten people unblocked is routing outbound mail through a third-party SMTP relay service (like Twilio SendGrid) instead of connecting IFS Connect directly to Office 365's own authenticated SMTP endpoint — the relay service accepts a simpler/compatible connection from IFS Connect and handles the modern-TLS handshake to Office 365 on its own end, sidestepping the old Java Mail library's TLS 1.2 gap entirely.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions