Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Hyperkitty Archives - Sidebar years/months

by Mark Sapiro

On 11/7/18 4:18 PM, Enrique Terrazas wrote: > Thank you Mark > I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: > /bin/sh: django-admin: command not found So whatever django-admin you are trying to run is not in the path of the cron job. Try an absolute path to django-admin instead. > If I run: > django-admin --help > > I get the following: > > Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). I install Mailman in a virtualenv and the django-admin file I run contains #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ The main things are the directory containing settings.py is /opt/mailman/mm and I export that as PYTHONPATH so my settings module can be found. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Emergency Moderation

by Mark Sapiro

On 5/24/20 10:59 AM, Allan Hansen wrote: > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ If you imported your MM 2.1 lists with `mailman import21`, `emergency` was set appropriately for the imported list and should be working to hold posts regardless of other settings. > My own current top-of-the-list issues: > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. Editing membership beyond what could be done via the admindb interface (i.e. clearing a moderated poster's mod flag) was never allowed for a moderator in MM 2.1. In MM 3, a moderator can set a member's moderation when handling a held post. Do you think a non-owner moderator should be able to make other changes to a member? > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're working on it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 13:09, bob B via Mailman-users wrote: > Mark, > Thanks for the Assistance but a little lost in the interpreter, and no luck googling. How do Iget back to the >>> prompt? > > I enter > > bash-5.0$ mailman shell -l maillistappha(a)XXXXX.org > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the maillistappha(a)XXXXX.org mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > ********* This is where I am stuck ********** I hit return it takes me to a new line with no characters? how do i get back up a level to the >>> prompt to enter commit() You wait until it finishes processing the 30K messages and then you'll get the >>> prompt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. > > 1) How do I set another default for Digest Size Threshold for new lists. It's hard coded in mailman/styles/base.py. It should be a config setting, but I think it's not. > 2) How do I change the default for existing lists Postorius -> Settings -> Digest > When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. No. digest_volume_frequency only controls how often the digest volume number increments (and issue number resets). In order to send periodic digests, you need to run 'mailman digests --periodic' via cron. > How do I change this setting, both on a single list and the default for new lists? The only setting is the lists digest_send_periodic which again is hard coded (to True) in mailman/styles/base.py. For existing lists, it is exposed in REST, but not yet in Postorius. -- 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

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/10/21 3:45 PM, dancab(a)caltech.edu wrote: > Thanks Mark. We're using https:// for the URLs. Mailman 3.3.5 is what we're running. > > (mailmanve) mailman@14ea21f6d4b1:/var/www/mailman-www$ mailman conf |grep tasks > [mailman] run_tasks_every: 1h > > We're using two containers behind a load balancer for Mailman so I suspect this is where the lost cache comes into play. Yes. The cache entry is stored in the database which presumably is shared, but the actual cached data may only be stored in the file system of the server that cached it so the other server will think it's lost. Are you sharing Mailman's var/ directory between the two servers? I think you need to do that. > Would it be safe to increase the task frequency to every 15 minutes via the setting below? > > run_tasks_every: 15m I don't think that will do what you hope. It won't hurt, but the task runner only evicts expired entries, and they have a life set by cache_life in the [mailman] section of mailman.cfg (not to be confused with cache_lifetime set in the [dmarc] section) with a default of 7 days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/25/22 23:00, Jan Eden via Mailman-users wrote: > > proxy_pass http://127.0.0.1:8000; â†’ proxy_pass http://unix:/opt/mailman/mm/var/mailman.sock; > > and received an error message (as expected): Because that won't work. You can't http to a unix socket in that way. Use ``` uwsgi_pass unix:/opt/mailman/mm/var/mailman.sock; ``` > There are obviously a couple of places where the http-socket on port > 8000 is referenced (e.g. mailman_web/settings/mailman.py, > /opt/mailman/mm/hyperkitty.cfg). Is there an overview of the > required changes when using a different (file) socket? If you configure uwsgi with only a unix `socket` and no `http-socket`, nothing will be listening on port 8000. Thus, you need to configure those references to public facing URLs and let ngnix determine where to go. e.g., for mailman-hyperkitty.cfg ``` [general] base_url: http://example.com/archives/ ``` and in settings.py ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' ``` to override the `localhost:8000` reference in mailman_web/settings/mailman.py. Those two are the only ones. While you might be able to change the references to something like ``` http+unix://%2fopt%2fmailman%2fmm%2fvar%2fmailman.sock/... ``` that may not work, and it's simpler to let ngnix handle it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: New installation, new issue: mailman3 migrate -- no module CommonMark

