Not noreply autoresponder (WAS: really amazon?)

[Christoffer Hansen]

On 30/07/2019 13:56, Robert McKay wrote:
> Even if it existed it would just be an autoresponder telling you that
> your email wasn't read and to go resubmit the report on their website.

Both yes and now. See below:*



"""
We are sorry to hear that you received unwanted email through Amazon SES.

Please note, this reporting address is only for mail sent via Amazon SES
(emails originated from 54.240.0.0/18). If you have a complaint about
other AWS abuse (e.g. EC2), please submit your complaint here:
https://aws.amazon.com/forms/report-abuse

If you did not provide the following information, please contact
email-ab...@amazon.com again with:

1. The full headers of the objectionable email message. For examples of
how to find email headers, see
https://support.google.com/mail/answer/22454?hl=en .

2. The type of abuse you are experiencing. For example, you didn't sign
up to receive emails from the sender, the sender doesn’t have an opt-out
option, etc.

Thank you for the report!

Sincerely,

The Amazon SES Team
"""



*) The contents I got back after firing Test E-mail from $CORP email
account on O365 infrastructure.

Christoffer



signature.asc
Description: OpenPGP digital signature

Re: really amazon?

[Christoffer Hansen]

On 30/07/2019 01:03, Dan Hollis wrote:
> Jul 29 09:47:27 yuri sendmail[14067]: x6TGlQe4014062:
> to=, ctladdr=
> (500/500), delay=00:00:01, xdelay=00:00:01, mailer=esmtp92,
> relay=amazon-smtp.amazon.com. [207.171.188.4], dsn=5.1.1, stat=User unknown

... :wondering: Works fine for me. If sending from $CORP e-mail account
hosted on O365 infrastructure.

Christoffer



signature.asc
Description: OpenPGP digital signature

User Unknown (WAS: really amazon?)

[Christoffer Hansen]

On 30/07/2019 11:59, Chris Knipe wrote:
> On Tue, Jul 30, 2019 at 11:45 AM Scott Christopher wrote:
>> Dan Hollis wrote:
>>> >>> RCPT To:
>>> <<< 550 #5.1.0 Address rejected.
>>> 550 5.1.1 ... User unknown
>>> >>> DATA
>>> <<< 503 #5.5.1 RCPT first
>>
>> Try jeff () amazon
>>
> Then update your ARIN records to reflect that.  Fully agree with Dan on
> this one.
> 

Imagine ARIN did a take from RIPE NCC [Policy Proposal Idea?] and a
policy came into effect of validating ALL 'OrgAbuseEmail' objects listed
in the ARIN database. And revoked the resources from those that failed
to respond after multiple attempts.



signature.asc
Description: OpenPGP digital signature

Re: BGP Experiment

[Christoffer Hansen]

On 23/01/2019 20:01, James Jun wrote:
> Kudos to researchers by the way, for sending courtesy announcements in 
> advance, and testing 
> against some common platforms available to them (Cisco, Quagga & BIRD) prior 
> to the experiment.
On 18/12/2018 16:05, Italo Cunha wrote:
> We have successfully tested propagation of the
> announcements on Cisco IOS-based routers running versions 12.2(33)SRA
> and 15.3(1)S, Quagga 0.99.23.1 and 1.1.1, as well as BIRD 1.4.5 and
> 1.6.3.

If tests was done _only_ Quagga, BIRD, Cisco IOS... I can only conclude
a limited set has been done. (But then again, $_vendors and $_versions
of $_software cannot be counted in small numbers.)



signature.asc
Description: OpenPGP digital signature

Re: BGP Experiment

[Christoffer Hansen]

> On Wed, Jan 23, 2019 at 12:00 PM Ben Cooper  wrote:
> 
>> Can you stop this?
>>
>> You caused again a massive prefix spike/flap, and as the internet is not
>> centered around NA (shock horror!) a number of operators in Asia and
>> Australia go effected by your “expirment” and had no idea what was
>> happening or why.

You could(?) be helpful by propagating the announcement to other $lists
or point out to the authors they are not spreading their announcements
about the experiment wide enough.

>> Get a sandbox like every other researcher, as of now we have black holed
>> and filtered your whole ASN, and have reccomended others do the same.
Probably the previous sent announcement about the prefix announcements
sent out today. Should have gone to more mailing lists at RIRs and NOGs.
(Encountered a FRR user today, too. Who had missed previous announcements)

