Testing the MM3 overload-sig
I've just subscribed to the MM3 overload-sig. The archives are empty, presumably because they haven't been migrated from MM2 yet. I'm curious whether this message will appear in the MM3 or the MM2 version of the list -- or both? --Guido
Interesting. I sent this through the MM3 web UI, but apparently what that form does is just send email to overload-sig@python.org, which is routed to the MM2 instance. Oh well. Now I know. On Sun, Jul 31, 2016 at 5:49 PM, Guido van Rossum <gvanrossum@gmail.com> wrote:
I've just subscribed to the MM3 overload-sig. The archives are empty, presumably because they haven't been migrated from MM2 yet. I'm curious whether this message will appear in the MM3 or the MM2 version of the list -- or both?
--Guido _______________________________________________ Overload-sig mailing list Overload-sig@python.org https://mail.python.org/mailman/listinfo/overload-sig
-- --Guido van Rossum (python.org/~guido)
On Jul 31, 2016, at 05:51 PM, Guido van Rossum wrote:
Interesting. I sent this through the MM3 web UI, but apparently what that form does is just send email to overload-sig@python.org, which is routed to the MM2 instance. Oh well. Now I know.
I just tried playing with the test list and I noticed a misconfiguration, which I've forwarded to postmasters. I know Mark is away for a bit so this may take a little bit to get resolved. The other interesting thing is that it *is* possible to post messages to a mailing list through the REST API (and command line FWIW); it doesn't have to go through the LMTP/SMTP interface. I actually thought that HyperKitty (i.e. through-the-web) posts would use the REST API but it apparently doesn't, leading to the misconfiguration delivery failure I noticed. I'll have to ask the HK folks why that is. Cheers, -Barry
participants (2)
-
Barry Warsaw -
Guido van Rossum