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

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/10/21 6:37 AM, Duane Raymond wrote: > Hi Mark, > > I think I have it working thanks to some hints in your questions. here is the process I took in case others experience it the same or in case anyone wishes to comment! > > When I use the mailman shell comment it seems to reflect just what you posted (I also tried test.campaigningforum.com and got the same result): > (venv) mailman@mail:/opt/mailman/mm$ mailman shell -l test(a)campaigningforum.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 test(a)campaigningforum.com mailing list > >>> > > Was there something beyond running this and getting the output I was supposed to enter? Was an error expected if one members doesn't have an associated address record? Did you enter this following the initial >>> prompt? >>> for mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... If so, it was expected to print the representation of the user object and that objects addresses list fo any member whose address attribute is None. ... > This time the posting was archived and I did get an acknowledgement of the post, but despite having the option "Receive own postings" set to "yes", I didn't receive it. As you have determined, this is a googlemail issue. See <https://wiki.list.org/x/4030680>. -- 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: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://gitlab.com/mailman/mailman/-/issues/385 which was fixed in Mailman 3.2.0 by https://gitlab.com/mailman/mailman/-/merge_requests/333. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Bug in 2.1.36?

by Mark Sapiro

On 11/12/21 1:06 PM, Joel Lord wrote: > I'm not sure if this is a bug or something about the new CSRF fix > doesn't get along with something I have (mis)configured, but this > definitely seems to be related. Sadly the script I use to backup > mailman before upgrading I recently stopped backing up the lists > themselves, so going back to 2.1.35 doesn't seem to be an option due to > the .pck file version bump. Here's the trace I get: > > Traceback (most recent call last): > File "/mailman/mailman-${domainslug}/scripts/driver", line 117, in > run_main > main() > File "/mailman/mailman-${domainslug}/Mailman/Cgi/admindb.py", line > 342, in main > print doc.Format() > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 352, in Format > output.append(Container.Format(self, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 267, in Format > output.append(HTMLFormatObject(item, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 53, > in HTMLFormatObject > return item.Format(indent) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 445, in Format > % csrf_token(self.mlist, self.contexts, self.user) > File "/mailman/mailman-${domainslug}/Mailman/CSRFcheck.py", line 53, > in csrf_token > mac = sha_new(secret + `issued`).hexdigest() > TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' > > Running Python 2.7.5 > . Thanks for the report. I think the issue is caused by the fix for https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a list admin is trying to handle moderator requests on a list that has no moderator password. I'll investigate and try to put out another fix later today. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/16/23 05:34, Jeremy Stanley wrote: > > Clearly a total misreading on my part of the Django documentation to > which you referred earlier. It talks about having to feed Django > multiple settings.py files with different SITE_ID values and running > migrate to configure them, then links to the document on migrations > which starts out explaining how to use makemigrations to create > them. I took that to mean creating and configuring Django sites from > the command line required supplying customized database migrations. > > The particularly misleading bits are where it says: > > "To set the correct name and domain for your project, you can > use a data migration." > > "In order to serve different sites in production, you’d create a > separate settings file with each SITE_ID" > > It doesn't seem to talk about using django_admin at all (or if it > does, it's not mentioned by name, maybe assuming the reader knows to > use it in order to perform the necessary steps). Yes, that doc really isn't appropriate for your purpose, but it's the only one I could find on Django sites. Most of what it talks about is for more complex situations than ours and whatever bits are relevant are already done in Postorius/HyperKitty. Sorry for leading you astray. > Thanks for the clear examples! If these are available somewhere in > Django's documentation, I did a terrible job of searching for them. I don't think Django's docs address the simple task of adding a site. -- 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: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Mark Sapiro

On 3/5/26 23:25, Thomas Krichel wrote: > > I have > > root@darni /etc/mailman3 # head -15 /etc/mailman3/settings.py > # Mailman Web configuration file. > # /etc/mailman3/settings.py > > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > > # Settings below supplement or override the defaults. > # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > del ACCOUNT_EMAIL_REQUIRED > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] These are good. > root@darni /etc/mailman3 # tail -17 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/settings/mailman.py > ### added by ToK > > #: Django Allauth > #ACCOUNT_AUTHENTICATION_METHOD = "username_email" > #ACCOUNT_EMAIL_REQUIRED = True > #ACCOUNT_EMAIL_VERIFICATION = "mandatory" > #ACCOUNT_UNIQUE_EMAIL = True > > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', > 'password2*'] > ACCOUNT_EMAIL_VERIFICATION = "mandatory" > ACCOUNT_UNIQUE_EMAIL = True > ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False > > del ACCOUNT_EMAIL_REQUIRED > ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] These should be unnecessary as the ones that actually change anything are overridden by the above changes in /etc/mailman3/settings.py. > Restarted > > root@darni /etc/mailman3 # systemctl restart mailman3 ; systemctl restart mailmanweb > > Same old. > > (venv) root@darni ~ # mailman-web migrate > System check identified some issues: > > WARNINGS: > ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] what does mailman-web diffsettings|grep ACCOUNT report? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

On 7/28/20 5:40 AM, Brian Carpenter wrote: > Ok, I see the other thread concerning this was deleted, along with my reply. Here it is again. It wasn't deleted. It's on another list - mailman-users(a)python.org. Here's my reply to your post On 7/27/20 7:13 PM, Brian Carpenter wrote: > > This is the client that I asking about in my post. She said what I did, did not work. This is what I did: > > 1. Get into a venv as user mailman > > 2. #mailman shell >>>> from mailman.model.mailinglist import MailingList >>>> mlist = MailingList('listname(a)listdomain.org') >>>> mlist.emergency = False >>>> commit() > ctrl-d (just to be on the safe side) > > Did I not follow your instructions correctly? That should work. I don't know why the result would be any different from what Johanna did. On 7/27/20 8:58 PM, Johanna Amann wrote: > As a small followup for anyone encountering the same problem in the > future - I ended up just changing the value in the database directly. > > So - an “update mailinglist set emergency = FALSE;” (or the equivalent > in the dialect of the database one uses) removes the emergency flag from > all mailing lists. That is another approach which is valid, but why the `mailman shell` method I suggested wouldn't do the same thing, I don't know. Of course, if you're doing multiple lists, this method is easier because just one simple query does them all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: equivalent mailman 3 commands from 2.0

by Mark Sapiro

On 10/25/21 9:16 AM, bob B wrote: > For my 2.0 environment, I have scripts to dump list info, but i can't find the equivalent in mailman 3, for some commands, for example I use: > > /usr/lib/mailman/bin/list_lists which equates in mailman3 to "mailman lists" > /usr/lib/mailman/bin/list_members which equates in mailman3 to "mailman members [listname]" > > But I also use > /usr/lib/mailman/bin/list_admins [listname] > /usr/lib/mailman/bin/config_list [listname] > > Are there equivalent command line commands to get this info in mailman3? for list_admins you can use `mailman members --role administrator [listspec]`. See `mailman members --help`. There is no mailman command equivalent to config_list at this time > The mailman3 "mailman withlist [listname]" takes me into an interactive prompt not sure where to go from there. From there you enter Python statements to do what you want. e.g. ``` $ /opt/mailman/mm/bin/mailman withlist -l list.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.example.com mailing list >>>for property in dir(m): ... if not property.startswith('_'): ... print(f'{property}: {m.__getattribute__(property)}') ... ``` You can also create scripts to run with the --run option, See `mailman withlist --details`. > I can use the API > > curl --user [ADMIN]:[password] http://[IP]]/3.1/lists/[listname]/config | python3 -m json.tool > > > But just curious if there is a command line equivalent like in mailman2? Not at this time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/12/22 22:03, Onyeibo Oku wrote: > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. I would suggest you not do that and just install mailman in `/opt/mailman` per https://docs.mailman3.org/en/latest/install/virtualenv.html. If you don't want to do that, you will have to replace all occurrences of `/opt/mailman` in the doc with `/usr/lib/mailman`. > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? Yes. The suggested change to .bashrc assumes you are logging in as the Mailman user, not switching via `su`. You might try `sudo -u mailman bash` or `sudo -u mailman -i` instead of `su`, but I'm sot sure if that will help. > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" I think if you have `var_dir: /usr/lib/mailman/mm/var` in the /etc/mailman3/mailman.cfg file you create per https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, then starting Mailman core `/usr/lib/mailman/venv/bin/mailman start` will create it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

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

by Mark Sapiro

On 3/30/23 07:36, Gregory Edigarov wrote: > I have the same issue now. > that's happen when I try to open held messages > > This is what I have in my logs: > > File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in _resource_as_dict > assert resource is not None, resource > AssertionError: None What is the full traceback? > that is the default mailman3 debian package. And your primary support resource should be Debian. > GNU Mailman 3.3.3 (Tom Sawyer) > > things were working smoothly for a very long time. it started after disk array disaster. we installed the thing to another server, and restored the database from backups. > > I've tried to use this magic: > ``` > The variable 'm' is the odoo_leads(a)qarea.org 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: > ... if not requestdb.get_request(req.id): > ... print(f'Bad request id: {req.id}, deleting') > ... requestdb.delete_request(req.id) > ... >>>> ``` > but no success. > is there any way to fix this? I think you're on the right track with the above `mailman shell`, but evidently the issue is different. You might try ``` >>> requestdb = IListRequests(m) >>> for req in requestdb.of_type(RequestType.held_message): ... if not requestdb.get_request(req.id): ... print(f'Bad request id: {req.id}, deleting') ... requestdb.delete_request(req.id) ... else: ... print(f'Held request: {requestdb.get_request(req.id)} ... >>> ``` To see what the requests look like. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/28/25 01:14, Mark wrote: > > Then I created a template using Postorius and updated the uri in > mailman.templates to: > > file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… - and that works. Which says get the template from the file system at that location and don't ask for it from Postorius at all. This would be the default action if there were no entry for this template in the mailman.template table at all. I.e. you now have a template in Postorius, but it is not used. > It's looking promising. Now I just need to modify my script that > periodically copies the data from the > "mailmanweb.postorius_emailtemplate" table to a file and updates the uri. > > Why it won't handle the templates in the database I don't know. But at > least I can get a work-around solution in place now. If you want to continue to use the template at /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt just delete the template from Postorius and update that file directly. If Postorius template updates don't work because of web server caching or whatever, just don't use them and use templates in the /opt/mailman/mm/var/templates/ hierarchy instead. You can create sitewide templates at /opt/mailman/mm/var/templates/site/en/*, domain specific templates in /opt/mailman/mm/var/templates/domains/en/* and list specific templates in /opt/mailman/mm/var/templates/lists/<list-id>/en/ without any entries in the mailman.template table. Note that sitewide templates can be the most useful and can't be created in Postorius anyway. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Search results for query "sapiro"