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

[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

3 years, 4 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

2 years, 3 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

1 year, 6 months

[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

11 months, 1 week

[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

11 months

[MM3-users] Re: Help request, almost got it going, but ....

by Mark Sapiro

On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote: > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> Recipient filters -> acceptable_aliases. It has nothing to do with submitters. It is a list of other addresses that can be in the To: or Cc: of a post to avoid and "implicit destination" hold if the list posting address is not there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: MM3 Docker

by Mark Sapiro

On 1/8/19 10:50 PM, Odhiambo Washington wrote: > Now that has clarified the matter for me. That even when I am logged out, > the scripts do the neccessary > to activate the venv to run things. As mentioned before, a virtualenv is not like a container. It is only a directory that contains among other things a bin/ directory with activate scripts and easy_install, python, pip and wheel commands. When you activate a virtualenv in your shell, all it really does is add a deactivate command, modify the command prompt and insert its bin/ directory at the beginning of its PATH. What this means is whether or not a virtualenv is "active", running a command from the bin/ directory in the virtualenv is using the virtualenv. -- 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: Migration from 2.1 to 3

by Mark Sapiro

On 12/23/19 7:52 AM, brunol(a)agro.uba.ar wrote: > > Dec 23 12:35:47 2019 (701) held message approved, message-id: <CAOwJ5NX=_bUnfb5ZNqVLFeF3EeOP0GMJW7NeeOWZqVmn5ViyBg(a)mail.gmail.com> > > And then nothing. None of the members receives the message Are you sure none of the members receive it or is it just you that doesn't receive it? If it's just you, I note the message-id is @mail.gmail.com and I wonder if the issue is <https://wiki.list.org/x/4030680>. What's in the MTA log for the time immediately after you approve the message? Are there any errors/tracebacks in the mailman.log after the above approval message? If a message is posted to the list that isn't held, is that message delivered? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: New Installation of MM3 is not archiving

by Mark Sapiro

On 1/30/23 02:57, Onyeibo Oku wrote: > > My new MM3 instance does not seem to be archiving. List subscribers > are currently sending and receiving mails on their subscribed lists. > However, none of the correspondence is showing up at > https://mailing-list-site.tld/archives/. That page shows a listing of > the active mailing-lists with '0 participants' and '0 discussions'. > Whereas, those lists contain mails. > > How do I troubleshoot this? The messages as pickled message objects are probably queued in /opt/mailman/mm/var/archives/hyperkitty/spool/. The first place to look for the reason is in /opt/mailman/mm/var/logs/mailman.log. There might also be info in /opt/mailman/web/logs/mailmanweb.log -- 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: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/25/25 12:29, Kim Sunggun via Mailman-users wrote: > Hello, > When I sign in new id, it has an issue. Could you please guide me to fix it? > > error: > ConnectionRefusedError at /accounts/login/ > [Errno 111] Connection refused > Request Method: POST > Request URL: https://lists.klnpa.org/accounts/login/ > Django Version: 4.2.19 > Exception Type: ConnectionRefusedError > Exception Value: > [Errno 111] Connection refused > Exception Location: /usr/lib64/python3.9/socket.py, line 844, in create_connection > Raised during: allauth.account.views.LoginView What is your Django setting for EMAIL_BACKEND? Normally, this is EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' Depending on your outgoing MTA, you may need additional settings. See https://docs.djangoproject.com/en/5.1/topics/email/#django.core.mail.backen… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Search results for query "sapiro"