Search results for "Postorius" - Mailman-users

Re: How to set up mailman 3

by Mark Sapiro

On 03/25/2017 04:23 PM, David Krantz wrote: > > I did get things working with the bundler at last. Quite tricky and I have > deactivated archival. But I suspect that I should retrace a bit of that > work and upgrade to the latest versions. I miss a few functions from > mailman2, especially setting a limit for message size to discourage sending > larger files to the list. I also notice that there are no modbits per user > that I can reach from the web as admin. See <https://wiki.list.org/x/17891998> for help in upgrading your bundler install. The lack of the ability to set a member's moderation option from the web UI is fixed in versions later than installed by bundler. Also see <https://gitlab.com/mailman/postorius/issues/127> A list's message_size can't currently be set in Postorius. File an issue at <https://gitlab.com/mailman/postorius/issues/new>. >> Where did you find out about the bundler? I'd like to make sure we steer >> people to the current best recommendations: > > The documentation can be found on several places. The one that is best > formatted is this one. I used a worse formatted version of the same text > but right now I cannot find the link. > > https://mailman-bundler.readthedocs.io/en/latest/ > > I notice that you changed the text on the githlab project. Better. > > Now I have no idea of how upgrading the different components. I might start > from scratch although it probably should be possible to upgrade the parts. > The best option is probably to switch to mailman2, but that has > disadvantages when handling lists for multiple domains if I am correctly > informed and I already have a few domains... See <https://wiki.list.org/x/17891998>. > I also found that sending mails manually (telnet to port 25) with no > headers other than "Subject:" causes the "Held messages" tab to crash with > a 500-error. Log below my signature. This is fixed: <https://gitlab.com/mailman/mailmanclient/merge_requests/16>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

Re: Message Sent to A Re-Created List Results In Error

by Stephen J. Turnbull

Abhilash Raj writes: > > > On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us wrote: > > I created a list in the Postorius interface, used it, and then > > deleted it. A week or so later, I re-created the list, and things > > were fine thru the creation and subscription process. But when I > > sent a message to the list, a "550 user unknown" error was sent > > back. > > Can you share more error details from the Mailman logs? If 550 > error response was sent, there must be some internal error > traceback in the logs. Also, be sure to tell us which MTA (mailserver) you use, and you should check the MTA configuration files to make sure the deleted and recreated list would be recognized.

4 years, 11 months

Telling Mailman/Hyperkitty where sass is

by Erin Justice

Hi all, Another issue that's cropped up when I am trying to run Mailman 3 on apache. I've downloaded and installed Mailman core, Django, Postorius & Hyperkitty. I'm using the mailman-suite django project from https://gitlab.com/mailman/mailman-suite/tree/master <https://gitlab.com/mailman/mailman-suite/tree/master>. When I run the site using Django's development server everything works. However when I run the site from apache it's not finding sass. Specifically I'm getting errors like: FilterError at /accounts/login/ /bin/sh: sass: command not found I triple checked that sass is installed which sass /Applications/MAMP/Library/bin/sass /Applications/MAMP/Library/bin/ is in $PATH when I checked that and I was thinking that it maybe wasn't getting to python properly. However pprint(sys.path) contains the same items whether I start the site from the dev server or apache. Any pointers would be appreciated. -Erin

8 years, 4 months

Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 18:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > > > What I called "local admin" should have > > rights to add and remove members of, say, the poodle-regionA mailing > list. > > > By "local admin", do you mean "list owner", i.e., a list owner should be > able to see her own "hidden" lists. > > Is that what you mean, or to you envision some new category of user that > has more access than a list owner? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > I mean "list owner"

7 years, 10 months

Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote: > Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. > Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. > The imported members and other settings are correctly shown in the postorius page. > Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: Mailman 3 Status Update Please?

by Barry Warsaw

