Jesus HC!   How do we disable all of that, I know its 99% USA centric, but
we've seen problems from some of them, if there is no easy way, there needs
to be a kill switch for all "default" whitelisting, because frankly, only
we, the each individual system administrator for our own domains and
networks, should be the only ones to decide who is trustworthy, those who
we trust we add in local.cf they should be the ones that S.A uses and no
other, but there is more chance of a year round snow in Vegas before
default whitelisting is removed from the code base, so should be a user
option to disable capability in one of the main conf file so people know
its there.

On Fri, Sep 18, 2026 at 4:36 AM Bill Cole <[email protected]> wrote:

> An extremely helpful user alerted us to many bitrotted entries in the
> default welcomelist, including domains which no longer resolve at all,
> ones which have changed control, and ones with DNS implying that they do
> not currently send mail.
>
> In response, I have just committed changes to the 60_welcomelist*.cf
> which remove a total of 41 domains. With the exception of bdcimail.com,
> which has recently been reregistered and used to send spam, these
> entries are believed to be effectively dead: they match no mail of any
> sort.
>
>
> --
> Bill Cole
>

Reply via email to