be depeer them?
>
> I know this sound extreme, but.. everything else seems to fail..
>
>
> -- Original message --
>
> From: Christopher Morrow
> To: nanog@nanog.org
> Subject: Re: ARIN email address (was cogent spamming directly from ARIN
>reco
? Maybe depeer them?
I know this sound extreme, but.. everything else seems to fail..
-- Original message --
From: Christopher Morrow
To: nanog@nanog.org
Subject: Re: ARIN email address (was cogent spamming directly from ARIN
records?)
Date: Tue, 3 Oct 2023 15:48:11 -0400
i
Heh. (:
Le 4 octobre 2023 01:23:13 UTC, Owen DeLong via NANOG a écrit
:
>I was one of the main people behind their suspension from ARIN whois for 6
>months.
>
>They have not spammed me since.
>
>They’re probably afraid of another cake.
>
>Owen
>
>
>> On Oct 3, 2023, at 18:18, Mike Lyon wrote:
On Oct 3, 2023, at 11:52 AM, Bryan Fields wrote:
On 10/2/23 11:28 AM, Mel Beckman wrote:
I believe they got the contact information from ARIN
I'd suggest everyone use an alias unique to ARIN for your POC and/or public
email. Makes it super simple to verify where it was sourced from.
(and
> On Oct 3, 2023, at 11:52 AM, Bryan Fields wrote:
>
> On 10/2/23 11:28 AM, Mel Beckman wrote:
>> I believe they got the contact information from ARIN
>
> I'd suggest everyone use an alias unique to ARIN for your POC and/or public
> email. Makes it super simple to verify where it was sourced
I was one of the main people behind their suspension from ARIN whois for 6
months.
They have not spammed me since.
They’re probably afraid of another cake.
Owen
> On Oct 3, 2023, at 18:18, Mike Lyon wrote:
>
> Give it time :)
>
> -Mike
>
>> On Oct 3, 2023, at 18:06, Owen DeLong via NANOG
Give it time :)
-Mike
> On Oct 3, 2023, at 18:06, Owen DeLong via NANOG wrote:
>
> But I seem to have finally gotten Cogent trained not to spam this one, so I
> think I’ll leave it as is.
>
> YMMV
>
> Owen
>
>
>> On Oct 3, 2023, at 08:52, Bryan Fields wrote:
>>
>>> On 10/2/23 11:28 AM,
But I seem to have finally gotten Cogent trained not to spam this one, so I
think I’ll leave it as is.
YMMV
Owen
> On Oct 3, 2023, at 08:52, Bryan Fields wrote:
>
> On 10/2/23 11:28 AM, Mel Beckman wrote:
>> I believe they got the contact information from ARIN
>
> I'd suggest everyone use
* morrowc.li...@gmail.com (Christopher Morrow) [Tue 03 Oct 2023, 21:50 CEST]:
I'm sure telling dave shaeffer: "Hey, your sales droids are being
rude" is going to end as well as sending him ED pill emails.
Such outreach to technical contacts is counterproductive anyway. Which
is more likely,
On 10/3/2023 3:48 PM, Christopher Morrow wrote:
those are a bit of a false equivalence... but... ok.
I think: "Oh look, more spam, delete"
is basically how this sort of problem (email from randos trying to
sell me ED pills or 10Gs) should be treated.
I don't know that it's helpful to keep
On Tue, Oct 3, 2023 at 12:54 PM wrote:
>
> * morrowc.li...@gmail.com (Christopher Morrow) [Tue 03 Oct 2023, 18:29 CEST]:
> >this sort of thing (provider X scrapes Y and mails Z for sales leads)
> >every ~18 months.
> >the same outrage and conversation happens every time.
> >the same protection
* morrowc.li...@gmail.com (Christopher Morrow) [Tue 03 Oct 2023, 18:29 CEST]:
this sort of thing (provider X scrapes Y and mails Z for sales leads)
every ~18 months.
the same outrage and conversation happens every time.
the same protection mechanisms are noted every time.
Is there a reason
this sort of thing (provider X scrapes Y and mails Z for sales leads)
every ~18 months.
the same outrage and conversation happens every time.
the same protection mechanisms are noted every time.
Is there a reason that: "killfileand move on" is not the answer
everytime for this?
(why do we need to
13 matches
Mail list logo
