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

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 8:55 AM, Kevin Hurtley wrote: > > It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. The issue with the way Postorius displayed all the subscription requests was that it wasn't possible for the moderator to distinguish request waiting moderator approval from those waiting user confirmation, and in general a moderator shouldn't approve a request waiting user confirmation, but this thread shows there is sometimes a need for a moderator to be able to deal with these. I have reopened <https://gitlab.com/mailman/postorius/issues/314>, and will look at fixing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Hyperkitty fulltext search performances

by Mark Sapiro

On 10/4/20 8:07 AM, Brian Carpenter wrote: > > On 10/4/20 8:59 AM, Loïc Dachary wrote: >> After a little digging it turns out the mailman3-web Debian GNU/Linux >> package I'm using is configured to use Woosh as a haystack backend. >> And it is not fit for volumes greater than a few hundred mega bytes. I >> should switch to something else from the list of supported >> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >> > For our servers running Postorius/Hyperkitty, we use Xapian. I believe > the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For > our Affinity/Empathy servers, we use Elasticsearch which we are very > happy with. Elasticsearch does have a higher memory requirement I > believe than Xapian. Brian is correct about this list. We started with Whoosh, then went to Elasticsearch and ultimately to Xapian. Each step gave better performance and a smaller footprint than the one before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/18/20 6:58 AM, Torge Riedel wrote: > Am 16.01.20 um 21:43 schrieb Mark Sapiro: >> >> This won't work for posts from members because the header checks are >> done between member moderation checks and non-member moderation checks, >> but if you create a Header Filter for header 'x-spam' and pattern 'yes' >> with action hold, a message from a non-member which has an X-Spam: Yes >> header should be held for that reason. >> >> > Hi Mark, > > thank you for your answer. Just to understand that right: In case a > posting with an "X-Spam: Yes" header comes from a member, it will not be > held? It will be directly forwarded to the list? No. I apologize for being unclear. A post from a member will first be handled according to that member's moderation action which may be the list's default action for posts from members or a specific action for that member. If that moderation action is reject, discard or hold, the post will be rejected, discarded or held as a moderated member post regardless of any header filters. If the action is accept, the post will be accepted without any further checks including the header checks. If the action is defer (default processing) the message will be held for matching the X-Spam: Yes header. What I meant was if the member's (or default) action was hold, the post would be held, but the reason would be moderated member, not header match. The bottom line here is the moderation action of accept should only be used in cases of a highly trusted member (such as a list owner) because it bypasses other checks, but the address is still subject to spoofing. In the normal case where a moderation hold is not desired, use the defer (default processing) action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: mailman2 import not working

by Mark Sapiro

On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: > > ------------------------------------------- > mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com > mailman import 21 foo-bar(a)lists.example.com path/to/config.pck > ------------------------------------------- You don't need to specify an owner for `mailman create`. The owners will be imported. > After everything done tried a test mail, but didn't reach any of the > inbox though mail is archived. mailman.log says message is accepted > > ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> > Nothing after this. It is surprising that no exception/traceback/SHUNTING message(s) are logged. That would seem to say that Mailman's `out` runner is not running. I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? Is there a .pck file either in shunt/ or in out/? what does `ps -fwwu list` show? There should be a lot of runner processes. Is there one with argument --runner=out:0:1? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/22/21 11:41 AM, Sarah H wrote: > here is the full error message. Nginx proxies on http. > > https://pastebin.com/raw/TUf5dYi8 Thanks for the log. It is basically just confirming what we see with this. > the curl commands above result in. > ... > (venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive > curl: (52) Empty reply from server I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser? Do you get a response from ``` curl http://127.0.0.1:8000/hyperkitty/ ``` If so, what? What you should get from ``` curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive ``` is ``` <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> ``` You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you? -- 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: Mailman 3 questions (purge archives, list metrics, and auto discard held messages)

by Mark Sapiro

