Search results for "Postorius" - Mailman-users

Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 11 months

Re: Adding / manipulating users

by Mark Sapiro

On 11/18/19 6:15 AM, Seth Seeger wrote: > > My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. You are correct that there is no existing command line tool or Postorius way to do this. If you have facility with Python, you can look at the mailman import21 command which is actually processed by mailman/utilities/importer.py. It shouldn't be too difficult to adapt the part that imports the list members to use your data and create a script to do what you want. Alternatively, you could create a script that would post the appropriate transactions to add a member and set moderation and delivery status to Mailman's REST API and use that to process your members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users]Re: Installation issues

by Mark Sapiro

On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > > I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? Sort of, but it's not (yet) public. The process I followed is very convoluted and not what I would recommend anyone follow. Part of the issue is I started with mailman-bundler not using a venv, but bundler still installs a lot of stuff in Python 2 and Python 3 venvs. I then proceeded to install the git master branches of mailman, mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their dependencies system wide and ripped out most of the venv stuff. Then there were issues because I'm running django 1.9 only and that's not compatible with django_haystack 2.4.1, so I upgraded that to 2.5.dev0 from GitHub, but that now has a compatibility issue with HyperKitty which I have worked around. As you can see this is not a clean process. If I were starting over with what I've learned, I'd probably let bundler install it all in venvs and then upgrade the venvs to the git master branches. There would still be issues, but it would be cleaner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 4 months

Re: User integration with Django application

by Abhilash Raj

On Sat, Sep 21, 2019, at 12:06 PM, Victoriano Giralt wrote: > Hi! > > Is there a way to integrate Mailman3 user database with an already existing > Django application? And then, generate the list roster with a subset of > those users. > > I've been scavenging the archives and failing to find an answer. You can set AUTH_USER_MODEL = 'customauth.MyUser' From Django's docs at https://docs.djangoproject.com/en/2.2/topics/auth/customizing/#specifying-c… Postorius and Hyperkitty should be able to use this user model, in theory. No one has tried this yet and there could be things that don't work. Although, I would be happy to accept any patches should there be any bugs related to this. Abhilash > Thanks! > -- > Victoriano Giralt CIO > University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. > > Q: Are you sure ? > >> A: Because it reverses the logical flow of conversation. > >>> Q: Why is top posting annoying in email ? > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

5 years, 10 months

Re: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/17/24 12:06 PM, Keith Christian wrote: > The path to the mailman3.py file is: > /home/mailman3/mailman/src/mailman/bin/mailman.py > I created a mailman3 user, then, set the ownership on all directories > and files in /home/mailman3 and below to mailman3:mailman3. You need to install all the dependencies and also have /home/mailman3/mailman/src/mailman in your PYTHONPATH. If you just want Mailman Core and given that you've already cloned it from gitlab, I suggest creating a Python virtual environment as the mailman3 user with `python3 -m venv /path/to/your/venv` and then as the mailman3 user activate the venv, `source /path/to/your/venv/bin/activate`, and do `pip install /home/mailman3/mailman` to install Mailman and it's dependencies in the venv. Then you can just run `mailman info`. I suggest a venv for this to isolate the dependencies from things that might already be installed system wide with differing versions. To install the whole suite including the Postorius web UI for list management and the HyperKitty archiver, see https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: how do I bulk-remove users from ML in MM3?

by tlhackque

On 25-Oct-17 12:05, Simon Hanna wrote: > Postorius is currently using this to mass unsubscribe. > AFAIK there is an open issue in core to add such functionality Yes, see https://gitlab.com/mailman/mailman/issues/419 Yes, the current API has a number of scaling issues. Delete is bad, but other operations can require multiple API calls... (e.g. get state to conditionally create; create+patch; create user+create subscription, ...) https://gitlab.com/mailman/mailman/issues/367 (and others) Mass modify is also missing - https://gitlab.com/mailman/mailman/issues/241 notes one such case. > On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >> On 10/25/2017 07:35 AM, Barry Warsaw wrote: >>> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >> wrote: >>>> I just realized that "mailman members" only offers to "add members" >> via >>>> "-a filename" but I see no remove option. >>> It’s true, `mailman members` doesn’t currently have a —remove option. >> I found Rest API call for single user removal but I am questioning it's >> effectiveness given that I need to use this operation to potentially >> remove 1500 members >> >> -- >> Sr System and DevOps Engineer SoM IRT

7 years, 9 months

Re: Message-Footer after migrating to Mailman3

by Stephen J. Turnbull

