Re: OIX (formerly Open-IX) Document Development Mailing List (Invitation to Join)

Hey all - friendly nudge to join the OIX-DDP mailing list if you are at all interested in interconnection - it will be very low volume and the more eyes we have on the process the better. Details below... Thanks to those of you who have already joined! ~Chris On Wed, Aug 21, 2024 at 5:35 PM

OIX (formerly Open-IX) Document Development Mailing List (Invitation to Join)

Hello NANOG, This message is being sent in my capacity as the Chair of the Board of OIX. We (OIX) have some proposed updates to standards documents that affect this community. As such, we would like to invite anyone and everyone interested to subscribe to the OIX DDP mailing list. The sole

Re: Mailing list SPF Failure

On Fri, 2024-05-17 at 08:13 +0300, Hank Nussbacher wrote: > On 17/05/2024 5:45, Karl Auer wrote: > > https://support.google.com/a/answer/81126 > > I think some may have missed these announcements: > > https://labs.ripe.net/author/fergalc/enhancing-email-delivery-at-the-ripe-ncc/ > > https://blog

Re: Mailing list SPF Failure

On 17/05/2024 5:45, Karl Auer wrote: On Thu, 2024-05-16 at 19:27 -0700, Michael Thomas wrote: On 5/16/24 7:22 PM, Scott Q. wrote: Mike, you do realize Google/Gmail rejects e-mails with invalid/missing SPF right ? I was receiving the mail while NANOG had no SPF record, so no? Any receiver would

Re: Mailing list SPF Failure

uot;Scott Q." Using Group-Office To: Michael Thomas , nanog@nanog.org Subject: Re: Mailing list SPF Failure SPF: NONE with IP 50.31.151.76 Learn more Message ID <74b33cf0-b7c4-46ac-8154-1cfca082e...@mtcc.com> Created at: Thu, May 16, 2024 at 2:13 PM (Delivered after 85 seconds) From: Mich

Re: Mailing list SPF Failure

On Thu, 2024-05-16 at 19:27 -0700, Michael Thomas wrote: > On 5/16/24 7:22 PM, Scott Q. wrote: > > Mike, you do realize Google/Gmail rejects e-mails with > > invalid/missing SPF right ? > > I was receiving the mail while NANOG had no SPF record, so no? Any > receiver would be really stupid take a

Re: Mailing list SPF Failure

On 5/16/24 7:36 PM, John R. Levine wrote: I think a lot of us have nanog whitelisted or otherwise special cased. I don't and gmail is my backend. That's trivial falsification that lack of an SPF records alone will cause gmail rejects. Mike Also, it's been pumping out list mail for decad

Re: Mailing list SPF Failure

> > I'm surprised nobody noticed for close to 10 days. Probably because it wasn't 10 days. On Thu, May 16, 2024 at 10:26 PM Scott Q. wrote: > I'm surprised nobody noticed for close to 10 days. I was away from work > and upon coming back I saw the little discussion there was , in my Spam > fold

Re: Mailing list SPF Failure

I think a lot of us have nanog whitelisted or otherwise special cased. Also, it's been pumping out list mail for decades and I expect has a close to zero complaint rate so even without the SPF ths IPs it sends from have a good reputation. On Thu, 16 May 2024, Scott Q. wrote: I'm surprised n

Re: Mailing list SPF Failure

omas mailto:m...@mtcc.com>> said: >>> Since probably 99% of the mail from NANOG is through this list, it >>> hardly matters since SPF will always fail. >> Sorry, but no. A mailing list puts its own envelope return address on >> the message so w

Re: Mailing list SPF Failure

I'm surprised nobody noticed for close to 10 days. I was away from work and upon coming back I saw the little discussion there was , in my Spam folder. On Thursday, 16/05/2024 at 18:56 John R. Levine wrote: On Thu, 16 May 2024, William Herrin wrote: > The message content (including the message

Re: Mailing list SPF Failure

On 5/16/24 3:54 PM, William Herrin wrote: On Thu, May 16, 2024 at 12:03 PM John Levine wrote: It appears that Michael Thomas said: Since probably 99% of the mail from NANOG is through this list, it hardly matters since SPF will always fail. Sorry, but no. A mailing list puts its own

Re: Mailing list SPF Failure

