FortiMail 5.3.8 Specialist

The size limit that FortiMail will apply to outbound email is determined by the session profile. The session profile in this configuration restricts the message size to 51200 KB. Although the domain configuration shows a higher limit, the session profile settings take precedence for SMTP limits. Therefore, the correct size limit for outbound emails is 51200 KB.

The expected outcome when FortiMail applies this action profile to an email is that a replacement message will be added to the email and virus content will be removed from the email. The profile indicates options for handling infected or suspicious content, including replacing the message, thus adding a replacement message, and removing virus content, making B and C the correct choices.

To ensure clients cannot send unauthenticated emails, configuring an access receive rule to verify authentication status is necessary. This rule will enforce checks at the point of email reception to confirm that the sending client is authenticated, effectively preventing unauthenticated emails from being sent via SMTP.

FortiMail processes emails based on the domain configurations and authentication rules in place. In this scenario, the protected domain is example.com. For unauthenticated senders, the system needs to determine whether to relay emails or not based on an access receive rule. FortiMail will relay emails for the protected domain automatically but requires rules for external domains to avoid open relay situations. In options B and C, the MAIL FROM addresses are not from example.com, while the RCPT TO addresses are from external domains or the protected domain. Therefore, unauthenticated senders for these scenarios would require specific access rules to relay those emails.

The output shows two mail exchange (MX) records for the example.com domain with different preference values. The MX record with the lower preference value (mx.hosted.com with a preference of 10) is prioritized higher. This means external MTAs will send email to mx.hosted.com first, and only if it is unreachable, they will then send emails to mx.example.com which has a higher preference value of 20. Therefore, the primary MTA for the example.com domain is mx.hosted.com, and if it becomes unreachable, then mx.example.com is used. Load balancing is not applicable here as it applies to servers with equal preference values.