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

[MM3-users] Re: multiple sites on a mailman3 server question

by Mark Sapiro

On 12/29/21 8:48 AM, William Oliver wrote: > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. If you are following https://docs.mailman3.org/en/latest/install/virtualenv.html you have ``` location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ``` in your nginx config and everything goes to uwsgi. What you want is to put those proxy directives in only the mailman locations as at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and then configure your document root so other locations are served from there. -- 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: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`

by Mark Sapiro

On 12/22/23 10:34 AM, Wikinaut wrote: > Wheras my older lists handled these format apparently correctly, I now cannot add any more > > "Givenname Familyname" <mailaddress> ; or > Givenname Familyname <mailaddress> > > In any of these cases, only the part <mailaddress> is added. > > Is this strange behaviour know? > What can be done to have the correct function back to working again? There haven't been any changes to this. The issue is almost certainly that when subscribing "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> if there is no Mailman user/address for <mailaddress>, one will be created with display name `Givenname Familyname`, but if there is an existing user/address for <mailaddress>, its display name won't be changed. In this case, you can find the user at https://www.example.com/mailman3/users, click the user's Manage button and update its display name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Legit login attempts yield, "An error occurred while processing your request."

by Mark Sapiro

On 8/14/24 3:18 PM, Greg Newby wrote: > > My primary question is: *How can I find out what's causing this*? > > I've looked in all the MM and web logfiles, by "tail -f" while generating > the error, and nothing is logged there. Apache logs shows something like > this: > > x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ > HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" > "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log. > I've come across this error while trying to do authentication-related > activities that worked before the reboot: Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0. -- 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: API privileges question for mailman3

by Mark Sapiro

On 10/14/21 12:41 PM, bob B wrote: > In mailman3 documentation it says: > "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost." > > So I just wanted to confirm there is no way to limit API access? For example I have a group that wants to use API access to mange their mail lists, but from what I can gather, if I give them access to the API they would have access to ALL the mail lists etc.. I would suspect this is even true if I give them their own domain? > > Is there anyway to limit access via the API to certain lists etc..... No, there isn't. If Postorius is not suitable for some reason, you would need to implement an application on the host to provide a user interface to the API with appropriate authentication and controls. There are some ideas but no actual code at <https://gitlab.com/mailman/lemme>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

On 6/26/22 08:07, Andy Smith wrote: > > On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > >> Just to be sure: for this feature, is it necessary to click on the >> subject and to choose in the drop-down list “Discard (no >> notification)”, or is it enough, on the .../held_messages page, to >> select the messages and click on “Discard”? > > Doing it from the held messages page will be a one-time thing; it is > only by clicking on the individual message that you can choose an action > for future messages from that address. In case the above is not clear, selecting the message and clicking Discard will only discard that message. To automatically discard all future messages from that sender, you need to set that (non-)member's moderation action to Discard which you can do by clicking on the subject and selecting the Discard moderation action from the dropdown list. -- 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: Mailman 3 Hyperkitty indexes not being built

by Mark Sapiro

On 10/18/22 05:27, tom(a)gather.coop wrote: > My config looks like this: > > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': os.path.join(BASE_DIR, "fulltext_index"), > ... > I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. > > What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. > > Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… And answered there. You need to be running several things periodically via cron. For Mailman core, see https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs and for Django, see https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required. The particular job which updates the search index is the hyperkitty update_index job which in current HyperKitty is one of the hourly jobs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:11 PM, David Newman wrote: > On 1/14/22 4:54 PM, Mark Sapiro wrote: >> >> It should work. I suspect you need to go to the list's Settings -> >> Automatic Responses and set `Admin immed notify` to Yes. > > > It's enabled. I think this triggers notifications only for new > subscription requests, not pending ones. Yes. That will send a single notification at the time of the request using the `list:admin:action:subscribe.txt` template. Notices of pending requests are sent by the `mailman notify` command using the `list:admin:notice:pending.txt` template. ... >> You can test `mailman notify` at any time by running it by hand. > > > Thanks. This still isn't working as intended. I took these steps: > > 1. Created the file > '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' The template name is `list:admin:notice:pending.txt`, not `list:admin:action:pending.txt`. Thats why it didn't work. ... > 2. Restarted the mailman3 and mailmanweb services You only needed to restart Mailman core. ... > What I'm trying to do here is replicate a feature from MM2.1, where > pending notifications had URLs embedded in the message. That's not > available out of the box in MM3, and if there's a place for feature > requests I'd be glad to ask that this be made the default. The place for feature requests for Mailman core (which this is) is https://gitlab.com/mailman/mailman/-/issues, however, this is not straightforward as Mailman core doesn't know if you even have Postorius or some other web management UI installed or what the URL to access it might be. Thus it's not just a simple matter of editing templates. It would also require a configuration setting for the base URL for the web admin UI and changes in logic to provide an appropriate replacement depending on whether or not the base URL was configured. -- 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: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/6/21 2:00 AM, marcus.granath(a)gmail.com wrote: > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? My fault. Sorry for the confusion. I wrote: > Now, no one can post. To allow your set of users to post, you have > choices. The easy way but not secure against spoofing is to set the > Maderation Action for the three allowed members to List Default and toi > create a non-member for no-reply(a)abc.com and set it's moderation action > to List Default. That should have said "set the Moderation Action for the three allowed members to Defer or Default Processing (again two names for the same thing) and to create a non-member for no-reply(a)abc.com and set it's moderation action also to Defer or Default Processing." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

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

by Mark Sapiro

On 10/22/21 2:10 PM, Marco Marinello wrote: > Dear Mark, > > configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. > > # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip > # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… It appears that https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… is the latest mailman-hyperkitty, but https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip is missing some commits. It has https://gitlab.com/mailman/hyperkitty/-/commit/79b22a23d3390db741a8233fa1ff… but is missing https://gitlab.com/mailman/hyperkitty/-/commit/ec9c8ed18798cf8f7e89dfaba001… which is very strange because it does seem to have https://gitlab.com/mailman/hyperkitty/-/commit/705bdbb2fb27be60d17ada7cba84… I Suggest you do pip install -U HyperKitty pip install -U mailman-hyperkitty which will get the latest packages from PyPI or if you want the heads from gitlab, pip install git+https://gitlab.com/mailman/HyperKitty.git pip install git+https://gitlab.com/mailman/mailman-hyperkitty.git -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Search results for query "sapiro"