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

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/9/25 10:04, dap1--- via Mailman-users wrote: > > I can now see the list. I can't find the URL for members so I'm not sure if this really worked. Have you created a Django superuser for yourself? mailman-web createsuperuser You need to do that and then go to https://your.host/accounts/login/ and log in as that user. Then if you go to https://your.host/mailman3/lists/lllllllllll@ddddddddd.net/ you will see a Users dropdown in the secondary nav bar and can view members, nonmembers, moderators and owners. You can also go directly to https://your.host/mailman3/lists/lllllllllll@ddddddddd.net/members/x/ where x is one of member, nonmember, moderator or owner. > It seems the archives were imported but when I go to that page there are no entries: To what URL are you going? Are you logged in? depending on the list's archiving settings you may need to be logged in as a superuser or list member to see the archives. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Postfix Hooks and Fetchmail

by Mark Sapiro

On 11/13/25 08:33, dap1--- via Mailman-users wrote: > I'm using fetchmail to feed mailman3 and am having a problem with the postfix hooks. My list name is llllllllll(a)ddddddddd.net. However, fetchmail passes the email to lllllllllll@localhost. So I am getting this error in the mail log: > > Out: 550 5.1.1 <llllllllll@localhost>: Recipient address rejected: User unknown in local recipient table > > Is there something I need to add to mailman's recipient table, fetchmail or an alias in postfix? You have probably configured Postfix per https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta which is based on https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. The issue is the postfix_lmtp file referred to in transport_maps and local_recipient_maps only have addresses in the ddddddddd.net domain. I think you can solve this by instead adding 'localhost' as an alias domain for the ddddddddd.net domain and configuring Postfix per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[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, 11 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, 5 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

8 years, 2 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, 10 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, 7 months

[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, 6 months

[MM3-users] Re: The doubled entries issue

by Mark Sapiro

On 11/11/23 23:56, Lars Bjørndal wrote: > > Thank you. The script I try to run, is found here: https://gitlab.com/mailman/mailman/-/issues/657 > > I named the script fix-doubled-entries.py. When I try > > `mailman shell --run ./fix-doubled-entries.py` I get: This is not the way to run a script with `mailman shell`. See ``` mailman shell --details ``` for info. However, that script cannot be run as is by `mailman shell --run`. It can be run by invoking `mailman shell` interactively and copying and pasting it, or if your Mailman is installed in a venv it can be run with the venv active by `python ./fix-doubled-entries.py`. However, that script will not fix your issue because you don't have multiple mhonarc entries for a list. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and as it says, Tell us more about the "duplicate entries" error, and if possible copy it exactly from where you found it originally, including any traceback. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: add / remove / set moderation bit of non-members via mailman shell

by Mark Sapiro

On 2/7/24 02:37, Zaheer Abbas wrote: > > I do the above via postorius because I couldn't find a way to do this via > mailman shell. Something like ``` mark@msapiro:~$ mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> NEW_NONMEMBERS = [('First User', 'user1(a)example.com'), ... ('Second User', 'user2(a)example.com'), ... ('Third User', 'user3(a)example.com'), ... ] >>> from mailman.app.membership import add_member >>> from mailman.interfaces.subscriptions import RequestRecord >>> for display_name, email in NEW_NONMEMBERS: ... record = RequestRecord(email, ... display_name=display_name, ... delivery_mode=None, ... ) ... member = add_member(m, record, role=MemberRole.nonmember) ... member.moderation_action = Action.accept ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Search results for query "sapiro"