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

[MM3-users] Re: Button unsubscribe

by Mark Sapiro

On 12/7/18 7:22 AM, erlonmz(a)hotmail.com wrote: > how to put a button unsubscribe in the message together with the part > > " LIST mailing list -- LIST@domain > To unsubscribe send an email to LIST-leave@domain' > > I want to put this button in the emails to the users unsubscribe. it would already send the confirmation tolkien. > > my question is, has some place where generated tolkien is saved in mailman files? No. The confirmation token is not generated until the unsubscribe request is received so there's no way to know it in advance. Further, a button requires HTML and the list's footer is plain text. Finally, one-click unsubscribe without confirmation is dangerous. People forward list messages to others and even reply to the list without removing the one-click unsubscribe link and then wonder why they get removed from the list. At least with confirmation, they only wonder why they got a confirmation request. -- 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: Template for Password Reset Email

by Mark Sapiro

On 11/14/24 13:57, Mark wrote: > > I have a list and user account set with French as the preferred language. > > Most message emails (such as the Welcome email) all arrive in French, > but not the Password Reset email (shown below) - it arrives in English. > > I'm guessing that there may not be an .mo file for it. This message comes from django-allauth. there is a French message catalog for it. These are in site-packages/allauth/locale/fr/LC_MESSAGES and should be good. You can always run `django-admin compilemessages` to update all the .mo files for all the projects. However, the issue is probably that Django doesn't get the language context from the list's preferred language. In fact, the password reset is not in a list context at all. See https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… for how it determines the language to serve. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 11:01, Arte Chambers via Mailman-users wrote: > Thanks, this was helpful. It was a message I sent to the list that was just > an image attachment with no body text. I noticed this other thread > about messages > with attachments, without text discarded silently > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I am attaching the pickle file hoping that it helps anyone researching this > issue. I think the underlying issue is the same as in that thread. While your message has mime structure multipart/mixed multipart/alternative text/plain <- empty text/html image/jpeg If you have content filtering Collapse alternatives = yes, it will become multipart/mixed text/plain <- empty image/jpeg after collapsing alternatives and that will trigger the error. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for a patch (not yet tested) that I think will fix this. -- 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: Cannot Create New List

by Mark Sapiro

On 11/11/25 08:45, dap1--- via Mailman-users wrote: > Not sure what that means. I would expect to allow any domain to access mailman-web since members can come from anywhere. Isn't that what the '*' means?. > > ALLOWED_HOSTS = ["*", > "localhost", # Archiving API from Mailman, keep it. > "127.0.0.1", > # "lists.your-domain.org", > # Add here all production domains you have. > ] You should not have the "*". The remote host accessing mailman-web does not need to be in ALLOWED_HOSTS. The host that needs to be allowed is the host that is receiving the request. You should remove the "*" as it's too permissive, and as it says, add any and all host names that external users use to access the system. That's why it's called ALLOWED_HOSTS rather that CLIENTS. And have you tried logging in using one of those host names rather than localhost? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: alembic version

by Mark Sapiro

On 3/6/26 23:22, Thomas Krichel wrote: > ... > Mar 07 07:01:03 darni mailman[1209747]: alembic.util.exc.CommandError: Can't locate revision identified by '8cc1f79f4459' ... > root@darni ~ # sudo -u postgres psql -d mailman3 > psql (18.2 (Debian 18.2-1)) > Type "help" for help. > > mailman3=# SELECT version_num FROM alembic_version; > version_num > -------------- > 8cc1f79f4459 > (1 row) That's not what it's complaining about. You have to look at /usr/local/mailman/venv/lib/python3.13/mailman/database/alembic/versions. Those are all the alembic migrations. Each one has a Revision ID: and a Revises: making a chain. There are tools to display that chain. With your venv active do ``` alembic -c /usr/local/mailman/venv/lib/python3.13/mailman/config/alembic.cfg history ``` What does that show? I suspect there is some issue between the database and the code. The version_num in the alembic_version table and the migrations. The version_num is the current migration so that `mailman-web migrate` knows which additional migrations to apply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Migration from old server to new server failed

