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

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/16/21 9:46 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > Unfortunately the provided options didn't work out either: > > 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 ************* mailing list >>>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm > workflow.restore() > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore > raise LookupError(self.token) > LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b It appears that although the token was in the pended table, it wasn't in the workflowstate table. I have no clue how this happened. > I noticed that the mail address was also listed as a non-member. > After deleting it there, I could not accept the subscription either. > Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. > > I'll monitor if such cases will happen again. Hopefully it won't happen again, but at least you have a workaround. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Mailman3 is wrongly display name a list member

by Mark Sapiro

On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:48 AM, Marc SCHAEFER wrote: > > May I just modify those files, and is there any way to see, in the web GUI, > where those files are referenced? Yes, you may modify them. The search algorithm for templates is described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… however, this is only for templates which have no entry or a mailman:/// entry in the template table in the database. Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > In the database itself, the template table is empty (as seen in the GUI) and I > did not see the text "web_page_url" in a dump of the database, so I have some > issues to understand how this is used by Mailman (except direct file access > to /var/lib/mailman3/templates?) It is by direct access following the search algorithm. If you are looking at templates in Postorius, these can be created and will place the template in the postorius_emailtemplate table in the database and an entry in the templates table with a URI beginning with the POSTORIUS_TEMPLATE_BASE_URL setting to retrieve the template via the Postorius API. The Postorius template UI should show the current value for a template not yet set in Postorius, but it doesn't. See https://gitlab.com/mailman/postorius/-/issues/366. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/20/22 19:54, Dan Caballero wrote: > I'm getting an unexpected error when I try to clear all the held messages. Any ideas what could be wrong here? > ``` > (mailmanve) mailman@11f52637274a:/var/www/mailman-www$ mailman shell -l jewishlife(a)caltech.edu > 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 jewishlife(a)caltech.edu mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > Traceback (most recent call last): > File "<console>", line 3, in <module> > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: cannot unpack non-iterable NoneType object ``` There is a corrupt request with a request id that doesn't exist. Try something like: ``` >>> from mailman.interfaces. >>> requestdb = IListRequests(m) >>> for req in requestdb.held_requests: ... if req.request_type == RequestType.held_message: ... if not requestdb.get_request(req.id): ... print(f'Bad request id: {req.id}, deleting') ... requestdb.delete_request(req.id) ... ``` -- 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: Archives with encoding characters

by Mark Sapiro

On 3/4/20 8:55 AM, Seth Seeger wrote: > Hello everyone, > > I have a few (but not all) members complaining that their digests are full of coded characters. Two examples below were forwarded to me: > >> What I ended up doing was creating 2 "practice lines" in the centre of=20 >> our big teaching circle (I always teach new figures in a big circle) -=20 >> which each had 3 people set up in a line with generous space between,=20 >> and first=C2=A0 I walked through one of those lines myself starting first= >> =20 > > and > >> Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= >> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= >> eft > > What is the cause? Is there anything I can do about it? The cause is a quoted-printable encoded message body not being decoded. This may or may not be a Mailman bug, but if as Mark Dadgar suggests, it only happens with some MUAs, the issue might be in the MUA. To understand more we'd need to see the actual raw digest message from the list, or maybe just a raw incoming message that winds up like that in the digest. -- 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: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/14/23 2:09 AM, Alex Schuilenburg via Mailman-users wrote: > > I am migrating from mailman 3.2.1 & mailman3-web 0+20180916-8 on Debian Buster to mailman 3.3.8 & mailman3-web 0+20200530-2.1 on Debian bookworm, have mailman3 and mailman3-web configured (and running on bookworm) from the initial install. But when I use the mailman3-web 0+20180916-8 database (after stopping mailman3 and mailman3-web) on bookworm, unfortunately migrate fails: ... > But the migrate fails at the first operation: > # mailman-web migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > Applying contenttypes.0001_initial...Traceback (most recent call last): ... > MySQLdb._exceptions.OperationalError: (1050, "Table 'django_content_type' already exists") You are attempting to apply migrations that have already been applied. Apparently the django_migrations table is inconsistent with the state of the database. > Indeed the table django_content_type already exists on 0+20180916-8 . Apart from fields changes, there are an additional 4 tables in mailman3-web 0+20200530-2.1 > > I managed to import the mailman 3.2.1 database to the mailman 3.3.8 database, and all lists, subscriptions and settings looks fine. > > So how can I upgrade my existing mailman3-web database? This appears to be a Debian package issue. I suggest you ask Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: [Mailman-Developers] Re: Help on Gitlab

