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

[MM3-users] Re: Problem updating mailman

by Odhiambo Washington

On Sun, 24 Jan 2021 at 00:46, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/23/21 2:56 AM, Odhiambo Washington wrote: > > I am getting this error after I did a git pull and build. > > > > (venv) [mailman3@gw ~/git]$ /opt/mailman/mm/bin/mailman-post-update > > + '[' False == False ']' > > + mkdir -p /opt/mailman/mm/static > > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > +* /opt/mailman/mm/bin/django-admin compress* > > CommandError: An error occurred during rendering > > > /opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.3.4rc2-py3.7.egg/hyperkitty/templates/hyperkitty/404.html: > > /usr/local/lib/ruby/site_ruby/2.7/rubygems/dependency.rb:311:in > `to_specs': > > Could not find 'sass-listen' (~> 4.0.0) among 4 total gem(s) > ... > > > Ruby-sass is no longer supported. Please see the Sass compiler section > at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies > >. > I uninstalled rubygem-sass from the OS. I don't remember consciously installing that because it was never in the guide I followed (which is your own writeup). But I still have a problem: (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 + /opt/mailman/mm/bin/django-admin compress CommandError: An error occurred during rendering /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: */bin/sh: sass: not found* pip3 install sass fails: ..... ERROR: Command errored out with exit status 1: /opt/mailman/mm/venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-vnlujru1/sass_15812b8baa1b405c8130edb21a4f4316/setup.py'"'"'; __file__='"'"'/tmp/pip-install-vnlujru1/sass_15812b8baa1b405c8130edb21a4f4316/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-_f8rgww1/install-record.txt --single-version-externally-managed --compile --install-headers /opt/mailman/mm/venv/include/site/python3.7/sass Check the logs for full command output. The complete failure text is at https://pastebin.ubuntu.com/p/tsB2CCNrQG/ Maybe it's time to blow up everything in the virtualenv and start over because I am not sure what caused this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 2 months

[MM3-users] upgraded Django & flufl.lock now do not receive own postings

by Christian

I just upgraded Django from version 3.0.11 to 3.2.15 receiving this confirmation > Successfully installed Django-3.2.15 asgiref-3.5.2 I also upgraded flufl.lock from version 7.0 to 7.1 > Successfully installed flufl.lock-7.1 Then I restarted mailman, qcluster & gunicorn Now for some reason I'm not receiving my own postings to the list whereas before I was. 'Receive own postings' is still set to yes. Thank you! -----Original Message----- From: David Newman <dnewman(a)networktest.com> Sent: Friday, July 8, 2022 11:29 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14 On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? Yes > > So I would guess you can remove them. Probably you have the relevant > Ubuntu packages cached somewhere, and they're probably available from > Ubuntu if you really wanted them. This system runs Debian 11, with everything installed in a venv. I'm unclear on the relationship between the usual apt* tools and pip, and just do everything Mailman-related using pip. On 7/8/22 7:47 AM, Mark Sapiro wrote: > When pip is doing an upgrade of the xyz package, it renames the existing > package as ~yz and then ultimately deletes the old ~yz package after > successfully installing the new xyz. In this case, the upgrade was > aborted because of the Django<3.1 constraint in mailman-web and > apparently pip then installed Django<3.1 and left the ~jango* > directories behind. Ahhh, that explains it. Thanks for your replies. I've deleted the ~ directories and so far have not noticed any adverse effects. dn _______________________________________________ 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/

3 years, 7 months

[MM3-users] Re: Message shows up individually but not in the thread

by Marvin Gülker

Am 03. November 2017 um 12:35 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > Are you running all of Django's periodic tasks? They are running. This is the excerpt from /etc/crontab: # Mailman jobs @daily mailman bash -c 'cd /home/mailman && . /home/mailman/env3/bin/activate && mailman digests --send' @hourly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs hourly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @daily mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs daily --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @weekly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs weekly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @monthly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs monthly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' @yearly mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs yearly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' * * * * * mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs minutely --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings' 2,17,32,47 * * * * mailman bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs quarter_hourly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings Obviously, mailman-suite is installed at /home/mailman/mailman-suite and owned by user 'mailman', with the actual Django project in the subdirectory 'mailman-suite_project', just as cloned from the Git repository. The only difference from the official guide here is that I took the liberty to place Mailman into two virtualenvs (a Python2 one for the Django project, and a Python3 one for Mailman-Core*). There are no errors reported with this in /var/log/cron.log. And before you ask, the task queue is running as well. The uWSGI config has this: # Setup the django_q related worker processes. attach-daemon = ./manage.py qcluster And the qcluster process shows both up in the process list and is happily logging away in the uWSGI log. Greetings Marvin * It'd be great if the mailman-suite was moved to Python 3 at some point. That way one wouldn't need two separate virtualenvs. -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 4 months

[MM3-users] Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 12:03 -0800, Mark Sapiro wrote: > On 2/19/22 08:33, William Oliver wrote: > > > > So... I run a small mailinglist using mailman3 that has been > > workiing > > great for a couple of months. Last week, all my users from gmail > > got > > kicked off because gmail decided that the list messages were > > "unsolicited email". I didn't find out about it until the users > > hit > > their mailman3 bounce limit. I *thought* would be seeing all the > > bounce messages, but apparently not. I didn't see any config > > settings > > for "see all the bounce messages" so i thought to myself, "Self, > > well > > maybe that's because my mailinglist username doesn't have a > > mailbox in > > /home/listname". > > > Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, > you > will see settings like `Notify owner on bounce increment`, ` Notify > owner on disable` and `Notify owner on removal` under `Bounce > Processing`. Presumable you did get the notification of removal, so > delivery to the owner works. Are the increment and disable (or maybe > just disable if your versions are older) notices set to Yes? Found it. Thanks. > > > > So, I decided to try that. I created /home/listname/Maildir/* and > > logged in as fplist to see if it would put mail there. In order to > > log > > in as listname, I gave the user listname a password. > > > Can't you just reverse those steps. I.e. remove /home/listname/ and > remove the listname user? > Well, that was my inclination, but I didn't know if I needed to have a user by the name of listname. I was afraid that if I just deleted the user "listname" it would cause even more problems. I had created that user back when I was using another mailinglist package -- a Joomla plugin (that doesn't work nearly as well as mailman3). I was afraid to just type in "userdel -r" in case mailman3 needed a "real" user... So, I can just kill the listname user altogether? billo

4 years, 1 month

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 10:29 AM, Dmitry Makovey wrote: > On 09/27/2017 10:20 AM, Abhilash Raj wrote: > > On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > >> On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > >>> On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >>>> I've come across mailman-cli docs: > >>>> > >>>> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >>>> > > > > This is basically one of our GSoC projects which hasn't yet been merged > > with MailmanClient. It uses the REST API to to provide a command line > > client for Mailman, while there hasn't been any in-compatible changes in > > API since this project was finished, I am not sure about the current > > status of it. > > > >>>> yet I cannot figure out what's the official source for the installation. > > > > Official source for MailmanClient is at gitlab.com/mailman/mailmanclient > > and it doesn't have a CLI, the Github project you linked to says right > > on the top that it is not official project (Thanks for that Rajeev!). > > I did see that, thus I was asking the question here. > > > Also, I would say not to use this client to remotely access Mailman, the > > REST API is not meant to be exposed over internet (unless you have a VPN > > or other sort of setup to securely access the box remotely). > > > > in my case - I need to use REST API since we're deploying with docker > and pieces that need to integrate with mailman commands now live in a > different container (and very likely on a different machine). I do need > to be able to execute commands remotely - I can handle securing of that > connection, but it is not an option for me to run "fat" docker > containers thus the only interconnect is via sockets (either UNIX or > TCP). The CLI project is basically a Shell+CLI based on MailmanClient (python library for Mailman API) and Mailman Core's REST API. So, if I understand correctly, this would run commands over REST API like you want. -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] Re: mailman-core installation on debian stretch/maria-db

by Wolfgang Bock

Am 10.03.2018 um 23:44 schrieb Mark Sapiro: > How? Did you install > <https://packages.debian.org/stretch-backports/mailman3-core>? -> No, if I had known this, I wouldn't waste my time for the last 3 days in fiddeling and googleling ... > 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? -> From here: http://docs.mailman3.org/en/latest/prodsetup.html#installing-mailman-core including dependencies > >> 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? -> /usr/local/bin/master -> After I set a symlink to /sbin/master another errormessage occurs >> 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 ? -> Yes, according to: http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html -> Not right?? After that I decided to delete mailman via pip and took a new approach via debians apt-get ... mailman 3 So far so good, now new errormessage: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.5/dist-packages/mailman/bin/mailman.py", line 94, in main initialize(config_path) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 189, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/local/lib/python3.5/dist-packages/mailman/core/initialize.py", line 160, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/local/lib/python3.5/dist-packages/mailman/database/factory.py", line 52, in create database = call_name(database_class) File "/usr/local/lib/python3.5/dist-packages/mailman/utilities/modules.py", line 67, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.5/dist-packages/mailman/utilities/modules.py", line 51, in find_name return getattr(sys.modules[package_path], object_name) AttributeError: module 'mailman.database.mysql' has no attribute 'MYSQLDatabase' Another question is, where can I find the sql-command within the database mailman3 like CREATE TABLE x and TABLE y as I created a database mailman3 which is empty?? Thanks for your help in advance. Regards Wolfgang

8 years

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 11/2/21 20:15, Mark Sapiro wrote: > On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I contributed in january to translate to spanish all the items left in >> Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I >> thought they will be used in the next upgrade, but I cannot see any >> improvement and there are many words untranslated. > > The Spanish translations for Mailman core and HyperKitty are currently > completely up to date with weblate. django-mailman3 differs in one > string that was translated on Feb 10 and hasn't yet been merged. > Postorius also differs in a few places from the Feb 10 version that > hasn't yet been merged. Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone. > Other than that, the translations should be good. > > >> Is there any way to upgrade the .po files in order to get the last >> translation? > > For the web UI you need to run the django management `compilemessages` > command. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error: su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. if I try with --settings param (for I missunderstood the error message) it shows the same: su -m mailman3 -c "python3 manage.py compilemessages --settings settings" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified. I tried to find any doc regarding the use of the "compilemessages" command but I couldn't As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job. I'm lost. Can you, please, point me in the right direction? > For Mailman core you need to run > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > ``` > to compile the mailman.po file for gettext. >

