New Post
Dear PowerDMARC Team,
We have received feedback from many of our customers regarding the current system's limitations in accurately detecting forwarded emails. To address this concern, I would like to propose an enhancement to the forwarding detection mechanism.
Determining whether an email has been forwarded is challenging with DMARC reports alone. While the XML data in DMARC reports can provide some indicators, such as:
many DMARC reports are incomplete. As a result, forwarded emails are often miscategorized as direct volumes, which can lead to inaccuracies.
I propose leveraging the Hosted DKIM feature currently available in PowerDMARC to address this issue. The implementation would involve:
By linking customer DKIM keys to specific email delivery platforms, this approach allows the system to determine whether a DKIM-signed email originates from a legitimate platform or a forwarded source. If the MTA sending the email is not associated with the designated platform, the system can classify it as forwarded.
Increased Value of Hosted DKIM
Simplified DMARC Report Analysis
This feature would not only address customer concerns but also improve the usability and marketability of PowerDMARC’s premium features.
I look forward to discussing this proposal in detail and am happy to provide additional insights or clarifications.
Best regards,
Yoichiro
changed description "Dear PowerDMARC Team, We have received feedback from many of our customers regarding the current system's limitations in accurately detecting forwarded emails. To address this concern, I would like to propose an enhancement to the forwarding detection mechanism. Current Challenges Determining whether an email has been forwarded is challenging with DMARC reports alone. While the XML data in DMARC reports can provide some indicators, such as: ARC pass results via local policy XOA pass results via local policy Presence of the "forwarded" tag many DMARC reports are incomplete. As a result, forwarded emails are often miscategorized as direct volumes, which can lead to inaccuracies. Proposed Solution I propose leveraging the Hosted DKIM feature currently available in PowerDMARC to address this issue. The implementation would involve: Utilizing the Hosted DKIM feature: Customers can register DKIM for better integration. Providing an option for customers who prefer not to use Hosted DKIM: These customers can still register DKIM keys. By linking customer DKIM keys to specific email delivery platforms, this approach allows the system to determine whether a DKIM-signed email originates from a legitimate platform or a forwarded source. If the MTA sending the email is not associated with the designated platform, the system can classify it as forwarded. Benefits of the Proposal Increased Value of Hosted DKIM This enhancement aligns with the previously requested DKIM Flattening feature, further emphasizing the importance of Hosted DKIM. It enhances user convenience and strengthens the case for upgrading to premium plans. Simplified DMARC Report Analysis Customers can focus solely on direct volumes, significantly reducing the time and effort required for analyzing DMARC reports. The separation of forwarded emails from direct volumes ensures more accurate insights for customers. This feature would not only address customer concerns but also improve the usability and marketability of PowerDMARC’s premium features. I look forward to discussing this proposal in detail and am happy to provide additional insights or clarifications. Best regards,
[YourName][YourPosition][YourContactInformation]~~~~ "changed description "Dear PowerDMARC Team, We have received feedback from many of our customers regarding the current system's limitations in accurately detecting forwarded emails. To address this concern, I would like to propose an enhancement to the forwarding detection mechanism. Current Challenges Determining whether an email has been forwarded is challenging with DMARC reports alone. While the XML data in DMARC reports can provide some indicators, such as: ARC pass results via local policy XOA pass results via local policy Presence of the "forwarded" tag many DMARC reports are incomplete. As a result, forwarded emails are often miscategorized as direct volumes, which can lead to inaccuracies. Proposed Solution I propose leveraging the Hosted DKIM feature currently available in PowerDMARC to address this issue. The implementation would involve: Utilizing the Hosted DKIM feature: Customers can register DKIM for better integration. Providing an option for customers who prefer not to use Hosted DKIM: These customers can still register DKIM keys. By linking customer DKIM keys to specific email delivery platforms, this approach allows the system to determine whether a DKIM-signed email originates from a legitimate platform or a forwarded source. If the MTA sending the email is not associated with the designated platform, the system can classify it as forwarded. Benefits of the Proposal Increased Value of Hosted DKIM This enhancement aligns with the previously requested DKIM Flattening feature, further emphasizing the importance of Hosted DKIM. It enhances user convenience and strengthens the case for upgrading to premium plans. Simplified DMARC Report Analysis Customers can focus solely on direct volumes, significantly reducing the time and effort required for analyzing DMARC reports. The separation of forwarded emails from direct volumes ensures more accurate insights for customers. This feature would not only address customer concerns but also improve the usability and marketability of PowerDMARC’s premium features. I look forward to discussing this proposal in detail and am happy to provide additional insights or clarifications. Best regards, Yoichiro **"