A non-ASCII character: Æ
“Smart” quotes and ‘apostrhophes’
A non-ASCII character: =C3=86
=E2=80=9CSmart= =E2=80=9D quotes and =E2=80=98apostrhophes=E2=80=99
=
Some bold and italic text.
Some
Dot
Points
A non-ASCII character: Æ
“Smart” quotes and greengrocers’ apostrophe’s.
.0pt;word-wrap:break-word">
Some bo= ld =C2=A0and italic text.
=C2=A0
>
">Some
>
">Dot=
">Points
:p>
=C2=A0
A non-ASCI= I character: =C3=86
=C2=A0
=E2=80=9CS= mart=E2=80=9D quotes and greengrocers=E2=80=99
apostrophe=E2=80=99s.
Let me know if I’ve missed anything. Cc’d to Sorle because Bordescros is the fist real list to be migrated. – Ælfred
Migration
• The list will be unavailable for a short period (1-2 hours) while its data is migrated from Mailman2 to Mailman3. Messages sent to the list during this period may be lost or bounced.
• After migration, list subscribers may continue using the list as before without taking any specific action; however, see additional information under “for list members” below.
• The migration process will preserve the list membership and list archives, but the archives will move to a new location with a new more featureful interface.
• The web interface for mailing lists (including archives and subscription management) will move to https://mailman.lochac.sca.org
For list members
• The day-to-day behaviour of the list will not change.
• Instead of having a separate password for each list, list members can manage their subscription settings for all lists by creating an account at https://mailman.lochac.sca.org.
• To access functions requiring a log-in, list members must create a new account even if they’re already subscribed to one or more lists. The new account should be automatically connected to all mailing lists to which the associated e-mail address is subscribed.
• List subscribers can also manage their subscription by sending e-mail to listname-request(a)lochac.sca.org, e.g. lochac-announce-request(a)lochac.sca.org for the Lochac-Announce list. Send a message with body ‘help’ for instructions. This doesn’t require an account.
For list administrators
• List administration is now done through your account at https://mailman.lochac.sca.org. This is the same account as the one you will use for managing your own list subscriptions.
• The Mailman3 site administrator is mailman3(a)lochac.sca.org (presently Ælfred se leof). Please direct requests for new lists, enquiries about the list administrator interface, etc. to this address.
= Let me know if I=E2=80=99ve missed anything. Cc=E2=80=99d to Sorle because =
Bordescros is the fist real list to be migrated. =E2=80=93 =C3=86lfred
<= p class=3DMsoNormal>
**Migration <= o:p>**
* The list will be unavailable for a short peri= od (1-2 hours) while its data is migrated from Mailman2 to Mailman3. Messag= es sent to the list during this period may be lost or bounced.
* After migration, list subscribers may continue using the list as bef= ore without taking any specific action; however, see additional information= under =E2=80=9Cfor list members=E2=80=9D below.
* The m= igration process will preserve the list membership and list archives, but t= he archives will move to a new location with a new more featureful interfac= e.
* The web interface for mailing lists (including archiv= es and subscription management) will move to [https://mailman.lochac.sca.org](3D"https://mailman.loc=)
**For list member= s**
* The day-to-day behaviour of the list will n= ot change.
* Instead of having a separate password for eac= h list, list members can manage their subscription settings for all lists b= y creating an account at [https:/= /mailman.lochac.sca.org](3D"https://mailman.lochac.sca.org"). =C2=A0
* To access functions = requiring a log-in, list members must create a new account even if they=E2= =80=99re already subscribed to one or more lists. The new account should be= automatically connected to all mailing lists to which the associated e-mai= l address is subscribed.
* List subscribers can also mana= ge their subscription by sending e-mail to listname-request(a)lochac.sca.org,= e.g. lochac-announce-request(a)lochac.sca.org for the Lochac-Announce list. = Send a message with body =E2=80=98help=E2=80=99 for instructions. This does= n=E2=80=99t require an account.
**For list administrators**
* List administration is now done through your account = at [https://mailman.lochac.sca.or= g](3D"https://mailman.lochac.sca.org"). This is the same account as the one you will use for managing your o= wn list subscriptions.
* The Mailman3 site administrator i= s mailman3(a)lochac.sca.org (presently =C3=86lfred se leof). Please direct re= quests for new lists, enquiries about the list administrator interface, etc= . to this address.
=
Yep, one of my tasks for this week is to write up some information about What Will Change for list subscribers and administrators. I’ll post a draft to this list when it’s ready for comment. I’ve already posted a heads up to the Kingdom Officers.
I can’t see any way of subscribing users from the command line but Mailman has a REST API for such things: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/….
The base URL is http://localhost:8001 but can be changed if necessary. The credentials are in /etc/mailman3/mailman-web.py (not posted to the list because the archives are public).
Alternatively, sending e-mails to listname-request(a)lochac.sca.org might work: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…
There’s probably also a way of doing it through the Mailman shell (sudo -u list mailman shell) but that would require connecting the Registry to Python.
Ælfred
From: nico(a)jeremygregson.com
Sent: Thursday, 10 March 2022 9:08 AM
To: 'Lochac Masonry Deputy'
Subject: RE: [Selenetest] Welcome to Mailman3
Okay - a question/observation. I'm getting the test emails successfully, because a couple of my email addresses are in that list. But when I go to the web interface to try to sign in, I discovered that I don't have a user account with Mailman3. I had to create one, with my already-subscribed address linked to it.
Now, if this only affects people who want to go to the web interface and administer a list, or browse the archives, it is not a huge deal for the majority of the population. Most people subscribed to lochac-announce will never know or care. But it is a concept which will need to be explained to list admins, at least. Ideally, modifying the template on the web home page to explain what's going on would be nice.
Meanwhile - I need to check whether mailman3 supports the same command-line process for adding a subscriber to a list. At the moment, when someone joins the SCA, the membership form includes a tickbox asking if they want to be subscribed to lochac-announce. And if they do, it gets done for them automatically behind the scenes, without them having to go through a separate manual process. I'd like to keep doing that, if I can.
So - small-scale testing on lesser lists progresseth nicely, but I think some change management for the one big list is probably in order.
Cheers,
Nico
-----Original Message-----
From: Lochac Masonry Deputy via Selenetest <selenetest(a)lochac.sca.org>
Sent: Wednesday, 9 March 2022 7:26 AM
To: nico--- via Selenetest <selenetest(a)lochac.sca.org>
Subject: [Selenetest] Welcome to Mailman3
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
Yep, = one of my tasks for this week is to write up some information about
What Wi= ll Change for list subscribers and administrators. I=E2=80=99ll post
a draf= t to this list when it=E2=80=99s ready for comment. I=E2=80=99ve
already po= sted a heads up to the Kingdom Officers.
&nbs;= p;
I can=E2=80=99t see any way of subscribing= users from the command line but
Mailman has a REST API for such things:
https://docs.mailman3.org/projects/mailman/en/latest/sr=
c/mailman/rest/docs/rest.html.
The base URL is [http://localhost:8001](3D"http://localhost:8001"=) but can be
changed if necessary. The credentials= are in /etc/mailman3/mailman-web.py
(not posted to the list because the ar= chives are public).
Alternatively, sending e-mails to listname-request(a)lochac.sca.= org might
work: [https://docs.mailman3.org/pro=
jects/mailman/en/latest/src/mailman/commands/docs/commands.html](3D"https://docs.mailman3.org/projects/mailman/en/la=)
There=E2=80=99s= probably also a way of doing it through the Mailman shell
(sudo -u list ma= ilman shell) but that would require connecting the Registry
to Python.
<= p class=3DMsoNormal>
=C2=A0=C2=A0=C2=A0=C2=A0=C3= =86lfred
**F= rom:**[nico@jeremygregson.com
**Sent:** Thursday, 10 March 2022 9:08 AM
**To:**['Lochac Masonry Deputy'](3D=)
**Subject: =** RE: [Selenetest] Welcome to Mailman3
Okay - a question/observation.=C2=A0 = I'm getting the test emails
successfully, because a couple of my email addr= esses are in that list.=C2=A0
But when I go to the web interface to try to = sign in, I discovered that I
don't have a user account with Mailman3.=C2=A0= I had to create one, with my
already-subscribed address linked to it.
<= p class=3DMsoNormal>
Now, if this = only affects people who want to go to the web interface and
administer a li= st, or browse the archives, it is not a huge deal for the
majority of the p= opulation.=C2=A0 Most people subscribed to lochac-announce
will never know = or care.=C2=A0 But it is a concept which will need to be
explained to list = admins, at least.=C2=A0 Ideally, modifying the template on
the web home pag= e to explain what's going on would be nice.
&n;= bsp;
Meanwhile - I need to check whether mail= man3 supports the same command-line
process for adding a subscriber to a li= st.=C2=A0 At the moment, when someone
joins the SCA, the membership form in= cludes a tickbox asking if they want to
be subscribed to lochac-announce.= =C2=A0 And if they do, it gets done for
them automatically behind the scene= s, without them having to go through a
separate manual process.=C2=A0 I'd l= ike to keep doing that, if I can.
=
So - small-scale testing on lesser lists progresse= th nicely, but I think
some change management for the one big list is proba= bly in order.
Cheers,
Nico
&nbs;= p;
= \-----Original Message-----
From: Lochac Masonry Dep= uty via Selenetest <selenetest(a)lochac.sca.org>
Sent: Wednesday, 9 March 2022 7:26 AM
To: nico--= \- via Selenetest <selenetest(a)lochac.sca.org>
= Subject: [Selenetest] Welcome to Mailman3
&nbs;= p;
Greetings Selene Test Team. Here are some = notes about this list to get us
started.
= ;
General information:
=E2=80=A2 The web interface is at https://mailman.lochac.sca.org =E2=80= =A2
The Mailman site administrator is mailman3(a)lochac.sca.org, which is cur=
rently an alias for my personal address =E2=80=A2 The Selenetest list admin=
istrators are mailman3(a)lochac.sca.org and masonry(a)lochac.sca.org
How It Works:
<= p class=3DMsoNormal>
Mailman3 is m= ade up of two systemd services, mailman3 and mailman3-web, with
configurati= on in /etc/mailman3/mailman.cfg and /etc/mailman3/mailman-web.py,
respectiv= ely.
I ha= ve configured mailman3 so that it starts only the two essential
=E2=80=98ru= nners=E2=80=99: the one that accepts mail from postfix
(=E2=80=98lmtp=E2=80= =99) and the one that implements the REST API
(=E2=80=98rest=E2=80=99). The= other runners, which process mail, are run from
cron jobs defined in /etc/= cron.d/mailman3:
=E2=80=A2 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 check
incoming mail, perform any necessary transfo= rmations on it, and send it out
again, respectively.
=E2=80=A2 The =E2=80=98command=E2=80=99 and =E2=80=98virgin=E2=80=99 queu= es
are also cleared every ten minutes. The first processes requests sent to=
listname-join@lochac, listname-leave@lochac, etc., while the second is whe= re
Mailman inserts its own messages (moderation requests, etc.) into the sy=
stem.
=E2=80=A2 The =E2=80=98retry=E2=80=99 and =E2= =80=98task=E2=80=99 queues are
cleared every hour =E2=80=A2 The =E2=80=98ar= chive=E2=80=99,
=E2=80=98bounces=E2=80=99 and =E2=80=98digest=E2=80=99 queu= es are cleared
every evening =E2=80=A2 I have disabled the =E2=80=98nntp=E2= =80=99 runner
altogether since no one is using NNTP as far as I know A home= brewed 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 M= ailman=E2=80=99s
own =E2=80=98runner=E2=80=99 script can only run indefinit= ely (which uses
huge amounts of memory) or process one message at each invo= cation (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 on= ly 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. Th= e 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/mailma=
n.*.log..
Manual operation:
Mailman3 has a single command-line tool, called =E2=80=98mailman= =E2=80=99
(no 3), that performs more or less the functions of the scripts i= n
/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 processes= owned
by root that other Mailman3 processes can=E2=80=99t work with, e.g.<= /p>
$ sudo -u= list mailman info=C2=A0=C2=A0 # displays version information
To process a queue m= anually, invoke /var/lib/mailman/bin/cron-runner with
the queue=E2=80=99s n= ame 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 unsh= unt
Other= resources:
=E2=80=A2 https://www.list.org
=E2=80=A2 https://mailman.readthedocs.io
=C2=A0=C2=A0=C2=A0 =C3=86l= fred
=
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.
=
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
=
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=)
