From barry at list.org  Fri Dec  2 11:07:24 2016
From: barry at list.org (Barry Warsaw)
Date: Fri, 2 Dec 2016 11:07:24 -0500
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
Message-ID: <20161202110724.6b00dde3@subdivisions.wooz.org>

Hello Mailman 3 users and developers!

It's been a long slog but I think we are finally ready to begin the release
process for Mailman 3.1.  I am pretty happy about the state of the Core, and
Florian is going to do some more integration testing with HyperKitty and
Postorius.  We still have a few issues and a merge proposal or two to address,
but I am planning to spin a beta of Core this weekend to facilitate testing.

Here is the Core's 3.1 milestone page:

https://gitlab.com/mailman/mailman/milestones/2

If your favorite issue or merge request isn't on that list, please do get in
touch.  Otherwise it will be deferred to 3.2.  I'm also not entirely promising
I'll get to all of these; I really want to release 3.1 in 2016 so if we run
out of time, it will get deferred.

Here's the project-wide list of 3.1 issues:

https://gitlab.com/groups/mailman/issues?scope=all&state=opened&utf8=%E2%9C%93&milestone_title=3.1

and merge requests:

https://gitlab.com/groups/mailman/merge_requests?scope=all&state=opened&utf8=%E2%9C%93&milestone_title=3.1

Except that HyperKitty isn't on this list.

Please do test whatever you can and let us know how it goes.

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161202/609f04be/attachment.sig>

From nikhil684 at gmail.com  Sat Dec  3 02:55:17 2016
From: nikhil684 at gmail.com (Nikhil Rayaprolu)
Date: Sat, 3 Dec 2016 13:25:17 +0530
Subject: [Mailman-Developers] Whoosh Error during installation of hyperkitty
Message-ID: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>

Hello I am new to the Mailman community and on my try to contribute for
Mailman,I started installing all packages . For Hyperkitty I followed
https://hyperkitty.readthedocs.io/en/latest/development.html . Everything
went fine without any errors but on accessing the hyperkitty on my browser
, it shows me an error stating "A server error occurred.  Please contact
the administrator."
and on the terminal the last 3 lines shows

