[Mailman-Developers] Re: Exception when trying to send mail to list
On 07/25/2018 09:43 AM, Kamran Soomro wrote:
> Hi,
>
> Recently I’ve started seeing some weird exceptions when trying to send emails
> to a list with mailman 3 running in docker:
>
> From mailman core logs:
>
> sqlalchemy.exc.DataError: (pymysql.err.DataError) (1406, "Data too long for
> column 'value' at row 1") [SQL: 'INSERT INTO pendedkeyvalue (`key`, value,
> pended_id) VALUES (%(key)s, %(value)s, %(pended_id)s)'] [parameters: {'key':
> '_pck_rule_misses', 'value':
> '"\\u0080\\u0003]q\\u(X\\u0010\\u\\u\\udmarc-mitigationq\\u0001X\\n\\u\\u\\uno-sendersq\\u0002X\\b\\u\\u\\uapp
> ... (382 characters truncated) ...
> \\u000bX\\b\\u\\u\\umax-sizeq\\fX\\u000f\\u\\u\\unews-moderationq\\rX\\u0011\\u\\u\\ususpicious-headerq\\u000ee."',
> 'pended_id': 12}] (Background on this error at: http://sqlalche.me/e/9h9h)
> Jul 25 07:33:28 2018 (32) SHUNTING:
> 1532504008.7233553+2ca45fec09fa01b9dd31ed584a06b04302ea155b
This seems to be the following issue
https://gitlab.com/mailman/mailman/issues/301
https://gitlab.com/mailman/mailman/issues/385
What version of core are you running?
> From mailman web logs:
>
> TypeError: ord() expected a character, but string of length 0 found
> ERROR 2018-07-25 07:42:41,098 22515 hyperkitty.lib.utils Failed to update the
> fulltext index: ord() expected a character, but string of length 0 found
>
> Could anybody guide me as to what’s wrong?
This was attributed to a change of Python versions in the past. Can you
delete the fulltext_index and rebuild the cache?
Also what version of Hyperkitty are you running. The latest release is
Python3 only and the traces are using Python2. Be sure to also fix your
cron jobs that might still be using Python2
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mm3/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3
Security Policy: https://wiki.list.org/x/QIA9
Re: [Mailman-Developers] mailman3 on debian
On 04/22/2018 12:31 PM, ?? wrote:
> OK, I follow the instruction of /usr/share/doc/mailman3/README.Debian,
>
>
> it can visit http://server/mailman3/postorius/lists/, but when login, it says
> Sever Error (500). in /var/log/mailman3/web/mailman-web.log there is a line:
> SMTPRecipientsRefused: {u'x...@xx.com': (451, '4.3.0 : Temporary
> lookup failure')}
> # x...@xx.com is superuser email address.
Did you use a valid email address? From what you describe what is
happening is that the frontend is trying to confirm your email address
but can't deliver it.
It might also be a configuration issue with the MTA you are using. Try
to send an email to that address from the command line on the server.
To work around this particular issue you could do the following:
open a django shell (I don't know where debian puts the manage.py file,
but you should have one):
python manage.py shell
in the shell do the following:
from allauth.account.models import EmailAddress
e = EmailAddress.objects.get(email='x...@xx.com')
e.verified = True
e.save()
Of course you need to replace the email, with the one you have used.
That should mark the email as verified in the database and let you
login. Note that this is sort of a hack and you should figure out what's
going on there...
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Handling additions to REST API in client side
On 12/28/2017 06:19 PM, Mark Sapiro wrote: On 12/28/2017 08:33 AM, Simon Hanna wrote: * New keys (and values) can be added anytime This would make things like exposing new stuff easy. Clients that don't know about a field can just ignore it. But that doesn't address the original issue which is that when a new key/value is added and a client is updated to use it, the client has no way to require a core API that provides it. Up until now I was under the impression that the clients (Postorius/Hyperkitty) always require the latest version of core. Do we really want to add the burden of having to care for different api versions in the clients? If we would start from scratch something like http://www.coreapi.org/ might be feasible, adding that now would more or less require a complete rewrite of Postorius. In my view backward compatibiliy should be applied so that old clients can still access newer versions of core. I don't think it's a good idea to require Postorius to be compatible with older(all?) versions of core. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Handling additions to REST API in client side
On 12/27/2017 09:49 AM, Abhilash Raj wrote: Hi All, Core's REST API is versioned and any change that break backwards-compatibility cause the version to bump so that clients can take care of that. However, one question that I have been thinking about recently is how to handle additions to REST API that don't necessarily break the backwards compatibility. For example, Core added `max_message_size` attribute to MailingList's REST endpoint, but it hasn't made into any released version yet. Also, Postorius added max_message_size in `Message Acceptance` settings. The problem here is that the entire PUT/PATCH request is going to fail if the currently running version of Core doesn't have `max_message_size` attribute exposed (Unknown Attribute Error). There is no easy way to check for whether the Core has this attribute as API is versioned at 3.1 for both cases. So, how do we actually handle this and maybe future cases like this? How about defining it this way: * The result of queries can be viewed as dictionaries * New endpoints (urls) can be added anytime * No endpoint is removed without a version bump * Existing dict keys will not be dropped without a version bump * The format of values assigned to existing keys will not change without a version bump * New keys (and values) can be added anytime This would make things like exposing new stuff easy. Clients that don't know about a field can just ignore it. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] no module named django
Replying back to the list :-) > #virtualenv?0?2 = /srv/django/mailman/env since you managed to install postorius and get it running, you either installed it systemwide which would work with it commented out, or you actually created a virtualenv in which case you should know where the location of that is. (virtualenv is preferred, you only use the system packages, if they are installes using your package manager and the application is too. Otherwise you will run into incompatibilties sooner or later. totally do not know about virtualenv, just follow the guide to install postorius. when runserver, it can visit by 192.168.1.96, when "ctrl+c", 192.168.1.96 not work. virtualenv is a python concept, you should be able to find information online about that. It's about how and where you install python dependencies. > #socket?0?2 = /run/uwsgi/mailman.sock This is the socket that is created for the webserver to connect to. I'm actually not sure what happens if you don't include that... I doubt uwsgi would actually start. installed uwsgi and it seems running, I run $ uwsgi, there is no error. but can't find /run/uwsgi/ directory, usually mailman.sock can be at which directory? By convention sockets are placed in /run/ you can put them wherever you want. I tried with docker, here is its guide with 6 steps: --- $ mkdir -p /opt/mailman/core $ mkdir -p /opt/mailman/web $ git clone https://github.com/maxking/docker-mailman $ cd docker-mailman # Change some configuration variables as mentioned above. $ docker-compose up -d But about configuration in step 5, I can't find?0?2/opt/mailman/core/mailman-extra.cfg and?0?2/opt/mailman/web/settings_local.py, and can't find it in any directory from /home/lists/docker-mailman/. so do not know what to with it. is it to create these two files? Yes, you have to manually create them. The idea is that there are default settings and you would override them in additional files. The default settings are found here https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/settings.py https://github.com/maxking/docker-mailman/blob/master/core/assets/mailman.cfg There are some settings that you have to overwrite, as mentioned in the readme of https://github.com/maxking/docker-mailman You do so, by specifing them in the respective files that you create in /opt/mailman/ on your host machine. You can search for the settings in the original files in the github repo and then use the same syntax in your new files. OK, maybe it is realistic for me to wait for debian backport. That will definelty mean less work for you, and you will have it running directly on the machine managed by your package manager. This will probably be easier with upgrades as well. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] no module named django
On 12/17/2017 10:59 AM, 孙志勇 wrote: Hi, when I init uwsgi, I find a problem "importerror no module named django". I install postorius following installation in http://postorius.readthedocs.io/en/latest/setup.html, and visit http://192.168.1.96:8001 it workes well after run: $ sudo python manage.py runserver 0.0.0.0:8001. That is very bad. You shouldn't run that as root! www-data or http or whatever your web user is, is the right user for that. I wonder why you use 0.0.0.0:8001 8001 is the default port of Mailman core, you probably don't want to use that. You need to have core on your system for postorius to actually do anything... Do not know what is about development in the page: http://postorius.readthedocs.io/en/latest/development.html, so I pass it. Do you want to setup for development? If yes, the guide should be more than enough to tell you what needs to be done. If you follow the link to https://wiki.list.org/DEV/HowToContributeGit you should be able to do that. Then go to deployment in http://postorius.readthedocs.io/en/latest/deployment.html. This somewhat contradicts the above url.. I creat file /home/lists/uwsgi.ini and put in it: --- [uwsgi] chdir = /home/lists/postorius/sample_project #virtualenv = /srv/django/mailman/env #socket = /run/uwsgi/mailman.sock wsgi-file = wsgi.py master = true process = 4 threads = 2 vacuum = true plugin = python2 uid = http gid = http --- then run: $ uwsgi --ini /home/lists/uwsgi.ini it gives the error "importerror, no module named django". I think it is the problem of the below 2 line: #virtualenv = /srv/django/mailman/env since you managed to install postorius and get it running, you either installed it systemwide which would work with it commented out, or you actually created a virtualenv in which case you should know where the location of that is. (virtualenv is preferred, you only use the system packages, if they are installes using your package manager and the application is too. Otherwise you will run into incompatibilties sooner or later. #socket = /run/uwsgi/mailman.sock This is the socket that is created for the webserver to connect to. I'm actually not sure what happens if you don't include that... I doubt uwsgi would actually start. but docs do not mention how to set about this 2 line, so I just comment out the 2 line. I also tried with mailman-suite, also have the same problem. can you help with me? will you think to write a installing instruction with command to follow for people totally don't know django in future? It's not entirely clear what you actually want to do, so it's hard to help... If you want it for production I suggest you use the docker images provided by maxking or wait a couple of weeks until the packages get into debian backports, where you can just run one command and then get a running system. For dev, the mentioned link should be more than enough to get you up and running. If you have issues from following a guide, please mention that so they can be improved... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Date of Mailman 3 Suite going Python 3 only after Django dropped Python 2
On 12/15/2017 08:03 PM, Tobias Conradi wrote: https://www.djangoproject.com/weblog/2017/dec/02/django-20-released/ 1) Is there a date for when Mailman Suite will switch to Python 3 only, so user are not required to install two Python versions? AFAIK there are merge requests for all the parts, the only hold-up is testing to make sure they actualy work. You can search for "Python 3" in the gitlab issue trackers for more information. 2) Is there a date for a switch to Django 2? Since Django 2 only supports Python3 support for it will most probably be added by merging the Python3 branches. I haven't gone over all the details, but I don't think there are any changes that still require porting... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] mailman var directory pip3
On 12/15/2017 09:15 PM, Mark Sapiro wrote: On 12/15/2017 05:43 AM, 孙志勇 wrote: Hi, I installed mailman3.1.1 using pip3 on debian9.3. Where is the var directory of mailman?Thank you. In the home directory of the user that runs 'mailman'. That's where it should be (by convention). It will be created in the current directory that you run any mailman command from, unless you specify a config directory. The recommended setup is a user called mailman owning /var/lib/mailman where the var directory would be placed. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman
These images are built using git-heads *only* if they are passing our test suite and are re-generated weekly. You should be aware that while all these components are tested with their individual test suites, their combination might sometimes not be stable. This will get you updates/bug-fixes much faster :) This contradicts what you said in my merge request for Postorius https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 You either use released versions, or make sure that the master branches are always compatible. You can't have both with the current development model. Not exactly, I still believe all our git-heads should be compatible with released (i.e. stable) versions of dependencies, regardless of the fact that we maintain those dependencies. Also, there is at least one test per-project which tests with git-heads of dependencies we maintain, so that we know if we make any incompatible changes. I am not sure what in the current development model prevents us to do both? The story for container images is different than testing with git-heads. We need better integration testing for the entire suite to be stable in conjunction, rather than independently. In fact, containers might be the perfect way to actually do the integration testing. Scenario: Core changes something about rest that is backwards incompatible. The change is commited to master. Since your containers use the master branches, all future builds will fail until mailmanclient and postorius/hyperkitty. If you want to always have Postorius (and others) compatible with the latest release of master, development for Postorius will be a Pain, because you can't use the master branch of mailman for testing and quick changes. Also your containers and all integration tests that can be done with them will always fail. Until you fix Postorius and the other clients... So why not just have the master branches always compatible and make life easier for developers. I don't see a good reason why you want to do it the other way round... Any bug in core that affects Postorius will also just remain there until you release a new version of core. If you really really want to have it your way, there have to be more frequent releases. - Improve the container images to work with new micro-services architecture, to achieve scaling and redundancy in services. The current bottleneck is the rest api from core. IMO bulk actions, filtering and sorting should be added there before trying to have multiple postorius/hyperkitty instances serving the same core... I didn't say they will be served from the same core ;-) Yes, the Core's API can be further improved to be more efficient. But that doesn't prevent us from scaling. I understand there are issues around multiple instances of containers, but I have ideas to get around most of them. I just don't want that people that have issues with big installations get the answer: We know of that issue, please deploy Mailman on X containers/machines as a workaround ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman
On 11/08/2017 12:03 AM, Abhilash Raj wrote: New images are available on quay.io and, moving forward, the rest of the image builds will also be moved to Quay[4][5]. Since docker deployment is currently the recommended install, with manual installs using the master branches for "experts" I wonder why you are using Quay. It looks like it's a non-free system. Why use Quay but refuse to use a non-free translation system like transifex? These images are built using git-heads *only* if they are passing our test suite and are re-generated weekly. You should be aware that while all these components are tested with their individual test suites, their combination might sometimes not be stable. This will get you updates/bug-fixes much faster :) This contradicts what you said in my merge request for Postorius https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 You either use released versions, or make sure that the master branches are always compatible. You can't have both with the current development model. If this campaign succeeds, here is a road map of what I intend to get done: Sounds great, what is the limit where the campaign succeeds? What will happen to the funds if it doesn't? - Add Admin Dashboard project from GSoC 2014 (maybe?) Didn't find anything using google. What is that project about? - Add better testing of container images and provide deployment instructions for Kubernetes & Docker Swarm To be honest, I don't think we should all in on containers. Yes they are nice, but I guess most people would prefer distro packages. Even if people want containers, I for instance would prefer plain systemd-nspawn - Improve the container images to work with new micro-services architecture, to achieve scaling and redundancy in services. The current bottleneck is the rest api from core. IMO bulk actions, filtering and sorting should be added there before trying to have multiple postorius/hyperkitty instances serving the same core... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Signing commits with gpg
I guess more important would be to sign the releases. At least archlinux likes to have signatures for source archives and often requests upstream projects to add this. For me as a user it would be more interesting to have a verified release signed by one key that's static rather than a commit history that is signed by many different keys that I don't know. I guess the single commit signature is more relevant to other developers, so we know who actually committed something. However, if all commits to the master branches come from merge requests, you already use gitlabs verification. It's not as good as gpg signatures, but in the end you have to trust gitlab to a certain degree anyway... Another thing that just came to mind: how does commit squashing work? You'll probably have to do that offline and not use gitlabs autosmashing... I don't have anything against it and I can also rather easily start doing that. (I will have to have my keychain nearby, as I don't have my keys stored on my machines...) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Migrating Postorius and Hyperkitty to Python 3
I'm in favor of dropping Python2. All distros have Python3 and afaik all dependencies are Python3 ready. So I don't see a reason why anybody would want to stick to Python2, especially since core is Python3 only... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 3 not restarting after reboot
On 09/05/2017 02:45 AM, Mark Sapiro wrote: > On 09/04/2017 02:46 PM, Simon Hanna wrote: >>> Does anyone have an idea why Mailman 3 is not starting on reboot? >> I'm using systemd and it has been working for me the last couple of >> reboots. I don't have one coming up on my prod setup until end of this >> month, I can check again then. > > What are you running? I think the issue is caused by > > commit ae0042a90220119414f61aeb20c6b58bfacb8af2 > > are you running with that? I'm currently still running 3.1.0 (Using my archlinux packages) ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 3 not restarting after reboot
> Does anyone have an idea why Mailman 3 is not starting on reboot? I'm using systemd and it has been working for me the last couple of reboots. I don't have one coming up on my prod setup until end of this month, I can check again then. I once had issues with stale locks, because the processes sometimes get killed, leaving locks in place. But you seem to --force it, so that shouldn't be the problem... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Next Postorius release
Hi, I know it might be a little early, but I'd like to talk about the plan for Postorius (Mailman in general) releases moving forward. Should there be more point releases? 3.1.X? Or just 3.X? Are releases bound to Core releases (following core's release numbering?)? How often do we do releases? Every X merge requests and/or X months? I'd like to know that just to organize issues/merge requests and so the whole process can be planned a little more... Would be also helpful to create this information in Gitlab milestones... cheers, Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Project idea understanding
On 03/10/2017 02:08 AM, raditya wrote: > Dear Mentors, > > After going through a lot of sources mentioned in recent replies to > other subscribers and some online sources i have got some understanding > about the idea, which i would like to share with you guys and get some > feedback and suggestions . > > I think we can encrypt the list in the following ways (broadly > speaking): > > 1) Each message will be encrypted with all users as recipients. > The mailing-list maintainer will have to regularly send the list of > recipients over the mailing-list itself, > so that every user comes to know the public keys of all recipients. > But this way the maintainer will have to send recipients list to a large > number of users. If you as sender encrypt the message for every receiver, you are literally doing all the work manually and don't need mailman > 2) Another way could be relaying each message through the maintainer. > The maintainer then encrypts it for single recipient. > This might solve the problem of sending messageto large number of users > but it increases latency (each message must wait for the maintainer to > process it) > the maintainer can censor each message as they all are relayed through > him. This approach makes "maintainers" (you probably mean moderators) do all the work which also eliminates the need for mailman > 3) Or instead of using asymmetric keys we use a password given to all > users. This can already be done right now. It's as if you send an encrypted attachment that contains the actual message There has been a GSoC project like this in the past and there was quite some discussion on the mailing list. https://www.mail-archive.com/search?q=encrypt&l=mailman-developers%40python.org ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 3 Dockerfile
On 01/26/2017 08:57 PM, Barry Warsaw wrote: > On Jan 26, 2017, at 07:38 PM, Simon Hanna wrote: > >> Please note that mailman-bundler currently doesn't produce a usable >> environment. > I think bundler does more harm than good. We should probably just abandon it, > we don't really have anything better. I don't have any strong opinions about > what technology to use (e.g. Docker, Salt, Chef, Juju, etc.) other than it > should be relatively easy to use on a wide variety of *nix platforms. It > doesn't need to handle anything more than the simple common case of deploying > it all to the same server. That's not to say that we can't point to lots of > good alternatives, and even distro packages once they're available. > > Cheers, > -Barry I just updated my repository I use for my deployment which can be found here https://gitlab.com/thelinuxguy/mailman-suite following it's readme should result in a usable installation. I can work on providing an ansible playbook ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 3 Dockerfile
On 26 January 2017 17:32:48 GMT+01:00, Stephan Wehner wrote: >I've been working with the Dockerfile at > >https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > >for setting up Mailman 3. > >The page doesn't say who to contact. > >Is this mailing list a good place to ask questions about where I'm >stuck? > >Stephan I guess you can ask here. I wrote a couple of docker files that were mainly intended for testing/demoing. It really depends on what you want to do with the containers and how (if) you want to deploy them. I still haven't figured out a way to connect Mailman to an "outside" postfix. Please note that mailman-bundler currently doesn't produce a usable environment. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3
On 01/10/2017 03:56 AM, Barry Warsaw wrote: > Reviving an ancient thread. > > On May 28, 2016, at 10:27 PM, Simon Hanna wrote: > >> I used Zanata, but found it not very intuitive to use. It's also >> painfully slow. >> >> I'm unaware of any big projects that use zanata. Well openstack does, but >> they use a self hosted version and that one is not faster. I'm not sure how >> Mailman 2 was translated, but I guess most of the translators did it >> offline. You can download translation files from pootle and later upload >> them. So anyone that doesn't want to translate in the browser, can still do >> it offline. > Since gettext will be the interchange format, it will probably not be that > difficult to switch to a different service if we ever find we need to. > > I appreciate your feedback on Zanata, and honestly we just need an i18n > champion to make it happen. My apologies for such a long delay in responding > here, but Simon, if you're still willing to take the lead on i18n, I will be > happy to defer to your preferences. > >> So If you give me the ok, I write the gnu pootle maintainers and ask >> them to create three projects for us. > +1 - if you're still willing, let's do this. Core is very nearly ready to > start rc'ing for 3.1 so I think this is a great time to being building the > infrastructure for i18n. > >> I guess we could add links in postorius and hyperkitty that request >> assistance with translation. > +1 So it looks like the gnu pootle server is not up anymore. So I guess Zanata is the way to go. The projects are already in place, we would just have to update the pot files I initially uploaded. I updated Hyperkitty and Postorius since I'm familiar with django translation. You can start translating them right aways over at: https://translate.zanata.org/iteration/view/postorius/1.0.3 https://translate.zanata.org/iteration/view/hyperkitty/1.0.3 Mailman on the other hand currently doesn't have any infrastructure, and I don't think I know enough to be sure that I get all the strings in the correct format. Can someone help with that? I'll start working on a wiki page and create merge requests for Hyperkitty and Postorius that include a link to the wiki asking for help. I'll check the other projects and find out if we need to create translation projects for them too. All registered users should be able to translate. I'll enable reviews which allow certain users more rights. If you want to be responsible for a language you should be able to request that from the interface or you can contact me mentioning your username. cheers, Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Whoosh Error during installation of hyperkitty
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 <mailto:simon.ha...@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 / > ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Whoosh Error during installation of hyperkitty
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@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/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Error during installation of postorius
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" ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Broken Gitlab Remote
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 ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [django_mailman3-1.0.2] No Facebook app configured: please add a SocialApp using the Django admin
On 28 November 2016 05:33:55 GMT+01:00, Leon wrote: >Hi developers. I copied production.py from ( >https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=AttachFile&do=view&target=production.py), >so 'allauth.socialaccount.providers.facebook' is in INSTALLED_APPS. >Also, I >added another site and set SITE_ID = 2( >http://stackoverflow.com/questions/14019017/django-allauth-no-facebook-app-configured-please-add-a-socialapp-using-the-djan). >However, the exception is not fixed. > > >Error log: >ImproperlyConfigured at /accounts/login/ > >No Facebook app configured: please add a SocialApp using the Django >admin > The error says it all... You need to login to the django admin and add the configuration for Facebook before you can start using it. This is needed because some auth providers require api tokens. Also are you sure you want site_id set to 2? You will have to configure a site in the admin as well. AFAIK with site_id set to 1 you get a automatically configured example.com site. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman Sprint happening NOW at PyCon 2016 Canada
On 11/15/2016 04:01 PM, Barry Warsaw wrote: > On Nov 15, 2016, at 11:12 PM, Stephen J. Turnbull wrote: > >> It was a good idea at the time, but IMO it will be way too much work >> to keep up to date as is. If we must provide a bundle, I think we >> should use something like Simon's script (AIUI) to create a fully- >> provisioned tree from git, probably in (a) venv(s), and make a source >> tarball from that, venvs and all. Something like a top-level setup.py >> to install it all in $prefix. >> >> Folks who don't want that (distros, seasoned admins) can probably >> handle git. Probably... ;-) And following readthedocs for config. > I think I missed a reference to Simon's script, but I'd be interested in that > approach too. At this point it sounds like we shouldn't fixate on a single > deployment mechanism; we can provide some official containers, help distro > packagers, and above all, have really good documentation. https://gitlab.com/thelinuxguy/mailman-suite/ It's not really a script. It's a django project configuration (Which you'll need to run postorius/hyperkitty) But it's built so that you can easily choose which components you want to actually use. However you may want to deploy Mailman, you'll have to use such a structure. It's pretty much barebones, with the added complexity resulting from allowing you to choose to run only one of postorius or hyperkitty.. And I tried to write up everything important in the readme... It doesn't actually install anything on its own, but instructs on the different options available... It also includes nginx and uwsgi config files since I'm using them for deployment It should work as is for the master branches, but my setups are a little behind right now... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman Sprint happening NOW at PyCon 2016 Canada
On 11/14/2016 09:17 PM, Barry Warsaw wrote: > How do the other subprojects look for a December release? > > This is a good link to track the project-wide milestone: > > https://gitlab.com/groups/mailman/milestones/31?title=3.1 I went ahead and tagged a couple of issues from Postorius and mailmanclient with the milestone. They are all user facing and I think would result in a lot of new issues, if they are not addresses before. > One problem is that it doesn't include HK, so we need to figure that out. I guess you need to somehow create a milestone in hyperkitty itself. I don't have the right to do so. I'm not 100% sure, but I guess maxking created those for postorius and hyperkitty > And we need to figure out whether we want to continue to support the bundler > or > use some other container-based release mechanism (I am going to continue to > play with building a Snap for the bits and pieces). Speaking for myself here: I'm not using it and I guess I won't be in the future. I'm using a git repository for my configuration that can be found here https://gitlab.com/thelinuxguy/mailman-suite along with a local branch that holds all my deployment specific changes. I still don't really understand what bundler does, and I always have to look through all the directories to try and find the file that I want to edit. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Issue recording VCR tapes in Postorius.
>So I need to record a new tape and modify the test. So my problem is I >can't record any tapes. My "tox -e record" attempts fail with >tracebacks >like the attached. > >It appears the virtualenv in .tox/record is a Python 3.5 virtualenv and >Python 3.5 doesn't have a urllib2 module. > >Why is tox creating this as a Python 3 virtualenv? All the others it >creates for Postorius are Python 2.7. I've even tried "tox -e record >--force-dep 'python <=2.7'" but that doesn't help. > >Does anyone know what I need? You have to prefix the environment with py27. So you would be running `tox -e py27-record` Since no base Python version is defined in to, it probably uses the Python version that was used to install tox itself. You can have a look at the tox config. You could also specify the django version to be used by adding django110 to the command (the environment selectors are always separated using hyphens) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Request to process merge requests faster
Hi, I know all core devs are volunteers, and no one is maintaing the Mailman projects full-time, but it's a little frustrating to have your merge request open for a couple of months without any/much reaction to it... I try to keep my merge requests up to date and conflict-free, but having to do this for a couple of months, while there is no clear reason why it's not merged yet, is a little demotivating. In Postorius there have been (and there still are) merge requests by new contributors that were probably abandoned, because quite some time has passed since their creation... Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Docker files for mailman
Hi, I started working on docker files for Mailman. I created three repositories: - https://github.com/simonsmiley/postorius-docker Holds the files needed to create a postorius container - https://github.com/simonsmiley/mailman-docker Holds the files needed to create a core container - https://github.com/simonsmiley/mailman-compose Holds docker-compose files that greatly simply the process of running the containers * The mailman repo currently lacks documentation * Currently no emails can be sent. I still have to figure out what the best way is... * Hyperkitty will be added next (together with a complete "bundler" install) I pushed two images to the docker hub. Their names are thelinuxguy/postorius and thelinuxguy/mailman I created two organizations mailman on docker hub and gnu-mailman on github https://github.com/gnu-mailman https://hub.docker.com/u/mailman/ I know we shouldn't use github, but there is no way around github/bitbucket for automated builds on docker hub. I post here to inform you about the docker images and I also to ask if I'm allowed to keep these two organizations and move my images/repos there. I'll happily give push/owner access to additional people if requested. The repositories could be mirrored to the gitlab mailman group, sadly the process doesn't work the other way round just yet. In case this request gets denied, I'll just remove the organizations and let the images be "unofficial". cheers, Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Countdown to the 3.1 release
> Please take a look at any other bugs not assigned to milestone 3.1 and let me > know if you think any are serious enough to block the 3.1 release. I'll say > in advance that I'm going to be brutal in assessing them, because 3.1 really > needs to be released soon! I guess https://gitlab.com/mailman/mailman/issues/219 should be fixed in the next release. If 3.1 find its way into repositories, we will get lot's of issue reports for this I suppose. > Note too that there may be blockers for Postorius, Hyperkitty, and > mailman.client, but I haven't looked at those subprojects yet. How close are > they to being release ready? Terri was working on this one, it's not critical but nice to have for usability https://gitlab.com/mailman/postorius/merge_requests/159 I have a mr pending for mailmanclient that should be included in the next release https://gitlab.com/mailman/mailmanclient/merge_requests/10 Postorius has a number of merge requests open. I'm not sure which of them should be merged before the next release Does your template branch in core need any immediate modifications to mailmanclient and/or postorius? cheers, Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Postorius: Search Plugin for List
On 06/11/2016 11:14 PM, Khushbu Parakh wrote: > Hi, > I am working on search plugin for lists I think this would be a nice addition to Postorius. > and wondering what would be the best approach, > using Ajax or reloading the page and which JS files. > Do I need to write urls with the handler for JSON? > I have made the UI for search list. > What is the best way to approach. It depends. What functions would your search plugin support, how would it be used? I guess it also depends on what functions of mailmanclient you would use. Actually I think that neither mailmanclient nor core expose (efficient) methods that can be used to search for lists. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Postorius issue tracker labels
>>I'm not sure "rest" is the way it's currently being used either: it >might be >>more useful to rename it to be like the wait-for-mailman tag to >indicate bugs >>that occur due to mailmanclient. > >'wait-for-mailman' is just a little weird given that we use the term >'mailman' >for the whole umbrella project. 'wait-for-core' is a little better but >it >doesn't accurately describe blockers on mailman.client. >'wait-for-api'? I'm >also okay with leaving it as it us until/unless we figure out something >better. In most cases I think we would have to wait for both core and mailmanclient. Thats why I don't think we need two labels for it. In my opinion it would be better to have only one label and always link to an issue in mailmanclient and/or core ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3
On 05/17/2016 04:06 PM, Barry Warsaw wrote: > Hi Simon, > > On May 17, 2016, at 03:31 PM, Simon Hanna wrote: > >> I guess I could take some sort of lead on that. I played around a little >> with pootle and I really like it. It's easy to use, fast and anyone that >> registers can start translating. > > Just by way of comparison, have you played with Zanata yet? How would you > compare the two systems? I used Zanata, but found it not very intuitive to use. It's also painfully slow. I'm unaware of any big projects that use zanata. Well openstack does, but they use a self hosted version and that one is not faster. I'm not sure how Mailman 2 was translated, but I guess most of the translators did it offline. You can download translation files from pootle and later upload them. So anyone that doesn't want to translate in the browser, can still do it offline. > >> The main question would be selfhosting vs using gnu's hosted version. > > I'd really prefer not to self-host. I don't think we're a big enough > organization to commit to long-term maintenance. I'm not at all questioning > your eagerness, abilities, and availability, but life has a way of throwing > curve balls at us[*] and I worry about 5 years in the future if interests or > availability changes. Also, I wonder if we wouldn't be giving up some > economies of scale by sharing translation infrastructure with other projects. > >> If you want I can spin up an instance on my server and provide >> interested people credentials to play with. (existing demo instances >> don't allow adding/managing projects) > > If the i18n community wants to play with a pootle, I think that's fine. We > can certainly use it to compare against other services. > > From my perspective, I don't have too many requirements, other than that we > can upload .pot files and download .po files when it makes sense for the > project, which would be disconnected from the timeline for translators to > submit translations. Right now for MM2.1, Mark has to request updates timed > to his releases, and I really want to avoid that. IWBNI whatever system we > choose had nice git integration, but that's not required. With pootle you can always download a snapshot for a language. I don't think any of the translation software out there has a real git integration. > > My only other requirement is that whatever we choose be comfortable enough > that translators *want* to use it. As a pretty typical monolinguist, I'm > definitely not qualified to judge that. > > Cheers, > -Barry > > [*] Is that a euphemism that translates outside of North America? ;) If you watch American TV shows, you know that it's origin is baseball So If you give me the ok, I write the gnu pootle maintainers and ask them to create three projects for us. I guess we could add links in postorius and hyperkitty that request assistance with translation. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Authorization System in Core
On 05/22/2016 12:08 AM, Harshit Bansal wrote: > Hi Simon, > This is the discussion that I was referring to: > > Harshit Bansal writes: > > > I think the "Permissions Systems" would have nothing to do with the > > core. It would be related to Postorius. We will have to create a style > > model separately in Postorius which would store the style name and the > > user who created it. Then only the user who has created the style > > would be granted the permission to edit it. > > Stephen J. Turnbull wrote: > > Then there is no *permissions* system! For example, one project last > year created a Javascript client -- that would completely bypass the > "permissions" system as you describe it. You could imagine that style > changes are a "friendly users" feature, and so the "style owner" > system would be a *safety* feature of the Postorius UI rather than an > *authorization* feature of styles. But in an enterprise context (eg, > a virtual hosting service), I'm sure that users will think of it as an > authorization system. While at present it seems unlikely that there > would be multiple interfaces on one hosting service, you never know > what users will do[1]. Also, it would not be obvious to somebody who > installed the node.js Mailman client that they are likely bypassing > "security" as documented in the typical Mailman manuals and tutorials > that you would find on the web. > > Thanks, > Harshit Bansal > >>Hi, >>Earlier, while discussing the permission system for manging styles, it >>was >>decided that the permissions system should be enforced in the core >>rather >>than in the postorius since otherwise it can be bypassed(deliberately >>or >>undeliberately). But one thing that I think I forgot to discuss was >>that >>currently there is no authorisation system in the core and now I am >>unable >>to figure out that how could the permissions be enforced in the core >>without an authorisation system. >>Should I workout an authorisation system for the core first or enforce >>permissions in postorius only? After reading this and your proposal, I'm wondering why you want to add the permission system in postorius. You are storing the styles in core, and grant permissions based on list/domain/site ownerships. All this information is in core. Currently mailmanclient exposes everything, not caring about permissions. You have admin rights, whoever uses mailmanclient has to manage access on their own. We currently have @list_moderator_required that we use in postorius. We are not doing anything with domain or site owners, but they should be pretty easy to implement. While in theory it would be possible to enforce permissions in core about who is allowed to call specific rest calls, this would require a lot of changes. I'm not sure we want to go this way. There are some things in core, that suggest that this might come sometime. (Users have passwords and you can authenticate them) But I guess this is somewhat legacy and will be dropped sometime in the future. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Authorization System in Core
>Hi, >Earlier, while discussing the permission system for manging styles, it >was >decided that the permissions system should be enforced in the core >rather >than in the postorius since otherwise it can be bypassed(deliberately >or >undeliberately). But one thing that I think I forgot to discuss was >that >currently there is no authorisation system in the core and now I am >unable >to figure out that how could the permissions be enforced in the core >without an authorisation system. >Should I workout an authorisation system for the core first or enforce >permissions in postorius only? Can you elaborate a little more? What do you want to use the authorization for? Why isn't doing it in postorius safe enough? -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [Mailman-i18n] Translation of Mailman 3
On 04/21/2016 04:47 AM, Stephen J. Turnbull wrote: > -i18n removed, I'm not subscribed. > > Barry Warsaw writes: > > > We need a Mailman 3 translation champion, someone who understand > > the technical and more importantly, social issues involved, and can > > spend time and energy on helping bring a good story to fruition. > > I'm happy to give wide latitude to the champion to help shape a > > solution that works for us. Maybe that's you Simon? > > I can help somewhat, I know the technology, I have a "friend in the > business" (a lawyer buddy who's heavily invested in legal translation > software), I've been involved with the Mailman and Debian translation > communitiess in the past. But right now I'm "busy as Barry", and for > the near future GSoC is going to sop up most of my Mailman time. I guess I could take some sort of lead on that. I played around a little with pootle and I really like it. It's easy to use, fast and anyone that registers can start translating. The main question would be selfhosting vs using gnu's hosted version. GNU is using v 2.5. 2.7.3 is the current version which changed quite a bit. The newer version has some sort of revision support has the ability to add comments to translations. The biggest change is that adding new files/ updating them requires filesystem access in 2.7.3 So I think that GNU is going to stick to 2.5 for the time being. Selfhosting would have a couple of upsides * Easier access to generated po files (scriptable) * Easier upgrade of po files * More features (v2.7.3) pootle has a couple of features that I think are nice to have. * Offline translation support (they have a very nice peace of software called virtaal) * Terminology support (we provide recommended translations for common words) * Used by (big) organizations (mozilla, document foundation, ...) * Relatively fine grained permissions (users can get permissions based on languages as well as projects The trend seems to be to use self hosted pootle servers, at least mozilla and libreoffice do, there are probably more. I don't think selfhosting would be that hard. It's based on python+django and uses redis. If you want I can spin up an instance on my server and provide interested people credentials to play with. (existing demo instances don't allow adding/managing projects) ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Translating notifications raised by mailman-core in postorius
Hi, Currently Postorius handles form submissions like this: 1. Check to see if inputs are malformed, raise error if so 2. Submit to mailman-core and see what the response is. - ConnectionError: Mailman-core is unreachable, display error message - Success: Display some success notification - HttpError: This happens when mailman-core rejects the request for some reason. Currently the HttpErrors are passed without modification to the user in a notification. Postorius should have some way of translating these. We can't translate the raw messages because they sometimes contain specific strings like emails and it would require us to manually add the strings to the .pot files. Theoretically the core could translate the messages before passing them to postorius. This would require core to know about the language it should translate to. I don't think this is a very good approach because we would have to make sure we offer the same languages for core and postorius and I'm not sure how we would pass the languages to core... I propose core to return an error code with each request. That way postorius can add strings for all the errors that it cares about and translate them accordingly. This would require an api change. Since 3.1 would change the api anyway, it would be nice to include the changes there. What do you think of my proposal? Do you have a better idea? The specifics have to be worked out of course. Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Systers Mailman3
On 05/12/2016 01:06 PM, ADITI GUPTA wrote: > Hello, > I am Aditi Gupta. I got selected for GSoC'16 Systers Mailman Project. Congrats. > I cloned systers repositories of mailman3, mailmanclient, postorius and > hyperkitty from github. Their versions are OLD! It doesn't look like they contain any changes. You should consider creating forks on gitlab so you can keep up to date and submit merge requests once in a while. > Also, I cloned the postorius_standalone and > hyperkitty_standalone from gitlab for testing purposes. postorius_standalone and hyperkitty_standalone are synced with their respective repositories on gitlab. They don't care about versions and releases (for now, maybe for ever). You shouldn't use them with anything other than the master branches of the gitlab repos. > On running setup.py > in postorius_standalone , I am getting deprecation warning because > postorius of systers is using older version of Django. There is nothing to install in postorius_standalone. It doesn't even contain a setup.py Also if they are using an older version of django there is nothing we can do about it. We are currently supporting what django supports. That is versions 1.8 and 1.9. All other versions are considered insecure! I don't think anyone will support you with any forks of the main repository. You should follow the official wiki and adhere to it, if you want people here to help you. https://wiki.list.org/DEV/Home The setup instructions is probably what you are looking for https://wiki.list.org/DEV/SetupDevEnvironment > Also,I am getting "ImportError: No module named middleware". Use the latest versions, and if you still run into issues, I'll help you work them out. (You might want to try the irc first to see if someone is available) > This is the traceback : http://pastebin.com/D1c4XCHe Screenshots are pretty useless FYI. :-) Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Facing build Issues Postorius
On 05/07/2016 09:41 PM, Anirudh Dahiya wrote: > Hi > I updated my builds and am facing the following error : > InvalidTemplateLibrary: Invalid template library specified. ImportError > raised when trying to load 'postorius.templatetags.membership_helpers': > cannot import name MailingList > I tried building on my other machine and faced the same error. > Complete traceback : http://dpaste.com/3WG8XQ5 > Thanks > Anirudh > (irc spark) I guess it's caused by an out of date mailmanclient installation inside one of your virtualenvs. Can you try clearing them out? The issue is caused by the following import: from mailmanclient._client import MailingList This import should not be there. We should not import via "private" things. Currently the MailingList is imported for additional functionality, but it's not actually being used inside Postorius. I guess a safer option would be to use postorius.models.List instead. We should be using these classes inside Postorius anyway. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Translation
Hi, I just completed setting up the Mailman 3 projects on zanata.org They can be found here: https://translate.zanata.org/project/view/mailman https://translate.zanata.org/project/view/postorius https://translate.zanata.org/project/view/hyperkitty I'm hesitating to ask people to translate because zanata is really slow and I'm afraid of scaring people away from translating mailman in the future :D Anyhow, I'm writing to ask for your opinions. What do you think about zanata? Maybe you can try translating a couple of things and report how you feel about it. I stumbled across a few other open source solutions: https://translatewiki.net http://pootle.locamotion.org/ https://demo.weblate.org/ This mediagoblin issue discussed some alternatives when they switched away from transifex. https://issues.mediagoblin.org/ticket/913 There seems to be a pootle server run by gnu itself. https://chapters.gnu.org/pootle/ What do you think? Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Postorius and verified email addresses
On 04/10/2016 11:06 PM, Terri Oda wrote: > On 2016-04-06 4:29 PM, Barry Warsaw wrote: >> On Apr 07, 2016, at 12:26 AM, Simon Hanna wrote: >> >>> Short version: it supports both external (social) and internal >>> (django) auth >>> systems and offers options to combine/switch between them . Allauth >>> provides >>> Signals that I used to verify the addresses in Mailman. >> >> I think we have to decide how and where addresses will be verified. >> Are they >> going to be via confirmations emailed by core or via Postorius? >> >> I think the core has to support emailed confirmation messages because >> Postorius is technically an optional component. So if a site were to >> build >> their own REST front-end, they'd at least want to allow the core to >> handle >> email verifications without having to build that into their front-end. > > I'd prefer core to do it, so that it's consistent regardless of > front-end and there isn't duplicated work in every single web component > for Mailman, which is one of the reasons I haven't reviewed any of the > proposed Postorius code to do this. (The other big one being that I > need to do some research on auth libraries, because past experience has > told me that I rarely agree with Simon. ;) ) >From time to time I search for such projects, and I currently prefer allauth. That doesn't mean that I know it's the best solution, it's just the best one (in my eyes) I currently know of. Postorius is currently confirming emails on it's own. And Hyperkitty doesn't at all (the registration process doesn't attempt to confirm emails). ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Postorius and verified email addresses
On 04/07/2016 01:29 AM, Barry Warsaw wrote: > On Apr 07, 2016, at 12:26 AM, Simon Hanna wrote: > >> Short version: it supports both external (social) and internal (django) auth >> systems and offers options to combine/switch between them . Allauth provides >> Signals that I used to verify the addresses in Mailman. > > I think we have to decide how and where addresses will be verified. Are they > going to be via confirmations emailed by core or via Postorius? > > I think the core has to support emailed confirmation messages because > Postorius is technically an optional component. So if a site were to build > their own REST front-end, they'd at least want to allow the core to handle > email verifications without having to build that into their front-end. I don't mind the core being able to handle verfications. But I'm pretty sure everyone that offers a web interface for managing mailman will want the ability to confirm emails using http links. I don't see a reason why we should implement that in mailman, if it can easily be added in the front-end. Doing this has one downside in my opinion. Storing the same addresses in several places (which isn't bad perse, as a matter of fact microservices encourage duplicating data and synchronizing it) would need synchronization. Ideally mailman would offer signals for various events that front-ends can hook in to. They would probably be similar to the hyperkitty archiver plugin I guess. Another thing I believe in is blocking access until an account is confirmed, which really shouldn't depend on mailman. While postorius might be a project that should always have an active connection to the core, and archive doesn't necessarily need it. > > That doesn't necessarily prevent Postorius from doing it, and when used with > Persona, we see how nicely that can work. It's also of course possible that > any 3rd party front-end will have its own way of verifying email addresses. > > The other thing to think about is that the core already must know how to talk > to the outgoing MTA, to provide proper reputation services, signing, etc. I > don't know that we want to make site admins have to configure that in two > places, and we almost certainly don't want Postorius to send out emails > directly. Sorry but I have to disagree with that. Postorius _has_ to be able to send out mails. In case any server errors occur, django tries to send out emails to administrators defined in the settings. I strongly recommend setting this up for a production system. The mta should take care of the rest (dkim signatures, ...). If you are referring to gpg signing and encryption, there are django apps for that. A quick search revealed https://github.com/stephenmcd/django-email-extras I haven't tried it, but I don't think it would be that hard to integrate if the core supports them. There is one more issue that needs to be discussed which is relevant to all templates: Translation. Django has builtin methods to translate and through the browser's preferred language can choose one. The core would require associating a language with each user in the settings. >From a usability point of view I would like Postorius to be able to set all >templates and not just link to files in mailman. There are a couple of businesses that manage thousands of lists and I guess they would appreciate it if list owners could do this without direct access to the mailman server. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Postorius and verified email addresses
>In that case, how should this address be validated? Should Postorius >consider that the login system always validates addresses and set them >as >verified in Mailman? Should it ask mailman to verify the email >addresses >when it encounters a user's un-verified address? This does not seem >possible in REST at the moment (unless I missed it), and should be >protected against multiple checks. > >Ideas? I started a thread about this a couple of months back. I was asking about what authentication system to switch to, since persona is being dropped. I found a couple of solutions and have my personal favorite: django-allauth I have a merge request pending that adds basic functionality for it in postorius. I think that it's better than python-social-auth that hyperkitty is currently using. Short version: it supports both external (social) and internal (django) auth systems and offers options to combine/switch between them . Allauth provides Signals that I used to verify the addresses in Mailman. The link to my merge request: https://gitlab.com/mailman/postorius/merge_requests/130 The link to my previous post: https://mail.python.org/pipermail/mailman-developers/2016-January/025338.html -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Correcting the display name in the recipient address
Am 25. März 2016 18:16:09 MEZ, schrieb Mark Sapiro : >On 03/25/2016 06:06 AM, Aditya Divekar wrote: >>> >> My knowledge of anonymous mailing lists is a bit less. But from what >I >> understand, the address for the mailbox would not have a display name >for >> anonymity purposes whereas the user can have a display name, >importing >> which may cause anonymity concerns. > > >The purpose of an anonymous list is to hide the identity of the author >of a post. There is not a need on an anonymous list to hide the >membership roster. There should be the normal controls on the >visibility >of the roster, i.e. list owners only, owners and members only or public >(I'm not sure how this is handled in Postorius, I'm not up to speed >there), but that is not the concern. > Just for reference: postorius currently only allowed moderators to vies the members of the list. >The concern is that a post as archived and delivered to list members >should have nothing in it's headers (including things like From:, >Received:, Message-ID, etc.) that identify the poster or the poster's >domain. This is a function of the core. Postorius is not involved nor >are the archivers as the post has been anonymized before it gets to an >archiver. I don't know that much about email, but shouldn't each message contain a message ID? -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Gsoc'16 Project:GitLab/development tools integration
Note that these are my personal thoughts and nothing official. :-) On 03/21/2016 10:50 PM, Shubham Ghiya wrote: > Hello, > > My name is Shubham Ghiya, a 3 year undergraduate from IIIT-Hyderbad. > > I was going through the GSOC 2016 ideas and found "GitLab/development tools > integration" project interesting. > > I have setup the mailman and postorius and have tried my hand on some bugs > also.Right now,I am learning more about hyperkitty which will help me learn > more about the implementation details for the project.I have a good > understanding of functionality of various modules and how mailman works. I > have also read the chapter on mailman by Barry Warsaw to understand mailman > in a much better way. > > For the project "GitLab/development tools integration" I figured out that > we are expected to create a tool that will extract the contents of the mail > on a mailing list and create an issue of it on Gitlab/Github through > various Gitlab/hub API's and python libraries. > > 1. For the extraction part Hyperkitty will be used from where we can > extract and parse the contents of the mail. Please note that it should be a thread not just one message of a thread. > > 2. For creating an issue on Gitlab, different API's will be used which I > have to figure out yet. It would be nice if you design your project so that it can be used with different providers/API's. You could add supporting Github, launchpad, etc. to your stretch goals. > > I know the above points are a very naive and a basic approach. Please tell > me if I am thinking in the right direction and how to proceed further. I think the most challenging part is to implement a UI that let's the users decide what gets included in the issue and what not. (Which messages of the thread, which parts of a message, attachments, ...) As this is only targeted at lists used by developers it would be nice if the plugin for hyperkitty is optional meaning you don't need to have it installed at all and if you have it installed, you don't need to enable it for a list. There might be other practical ways to trigger the creation of an issue. For instance by including specific headers in the email or putting a special string in the subject. I don't think you need to do that, but if you want something challenging you can think about it. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] New lists at lists.mailman3.org
On 03/18/2016 10:25 AM, Odhiambo Washington wrote: > I try to login to test2 using google and I get Server Error (500). > > I can't use persona and I don't wanna use Yahoo! citing the previous mail: > Note that the login page offers Persona, Google and Yahoo for login, but > only Persona works Why can't you use persona? It's working for me ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] New lists at lists.mailman3.org
> Thanks, Florian, but why should I go that way when there is a link to sign > in with google, which I already have? > I have gone ahead and done that anyway, since I am curious about MM3. This server is not yet fully operational. That's why currently only persona works. > Are there people who have installed MM3 on FreeBSD? And integrated with > Exim? There was a merge adding something about exim, so it should work. Search the the archives and mailman docs. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Advice needed on Production MM3 install
On 03/16/2016 06:35 AM, Mark Sapiro wrote: > Some of you may have seen my posts on mailman-cabal, but I am installing > a production instance of Mailman 3 on lists.mailman3.org in order to > support initially a Mailman 3 users list. > > The first question is should it be mailman-us...@mailman3.org or > mailman-us...@mailman3.org. The former is more of a recognition that > Mailman 3 is now Mailman while the latter offers less possibility for > confusion with mailman-us...@python.org. Then, I suppose it could be > just us...@mailman3.org, but we might want to support other 'users' > lists in the future. The list names are the same, I guess you misspelled one. > The next thing is I'm having much more difficulty than I anticipated, > probably in large part because I haven't followed Postorius and > HyperKitty development that closely. I have lots of things I think I > should be able to do in Postorius and I can't and I don't know if the > issue is Postorius or my installation. > > I initially installed mailman-bundler from gitlab. configured it for > production, ran buildout and set it up. My initial issue is I couldn't > log in to Postorius at all. I had set a Django superuser, but I see > nowhere to authenticate as that. The only logins offered were Google, > Yahoo and Persona, and they all threw various but similar exceptions. Postorius enables local logins by default. Hyperkitty needs you to set USE_INTERNAL_AUTH = True in the settings file. Postorius has it's own login templates '/postorius/accounts/login' where you should always be able to login using a local account. Postorius only supports local and persona. Hyperkitty's templates are used by default, which add yahoo and google login, but will need tweaking the settings for local logins. About the other login methods. I only have persona enabled and haven't used the others. At least for google you will need to sign up for a client ID. I > With Abhilash's help, I got past some of that and I can now log in with > Persona, but there are still issues with the others[1]. > > In the process of working through that, I cloned the head of the mailman > branch from github and upgraded to that, but Postorius and HyperKitty > are still what bundler installed. Just in case you run into issues, you should probably use the git versions of Postorius, Hyperkitty and mailmanclient as well. > I got PostgreSQL, Postfix, openDKIM, nginx and gunicorn all configured > and that all seems good. > > In the process of working through some other issues, I enabled SSL in > Django with certificates I got from Let's Encrypt. That has led to a > current issue which is if a list's archiving is on, I can't post. The > post gets shunted in archiving because somewhere in the process the > runner tries to make an SSL connection to 127.0.0.1 and the certificate > is only valid for lists.mailman3.org, mirror.list.org and > mirror.mailman3.org[2]. I'm sure there must be a way to change the > connect to use lists.mailman3.org, but I don't know it. I ran into this issue as well. I had all of postorius and hyperkitty secured by ssl. So the link I used in mailman-hyperkitty (archiver plugin) started with "https" Hyperkitty a setting MAILMAN_ARCHIVER_FROM that defines which ips are allowed to use it's api to add to the archives. By default it only contains localhost addresses. You will need to add your external ip addresses, as the requests will all have your external ip. > Then perhaps my biggest issue is I can't do any admin tasks in Postorius > other than on my own lists. I can't create lists or domains or edit > domains or anything like that. I even set my user record is_server_owner > flag True, but that didn't help. I managed to do some of what I needed > via the mailman create and mailman shell commands, but I'm sure I should > be able to do that in Postorius, but I can't log in as superuser and it > doesn't seem to care that I'm a server admin. Maybe I need to upgrade > Postorius and HyperKitty. > > Which is the next advice I need. I'm thinking of trying to start clean > and I have questions. > > Is it better to use bundler and then upgrade what it installed or just > install the separate pieces and try to knit them together or should I > maybe just upgrade Postorius and HyperKitty in place as I did the core. > If I start clean will running the bin/mailman-post-update script > initialize all the data or will there be residue in the PostgreSQL > database that may cause problems. Running mailman-post-update multiple times shouldn't cause any issues. I like deploying things myself, so I know how to fix them if needed, I have a running production installation using git. (mainly because the released version of mailman doesn't support python 3.5) It's really not that hard to setup. It's mostly just python setup.py install or just using pip. I have a bunch of pkgbuilds for archlinux that might be helpful if you want to install it on your own. This one holds everything together: https://au
Re: [Mailman-Developers] adding to REST
On 03/14/2016 10:34 PM, treal tv wrote: > I might be misunderstanding you, Simon, but should I not be using Mailman 3 > built with the bundler > if I intend to modify/further build on the code? > > I've been working off one built with the bundler for the last couple months > and it's tolerated the > mods I made without issue but I'd rather switch to source built sooner rather > than later if it's > going to matter in the future. I'm unaware of any real downside to using the repo (unless you are a security fanatic and want stuff tested for a couple of years ^^) You can also use bundler with git repos. You'll just have to do run "python setup.py develop" for mailman in the python3 virtualenv that bundler installs. Note you will want to use the other repos as well, as there might be some incompatibilities. Now to why you should be using it: In case you want to turn in patches (merge requests) then having a repo is a must. And if you don't plan to turn in patches it's still useful. You can work on another branch than master and whenever upstream has new commits you can rebase them into your branch. That way you stay up to date without too much maintenance ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] adding to REST
On 03/14/2016 07:25 PM, Dominic Dambrogia wrote: > Hi, My name is Dominic. > I contacted this mailing list last week about list moderation and post > approval. My problem was not being able to set a list password via the REST > api. I need this for nonmember approval of posting to a mailing list via > email in the "Approved: *list password*" style in the first line of the > email like the default request for moderation email suggests. > > I'd like to go ahead and tackle this problem personally. I would appreciate > some insight on where to start looking in the project itself. I've only > installed the bundler and used REST so far, so my knowledge of how the > python code works so far is minimal. > > Any insight is greatly appreciated, thanks. > - Dominic If you want to actually develop mailman, you shouldn't use bundler for that. Check out the following two pages that help you with some git knowledge and setting up your dev environment. http://wiki.list.org/DEV/HowToContributeGit http://wiki.list.org/DEV/SetupDevEnvironment You should create an issue on gitlab https://gitlab.com/mailman/mailman/issues if there isn't one already. This issue can be used to discuss specifics about the implementation. You could try the irc channel #mailman on freenode for help in case you need something. You can of course also post to this list. All the code regarding the rest interface lives in src/mailman/rest I hope this get's you started, Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Interested in the GSoC idea 'GitLab/development tools integration'
On 03/11/2016 10:54 AM, Wasim Thabraze wrote: > Hi Abhilash, > > So the tool can be anything like web based thing, a module or a plugin?! Am > I thinking wrong? > > Before I can propose a way, I need your help in knowing more about the > project. > > 1. Can anyone use it or only the admin? I guess a good choice would be moderators or owners. > 2. The input to the tool is a thread from a mailing list. But how does the > tool actually take a thread from a mailing list? Hyperkitty? I guess Hyperkitty is a good place to put it in. The core functionality will (should) probably be reusable anyway. > 3. Are there any such tools in the software world that are more or less > doing similar work? (This query would help me in getting a clear cut idea > of the project.) You will have to use gitlab/hub apis. There should be python libraries to do that. There are some projects that create github issues out of email. Not sure if they are open source though... > > > Can you please give more information about the query #2?! Or can point me > to any links that would help me in getting a brief idea. In the end it really depends on what you want to do... ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Help regarding an error during installation
On 03/10/2016 04:18 PM, Daman Singh wrote: > Hello everyone! > > I am trying to install mailman for development using mailman-bundler. I > followed the instructions given here > http://mailman-bundler.readthedocs.org/en/latest/ , but i am facing a > problem. > When i run buildout command i get an error saying,"no module named 'zlib'" > but on running ipython, when i import zlib it works all right. > I am using a virtualenvironment. Basically module named zlib is already > installed but "buildout" command is still giving me error. > Anyone having its fix kindly provide me its fix I'm unaware of any dependency on zlib. If you want to install mailman for development please refer to this wiki page http://wiki.list.org/DEV/SetupDevEnvironment ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Guides for contributing to mailman
Hi, I took the liberty of updating a couple of pages on the wiki. Noticeable additions are the following two pages: http://wiki.list.org/DEV/HowToContributeGit which is intended to be a howto regarding git. It should cover the basics by giving example executions of commands. Real documentation and tutorials can be found easily on the web. This is also the place for code of conduct regarding gitlab commits/issues/merge requests. http://wiki.list.org/DEV/SetupDevEnvironment This are brief setup instructions for the mailman packages. It is not supposed to be complete or explain anything in details. readthedocs.org is a much better place for such information. I kindly request you to read through it and help improve it. I placed links on the top of the dev homepage http://wiki.list.org/DEV/Home It would be helpful if all "newcomers" are directed to these two pages when they ask questions about setting up. Feel free to add to the pages when you think more information is necessary of if people turn out to need more help with how to do stuff in git/gitlab Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman-bundler installation
On 03/08/2016 03:35 AM, Aditya Divekar wrote:
> Hi,
> I recently reinstalled my OS, ubuntu 14.04 , and was trying to get the
> development server for mailman running. (I had mailman running in my
> previous OS setup, but I had to reinstall my OS due to some python issues)
You generally don't want to reinstall an os. You should fix it. OTOH I'm using
archlinux, so it
might just be arch talking :D
> For this I was following the mailman-bundler documentation. After
Do you want to participate in development? Then _don't_ use mailman-bundler.
Mailman-bundler is for production setups and to just try it out.
Refer to the documentation of the projects on readthedocs.org on how to get dev
setups running.
> activating the python2.7 virtual environment, when I give the command to
> start mailman, I get an error.
> (venv) aditya@aditya:~/mailman-server/mailman-bundler$ sudo
> ./bin/mailman-web-django-admin runserver &
> [1] 3299
_Never_ ever run this using sudo
You should only use sudo to do administrative tasks on your pc. Do not run any
program that throws
errors using sudo. That might actually brick your pc and in the end require a
reinstallation
> (venv) aditya@aditya:~/mailman-server/mailman-bundler$ INFO Generating
> grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
> INFO Generating grammar tables from
> /usr/lib/python2.7/lib2to3/PatternGrammar.txt
> INFO Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
> INFO Generating grammar tables from
> /usr/lib/python2.7/lib2to3/PatternGrammar.txt
> Performing system checks...
>
> System check identified no issues (0 silenced).
> March 07, 2016 - 20:43:38
> Django version 1.8.11, using settings 'mailman_web.development'
> Starting development server at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
> /home/aditya/mailman-server/mailman-bundler/mailman_web/urls.py:7:
> RemovedInDjango19Warning: Default value of 'RedirectView.permanent' will
> change from True to False in Django 1.9. Set an explicit value to silence
> this warning.
> url(r'^$',
> RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))),
>
> WARNING /home/aditya/mailman-server/mailman-bundler/mailman_web/urls.py:7:
> RemovedInDjango19Warning: Default value of 'RedirectView.permanent' will
> change from True to False in Django 1.9. Set an explicit value to silence
> this warning.
> url(r'^$',
> RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))),
>
> Traceback (most recent call last):
> File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
> self.result = application(self.environ, self.start_response)
> File
> "/home/aditya/mailman-server/mailman-bundler/eggs/Django-1.8.11-py2.7.egg/django/contrib/staticfiles/handlers.py",
> line 63, in __call__
> return self.application(environ, start_response)
> File
> "/home/aditya/mailman-server/mailman-bundler/eggs/Django-1.8.11-py2.7.egg/django/core/handlers/wsgi.py",
> line 170, in __call__
> self.load_middleware()
> File
> "/home/aditya/mailman-server/mailman-bundler/eggs/Django-1.8.11-py2.7.egg/django/core/handlers/base.py",
> line 50, in load_middleware
> mw_class = import_string(middleware_path)
> File
> "/home/aditya/mailman-server/mailman-bundler/eggs/Django-1.8.11-py2.7.egg/django/utils/module_loading.py",
> line 26, in import_string
> module = import_module(module_path)
> File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
> __import__(name)
> ImportError: No module named middleware
>
>
> I tried checking for the solution online, but couldn't find a fix. I
> reinstalled django twice to ensure that the installation was thorough, and
> that all the libraries were installed.
> Has anyone faced this issue?
There is an issue over at postorius regarding this
https://gitlab.com/mailman/postorius/issues/107
You will have to manually fix it.
> Note - I am currently running django 1.9.4 in both python3 and python2.7,
> and have installed django 1.8.11 in the 'venv' virtual environment.
postorius and hyperkitty are currently python2 projects. So python3 will most
probably not work at all
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] CAPTCHA support
On 03/05/2016 11:57 AM, Aditya Divekar wrote: > Hi! > I was looking around the mailman code, and could not find the functionality > for captcha in the mailing lists subscription pages. > I think it could be a good feature to implement in the upcoming versions, > and would like to know if its a good idea? > I also came across the thread - > http://permalink.gmane.org/gmane.mail.mailman.user/74167 > and read about the previous discussion on it by some members. > Since captcha back then was easier to break, it might not have been a > profitable feature, according to the thread. > But with the new recaptcha, I would like to know if the stand is the same. The message you mentioned said that it might be because of lacking csrf protection. With django all the forms are protected by csrf. About captchas. If they are implemented, they would have to be optional in my opinion as they would require signing up for a token with the captcha provider. Or were you thinking about implementing your own service? I'm pretty sure there are django apps out there that add captcha support. It would be a nice addition if it's optional. If it's not I guess it would need more discussion. ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Accessing the members of a list
I just realized I didn't reply to the list but to the OP only. Here is my reply:
> CannotOverwriteExistingCassetteException: No match for the request
> ( http://localhost:9001/3.0/members/find?subscriber=%2Aexample.com%2A&list_id=foo.example.com&role=member>)
> was found. Can't overwrite existing cassette
> ('/home/hp/postorius_aditya/src/postorius/tests/fixtures/vcr_cassettes/ListMembersTest.test_search_members_1.yaml')
> in your current record mode ('once').
>
> Is this error because the request is not present in test cases or is it
> some other error?
> Also, if it is a test case problem, can anyone suggest me how to change the
> test case (or where I could read about how to go about it) to make the
> build pass?
It's because the request is not recorded in the mentioned yaml file.
In order to record tapes, you will have to have a running mailman instance. The
config file for
mailman can be found in the testing directory of postorius.
1. Make sure you have an empty mailman database (just remove everything that
mailman creates ^^).
2. You will want to delete the yaml file you want to overwrite.
3. run `tox -e record` in postorius.
Repeat steps 1-3 as long as you get errors (you will have to fix the errors of
course)
4. confirm that everything works by running `tox`
commit the yaml file you wanted to overwrite.
Sidenote: You might not have to rerecord the yaml file over and over if you are
only fixing things
that don't result in new/changed requests.
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Dropping Persona
> I just found another solution: django-allauth > http://www.intenct.nl/projects/django-allauth/ > http://django-allauth.readthedocs.org/en/latest/overview.html > https://github.com/pennersr/django-allauth > > It's a relatively large project. It has 2000+ stars and about 800 forks on > github. The other two I > introduced can't get these values when adding them together. > > About their functionalit quoting from their docs: > * Signup of both local and social accounts > * Connecting more than one social account to a local account > * Disconnecting a social account – requires setting a password if only the > local account remains > * Optional instant-signup for social accounts – no questions asked > * E-mail address management (multiple e-mail addresses, setting a primary) > * Password forgotten flow > * E-mail address verification flow > > They are basically supporting every OAuth provider out there > > They have more signals than the other two projects I introduced. Some of them > are: > * when a user signs up > * when a user adds an email > * when the user removes an email > > I didn't look at the code yet but I think they are only using emails and not > usernames. I just opened a merge request over at postorius https://gitlab.com/mailman/postorius/merge_requests/91 It includes basic functionality for django-allauth. All the included code should work, the merge request contains info about what still needs to be done. What do you think? ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Dropping Persona
On 01/29/2016 08:59 PM, f...@florianfuchs.com wrote: > > > On 2016-01-29 16:00, Barry Warsaw wrote: >> From a UX perspective, I do want to allow people to log into their accounts >> using any of their registered and validated email addresses. People very >> often forget just which address is subscribed to which mailing list, so it >> really shouldn't matter which one they use to get into their account. > > We should check out which external app allows for multiple emails to be set. > Or which ones allows > for easy customization to do so at least. > >> Further, I have a strong personal preference for "no user names", or >> alternatively, using email addresses as their "user name". I think user >> names >> are essentially contrived extra information for which there's no need, when >> clearly your identity is your email address. I liked this about Persona. > > I agree, especially since even though we now have HyperKitty, there will > probably always be many > folks whose interface of choice for Mailman is email, and who will not use > the interface very often. > Remembering usernames for sites you last visited 20 months ago is awful. I just found another solution: django-allauth http://www.intenct.nl/projects/django-allauth/ http://django-allauth.readthedocs.org/en/latest/overview.html https://github.com/pennersr/django-allauth It's a relatively large project. It has 2000+ stars and about 800 forks on github. The other two I introduced can't get these values when adding them together. About their functionalit quoting from their docs: * Signup of both local and social accounts * Connecting more than one social account to a local account * Disconnecting a social account – requires setting a password if only the local account remains * Optional instant-signup for social accounts – no questions asked * E-mail address management (multiple e-mail addresses, setting a primary) * Password forgotten flow * E-mail address verification flow They are basically supporting every OAuth provider out there They have more signals than the other two projects I introduced. Some of them are: * when a user signs up * when a user adds an email * when the user removes an email I didn't look at the code yet but I think they are only using emails and not usernames. I will try to integrate it in the next couple of weeks and see if we should create a sepparate app for that or do the work in both projects ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Dropping Persona
Hi, Mozilla is dropping Persona and shutting it down later this year [1]. Postorius and Hyperkitty will have to drop it, and use something else as a default login mechanism. I propose using the django authentication system by default and making it easy for people to add other authentication methods. If we go with django authentication we can either build everything ourselves (I did it for a couple of projects myself) or use some provided project. This is because django doesn't offer registration views and email confirmation. Also password changing and password resetting will have to be added. I know of two projects that do that already: django-user-accounts [2] It's part of the pinax platform, but can be used independently of the other components. It comes with everything we need and not much more. Note that the profiles of django-user-accounts can contain additional emails, which we probably don't want. It's officially supporting django 1.8 and 1.9. I'm not sure about our django dependency policy but since upstream has marked all pre 1.8 as being out of date, I think that we can move on as well... django-userena [3] Pretty much the same as django-user-accounts but it has additional "features" like messaging which we definitely don't need. It's not yet django 1.9 compatible but there is a merge request that adds support for it. Since we have two projects to maintain, I'd rather go with an external app. I guess it would be easiest to have exactly the same configurations for Postorius and Hyperkitty. In order to not duplicate any templates and other code, I'd propose to create a third project that has all the account functionality and put everything we need in there. In case we go with doing everything ourselves, I guess it's still better to create a separate app for that. My personal favorite is django-user-accounts for which I have some basic functionality in a merge request for Postorius so you can have a look at what needs to be changed. [4] Regardless of what approach we choose, we should also think of migrations. Existing internal django accounts can be easily migrated. We'll have to choose if we want to migrate the "social" accounts as well or just tell people to sign up again. We still have time for the transition, but I'd prefer dropping persona before the 3.1 release if that happens to come before the shutdown. What do you think? Simon [1]: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers [2]: https://github.com/pinax/django-user-accounts [3]: https://github.com/bread-and-pepper/django-userena [4]: https://gitlab.com/mailman/postorius/merge_requests/73 ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Availability as a mentor
Hi, (mainly for Florian, but it's not secret) Since I'm a student, I was thinking about applying for a GSoC spot this summer, but I'll probably not have the time for it, so I won't do that. I would however have enough time to be a mentor. (Google says about 5h a week per student, I could manage up to 10h I guess) The code of the mailman-suite I know best is postorius, so if a mentor is needed for that, I'm available. I could of course still manage mentoring other projects. A little bio: I'm a 24 year old computer science student, currently pursuing my master degree. I'm studying in Stuttgart, Germany. I'm fluent in English, German and Arabic (but I really don't like typing Arabic ^^) I was a tutor for about 8 different computing courses at my University. I was always responsible for a group of up to 20 students. My job was to help them with their assignments, grade them and explain stuff they didn't understand in the lectures. The courses included practical programming courses, programming languages, distributed computing and computer networks, algorithms and data structures, ... If you want to look at my code, you'll find most of it in postorius where my username is 'thelinuxguy'. So, if a mentor is needed, I'm available :-) Feel free to ask any questions... Simon ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Initial experiments with Mailman 3/Buildout
> Installing mailman-web. > Error: There is a version conflict. > We already have: pbr 1.8.1 > but lockfile 0.11.0 requires 'pbr!=0.7,<1.0,>=0.6'. It looks like lockfile does not actually need a specific version of pbr. https://bugs.launchpad.net/pylockfile/+bug/1506679 not sure though since I manually installed mailman signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] issues with MM3 / Apache mod_wsgi errors
> my server's apache postorius error log shows me: > > [Tue Oct 06 15:52:34.961249 2015] [:error] [pid 11691] (13)Permission > denied: [client :42590] mod_wsgi (pid=11691): Unable to connect to WSGI > daemon process 'hyperkitty' on '/run/httpd/wsgi.11685.0.1.sock' after > multiple attempts. > [Tue Oct 06 15:58:53.355159 2015] [:error] [pid 11693] (13)Permission > denied: [client :42654] mod_wsgi (pid=11693): Unable to connect to WSGI > daemon process 'postorius' on '/run/httpd/wsgi.11685.0.2.sock' after > multiple attempts. > > > MM3 components installed from hyperkitty-el.repo and using apache 2.4.6 on > centos 7. python 2.7 and 3.4 installed. Are you sure the sockets exist? If they exist, what are their permissions? Do they belong to the same user as apache is using? You might want to look at the wsgi logs as well to see if the python application is the culprit. You can check out my deployment instructions [1] using nginx and uwsgi. It might help you with debugging the issue [1]: https://gitlab.com/thelinuxguy/mailman-suite signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Mailman 3 packages for Archlinux
Hi,
I just finished packaging Mailman 3 for Archlinux.
I divided it into packages as follows:
mailman-core: the core mailman installation
mailman-django-git: a skeleton django project for serving hyperkitty and
postorius
python2-django-postorius: the postorius module
python2-django-hyperkitty: the hyperkitty module
python-mailman-hyperkitty-plugin: hyperkitty plugin for archival
python-mailmanclient: python bindings for rest api
python2-mailmanclient: python bindings for rest api
python2-django-postorius-git: the postorius module (git-version)
python2-django-hyperkitty-git: the hyperkitty module (git-version)
mailman-suite-git: A dummy package installing everyhing that can be installed
For the dependencies I choose to go with that:
mailman-core: optionally depends on python-mailman-hyperkitty-plugin
optionally depends on python-mailmanclient
optionally depends on python2-mailmanclient
mailman-django-git: optionally depends on python2-django-postorius-git
optionally depends on python2-django-hyperkitty-git
optionally depends on python2-whoosh
python2-django-hyperkitty: depends on python2-mailmanclient
python2-django-postorius: depends on python2-mailmanclient
I will push non-git versions of mailman-django-git and mailman-suite-git.
However, currently they wont work, as hyperkitty's change from {{ STATIC_URL }}
to {% static %} is
currently not yet released (just in master branch).
My mailman-django skeleton however requires {% static %}
Currently one dependency of hyperkitty isn't met yet, because
python2-django-compressor should be depending on python2-django-appconf.
However it's maintainer didn't add it. I am trying to contact him
and should resolve this within the next week.
The packages can be found in the AUR under this link:
https://aur.archlinux.org/packages/?SeB=m&K=thelinuxguy&O=0&PP=50
the whole dependency tree is as follows:
(it's probably not a complete list, but these packages should be present for
Mailman3 to work)
mailman-suite:
mailman-core
postfix
python-alembic
python-falcon
python-flufl-bounce
python-flufl-i18n
python-flufl-lock
python-httplib2
python-lazr-config
python-lazr-delegates
python-lazr-smtptest
python-mock
python-nose2
python-passlib
python-sqlalchemy
python-zope-component
python-zope-configuration
python-zope-i18nmessageid
python-zope-schema
python-zope-event
python-zope-interface
python-mailman-hyperkitty-plugin
mailman-django
python2-django-hyperkitty
python2-django
lessc (nodejs-less)
python2-dateutil
python2-django-browserid
python2-django-extensions
python2-django-compressor
python2-lxml
python2-django-appconf
python2-django-crispy-forms
python2-django-gravatar
python2-django-haystack
python2-django-paintstore
python2-django-rest-framework
python2-enum34
python2-networkx
python2-pytz
python2-robot-detection
python2-social-auth
python2-jwt
python2-oauthlib
python2-openid
python2-requests
python2-requests-oauthlib
python2-six
python2-mailmanclient
python2-django-postorius
python2-django
python2-django-browser-id
python2-httplib2
python2-mailmanclient
python2-whoosh
python-setuptools, python2-setuptools and git needed for building the packages
signature.asc
Description: PGP signature
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Let's try to package mailman3 in Debian!
On Fri, Sep 11, 2015 at 11:26:44AM +0900, Stephen J. Turnbull wrote: > Pierre-Elliott Bécue writes: > > > It seems that if I want to have a good source package, I need 5 repos : > > > > - Mailman > > - HyperKitty > > - Postorius > > - HyperKitty - MailMan Plugin > > - MailmanClient > > In the spirit of the refactoring, I would say mailman-core (mailman + > mailmanclient), hyperkitty, and postorious should be three separate > packages in Debian. Exactly which repos are needed, I'm not sure. Actually mailman-core is fully functional all alone. - I would make a mailman-core package, everything depends on that - mailmanclient would be a package providing the python bindings - postorius would be a package depending on mailman-core and mailmanclient - hyperkitty would be a package depending on mailman-core and mailmanclient, it should also inlcude the hyperkitty mailman plugin - mailman-deploy (or some other name) would contain a django skeleton project. It would have optional dependencies on postorius and hyperkitty. - mailman-suite would depend on all of the packages > > On another way, I also see that there is a standalone postorius repo and > > also some django project files for HyperKitty in another one. I have the > > impression it is more designed for people to work on as standalone - > > forkable projects for other features, and so I wouldn't need them in a > > Debian package. > > No, IIRC these are variants which don't need a separate webserver such > as Apache (convenient for testing), but they're still closely tied to > mailman core and mailmanclient. All django projects can be run without a separate webserver. However, this should _not_ be used in production enviornments. I am deploying several django projects using nginx and uwsgi, works like a charm. I would either link to or provide documentation about different options for deploying django projects. Anything applicable to django is applicable to postorius and hyperkitty Since postorius and hyperkitty are django apps, you are going to need a django project to deploy them. The *_standalone repositories are such projects to deploy postorius or hyperkitty. In a production environment you would probably want to have both in one django project. I would provide a skeleton with comments about what options need to be changed to get to a sane production system. I am currently working on writing such a project skeleton that would be able to deploy postorius or hyperkitty or both. I will publish a repo on gitlab when it's functional signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] User-centric authentication and access control
On Tue, Sep 01, 2015 at 09:02:00PM -0400, Waldbieser, Carl wrote: > > I am currently using Mailman 2. > If Mailman 3 provides the features I am interested in, that would be great, > provided there is some kind of well-defined upgrade path. AFAIK the official statement is that Mailman 3.1 will provide upgrade paths from 2.x I would wait for the 3.1 release... > I am a bit confused as to what the various components in Mailman 3 are. Is > the web interface to Mailman 3 based on Django? Is that Postorius? Correct. Mailman itself is just the core. The core exposes a REST interface. There is a client implementation for python (mailman-client). A Nodejs client is in the works AFAIK. You can use these to build your own UI. Or you could use postorius for that. It is based on django and uses mailman-client to interact with the core. > And if Django is allows you to do user management, where does Mailmania fit > into that landscape? > > Would I be correct in assuming that if I wanted to use say, CAS > authentication for Mailman 3, I could just use a Django middleware like this? > > https://bitbucket.org/cpcc/django-cas/overview That is probably correct. I personally have not yet included other authentication backends to django, but the process should be rather easy. Django has ver good documentation online. Including an LDAP backend should be standard enough for numerous tutorials to be out there. You just have to search for integrating different Backends into postorius. Postorius itself is actually doing this. Persona is used as the main Authentication Backend. Hyperkitty (yet another module) which is responsible for serving Archives of Lists even includes more Authentication Backends. That code should show you what you need to do, to add further Backends. signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] User-centric authentication and access control
On Tue, Sep 01, 2015 at 11:15:47AM -0400, Waldbieser, Carl wrote: > I know that currently, mailman roles are set up such that the roles > themselves have a shared password per role. I want to be able to move away > from that model and have roles assigned to individual user accounts that > would allow access to the admin interfaces for individual lists. > > For example, say we have mail lists "Campus" and "Board of Trustees". I > might have roles "campus_moderators", "campus_admins", > "boardoftrustees_moderators", and "boardoftrustees_admins". > If I assign the role campus_admins to user "johnsmith", I would like this > user to be able to access the mailman admin interface for the "Campus" list > using his own credentials. Ideally, "johnsmith" would not have to present > his primary credentials to the mailman interface because our institution has > a web single sign-on infrastructure (Web SSO). > > I would like to actually move the authentication and role management > *outside* of mailman and have the administrative interface consume the role > based information from external sources (e.g. LDAP, CAS or SAML2 attribute > release), so I am looking for a more "pluggable" authentication and access > management architecture. > > Does anything like this exist for Mailman, or is it on the roadmap? Are > there technical guidelines for how one might contribute toward something like > this? Are you using Mailman version 2 or 3? From your mail mentioning single moderator password, I suspect version 2. In postorius (Mailman 3) you can add moderators and owners, these will have access to the administrative options. About LDAP: You just have to add another authentication mechanism in django. You will just need to provide an email address for every user. signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Why is postorius using python2?
Hi there, 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. Simon signature.asc Description: PGP signature ___ Mailman-Developers mailing list Mailman-Developers@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