On Thu, 16 May 2024, William Herrin wrote: The message content (including the message headers) is theoretically not used for SPF validation. In practice, some SPF validators don't have direct access to the SMTP session so they rely on the SMTP session placing the envelope sender in the Return-pat

Re: Mailing list SPF Failure

On Thu, May 16, 2024 at 12:03 PM John Levine wrote: > It appears that Michael Thomas said: > >Since probably 99% of the mail from NANOG is through this list, it > >hardly matters since SPF will always fail. > > Sorry, but no. A mailing list puts its own envelope return add

Re: Mailing list SPF Failure

;hardly matters since SPF will always fail. Sorry, but no. A mailing list puts its own envelope return address on the message so with a reasonable SPF record, SPF will normally succeed. (If the mail is subsequently forwarded SPF will fail, but that's not unique to mailing lists.) DKIM and DMARC

Re: Mailing list SPF Failure

On 5/16/24 8:59 AM, Scott Q. wrote: Uhm, not really. An SPF failure is really bad even though DKIM works. It might depend what they do with DMARC but even so, there's no reason they can't just add that IP to their SPF record. SPF has from day one been known to be broken with mailing lists. It

Re: Mailing list SPF Failure

Uhm, not really. An SPF failure is really bad even though DKIM works. It might depend what they do with DMARC but even so, there's no reason they can't just add that IP to their SPF record. >From what I see, it's been broken at least since May 6-7. On Thursday, 16/05/2024 at 11:37 Michael Thomas

Re: Mailing list SPF Failure

On 5/16/24 8:11 AM, Peter Potvin via NANOG wrote: Appears there’s no SPF record at all now for nanog.org , which is not ideal… Since probably 99% of the mail from NANOG is through this list, it hardly matters since SPF will always fail. What is more important is that they r

Re: Mailing list SPF Failure

Appears there’s no SPF record at all now for nanog.org, which is not ideal… Kind regards, Peter Potvin On Thu, May 16, 2024 at 02:59 Bjørn Mork wrote: > "Scott Q." writes: > > > Anyone else getting SPF failures on all messages sent to the list > > ? > > > > I see them all originating from 50.

Re: Mailing list SPF Failure

"Scott Q." writes: > Anyone else getting SPF failures on all messages sent to the list > ? > > I see them all originating from 50.31.151.76 but nanog.org's SPF > record doesn't list that as allowed. I see the same. nanog.org mail is originated from 2001:1838:2001:8:0:0:0:20 or 50.31.151.76, and

Re: Mailing list SPF Failure

Let us see… -mel beckman > On May 15, 2024, at 7:47 PM, Scott Q. wrote: > >  Anyone else getting SPF failures on all messages sent to the list ? > > I see them all originating from 50.31.151.76 but nanog.org's SPF record > doesn't list that as allowed. >

Mailing list SPF Failure

Anyone else getting SPF failures on all messages sent to the list ? I see them all originating from 50.31.151.76 but nanog.org's SPF record doesn't list that as allowed.

new net neutrality/title ii mailing list

Since network neutrality and title ii regulation is back in the news, and the issues so fraught with technical and political mis-conceptions, I have started a new mailing list to discuss it, and try (for once) to feed back valid techical feedback into the FCC´s normal processes. I kind of expect

Re: Issues with NANOG mailing list operations and subscriptions

Hi Sean, Will, group, On Sun, Jan 17, 2021 at 03:01:22PM -0800, William Herrin wrote: > On Sun, Jan 17, 2021 at 1:37 PM Sean Donelan wrote: > > Some people think its funny to ghost subscribe email addresses, and > > the NANOG mailing list auomation doesn't catch them

Re: Issues with NANOG mailing list operations and subscriptions

On Sun, Jan 17, 2021 at 1:37 PM Sean Donelan wrote: > Some people think its funny to ghost subscribe email addresses, and > the NANOG mailing list auomation doesn't catch them in the verification > process. Hi Sean, How is that possible? This is exactly what a correctly impleme

Issues with NANOG mailing list operations and subscriptions

Some people think its funny to ghost subscribe email addresses, and the NANOG mailing list auomation doesn't catch them in the verification process. Most of the time, if you send a note to the mailing list admins, they will quickly unsubscribe the address. Although sometimes the pr

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On 1/11/2019 2:50 PM, Grant Taylor via NANOG wrote: On 01/11/2019 12:32 PM, Rob McEwen wrote: but if done right, fwiw,, wouldn't that be sent over SMTP using TLS encryption? Oy vey.  in-flight vs at-rest encryption.  which is why i said "fwiw", acknowledging upfront that TLS transmission e

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

Whaddya expect guys, the mailing list is hosted on an embedded DVR recorder On Fri, Jan 11, 2019 at 12:52 PM Töma Gavrichenkov wrote: > 11 Jan. 2019 г., 23:19 Mark Andrews : > >> So STARTTLS strip is not a problem anymore? > >> > > If you deploy DANE (client and serve

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

fails TLSA lookup, then fair enough. I don't think this is (and is going to be in the near future) the case for the dumpsterfire mailing list, but you may rightfully assume I haven't checked yet. > gmail.com hasn’t (server side at least). Google folks are on this mailing list, so

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

> On 12 Jan 2019, at 6:36 am, Töma Gavrichenkov wrote: > > 11 Jan. 2019 г., 22:33 Rob McEwen : > > but if done right, fwiw,, wouldn't that > > be sent over SMTP using TLS encryption > > So STARTTLS strip is not a problem anymore? If you deploy DANE (client and server sides) then stripping ST

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

ent.com (206.210.75.234) 42 msec 42 msec 51 msec > 16 xe-0-3-0.1sc-node.expedient.com (216.230.108.246) 50 msec 42 msec 59 msec > 17 ten1-6-2.tdp-core.expedient.com (216.230.108.229) 42 msec 42 msec 50 msec > 18 firemountain.net (207.114.3.55) 50 msec 42 msec 51 msec > > > HTH >

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On 1/11/19 12:11 PM, Andreas Ott wrote: On Fri, Jan 11, 2019 at 12:17:09PM -0500, Rich Kulawiec wrote: On Fri, Jan 11, 2019 at 08:23:31AM -0800, Yang Yu wrote: * no HTTPS HTTPS isn't needed for this application. I'll probably add it anyway when I have a chance, but there are other thin

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On 01/11/2019 12:32 PM, Rob McEwen wrote: but if done right, fwiw,, wouldn't that be sent over SMTP using TLS encryption? Oy vey. in-flight vs at-rest encryption. (but, then again, that ALSO requires a certificate!) Let's Encrypt works perfectly fine for that too. }:-) -- Grant. . .

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

