Search results for "Postorius" - Mailman-users

Re: problem configuring mailman3 on debian bullseye

by Mark Sapiro

On 3/15/23 09:55, Odhiambo Washington wrote: > On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione > territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: > >> Hi, >> >> I created a template but after some tests I deleted it. >> >> Now I created only a standard list without modifying any templates. >> >> So they are the standard templates coming with the distribution. I did not >> change also the language >> > Maybe you can start by deleting any templates in postorius_emailtemplate > table in the DB? There shouldn't be any, but if the issue is with accessing postorius templates, that might make it worse. If you want only the system default templates, you could do this database query to remove any non-defaults: DELETE FROM templates; That will ensure that you aren't accessing Postorius for any templates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Re: How to edit default 'Reject (with notification)' message

by Mark Sapiro

On 5/26/23 7:57 AM, Zaheer Abbas wrote: > > I have created a template with the option, "Notice sent to a poster when > their message has been rejected by the list’s moderator." but it only works > if message acceptance is set to 'Hold for Moderation' and then the > moderator rejects the post manually. > > Is there any source file, which I can modify to replace the default > rejection text mentioned above? The template you want is described in Postorius as [list.user.notice.rejected] Notice sent to a poster when their message has been rejected automatically You can set it in Postorius per list or per domain or you can set it sitewide by putting it in Mailman's var/templates/site/en/list.user.notice.rejected.txt and if you do that, be sure the Mailman user has access to read it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Re: Topics - Tags

by Mark

On 2024-03-23 06:36, Mark Sapiro wrote: > On 3/21/24 21:10, Mark wrote: >> Hi, >> >> I'm reading the docs on "Message tagging" >> (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) >> as saying shell access is needed to: (a) enable topics, and (b) write >> the keywords. >> >> In Mailman 2 there is an Admin web UI for "Topics". Is there such a >> web UI that can be enabled in Mailman 3 so that the list owners can >> create topics (tags) in their lists? > > > At this point, topics are not exposed in REST. Managing them via > Postorius first requires updating the REST API to read and set the > topic attributes and then updating Postorius to display/set them. > > Further, there is currently no implementation for list member topics > of interest either in Mailman core or the REST API. I.e., there is no > way for a list member to indicate topics of interest. > Thank you for this information Mark. Best, Mark

1 year, 2 months

Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 18:05 schrieb Mark Sapiro: > On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: >> >> Right now everything is running as root (except for Apache). I realized >> too late that I should've used a mailman user. Could that be the reason >> for the issue? > > Since you have determined it was a browser issue, that probably isn't > the reason, but running Mailman as root is a bad idea in general for > security reasons. Thanks, I'm aware, and I'm not going to on a production system. This installation is just a trial run. > I don't know if it's relevant or not, but I have just recently had > issues with Firefox not working properly on two different (not mailman) > web sites, and these issues were fixed by clearing cookies and cached > data from the affected sites and restarting Firefox. I can confirm that that worked in my case as well.

4 years, 9 months

Re: Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

On 7/8/21 13:55, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > Yesterday I had a problem with a private list. A spammer sent a mail > > forging one address that was a non-member (in fact was an "accept this > > no subscriber mails" from mailman 2.1 import) with very bad intentions > > and it was distributed. > > If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers > list for each list is grandfathered into the Mailman 3 list (from > rules/moderation.py): > > # Check the '*_these_nonmembers' properties first. XXX These are > # legacy attributes from MM2.1; their database type is 'pickle' and > # they should eventually get replaced. > for action_name in ('accept', 'hold', 'reject', 'discard'): > legacy_attribute_name = '{}_these_nonmembers'.format( > action_name) > > > There were no list of "accept this non members" in the Postorius > > config > > If there is no such list in Postorius, I would guess that some > developer thought "OK, this is a legacy feature and I'll get back to > it when we move it to the proper database" (unfortunate, but most of > us have open-subscription member-posts-only lists, and the current > workflow seems to work well, so this feature may not be so salient). > > > I think it is solved now (deleting all and putting to hold just the > > non-members addresses that I would want to pass messages on) > > This should not be necessary, unless there were pre-approved addresses > that are no longer appropriate. But Mailman can't know that! > > > The fact is that any sender address of mails sent to the list is saved > > as a "non member", and it make me nervous as it will grow despite it is > > a legitimate message or not. > > As far as I can see there is no other rule except that legacy rule > (and the rule that accepts all posts, which is rarely used) that will > accept a post from nonmembers. > > > Anybody knows if there is a per list config to avoid saving all that > > addresses as non members? o a overall config? > > No, there isn't, and there never will be. This is a basic design > decision about the representation of "people who participate in any > way in mailing lists". The only way to prevent creation of an Address > object for the sender of an email is to reject or discard the post (in > which case the "create an Address" path isn't entered), and don't set > a moderation action on the sender. Obviously if you set a moderation > action, that will create an Address in the database. > > The problem you encountered is not preventable by any means > whatsoever: a malicious actor discovered an address that is allowed to > post. The specific case you're worried about, that nonmembers will > automatically be allowed to post, is not possible. Well, as I couldn't locate which legacy accepted to post non-member addresses were permitted, I solved it deleting all of them (thanks again Mark) and adding via Postorius to the list of "hold these non-members messages" that I will examine and decide if it is a legitimate send. Thanks a lot for your detailed explanation. I can do better decisions now adjusting the configuration as needed. > The only way to > get on the list of "accept_these_nonmembers" is to be inherited from > accept_these_nonmembers on the parent Mailman 2 list, or an explicit > decision by a moderator. > > The fact that this list is not exposed in Postorius is a bug, but I > can't say when it might be fixed. It appears that the current process > (the moderator can set the sender's persistent moderation action > separately from approving or rejecting a particular post) works fine, > since this is the first time I've heard of this issue, and as you > present it, Mailman is doing the best it can since Somebody Authorized > put that sender on the approved list in Mailman 2. > > If a particular nonmember becomes a problem, you can access that > User or Address in Postorius and set them to Hold, Reject, or Discard. > > The process of deleting all nonmembers has been more difficult than it > should be, but this is being fixed, IIRC in the next release. > > Steve > --

