- Selenetest - Kingdom of Lochac

Testing lists with bouncing addresses
by Lochac Masonry Deputy 10 Mar '22

10 Mar '22

This message is to test what happens when I subscribe some non-existent addresses to the list then try to send e-mail to it. Real e-mail addresses may ignore this message. This message is to test what happen= s when I subscribe some non-existent addresses to the list then try to send= e-mail to it. Real e-mail addresses may ignore this message. =

1 0

Welcome to Mailman3
by Lochac Masonry Deputy 09 Mar '22

09 Mar '22

Greetings Selene Test Team. Here are some notes about this list to get us started. General information: • The web interface is at https://mailman.lochac.sca.org • The Mailman site administrator is mailman3(a)lochac.sca.org, which is currently an alias for my personal address • The Selenetest list administrators are mailman3(a)lochac.sca.org and masonry(a)lochac.sca.org How It Works: Mailman3 is made up of two systemd services, mailman3 and mailman3-web, with configuration in /etc/mailman3/mailman.cfg and /etc/mailman3/mailman-web.py, respectively. I have configured mailman3 so that it starts only the two essential ‘runners’: the one that accepts mail from postfix (‘lmtp’) and the one that implements the REST API (‘rest’). The other runners, which process mail, are run from cron jobs defined in /etc/cron.d/mailman3: • The ‘in’, ‘pipeline’, and ‘out’ queues are cleared every ten minutes. These check incoming mail, perform any necessary transformations on it, and send it out again, respectively. • The ‘command’ and ‘virgin’ queues are also cleared every ten minutes. The first processes requests sent to listname-join@lochac, listname-leave@lochac, etc., while the second is where Mailman inserts its own messages (moderation requests, etc.) into the system. • The ‘retry’ and ‘task’ queues are cleared every hour • The ‘archive’, ‘bounces’ and ‘digest’ queues are cleared every evening • I have disabled the ‘nntp’ runner altogether since no one is using NNTP as far as I know A homebrewed Python script in /var/lib/mailman3/bin/cron-runner.py processes the queues. The script only starts the runner if mail is actually in the queue, and then only makes one pass over the queue. I wrote this script because Mailman’s own ‘runner’ script can only run indefinitely (which uses huge amounts of memory) or process one message at each invocation (which is painful). One upshot of this for ordinary people is that mail to a list may take up to 10-15 minutes to be sent out again, and archives are only updated once per day. This can of course be changed by changing the cron configuration. Log files are in /var/log/mailman3. The main log is mailman3.log. The web service has another log /var/log/mailman3/web/mailman3-web.log, which is different to the Apache log. The Apache logs are /var/log/apache/mailman.*.log.. Manual operation: Mailman3 has a single command-line tool, called ‘mailman’ (no 3), that performs more or less the functions of the scripts in /usr/lib/mailman/bin in Mailman2. For most purposes, it should be run as the ‘list’ user, otherwise it may create files or processes owned by root that other Mailman3 processes can’t work with, e.g. $ sudo -u list mailman info # displays version information To process a queue manually, invoke /var/lib/mailman/bin/cron-runner with the queue’s name as the first argument, e.g. $ sudo -u list /var/lib/mailman/bin/cron-runner in # process all incoming mail If mail cannot be processed due to an error (e.g. Python throws an exception), Mailman3 puts it in the ‘shunt’ queue. Once the error has been fixed, use the ‘unshunt’ command to get the mail going again: $ sudo -u list mailman unshunt Other resources: • https://www.list.org • https://mailman.readthedocs.io Ælfred Greetings Selene Test Team. Here are some notes about this list to get= us started. **General information:** * The web interface is at [https://mailman.lochac.sca.org](=3D"https://mailman.lochac.sca.org") = * The Mailman site administrator is [mailman3(a)lochac.sca.org](=3D"mailto:mailman3@lochac.sca.org"), which is c= urrently an alias for my personal address * * The =E2=80=98in=E2=80=99, =E2=80=98pipeline=E2=80=99= , and =E2=80=98out=E2=80=99 queues are cleared every ten minutes. These che= ck incoming mail, perform any necessary transformations on it, and send it = out again, respectively. * The =E2=80= =98command=E2=80=99 and =E2=80=98virgin=E2=80=99 queues are also cleared ev= ery ten minutes. The first processes requests sent to listname-join@lochac,= listname-leave@lochac, etc., while the second is where Mailman inserts its= own messages (moderation requests, etc.) into the system. * The =E2=80=98retry=E2=80=99 and =E2=80=98task=E2=80=99= queues are cleared every hour * The =E2= =80=98archive=E2=80=99, =E2=80=98bounces=E2=80=99 and =E2=80=98digest=E2=80= =99 queues are cleared every evening * I h= ave disabled the =E2=80=98nntp=E2=80=99 runner altogether since no one is u= sing NNTP as far as I know A homebrewed Pytho= n script in /var/lib/mailman3/bin/cron-runner.py processes the queues. The = script only starts the runner if mail is actually in the queue, and then on= ly makes one pass over the queue. I wrote this script because Mailman=E2=80= =99s own =E2=80=98runner=E2=80=99 script can only run indefinitely (which u= ses huge amounts of memory) or process one message at each invocation (whic= h is painful). One upshot of this for ordinary people is that mail to a list may tak= e up to 10-15 minutes to be sent out again, and archives are only updated o= nce per day. This can of course be changed by changing the cron configurati= on. Log f= iles are in /var/log/mailman3. The main log is mailman3.log. The web servic= e has another log /var/log/mailman3/web/mailman3-web.log, which is differen= t to the Apache log. The Apache logs are /var/log/apache/mailman.*.log. = **Manual op= eration:** Mailman3 has a single command-line tool, called =E2=80=98mai= lman=E2=80=99 (no 3), that performs more or less the functions of the scrip= ts in /usr/lib/mailman/bin in Mailman2. For most purposes, it should be run= as the =E2=80=98list=E2=80=99 user, otherwise it may create files or proce= sses owned by root that other Mailman3 processes can=E2=80=99t work with, e= .g. $ sudo -u list mailman info=C2=A0=C2=A0 # displays = version information To process a queue manually, invoke /var/lib/mailman/bin/cron-= runner with the queue=E2=80=99s name as the first argument, e.g. $ sudo -u list /var/lib/mailman/bin/cron-runner in=C2=A0=C2=A0=C2= =A0=C2=A0 # process all incoming mail If mail cannot be processed due to an error (e= .g. Python throws an exception), Mailman3 puts it in the =E2=80=98shunt=E2= =80=99 queue. Once the error has been fixed, use the =E2=80=98unshunt=E2=80= =99 command to get the mail going again: = ; $ sudo -u list= mailman unshunt = **Other resources:** = * https://www.list.org * [https://mailman.= readthedocs.io](3D"https://mailman.readthedocs.io") =C2=A0=C2=A0=C2=A0 =C3=86lfred =