11 Jan. 2019 г., 22:33 Rob McEwen : > but if done right, fwiw,, wouldn't that > be sent over SMTP using TLS encryption So STARTTLS strip is not a problem anymore? -- Töma

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On 1/11/2019 1:11 PM, Andreas Ott wrote: Admittedly, mailman does send you the password in clear text over SMTP if you ask for it  but if done right, fwiw,, wouldn't that be sent over SMTP using TLS encryption? (but, then again, that ALSO requires a certificate!) -- Rob McEwen, invaluement

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On Fri, Jan 11, 2019 at 12:17:09PM -0500, Rich Kulawiec wrote: > On Fri, Jan 11, 2019 at 08:23:31AM -0800, Yang Yu wrote: > > * no HTTPS > > HTTPS isn't needed for this application. I'll probably add it anyway > when I have a chance, but there are other things ahead of it. I respectfully disag

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

Thank you! Forwarded that to the RIPE IoT WG. 10 Jan. 2019 г., 19:23 Rich Kulawiec : > The "dumpsterfire" mailing list is for the discussion of security and > privacy issues related to the IoT (Internet of Things). Arguably, > the entire IoT *is* a security and privacy issu

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On Thu, Jan 10, 2019 at 10:57:02AM -0600, J. Hellenthal via NANOG wrote: > Unfortunately I don???t see this as having very much connectivity where I am > at. It's not the best-connected or most powerful server, however it's been running a bunch of public/private mailing lists for many years and f

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

ct to see when a Mailman archive is empty, as it is for any new mailing list. Now it's not. So now you won't. ---rsk

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On Fri, Jan 11, 2019 at 10:30:57AM -0600, Mike Hammett wrote: > No HTTPS?!?! Where are the tar and feathers??!?!! > > This isn't something that needs HTTPS. > - > Mike Hammett > Intelligent Computing Solutions True, but our browser overlords would condemn it because they seem to believe

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

