BALUG-Admin

balug-admin@lists.balug.org

2 participants
548 discussions

Gandi.net wins (was: So, joker.com, then?)
by Rick Moen 02 Jun '24

02 Jun '24

I note with no objection that you dropped offlist, but I'll move back anyway. Quoting Michael Paoli (michael.paoli(a)berkeley.edu): > I'm thinking the option may also be generic, > but whether or not it actually does anything may be > TLD specific, so, e.g. may do nothing for com., > but may actually be usefully effective for some other > TLDs. I.e. com. may not even use or accept "Billing Contact" > into whois data, but some other TLDs may accept such. FWIW, I also see that Billing Contact isn't shown in public WHOIS for unixmercenary.net, either -- but that's consistent with your hypothesis, since both com. and net. are operated by VeriSign, Inc. as "authoritative registry", or, as VeriSign calls it, the firm's "naming services division". https://en.wikipedia.org/wiki/Verisign#Naming_services That line of business it acquired by buying Network Solutions in 2000, divesting the _regisrar_ portion in 2003 but keeping the registry (wholesale & back-end) portion. They also, ugh, have the contract for the root nameserver operation, operating two of them, "A" and "J", directly. Plus maintaining the root zonefile. NetSol, in turn, got the football in 1993 under contract from NSF. The division between "registry" and "registrar" (within NetSol) followed in 1998 when ICANN got conjured into existence (at the invitation of Dept. of Commerce, IIRC), and ICANN grandly pronounced that it required NetSol to engineer an interface permitting competing registrars. (ICANN by itself was a "Who the hell are you?" paper tiger, but they had the blessing of US Dept. of Commerce Dept., which had legal and checkbook power, and ISTR somehow the issuance of marching orders somehow went from Commerce to ICANN to IATA (which is a nonprofit under Commerce Dept. contract, hence checkbook power). VeriSign Naming Services is now at 12061 Bluemont Way, Reston Town Center development, Reston, VA. Anyway, bottom line, I concur with your guess that "Billing Contact doesn't go into WHOIS" is probably implemented at the VeriSign com./net./etc. end of things, and is probably a legacy of NetSol 1990s buildout that's still embedded into everything, there.

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Jun '24

01 Jun '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-06-01 498 231 33 2024-05-01 499 231 33 2024-04-01 500 230 33 2024-03-01 498 230 33 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 May '24

01 May '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-05-01 499 231 33 2024-04-01 500 230 33 2024-03-01 498 230 33 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Apr '24

01 Apr '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-04-01 500 230 33 2024-03-01 498 230 33 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