3 years, 10 months

Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/18/22 06:24, Stephan Krinetzki wrote: > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? There are two steps in handling the POST for a held message. The first step is accepting, rejecting or discarding the message. This is happening immediately. The second step is handling the poster's moderation action based on the choice from the Set member moderation dropdown in the view of the held message. This is processed by the code at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…>. If no selection has been made, the default value POSTed for moderation_choice is `no-action` and that code is skipped. If it is one of the choices `Hold for moderation`, `Reject (with notification)`, `Discard (no notification)`, `Accept immediately (bypass other rules)` or `Default processing` that is processed. So presumably a selection has been made and processing is stuck on getting the member or setting the member's moderation action. Possibly the logs of your database manager will have information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 12:50 PM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: >>> >>>> >>>> >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >>>> wrote: >>>> >>>> /bin/sh: sass: Permission denied* ... >> Try `which sass` >> > > root@gw:/usr/home/wash # su mailman3 > (venv) [mailman3@gw /usr/home/wash]$ which sass > (venv) [mailman3@gw /usr/home/wash]$ > > There is no sass. There has to be. You can't get a permissions error on sass if it doesn't exist (well, maybe if you don't have permission to search a superordinate directory, but that's unlikely). Try `find /usr -name sass` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

sqlite3 Database "read only" error on mailman_sync job

by ugniusviln＠gmail.com

Hi. All the project installation is under the same user / path and it works. Archiving working as well, (just one remark: no matter what to set in postorius, hyperkitty shows list as public) I have found work around - it is possible to change list as private in "admin" page. I started to get issues with runjobs after I have created couple of new lists with "no archive" option. If as owner user from project home I run: django-admin mailman_sync Traceback (most recent call last): File "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: attempt to write a readonly database "django-admin runjob sync_mailman " - makes read only errors as well. "django-admin runjob new_lists_from_mailman" django.db.utils.OperationalError: attempt to write a readonly database END TRACEBACK I did not find information how to fix this. It was worked without errors before. I noticed, that if I stop mailman, "django-admin mailman_sync" starts to work. If I start "mailman start", then "django-admin mailman_sync" failing again. I did not check other jobs, but I think what is related to database, will get errors. Seems mailman locking the database. It is not a file permissions issue. Mailman db location is: /project_directory/var/data/mailman.db if to rename /project_directory/var/data/mailman.db to something, mailman creates database file size 0, django-admin runjobs start working, but of course postorius stops working. I did it for testing. I have returned this database file back, postorius started to work again, but django-admin runjobs does not work, error: "database read only". Please help me how to fix this issue.

5 years, 9 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 3:00 PM, Odhiambo Washington wrote: > On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Those are headers for compiling some sass. Possibly you actually have a >> `sassc` installed in which case you may need >> >> COMPRESS_PRECOMPILERS = ( >> ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), >> ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), >> ) >> >> > This change makes the error I was getting to go away. However, I cannot > login to manage lists, even after restarting mailman. > > The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ The relevant part of which is OfflineGenerationError at /accounts/login/ You have offline compression enabled but key "fa788b08b65fd318d68cfc5afebc18acd3e93cebffadb54d863572ad1754f368" is missing from offline manifest. You may need to run "python manage.py compress". Here is the original content: I.e., something went wrong with your compress command. Try it again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

CSS Hyperkitty ERROR

by Johan Alsina

Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. Here you can see what i see when loading hyperkitty https://freeimage.host/i/3n6kXKQ and mailman(postorius) https://freeimage.host/i/mailman.3n6kVix When i run my server with verbosity it shows like all is loading ok: https://freeimage.host/i/3n6SViG Any ideas? :/ My static files are loading from /static/CACHE/css/output.a0f71925131b.css and /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css It seems like the real error are in the /static/CACHE files, because hyperkitty is the only one who load files from this directory.. postorius uses /static/postorius and all the css files are working fine. I checked permissions for the directory, cleared cache, etc.. i dont know what to do. This is my config for staticfiles: STATIC_URL = 'static/' STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles') STATICFILES_DIRS = [ os.path.join(BASE_DIR, 'static'), '/opt/mailman/projectes/mailman3web/static/CACHE', Thank you so much in advance.

2 months, 4 weeks

Mailman-users search results for query "Postorius"