by Mark Sapiro

Plese keep the thread on the list. On 3/8/24 6:36 AM, Daniel Azubuine wrote: > Sir, I get this error > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python: can't > open file '/home/daniel/Documents/repos/mailman/mailman/setup.py': > [Errno 2] No such file or directory > ERROR: invocation failed (exit code 2)/ > _______________________________________________ summary > ________________________________________________ > ERROR: qa: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python > /home/daniel/Documents/repos/mailman/mailman/setup.py --name (exited > with code 2) > when i run tox -e qa. What is your tox version (tox --version)? You shouldn't need this, but adding ``` skipdist = True ``` in the [tox] section of tox.ini may help. > I also get this when i run tox -e py310-diffcov > ------------- > src/mailman/interfaces/listmanager.py (75.0%): Missing lines 37 > ------------- > Total: 4 lines > Missing: 1 line > Coverage: 75% > ------------- > > ERROR: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/py310-diffcov/bin/diff-cover coverage.xml --fail-under=100 --compare-branch origin/master (exited with code 1) This is expected output in this case. Line 37 in your src/mailman/interfaces/listmanager.py is not covered by any tests. Modifying the test_cannot_create_a_list_twice test in src/mailman/model/tests/test_listmanager.py to use assertRaisesRegex rather than assertRaises may help. See <https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertRai…>. -- 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: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/03/2017 01:22 PM, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> > >> You need to forward port 25 for SMTP mail delivery and if you want the > >> web UI (Postorius and HyperKitty) accessible from the outside, port 80 > >> for http and/or port 443 for https > >> < > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>> . > >> > > > > I mean for incoming mail redirected from my hostgator hosting, because > when > > I suscribe an email address MM3 sends a confirmation email, so I have to > > reply to be suscribed to the list. > > > As I said, for mail delivery you need to forward port 25 to the Mailman > server. > Ok so I'll redirect in my zentyal firewall the port 25 to my local centos7 with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

On 9/23/23 02:54, Jana Berger wrote: > > I have multiple control messages, all received from my instance which > all contain the "Content-Transfer-Encoding: base64" marker, their > contents is plain text (Content-Type: text/plain; charset="utf-8"), but > they are still encoded using base64. It seems you are saying these messages are valid. I.e. they specify "Content-Transfer-Encoding: base64" and the body is in fact base64 encoded. This is as they should be. > Of course that is not proof, but an indication that it is either done by > the mail server itself or widely across MUAs. As you say, this suggests that some MTA in the path to your user or the user's MUA is responsible for decoding the base64 encoded body but leaving the "Content-Transfer-Encoding: base64" header as is. > Global "Preferred language" is "English (USA)", which is not overridden > by the list in question. I have not changed the default encoding. Is > there a surefire way to detect this? > > My mailman.cfg has no section pertaining to encoding, and all related > files also do not mention encoding. The Subject: and body of these messages should be ascii, not utf-8 unless you have something like ``` [language.en] charset: utf-8 ``` in your mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Single Click Unsubscribe

by Mark Sapiro

On 1/25/24 15:21, olebra(a)samfundet.no wrote: > > To me, "subscribed messages" in the above means the policy applies to > everyone sending over 5k emails daily, whether for marketing or not. > > All the best, > Ole > > [0]: https://support.google.com/a/answer/81126 > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You can always put something like the above "To unsubscribe ..." line in the lists footer as we do. Gmail's web UI renders that as a mailto: link. Further, at least in some cases, Gmail's web UI recognizes the List-Unsubscribe header in the message and provides it's own Unsubscribe buttons in the web UI. Granted, these aren't truly "one click" as they require confirmation, but that can be avoided by setting a list's unsubscribe_policy to `open`. Also granted that Gmail is the 900 pound gorilla here, but unsubscribe links that don't require confirmation are a bad idea. Even if the link contains some kind of encrypted data to ensure it can't be spoofed, there is still a danger if I forward list mail to a 3rd party and they click my unsubscribe link. -- 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

Search results for query "sapiro"