Yes, I'm an old guy, so I know it's been around since the 90s. But not in as widespread use by "companies" as it is today. Many companies in the 90s had onsite microsoft mail servers, or sun/unix/linux mail servers and a lot of the shared hosting was used by individuals and casual users, and spammers.
These days many of the small businesses my clients work with
outsource their mail to hosted exchange or google. I realize a lot
of spam originates from all the various MS domains and from gmail,
but I cannot afford to completely block any of those servers. It
kills my clients as they don't get emails from their customers and
partners.
g
On 3/22/2024 10:58 AM, William
Silverstein wrote:
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.comOn Fri, March 22, 2024 4:40 am, Gary Bowling wrote:In the spamdyke config, the default is to use spamcop for blacklisting. I've had a lot of trouble recently with spamcop. They keep adding the outlook.com servers to their database. Which means every company that uses Microsoft office 365 for mail gets blocked. This has caused me a lot of problems as there are a lot of companies in the US that use office365 for mail hosting. I am wondering if in these days we should be blacklisting server ip addresses. So many users are on shared services that blocking entire servers by ip seems like a bad idea. They also block entire ip ranges from hosting providers.Shared hosting has been around since the 1990s. That was part of the idea behind blacklisting. That by blocking IP ranges, it would encourage providers to stop spam because it would cause harm to more than just the spamming customer.
