Search results for "Postorius" - Mailman-users

Re: Where is the site to translate HyperKitty?

by Mark Sapiro

On 9/25/18 11:17 PM, Ooyama Yosiyuki wrote: > I think that mailman website is not clear where the translation will be done even if reading the page ? > > http://www.gnu.org/software/mailman/index.html > > Even looking at "Developers" page, I can not find the translation phrase. > > Are you going to leave this problem? Are you planning not to internationalize? Is not ? Yes, we are planning to internationalize all of Mailman 3, but we have been focusing more on other issues and also trying to find an appropriate translation site. We have just started a project at <https://hosted.weblate.org/engage/postorius/> for Postorius. We have nothing for HyperKitty yet, but would welcome your help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

Re: Template - "You can use these variables in the templates" - The variable for "leave" is missing

by Mark Sapiro

On 11/3/23 01:28, Wikinaut wrote: > I suggest to add this is as a new variable $leave_email . > > By the way: how can I access the _short_ list description text as a variable? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information on the variables that can be used in templates. There you will see the variable for "the mailing list’s short description text" is `description`. This is missing from the list displayed in Postorius which needs updating for this and other reasons, e.g. $hyperkitty_url is only available in regular headers and footers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Re: Mailing list welcome message won't update

by frances.du＠uq.edu.au

Hi Mark, I have a dev mailman server that is having the same problem too. (When updated the welcome text file, then subscribe to the mailing list but still get the old welcome message.) The dev mailman instance is much newer: GNU Mailman 3.3.9 (Tom Sawyer) Postorius Version 1.3.13 I also found that the actual file containing the welcome message and footer message does not have the .txt extension for my dev instance. root@mailman-dev:/var/lib/mailman3/templates/lists/[redacted].mailman-dev.dev.aws.[redacted].org.au/en# ll total 12 drwxr--r-- 2 mailman operations 4096 Jan 22 14:14 ./ drwxr--r-- 3 mailman operations 4096 Oct 1 13:50 ../ -rwxr--r-- 1 mailman operations 0 Oct 1 13:50 list:member:regular:footer* -rwxr--r-- 1 mailman operations 506 Jan 22 14:12 list:user:notice:welcome* What is that * at the end of the file name mean? Thank you. Frances

1 year, 8 months

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

9 years, 5 months

Re: Question about lists and domains on Mailman 3

by Jeff

I believe that you need to add "FILTER_VHOST = True” to your “settings.py" > On Dec 29, 2021, at 5:11 AM, Philip Colmer <philip.colmer(a)linaro.org> wrote: > > I've got a single server hosting multiple domains. I've got Apache working > as the proxy in front of MM3. > > Regardless of whether I go to https://lists.domainA.org/mailman3/lists/ or > https://lists.domainB.org/mailman3/lists/, Postorius lists ALL of the lists > across both domains. > > Is there a way of configuring the system so that, if a user goes to "domain > A", only the lists for that domain are listed? > > Thanks. > > Philip > _______________________________________________ > 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/

4 years, 8 months

API errors making member changes to one list but not others

by Stephen Willey Mats Mats

We had an issue with the UI getting API timeouts for a single list for specific functions but not other lists or other functions. This started happening after we accidentally filled the disk partition used by most of the system including the database. There was a single person testing at the time when the disk fullness happened and it was only the single list that got ‘damaged’. After disk cleanup and restarting the docker images the single list would give API errors ("HTTP Error 400: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5)” ) on the screen and logged errors (below) when list members were either subscribed or removed. The issue was repeatable in Postorius and did not ‘heal’. Oddly the issue was resolved by making seemingingly the same API calls from the command line via curl. Making the below call to add a member succeeded and fixed being able to add members in the UI. Similarly sending a DELETE cal from curl worked where unsubscribe requests from postorius (either mass removal or picking addresses from the list member and unsubscribing selected) failed. Again, the unsubscribe from the curl DELETE call ‘healed’ the list such that subsequent unsubscribes in Postorius worked. curl --user user:password -X POST -d 'list_id=laura-test.mm3.aca-aws.s.uw.edu' -d 'subscriber=ssw(a)uw.edu' -d 'pre_verified=true' -d 'pre_confirmed=true' -d 'pre_approved=true' http://172.19.199.2:8001/3.1/members We’re running the current rolling docker images (up to date as of 25Jan2021) Obviously, people should run their servers better than letting disk partitions fill-up but it’s going to happen and mailman3 should do a better job of reporting errors and recovering when accidents happen. thanks, steve I’ve included mailman.log lines from going to the mass subscribe [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 434 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:42:49 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:01 +0000] "GET /3.1/lists/laura-test.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 434 "-" "GNU Mailman REST client v3.3.2" Jan 26 20:43:07 2021 (48) deque: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 426, in _make_request six.raise_from(e, None) File "<string>", line 3, in raise_from File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 421, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.8/http/client.py", line 1347, in getresponse response.begin() File "/usr/lib/python3.8/http/client.py", line 307, in begin version, status, reason = self._read_status() File "/usr/lib/python3.8/http/client.py", line 268, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.8/socket.py", line 669, in readinto return self._sock.recv_into(b) socket.timeout: timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 439, in send resp = conn.urlopen( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 724, in urlopen retries = retries.increment( File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line 403, in increment raise six.reraise(type(error), error, _stacktrace) File "/usr/lib/python3.8/site-packages/urllib3/packages/six.py", line 735, in reraise raise value File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 428, in _make_request self._raise_timeout(err=e, url=url, timeout_value=read_timeout) File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 335, in _raise_timeout raise ReadTimeoutError( urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/usr/lib/python3.8/site-packages/mailman/app/subscriptions.py", line 343, in _step_do_subscription self.member = self.mlist.subscribe( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 507, in subscribe notify(SubscriptionEvent( File "/usr/lib/python3.8/site-packages/zope/event/__init__.py", line 32, in notify subscriber(event) File "/usr/lib/python3.8/site-packages/mailman/app/membership.py", line 176, in handle_SubscriptionEvent send_welcome_message(mlist, member, member.preferred_language) File "/usr/lib/python3.8/site-packages/mailman/app/notifications.py", line 51, in send_welcome_message welcome_message = wrap(getUtility(ITemplateLoader).get( File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 188, in get contents = getUtility(ITemplateManager).get( File "/usr/lib/python3.8/site-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3.8/site-packages/mailman/model/template.py", line 110, in get contents = protocols.get(actual_uri, **auth) File "/usr/lib/python3.8/site-packages/mailman/utilities/protocols.py", line 38, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.8/site-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/lib/python3.8/site-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 530, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 643, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 529, in send raise ReadTimeout(e, request=request) requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', port=8000): Read timed out. (read timeout=5) [26/Jan/2021:20:43:07 +0000] "POST /3.1/members HTTP/1.1" 400 130 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:07 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:43:07 +0000] "GET /3.1/lists/laura-test(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" Then the results of a successful subscribe: [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2.mm3.aca-aws.s.uw.edu HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "POST /3.1/members HTTP/1.1" 201 0 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2(a)mm3.aca-aws.s.uw.edu/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2" [26/Jan/2021:20:46:20 +0000] "GET /3.1/lists/list2(a)mm3.aca-aws.s.uw.edu/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.2” >

5 years, 7 months

Acceptable aliases defaults to []

by Henrik Rasmussen

* Docker-mail 0.1.1 * Mailman 3.1 * Postorius 1.1.1 * Hyperkitty 1.1.1 Minor issues: Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2: * http://www.list.org/mailman-admin/node23.html * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

9 years

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, 10 months

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

9 years, 7 months

Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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

Mailman-users search results for query "Postorius"