Re: Friday Thanks

Sorry, NTT, I didn't mean to leave you out, you were great too - Thanks. From: NANOG on behalf of Graham Johnston via NANOG Sent: Friday, August 11, 2023 10:53 AM To: nanog@nanog.org Subject: Friday Thanks I've been busy over the last few days

Re: Friday Thanks

really hurting > me, but I feel like there shouldn't be competing incorrect information out > there that I'm not in control of. The database maintainers have been mixed > in their response so far. This email isn't about name and shame though, I'm > not at that point. Ins

Friday Thanks

information out there that I'm not in control of. The database maintainers have been mixed in their response so far. This email isn't about name and shame though, I'm not at that point. Instead, I want to provide thanks to two organizations that have been very responsive and easy t

WATCH NOW: N87 Recap, Talks are LIVE, + Special Thanks

com/watch?v=fejIBHzKU14> *NANOG 87 Talks are LIVE!* *Have you Subscribed to our YouTube Channel?* Check out the "NANOG 87 Playlist" and find all your favorite talks from NANOG 87. *WATCH * <https://www.youtube.com/watch?v=GKRDgIQzlGc&list=PLO8DR5ZGla8hFbB2qGVHFRSmJO83G9ReF> *

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On 10/28/19 1:43 PM, Alain Hebert wrote:     Hi,     This is not an assumption, it is my experience. Mine as well. My mail server's PTR records are identical for IPv4 and IPv6. IPv6 fails and IPv4 is fine. I disabled IPv6 for gmail.com.     Sorry it didn't fit your case. - Alain

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

    Hi,     This is not an assumption, it is my experience.     Sorry it didn't fit your case. - Alain Hebertaheb...@pubnix.net PubNIX Inc. 50 boul. St-Charles P.O. Box 26770 Beaconsfield, Quebec H9W 6G7 Tel: 514-990-5911 http://www.pubnix.netFax

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Friday 2019-10-25 01:22, Rich Kulawiec wrote: On Thu, Oct 24, 2019 at 01:21:12PM -0700, Mark Milhollan wrote: My experience says that: their system has learned that your system(s) continued to send messages that their user (yes you, but they don't know that) did not want [and nothing influ

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Fri, Oct 25, 2019 at 07:52:17AM -0700, Damian Menscher via NANOG wrote: > > There is a persistent mythos -- a worst practice, actually -- among many > > operations that obfuscating the reasons why messages are rejected is > > useful. > > This is wrong. > > > > Consider: either the sender is beni

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Thu, Oct 24, 2019 at 5:34 AM Rich Kulawiec wrote: > On Wed, Oct 23, 2019 at 06:18:46PM -0600, Constantine A. Murenin wrote: > > it is revealed that Postmaster Tools cannot tell me anything at all, with > > all tabs and screens being 100% blank, allegedly because I'm not > actually a > > mass e

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

[ Again, just commenting on one point. ] On Thu, Oct 24, 2019 at 01:21:12PM -0700, Mark Milhollan wrote: > My experience says that: their system has learned that your system(s) > continued to send messages that their user (yes you, but they don't know > that) did not want, i.e., you left it marked

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Thu, 24 Oct 2019 at 11:41, Joe Klein wrote: […] I suspect that by changing your 5321.MailFrom, you changed the signal > calculus, for now. I bet in a bit, provided that you don’t change any other > behaviors, that these emails will eventually be rejected too. > Of course. This is just a tel

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

You're assuming that IPv6 is at fault, but as I've already mentioned, if I change the From and MAIL FROM to one of the other domains with a DNS zone similar to the primary one with crontab-acquired "very low reputation", without changing anything else, then the identical messages do get through at

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Wednesday 2019-10-23 17:18, Constantine A. Murenin wrote: I use my own personal domain name for various UNIX stuff, including sending log-related things to myself out of cron, which end up in my own Gmail.com account, either directly, or through forwarding (w/o SRS). (I do not use G Suite fo

RE: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

ober 23, 2019 7:19 PM To: North American Network Operators' Group Cc: Constantine A. Murenin Subject: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite. External Mail Dear NANOG@, I'm not sure where else to post this, and this is not really new, eith

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Wed, Oct 23, 2019, at 7:18 PM, Constantine A. Murenin wrote: > A couple of months ago, I setup some new scripts that would send me new > nightly emails. It's all plain text, but had a few dozen of domain > names present (it's logs). Absolutely no links, just plenty of domains > which I don't

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Wed, Oct 23, 2019 at 06:18:46PM -0600, Constantine A. Murenin wrote: > Dear NANOG@, > [...] > > Over the years, I sometimes had certain messages rejected by Gmail, but it > was a very low rate of rejection (less than 5% for any mail I cared about), > and wasn't a major problem (usually only so

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

zip up the log before you send it. -Joe -- Joe Hamelin, W7COM, Tulalip, WA, +1 (360) 474-7474 On Wed, Oct 23, 2019 at 5:20 PM Constantine A. Murenin wrote: > Dear NANOG@, > > I'm not sure where else to post this, and this is not really new, either, > but I think I have a new take here. > > I us

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

    "Trust Andrew(tm) when I say this." Disable your IPv6 access to their mail server.     At Google, something hasn't worked, well since the beginning of time, when it come to propagating your domain reputation to handling incoming emails using IPv6.     I just had the case last week when

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

[ I'm just going to focus on one point. ] On Wed, Oct 23, 2019 at 06:18:46PM -0600, Constantine A. Murenin wrote: > it is revealed that Postmaster Tools cannot tell me anything at all, with > all tabs and screens being 100% blank, allegedly because I'm not actually a > mass email sender (I don't s

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On 10/23/19 8:18 PM, Constantine A. Murenin wrote: A long message about how sending arbitrary operational text data to gmail can cause unsuspected problems This is a perfect example of why service providers, IT consulting outfits, etc. really need to either run their own mail infrastructure o

RE: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

On Wednesday, 23 October, 2019 18:36, Brandon Applegate wrote: >Bigger picture, I think that (unfortunately) we will see more and more >problems like this. With the large providers running so much (as you >mentioned - “monoculture”), and their services tending toward the “black >box” ... I do

Re: Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

> On Oct 23, 2019, at 8:18 PM, Constantine A. Murenin > wrote: > I’d recommend posting this over on the mailop list as well. Lots of discussions about issues like this there. I too send myself various cron/*nix emails. The difference is I send to my own domain on my own server so I don’t s

Unable to email anyone from my primary domain name; thanks Google Mail and G Suite.

Dear NANOG@, I'm not sure where else to post this, and this is not really new, either, but I think I have a new take here. I use my own personal domain name for various UNIX stuff, including sending log-related things to myself out of cron, which end up in my own Gmail.com account, either directl

Re: Thanks aws / gcc / azure

As someone rightly pointed out "ARIN now down to 0.00978 /8s in aggregate." > or this > > https://www.youtube.com/watch?v=_y36fG2Oba0 so this is more appropriate "I suppose we'd better give it a try"

Re: Thanks aws / gcc / azure

> On Jun 26, 2015, at 9:24 AM, Lee Howard wrote: > > On 6/23/15, 9:01 AM, "NANOG on behalf of Ca By" on behalf of cb.li...@gmail.com> wrote: > >> Since you have failed to achieve in the modest task that was your charge >> >> You now get this >> >> https://www.markshuttleworth.com/archives/14

Re: Thanks aws / gcc / azure

On 6/23/15, 9:01 AM, "NANOG on behalf of Ca By" wrote: >Since you have failed to achieve in the modest task that was your charge > >You now get this > >https://www.markshuttleworth.com/archives/1471 Time to watch this again: https://www.youtube.com/watch?v=v26BAlfWBm8 Lee > >Or s/money/addre

Re: Thanks aws / gcc / azure

> On Jun 23, 2015, at 9:01 AM, Ca By wrote: > > Since you have failed to achieve in the modest task that was your charge > > You now get this > > https://www.markshuttleworth.com/archives/1471 > > Or s/money/addresses/ > > http://youtu.be/pA8f-Nh5gRs Cameron, I share your disappointment th

Thanks aws / gcc / azure

Since you have failed to achieve in the modest task that was your charge You now get this https://www.markshuttleworth.com/archives/1471 Or s/money/addresses/ http://youtu.be/pA8f-Nh5gRs

It worked! Huge Thanks Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?

7;s Collaborative Edge Blog http://www.cookreport.com/wp/ Subscription info: http://www.cookreport.com/index.php?option=com_content&view=article&id=54&Itemid=65 = On Oct 4, 2013, at 3:50 PM, "Moore, Matthew

RE: Cross country point to point link question :: THANKS

Thanks everyone, I've gotten a lot of pointers off-list, and I have a good idea of our next few steps of verification. -Petter -Original Message- From: Petter Bruland [mailto:petter.brul...@allegiantair.com] Sent: Thursday, April 18, 2013 9:20 AM To: nanog@nanog.org Subject:

Re: Thanks & Let's Prevent this in the Future.

On Thursday, February 02, 2012 01:00:43 AM George Bonser wrote: > One problem is the number of routing registries and the > requirements differ for them. The nefarious operator > can enter routes in an IRR just as easily as a > legitimate operator. There was a time when some > significant netwo

RE: Thanks & Let's Prevent this in the Future.

Thanks for the reminder, Richard. Yes, as I announced earlier (see http://mailman.nanog.org/pipermail/nanog/2012-January/044493.html - the message with the corrected date), there is an interim sidr meeting on Thu *9* Feb in San Diego. Registration is free. Registration is easy (email

Re: Thanks & Let's Prevent this in the Future.

In related news, the IETF working group that is writing standards for the RPKI is having an interim meeting in San Diego just after NANOG. They deliberately chose that place/time to make it easy for NANOG attendees to contribute, so comments from this community are definitely welcome.

Re: Thanks & Let's Prevent this in the Future.

One option is to use RPKI and origin validation. But it won't help much unless prefix holders create their certificates and ROAs and networks operators use those to validate origins. It won't solve all the issues but at least some fat fingers/un-expierience errors. We are runni

RE: Thanks & Let's Prevent this in the Future.

On Wed, 1 Feb 2012, George Bonser wrote: One problem is the number of routing registries and the requirements differ for them. The nefarious operator can enter routes in an IRR just as easily as a legitimate operator. There was a time when some significant networks used the IRRs for their fi

RE: Thanks & Let's Prevent this in the Future.

> I'd like to get a conversation going and possibly some support of an > initiative to spend that extra 30-seconds to verify ownership and > authorization of network space to be advertised. Additionally, if > someone rings your NOC's line an industry-standard process of verifying > "ownership" > a

Re: Thanks & Let's Prevent this in the Future.

At 03:58 01/02/2012 -0500, Kelvin Williams wrote: Those ISPs that are good network citizens have done it already. Those who don't care and who haven't done it yet - won't do it in the future. The only recourse you have is exactly what you have done. -Hank How can we prevent anyone else fr

Re: Thanks & Let's Prevent this in the Future.

On 1 Feb 2012, at 09:01, "Kelvin Williams" wrote: > > A few months ago, when establishing a new peering relationship I was > encouraged (actually required) to utilize one of the IRRs. I took the time > to register all of my routes, ASNs, etc. However, as I learned today, this > was probably d

Thanks & Let's Prevent this in the Future.

First off, I'd like to thank everyone on this list who have reached out today and offered us help with our hijacked network space. It's so refreshing to see that there are still so many who refuse to leave a man/woman down. I'm not going to place any blame, its useless. There were lies, there we

RE: ping me please... Think I've got enough data, thanks

few reports from one customer that some of his > users are unable to reach his system. If I could get people > on the list to ping 65.5.48.2, and if it fails, to do a > traceroute and email it to me offlist? I'd appreciate it. > Thanks. I think I've got enough data. If there'

Thanks for the Info! (was: Anyone have PDF Manual for Nortel/BayStack 425-24T Switch)

Thanks for the reply's. A User Guide was forwarded which should enable access to this switch. On Tue, 01 Feb 2011 11:33:40 -0500, "kmedc...@dessus.com" wrote: Does anyone happen to have PDF Manuals (not the sales literature, but the switch software command references)

Thanks guys!

Followup and Thanks: AT&T Dry Pairs?

I just wanted to follow up and say Thank You to everyone who responded to my email regarding getting an "alarm line" from AT&T. I've made some headway once I reached someone with clue, and everyone was extremely helpful with the information they provided. -- Brandon Galbraith US Voice: 630.492.04

Re: Hey ISC, thanks for providing free wifi to intercage!

On Sat, 4 Oct 2008, Suresh Ramasubramanian wrote: On Sat, Oct 4, 2008 at 6:19 AM, Gadi Evron <[EMAIL PROTECTED]> wrote: On Sat, 4 Oct 2008, Noel Butler wrote: I'll post what I want, when I want and however I want, and no self appointed net nazi is going to tell me otherwise. Ah! You mentione

Re: Hey ISC, thanks for providing free wifi to intercage!

On Sat, Oct 4, 2008 at 6:19 AM, Gadi Evron <[EMAIL PROTECTED]> wrote: > On Sat, 4 Oct 2008, Noel Butler wrote: >> >> I'll post what I want, when I want and however I want, and no self >> appointed net nazi is going to tell me otherwise. > > Ah! You mentioned the Nazis. Now we know the thread is ove

Re: Hey ISC, thanks for providing free wifi to intercage!

On Sat, 4 Oct 2008, Noel Butler wrote: I'll post what I want, when I want and however I want, and no self appointed net nazi is going to tell me otherwise. Ah! You mentioned the Nazis. Now we know the thread is over. :) We should mention Nazis more often to end threads here. Godwin's law to t

Re: Hey ISC, thanks for providing free wifi to intercage!

I'll post what I want, when I want and however I want, and no self appointed net nazi is going to tell me otherwise. have a nice weekend, I know I will. On Thu, 2008-10-02 at 22:47, Laurence F. Sheldon, Jr. wrote: > Noel Butler wrote: > [nothing worth having been forwarded several times] > > I

Re: Hey ISC, thanks for providing free wifi to intercage!

On Thu, Oct 2, 2008 at 10:40, <[EMAIL PROTECTED]> wrote: >> > How about moving the meta-nanog themes in this thread to >> > nanog-futures, instead of adding to the noise on the main list? >> >> Because nobody reads it? > > Try "because nobody knows that NANOG has a website where you can > simple i

RE: Hey ISC, thanks for providing free wifi to intercage!

> > How about moving the meta-nanog themes in this thread to > > nanog-futures, instead of adding to the noise on the main list? > > Because nobody reads it? Try "because nobody knows that NANOG has a website where you can simple instructions to subscribe to Nanog-futures". For the record, ther

Re: Hey ISC, thanks for providing free wifi to intercage!

Laurence F. Sheldon, Jr. wrote: Joe Abley wrote: How about moving the meta-nanog themes in this thread to nanog-futures, instead of adding to the noise on the main list? Because nobody reads it? You are mistaken, sir. There are plenty that read it, and meta discussions belong there. --

Reading NANOG-Futures [was: Hey ISC, thanks for providing free wifi to intercage!]

On Oct 2, 2008, at 9:33 AM, Laurence F. Sheldon, Jr. wrote: Joe Abley wrote: How about moving the meta-nanog themes in this thread to nanog- futures, instead of adding to the noise on the main list? Because nobody reads it? I've been called a lot of things, but I can't seem to remember bein

Re: Hey ISC, thanks for providing free wifi to intercage!

Joe Abley wrote: How about moving the meta-nanog themes in this thread to nanog-futures, instead of adding to the noise on the main list? Because nobody reads it?

Re: Hey ISC, thanks for providing free wifi to intercage!

On 2 Oct 2008, at 08:47, Laurence F. Sheldon, Jr. wrote: I'm sure I'll get a nastygram from the kabal for this, but just out of curiosity, why is talking about broken network protocols and other stuff "off topic", but talking mindlessly and endlessly about mindless and pointless drivel (qu

Re: Hey ISC, thanks for providing free wifi to intercage!

Noel Butler wrote: [nothing worth having been forwarded several times] I'm sure I'll get a nastygram from the kabal for this, but just out of curiosity, why is talking about broken network protocols and other stuff "off topic", but talking mindlessly and endlessly about mindless and pointless

Re: Hey ISC, thanks for providing free wifi to intercage!

On 2008/10/02 05:25 AM Noel Butler wrote: They wouldn't have the guts to post under their real name, remember, IRC is for the gutless keyboard commandos... What a stupid generalisation

Re: Hey ISC, thanks for providing free wifi to intercage!

could we all let this thread skate off into memory-land now? It's not productive nor operationally focused. thanks, citizen-chris On Thu, Oct 2, 2008 at 12:05 AM, William Pitcock <[EMAIL PROTECTED]> wrote: > Hi,

Re: Hey ISC, thanks for providing free wifi to intercage!

Hi, On Thu, 2008-10-02 at 09:06 +0530, Suresh Ramasubramanian wrote: > On Thu, Oct 2, 2008 at 8:55 AM, Noel Butler <[EMAIL PROTECTED]> wrote: > > They wouldn't have the guts to post under their real name, remember, IRC > > is for the gutless keyboard commandos...and for posting IRC logs on > > mai

Re: Hey ISC, thanks for providing free wifi to intercage!

On Thu, Oct 2, 2008 at 8:55 AM, Noel Butler <[EMAIL PROTECTED]> wrote: > They wouldn't have the guts to post under their real name, remember, IRC > is for the gutless keyboard commandos...and for posting IRC logs on > mailing lists, is it school holidays over there or something, must be. Well .. o

Re: Hey ISC, thanks for providing free wifi to intercage!

see, *this* is why google needs to WAKE UP and start putting real headers in their gmail spew. _H*

Re: Hey ISC, thanks for providing free wifi to intercage!

a cage on the other side of the > > wall from one of my cages (I'm at my desk) > > lol > > nenolod: So I'm using their wireless since my wireless is dead > > lol > > thanks esthost > > * RussM has quit (Quit: Leaving) > >

Re: Hey ISC, thanks for providing free wifi to intercage!

esk) > lol > nenolod: So I'm using their wireless since my wireless is dead > lol > thanks esthost > * RussM has quit (Quit: Leaving)

Re: Hey ISC, thanks for providing free wifi to intercage!

27;ve never seen him here knock him out again for DHCPD LOL ISC: making my life hell daily nenolod: ISC has a few racks and a cage on the other side of the wall from one of my cages (I'm at my desk) lol nenolod: So I'm using their wireless since my wireless is dead lol thanks esthost *

Hey ISC, thanks for providing free wifi to intercage!

7;m using their wireless since my wireless is dead lol thanks esthost * RussM has quit (Quit: Leaving)

[ot] Re: Thanks

network engineers at Comcast, and they're now > working on a resolution. Thanks for the fast work guys! > > Andrew > > -- Would you like a little bit of legal advice? NEVER let a scientist use the words "unanticipated" and "immediate" in the same sentence. Okay? Okay.

Thanks

I got a reply from several network engineers at Comcast, and they're now working on a resolution. Thanks for the fast work guys! Andrew