by Mark Sapiro

On 2/16/24 07:12, Helio Loureiro wrote: > - start mailman3 and mailman-3web > - run mailman3-web migrate You should run mailman3-web migrate when mailman-3web is not running. > django.db.utils.OperationalError: (1050, "Table > 'hyperkitty_mailinglist_moderators' already exists") > > I tried to drop the table, but then it complained about another one. I > dropped all the complained tables and as result hypperkitty never > started. So I went back to see why the first error happened. The errors occurred because you had recently added tables in your database so they couldn't be added by the migrations. Dropping the tables was the correct thing to do. Did you ultimately successfully run all the migrations? When you say `hypperkitty never started`, what exactly does that mean? What happens when you try to access the archives? Can you access postorius? Are any errors logged in mailman3-web's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: sync_members via email

by Mark Sapiro

On 1/20/25 13:45, kbaumann(a)chicagoiww.org wrote: > I can use email to get a list of members: > > To: mylist-request(a)lists.theserver.org > Subject: who (password) The password argument is Mailman 2.1 only. If provided for Mailman 3 it will result in an error Unrecognized or invalid argument(s): (password) > Any chance that a sync_members could be accomplished in a similar fashion? Looks like it's only available from the console, but I'm asking anyway to be sure. You are correct, there is no email sync members function. The issue for this is authentication. As far as the who command is concerned, the only authentication is whether the sender is authorized to see the result. In the case of a spoofed sender, no harm is done as the result will be sent to the sender address. The same method could not be used for syncing members because if the sender were spoofed, the syncing would be done. -- 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: mailman-core installation on debian stretch/maria-db

by Mark Sapiro

On 03/10/2018 01:53 PM, Wolfgang Bock wrote: > > Hi, > > I need your help: I installed mailman3 on a debian stretch environment > and faced following problems. How? Did you install <https://packages.debian.org/stretch-backports/mailman3-core>? If so, these are probably issues with the Debian package. You may find <https://gitlab.com/mailman/mailman/issues/455> to be of interest. If you installed Mailman some other way, How? > 1. On "mailman start" I got the error message: > Starting Mailman's master runner > /usr/bin/python3: can't open file '/sbin/master': [Errno 2] No such file > or directory Where is it? What does 'which master' show? > 2. connection to maria-db > In debian stretch maria-db is running. In my mailman.cfg I set: > [database] > class: mailman.database.mysql.MySQLDatabase > url: > mysql+pmysql://#username#:#user-pawo#@localhost/#databasename#?charset=utf8&use_unicode=1 should that be mysql+pymysql ? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/29/20 5:17 AM, Brian Carpenter wrote: > > On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >> On 29/10/2020 01:57, Brian Carpenter wrote: >>> With Mailman 3, every list owner has the ability to remove a reply in >>> a thread, a complete thread, and even the entire archives. That is a >>> welcome difference from MM2 in my opinion. >> >> A very welcome difference, only I don't see this option in the web >> interface of my debian 3.2.1 installation. Is this a shell only >> option, 3.3 feature or configuration option I have missed? > It is not a shell option. It can be done via Hyperkitty but I am not > sure when that feature showed up. Actually, with current HyperKitty, only site admins can remove messages or threads or the archive. The ability for list owners to do it is <https://gitlab.com/mailman/hyperkitty/-/issues/261>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 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 12:13, Wikinaut wrote: > I have such entries again in the postorius list "=?utf-8?q?Alexandro....", even after having deleted the user twice (there were no entries), the text file has nothing special, uchardet says "UTF8". Presumably these are being picked up from an email header that has the display name properly RFC 2047 encoded but then not decoded for the database address or user record. This could be a bug, but without knowing the exact scenario that results in these encoded display names, it's difficult to know where the bug might be. In what postorius list (members or non-members) are you seeing these? Are there log messages about them in the subscribe log (by default written to mailman.log)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Search results for query "sapiro"