On 8/20/20 8:19 PM, Jack wrote:
On 2020.08.20 18:42, james wrote:
On 8/20/20 1:20 PM, Neil Bothwick wrote:
On Thu, 20 Aug 2020 13:06:39 -0400, james wrote:
As you do document all you are doing, and the information you gather, I
see several interrelated but distinct areas.� hardware, software
(several possibilities for each of several tasks,) network provisioning,
and network configuration.� I'd prefer a better term for that last one -
but I mean things like assuring your IP address doesn't end up (or start
out) in a blacklisted block for any smtp attempts.� In my case, it's
mostly that one (plus spam filtering) which gives me hesitation to
attempt rolling my own.
Black listing seems a valid issue. Here:
Down the list is blacklisting. For me it is simple; if Blacklisting
occurs, based on the IP addresses I get from Frontier, I'll just ask for
different ones and cancel the bad (blacklisted) IPs. I'm telling
Frontier up front, that is the reason for the IPs (to run email
services) and my "commercial, extra cost" service with them. Power of
the checkbook.
Truthfully, I *should* be able to ferret out IP addresses that are
blacklisted, right? This issue seems to now be the only impediment to
continuing this email server(s) of static ip address(es).
Frontier is in this document:
https://www.ipvoid.com/ip-blacklist-check/
So I can just forward this list and any other tools that identify 'black
listed IPs' to my sales contacts at Frontier, Verizon, Spectrum or any
other ISP, willing to sell to me bandwidth, bonded with static IP
addresses, right?
James