5 years, 1 month

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/26/26 13:20, Ibiam Chihurumnaya via Mailman-users wrote: > > I'm doing it in mailman shell, list_name is a List object, and it seems to have a settings > > attribute as list_name.settings returns > > {'acceptable_aliases': [], ...} > > I would really like to know what Mailman version this is, and how it was > installed? In my case with Mailman core from the head of the GitLab branch: > $ mailman shell -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 > >>> m.settings > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: 'MailingList' object has no attribute 'settings' > >>> m.settings['accept_these_nonmembers'] > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: 'MailingList' object has no attribute 'settings' > >>> Currently running Mailman 3.3.10 and I followed the instructions from https://docs.mailman3.org/en/latest/install/virtualenv.html# to install. This is the output from mine, I get the same output as you do when I try exactly what you do; mailman shell -l systems-logs(a)lists.sugarlabs.org 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 systems-logs(a)lists.sugarlabs.org mailing list >>> m.settings Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'MailingList' object has no attribute 'settings' I get something else when I do it differently - how I've been doing it so far -. mailman shell 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. >>> from mailmanclient import Client >>> from mailmanclient import Client >>> client = Client('http://localhost:8001/3.1', '**', '**') >>> sg = client.domains[0] >>> sy = sg.get_lists()[-1] >>> sy <List 'systems-logs(a)lists.sugarlabs.org'> >>> sy.settings {'acceptable_aliases': [], 'accept_these_nonmembers': [], 'admin_immed_notify': True, 'admin_notify_mchanges': False, 'administrivia': True, 'advertised': False, 'allow_list_posts': True, 'anonymous_list': False, 'archive_policy': 'public', 'archive_rendering_mode': 'text', 'autorespond_owner': 'none', 'autorespond_postings': 'none', 'autorespond_requests': 'none', 'autoresponse_grace_period': '90d', 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounces_address': 'systems-logs-bounces(a)lists.sugarlabs.org', 'bounce_info_stale_after': '7d', 'bounce_notify_owner_on_bounce_increment': False, 'bounce_notify_owner_on_disable': True, 'bounce_notify_owner_on_removal': True, 'bounce_score_threshold': 5, 'bounce_you_are_disabled_warnings': 3, 'bounce_you_are_disabled_warnings_interval': '7d', 'collapse_alternatives': True, 'convert_html_to_plaintext': False, 'created_at': '2026-02-04T21:53:10.928951', 'default_member_action': 'defer', 'default_nonmember_action': 'accept', 'description': '', 'digest_last_sent_at': '2026-02-27T11:24:11.916379', 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': 'monthly', 'digests_enabled': True, 'display_name': 'Systems-logs', 'discard_these_nonmembers': [], 'dmarc_mitigate_action': 'no_mitigation', 'dmarc_mitigate_unconditionally': False, 'dmarc_addresses': [], 'dmarc_moderation_notice': '', 'dmarc_wrapped_message_text': '', 'emergency': False, 'filter_action': 'discard', 'filter_content': False, 'filter_extensions': [], 'filter_types': [], 'first_strip_reply_to': False, 'forward_unrecognized_bounces_to': 'administrators', 'fqdn_listname': 'systems-logs(a)lists.sugarlabs.org', 'gateway_to_mail': False, 'gateway_to_news': False, 'hold_these_nonmembers': [], 'include_rfc2369_headers': True, 'info': '', 'join_address': 'systems-logs-join(a)lists.sugarlabs.org', 'last_post_at': '2026-02-27T11:32:51.317220', 'leave_address': 'systems-logs-leave(a)lists.sugarlabs.org', 'linked_newsgroup': '', 'list_name': 'systems-logs', 'mail_host': 'lists.sugarlabs.org', 'max_message_size': 40, 'max_num_recipients': 10, 'max_days_to_hold': 0, 'member_roster_visibility': 'moderators', 'moderator_password': None, 'newsgroup_moderation': 'none', 'next_digest_number': 60, 'nntp_prefix_subject_too': True, 'no_reply_address': 'noreply(a)lists.sugarlabs.org', 'owner_address': 'systems-logs-owner(a)lists.sugarlabs.org', 'pass_types': [], 'pass_extensions': [], 'personalize': 'none', 'post_id': 316, 'posting_address': 'systems-logs(a)lists.sugarlabs.org', 'posting_pipeline': 'default-posting-pipeline', 'preferred_language': 'en', 'process_bounces': True, 'reject_these_nonmembers': [], 'reply_goes_to_list': 'no_munging', 'reply_to_address': '', 'request_address': 'systems-logs-request(a)lists.sugarlabs.org', 'require_explicit_destination': True, 'respond_to_post_requests': True, 'send_goodbye_message': True, 'send_welcome_message': True, 'subject_prefix': '[Systems-logs] ', 'subscription_policy': 'confirm', 'unsubscription_policy': 'confirm', 'usenet_watermark': None, 'volume': 1} > > Presumably in your case, you could do > list_name.settings['accept_these_nonmembers'].append('user(a)example.com') > > or > > list_name.settings['accept_these_nonmembers'].extend(['user1(a)example.com', > 'user2(a)example.com', 'user3(a)example.com']) > > but as I've said previously, accept_these_nonmembers is not the > preferred way to do this. Something like > $ mailman addmembers --delivery disabled FILE LIST > Yes, I see now that it's not the preferred way to do it. It's difficult to know that when looking at the documentation. > where FILE contains the addresses to add, one per line and LIST is the > list name would add the addresses as members with delivery disabled. To > add them as nonmembers with moderation_action Defer: > $ mailman shell -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 > >>> from mailman.app.membership import add_member > >>> addresses = ('user1(a)example.com', 'user2(a)example.com', > ... 'user3(a)example.com') > >>> for addr in addresses: > ... rr = RequestRecord(addr) > ... nm = add_member(m, rr, role=MemberRole.nonmember) > ... nm.moderation_action = Action.defer > ... > >>>commit() Thank you! > > Of course, all of this can be done, perhaps more easily, using the > Postorius web UI. Yes, but like I've mentioned in another thread, I don't have access to the web UI because I can't get a confirmation link. > -- > 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: not correct language in subject(s)

