From: Vint Cerf <vint@google.com>
To: Bill Woodcock <woody@pch.net>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
"Christopher Hawker" <chris@thesysadmin.au>
Subject: Re: [NNagain] Verified Email
Date: Wed, 13 Mar 2024 07:27:07 -0400 [thread overview]
Message-ID: <CAHxHggd-vXd=Ry7Pk9oCxpoKK9CGqnAT63zhdQr=UeGb8EBspw@mail.gmail.com> (raw)
In-Reply-To: <4e327231-311f-4cdc-b827-00f3e0ada999@Canary>
[-- Attachment #1.1: Type: text/plain, Size: 2589 bytes --]
yes, I should have been more precise - that's what I had in mind, too.
v
On Wed, Mar 13, 2024 at 6:28 AM Bill Woodcock <woody@pch.net> wrote:
> Rather than a hack, per se, I suspect that it’s a dot-com abusing Steve’s
> trust and his contacts, spamming all of them.
>
> -Bill
>
>
> On Wednesday, Mar 13, 2024 at 11:22, Vint Cerf via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
> i wondered whether this was a hack. Not like Steve to do this.
> v
>
>
> On Wed, Mar 13, 2024 at 6:20 AM Christopher Hawker via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
>
>> With all due respect, I didn't think this was a mailing list to advertise
>> paid services.
>>
>> Dave?
>>
>> Regards,
>> Christopher Hawker
>> ------------------------------
>> *From:* Nnagain <nnagain-bounces@lists.bufferbloat.net> on behalf of
>> Steve Crocker via Nnagain <nnagain@lists.bufferbloat.net>
>> *Sent:* Wednesday, March 13, 2024 9:18 PM
>> *To:* nnagain@lists.bufferbloat.net <nnagain@lists.bufferbloat.net>
>> *Cc:* Steve Crocker <steve@shinkuro.com>
>> *Subject:* [NNagain] Verified Email
>>
>> Hi Network,
>>
>> I’ve been using a new tool called Verified Email
>> <https://verified.inc/verified-email?email=nnagain%40lists.bufferbloat.net&verificationCode=756653&referralCode=tcp16fM4W47y>.
>> It runs in my inbox and shows me who’s a real person — saves time and
>> reduces spam.
>>
>> Thought you might find it useful. Here’s my invite link
>> <https://wallet.verified.inc/authentication?email=nnagain%40lists.bufferbloat.net&verificationCode=756653&referralCode=tcp16fM4W47y>
>> if you want to try it.
>>
>> Steve
>>
>> Sent by a Verified
>> [image: Sent by a Verified sender]
>> <https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y>
>> sender
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>>
>
>
> --
> Please send any postal/overnight deliveries to:
> Vint Cerf
> Google, LLC
> 1900 Reston Metro Plaza, 16th Floor
> Reston, VA 20190
> +1 (571) 213 1346 <(571)%20213-1346>
>
>
> until further notice
>
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>
>
--
Please send any postal/overnight deliveries to:
Vint Cerf
Google, LLC
1900 Reston Metro Plaza, 16th Floor
Reston, VA 20190
+1 (571) 213 1346
until further notice
[-- Attachment #1.2: Type: text/html, Size: 6643 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4006 bytes --]
next prev parent reply other threads:[~2024-03-13 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 10:18 Steve Crocker
2024-03-13 10:20 ` Christopher Hawker
2024-03-13 10:22 ` Vint Cerf
2024-03-13 10:25 ` Bill Woodcock
2024-03-13 11:27 ` Vint Cerf [this message]
2024-03-13 11:47 ` Olivier MJ Crépin-Leblond
2024-03-13 12:21 ` Steve Crocker
2024-03-13 12:42 ` Steve Crocker
2024-03-13 17:58 ` [NNagain] Scope of "Network Neutrality"? Jack Haverty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHxHggd-vXd=Ry7Pk9oCxpoKK9CGqnAT63zhdQr=UeGb8EBspw@mail.gmail.com' \
--to=vint@google.com \
--cc=chris@thesysadmin.au \
--cc=nnagain@lists.bufferbloat.net \
--cc=woody@pch.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox