BugZero | Fortinet BugID 1228574 - Email logs are incomplete when using proxy inspect...

BugZero | Fortinet BugID 1228574 - Email logs are incomplete when using proxy inspect...

Fortinet - Defect ID: 1228574

Email logs are incomplete when using proxy inspection mode with an email profile

Fortinet - Defect ID: 1228574

Email logs are incomplete when using proxy inspection mode with an email profile

Last updated on April 21st, 2026

BugZero Risk Score
8.0 High

Overall: 8.0

Lifecycle: 10.0

Community: 3.7

What is the BugZero Risk Score?

Fortinet Integration

Learn more about where this data comes from

Fortinet Integration

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Bug Details

Priority: Unspecified
Status: Fixed
Impacted Service: Antispam

Description

Email logs are incomplete when using proxy inspection mode with an email profile.

Change history

2026-04-21 Added: 8.0.0

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:No known affected versions

Fixed versions: 8.0.0

Relevant Products

Click on a version to see all relevant bugs

Affected versions:No known affected versions

Fixed versions: 8.0.0

Top Fortinet Defects

8.0Defect ID: 1190878
Incorrect firewall.vip type=server-load-balance global limit in Max Values table
8.0Defect ID: 1198219
Packets are dropped when using auto-asic-offload with EMAC-VLAN over LACP on FortiGate
8.0Defect ID: 1203504
Traffic fails over emac-vlan interface between vdoms when offloading is enabled
8.0Defect ID: 1214413
The handling of "firewall-session-dirty check-all" has been optimized so that changes to interfaces or policies unrelated to the offloaded session will not cause the offloaded session to become dirty
8.0Defect ID: 1215886
Spoofed reply packets bypass FortiGate when strict check is enabled and reply traffic comes from a different interface

Ready to prevent the next vendor outage?