Favorite comment of the week!
-Eric
From: Don Gould via NANOG
Sent: Monday, March 3, 2025 6:38 PM
To: North American Network Operators Group
Cc: Niels Bakker ; Don Gould
Subject: [NANOG] Re: DKIM and list policies (was Re: Scheduled Maintenance
Finished)
Lol
12:13 pm (GMT+12:00)
> To: nanog@lists.nanog.org
> Cc: Niels Bakker , nanog@lists.nanog.org, Joel Esler
>
> Subject: [NANOG] Re: DKIM and list policies (was Re: Scheduled Maintenance
> Finished)
>
> I know! I had to update my rules too! Was wondering why all the list
&
(GMT+12:00) To:
nanog@lists.nanog.org Cc: Niels Bakker ,
nanog@lists.nanog.org, Joel Esler Subject: [NANOG] Re:
DKIM and list policies (was Re: Scheduled Maintenance Finished) I know! I had
to update my rules too! Was wondering why all the list traffic was finding its
way into my inbox.—Sent from
I know! I had to update my rules too! Was wondering why all the list traffic
was finding its way into my inbox.
—
Sent from my iPad
> On Mar 3, 2025, at 15:50, Vinny Abello via NANOG
> wrote:
>
> On 3/3/2025 2:28 PM, Sam Thomas via NANOG wrote:
>> Surprised I'm the first (I know of) to com
On 3/3/2025 2:28 PM, Sam Thomas via NANOG wrote:
Surprised I'm the first (I know of) to complain that List-id: changed. (insert
whining about how I had to adjust email filter here)
I just had to update my procmail config to match the new
list-id.
I've been complaining (in my head) since it
On 3/2/25 3:46 PM, Bryan Fields wrote:
There are two other options:
1. Rewrite the from for all messages
2. Implement ARC https://arc-spec.org/
Option one is a bit like a shotgun approach, but it works across all
providers, and is well understood. A number of other lists in our
industry do
On 3/3/25 12:30 PM, Matt Corallo via NANOG wrote:
On 3/2/25 6:46 PM, Bryan Fields wrote:
There are two other options:
1. Rewrite the from for all messages
2. Implement ARC https://arc-spec.org/
Option one is a bit like a shotgun approach, but it works across all
providers, and is well unde
On 3/2/25 6:46 PM, Bryan Fields wrote:
There are two other options:
1. Rewrite the from for all messages
2. Implement ARC https://arc-spec.org/
Option one is a bit like a shotgun approach, but it works across all providers, and is well
understood. A number of other lists in our industry do
On Mon, Mar 3, 2025 at 3:39 AM Niels Bakker via NANOG
wrote:
>
>
>
>
> -- Forwarded message --
> From: Niels Bakker
> To: nanog@lists.nanog.org
> Cc:
> Bcc:
> Date: Mon, 3 Mar 2025 10:38:20 +0100
> Subject: [NANOG] Re: DKIM and list polici
* Ray Bellis [Mon 03 Mar 2025, 11:26 CET]:
Note also that the List-Id has changed from to
.
This broke my folder filtering.
Same. To be fair, that change, while unnecessary, was preannounced here
https://mailman.nanog.org/pipermail/nanog/2025-February/227312.html
-- Niels.
__
On 03/03/2025 10:02, Bryan Fields via NANOG wrote:
Currently the list is configured to rewrite the from as being from the
list, ex: "From: Bryan Fields via NANOG ". It is
possible to see if the signature on the inbound message was valid by
looking at the "Authentication-Results: lists.nanog.o
On 3/3/25 04:38, Niels Bakker via NANOG wrote:
Agreed on both counts. Look at this monstrosity:
Subject: [NANOG] Re: [NANOG]Re: Hardware for MPLS/SR network
That happened since the "[NANOG]" was changed to "[NANOG] " and mailman will
only catch the current prefix. Mailman will find any in
--- Begin Message ---
* br...@bryanfields.net (Bryan Fields) [Mon 03 Mar 2025, 00:47 CET]:
The footer is a bit redundant, as mailman3 has the direct link in
the "Archived-At:" header now. I'd propose removing the footer and
subject prefix, and investigate implementing ARC now that we can
sup
13 matches
Mail list logo