Hi David, On Jan 31, 2017, at 06:24 PM, ddw David Wilson wrote: >I have been eagerly looking forward to a comprehensive install script for >Mailman3 since the originally stated target date of Aug Sept and wondered if >any new dates have been proposed? We're very close I think. Core is essentially done. I've made a pass through the Postorius, HyperKitty, and mailmanclient milestones and there's not a lot left, but both of the former two could probably use some help getting to the finish line. I'm going to spend some time on mailmanclient. gitlab.com is down right now so I can't provide any links. >Furthermore, I wonder if either of the two following projects have been >proposed for Google Summer of Code applications: > >1) the afore mentioned comprehensive install script for Mailman3 on various >targeted hardware; and/or; We've been debating about the best way to do this, and right now the only thing we can agree on is that mailman-bundler needs to go away. ;) We know we want distro packages, but that's a longer term prospect. I suspect we want some container-based deployment options too, and I know that there are several dockerfiles floating around, but none are currently blessed officially. It's possible we won't have one single official deploy method, but instead we'll encourage experimentation and help to promote the best options in the short term, perhaps with adoption in the longer term. I don't have a more solid answer than that, but I highly encourage anybody who has an interest in this to come to mailman-developers@ and help us get there. >2) updated for Python 3 and the latest P3 compatible Django utilities for >archiving and email list collection, along with any new appropriate features? That's a great question for the Postorius and HyperKitty folks. Core is Python 3 already (and only), while P and HK should support both on Django. mailmanclient is and will remain bilingual. >Many thanks in advance for all your efforts in this extremely worthwhile OSS >project. Thank! We have a small team of core developers, but they are really awesome. And of course, we welcome new contributors! Cheers, -Barry

8 years, 10 months

Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Odhiambo Washington writes: > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > > only thing I can think of is an Apache rewrite rule. It's not in the > > Postorius and HyperKitty templates. > > And I do not have any rewrite rules in my VHOST config: > > https://pastebin.ubuntu.com/p/9MRMJST9zZ/ Is there a mod_wsgi.conf file? I've never seen this "mysterious" insertion of "/mailman3" in URLs. I'm trying to imagine where mod_wsgi would get it from, and just can't think of why that would be in mod_wsgi or its .load or .conf files in the Apache config. The maintainable place for URL configuration is the main apache.conf or a site-specific include file such as sites-available/mailman.conf. I guess it could be in an instance-specific configuration file or stanza of uwsgi to create a namespace. Steve

2 years, 11 months

Re: [Mailman-Developers] Docker files for mailman

by Danil Smirnov

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/ > mailman-developers%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman- > developers/danil%40smirnov.la > > Security Policy: http://wiki.list.org/x/QIA9 >

9 years

Patch/kludge suggestion and a question on adding accepted addresses

by David Krantz

Hi. I found out that I had a broken email in one of my held messages queues). That gave a HTTP 500 error although that should be fixed . After some digging I found out that where the error occured. I'd suggest adding a catch for AttributeError similar to the one for KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my immediate problem at least. I run the version from git with the tag 263711b3b7988c7c474e3b8952dc7e0f02f04fa2 The message causing this was probably one where I had sent a minimal email via telnet to the SMTP port and forgot the MessageID-header or something similarily silly. But it prevented me from seeing the held messages-list in postorius. I have another question: In the old mailman you could add accepted senders without adding them to the list. Is that possible in Mailman 3/Postorius? cheers. // David

8 years, 7 months

No path configuration found: paths.master

by Pierre Abbat

I installed postorius and hyperkitty with pip and ran into another problem. I ran "mailman info" and got "No path configuration found: paths.master". I have three files named mailman.cfg: /etc/mailman.cfg /usr/local/lib/python3.5/dist-packages/mailman/config/mailman.cfg /var/etc/mailman.cfg The one in /etc contains the following: [mailman] layout: master The one in /var/etc is completely commented out. If I move the one in /etc/ out of the way and run "mailman info" again, I get this: GNU Mailman 3.1.0 (Between The Wheels) Python 3.5.2 (default, Sep 14 2017, 22:51:06) [GCC 5.4.0 20160609] config file: None db url: sqlite:////etc/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass It said "config file: /var/etc/mailman.cfg" before. What changed? Pierre -- La sal en el mar es más que en la sangre. Le sel dans la mer est plus que dans le sang.

8 years, 1 month

Mailman-users search results for query "Postorius"