All of the providers with whom we are familiar block TCP Port 25 Outbound by default, either entirely, or, except to approved paid relaying partner-providers. If you want to send outbound email directly, there is an application/approval process to be followed.
AWS over the past few months has become more strict in granting such approvals we have seen, and have recommended customers use AWS SES when they deny opening port 25 outbound -- which probably helps explain if only in part why we all are seeing more spam from AWS SES. Hope that helps, Mark -- _________________________________________________________________ L. Mark Stone, Founder North America's Leading Zimbra VAR/BSP/Training Partner For Companies With Mission-Critical Email Needs ----- Original Message ----- | From: "Mark E Jeftovic via mailop" <mailop@mailop.org> | To: "mailop" <mailop@mailop.org> | Sent: Friday, July 12, 2024 1:57:15 PM | Subject: [mailop] Best practices for VPS providers? | The responsible cloud hosts thread has me wondering about the state of the art | of best practices for VPS providers | | When someone provisions a VPS there’s a danger that they’ll just spin up and | blast - if they’re using stolen credit cards, etc you can mitigate and filter | on that side using fraud detection methods (Stripe radar, etc) | | But let’s say they get a VM provisioned - now what? | | We do RBL checks on our VPS IPs but it takes some time for that to show up | | What about monitoring net flows out of the IP? Are there any modules or plugins | for the hyper vizors - or management panels (Proxmox ) to monitor? | | Are there any third party services? | | Thanks | | - mark | | Sent from my iPhone | _______________________________________________ | mailop mailing list | mailop@mailop.org | https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
