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

[MM3-users] Re: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/18/23 12:33 PM, bryan.kartzman(a)yu.edu wrote: > Sorry for the multitude of posts. I probably should have saved it all up for one post. > > I see in the hyperhitty_email table right after the "date" field there is a "timezone" field. I altered the "date" field to "timestamp with time zone" when I changed every timestamp field in the database from "without time zone" to "with time zone". Are there some (like this "date" field) that should have remained "without time zone"? The date field and the archived_date field should be `timestamp with time zone` in spite of there being a separate timezone field. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: An issue with the postfix_domains directory creation and the mailman start command.

by Mark Sapiro

On July 10, 2024 1:35:03 PM PDT, Keith Christian via Mailman-users <mailman-users(a)mailman3.org> wrote: >Ron, I get this: > > > 1 (venv) [mailman3@somehost ~]$ mailman conf | grep layout > 2 [mailman] layout: local > >I've added your paths to /etc/mailman3/mailman.cfg: > > 1 # /etc/mailman3/mailman.cfg > 2 > 3 [paths.here] > 4 var_dir: /opt/mailman3/mm/var > 5 bin_dir: $argv > 6 log_dir: $var_dir/logs > 7 data_dir: $var_dir/data > 8 > 9 > 10 > 11 [mailman] > 12 layout: here > 13 layout: fhs > 14 layout: local > Everything you put on lines 4-7 is irrelevant because line 14 overrides line 12. Remove lines 13 and 14. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 5 months

[MM3-users] Re: Counter-intuitive header filter processing

by Mark Sapiro

On 09/18/2018 10:26 AM, Jonas Meurer wrote: > > Apparently, that's not the case. If the default message acceptance > setting for members is set to "reject", then mails from > *(a)freesources.org get rejected even though the header filter says > "accept". In other words, the default message acceptance action seems to > overrule any header filters. > > Is this expected behaviour? Yes. Rules are normally checked in a sequence defined in mailman/chains/builtin.py and that sequence checks several things including member moderation before checking header matches, so if "Default action to take when a member posts to the list" is anything other than "Default processing", that action will take precedence over header matches. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Configure MM3 with separate IMAP Mailserver

by Mark Sapiro

On 1/2/23 03:44, clemens.leider(a)gmail.com wrote: > Dear all, > > we have managed to setup MM3 following the docker Installation concept/Tutorial. So far so good. However now i am struggeling with connecting to MTA. We are using imap server of our hosting provider.how to integrate that properly? Google was not too much of help unfortunately…looking for some tutorial or howto/step by step if possible. Assuming your Docker container can send TCP requests to the outside world, you need to set things in mailman.cfg like [mta] smtp_host: name or IP address of the IMAP server smtp_port: 587 or whatever the server's submission port is smtp_user: credentials for IMAP login smtp_pass: " " " " -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Verification links to localhost

by Mark Sapiro

On 2/4/23 22:50, Lars Bjørndal wrote: > The verification link I get back when trying to add an account, referes > to localhost, e.g. > > To confirm this is correct, go to https://localhost:8000/accounts/confirm-email/Mw:1... > > Where do I change that? This message comes from Django allauth and is probably using what it thinks is the host that is doing the add. This is based on your web server configuration which I would need to see to be more specific. I suspect you are proxying requests to https://localhost:8000/ and you are missing a directive to pass the host. For Apache I think you want ``` ProxyPreserveHost On ``` and for nginx ``` proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; ``` -- 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: Template URI gets written incorrectly

by Mark Sapiro

On 5/23/23 16:51, Mark Dale via Mailman-users wrote: > > When I create a template, it writes the URI incorrectly into the > template table in the mailman3 database and the list stops working. > > For example, it writes: > > http://localhost/mailman3/postorius/api/templates/list/markslist.lists.post… > > When I correct it like so, all is well: > > https://lists.postmark.io/mailman3/postorius/api/templates/list/markslist.l… > > Have I missed a config setting somewhere, or is this a bug with the > older Debian Mailman 3.3.3 ? You need to set POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.postmark.io/' in your Django settings. Debian probably has set it to 'http://localhost/'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: 500 error on one list

by Mark Sapiro

On 7/13/24 8:35 AM, Seth Seeger wrote: > > Did this one list get corrupted somehow? This is https://gitlab.com/mailman/mailman/-/issues/657 We still don't know the underlying cause. Note that the first script in that issue assumes that the multiple entries are for the mhonarc archiver, but this isn't always true. If you run this database query SELECT * FROM listarchiver WHERE mailing_list_id = (SELECT id from mailinglist WHERE list_id = 'list.example.com'); replacing list.example.com with the list_id of your problem list, you will see there are two entries with the same name. Then do DELETE FROM listarchiver WHERE id = nn; where nn is the id of one of the duplicates, it doesn't matter which. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Moderator e-mails only going out once a day

by Mark Sapiro

On 3/26/25 6:46 AM, jkoral(a)luc.edu wrote: > OK, another thought. Could it be because of the way my cronjob is setup??? Here is what I have. > > @daily /opt/mailman/venv/bin/mailman digests --periodic > @daily /opt/mailman/venv/bin/mailman notify > * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely > 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly > @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly > @daily /opt/mailman/venv/bin/mailman-web runjobs daily > @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly > @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly > @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly That looks good, but admin_immed_notify doesn't depend on any cron. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/8/25 12:29, dap1--- via Mailman-users wrote: > I guess it is obvious pointers are still messed up. I still don't understand why the `mailman` command is getting it's config from /opt/mailman/mm/var/etc/mailman.cfg instead of /etc/mailman3/mailman.cfg, but as a workaround do rm /opt/mailman/mm/var/etc/mailman.cfg ln -s /etc/mailman3/mailman.cfg /opt/mailman/mm/var/etc/mailman.cfg Then you can redo the `mailman create` and `mailman import21` processes. You can also delete the /opt/mailman/var/data/mailman.db sqlite db. I suspect you don't need to redo the `mailman-web hyperkitty_import` unless there are additional messages in the .mbox, as I suspect the archives are there at http(s)://your.host/archives/ from the prior run -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/13/25 06:23, Stephen J. Turnbull wrote: > > OK, that's not it. If it's CSRF, there's some problem with matching > the data in the backend, but I have no idea. I tried to find the > cookie in the Mailman database but either it's not there or I missed > it. Anyway, I don't have a further suggestion for fixing this > installation at this point. And I'm out of ideas too. I suggest you, @dap1, proceed by looking at https://www.google.com/search?q=django+csrf+failure for possibly relevant information. If that doesn't help, you might also consider posting to https://forum.djangoproject.com/ (see https://docs.djangoproject.com/en/dev/internals/mailing-lists/#django-forum) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

Search results for query "sapiro"