by Mark Sapiro

On 10/26/24 16:20, Bill Oliver wrote: > > (venv) mailman@mail:~$ mailman-web migrate > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.10/site- > packages/django/template/backends/django.py", line 128, in > get_package_libraries > module = import_module(entry[1]) > File "/usr/lib/python3.10/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1050, in _gcd_import > File "<frozen importlib._bootstrap>", line 1027, in _find_and_load > File "<frozen importlib._bootstrap>", line 1006, in > _find_and_load_unlocked > File "<frozen importlib._bootstrap>", line 688, in _load_unlocked > File "<frozen importlib._bootstrap_external>", line 883, in > exec_module > File "<frozen importlib._bootstrap>", line 241, in > _call_with_frames_removed > File "/opt/mailman/venv/lib/python3.10/site- > packages/postorius/templatetags/markdown.py", line 21, in <module> > from readme_renderer import markdown as md_render > File "/opt/mailman/venv/lib/python3.10/site- > packages/readme_renderer/markdown.py", line 16, in <module> > from CommonMark import commonmark > ModuleNotFoundError: No module named 'CommonMark' What is your version of readme_renderer? I don't see readme_renderer importing from CommonMark in any recent version. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Backups & disaster recovery of mailman3

by Mark Sapiro

On 3/7/21 11:07 AM, David Partain via Mailman-users wrote: > Hi, > > So now I have a running mailman3 installation. Whew... > > Is there documentation of things like thorough backups and disaster recovery? I haven't yet found it. > > Backups: Obviously, I understand that I need to have datbase (mysql, in my case) dumps, and I'll have file system backups onto something that our IT folks will backup. Is there more I should think of? No, backing up the database with dumps and backing up Mailman's var/ directory and the various settings and mailman.cfg files should be sufficient. Backing up the entire Mailman installation might be useful should you need to restore it on a new server. > Disaster recovery: So, let's say my server (which is cloud-y) gets trashed and I need to get mailman back on a new server. Is this process described somewhere? I don't think so, but assuming you get all the Mailman pieces together on the new server, loading the database from a backup dump and restoring the var/ directory and the various settings and mailman.cfg files should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Problem with Gmail; bulk email

by Mark Sapiro

On 5/8/23 21:35, Lars Bjørndal wrote: > Does someone have tips in how to solve the problem? Look at the log: > mai 09 06:16:52 dalen.lamasti.net postfix/smtp[2174424]: 8163214C1740: to=<example(a)gmail.com>, relay=alt1.gmail-smtp-in.l.google.com[142.250.157.27]:25, delay=50885, delays=50875/0.04/6.5/3.7, dsn=4.7.28, status=deferred (host alt1.gmail-smtp-in.l.google.com[142.250.157.27] said: 421-4.7.28 [185.181.61.11 15] Our system has detected an unusual rate of 421-4.7.28 unsolicited mail originating from your IP address. To protect our 421-4.7.28 users from spam, mail sent from your IP address has been temporarily 421-4.7.28 rate limited. Please visit 421-4.7.28 https://support.google.com/mail/?p=UnsolicitedRateLimitError to 421 4.7.28 review our Bulk Email Senders Guidelines. 14-20020a63184e000000b00519f8ebcc5esi643336pgy.121 - gsmtp (in reply to end of DATA command)) First of all, that's just throttling/greylisting/whatever. It's a temp fail and your MTA should retry and the mail should ultimately be accepted. Was your server sending an unusual amount of mail to google users, perhaps an unusually large amount of traffic on a list? I'm only guessing, but I suspect this problem may go away after google gets more experience with your mail, but in any case, it should only result in delayed mail delivery. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 8/16/25 8:14 PM, Wikinaut wrote: > and mails appear not to be processed any more. > > One mail came through, but look to the third lien of the footer, some variables are not replaced by their values: > > berlin mailing list -- berlin(a)xxxxx.de > To unsubscribe send an email to berlin-leave(a)xxxxx.de > %(web_page_url)slistinfo/%(_internal_name)s This line is from a msg_footer imported from Mailman 2.1 by 'mailman import21'. The substitutions are not replaced because they are MM 2.1 syntax which MM 3 doesn't recognize. If you have Mailman core >=3.3.10 and have set the Base Url parameter for the domain, you can replace that line in the template with simply $mailinglist_url If your Mailman core is older, you need to hardcode that as something like https://example.com/mailman3/lists/$list_id I'm only guessing here, but I suspect that you have some directories/files in the /opt/mailman/mm/var/templates/ hierarchy with mode and ownership such that they aren't readable by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Search results for query "sapiro"