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

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/6/22 10:35 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > It looks the right way (I have apache running in that server) to solve > it. What intrigues me is the fact that I didn't change anything in the > apache config or update apache itself. That doesn't matter. With your older HyperKitty and mailman-hyperkitty the MAILMAN_ARCHIVER_KEY was sent from mailman-hyperkitty to HyperKitty as a query fragment (key=...) in the URL. The changes in HyperKitty 1.3.5 and mailman-hyperkitty 1.2.0 send it in an Authorization HTTP header instead, so before, it didn't matter if the Authorization HTTP header was dropped, now it does. -- 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

[MM3-users] Re: Excluding archives from a mailman3web database backup

by Mark Sapiro

On 6/23/22 17:38, Andy Smith wrote: > > Is that a realistic proposal? i.e. does a typical maildir2mbox > conversion script generate something that "manage.py > hyperkitty_import" would be happy with when run on prototype's > maildir? Yes. > If so, is it safe to just exclude every table starting with > "hyperkitty_" from the database backup of mailman3web? Dumping only > the schema for these, I mean, so that an import would restore empty > tables. That should be safe. The hyperkitty_import job should populate the tables as necessary. You will lose things like favorites, last views, tags and votes, but that may not be important. -- 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: Link to account

by Mark Sapiro

On 4/11/23 23:08, Lars Bjørndal wrote: > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. Try this. In urls.py ``` urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('mailman3/accounts/', include('allauth.urls')), path('mailman3/admin/', admin.site.urls), path('mailman3/', include('postorius.urls')), ] ``` In apache ``` <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3/archives" "http://127.0.0.1:8000/mailman3/archives" ProxyPass "/mailman3/accounts" "http://127.0.0.1:8000/mailman3/accounts" ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" </IfModule> ``` -- 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: Cannot Install Web UI

by Mark Sapiro

On 10/31/25 08:16, dap1--- via Mailman-users wrote: > I don't know where to go from here. I've verified that ports 443 and 8000 are both listening. If they weren't, you wouldn't be getting 404 errors. If you were proxying to a port that wasn't listening you'd get a 503 Service unavailable and if your web server wasn't listening your browser wouldn't be able to connect. To recap, the issue is http://localhost/mailman3 and presumably https://localhost/mailman3 give a 404. What about other urls like https://localhost/mailman3/lists/ https://localhost/archives https://localhost/accounts https://localhost/user-profile And again, is there anything relevant in /opt/mailman/mm/var/logs/error.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/25/21 5:18 AM, Marco Marinello wrote: > Finally have found my issue... Apache automatically removes the header, see https://stackoverflow.com/questions/26549250/apache-strips-down-authorizati… . Hope it can be useful for somebody else! I'm glad you found this, but I'm a bit confused. I run a few servers with apache 2.4 proxying to gunicorn and I don't see the issue. Perhaps this is a uWSGI or mod_wsgi issue. In any case, it can possibly be avoided by setting base_url in mailman-hyperkitty.cfg to something like base_url: https://127.0.0.1:8000/archives or whatever localhost port the WSGI application is listening on to bypass apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

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

by Mark Sapiro

On 12/16/21 10:35 AM, dancab(a)caltech.edu wrote: > Mark, > > I updated mailman.cfg to point at our shared EFS mount. > > cache_dir: /mnt/var-mailman3/cache > > But I'm still getting reports of this issue. Is there somewhere else I need to set that location? If your layout is other than fhs, I would set var_dir: /mnt/var-mailman3/ For fhs layout, I would ensure that at a minimum, /var/lib/mailman, /var/spool/mailman and /var/lock/mailman are all shared. However for your issue with shared cache, you need to wait 7 days for all the old cache entries to expire or do getUtility(ICacheManager).clear() in `mailman shell` to clear the cache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Database permission problem?

by Mark Sapiro

On 10/15/24 15:03, Bill Oliver wrote: > > I'll also add that the instructions get a little hazy when you get to > the "Unusual Postfix configuration" part, which is me, with multiple > virtual domains, virtual mailboxes, and use dovecot. > > For instance, it's not clear to me in the "Unusual Postfix > configuration" when you should use > > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} > > versus > > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp I don't know anything about postfix configurations for dovecot delivery. I've only used dovecot for sasl authentication. In any case, dovecot delivery should not be involved in delivery to Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Python backtrace from `mailman -h`

by Mark Sapiro

On 8/24/25 17:03, Peter Chubb via Mailman-users wrote: > Hi Folks, > I'm running the Debian-packaged mailman3 (yes I know ...) > and running: > sudo -u list mailman -h > gives a python backtrace (which I've appended the tail end of). > Can someone who has the upstream installed version (using venv) > please check that `mailman -h` works there before I waste too much time > investigating in the wrong places? Yes, `mailman -h` works and produces the same help output and list of subcommands as `mailman` with no arguments or options. Does it work with no options? Does it work if you do `mailman -C path/to/mailman.cfg -h`? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Confirmation for subscriptions

by Mark Sapiro

On 6/23/19 7:28 PM, Mark Sapiro wrote: > On 6/23/19 7:11 PM, andrew.bernard(a)gmail.com wrote: >> I have had some trouble with uwsgi, now resolved. Not that there may be any connection, but now, email requests to join are sent a confirmation mail, but the webui just signs you up with no confirmation despite having the subscription policy set to Confirm, and the right code in the database table underneath. > > > Is this a web subscribe for a logged in user or and "anonymous > subscribe" for a non-logged in user or both? I have done some further investigation. With subscribe policy 'confirm': A person without an account can subscribe to a list anonymously. The person is sent an email requesting confirmation of her address and intent to subscribe. Replying to the email confirms the address and subscribes it. A person can sign up for an account with an email address. This results in an email request to the address with a link to confirm it. Following the link and confirming the address then creates the account with the confirmed address. Subsequently, the user can log in and subscribe to the list without further confirmation because the user has already confirmed the address and has logged in, so further confirmation is not required. If subscribe policy is 'moderate', both of the above cases send the request to the moderator for approval. I think this behavior, particularly allowing a logged in user with a confirmed address to subscribe without further confirmation, is reasonable. Is this what you see, or are you seeing something else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Emailing a list from the list server

by Mark Sapiro

On 6/1/20 11:56 AM, Mark Dadgar wrote: > On Jun 1, 2020, at 11:45 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> What's in Postfix's mail.log? > > > Jun 1 11:54:55 mail postfix/lmtp[238922]: 1F42613BEB5: to=<test3(a)pdc-racing.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.02/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) OK. It was delivered to Mailman's LMTP runner which presumably accepted it and queued it because that's the only case in which it returns '250' You could set [logging.smtp] level: debug in mailman.cfg to get more logging, but I think that that will just add confirmation of what we already know, i.e., it was queued in the in queue. So that leaves us with: some error in processing shunting the message. In that case the error would be logged in mailman.log and the message would be in var/queue/shunt. or some rule discarding the message. In that case, there should be a DISCARD: <message-id> entry in mailman.log. If that's the case, we still don't know which rule did the discard and why. One thing you might consider is the possibility that you've missed some message because it was delivered to a local mailbox rather than where you expect it. In my case, msapiro.net has an MX record pointing to my real mail server, but it is also the host name of my development box so mail generated on that box for me winds up in /var/mail/mark instead of being delivered to my real mail server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Search results for query "sapiro"