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

[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

1 year, 7 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

5 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

5 years, 5 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/10/22 22:22, Stephen J. Turnbull wrote: > > Will let you know if I find anything. Mark will be back soon, too. Yes, I'm back and am looking at this. I'm looking at the traceback at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and I would like to get a copy of the shunted 1662376669.3194733+25b74de3b7cd8a28d0c3cf5b6cc6fc582726efec.pck file. If that is not available, any of the shunted files from the same `Uncaught runner exception: 'list' object has no attribute 'encode'` will do. Also, the same post contains a traceback from mailman_hyperkitty indicating the message has no Message-ID header. This is possibly related to the fact this is an anonymous list. For anonymous lists, the original Message-ID is removed because it can reveal the sender's domain, but it should always be replaced by a generated one. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/clean… -- 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: [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

9 years

[MM3-users] Re: Customizing Look and Feel?

by Mark Sapiro

On 12/27/18 7:42 PM, Joel Lord wrote: > Is it possible to customize the look at feel of the web interface at > all? I have some lists that really require that subscription requests > include full name, to make the workload on the moderators, well, > workable in keeping a closed list tight. I've found where the "Your > name (optional)" text is in list_forms.py, but modifying that strikes me > as a poor plan. > > Changing that text would be lovely. Actually making that field required > would be seriously awesome. > > Is this possible in the current code base (3.2.0) without doing > ill-advised things modifying source code? None of this is really possible in Postorius without modifying source code. However, Postorius is just an example of a web list management UI. While it is non-trivial, it is possible to build your own web UI that either communicates directly with Mailman core's REST API or communicates via MailmanClient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Disabling max_message_size and send_welcome/goodbye_msg globally or by API

by Mark Sapiro

On 10/10/2017 12:04 PM, Peter Mueller wrote: > > is it possible to turn off max_message_size and send_welcome_msg / > send_goodbye_msg globally? Not for existing lists, but for new lists you can create a style with these settings and make it the default style. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for how you might do that. > If there are no global options, how can I turn off these feature using the > REST API? > In python you can do it with >>> mlist.max_message_size = 0. > If I send a PATCH request to lists/some@list/config with body > max_message_size=0, I get "Unknown attribute". Same for send_welcome_msg > and send_goodbye_msg. max_message_size and send_goodbye_msg are not currently exposed in REST. See the definition of ATTRIBUTES in mailman/rest/listconf.py for what is. You should be able to PATCH send_welcome_msg via REST. I don't know why that didn't work for you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: SUBSCRIBE_FORM_SECRET in MM3?

by Mark Sapiro

On 1/30/20 1:50 AM, Gila Halpern wrote: > I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? This feature in MM 2.1 is not very effective. On mail.python.org, this feature as well as reCAPTCHA is enabled (e.g. <https://mail.python.org/mailman/listinfo/mailman-users>) and we still get periodic attacks of robotic subscribes that get around these measures. To answer your question, no, this does not exist in Postorius which is an entirely different, Django based web UI. Django may have some protections built in; I'm not sure about that, but there's nothing in Postorius itself like this MM 2.1 feature. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/2/20 12:51 AM, Samir Faci wrote: > A few questions about an Ubuntu install. > > I managed to add my domain to hyperkitty, created a new list and now i'm > getting this behavior: > AttributeError: module 'time' has no attribute 'clock' > I'm on python 3.8.2 It time.clock() went away in Python 3.8. Mailman versions older than 3.3.0 are not compatible with Python 3.8. You need to upgrade Mailman core. > Question #2. I'm setting up mailman 3 on sqlite for simplicity's sake. Do > people find the performance of mysql / postgres worth the upgrade? It depends on the size of your installation - how many lists, how many list members, frequency of posts and so on. You may find <https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgre…> of interest. > 2B. Is there a migration path if I want to switch to mysql at a later date? The migration path mostly consists of migrating the data from the SQLite database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Mark Sapiro

On 6/15/20 12:37 PM, Gilles Filippini wrote: > > There are 4 emails stored into this folder. 3 of them are spam, and the > last one is a legitimate email. This is annoying that such emails could > accumulate and stay into var/archives/hyperkitty/spool/ forever, causing > more and more hyperkitty errors. > > Any idea how to make their processing more error proof? Change the offending .encode() method to add errors='replace'. The traceback from the error should tell you where it is. You could also open an issue at <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If you do that, please include an error traceback if possible. If there is not a traceback in mailman.log associated with the error, there might be one in HyperKitty's log (configured in Django's settings). Also, including enough of a message to duplicate the issue is very helpful. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Search results for query "sapiro"