Huge improvement to SPAM protection (forged senders)
Within WebAdmin / Security & Filtering / Acceptance & Routing / Advanced Settings....
Please, please, please add a simple checkbox option to push incoming messages to the Spam folder whenever the incoming message has a "Return-Path" header string value that cannot be found within the "From" header string value.
That feature would complete the SPAM protection described at the following link, which currently does not stop SPAM with forged From addresses.
https://www.axigen.com/knowledgebase/How-to-filter-emails-with-forged-headers_245.html
Why is this not a feature already?
Patrick Shaughness
shared this idea
-
Patrick Shaughness
commented
And another (for example)....
Return-Path: <info@viata.es>
From: iPhone 13<Contact@71662.lnstagramYX.com> -
Patrick Shaughness
commented
Here is another one. We get a lot of these coming through everyday. The feature request described above would enable any Axigen administrator block these SPAM messages with forged senders.
Return-Path: <info@viata.es>
From:Costco unlocked <Contact@TM437.lnstagramYX.com> -
Patrick Shaughness
commented
For example, by checking the checkbox, incoming messages like the following one would be placed in the Spam folder by default....
Return-Path: <0100017ebb83811d-823501f8-4a5f-406e-8536-939200c21016-000000@amazonses.com>
From: My Daily Investor <newsletter@mydailyinvestor.com>