1 0

Testing message footer
by Ælfred se leof 08 Mar '22

08 Mar '22

The footer should appear right here: The footer should appear right here:

1 0

Re: Testing HyperKitty configuration
by Ælfred se leof 06 Mar '22

06 Mar '22

And that message was supposed to be sent via the list so that I could see if I'd fixed the archiving problem. ------ Original Message ------ From: "Ælfred se leof" <aelfred(a)nps.id.au> To: "Jeremy Gregson" <jeremy.gregson(a)gmail.com> Sent: 6/03/2022 12:00:12 PM Subject: Re: [Selenetest] Testing HyperKitty configuration >The problem with "Forbidden" is that it isn't much more helpful than >"bad kitty". > >I think it's because the HyperKitty API was only accepting connections >from localhost but Mailman Core is connecting from 163.53.249.53. So >has been going through but not getting archived. > >------ Original Message ------ >From: "Jeremy Gregson" <jeremy.gregson(a)gmail.com> >To: "Ælfred se leof" <aelfred(a)nps.id.au> >Sent: 6/03/2022 11:03:41 AM >Subject: Re: [Selenetest] Testing HyperKitty configuration > >>Bad kitty? >> >>On Sun, 6 Mar 2022, 10:59 am Ælfred se leof, <aelfred(a)nps.id.au> >>wrote: >>>To which the system says, >>> >>>HyperKitty failure on >>>http://mailman.lochac.sca.org/hyperkitty/api/mailman/urls: >>><html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> >>>------ Original Message ------ >>>From: "Jeremy Gregson" <jeremy.gregson(a)gmail.com> >>>To: "Ælfred se leof" <aelfred(a)nps.id.au> >>>Sent: 6/03/2022 10:56:36 AM >>>Subject: Re: [Selenetest] Testing HyperKitty configuration >>> >>>>I don't know if it is ironic or fitting, but as I opened this >>>>email, a hyperkitty jumped onto my lap. >>>> >>>>On Sun, 6 Mar 2022, 9:43 am Ælfred se leof via Selenetest, >>>><selenetest(a)lochac.sca.org> wrote: >>>>>Test message to be archived >>>>> >>>>>_______________________________________________ >>>>>Selenetest mailing list -- selenetest(a)lochac.sca.org >>>>>To unsubscribe send an email to selenetest-leave(a)lochac.sca.org And that message was supposed to be sent via t= he list so that I could see if I'd fixed the archiving problem. \------ Original Message ------ From: "=C3=86lfred se leof" <[a= elfred(a)nps.id.au](3D"mailto:aelfred@nps.id.au")> To: "Jeremy Gregson" <[j= eremy.gregson(a)gmail.com](3D"mailto:jeremy.gregson@gmail.com")> Sent: 6/03/2022 12:00:12 PM Subject: Re: [Selenetest] Testing HyperKitty configuration <= br /> > The problem with "Forbidden" is that it isn't much more helpful than "= bad > kitty". > > > > > I think it's because the HyperKitty= API was only accepting connections from > localhost but Mailman Core is conne= cting from 163.53.249.53. So has been > going through but not getting archive= d. > > > > > \------ Original Message ------ > > From: "Jeremy Gregson" > <[jeremy.gregson(a)gmail.com](3D"mailto:jeremy.gregson@gmail.com"=)> > > To: "=C3=86lfred se leof" <[ael= > fred(a)nps.id.au](3D"mailto:aelfred@nps.id.au")> > > Sent: 6/03/2022 11:03:41 AM > > Subject: Re: [Selenetest] Testing HyperKitty configuration > > <= br /> > >> Bad kitty? >> >> > >> >> On Sun, 6 Mar 2022, 10:59 am =C3=86lfred se l= eof, <[aelfred(a)nps.id.au](3D"mailto:aelfred@nps.id.au")> wro= te: > >> >>> To which the system = says, >>> >>> > >>> >>> HyperKitty failure on [http:= //mailman.lochac.sca.org/hyperkitty/api/mailman/urls](3D"http://m=): <html><t= itle>Forbidden</title><body> > =C2=A0 =C2=A0=C2=A0 =C2=A0= =C2=A0 =C2=A0=C2=A0 =C2=A0=C2=A0 =C2=A0 > <h1>Access is forbidden</h= 1></body></html> (403) >>> >>> > >>> >>> \------ Original Message ------ >>> >>> From: "Jeremy Gregson" <[jeremy.gregson(a)gmail.com](3D"mailto:jeremy.gregson@gmail.com")> >>> >>> To: "=C3=86lfred se leof" <[aelfred(a)nps.id.au](3D"mailto:aelfred@nps.id.au")> >>> >>> Sent: 6/03/2022 10:56:36 AM >>> >>> Subject: Re: [Selenetest] Testing HyperKitty configuration >>> >>> <= br /> >>> >>>> I don't know if it is ironic or fitting,=C2=A0 but as I o= pened this email,=C2=A0 a hyperkitty jumped onto my lap. >>>> >>>> > >>>> >>>> On Sun, 6 Mar 202= 2, 9:43 am =C3=86lfred se leof via Selenetest, <[selenetest(a)lochac.sca.org](3D"mailto:selene=)> w= rote: > >>>> >>>>> Test message to be archived= > > _______________________________________________ > Selenetest mailing list -- > [selenetest(a)lochac.sca.org](3D"mailto:selenetest@lochac.sca.org") > To unsubscribe send an email to [selenetest- > leave(a)lochac.sca.org](3D"mailto:selenetest-leave@lochac.s=)

