You are splitting hairs - But the original questions is how to process large email blasts.
"Large" was not defined - but - I assure you if we look into namecheaps.com's TOS they would shut down a Spam account very quickly.



"...engage in or to instigate actions that cause harm to Namecheap or other customers. Such actions include, but are not limited to, actions resulting in blacklisting any of Our IPs by the any online spam database, actions resulting in DDOS attacks for any servers, etc. Namecheap reserves the right to refuse service to anyone upon Our discretion. Any material that in Namecheap judgment is either obscene or threatening is strictly prohibited and will be removed from Namecheap servers immediately with or without prior notice and may lead to possible warning, suspension or immediate account termination with no refund. You agree that We have the sole right to decide what constitutes a violation of the Acceptable Use Policy as well as what is the appropriate severity of any corrective action to be applied ..."

Large email blasting is a is not very effective - BUT - If someone wants to engage in that services - you need the proper software, bandwidth etc. You are not going to utilize any 3rd party software hosting - whether it is namecheap, Google, Yahoo, Hotmail, etc.


BTW - Your own email server was having a few hiccups this morning:

Microsoft Windows [Version 10.0.19042.746]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>tracert mail.abfunders.com

Tracing route to abfunders.com [198.187.29.122]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 11 ms 14 ms 12 ms 072-031-129-121.res.spectrum.com [72.31.129.121]
3 9 ms 10 ms 16 ms 071-046-027-215.res.spectrum.com [71.46.27.215]
4 15 ms 13 ms 14 ms bundle-ether39.tamp20-car2.bhn.net [72.31.7.199]
5 15 ms 15 ms 13 ms 071-044-003-035.res.spectrum.com [71.44.3.35]
6 28 ms 15 ms 14 ms 0.xe-2-2-1.pr0.atl20.tbone.rr.com [66.109.9.138]
7 17 ms 14 ms 17 ms ae-10.bar3.Orlando1.Level3.net [4.68.111.185]
8 * * * Request timed out.
9 72 ms 78 ms 74 ms 4.7.26.34
10 * * * Request timed out.
11 76 ms 76 ms 79 ms 199.193.7.170
12 110 ms 114 ms 117 ms 199.193.7.46
13 74 ms 80 ms 76 ms premium74-1.web-hosting.com [198.187.29.122]

Trace complete.

C:\Users\Administrator>tracert mail.abfunders.com

Tracing route to abfunders.com [198.187.29.122]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms www.routerlogin.com [192.168.1.1]
2 14 ms 11 ms 13 ms 072-031-129-121.res.spectrum.com [72.31.129.121]
3 10 ms 11 ms 21 ms 071-046-027-215.res.spectrum.com [71.46.27.215]
4 13 ms 16 ms 11 ms bundle-ether39.tamp20-car2.bhn.net [72.31.7.199]
5 18 ms 17 ms 15 ms 071-044-003-035.res.spectrum.com [71.44.3.35]
6 15 ms 22 ms 15 ms 0.xe-2-2-1.pr0.atl20.tbone.rr.com [66.109.9.138]
7 19 ms 19 ms 19 ms ae-10.bar3.Orlando1.Level3.net [4.68.111.185]
8 * * * Request timed out.
9 74 ms 71 ms 74 ms 4.7.26.34
10 * * * Request timed out.
11 75 ms 75 ms 91 ms 199.193.7.170
12 164 ms 97 ms 125 ms 199.193.7.46
13 78 ms 86 ms 92 ms premium74-1.web-hosting.com [198.187.29.122]

Trace complete.

C:\Users\Administrator>

1st issue was the hop to Level 3:
https://ipgeolocation.io/browse/ip/4.7.26.34

2nd issue: 199.193.7.170 - Namecheap
https://ipgeolocation.io/browse/ip/199.193.7.170