Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

Heho, On Sat, 2023-04-08 at 17:25 -0700, Neil Anuskiewicz via mailop wrote: > > On Apr 7, 2023, at 9:26 PM, Jarland Donnell via mailop > > wrote: > > ... > > Blocking SMTP by default makes sense, but settling on the best way > > to handle opening it (automated? manual review?) is a discussion > >

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

> On Apr 7, 2023, at 9:26 PM, Jarland Donnell via mailop > wrote: > > To be clear they have an amazing abuse team, easily the first people I would > hit up if I were hiring in that area. Just top notch admins. > > Blocking SMTP by default makes sense, but settling on the best way to handle

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

Dňa 8. apríla 2023 6:20:52 UTC používateľ Hans-Martin Mosner via mailop napísal: >And that's why I'm still in favor of blocking spammer-hosting providers >swiftly and broadly. It needs to affect the non-spamming customers, too, to be >a strong economic incentive for keeping spammers out. I a

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

On 2023-04-08 01:20, Hans-Martin Mosner via mailop wrote: And that's why I'm still in favor of blocking spammer-hosting providers swiftly and broadly. It needs to affect the non-spamming customers, too, to be a strong economic incentive for keeping spammers out. Of course I also punch holes whe

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

Am 08.04.23 um 06:17 schrieb Jarland Donnell via mailop: To be clear they have an amazing abuse team, easily the first people I would hit up if I were hiring in that area. Just top notch admins. If they are top notch but have their hands tied they are essentially worthless to me. They could just

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

/googleusercontent.com, I'm so done with you I mean if the goal is to try not to appear hostile to customers, rate limiting a port is as bad or worse than blocking it. At least with blocking you know right away, but rate limiting it could create much more time in troubleshooting for an admin that misse

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

u can appreciate --srs - From: mailop on behalf of Jarland Donnell via mailop Sent: Saturday, April 8, 2023 9:47:23 AM To: mailop@mailop.org Subject: Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you To be clear they have an amazing

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

] linodeusercontent.com/googleusercontent.com, I'm so done with you To be clear they have an amazing abuse team, easily the first people I would hit up if I were hiring in that area. Just top notch admins. Blocking SMTP by default makes sense, but settling on the best way to handle openi

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

To be clear they have an amazing abuse team, easily the first people I would hit up if I were hiring in that area. Just top notch admins. Blocking SMTP by default makes sense, but settling on the best way to handle opening it (automated? manual review?) is a discussion that is very easy to get

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

> On Apr 4, 2023, at 12:42 PM, Jarland Donnell via mailop > wrote: > > I feel like I've told this story before on the list, but I can't recall. It > always feels worth telling. > > When I worked at DigitalOcean I took what felt like a year (may have been > less) and I focused more energy t

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

Am 04.04.23 um 23:02 schrieb Brandon Long via mailop: Google Cloud, which I assume is what googleusercontent.com is from this, is only unblocked for smtp for supposedly good customers... though I think they are allowed to connect to the Workspace relays (but then I

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

Google Cloud, which I assume is what googleusercontent.com is from this, is only unblocked for smtp for supposedly good customers... though I think they are allowed to connect to the Workspace relays (but then I wouldn't expect them to come from googleusercontent.com but from the regular Workspace

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

On 2023-04-04 09:14, Hans-Martin Mosner via mailop wrote: Those two cloud providers are currently providing 99% of the incoming spam at one site. googleusercontent.com sends a never-ending flood of DHL phishing mails. linodeusercontent.com sends unsolicited ad crap using a domain "klwinkel.ap

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

I feel like I've told this story before on the list, but I can't recall. It always feels worth telling. When I worked at DigitalOcean I took what felt like a year (may have been less) and I focused more energy than any one person probably ever has at any cloud provider on tackling spammers bas

Re: [mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

On Tue, 4 Apr 2023, Hans-Martin Mosner via mailop wrote: Those two cloud providers are currently providing 99% of the incoming spam at one site. googleusercontent.com sends a never-ending flood of DHL phishing mails. linodeusercontent.com sends unsolicited ad crap using a domain "klwinkel.ap

[mailop] linodeusercontent.com/googleusercontent.com, I'm so done with you

Those two cloud providers are currently providing 99% of the incoming spam at one site. googleusercontent.com sends a never-ending flood of DHL phishing mails. linodeusercontent.com sends unsolicited ad crap using a domain "klwinkel.app". Time for large scale IP range blocking, I really can't