1 0

Testing HyperKitty configuration
by Ælfred se leof 06 Mar '22

06 Mar '22

Test message to be archived Test message to be archived

1 1

Testing Mailman2
by Lochac Masonry Deputy 06 Feb '22

06 Feb '22

Still working.

1 0

FW: Testing Mailman2 again
by Lochac Masonry Deputy 05 Feb '22

05 Feb '22

Testing I haven’t broken anything From: Lochac Masonry Deputy Sent: Saturday, 5 February 2022 3:21 PM To: nico--- via Selenetest Subject: Testing Mailman2 again Now with Mailman3 using a virtual domain.

1 0

Re: [Selenetest] Testing Mailman2
by Lochac Masonry Deputy 05 Feb '22

05 Feb '22

I _think_ I’ve got this working now on my test server so that Mailman2 and Mailman3 will work at the same time. If all goes according to plan I’ll migrate this list to Mailman3 later this weekend. Expect more test traffic. From: Jeremy Gregson Sent: Saturday, 5 February 2022 11:04 AM To: 'Lochac Masonry Deputy' Subject: RE: [Selenetest] Testing Mailman2 I got it. -----Original Message----- From: Selenetest <selenetest-bounces(a)lochac.sca.org> On Behalf Of Lochac Masonry Deputy via Selenetest Sent: Saturday, 5 February 2022 10:44 AM To: nico--- via Selenetest <selenetest(a)lochac.sca.org> Subject: [Selenetest] Testing Mailman2 Testing

1 0

Testing Mailman2
by Lochac Masonry Deputy 05 Feb '22

05 Feb '22

Testing

1 0

FW: checking a PDF attachment
by nico＠jeremygregson.com 09 Mar '21

09 Mar '21

..and trying again From: nico(a)jeremygregson.com <nico(a)jeremygregson.com> Sent: Tuesday, 9 March 2021 6:32 PM To: 'selenetest(a)lochac.sca.org' <selenetest(a)lochac.sca.org> Subject: FW: checking a PDF attachment Repeating the exercise with the message size limit removed. From: nico(a)jeremygregson.com <mailto:nico@jeremygregson.com> <nico(a)jeremygregson.com <mailto:nico@jeremygregson.com> > Sent: Tuesday, 9 March 2021 6:29 PM To: 'selenetest(a)lochac.sca.org' <selenetest(a)lochac.sca.org <mailto:selenetest@lochac.sca.org> > Subject: checking a PDF attachment This is testing to confirm that I'm giving someone else correct advice about how to enable PDF attachments on a different mailing list.

1 0