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

[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

7 years, 9 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/13/26 12:25, Ibiam Chihurumnaya via Mailman-users wrote: > > Mark Sapiro wrote: > > You normally don't need to set any of those. The defaults should be fine > > for a local MTA listening on port 25, however what's in /etc/hosts for > > localhost. If it's the IPv6 address ::1, I suggest changing it to 127.0.0.1. > > Yes, I did change it after you'd said so in the other thread. > > In that case I can't explain why something about the confirmation mail > doesn't show up in the MTA's log. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Is there anything in the uwsgi-error logs that'll indicate an issue with this? I just tried again and I didn't receive the confirmation, I registered a new user. The logs also don't show anything about this, except the uwsgi log which shows the event.

8 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

9 years

[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

6 years, 8 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

6 years, 5 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

6 years, 4 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, 11 months

[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

2 years, 8 months

[MM3-users] Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Mark Sapiro

On 8/5/25 13:12, Wikinaut wrote: > > After a new add/syncmember, that spooky entry was up again! And were any of the spooky entry email addresses in the input to that command? If so what was the exact display name for the line containing that address. If that looked normal, > Then I used mailman delmembers --fromall --no-goodbye-msg --no-admin-notify -m <this@address>: > Then after a new add/syncmember, that entry was gone and the correct entry was shown. > > That means, that somewhere some remains were stored somewhere. Possibly in an Address record. Display names are in User Records and Address records. The script you ran to delete users should have removed User records, but an Address record for the address with the odd display name may have remained. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 14:01, Thomas Stein wrote: > Am 2024-04-25 22:03, schrieb Mark Sapiro: >> >> I don't know how things are arranged in the Debian/Ubuntu package, but >> you may have a settings.py which at the end does something like >> ``` >> try: >> from settings_local import * >> except ImportError: >> pass >> ``` >> If that is the case, adding the above snippet to the end of >> settings_local.py should work. > > Yes, that's the case. I added the snippet in question to > settings_local.py but this leads to another error: > > File "/usr/share/mailman3-web/settings.py", line 503, in <module> > from settings_local import * > File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> > x = list(MIDDLEWARE) > ^^^^^^^^^^ > NameError: name 'MIDDLEWARE' is not defined > dpkg: error processing package mailman3-web (--configure): Yes. I understand. In your case, MIDDLEWARE is only defined in settings.py and not in settings_local.py. As I understand it originally you added ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to settings.py and you say it didn't help. I don't know why that wouldn't work as long as there is no setting for MIDDLEWARE in settings_local.py and you added that after the MIDDLEWARE setting in settings.py. When you say it didn't help, do you mean you still get the django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE message or something else? I note that the original post in this thread refers to /etc/mailman3/mailman-web.py which is presumably where the package ultimately puts the Django settings, and I don't know what `dpkg --configure` is doing. One thing you could try is in settings_local.py, put ``` from settings import MIDDLEWARE x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to work around the NameError. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Search results for query "sapiro"