March 2016 - Test - {{ block.super }

setting up the mailman-users@mailman3.org list
by Mark Sapiro 27 Mar '16

27 Mar '16

I think we are very close to going live with a mailman-users(a)mailman3.org list. I am comfortable that between Postorius and mailman shell I can create and configure the list. The HyperKitty issues that were blockers for me have been fixed. The one remaining blocker that I see[1] is that Google login doesn't work. This is reported here <https://gitlab.com/mailman/hyperkitty/issues/73>. Any ideas on that? [1] Steve has an issue trying to add a second address, but I am unable to duplicate that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 3

Re: Another try at USE_SSL = True
by Mark Sapiro 23 Mar '16

23 Mar '16

On 03/22/2016 06:07 PM, Mark Sapiro wrote: > Trying again. The last one actually succeeded in getting an archive url but got a 301 and then a 400 on the actual archiving. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 3

Re: What now -reply from web
by Mark Sapiro 21 Mar '16

21 Mar '16

On 03/20/2016 07:22 PM, mailman(a)mailman3.org wrote: > The last post with SSL = True and latest core still hits the same > underlying exception both in trying to get the archive URL and in > trying to archive the message. The core now handles these exceptions > and continues so the message goes to the list, but isn't archived and > has no archive headers. > > This is a post from hyperkitty which will probably be handled the > same, so we have to go back to SSL = False until we can fix the > certificate issue. Yes. Bottom line. With USE_SSL = True, core connects to hyperkitty via SSL to 127.0.0.1 and the certificates I installed don't include 127.0.0.1 in their domains, so urllib3 or requests (depending on where we're coming from) throws SSLError: hostname '127.0.0.1' doesn't match either of 'lists.mailman3.org', 'mirror.list.org', 'mirror.mailman3.org'. The core now handles the exceptions and the message is ultimately delivered but not archived. regardless of where it originated. We're back to USE_SSL = False now so this post should be archived, albeit the archive URLs will have 127.0.0.1 ast the host and not lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 2

Baseline
by Playground for testing 21 Mar '16

21 Mar '16

I'm going to try a few config changes. This post is just to establish a baseline. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 7

Down time.
by Mark Sapiro 19 Mar '16

19 Mar '16

Later this evening (maybe March 19 02:00 UTC) I will be attempting to reconfigure things to use the gitlab master branches of MailmanClient, Postorius, HyperKitty and the HyperKitty-Mailman plugin in addition to using gitlab master branch of Mailman itself which is already the case. This will probably involve down time and/or anomalous behavior. You have been warned. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 2

Is there anybody out there?
by Florian Fuchs 17 Mar '16

17 Mar '16

Ping! Cheers, Florian

2 1

Test after second reboot
by Mark Sapiro 17 Mar '16

17 Mar '16

-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Test after reboot
by Mark Sapiro 17 Mar '16

17 Mar '16

-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

posting here
by Mark Sapiro 15 Mar '16

15 Mar '16

This is a list post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Test March 2016