On Tue, Jun 18, 2024 at 6:18 PM Michael Peddemors via mailop < mailop@mailop.org> wrote:
> https://wznoc.com/ > > With a obscure page like that, you are asking for trouble.. > Just like the pages many of the bullet proof hosters throw up.. > > Why not use amscomputer.com in the PTR records, if these are your servers? > I work in the shared web hosting industry, which may be foreign to a lot of people on this list. With shared hosting, 1 physical server and 1 IP address hosts 100s of other websites and email accounts. And some of those accounts are resold accounts that don't need to be aware of the amscomputer.com brand. That's why we use the generic wznoc.com domain. I can assure you that we're not the only ones that operate this way. Take a stroll down the shared hosting industry and you'll find that this is the way it operates. I understand that for the majority of people that are on this Mailops list, they still tend to gravitate towards "one IP address means one domain means one email server." That's not how shared hosting works. The days of one IP address being tied to one domain name being tied to one physical or pseudo-physical server are way in the past. I also would very much like to understand how what a domain's website shows has any bearing at all towards the reputation of a mail sending IP. I'll pose the question to Mailops... do you build your reputation list by visiting the website of the hostname of the reverse DNS of a mailing sending IP and gauge its well-being on the look and feel of that website? Might be a fun exercise, take a look at some of the domains people are writing from on this mailing list. Do an IP address lookup of those domain names. Then do a reverse DNS lookup of those IP addresses - do they always return the same domain name the individual is writing from? What happens if you add an http:// before those IP addresses and try to visit the website of the IP address - does it always show the website for the domain that the individual is writing from? My experience has shown that almost ALL of the blacklisting, blockings, and outright rejection of emails has to do solely with the IP address. Obviously you have to have proper FCrDNS - if you don't have that then that would be grounds for email rejection. Proper SPF, DKIM, and DMARC for the sending domains are also needed. But none of that means a hill of beans if one of the big email service providers want to block or blacklist your sending IP address. One of the things I absolutely hate is the fact that none of the major email service providers (AT&T in this case, Outlook, Yahoo, Gmail) provide no way of checking to see if an IP address is on their blacklist. You only find out that the IP is on their blacklist when a customer tries to send an email to an email address at one of these providers. The first thing I do with any new server or IP address is check it for blacklists at https://multirbl.valli.org - now these IPs may be listed on a couple of blacklists - rbl.rbldns.ru and SPFBL.net RBL - but every IP in existence is on these blacklists. Nothing stands out to me from the reports from multirbl.valli.org that indicates widespread problems. If these IPs were on a bunch of blacklists as reported at multirbl.valli.org then I wouldn't be so upset with the IPs being listed at AT&T (or Microsoft or Yahoo whenever those cases may be). But when an IP address is seemingly only listed at one email service provider, that provides no way to check this - AND THEN proceeds to include an email address for assistance that never gets checked. Yea.. I get upset. Every single person on this mailing list would get upset if they were in those same shoes.
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