-Christoffer




signature.asc
Description: OpenPGP digital signature

Re: BGP Experiment

[Christoffer Hansen]

On 23/01/2019 18:19, Italo Cunha wrote:
> We have canceled this experiment permanently.

Sad to hear! :/

My impression if you continue is more users will get aware of bugs with
running BGP implementations. Not all follow announcement from $vendor
and will continue to run older broken code and complain to $vendor about
errors with the software.

Re: Network Speed Testing and Monitoring Platform

[Christoffer Hansen]

On 16/01/2019 17:52, Colton Conor wrote:
> We are looking for a way to remotely test customers internet connections
> besides telling the customer to go to speedtest.net, or worse sending a
> tech out with a laptop to do the same thing.
> 
> What opensource and commercial options are out there?

You could optionally run tools such as iperf[123] on the CPE device
directly. If you can install it on the CPE, that is.

Alternative is the classic of doing a L2 loop with dedicated VLANs on
the CPE. E.g. Server1 -> VlanX -> CPE -> VlanY -> Server2 in your own
network.

-Christoffer

Re: Announcing Peering-LAN prefixes to customers

[Christoffer Hansen]

On 16/01/2019 15:55, John Kristoff wrote:
> In Randy's presentation there is the suggestion to develop an IX filter
> list.  Nearly 20 years later that actually happened.
> 
>   
> 
> This wasn't a popular service when I left Team Cymru, but it seems to
> still be available if anyone wants to consider using that.

You could do the same trick. But with data fetched from PeeringDB via
the public API. Works well.

-Christoffer

Re: Announcing Peering-LAN prefixes to customers

[Christoffer Hansen]

On 16/01/2019 08:56, Mark Tinka wrote:
> Running a few exchange points in Africa since 2002, the news was that
> the exchange point LAN should not be visible anywhere on the Internet.

Do you use AS0 as origin on the RPKI objects for said exchange point
LAN(s) to prevent route propagation?

-Christoffer



signature.asc
Description: OpenPGP digital signature

Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting

[Christoffer Hansen]

On 13/01/2019 21:11, valdis.kletni...@vt.edu wrote:
> Back when we were designing MIME,  somebody (Vernon Schryver?) stated
> that multipart/alternative with text/plain and text/html was *always* 
> incorrect.

-_-

> If the two parts are semantically equal, then one is superfluous and doesn't
> need to be sent. (Remember bandwidth costs in 1992...)

I can imagine.

> If the two parts aren't semantically equal, then one part is deficient at best
> and actively misleading at worst, and should not be sent.

In 2019 I would hope this are not the case. Cause Cheap Bandwidth
compared to the 90'ies.

Still not always the case. Sadly. :/

-Christoffer



signature.asc
Description: OpenPGP digital signature

Re: plaintext email?

[Christoffer Hansen]

On 13/01/2019 20:57, Brian Kantor wrote:
> Are you trying to start another flame war?

I certainly hope to avoid this discussion currently!

(back to 1) @NETFLIX: Anybody willing to listen to previous stated
comment and take action on it?

- Christoffer



signature.asc
Description: OpenPGP digital signature

Re: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting

[Christoffer Hansen]

On 13/01/2019 20:50, Mike Hammett wrote:
> People use plain-text e-mail on purpose? 
I do most of the time.

(*it is frustrating when content parity between HTML and PLAINTEXT
sections is e-mails is inconsistent. :/ )

-- 
Christoffer

Fwd: (Netflix/GlobalConnect a/s) Scheduled Open Connect Appliance upgrade is starting

[Christoffer Hansen]

Sent to NANOG,

Anyone from NETFLIX subscribed?


Could you please fix the below type notification e-mails to ALSO be
available if one ONLY USES PLAIN-TEXT email clients?

Currently the notice information is formatted in such a way the
PLAIN-TEXT section is completely EMPTY.
ONLY the HTML section contains information.

(E-mail client on my case is Thunderbird)

-- 
Cheers

Christoffer

 Forwarded Message 
Subject:(Netflix/***) Scheduled Open Connect Appliance
upgrade is starting
Resent-From:***
Date:   *** Jan 2019 ***
From:   Netflix 
Reply-To:   no_re...@netflix.com
To: ***



Netflix


Hello ***,

The scheduled upgrade of your Open Connect Appliance(s) (OCAs) is
beginning now. The list of affected appliances is:

IP Address  NameFacility
*** *** ***