Bill,
true at the edge in MTA is the best solution. But in SA has the
advantage that the customers can WL if they expect a „very important“
mail from a sender with such a MX. In my experience this usually happens
5min after adding the reject to MTA 😉
Have a good one
Tobi
------ Originalnachricht ------
Von "Bill Cole" <[email protected]>
An [email protected]
Datum 07.11.2025 14:34:02
Betreff Re: Score based on MX of evelope / from domain?
On 2025-11-07 at 02:45:46 UTC-0500 (Fri, 7 Nov 2025 08:45:46 +0100)
Benoît Panizzon <[email protected]>
is rumored to have said:
Hi Jimmy
If you have the necessary access to add plugins, the solution involves
creating a custom plugin specifically for this checking and filtering
functionality.
Oh wow, great! Thanks a lot for that template!
A plugin is a fine solution for cases where the MX isn't a perfect spamsign,
but it is also possible for small numbers of bad MXs to handle this absolutely
outside of SA such as with check_sender_mx_access in postfix, or less elegantly
through hosts file entries mapping the MX names to something your MTA will
recognize as bogus.
The advantage to doing that outside of SA is that it allows you to reject spam
that you don't bother to actually receive.
-- Bill Cole
[email protected] or [email protected]
(AKA @[email protected] and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