Cc: "NANOG list" Sent: Friday, January 11, 2019 10:23:31 AM Subject: Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues On Thu, Jan 10, 2019 at 8:23 AM Rich Kulawiec wrote: > > The "dumpsterfire" mailing list is for the di

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

A dumpster fire, indeed. On Fri, Jan 11, 2019, 11:26 AM Yang Yu On Thu, Jan 10, 2019 at 8:23 AM Rich Kulawiec wrote: > > > > The "dumpsterfire" mailing list is for the discussion of security and > > privacy issues related to the IoT (Internet of Things). Arguabl

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

On Thu, Jan 10, 2019 at 8:23 AM Rich Kulawiec wrote: > > The "dumpsterfire" mailing list is for the discussion of security and > privacy issues related to the IoT (Internet of Things). Arguably, > the entire IoT *is* a security and privacy issue, but we'll get to that

Re: Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

> On Jan 10, 2019, at 10:22, Rich Kulawiec wrote: > > The "dumpsterfire" mailing list is for the discussion of security and > privacy issues related to the IoT (Internet of Things). Arguably, > the entire IoT *is* a security and privacy issue, but we'll get to that &g

Announcing: "dumpsterfire", the mailing list for IoT security/privacy issues

The "dumpsterfire" mailing list is for the discussion of security and privacy issues related to the IoT (Internet of Things). Arguably, the entire IoT *is* a security and privacy issue, but we'll get to that in good time. If you want to join, you can either use the

Re: AW: DSL Operators Mailing List?

Until now I've got only four replies... I don't think it justifies the effort to operate a mailing list. There should be a bit more interest before I would set it up. Am Mittwoch, 9. Mai 2018, 23:01:13 schrieb Karsten Thomann via NANOG: > ?If there is real interest just let me know

AW: DSL Operators Mailing List?

‎If there is real interest just let me know and I'll set up a mailman for a mailing list.  I think it is the simplest solution for all...   Originalnachricht   Von: Scott Weeks Gesendet: Mittwoch, 9. Mai 2018 22:54 An: nanog@nanog.org Antwort an: sur...@mauigateway.com Betreff: Re

Re: DSL Operators Mailing List?

>> I made a Facebook group for xLEC-related things. > (Not useful for those of us not on Facebook.) Whaaat??? Someone's not on FB? Because...like totally...all the cool kids are doing it! Don't you want to be one of the cool kids, too? >>> Then don't participate and move on? Awww, too b

Re: DSL Operators Mailing List?

uot; To: nanog@nanog.org Sent: Tuesday, May 8, 2018 11:19:30 AM Subject: Re: DSL Operators Mailing List? On 05/08/2018 07:12 AM, Mike Hammett wrote: I made a Facebook group for xLEC-related things. (Not useful for those of us not on Facebook.)

Re: DSL Operators Mailing List?

ubject: Re: DSL Operators Mailing List? On 05/08/2018 07:12 AM, Mike Hammett wrote: > I made a Facebook group for xLEC-related things. (Not useful for those of us not on Facebook.)

Re: DSL Operators Mailing List?

> On May 8, 2018, at 11:19 AM, Stephen Satchell wrote: > > (Not useful for those of us not on Facebook.) LIKE

Re: DSL Operators Mailing List?

On 05/08/2018 07:12 AM, Mike Hammett wrote: I made a Facebook group for xLEC-related things. (Not useful for those of us not on Facebook.)

Re: DSL Operators Mailing List?

t;NANOG" Sent: Sunday, January 7, 2018 11:10:11 AM Subject: DSL Operators Mailing List? Is there a good mailing list for DSL operators? A cursory search really only came up with DSL Reports, which is far from what I'm looking for. - Mike Hammett Intelligent Computing Sol

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

Subject: Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder] Date: Fri, Feb 02, 2018 at 04:04:54PM -0500 Quoting valdis.kletni...@vt.edu (valdis.kletni...@vt.edu): > And you have reason to think that it *still* does things that way, 17 years > later? I honestly

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

On Fri, 02 Feb 2018 19:13:04 +0100, Måns Nilsson said: > A VM/370 app that still does all internal processing in EBCDIC, even on > POSIX OSes[0], with almost-ascii config files, and that ran very well > on VMS? What is there not to love? > [0] Eric Thomas, mr LISTSERV himself, told me this when w

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