Peter Münster writes: > On Thu, Sep 01 2022, Stephen J. Turnbull wrote: > > I'm not very familiar with Django's handling of such files, > > I don't think, that Django is involved here. Ah, you're right. My GSoC student is working on Postorius so I have Django on the brain. > My language setting is "fr", so I've copied templates/site/en > templates/site/fr and now it works. > > So no real problem, but the question remains: why did it not work > with "en"? The template to be used is determined by the language setting of the user, or the default if the user is anonymous. You have to repeat the process with all of the templates that might be used on your system due to users' language settings. Presumably it *would* have worked for any user whose language setting was "en". But if you do have "de" users, you'll need to replace the "de" template as well. If you mean that you switched your language setting to "en" or have an "en" user, and tested it, we can take a look at it, but as I understand the situation, you have a "fr" setting so you saw the "fr" template. Steve

2 years, 11 months

Re: mailman import21 passwords

by Mark Sapiro

On 9/16/24 16:25, Sam Darwin via Mailman-users wrote: > > Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? > (is there a link to where this is already explained? ) Mailman 3 users have a _password attribute which isn't actually used for anything. The importer used to set this from the MM 2.1 member's password, but this was dropped by <https://gitlab.com/mailman/mailman/-/merge_requests/565>. See <https://mail.python.org/archives/list/mailman-developers@python.org/thread/…> for a discussion of this. Also note that since member passwords were stored in plain text in MM 2.1 and periodically emailed, those passwords are inherently not secure and have possibly been exposed so setting that password, even though encrypted in MM 3, is not a good idea. As far as creating a Django user for an imported member, whether or not with the member's MM 2.1 password, it is at least as expensive as just encrypting the password and would result in poor performance. Further, and perhaps more importantly, Mailman 3 is modular. There is no guarantee that any Mailman Core installation into which a MM 2.1 list is imported actually also supports Django users for Postorius and/or HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/4/22 11:15, gordon(a)dickens.com wrote: > > 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 > 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 > > So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: It's not the alias for static > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > # ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > </IfModule> It's the fact that ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost is commented out. This should not be commented assuming you are using uWSGI and it is listening on the socket /run/mailman3-web/uwsgi.sock -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: [Mailman-Developers] Docker files for mailman

by Danil Smirnov

Okay I've found that image can be built if you base on Ubuntu Trusty distro (line 6 of the Dockerfile: "FROM ubuntu:trusty") and add ruby-sass to the set of packages to install (line 13: "apt-get install -y git python3-dev python3-pip python-dev python-pip python-virtualenv ruby-sass"). I'm not sure whether I need to change it in the Wiki... On 18 November 2016 at 16:08, Danil Smirnov <danil(a)smirnov.la> wrote: > Hi Simon! > > I've just tried to build docker image from the Dockerfile mentioned on page > https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Dockerfile > > The building has stopped with the following error > > Installing mailman. >> The executable python3.4 (from --python=python3.4) does not exist >> /tmp/tmpez1ftK/run: 2: /tmp/tmpez1ftK/run: /mailman3/mailman-bundler/venv-3.4/bin/pip: >> not found >> While: >> Installing mailman. >> >> An internal error occurred due to a bug in either zc.buildout or in a >> recipe being used: >> Traceback (most recent call last): >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 1995, in main >> getattr(buildout, command)(args) >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 666, in install >> installed_files = self[part]._call(recipe.install) >> File "/usr/local/lib/python2.7/dist-packages/zc/buildout/buildout.py", >> line 1410, in _call >> return f() >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 56, in install >> self.execute() >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 69, in execute >> run_commands(cmds, self.shell) >> File "/mailman3/mailman-bundler/eggs/collective.recipe.cmd-0. >> 11-py2.7.egg/collective/recipe/cmd/__init__.py", line 39, in run_commands >> check_call('%s %s' % (shell, tmpfile), shell=True) >> File "/usr/lib/python2.7/subprocess.py", line 541, in check_call >> raise CalledProcessError(retcode, cmd) >> CalledProcessError: Command 'sh /tmp/tmpez1ftK/run' returned non-zero >> exit status 127 >> The command '/bin/sh -c buildout' returned a non-zero code: 1 >> > > Do you have any clue what happens? > > Danil > > > On 17 July 2016 at 20:06, Simon Hanna <simon.hanna(a)serve-me.info> wrote: > >> 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(a)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/ma >> ilman-developers%40python.org/ >> Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/ >> danil%40smirnov.la >> >> Security Policy: http://wiki.list.org/x/QIA9 >> > >

8 years, 9 months

Mailman-users search results for query "Postorius"