The majority of blacklists work on the individual host level (IPv4 /32
or IPv6 /64). If your provider's entire /22 is being listed by public
blacklists then I suspect you either have a very disreputable provider
or the provider has indicated that the /22 is intended for use by
residential/dynamic subscribers only (not for mail servers). Most of the
folks with the "bigger" setups you asked about tend to use reputable
providers, use internet connections intended for servers, or obtain
their own IP space. If you intend to operate an email server, you might
want to find a provider whose policies allow you to do so reliably.
Stefan Bauer wrote on 5/31/2019 12:12 PM:
Hi Noel,
thank you for your reply. You know, in real world, ips/ranges get
blocked from time to time and i would like to be ready for this and
not rely on others :)
The workaround looks indeed crappy - i wonder how others handle this
situation in "bigger" setups? I'm currently having 7000-8000 mails / day.
Stefan
Am Fr., 31. Mai 2019 um 18:37 Uhr schrieb Noel Jones
<njo...@megan.vbhcs.org <mailto:njo...@megan.vbhcs.org>>:
On 5/31/2019 1:48 AM, Stefan Bauer wrote:
> Hi,
>
> I'm running a pair of postfix-servers in different data-centers
> (different ip networks) for outgoing-only delivery. once in a while
> my providers /22 appear on public blacklists, so mails from my
nodes
> also gets rejected.
>
> For this, i have now a third backup-instance in another data center
> that is not visible to my users and only fairly with dummy mails
> used to keep reputation up and good. Howto re-route traffic on
> demand with postfix in case, ip-networks get blocked again?
>
> How do others handle this?
>
> Thank you.
>
> Stefan