On 8/2/22 08:53, bob B via Mailman-users wrote: > Mark, > > Thanks, I know you are not a docker guy, but any idea on how to run this in the maxking docker environment? Or maxking any thoughts? > > Not sure if the docker environment has all the components or can get them all to run this script, but I have been trying to figure it out. > I assume it should be run in the mailman-web container? we are using an external database, but I don't think that should matter. Yes, it would run in the mailman-web container in the same way the `manage.py` command is run for example. Looking at https://asynchronous.in/docker-mailman/web/#django-management-commands, I think this would be something like ``` $ docker exec -it mailman-web python3 prune_arch3 yyyy-mm-dd ``` after saving the prune_arch3 file in the same place as manage.py -- 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: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 6:35 AM, Jered Floyd wrote: > > OK -- my turn to ask a question... > > I created a new domain and lists in my (functioning) Mailman 3 install. > > Messages to these new lists are successfully delivered via LMTP to Mailman and then disappear. They are in the shunt queue, with a source queue of "in". There are no exceptions logged in my mailman.log. When Mailman shunts a message, it always attempts to log the exception to its error.log which by default is written to mailman.log. If you can't find these messages, either you aren't looking in the right place or Mailman doesn't have permission to write the log. > Unshunting the message has no effect, and no logs are generated. Actually, the message is moved back to the `in` queue and shunted again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > Ok I did install using the > https://docs.mailman3.org/en/latest/install/virtualenv.html > > I added > ``` > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > ``` I hope you didn't add the above literally without replacing www.example.com with your actual host name. It should be ``` POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' ``` > to /etc/mailman3/settings.py and restarted mailman services > > However I'm still getting the same error from mailman.log > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > port=8000): Read timed out. (read timeout=5) I don't understand why it should still be trying to connect to localhost:8000. Also, I don't understand why localhost:8000 times out. What is your setting for localhost in /etc/hosts? it should be `127.0.0.1`. If it is `::1` that could be the issue. > Not sure if I'm editing the correct config file. /etc/mailman3/settings.py should be correct. -- 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: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Mark Sapiro

On 8/25/25 12:42, Flo via Mailman-users wrote: > Hi, > > I have setup in Debian Trixie mailman3-full and came that far, that I > have created a mailing list. I can sent emails to the members. Your primary support resource for the Debian package is Debian. See https://wiki.list.org/x/12812344 > However when I send from an email which is non-member the message is > held. If I want to accept this message as list admin, I get: > > `An error occurred while processing your request.` > > And I get an email: > > `Internal Server Error: /mailman3/postorius/.../held_messages > > TemplateSyntaxError at /postorius/lists/.../held_messages > 'humanize' is not a registered tag library. Must be one of: You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in settings.py. If you Debian packages don't do this, it should definitely be reported to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 6/24/16 8:18 AM, John Griessen wrote: > On 06/18/2016 02:10 PM, Mark Sapiro wrote: >> I think in the >> long run, you'd be better off with Mailman 3. > > > Is it time to install version 3? > > Is that going to work with different rewrite rules behind nginx? > > Will it cure my problem with moderation and nginx and https? If you are going to post to mailman-users(a)mailman3.org, please join the list. That way you will see replies to your posts such as the one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. You can join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. The reply addresses your first question. With respect to your other questions, I think you have resolved your http/https issues in MM 2.1. MM 3 works similarly, but perhaps more obviously. When you create a domain in MM3 you specify a web URL for the domain's web UI. If this is an https URL, you won't have the issues you saw. There is another way to address this, and that's in the web server (nginx in your case) when you configure the web server to redirect http to https with a 301 Moved Permanently status (or maybe a 302), this tells the browser to issue a GET for the new URI, even if the original request was a POST. Thus the POST data is lost. That is the underlying issue. If instead, you configure the web server to issue a 308 Permanent Redirect instead, this tells the browser to issue a request for the new URI using the original GET/POST/whatever method, so the browser SHOULD reissue the original POST to the new URI. This will work provided the browser recognizes 308 and acts appropriately. Thus, fixing the scheme in Mailman is the more reliable solution as it doesn't depend on the browser knowing what to do. See, e.g., <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 1 month

Search results for query "sapiro"