On Fri, 02 Feb 2018 06:30:20 -0500, Rich Kulawiec said: > > 1. It's not a listserv. It's a mailing list. ListServ is obsolete, > expensive, closed-source garbage software used exclusively by people > who don't know any better and like to waste their money. Well Rich,

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

Subject: Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder] Date: Fri, Feb 02, 2018 at 06:30:20AM -0500 Quoting Rich Kulawiec (r...@gsp.org): > > 1. It's not a listserv. It's a mailing list. ListServ is obsolete, > expensive, closed-source ga

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

Last night there was an update to the OS of our production environment, and a restart of the system. We are currently working to confirm all is functioning properly. Apologies for the extra noise in the mail list. Cheers, Valerie Valerie Wittkop NANOG Program Director Tel: +1 866 902 133

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

Groundhog day AGAIN! Lyle On 2/1/2018 10:07 PM, Jean-Francois Mezei wrote: On 2018-02-01 22:59, Paul Ferguson wrote: Started getting a series of these just now from the past. :-) Same here. The 821 headers show Received: to be "now", while the RFC 822 headers have a Date of first of where

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

1. It's not a listserv. It's a mailing list. ListServ is obsolete, expensive, closed-source garbage software used exclusively by people who don't know any better and like to waste their money. 2. This problem was possibly, but not certainly, caused by a misfiring cron job.

Re: listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

On 2018-02-01 22:59, Paul Ferguson wrote: > Started getting a series of these just now from the past. :-) Same here. The 821 headers show Received: to be "now", while the RFC 822 headers have a Date of first of where Month started in August 2017. Suspect something got reset and the list serve

listserv hosed? [Was: Fwd: nanog.org mailing list memberships reminder]

- Forwarded Message Subject: nanog.org mailing list memberships reminder Date: Fri, 01 Sep 2017 05:00:40 + From: mailman-ow...@nanog.org To: fergdawgs...@mykolab.com This is a reminder, sent out once a month, about your nanog.org mailing list memberships. It includes your subscription

Re: DSL Operators Mailing List?

Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com - Original Message - From: "Colton Conor" To: "James Bensley" Cc: "Mike Hammett" , "NANOG" Sent: Monday, January 8, 2018 8:24:35 PM Subject: Re: DSL Operators Mai

Re: DSL Operators Mailing List?

Mike, Lots of people on this list have DSL experience. What are you looking for? On Mon, Jan 8, 2018 at 8:21 AM, James Bensley wrote: > On 7 January 2018 at 17:10, Mike Hammett wrote: > > Is there a good mailing list for DSL operators? A cursory search really > only came up with

Re: DSL Operators Mailing List?

On 7 January 2018 at 17:10, Mike Hammett wrote: > Is there a good mailing list for DSL operators? A cursory search really only > came up with DSL Reports, which is far from what I'm looking for. Hi Mike, I only know of the https://puck.nether.net/mailman/listinfo/cisco-bba list.

DSL Operators Mailing List?

Is there a good mailing list for DSL operators? A cursory search really only came up with DSL Reports, which is far from what I'm looking for. - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP

Mailing list messages with attachments (was Re:)

Be advised that I have made changes to my personal spam traps to bin mailing list messages with attachments. -- sed quis custodiet ipsos custodes? (Juvenal)

Re: Mailing list posts wrapped

In message , Andrew Koch writes : > There was an inadvertent DMARC handling setting applied to all posts. This h= > as been corrected. Sorry for the disruption.=20 > > Andrew Koch= It was also not copying the Subject: to the outer SMTP envelope. It would pay to check that this is being done to a

Mailing list posts wrapped

There was an inadvertent DMARC handling setting applied to all posts. This has been corrected. Sorry for the disruption. Andrew Koch

IANA Stewardship Transition Proposal - Issue survey and ARIN-region Mailing List

net> mailing list. The survey results and discussion on that mailing list will be used to formulate a proposal from the ARIN region (to be combined with the other regions) for transition of the IANA stewardship. Reference the ICANN announcement for more background. Thanks!

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On Fri, Oct 10, 2014 at 09:48:26PM +0530, Suresh Ramasubramanian wrote: > Call it triage. When a minuscule amount of mailing list traffic is weighed > against huge volumes of forged spam and phish... Triage as an abuse mitigation tactic is fine. But where that triage needs to be applie

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

