On 2015-08-04 7:15 PM, Amate Yolande wrote:
> My name is Amate Yolande, a second year Computer Science student from
> the University of Buea Cameroon. I am new to open source and interested in
> contributing to mailman. I am primarily a Python programmer with basic
> mailman3 with Postorius and Hyperkitty locally, but I have no prior
> experience with mailman so I would like to get directives on some
> beginners tasks to help me familiarize myself with mailman.
We try to tag our bugs as "beginner-friendly" or "easy" when we think
they might be suitable for new contributors:
There aren't a huge number of bugs in that category right now because we
cleaned up a lot of the easier bugs before the release earlier this
year, but one thing that is *always* helpful and reasonably beginner
friendly is adding more test cases. There's a bug in postorius with a
few hints as to how to get started:
The other great thing to do as a beginner is to report bugs. And that's
not just bugs in the software, but also bugs in the documentation: did
you find anything stupidly confusing when you set up your instance? Is
there anything you found hard to find on the website? Ask about it
here, and maybe file a bug or two so we don't forget to fix things! It
really helps us to have people coming in and seeing all that stuff with
fresh eyes, so those are awesome things to do now before you get super
familiar with the process!
For example, having just answered this question, I can see that it would
be super awesome if we had a page on the website telling new users where
to find the easy bugs. Would you like to file that bug to get you started?
You can do it from here:
I've been made aware several times that the mailman-bundler docs don't
work super well for folk who are focused on getting a production rather
than a development server up and running. Now, I know we're hoping that
there will be distro packages and an easier path for this eventually
(please, if you're interested in doing some distro packaging, we need
help!) but I thought I'd take a stab at making it better even for people
going from source.
I've started a fork with my first thoughts here:
- a new section "Development vs Production" with a note about the
expected workflow (development->test->production) and a pointer to the
production documentation (although I think my link is broken right now.
My restructuredtext-fu is weak tonight and google didn't help.)
- Something more explicit in "Run the services" about how to run django
on something other than localhost.
Those were the two things that really stood out for me when I was
setting up a server this week, but I am certain they're not the only
places where we could be more clear.
So... I'd like some feedback! What seems confusing about the doc? What
concerns are there for production servers that we aren't addressing?
PS - Don't worry, I will make a merge request when I fix the formatting
errors, but it's late and I wanted to get an email out before I go to bed
the company I am working for is currently evaluating whether or not to
upgrade to mailman 3.0 from mailman 2.X. So far I am very impressed by
the improved functionality and the good looking webinterface(s) and I am
thankful for the good work.
However, I am having some trouble understanding the procedure of
granting users access to the Postorius webinterface. I created a bunch
of Mailman users using the REST-interface (apparently inserted in table
'user' in var/data/mailman.db) which however are not automatically given
access to the Postorius web interface, apparently only granted to users
in the 'auth_user' table in var/mailman-web/mailman-web.sqlite. So my
1. What is the procedure of granting Postorius web access to Mailman
2. Is there a timeframe in which a good Mailman 3 documentation can
be expected? I find it quite hard to solve problems myself given the
small amount of informationon the web right now.
Thanks a lot!
I am planning to migrate from mailman 2.1.14 to mailman 3. At the moment
mailman 3 is running on a new CentOS 7 server with postfix as MTA. But I
have some questions and problems:
1. I have an error with hyperkitty
ERROR 2015-07-29 08:11:02,287 update_index 7216 140406344681280 Failed to
update the fulltext index: 'Command' object has no attribute 'commit'
Traceback (most recent call last):
s/update_index.py", line 58, in execute
rch_indexes.py", line 73, in update_index
management/commands/update_index.py", line 233, in update_backend
do_update(backend, index, qs, start, end, total,
AttributeError: 'Command' object has no attribute 'commit'
As far as I can tell, there is an error with the haystack indexing of
archived mails. But how to fix this? I'm clueless.
2. In mailman 2, I've created a list and added a new owner. Then the owner
get an email, with his password and a link to the admin page of the list.
How does this work in mailman3? If I create an list in mailman3 and set the
owner, then the email address is the owner, but he isn't noticed. So what
steps are needed to get an password for the new owner and admin of the list?
3. Is it possible to get Shibboleth ( <https://www.shibboleth.net>
4. The link in the welcome mail to the info page of the list is wrong. It
http://email@example.com and if I
visit this link, I get an 404 error. (example.com is here a real domain).
The Second link says <http://firstname.lastname@example.org>
http://email@example.com where the example.com
part seems to be hardcoded.
Thank you for your help and I hope my English is not too bad (I'm just a
German IT Administrator...)
Greetings from Germany
My name is Amate Yolande, a second year Computer Science student from
the University of Buea Cameroon. I am new to open source and interested in
contributing to mailman. I am primarily a Python programmer with basic
mailman3 with Postorius and Hyperkitty locally, but I have no prior
experience with mailman so I would like to get directives on some
beginners tasks to help me familiarize myself with mailman.
I just downloaded the mailman3 code to see if I can contribute anything.
I was astonished to find out that postorius still uses python2
although mailman made the switch to python3.
Is there any reason behind this?
I asked on the irc channel but got no answer so I'm trying here.
I used 2to3 on the code and successfully executed the code.
I executed the tests, and ran into some errors.
If this work is going to be included sometime,
I'm willing to investigate and try to fix these errors.
On Jul 21, 2015, at 06:39 PM, Aurelien Bompard wrote:
>If I try to associate an existing address to an existing user (without
>this address obviously), the Mailman API will reply with a 400 error
>"User already exists". Postorius currently does not detect that and
>just errors out with a 500 page (but that's not the issue here).
>I think I need to merge the two users, and that's currently not
>supported. I believe it would be a useful feature, so I'd like to
>discuss it here. IMHO, the only tricky part would be to merge the
>preferences associated with each user, but if I know which of my two
>users has priority, I can just resolve the conflicts that way.
>Am I missing something? Do you agree it would be a useful feature to have?
So, Abhilash submitted a merge request to allow for unlinked addresses to be
linked to existing users via the REST API.
That's essentially the correct fix for the first order problem (though there's
a subtle bug in the mr that I will fix manually).
If that answers your question, then great!
Actually merging two existing users is indeed a tricky thing because users
link to so many other interesting bits and pieces. Two separate users have
two separate memberships, linked addresses, preferred addresses, and yes,
preferences. There are also the created_on, display_name, and (the mostly
unused) password attributes.
How deep does merging users go?
On 07/25/2015 05:30 PM, Bhavesh Goyal wrote:
> Hey !
> I Just updated my Blog with an update of The Project Progress so far.
> Attached to The Blog is also a preview of The Dashboard for those who
> have't been able to test it yet on their machine.
I had a look at your branch and also tested it out. I was not able to
test each and every functionality, but am pretty impressed with your
work. I liked that for smaller screens you can hide some widgets and
switch between them from the nav bar.
- The dropdown on the left-most of Nav Bar, does not look like a
dropdown. Maybe add a caret symbol or something like that?
- I had a small overview of the tests that you asked me to look at and
they are good!