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

[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, 9 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, 4 months

[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, 5 months

[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

4 months, 4 weeks

[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!

3 years, 2 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

6 years, 1 month

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

by Ibiam Chihurumnaya

Stephen J. Turnbull wrote: > Ibiam Chihurumnaya via Mailman-users writes: > > Mark Sapiro wrote: > > > OK, this is Django. The default EMAIL_BACKEND from > > mailman_web/settings/base.py is > > django.core.mail.backends.smtp.EmailBackend and unless you've changed > > that or added overrides various other defaults are > > EMAIL_HOST = "localhost" > > EMAIL_PORT = 25 > > EMAIL_HOST_USER = "" > > EMAIL_HOST_PASSWORD = "" > > EMAIL_USE_TLS = False > > EMAIL_USE_SSL = False > > EMAIL_SSL_CERTFILE = None > > EMAIL_SSL_KEYFILE = None > > Are those appropriate? Do you have an outgoing MTA listening on > > localhost:25? What's in it's logs? > > I don't have any of those set, didn't realize I needed to have them > > set, the docs didn't make it obvious too. > > Those defaults *are* set in the mailman_web settings files. You can > override them in /etc/mailman3/settings.py, but often you don't need > to. Makes sense, I didn't think I needed to. Couldn't see them with mailman conf though. > > I also didn't notice them in schema.cfg in mailman. > > This is for Django, whose configuration is in > /etc/mailman3/settings.py, with defaults set in the mailmanweb package > in your venv's site-package in the files in .../mailman_web/settings/. > > smtp_port is currently set to 25, and I do have an outgoing MTA > > listening on localhost:25. > > If Mailman can distribute posts that way, Django should be able to > send mail with the default settings. > > Nothing shows up in the MTA logs about this particular email. > > Not sure what to say about that. I'm not sure Postorius or Django log > outgoing mail messages but I think they use the mailmanweb.log file by > default if they log mail at all. (This is separate from the MTA logs > which should record any connections from localhost and mail submitted.) Is there any way I could get more logs, I had set Debug = True in settings.py a while back, but can't see anything more. > -- > GNU Mailman consultant (installation, migration, customization) > Sirius Open Source https://www.siriusopensource.com/ > Software systems consulting in Europe, North America, and Japan

5 months, 1 week

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Thu, 30 Jul 2020 at 00:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > > > Yes, the same problem. > > I created the file __init__.py in /opt/mailman/mm > > However, when I run using the wsgi.py I ended up (still do!) with the > error: > > > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > > application='mm3-lists.server.name|/mm3'): Loading Python script file > > '/opt/mailman/mm/wsgi.py'. > > What is the contend of the file /opt/mailman/mm/wsgi.py? > [wash@gw ~]$ cd /opt/mailman/mm/ [wash@gw /opt/mailman/mm]$ less wsgi.py """ WSGI config for HyperKitty project. It exposes the WSGI callable as a module-level variable named ``application``. For more information on this file, see https://docs.djangoproject.com/en/{{ docs_version }}/howto/deployment/wsgi/ """ import os # import sys # import site # For some unknown reason, sometimes mod_wsgi fails to set the python paths to # the virtualenv, with the 'python-path' option. You can do it here too. # # # Remember original sys.path. #prev_sys_path = list(sys.path) # # Add here, for the settings module #site.addsitedir(os.path.abspath(os.path.dirname(__file__))) # # Add the virtualenv #venv = os.path.join(os.path.abspath(os.path.dirname(__file__)), # '..', 'lib', 'python2.6', 'site-packages') # site.addsitedir(venv) # # Reorder sys.path so new directories at the front. # new_sys_path = [] # for item in list(sys.path): # if item not in prev_sys_path: # new_sys_path.append(item) # sys.path.remove(item) # sys.path[:0] = new_sys_path from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") application = get_wsgi_application() > You previously posted the setting of WSGIDaemonProcess in your Apache > config as: > > > WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 user=mailman3 \ > > group=mailman3 > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > \ > > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > Is it still that? > This is from wsgi.conf in my Apache Includes/. It's a copy/paste of your version, with the only modification being the change pf python version to 3.7 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 11 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 25, 2017 9:13:20 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: >> >> No to the domains part and I think virtual alias maps is needed: >> >> mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx >in BOTH virtual_mailbox_domains and relay_domains >> Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not >list domain xxx in BOTH virtual_mailbox_domains and relay_domains >> Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: >reject: RCPT from >pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 ><test123@xxx>: Recipient address rejected: User unknown in virtual >mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP >helo=<[10.0.0.29]> > >(above slightly sanitized for return to the list) > >The issue here is your list domain cannot be a virtual_mailbox_domain >or >a virtual_alias_domain. > >I have the same issue on mail.python.org where we have both Mailman 2 >and Mailman 3 lists @python.org. and python.org is a >virtual_alias_domain. > >I have a group of MRs for a branch that implements "alias_domains" to >deal with this. > >Basically it works by creating another (virtual_alias_maps) >postfix_vmap >mapping to map list addresses @python.org to addresses @x.python.org. >Then the postfix_domains and postfix_lmtp maps have the x.python.org >domain and there is a patch to mailman/runners/lmtp.py to map the >x.python.org domain back to python.org. > >The various MRs are ><https://gitlab.com/mailman/mailman/merge_requests/202> for the core, ><https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the >REST bindings used by Postorius and ><https://gitlab.com/mailman/postorius/merge_requests/186> to be able to >set an alias_domain via Postorius. > >That's not all implemented at mail.python.org. What's there is the >basic >Postfix config, a bash script the generate the new mappings from the >old >and a simple patch to mailman/runners/lmtp.py. > >So, the bottom line is it can be done and it's in process, but it won't >really be supported until Mailman 3.2. In the mean time, you just need >to have a separate domain for your lists that isn't a virtual_*_domain. Ok thanks. At least I have a clear answer now. Any ETA on 3.2 in mind yet? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 9 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Much appreciated, Mark. We'll go with (a.), as it's a one-liner as I expected, and it does not require me to change the policy. I'll just need to make some adjustments to the template contents. Yours, Allan On 3/28/23, 11:29, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/NNMWW4PW55H4OLA3NTAKZLRNIEV2HHUA/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

3 years, 3 months

Search results for query "sapiro"