>But other than providing more warning, what would have been a better >way to start eliminating forged senders? Everything I've read >indicates that both Yahoo and AOL did this with eyes wide open. A good move would have been to improve their security so that AOL and Yahoo didn't have massive the

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

rd? What other theory > about their motivation makes sense? I'm fairly sure that their motivation wasn't anything like that clearly thought through - but their motivation doesn't really matter. Mailing list operators are stuck in the middle, and they have three reasonable

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On Fri, Oct 10, 2014 at 12:21 PM, Royce Williams wrote: > What other theory about their motivation makes sense? Most of the DMARC backers offer one or more services that compete with traditional mailinglists. -Jim P.

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On Fri, Oct 10, 2014 at 7:31 AM, Steve Atkins wrote: > If your domain publishes p=reject it should not have any users > that participate in mailing lists. Like many, I was pretty unhappy (and busy) with the unilateral changes made by Yahoo and AOL. But this understandable stance may change. Neit

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

Call it triage. When a minuscule amount of mailing list traffic is weighed against huge volumes of forged spam and phish... On 10-Oct-2014 9:40 pm, "Michael Thomas" wrote: > On 10/10/2014 08:10 AM, Randy Bush wrote: > >> a better approach would be to recommend that mai

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On 10/10/2014 08:10 AM, Randy Bush wrote: a better approach would be to recommend that mailing list participants who want to actually participate should utilize a mail service appropriate for the purpose. support to be fair, this means EITHER one which does not DMARC mark messages OR one which

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On Oct 10, 2014, at 8:05 AM, Christopher Morrow wrote: > On Fri, Oct 10, 2014 at 10:54 AM, Randy Bush wrote: >>> a better approach would be to recommend that mailing list participants >>> who want to actually participate should utilize a mail service >>&g

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

>>> a better approach would be to recommend that mailing list participants >>> who want to actually participate should utilize a mail service >>> appropriate for the purpose. >> >> support > > to be fair, this means EITHER one which does not DMARC m

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On Fri, Oct 10, 2014 at 10:54 AM, Randy Bush wrote: >> a better approach would be to recommend that mailing list participants >> who want to actually participate should utilize a mail service >> appropriate for the purpose. > > support to be fair, this means EITHER one w

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

> a better approach would be to recommend that mailing list participants > who want to actually participate should utilize a mail service > appropriate for the purpose. support

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

FYI, I migrated to Mailman 2.1.18-1 shortly after Yahoo decided to break every mailing list on the Internet for no good reason. (It certainly has done nothing to mitigate the ongoing flow of spam, phishing and other abuse coming from Yahoo, which continues pretty much as it has for many years

Re: Bounce action notifications - NANOG mailing list changes yahoo.com users

On Thu, Oct 9, 2014 at 2:20 PM, Andrew Koch wrote: > To correct this moving forward, selective rewriting of the from header > has been recommended, but requires an upgrade to the Mailman software. If the admins have settled on a best practice, it could help other Mailman operators like myself.

Bounce action notifications - NANOG mailing list changes yahoo.com users

Hello Colleagues, The NANOG mailing list had a discussion several months back regarding changes that Yahoo made to their DMARC settings. Over the past day, the NANOG mailing list has received a number of posts from yahoo.com mail users. This triggered bounce action on nearly 300 NANOG

[Infowarrior] - FYI ~ attrition.org uses an invalid security certificate for mailing list sign-up

FYI... Say it isn't so In today's Heartbleed state of affairs... attrition.org uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for Lyger The certificate expired on 12/21/2012 1:44 PM. The current time i

Data Mining/Crawling through a Mailing List

Hello, A bit off topic but i was looking for a way/tool that could crawl through nanog(or other) archives and try to filter most common discussions and things like that, if anyone is aware of such a tool, pls let me know. Thanks, Kim

RE: Data Mining/Crawling through a Mailing List

attachments) to post directly to NANOG. Tony Patti CIO S. Walter Packaging Corp. -Original Message- From: Kasper Adel [mailto:karim.a...@gmail.com] Sent: Thursday, September 05, 2013 2:22 PM To: NANOG list Subject: Data Mining/Crawling through a Mailing List Hello, A bit off topic but i was