by Jens Günther

Thanks Mark for the tests and your thoughts on this matter. Am 23.05.23 um 17:19 schrieb Mark Sapiro: > > That file was for a test only. The German message catalog is at > mailman/messages/de/LC_MESSAGES/. That directory should contain a > mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be > created. The source distribution contains a generate_mo.sh script to > generate these for all languages, but you can do the German one by > changing to the mailman/messages/de/LC_MESSAGES/ directory in the > running installation and doing > > msgfmt mailman.po -o mailman.mo I just checked the mailman/messages/de/LC_MESSAGES directory and there was only a mailman.po. I tried to create the mo-file with the command you provided, unfortunately it doesn't work in the running docker-container (obviously the gettext-package is missing ... and can't install it with apt, but this is another docker-related problem, shall I open another thread?). I did create on OS-level the mo-file, restarted the container and now the welcome- and goodbye-subject is indeed in German, coolio! 2 thoughts on this for me is: - Shall I create all the mo-files (the other folders also only contain the po)? If so, how would it be possible? - How can I make it persistent? (probably it should be included in the repo!? also another thread or an issue regarding maxxking's repo!?) > > I just tested, and the notice to the moderator of a held message is in > the list's preferred language including the Subject: and the moderation > reason, and the notice to the user sending a held message is in the > User's preferred language for that list including the Subject: and the > moderation reason. > > I suspect your issue is you don't have the compiled mailman.mo German > message catalog. The text is in German because it comes from templates > and you presumably do have German language templates. > Exactly. What I was wondering: for the welcome-messages I did not have explicit templates for those lists/domains/site that I wrote in German, it has to be from the predefined templates, which are stored elsewhere the in the mo-files!? (actually I don't get this point exactly but wouldn't bother, if the above works). Thanks again!

2 years, 10 months

[MM3-users] Re: Removing a mail addresses and users

by Abhijith PA

Hi Mark, On 11/06/20 1:16 am, Mark Sapiro wrote: > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) In my case these user signups were just to test postorious. These mail accounts didn't subscribed to anything. >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > Thanks for the link, let me try that out. --abhijith

5 years, 9 months

Search results for query "sapiro"