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

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/6/22 1:20 AM, Michael Heseltine wrote: > Hi all, > I've done the additional steps > > /opt/mailman/mm/bin/django-admin migrate > /opt/mailman/mm/bin/django-admin createsuperuser > > without error, and also started the services mailman, qcluster and gunicorn without error messages. Did you see my post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and did you run /opt/mailman/mm/bin/django-admin migrate before starting services? > However, I just get an internal server error when I try to access https://lists.mydomain.com/ (which is served by a local apache virthost). > > The apache log shows just one error: > > [Thu Jan 06 10:01:39.201833 2022] [proxy:warn] [pid 3627279] [client 333.333.333.333:59328] AH01144: No protocol handler was valid for the URL / (scheme 'http'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule. Do you have all of these apache modules enabled, proxy.conf, proxy_http.load and proxy.load, in particular proxy_http.load? -- 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: Main daemon process sticks around after forking

by Mark Sapiro

On 8/6/25 09:03, Jérôme Charaoui wrote: > > I'm running a (rather large) mailman3 instance on Debian 13 (trixie) using the distribution packages. > > To manage the mailman3 daemon, the package installs this systemd service unit: https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/ > > It has been working fine until recently: after a reboot, we noticed the mailman3 unit consistently failing to start due to a timeout error. > > I figured out that the timeout was related to the service unit type (Type=forking) and the fact that the main/parent process was forking subprocesses (and running normally), writing a PID file, but it wasn't exiting, so systemd identifies this as an error and aborts the service. The master is not supposed to exit. It continues to run and monitor the child runner processes and will under some circumstances restart a runner that dies. > Since switching to Type=simple, it has been working fine. This is a Debian package issue and should be reported to Debian. See https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Mark Sapiro

On 10/28/24 18:33, Bill Oliver wrote: > > Aha, I thought. I should have changed that. Then I noticed that I > didn't even have a mailman-hyperkitty.cfg file, and I can't find > mention of it in the venv instructions. I *have* installed mailman- > hyperkitty during the "pip install mailman-web mailman-hyperkitty" > step. I did a "find" on /opt/mailman, and it doesn't seem the file is > there at all. > > Do I need this file? Yes. See the last part of the section at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it says in part `And, create the /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: ...` > I found a template here: > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… > > > Do I need to copy and paste that in my installation? It, or something as mentioned in the above doc needs to be at the location defined in the `configuration:` setting in the `[archiver.hyperkitty]` section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Mark Sapiro

On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID 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 LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: installation

by Mark Sapiro

On 11/22/20 3:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I have > used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. You need a fixed IP address and "full circle" aka "forward confirmed reverse DNS" <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. You also need to DKIM sign your outgoing mail from your domain and publish an SPF record allowing your IP as a sender for your domain. I'm not sure, but publishing a DMARC policy, even if it's p=none is possibly helpful with some recipient domains. Beyond that check your IP for blacklisting with a tool like <http://mxtoolbox.com/blacklists.aspx> and monitor your mail logs for blocked email and follow up with the blockers to get unblocked. Things get better over time as your server develops a reputation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 12/29/21 3:58 PM, William Oliver wrote: > > I'd like to delete all my archives that are more than a certain age, > e.g. more than a week old. I can easily do that with a cron job, > deleting old files in > > > /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* > > which is, as far as I can see the only place archive emails live. Those are emails archived in the prototype archiver. That's all the prototype archiver does - store the mail there. The HyperKitty archived emails are stored in the mailmanweb database in the hyperkitty_email table. Attachments are in the hyperkitty_attachment table and other tables are also involved. > However... I was wondering if there was some mailman command or config > variable that would accomplish this without using cron. The cron will work for the prototype archives, but it's probably easier to just disable the prototype archiver. For HyperKitty, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 06:52, Frank Steinberg wrote: > Hi, > > I’ve added links to some templates to give owners and moderators > shortcuts to the postorius UI for moderation tasks, e.g., I’ve added > > https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> > > Unfortunately those lines seem to exceed a certain limit and get > folded, so that they appear as, e.g. > > https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> > messages > > (or similar) and are not directly useful. How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? Also are those lines of the form https://... <https://...> what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? -- 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

[MM3-users] Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 10:12 PM, Torge Riedel wrote: > Am 21.04.20 um 23:08 schrieb Brian Carpenter: >> Maybe I can get the client to agree to use the web domain as part of >> their list address. > > Hi, > > maybe it is a solution for you what I did on my side (since it was > already the setup for mailman2 my customer is happy with it): > > Set everything up in mailman3 with lists.domain.com and define in > postfix (if you use postfix, others should support it also) aliases from > - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail > list. > > In the list setup in mailman3 (available via postorius) define > list1(a)domain.com as an allowed alias for list1(a)lists.domain.com This is a good workaround, however to be complete, you may also want MTA aliases for the list1-*(a)domain.com addresses. Note, I'm currently working on a fix for <https://gitlab.com/mailman/postorius/-/issues/394>. Hopefully that will be in the next Postorius release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Mailman 3 - docker container - sync_members

by Mark Sapiro

On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > I would like to populate list members via the Mailman 3 sync_members script. > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? I'm not sure what version of Mailman core is in the Docker containers. According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman core is docker version 1.1.1 released Aug 9 2017 which is about the time of MM Core 3.1.0 which is quite old and has neither a `mailman syncmembers` (introduced in core 3.3.2) command nor the older `mailman members --sync` option (introduced in core 3.3.1). There are `rolling releases` <https://asynchronous.in/docker-mailman/#rolling-releases> which should have these. > Searching this list I found a reasonable approach: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Is there a different/preferred solution? The script at <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> seems fine. The alternative is to update your Docker container to one including the appropriate `mailman` sub-command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: hyperkitty url not found

by Mark Sapiro

On 3/14/22 12:24, Eggert Ehmke wrote: > So I have to use the external url via https? > > I can access the address > https://lists.[1]<tld>_/mailman3/archives/api/_ > > so I set: (<tld> is my existing domain) > > base_url: https://lists.<tld>/mailman3/archives > Now I get this in the mailman.log: > > Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> > Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ > api/mailman/urls: <html><title>Forbidden</title><body> > <h1>Access is forbidden</h1><p>Please check the IP addresses > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > </p></body></html> (403) > In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there? Is whatever is proxying to Django forwarding the IP and are you sure it matches the "my local IP" you set? You might instead try setting base_url to http://localhost:8000/mailman3/archives/ or more likely http://localhost:8000/archives/ (I.e. whatever your webserver proxies the https://lists.<tld>/mailman3/archives/ url to. -- 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

Search results for query "sapiro"