File
"/home/nikhil/dev/mailman/venv2/local/lib/python2.7/site-packages/django_haystack-2.5.1-py2.7.egg/haystack/backends/whoosh_backend.py",
line 30, in <module>
    raise MissingDependency("The 'whoosh' backend requires the installation
of 'Whoosh'. Please refer to the documentation.")
MissingDependency: The 'whoosh' backend requires the installation of
'Whoosh'. Please refer to the documentation.

Can any one help me with figuring out the cause for this error

From mark at msapiro.net  Sat Dec  3 10:48:57 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 3 Dec 2016 07:48:57 -0800
Subject: [Mailman-Developers] Whoosh Error during installation of
 hyperkitty
In-Reply-To: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>
References: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>
Message-ID: <984bae93-3065-3a63-e58d-96b37fcc7edf@msapiro.net>

On 12/02/2016 11:55 PM, Nikhil Rayaprolu wrote:
> Hello I am new to the Mailman community and on my try to contribute for
> Mailman,I started installing all packages . For Hyperkitty I followed
> https://hyperkitty.readthedocs.io/en/latest/development.html . Everything
> went fine without any errors but on accessing the hyperkitty on my browser
> , it shows me an error stating "A server error occurred.  Please contact
> the administrator."
> and on the terminal the last 3 lines shows
> 
> File
> "/home/nikhil/dev/mailman/venv2/local/lib/python2.7/site-packages/django_haystack-2.5.1-py2.7.egg/haystack/backends/whoosh_backend.py",
> line 30, in <module>
>     raise MissingDependency("The 'whoosh' backend requires the installation
> of 'Whoosh'. Please refer to the documentation.")
> MissingDependency: The 'whoosh' backend requires the installation of
> 'Whoosh'. Please refer to the documentation.



As it says at
<http://hyperkitty.readthedocs.io/en/latest/development.html#setting-up-the-databases>,
"HyperKitty?s default configuration uses the Whoosh backend, so if you
want to use that you just need to install the Whoosh Python library."

  pip install Whoosh

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

From f at florianfuchs.com  Sat Dec  3 15:22:44 2016
From: f at florianfuchs.com (Florian Fuchs)
Date: Sat, 3 Dec 2016 21:22:44 +0100
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <20161202110724.6b00dde3@subdivisions.wooz.org>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
Message-ID: <20161203202244.GA10744@linux.fritz.box>

On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote:
>Hello Mailman 3 users and developers!
>
>It's been a long slog but I think we are finally ready to begin the release
>process for Mailman 3.1.  I am pretty happy about the state of the Core, and
>Florian is going to do some more integration testing with HyperKitty and
>Postorius.  We still have a few issues and a merge proposal or two to address,

I did some manual integration testing today
(core+mailmanclient+postorius) which looked fine so far. I didn't get
to test HyperKitty and the bundler though, so any help testing those
would be very much appreciated. I will have some more time tomorrow.

I did all of my testing locally, which has some limitations. So I
started setting up a more realistic environment on one of my dev
machines. But I'm not done yet. Will report back when I'm done... ;-)

>but I am planning to spin a beta of Core this weekend to facilitate testing.

I think it's OK to put out a separate beta of the core, because the
version pulled from pypi will still be 3.0 if I'm not terribly mistaken.

For the real 3.1 we should probably do a coordinated release of all
components, once everything's tested a little more thoroughly.

Cheers
Florian

From barry at list.org  Sat Dec  3 16:30:05 2016
From: barry at list.org (Barry Warsaw)
Date: Sat, 3 Dec 2016 16:30:05 -0500
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <20161203202244.GA10744@linux.fritz.box>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <20161203202244.GA10744@linux.fritz.box>
Message-ID: <E2CEA585-E080-40A1-99B6-D8861A5C4D83@list.org>

Thanks for doing the testing Florian.  Btw I fixed the venv problem. It was actually a bug in one of the dependencies.  I have another small branch to land before spinning the beta but I think the MySQL docker image on ci is having some problems. I can't double check ATM.

Sent from my digital lollipop.

> On Dec 3, 2016, at 15:22, Florian Fuchs <f at florianfuchs.com> wrote:
> 
>> On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote:
>> Hello Mailman 3 users and developers!
>> 
>> It's been a long slog but I think we are finally ready to begin the release
>> process for Mailman 3.1.  I am pretty happy about the state of the Core, and
>> Florian is going to do some more integration testing with HyperKitty and
>> Postorius.  We still have a few issues and a merge proposal or two to address,
> 
> I did some manual integration testing today
> (core+mailmanclient+postorius) which looked fine so far. I didn't get
> to test HyperKitty and the bundler though, so any help testing those
> would be very much appreciated. I will have some more time tomorrow.
> 
> I did all of my testing locally, which has some limitations. So I
> started setting up a more realistic environment on one of my dev
> machines. But I'm not done yet. Will report back when I'm done... ;-)
> 
>> but I am planning to spin a beta of Core this weekend to facilitate testing.
> 
> I think it's OK to put out a separate beta of the core, because the
> version pulled from pypi will still be 3.0 if I'm not terribly mistaken.
> 
> For the real 3.1 we should probably do a coordinated release of all
> components, once everything's tested a little more thoroughly.
> 
> Cheers
> Florian


From terri at toybox.ca  Sat Dec  3 20:25:24 2016
From: terri at toybox.ca (Terri Oda)
Date: Sat, 3 Dec 2016 17:25:24 -0800
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <20161203202244.GA10744@linux.fritz.box>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <20161203202244.GA10744@linux.fritz.box>
Message-ID: <c4e90278-6b2d-aa1a-1a93-a257dc6c76be@toybox.ca>

On 2016-12-03 12:22 PM, Florian Fuchs wrote:
> I did some manual integration testing today
> (core+mailmanclient+postorius) which looked fine so far. I didn't get
> to test HyperKitty and the bundler though, so any help testing those
> would be very much appreciated. I will have some more time tomorrow.

