Refer to the exhibits, which display a topology diagram (Topology) and two FortiMail device configurations (FML1 Configuration and FML2 Configuration). What is the expected outcome of SMTP sessions…

Question

Exhibits

Options

• AFML1 will fail to establish any connection with FML2.
• BFML1 will attempt to establish an SMTPS session with FML2. but fail and revert to standard
• CFML1 will send the STARTTLS command in the SMTP session, which will be rejected by FML2.
• DFML1 will successfully establish an SMTPS session with FML2.

• A
  26% (5)
• B
  5% (1)
• C
  11% (2)
• D
  58% (11)

Explanation

Option D is correct because when FortiMail is configured with SMTPS (implicit TLS on port 465), it wraps the entire SMTP session in SSL/TLS from the very first packet - no negotiation needed. If FML1's outbound delivery profile specifies SMTPS and FML2 is listening on port 465 with a valid certificate, the encrypted session establishes successfully without any fallback or command exchange.

• A is wrong because both devices are properly configured to speak the same protocol (SMTPS), so there's no reason for a connection failure.
• B is wrong because SMTPS doesn't "try and fall back" - it either connects on port 465 with TLS or fails outright; fallback behavior applies to STARTTLS, not SMTPS.
• C is wrong because STARTTLS is a command sent within a plain SMTP session (port 25/587) to upgrade it to TLS - SMTPS never sends STARTTLS because TLS is already active before any SMTP commands are exchanged.

Memory tip: Think of SMTPS = SSL first, talk later (like HTTPS) vs. STARTTLS = talk first, then upgrade (like a handshake mid-conversation). If both ends are configured for SMTPS, the session just works - no upgrade command, no fallback.

No community discussion yet for this question.