RE: Data Mining/Crawling through a Mailing List

That tool will have its work cut out for it... ;) Sent from my Mobile Device. Original message From: Kasper Adel Date: 09/05/2013 11:23 AM (GMT-08:00) To: NANOG list Subject: Data Mining/Crawling through a Mailing List Hello, A bit off topic but i was looking for a way

Re: Data Mining/Crawling through a Mailing List

Dump it all into Hadoop and run a word cloud analysis :3. Honestly it sounds like a cool idea, and I'm sure someone has worked on it before but I don't know anything off the top of my head. Cheers, Joshua Sent from my iPad On Sep 5, 2013, at 11:23 AM, "Kasper Adel" wrote: > Hello, > > A bit

Re: Fwd: Welcome to the "Marketing" mailing list

Betty Burke wrote: Everyone: This was truly just a honest mistake on my part. You are all right, should not have happened and I apologize. No worries, Betty. The only ones amongst us who don't make mistakes are the ones who don't do anything. --Michael

Re: Welcome to the "Marketing" mailing list

On 11/17/2011 10:47 AM, Jay Ashworth wrote: My, but there are a lot of people, in my best friend's favorite phrase, "spring loaded to the pissed-off position". I didn't think NANOGers were quite so prone to recreational indignation... Cheers, -- jra NANOG where no day is complete without a bit

Re: Welcome to the "Marketing" mailing list

On 11/17/2011 3:47 PM, Jay Ashworth wrote: > My, but there are a lot of people, in my best friend's favorite phrase, > "spring loaded to the pissed-off position". I didn't think NANOGers were > quite so prone to recreational indignation... > > Cheers, > -- jra If only there was some sort of movem

Re: Welcome to the "Marketing" mailing list

On Nov 17, 2011, at 3:47 PM, Jay Ashworth wrote: > - Original Message - >> From: "Richard Golodner" > >>> 1. Why was such a list created? >>> 2. Why was I automatically subscribed to it? >>> 3. Why was this done without notice to the community? > >> This has a lot of us wondering the sa

Re: Welcome to the "Marketing" mailing list

- Original Message - > From: "Richard Golodner" > > 1. Why was such a list created? > > 2. Why was I automatically subscribed to it? > > 3. Why was this done without notice to the community? > This has a lot of us wondering the same as Owen. > This is also not typical of how NANOG does t

Re: Fwd: Welcome to the "Marketing" mailing list

To echo what Betty said and address an unspoken concern: "market...@nanog.org" is the mailing list (and external interface?) for the folks who make sure that there are good cookies and other break goodies, beer-n-gear sponsors, meeting hosts, etc. It is most assuredly not a spamming l

Re: Fwd: Welcome to the "Marketing" mailing list

Everyone: This was truly just a honest mistake on my part. You are all right, should not have happened and I apologize. market...@nanog.org is a list used in connection with Sponsorship inquiries/activity. refer to http://www.nanog.org/sponsors/ Membership of market...@nanog.or is the Developmen

Re: Welcome to the "Marketing" mailing list

On Thu, 17 Nov 2011 12:59:38 EST, "Betty Burke " said: > So Sorry Owen, as explained earlier, my mistake in list management! All > resolved and those members added to the wrong list have been removed. It's OK.. Everybody's entitled to at least one low-caffeine low-impact faux pax a year. ;) pg

Re: Fwd: Welcome to the "Marketing" mailing list

On Thu, 2011-11-17 at 09:35 -0800, Owen DeLong wrote: > Can someone explain this one to me? > > 1. Why was such a list created? > 2. Why was I automatically subscribed to it? > 3. Why was this done without notice to the community? > > Thanks, This has a lot of us wondering

Re: Welcome to the "Marketing" mailing list

> Date: November 17, 2011 7:17:00 AM PST > > To: o...@delong.com > > Subject: Welcome to the "Marketing" mailing list > > > > Welcome to the market...@nanog.org mailing list! > > > > To post to this list, send your message to: > > > >

Re: Fwd: Welcome to the "Marketing" mailing list

On 11/17/2011 9:35 AM, Owen DeLong wrote: Um, Can someone explain this one to me? 1. Why was such a list created? 2. Why was I automatically subscribed to it? 3. Why was this done without notice to the community? Before this erupts in yet another thread, this was already asked

  1   2   >