I tried to do some testing based on these wiki instructions last weekend
https://wiki.list.org/HyperKitty/DevelopmentSetupGuide

and hit a "[Errno 61] Connection refused" issue when attempting to log 
in to Postorius.  I suspect it might be an issue with the mac, since 
googling for the error (it's a django one) seems to find a lot of people 
on macs with problems, but I didn't manage to narrow it down more than 
that to make a useful bug report.

I did set up a new linux install on another machine to work on next, 
though, so I may have something else to say on that front tomorrow.

  Terri



From mahim97 at gmail.com  Sun Dec  4 04:41:36 2016
From: mahim97 at gmail.com (Mahim Goyal)
Date: Sun, 4 Dec 2016 15:11:36 +0530
Subject: [Mailman-Developers] New to contributing field
Message-ID: <CALkB_YCvzofuremcKmDSTeX4ONvBhKfixqmWyW_9yYcDL8t1iQ@mail.gmail.com>

Hi,


I am a sophomore student at Indian Institute of Technology, Guwahati. I
would like to contribute to GNU Mailman. I am skilled at Python and C++/C.
I am also working on a college project based on Django and PostgreSQL. It
would be great to be directed to the right direction to start contributing
on the lines of GSoC 2017.

Thanks



Regards

Mahim Goyal

From simon.hanna at serve-me.info  Mon Dec  5 17:36:11 2016
From: simon.hanna at serve-me.info (Simon Hanna)
Date: Mon, 5 Dec 2016 23:36:11 +0100
Subject: [Mailman-Developers] Broken Gitlab Remote
Message-ID: <00ad1137-260d-d0d4-de9f-1daaeb7fc2a0@serve-me.info>

Hi,

Just a quick warning:

Do not use the online merge conflict resolver of GitLab. It can break
your remote copy of the repository in a way that you can't fix yourself.
And it looks like GitLab staff is not actually helping...

I broke my Postorius remote

https://gitlab.com/gitlab-com/support-forum/issues/1114

be careful,

Simon


From vince at vheuser.com  Mon Dec  5 19:38:16 2016
From: vince at vheuser.com (vince at vheuser.com)
Date: Mon, 5 Dec 2016 19:38:16 -0500
Subject: [Mailman-Developers] disregard...
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <20161203202244.GA10744@linux.fritz.box>
Message-ID: <E9053D821CC34A3DAC42F2FC387955E9@L520>

just verifying my ability post...
Since there is a human delay in approvals,
why wait until there is a need?

Vince

From nikhil684 at gmail.com  Tue Dec  6 04:15:26 2016
From: nikhil684 at gmail.com (Nikhil Rayaprolu)
Date: Tue, 6 Dec 2016 14:45:26 +0530
Subject: [Mailman-Developers] Whoosh Error during installation of
 hyperkitty
In-Reply-To: <984bae93-3065-3a63-e58d-96b37fcc7edf@msapiro.net>
References: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>
 <984bae93-3065-3a63-e58d-96b37fcc7edf@msapiro.net>
Message-ID: <CAKYz7F6KziFmSkZOmD8_aihm3waNTPEA4H+MyUq4oi30_Gg63A@mail.gmail.com>

I tried installing hyperkitty ,following the doc
https://hyperkitty.readthedocs.io/en/latest/development.html . but on
opening the localhost:8000 on browser.
NoReverseMatch at /

Reverse for 'hyperkitty.views.index.index' with arguments '()' and
keyword arguments '{}' not found. 0 pattern(s) tried: []

what would be causing the problem?

From nikhil684 at gmail.com  Tue Dec  6 05:37:15 2016
From: nikhil684 at gmail.com (Nikhil Rayaprolu)
Date: Tue, 6 Dec 2016 16:07:15 +0530
Subject: [Mailman-Developers] Error during installation of postorius
Message-ID: <CAKYz7F7aWtXA9Mm6JZBd6DOgMy1S9Se77uSBTFQ_smm5wXfDvw@mail.gmail.com>

I tried installing the postorius , and on logging in I am facing an error
"SMTPRecipientsRefused at /accounts/login/"
what would be causing the problem?
on reading the docs I found that we should add the settings of postfix in
mailman.cfg file.but even on adding the settings , problem persist.
Thank You
-Nikhil Rayaprolu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-12-06 15-58-59.png
Type: image/png
Size: 20548 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161206/bc960fce/attachment-0001.png>

From simon.hanna at serve-me.info  Tue Dec  6 06:17:08 2016
From: simon.hanna at serve-me.info (Simon Hanna)
Date: Tue, 6 Dec 2016 12:17:08 +0100
Subject: [Mailman-Developers] Error during installation of postorius
In-Reply-To: <CAKYz7F7aWtXA9Mm6JZBd6DOgMy1S9Se77uSBTFQ_smm5wXfDvw@mail.gmail.com>
References: <CAKYz7F7aWtXA9Mm6JZBd6DOgMy1S9Se77uSBTFQ_smm5wXfDvw@mail.gmail.com>
Message-ID: <2e2e6538-c9e7-2b57-ccc1-62d97eade05c@serve-me.info>

On 12/06/2016 11:37 AM, Nikhil Rayaprolu wrote:
> I tried installing the postorius , and on logging in I am facing an error
> "SMTPRecipientsRefused at /accounts/login/"
> what would be causing the problem?
> on reading the docs I found that we should add the settings of postfix in
> mailman.cfg file.but even on adding the settings , problem persist.
> Thank You
> -Nikhil Rayaprolu
You are trying to send actual mail through postfix, and postfix can't
send it because something is wrong about the address. If you are just
trying to get a development setup up and running use the python builtin
smtp server instead.
"sudo python -m smtpd -n -c DebuggingServer localhost:25"

From simon.hanna at serve-me.info  Tue Dec  6 06:51:16 2016
From: simon.hanna at serve-me.info (Simon Hanna)
Date: Tue, 6 Dec 2016 12:51:16 +0100
Subject: [Mailman-Developers] Whoosh Error during installation of
 hyperkitty
In-Reply-To: <CAKYz7F6KziFmSkZOmD8_aihm3waNTPEA4H+MyUq4oi30_Gg63A@mail.gmail.com>
References: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>
 <984bae93-3065-3a63-e58d-96b37fcc7edf@msapiro.net>
 <CAKYz7F6KziFmSkZOmD8_aihm3waNTPEA4H+MyUq4oi30_Gg63A@mail.gmail.com>
Message-ID: <8140af7c-e827-15e6-9914-e9bf2b555cdb@serve-me.info>

On 12/06/2016 10:15 AM, Nikhil Rayaprolu wrote:
> I tried installing hyperkitty ,following the doc
> https://hyperkitty.readthedocs.io/en/latest/development.html . but on
> opening the localhost:8000 on browser.
> NoReverseMatch at /
>
> Reverse for 'hyperkitty.views.index.index' with arguments '()' and
> keyword arguments '{}' not found. 0 pattern(s) tried: []
>
> what would be causing the problem?
Apply this patch until it gets merged into master
https://gitlab.com/mailman/hyperkitty/merge_requests/42

From nikhil684 at gmail.com  Tue Dec  6 07:18:03 2016
From: nikhil684 at gmail.com (Nikhil Rayaprolu)
Date: Tue, 6 Dec 2016 17:48:03 +0530
Subject: [Mailman-Developers] Whoosh Error during installation of
 hyperkitty
In-Reply-To: <8140af7c-e827-15e6-9914-e9bf2b555cdb@serve-me.info>
References: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>
 <984bae93-3065-3a63-e58d-96b37fcc7edf@msapiro.net>
 <CAKYz7F6KziFmSkZOmD8_aihm3waNTPEA4H+MyUq4oi30_Gg63A@mail.gmail.com>
 <8140af7c-e827-15e6-9914-e9bf2b555cdb@serve-me.info>
Message-ID: <CAKYz7F6PafJKyGEGCYj9zEWZ5w0v7FY52_uL=+6ZWD0JupxnPA@mail.gmail.com>

Thank you Simon,
your solution to the previous issue has solved it but unfortunately a new
error has arisen something like "Filter Error at /hyperkitty/

/bin/sh: 1: sassc: not found"

-Nikhil Rayaprolu



On 6 December 2016 at 17:21, Simon Hanna <simon.hanna at serve-me.info> wrote:

> On 12/06/2016 10:15 AM, Nikhil Rayaprolu wrote:
> > I tried installing hyperkitty ,following the doc
> > https://hyperkitty.readthedocs.io/en/latest/development.html . but on
> > opening the localhost:8000 on browser.
> > NoReverseMatch at /
> >
> > Reverse for 'hyperkitty.views.index.index' with arguments '()' and
> > keyword arguments '{}' not found. 0 pattern(s) tried: []
> >
> > what would be causing the problem?
> Apply this patch until it gets merged into master
> https://gitlab.com/mailman/hyperkitty/merge_requests/42
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> https://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/
> mailman-developers%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-
> developers/nikhil684%40gmail.com
>
> Security Policy: http://wiki.list.org/x/QIA9
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-12-06 17-44-26.png
Type: image/png
Size: 8483 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161206/df3a7424/attachment.png>

From simon.hanna at serve-me.info  Tue Dec  6 07:23:53 2016
From: simon.hanna at serve-me.info (Simon Hanna)
Date: Tue, 6 Dec 2016 13:23:53 +0100
Subject: [Mailman-Developers] Whoosh Error during installation of
 hyperkitty
In-Reply-To: <CAKYz7F6PafJKyGEGCYj9zEWZ5w0v7FY52_uL=+6ZWD0JupxnPA@mail.gmail.com>
References: <CAKYz7F6FqpoxsWuveyuUOnvijPF3dwOdcov43V6gz6SiwFtngA@mail.gmail.com>
 <984bae93-3065-3a63-e58d-96b37fcc7edf@msapiro.net>
 <CAKYz7F6KziFmSkZOmD8_aihm3waNTPEA4H+MyUq4oi30_Gg63A@mail.gmail.com>
 <8140af7c-e827-15e6-9914-e9bf2b555cdb@serve-me.info>
 <CAKYz7F6PafJKyGEGCYj9zEWZ5w0v7FY52_uL=+6ZWD0JupxnPA@mail.gmail.com>
Message-ID: <05405e12-abe6-3d9f-aa34-bcebf88bedaf@serve-me.info>

On 12/06/2016 01:18 PM, Nikhil Rayaprolu wrote:
> Thank you Simon,
> your solution to the previous issue has solved it but unfortunately a
> new error has arisen something like "Filter Error at /hyperkitty/
> /bin/sh: 1: sassc: not found"
>
> -Nikhil Rayaprolu
When you follow a guide, please read the whole guide. There is a section
included that instructs you to install a sass compiler. Which one you
can install depends on the your OS.

And please don't post pictures. You should include a text-only full
trace. You can use images if you want to highlight some graphic issue...
>
> On 6 December 2016 at 17:21, Simon Hanna <simon.hanna at serve-me.info
> <mailto:simon.hanna at serve-me.info>> wrote:
>
>     On 12/06/2016 10:15 AM, Nikhil Rayaprolu wrote:
>     > I tried installing hyperkitty ,following the doc
>     > https://hyperkitty.readthedocs.io/en/latest/development.html
>     <https://hyperkitty.readthedocs.io/en/latest/development.html> .
>     but on
>     > opening the localhost:8000 on browser.
>     > NoReverseMatch at /
>


From f at florianfuchs.com  Thu Dec  8 12:45:45 2016
From: f at florianfuchs.com (Florian Fuchs)
Date: Thu, 8 Dec 2016 18:45:45 +0100
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <c4e90278-6b2d-aa1a-1a93-a257dc6c76be@toybox.ca>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <20161203202244.GA10744@linux.fritz.box>
 <c4e90278-6b2d-aa1a-1a93-a257dc6c76be@toybox.ca>
Message-ID: <20161208174544.GA20298@linux.fritz.box>

On Sat, Dec 03, 2016 at 17:25:24PM -0800, Terri Oda wrote:
>On 2016-12-03 12:22 PM, Florian Fuchs wrote:
>>I did some manual integration testing today
>>(core+mailmanclient+postorius) which looked fine so far. I didn't get
>>to test HyperKitty and the bundler though, so any help testing those
>>would be very much appreciated. I will have some more time tomorrow.
>
>I tried to do some testing based on these wiki instructions last weekend
>https://wiki.list.org/HyperKitty/DevelopmentSetupGuide
>
>and hit a "[Errno 61] Connection refused" issue when attempting to log 
>in to Postorius.  I suspect it might be an issue with the mac, since 
>googling for the error (it's a django one) seems to find a lot of 
>people on macs with problems, but I didn't manage to narrow it down 
>more than that to make a useful bug report.

Do you have a traceback somewhere? If you're logging in for the first
time, it *might* have to do with allauth trying to verify your email
address by sending you an confirmation email (which probably fails if
you don't have smtp set up on your mac).

If that's the case, we should probably try to catch this condition and
display a useful error message instead of just letting it break.

Cheers
Florian

>I did set up a new linux install on another machine to work on next, 
>though, so I may have something else to say on that front tomorrow.
>
> Terri
>
>
>_______________________________________________
>Mailman-Developers mailing list
>Mailman-Developers at python.org
>https://mail.python.org/mailman/listinfo/mailman-developers
>Mailman FAQ: http://wiki.list.org/x/AgA3
>Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
>Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/f%40florianfuchs.com
>
>Security Policy: http://wiki.list.org/x/QIA9

From nikhil684 at gmail.com  Fri Dec  9 06:29:24 2016
From: nikhil684 at gmail.com (Nikhil Rayaprolu)
Date: Fri, 9 Dec 2016 16:59:24 +0530
Subject: [Mailman-Developers] Contributing to Mailman Core
Message-ID: <CAKYz7F73G_cyK1+ZFS-vVEiCbDbRvxRzViR0NXO7eEhz6CMnOA@mail.gmail.com>

Hello, I would like to contribute to mailman core . Can any one mentor me
by picking some issues in core application which could make me understand
the code structure. and also guide me through understanding the core module.

I made two merge requests to postorius and read the documentation of maiman
along with videos on mailman architecture by barry warshaw.

Thank You
-Nikhil Rayaprolu

From mark at msapiro.net  Fri Dec  9 12:37:20 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 9 Dec 2016 09:37:20 -0800
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <20161202110724.6b00dde3@subdivisions.wooz.org>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
Message-ID: <661a0aa4-d525-20a4-6cca-5c1be6d270ef@msapiro.net>

On 12/02/2016 08:07 AM, Barry Warsaw wrote:
> Hello Mailman 3 users and developers!
> 
> It's been a long slog but I think we are finally ready to begin the release
> process for Mailman 3.1.  I am pretty happy about the state of the Core, and
> Florian is going to do some more integration testing with HyperKitty and
> Postorius.  We still have a few issues and a merge proposal or two to address,
> but I am planning to spin a beta of Core this weekend to facilitate testing.


Barry,

I understand you need to feel comfortable about everything going into
the core and this takes time and energy to review all the MRs, but I
think it is pretty important to get the DMARC mitigations into the core.
If there's anything I can do to help with this, let me know.

I will rebase my branch again and possibly make one minor tweak, but I
think it should be OK.

I can also work on Postorius. Also in this vein I have a question.
Should the DMARC settings be added to the Alter Messages tab in the List
Settings view or would it be better to have a separate DMARC Mitigations
tab.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161209/7c8265f7/attachment.sig>

From barry at list.org  Sat Dec 10 03:52:09 2016
From: barry at list.org (Barry Warsaw)
Date: Sat, 10 Dec 2016 09:52:09 +0100
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <661a0aa4-d525-20a4-6cca-5c1be6d270ef@msapiro.net>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <661a0aa4-d525-20a4-6cca-5c1be6d270ef@msapiro.net>
Message-ID: <20161210095209.78a73649@presto>

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote:

>I understand you need to feel comfortable about everything going into
>the core and this takes time and energy to review all the MRs, but I
>think it is pretty important to get the DMARC mitigations into the core.
>If there's anything I can do to help with this, let me know.
>
>I will rebase my branch again and possibly make one minor tweak, but I
>think it should be OK.

Thanks for pushing back on this Mark.  Obviously, I have a high degree of
trust in your work, but yeah, my compulsive behavior is showing through. ;)

Please do rebase and if you can, remilestone the MR to 3.1.  We'll get it in.

>I can also work on Postorius. Also in this vein I have a question.
>Should the DMARC settings be added to the Alter Messages tab in the List
>Settings view or would it be better to have a separate DMARC Mitigations
>tab.

My gut reaction is to add a separate DMARC Mitigations tab, but Florian and
Terri have final say I think.

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161210/116bf1cb/attachment.sig>

From barry at list.org  Sat Dec 10 03:56:35 2016
From: barry at list.org (Barry Warsaw)
Date: Sat, 10 Dec 2016 09:56:35 +0100
Subject: [Mailman-Developers] [MM3-users] Re: Mailman 3.1 beta coming
 soon
In-Reply-To: <20161203202244.GA10744@linux.fritz.box>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <20161203202244.GA10744@linux.fritz.box>
Message-ID: <20161210095635.7fd8e055@presto>

On Dec 03, 2016, at 09:22 PM, Florian Fuchs wrote:

>I think it's OK to put out a separate beta of the core, because the
>version pulled from pypi will still be 3.0 if I'm not terribly mistaken.

BTW, I did upload a beta of Core to PyPI before I started my travel.

>For the real 3.1 we should probably do a coordinated release of all
>components, once everything's tested a little more thoroughly.

For sure.

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161210/e565a8e6/attachment.sig>

From mark at msapiro.net  Sat Dec 10 11:49:56 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 10 Dec 2016 08:49:56 -0800
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <20161210095209.78a73649@presto>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <661a0aa4-d525-20a4-6cca-5c1be6d270ef@msapiro.net>
 <20161210095209.78a73649@presto>
Message-ID: <dba14981-40ff-75f0-64f2-92f48a054b96@msapiro.net>

On 12/10/2016 12:52 AM, Barry Warsaw wrote:
> 
> Please do rebase and if you can, remilestone the MR to 3.1.  We'll get it in.


Done. There is one "temporary" commit in my MR to work around
<https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass.


>> I can also work on Postorius. Also in this vein I have a question.
>> Should the DMARC settings be added to the Alter Messages tab in the List
>> Settings view or would it be better to have a separate DMARC Mitigations
>> tab.
> 
> My gut reaction is to add a separate DMARC Mitigations tab, but Florian and
> Terri have final say I think.


I have a WIP MR at
<https://gitlab.com/mailman/postorius/merge_requests/194> that adds a
tab. Maybe Florian and Terri can look at that and chime in.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20161210/f6105e84/attachment.sig>

From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Dec 12 03:29:10 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Mon, 12 Dec 2016 17:29:10 +0900
Subject: [Mailman-Developers] [MM3-users] Re: Mailman 3.1 beta coming soon
In-Reply-To: <20161210095209.78a73649@presto>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <661a0aa4-d525-20a4-6cca-5c1be6d270ef@msapiro.net>
 <20161210095209.78a73649@presto>
Message-ID: <22606.24534.641604.203373@turnbull.sk.tsukuba.ac.jp>

Barry Warsaw writes:

 > >I can also work on Postorius. Also in this vein I have a question.
 > >Should the DMARC settings be added to the Alter Messages tab in the List
 > >Settings view or would it be better to have a separate DMARC Mitigations
 > >tab.
 > 
 > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and
 > Terri have final say I think.

I would find it more natural to have "Posting Policy" (which would
include posting filters on size and list membership, as well as
message alterations such as removing .exe files and enforcing plain
text by removing or rendering HTML parts), and "Malware Mitigation",
which would include IP, domain, and mailbox filters as well as DMARC.
I think DMARC mitigation is probably too special to deserve its own
tab.

Probably this is way too much reorganization to do at this point, but
I'd like to keep this point in mind.  We are already getting reports
that configuration options are hard to find just because it's
different from Mailman 2.  I suspect that the REST API is sufficiently
flexible and regular that we'll be tempted to proliferate options, so
let's try to keep them organized.

Steve


From terri at toybox.ca  Tue Dec 13 00:38:52 2016
From: terri at toybox.ca (Terri Oda)
Date: Mon, 12 Dec 2016 21:38:52 -0800
Subject: [Mailman-Developers] Mailman 3.1 beta coming soon
In-Reply-To: <20161208174544.GA20298@linux.fritz.box>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <20161203202244.GA10744@linux.fritz.box>
 <c4e90278-6b2d-aa1a-1a93-a257dc6c76be@toybox.ca>
 <20161208174544.GA20298@linux.fritz.box>
Message-ID: <35113e2f-14fc-423d-aa8a-eb05b902e64a@toybox.ca>

On 2016-12-08 9:45 AM, Florian Fuchs wrote:
  you have a traceback somewhere? If you're logging in for the first
> time, it *might* have to do with allauth trying to verify your email
> address by sending you an confirmation email (which probably fails if
> you don't have smtp set up on your mac).
>
> If that's the case, we should probably try to catch this condition and
> display a useful error message instead of just letting it break.

The email *would* make sense, and would explain why I saw the error more 
often associated with macs.  If that's the case it sounds like an error 
that should be caught and explained.  I'll file a bug and dump the 
traceback there.

  Terri



From terri at toybox.ca  Tue Dec 13 00:34:24 2016
From: terri at toybox.ca (Terri Oda)
Date: Mon, 12 Dec 2016 21:34:24 -0800
Subject: [Mailman-Developers] [MM3-users] Re: Mailman 3.1 beta coming
 soon
In-Reply-To: <22606.24534.641604.203373@turnbull.sk.tsukuba.ac.jp>
References: <20161202110724.6b00dde3@subdivisions.wooz.org>
 <661a0aa4-d525-20a4-6cca-5c1be6d270ef@msapiro.net>
 <20161210095209.78a73649@presto>
 <22606.24534.641604.203373@turnbull.sk.tsukuba.ac.jp>
Message-ID: <04d69c20-c1cf-3d4b-d6b2-91affe1f6cae@toybox.ca>

On 2016-12-12 12:29 AM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
>  > >I can also work on Postorius. Also in this vein I have a question.
>  > >Should the DMARC settings be added to the Alter Messages tab in the List
>  > >Settings view or would it be better to have a separate DMARC Mitigations
>  > >tab.
>  >
>  > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and
>  > Terri have final say I think.
>
> I would find it more natural to have "Posting Policy" (which would
> include posting filters on size and list membership, as well as
> message alterations such as removing .exe files and enforcing plain
> text by removing or rendering HTML parts), and "Malware Mitigation",
> which would include IP, domain, and mailbox filters as well as DMARC.
> I think DMARC mitigation is probably too special to deserve its own
> tab.

Alter messages tab works for me, but DMARC is kind of a big enough deal 
(as far as mail delivery goes) and sufficiently different that I agree 
with Mark that it's not unreasonable to give it a separate tab.   I'd be 
willing to start it on its own and move it if we're getting too 
cluttered later, as long as we document it in the release notes when we 
do. Florian, what do you think?

> Probably this is way too much reorganization to do at this point, but
> I'd like to keep this point in mind.  We are already getting reports
> that configuration options are hard to find just because it's
> different from Mailman 2.  I suspect that the REST API is sufficiently
> flexible and regular that we'll be tempted to proliferate options, so
> let's try to keep them organized.

We also get reports that mailman 2.1 options are hard to find -- I think 
I personally help someone find something at least once a month (on irc, 
in person, or by email) for the past decade. :)  I imagine Mark has 
answered a lot more of those than I have.

The big thing I want is good documentation here.  There's never going to 
be an organization that works for everyone, but an easily searchable 
document with all the options would make a big difference.  I only got 
to that level with the user docs not the list admin docs in 2.1