Re: [BALUG-Admin] very delayed: [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG News
by Michael Paoli 19 Mar '24

19 Mar '24

+balug-admin(a)lists.balug.org - don't send/cc/bcc to that email if you're not on that list Oh, and most of the timezones are UTC, unless indicated otherwise. So ... first we look at full headers of the received. To make that simpler, I first unfolded (any header lines starting with a space I joined to line above), then removed all lines except those with a date or timestamp or the like and also retaining those that might be relatively usefully informative, and dropped the rest. Then for readability I (re)folded those more than 72 characters wide, with a space indent where folded. And I preserved ordering. That leaves us with: Received: by 2002:aa7:da18:0:b0:568:550c:e550 with SMTP id r24csp203374eds; Thu, 14 Mar 2024 00:51:42 -0700 (PDT) X-Received: by 2002:a05:6808:1285:b0:3c2:18fe:f810 with SMTP id a5-20020a056808128500b003c218fef810mr1187019oiw.27.1710402702247; Thu, 14 Mar 2024 00:51:42 -0700 (PDT) Return-Path: <balug-announce-bounces(a)lists.balug.org> Received: from balug-sf-lug-v2.balug.org (balug.org. [2001:470:1f05:19e::2]) by mx.google.com with ESMTPS id e17-20020aca1311000000b003c365f41a1fsi65493oii.37.2024.03.14.00.51.41 for <michael.paoli(a)cal.berkeley.edu> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Mar 2024 00:51:42 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=balug.org) by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) (envelope-from <balug-announce-bounces(a)lists.balug.org>) id 1rkfsB-0002wb-L7; Thu, 14 Mar 2024 07:51:31 +0000 Received: from shell1.rawbw.com ([198.144.192.42]) by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) (envelope-from <Michael.Paoli(a)cal.berkeley.edu>) id 1rcPqS-0002KU-Ko for balug-announce(a)lists.balug.org; Tue, 20 Feb 2024 13:07:36 +0000 Received: from webmail.rawbw.com (mail0.rawbw.com [198.144.192.41]) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTP id 41KD7ZwB068218; Tue, 20 Feb 2024 05:07:35 -0800 (PST) (envelope-from Michael.Paoli(a)cal.berkeley.edu) Date: Tue, 20 Feb 2024 05:07:35 -0800 To: BALUG-Announce <balug-announce(a)lists.balug.org> Message-ID: <94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu> X-Sender: Michael.Paoli(a)cal.berkeley.edu Received-SPF: none client-ip=198.144.192.42; envelope-from=Michael.Paoli(a)cal.berkeley.edu; helo=shell1.rawbw.com Subject: [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG News From: Michael Paoli via BALUG-Announce <balug-announce(a)lists.balug.org> Reply-To: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> Errors-To: balug-announce-bounces(a)lists.balug.org Sender: BALUG-Announce <balug-announce-bounces(a)lists.balug.org> So, we see the big time gap here: Received: from localhost ([127.0.0.1] helo=balug.org) by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) (envelope-from <balug-announce-bounces(a)lists.balug.org>) id 1rkfsB-0002wb-L7; Thu, 14 Mar 2024 07:51:31 +0000 Received: from shell1.rawbw.com ([198.144.192.42]) by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) (envelope-from <Michael.Paoli(a)cal.berkeley.edu>) id 1rcPqS-0002KU-Ko for balug-announce(a)lists.balug.org; Tue, 20 Feb 2024 13:07:36 +0000 Those Received: headers are read from bottom up in order of processing, newer Received: headers are added atop any existing. That's not only useful for tracing route of mail, but these also generally include timestamps. So, I sent it from one of my ISP's email to the list, and that was received, then it took a long time for the next hop - which was entirely local on the same host - so something went wrong there between MTA and/or mailman. If I convert those timestamps to ISO format, have: 2024-02-20T13:07:36+0000 2024-03-14T07:51:31+0000 $ who -r run-level 5 Mar 14 06:51 So, between that and a presumed exponential back-off on retries on the sending MTA, that would presumably account for when the MTA received that, presuming for the period before that there was some reason it couldn't or wouldn't. And looking at receiving MTA logs, no shortage of logs between those timestamps, so ... what happened? We do have: Message-ID: <94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu> and that should be unique, so can be quite useful for, e.g. searching in mail logs. What (if anything) can we find for that in the time range in question? MTA exim4 ... I don't have mainlog files going back that far, but I do have rejectlog files going back that far. In chronological order by mtime for files covering range: 2024-02-20T13:07:36+0000 2024-03-14T07:51:31+0000 have files matching these patterns: rejectlog.{5{9,8,7,6,5,4,3,2,1,0},4{9,8,7,6,5,4,3,2,1,0},3{9,8,7,6,5,4,3,2,1,0},2{9,8,7}}.gz paniclog rejectlog.{2{6,5,4,3,2,1,0},1{9,8,7,6,5,4,3,2,1,0}}.gz mainlog.10.gz eval echo \{rejectlog,mainlog\}{.{9,8,7,6,5,4,3,2,1}.gz,} checking for that Message-ID, have: ( Message_ID='94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu' eval set -- \ rejectlog.{5{9,8,7,6,5,4,3,2,1,0},4{9,8,7,6,5,4,3,2,1,0},3{9,8,7,6,5,4,3,2,1,0},2{9,8,7}}.gz \ paniclog \ rejectlog.{2{6,5,4,3,2,1,0},1{9,8,7,6,5,4,3,2,1,0}}.gz \ mainlog.10.gz \ \{rejectlog,mainlog\}{.{9,8,7,6,5,4,3,2}.gz,.1,} for f do case "$f" in *.gz) gzip -d < "$f" | grep -F -q -e "$Message_ID" && { echo "$f" gzip -d < "$f" | grep -F -e "$Message_ID" } ;; *) grep -F -l -e "$Message_ID" "$f" && grep -F -e "$Message_ID" "$f" ;; esac done ) mainlog.5.gz 2024-03-14 07:51:31 1rkfsB-0002wb-L7 <= balug-announce-bounces(a)lists.balug.org H=localhost (balug.org) [127.0.0.1] P=esmtp S=7761 id=94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu 2024-03-14 07:51:31 1rkfsB-0002wb-Me <= balug-announce-bounces(a)lists.balug.org H=localhost (balug.org) [127.0.0.1] P=esmtp S=7761 id=94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu 2024-03-14 07:51:31 1rkfsB-0002wb-TW <= balug-announce-bounces(a)lists.balug.org H=localhost (balug.org) [127.0.0.1] P=esmtp S=7761 id=94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu 2024-03-14 07:51:31 1rkfsB-0002wb-UG <= balug-announce-bounces(a)lists.balug.org H=localhost (balug.org) [127.0.0.1] P=esmtp S=7761 id=94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu 2024-03-14 07:51:41 1rkfsB-0002wb-L7 => <REDACTED> ... So, basically it comes in (apparently goes through multiple times in processing), and then lots of sends out very shortly after that. Unfortunately don't have the earlier mainlog files, so not sure what may have happened then - at least as far as MTA goes. Let's see about mailman. For log files in the relevant time frame, and ignoring those which are compressed empty files (yeah, I should have logrotate not compress empty files), these are the files in chronological order (by mtime): vette.4.gz mischief.1 error.3.gz error.2.gz security qrunner.5.gz smtp-failure.5.gz locks.5.gz smtp.5.gz qrunner.4.gz bounce.1 subscribe And going through those files, nothing relevant in the applicable time frame. So ... thus far best guess is something that was essentially somewhere along that chain failed or wedged or died or crashed or the like, didn't particularly log anything indicating the problem in the meantime, and things went back to "normal" and got unjammed after host rebooted. Oh, mailman did also add it to the archives ... can we see when, that may provide a clue. >From Michael.Paoli(a)cal.berkeley.edu Tue Feb 20 13:07:36 2024 Received: from shell1.rawbw.com ([198.144.192.42]) by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) (envelope-from <Michael.Paoli(a)cal.berkeley.edu>) id 1rcPqS-0002KU-Ko for balug-announce(a)lists.balug.org; Tue, 20 Feb 2024 13:07:36 +0000 Received: from webmail.rawbw.com (mail0.rawbw.com [198.144.192.41]) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTP id 41KD7ZwB068218; Tue, 20 Feb 2024 05:07:35 -0800 (PST) (envelope-from Michael.Paoli(a)cal.berkeley.edu) From: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> To: BALUG-Announce <balug-announce(a)lists.balug.org> Message-ID: <94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu> X-Sender: Michael.Paoli(a)cal.berkeley.edu Subject: [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG News X-BeenThere: balug-announce(a)lists.balug.org Date: Tue, 20 Feb 2024 13:07:36 -0000 X-Original-Date: Tue, 20 Feb 2024 05:07:35 -0800 X-List-Received-Date: Tue, 20 Feb 2024 13:07:36 -0000 At least what shows in the archive (complete mbox file), from the full headers, looks like it got it in timely manner. What about where it processes those for showing on web? # pwd -P && ls -ontr $(find * ! -mtime +30 -type f -print | fgrep Feb) /var/lib/mailman/archives/private/balug-announce -rw-rw-r-- 1 38 5689 Mar 14 06:51 2024-February.txt -rw-rw-r-- 1 38 1729 Mar 14 06:51 2024-February/date.html -rw-rw-r-- 1 38 1723 Mar 14 06:51 2024-February/subject.html -rw-rw-r-- 1 38 1725 Mar 14 06:51 2024-February/author.html -rw-rw-r-- 1 38 1752 Mar 14 06:51 2024-February/thread.html -rw-rw-r-- 1 38 8276 Mar 14 06:51 2024-February/000340.html -rw-rw---- 1 38 136 Mar 14 06:51 database/2024-February-thread -rw-rw---- 1 38 183 Mar 14 06:51 database/2024-February-subject -rw-rw---- 1 38 131 Mar 14 06:51 database/2024-February-date -rw-rw---- 1 38 150 Mar 14 06:51 database/2024-February-author -rw-rw---- 1 38 1259 Mar 14 06:51 database/2024-February-article -rw-rw-r-- 1 38 2687 Mar 15 03:27 2024-February.txt.gz # Yeah, it would seem to implicate a problem within mailman. Looks like our sequence went about like this: 2024-02-20T13:07:36+0000 email generated on sending MTA, looks like it made it to receiving MTA and into mailman, notably mailman show it in the mbox full archive with corresponding timestamps, but then looks like it stuck at some point after that, notably not even the archiving was fully processed, as the web archive files didn't catch up until 2024-03-14T06:51+0000 we have a reboot $ who -r run-level 5 Mar 14 06:51 And the mailman web archive files catch up. Then, an hour later: 2024-03-14T07:51:31+0000 mail to list recipients is actually sent out (perhaps some retry logic caused the hour's delay at that point). Anyway, that's my best guestimation based on the evidence. ---------- Forwarded message --------- From: Michael Paoli <michael.paoli(a)cal.berkeley.edu> Date: Thu, Mar 14, 2024 at 8:26 PM Subject: Re: [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG News To: aaronco36 <aaronco36(a)sdf.org>, <balug-admin(a)lists.balug.org> Cc: Rick Moen <rick(a)linuxmafia.com> +balug-admin(a)lists.balug.org - don't send/cc/bcc to that email if you're not on that list Yeah, ... I noticed that too - haven't dug down yet to figure out what happened, but some list mail went out (or went out again?) very late - like weeks late. And like I say, haven't dug down to the bottom of it to figure out what happened yet. "Other than that" didn't notice anything unusual. But ... maybe some queue got stuck or some demon that was supposed to be running wasn't, and then perhaps with some reboot or update or the like, somehow things got unjammed and/or reprocessed? Still guessing a bit at this point - will need to review logs and some full headers and other details to figure out what happened. Anyway, maybe I get to it sometime this weekend(ish) or so. Shouldn't have happened, but there isn't an "undo" for mail sent, so 'bout best can do with it is figure out (hopefully) how it happened, and hopefully prevent a repeat of that. Possible some queue got stuck or daemon down or crashed or stuck, and I didn't catch it earlier, and things just got inordinately delayed ... that'd at least be my first guess, though there are certainly other possibilities. And it wasn't just that one BALUG-Announce mail, but a moderate spattering of mailman and/or exim4 mail that was impacted - all came through at once. I think I saw about 20 emails or so (most of which were for list admin or the like) all come through at or right around the same time. Anyway, probably answers to be found in the full headers and/or other log data and such. On Thu, Mar 14, 2024 at 7:58 PM aaronco36 <aaronco36(a)sdf.org> wrote: > > Hello Rick and Michael, > > > Quoting aaronco36 (aaronco36(a)sdf.org): > > > >> ???? > >> Now ~12:15 PDT (UTC-07:00) on Thursday 2024-03-14. > >> > >> aaronco36(at)SDF.org > > > > I'm not sure what you're talking about Aaron. The most recent > > balug-announce posting (this one, from Michael P.:) > > https://lists.balug.org/pipermail/balug-announce/2024-February/000340.html) > > really did go out on Tue Feb 20 13:07:36 UTC 2024, not today. > > > > > > Hmmmm, mystery to me as well :-\ > Perhaps very delayed transmission having something to do with the top pair > of "Received:" sections dated this morning, below ?? > > -A > > Contents of the Full Header of today's message: > ~~~~~~~~~~~~~~~~ quoting in full ~~~~~~~~~~~~~~~~~~~~~ > > Return-Path: <balug-announce-bounces(a)lists.balug.org> > Received: from balug-sf-lug-v2.balug.org (balug.org [96.86.170.229]) > by mx.sdf.org (8.16.1/8.14.3) with ESMTPS id 42E8VA6p012184 > (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified > NO) > for <aaronco36(a)sdf.org>; Thu, 14 Mar 2024 08:31:10 GMT > Received: from localhost ([127.0.0.1] helo=balug.org) > by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) > (envelope-from <balug-announce-bounces(a)lists.balug.org>) > id 1rkfsB-0002wb-Me; Thu, 14 Mar 2024 07:51:31 +0000 > Received: from shell1.rawbw.com ([198.144.192.42]) > by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) > (envelope-from <Michael.Paoli(a)cal.berkeley.edu>) id 1rcPqS-0002KU-Ko > for balug-announce(a)lists.balug.org; Tue, 20 Feb 2024 13:07:36 +0000 > Received: from webmail.rawbw.com (mail0.rawbw.com [198.144.192.41]) > by shell1.rawbw.com (8.15.1/8.15.1) with ESMTP id 41KD7ZwB068218; > Tue, 20 Feb 2024 05:07:35 -0800 (PST) > (envelope-from Michael.Paoli(a)cal.berkeley.edu) > X-Authentication-Warning: shell1.rawbw.com: Host mail0.rawbw.com > [198.144.192.41] claimed to be webmail.rawbw.com > MIME-Version: 1.0 > Date: Tue, 20 Feb 2024 05:07:35 -0800 > To: BALUG-Announce <balug-announce(a)lists.balug.org> > Message-ID: <94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu> > X-Sender: Michael.Paoli(a)cal.berkeley.edu > Received-SPF: none client-ip=198.144.192.42; > envelope-from=Michael.Paoli(a)cal.berkeley.edu; helo=shell1.rawbw.com > Subject: [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG > News > X-BeenThere: balug-announce(a)lists.balug.org > X-Mailman-Version: 2.1.29 > Precedence: list > List-Id: Announcements for and by BALUG <balug-announce.lists.balug.org> > List-Unsubscribe: > <https://lists.balug.org/cgi-bin/mailman/options/balug-announce>, > <mailto:balug-announce-request@lists.balug.org?subject=unsubscribe> > List-Archive: <https://lists.balug.org/pipermail/balug-announce/> > List-Post: <mailto:balug-announce@lists.balug.org> > List-Help: <mailto:balug-announce-request@lists.balug.org?subject=help> > List-Subscribe: > <https://lists.balug.org/cgi-bin/mailman/listinfo/balug-announce>, > <mailto:balug-announce-request@lists.balug.org?subject=subscribe> > From: Michael Paoli via BALUG-Announce <balug-announce(a)lists.balug.org> > Reply-To: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> > Content-Transfer-Encoding: 7bit > Content-Type: text/plain; charset="us-ascii"; Format="flowed" > Errors-To: balug-announce-bounces(a)lists.balug.org > Sender: "BALUG-Announce" <balug-announce-bounces(a)lists.balug.org> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >

1 0

Re: [BALUG-Admin] [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG News
by Michael Paoli 15 Mar '24

15 Mar '24

+balug-admin(a)lists.balug.org - don't send/cc/bcc to that email if you're not on that list Yeah, ... I noticed that too - haven't dug down yet to figure out what happened, but some list mail went out (or went out again?) very late - like weeks late. And like I say, haven't dug down to the bottom of it to figure out what happened yet. "Other than that" didn't notice anything unusual. But ... maybe some queue got stuck or some demon that was supposed to be running wasn't, and then perhaps with some reboot or update or the like, somehow things got unjammed and/or reprocessed? Still guessing a bit at this point - will need to review logs and some full headers and other details to figure out what happened. Anyway, maybe I get to it sometime this weekend(ish) or so. Shouldn't have happened, but there isn't an "undo" for mail sent, so 'bout best can do with it is figure out (hopefully) how it happened, and hopefully prevent a repeat of that. Possible some queue got stuck or daemon down or crashed or stuck, and I didn't catch it earlier, and things just got inordinately delayed ... that'd at least be my first guess, though there are certainly other possibilities. And it wasn't just that one BALUG-Announce mail, but a moderate spattering of mailman and/or exim4 mail that was impacted - all came through at once. I think I saw about 20 emails or so (most of which were for list admin or the like) all come through at or right around the same time. Anyway, probably answers to be found in the full headers and/or other log data and such. On Thu, Mar 14, 2024 at 7:58 PM aaronco36 <aaronco36(a)sdf.org> wrote: > > Hello Rick and Michael, > > > Quoting aaronco36 (aaronco36(a)sdf.org): > > > >> ???? > >> Now ~12:15 PDT (UTC-07:00) on Thursday 2024-03-14. > >> > >> aaronco36(at)SDF.org > > > > I'm not sure what you're talking about Aaron. The most recent > > balug-announce posting (this one, from Michael P.:) > > https://lists.balug.org/pipermail/balug-announce/2024-February/000340.html) > > really did go out on Tue Feb 20 13:07:36 UTC 2024, not today. > > > > > > Hmmmm, mystery to me as well :-\ > Perhaps very delayed transmission having something to do with the top pair > of "Received:" sections dated this morning, below ?? > > -A > > Contents of the Full Header of today's message: > ~~~~~~~~~~~~~~~~ quoting in full ~~~~~~~~~~~~~~~~~~~~~ > > Return-Path: <balug-announce-bounces(a)lists.balug.org> > Received: from balug-sf-lug-v2.balug.org (balug.org [96.86.170.229]) > by mx.sdf.org (8.16.1/8.14.3) with ESMTPS id 42E8VA6p012184 > (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified > NO) > for <aaronco36(a)sdf.org>; Thu, 14 Mar 2024 08:31:10 GMT > Received: from localhost ([127.0.0.1] helo=balug.org) > by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) > (envelope-from <balug-announce-bounces(a)lists.balug.org>) > id 1rkfsB-0002wb-Me; Thu, 14 Mar 2024 07:51:31 +0000 > Received: from shell1.rawbw.com ([198.144.192.42]) > by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92) > (envelope-from <Michael.Paoli(a)cal.berkeley.edu>) id 1rcPqS-0002KU-Ko > for balug-announce(a)lists.balug.org; Tue, 20 Feb 2024 13:07:36 +0000 > Received: from webmail.rawbw.com (mail0.rawbw.com [198.144.192.41]) > by shell1.rawbw.com (8.15.1/8.15.1) with ESMTP id 41KD7ZwB068218; > Tue, 20 Feb 2024 05:07:35 -0800 (PST) > (envelope-from Michael.Paoli(a)cal.berkeley.edu) > X-Authentication-Warning: shell1.rawbw.com: Host mail0.rawbw.com > [198.144.192.41] claimed to be webmail.rawbw.com > MIME-Version: 1.0 > Date: Tue, 20 Feb 2024 05:07:35 -0800 > To: BALUG-Announce <balug-announce(a)lists.balug.org> > Message-ID: <94cc17d1e831608786fb59c3a4eb70a9(a)cal.berkeley.edu> > X-Sender: Michael.Paoli(a)cal.berkeley.edu > Received-SPF: none client-ip=198.144.192.42; > envelope-from=Michael.Paoli(a)cal.berkeley.edu; helo=shell1.rawbw.com > Subject: [BALUG-Announce] BALUG: meeting TODAY!: Tu 2024-02-20 & other BALUG > News > X-BeenThere: balug-announce(a)lists.balug.org > X-Mailman-Version: 2.1.29 > Precedence: list > List-Id: Announcements for and by BALUG <balug-announce.lists.balug.org> > List-Unsubscribe: > <https://lists.balug.org/cgi-bin/mailman/options/balug-announce>, > <mailto:balug-announce-request@lists.balug.org?subject=unsubscribe> > List-Archive: <https://lists.balug.org/pipermail/balug-announce/> > List-Post: <mailto:balug-announce@lists.balug.org> > List-Help: <mailto:balug-announce-request@lists.balug.org?subject=help> > List-Subscribe: > <https://lists.balug.org/cgi-bin/mailman/listinfo/balug-announce>, > <mailto:balug-announce-request@lists.balug.org?subject=subscribe> > From: Michael Paoli via BALUG-Announce <balug-announce(a)lists.balug.org> > Reply-To: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu> > Content-Transfer-Encoding: 7bit > Content-Type: text/plain; charset="us-ascii"; Format="flowed" > Errors-To: balug-announce-bounces(a)lists.balug.org > Sender: "BALUG-Announce" <balug-announce-bounces(a)lists.balug.org> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Mar '24

01 Mar '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-03-01 498 230 33 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

So, DMARC. A week ago.
by Rick Moen 08 Feb '24

08 Feb '24

1. New Problem - Whee! At the beginning of this month, Yahoo (or whatever they're called) and Google tightened down the screws on requiring DMARC and encouraging DKIM (and/or SPF). https://blog.google/products/gmail/gmail-security-authentication-spam-prote… https://support.google.com/a/answer/81126?visit_id=638429646339446077-23847… See links for GMail's alleged implementation, which has numerous parts. The page _claims_ the Feb. 1 enforcement is just for "bulk senders — those who send more than 5,000 messages to Gmail addresses in one day", but word around the Net is that they started spamboxing mail from even _tiny_ mail sending domains not in compliance. 2. Parts of the Problem (Gods, I hope my MTA uses TLS for transmitting mail. It's been so long since I looked at that, I'm not sure. Anyway, that was a hard requirement for reaching GMail starting 2023-12-31, per above pages.) Here, verbatim, are the requirements Gmail says it henceforth requires of all sending domains (with some others for "bulk senders"): o Set up SPF or DKIM email authentication for your domain. o Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records. Learn more o Use a TLS connection for transmitting email. For steps to set up TLS in Google Workspace, visit Require a secure connection for email. o Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher. Learn more about spam rates. o Format messages according to the Internet Message Format standard (RFC 5322). o Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy, and impersonating Gmail From: headers might impact your email delivery. o If you regularly forward email, including using mailing lists or inbound gateways, add ARC headers to outgoing email. ARC headers indicate the message was forwarded and identify you as the forwarder. Mailing list senders should also add a List-id: header, which specifies the mailing list, to outgoing messages. (I'm blearily looking up what is meant by "ARC headers", and I have never previously had cause or interest to look at Google's Postmaster Tools.) 3. DKIM Considered Harmful Long rant not indulged here: DKIM is mailing list-hostile (though mitigations are possible). I'm sitting out DKIM mail-signing, but also my present host can't do it as equipped anyway. DMARC is a metastandard atop either or both of SPF and DKIM. By the definition of DMARC, if you have both (a) a valid DMARC DNS record and (b) _either_ DKIM or SPF (or both), then you are DMARC-compliant. 4. SPF Is My Jedi Master linuxmafia.com has had bullet-proof, simple SPF for ages. I like SPF and consider it well-scoped, well-implemented for preventing others to believably forge your domain for mail. It's good here, it works. Here: :r! dig -t txt @ns1.linuxmafia.com linuxmafia.com +short "v=spf1 ip4:96.95.217.99 -all" Dirt-simple: It says "If mail arrives from any IP other than 96.95.217.99 purporting to be from linuxmafia.com, please treat it as forged." 5. Let's Look at a Good DMARC RR So, obviously I need a value DMARC record as of a week ago. A couple of years ago, I tried one, and could swear I remember it impairing my deliverability of mailing list mail (but can't remember details), not to mention the avalanche of DMARC "report" mails that are the hallmark of that botched (IMO) Yahoo anti-forgery metastandard. But, let's look at the RR for mxtoolbox.com. The RR is always hostname _dmarc , and is a TXT record. In mxtoolbox.com's case, that's a CNAME pointing to mxtoolbox.com.hosted.dmarc-report.com . Here 'tis: :r! dig -t txt mxtoolbox.com.hosted.dmarc-report.com +short "v=DMARC1; p=reject; rua=mailto:634990a7@mxtoolbox.dmarc-report.com,mailto:634990a7@mxtoolbox.dmarc-report.net; ruf=mailto:634990a7@forensics.dmarc-report.com; fo=1; pct=100" Breaking that down: FQDN: mxtoolbox.com.hosted.dmarc-report.com. TTL: 300 class: IN RR type: TXT TXT record breakdown (from within doublequotes): Version: v=DMARC1; Action to take if the mail fails authentication: p=reject Report URIs for Aggregate data to (optional): rua=mailto:634990a7@mxtoolbox.dmarc-report.com,mailto:634990a7@mxtoolbox.dmarc-report.net; Report URIs for Forensics/Failure data to (optional): ruf=mailto:634990a7@forensics.dmarc-report.com; Forensic Options: fo=1; Percentage of mail subjected to filtering: pct=100 6. Let's build a _dmarc.linuxmafia.com DMARC RR So, in consultation with the pages mentioned below, I constructed one (and these were my resulting notes): Include v=DMARC1; because DMARCv1 is the only game in town. Note that this tag must appear first, or the RR is not a valid DMARC record. Start policy adoption with p=none; (mostly because of mailing list forwarding). https://dmarc.org/2017/03/can-i-use-dmarc-if-i-have-only-deployed-spf/ Include sp=none; This is the "p" policy setting, except as applied to subdomains. https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-sp Omit aspf=$THING option for now; defaults to "relaxed" SPF alignment (though I think all mail from linuxmafia.com will originate from that FQDN as MailFROM and Header From domains). https://mxtoolbox.com/dmarc/details/dmarc-tags/aspf Include fo=s; This generates an SPF failure report if the message failed SPF evaluation, regardless of its alignment. This setting is used to decide what to send to addresses specified in the RUF tag. https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-failure-reporting-opti… Include rua=mailto:hostmaster@linuxmafia.com; This says where to send DMARC Aggregate Feedback reports to. Be warned that this can be a lot of... stuff. https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-rua Include ruf=mailto:hostmaster@linuxmafia.com; This says where to send failure/forensic reports, which are much more detailed than are DMARC Aggregate reports. Only a few mail senders issue those. Prepare to revise/lose this if I get swamped with reports. https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-ruf Omit rf=$THING (report format), because there's only one format (Authentication Failure Reporting Format = AFRF) so far, and it's default, making this tag so far pointless. https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-report-format Include ri=604800; report interval (default 86400 = 1 day), so that reporting sites send me aggregate reports every 7 days rather than daily. https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-report-interval Include pct=100; Means apply the declared policy to mail purporting to be mine 100% of the time. Since I'm saying "none" for now, this will matter really only when I shift to p=quarantine; or p=reject; . https://mxtoolbox.com/dmarc/details/dmarc-tags/dmarc-percentage Results in: _dmarc.linuxmafia.com 300 IN TXT "v=DMARC1; p=none; sp=none; rua=mailto:hostmaster@linuxmafia.com; ruf=mailto:hostmaster@linuxmafia.com; fo=s; ri=604800; pct=100" 7. How about Y'all? What are you guys doing about the problem?

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Feb '24

01 Feb '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-02-01 499 229 33 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

BALUG: Lists, stats, etc.
by Michael Paoli 01 Jan '24

01 Jan '24

dates, lists, number of members: YYYY-MM-DD announce talk admin 2024-01-01 497 227 31 2023-12-01 497 227 32 2023-11-01 496 249 32 2023-10-01 496 248 32 2023-09-01 497 248 32 2023-08-01 498 248 32 2023-07-01 500 248 32 2023-06-01 501 249 32 2023-05-01 501 249 32 2023-04-01 501 249 32 2023-03-01 501 249 32 2023-02-01 501 249 32 2023-01-01 500 249 32 2022-12-01 520 249 32 2022-11-01 564 249 32 2022-10-01 589 249 32 2022-09-01 589 249 33 2022-08-01 616 249 33 2022-07-01 834 260 35 2022-06-01 832 259 35 2022-05-01 832 259 35 2022-04-01 832 259 35 2022-03-01 833 259 35 2022-02-01 833 259 35 2022-01-01 833 258 35 2021-12-01 832 257 35 2021-11-01 831 257 35 2021-10-01 832 257 35 2021-09-01 832 257 35 2021-08-01 832 257 35 2021-07-01 832 257 35 2021-06-01 832 256 35 2021-05-01 833 257 35 2021-04-01 832 259 35 2021-03-01 833 259 35 2021-02-01 833 259 35 2021-01-01 833 259 35 2020-12-01 832 259 35 2020-11-01 833 260 35 2020-10-01 834 260 35 2020-09-01 835 260 35 2020-08-01 834 259 34 2020-07-01 834 266 34 2020-06-01 838 266 34 2020-05-01 839 267 34 2020-04-01 840 270 34 2020-03-01 840 271 34 2020-02-01 841 271 34 2020-01-01 841 271 34 2019-12-01 841 271 34 2019-11-01 840 271 34 2019-10-01 842 271 34 2019-09-01 844 272 34 2019-08-01 847 272 34 2019-07-01 852 272 36 2019-06-01 854 273 37 2019-05-01 856 272 38 2019-04-01 853 273 38 2019-03-01 851 273 38 2019-02-01 853 273 38 2019-01-01 856 274 38 2018-12-01 858 274 38 2018-11-01 861 274 39 2018-10-02 862 274 39 2018-09-01 864 274 38 2018-07-28 866 278 38 2018-06-08 870 282 38 2018-04-28 875 282 38 2018-02-17 880 283 36 2017-11-04 883 284 36 2017-08-19 897 293 37 2017-07-01 897 297 38 2017-05-27 897 297 38 2017-05-16 897 296 38 2017-04-01 896 297 38 2017-03-30 885 297 38 2016-05-03 886 291 39 2016-04-03 887 290 39 2016-03-05 888 291 45 2016-01-05 887 295 45 2015-12-05 887 296 45 2015-11-07 887 301 45 2015-10-06 888 301 45 2015-09-05 887 301 45 2015-08-04 888 301 45 2015-07-03 888 300 45 2015-06-05 888 301 46 2015-05-02 885 298 45 2015-04-04 884 297 44 2015-03-07 886 298 44 2015-02-06 885 303 44 2015-01-07 885 304 45 2014-12-06 886 304 45 2014-11-01 884 302 45 2014-10-04 881 303 46 2014-09-06 878 309 44 2014-06-13 875 307 44 2014-05-02 874 306 44 2014-04-04 876 306 44 2014-03-01 876 306 43 2014-01-11 872 305 42 2013-10-05 854 293 40 2013-08-31 855 295 41 2013-07-20 852 297 40 2013-04-10 838 286 41 2013-03-03 841 289 41 2013-02-02 843 291 41 2012-12-15 845 310 41 2012-03-23 818 310 39 2012-02-01 813 307 40 2011-04-28 768 291 37 2011-02-27 762 288 36 2010-05-02 730 289 34 2010-04-01 727 291 33 2010-03-16 727 293 33 2009-12-16 716 290 33 2009-09-09 700 288 32 2009-03-27 677 287 29 2009-01-10 662 290 30 2008-08-17 635 290 29 2008-03-03 571 247 28 2008-01-02 337 260 28 2007-12-28 336 261 28 2007-09-03 264 258 27 2007-07-24 287 256 27 2007-06-17 280 249 27 references: http://www.balug.org/#Lists

1 0

← Newer
1
2
3
4
5
6
7
8
...
55
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

BALUG-Admin