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

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

Hi, Marik! I realized that I had two variables in settings.py where the domains is listed, and one of them had a preceding https. I've now followed the documentation for configuring Apache here: https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. I want both domains to start mailman3 when contacting example1.com/mailman3 and example2.com/mailman3. I have the sam configuration in both virtualhost section in Apache. For example1.com/mailman3, it works perfectly. For example2.com/mailman3 however, the browser (elinks), reports Host not found: example2.commailman3 e.g. without a slash after the domain name. What could cause this to happen? Thanks Lars On Fri, Feb 10, 2023 at 11:59:02AM -0800, Mark Sapiro wrote: > On 2/10/23 01:43, Lars Bjørndal wrote: > > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > > > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > > > > > If I connect to example2.com, the title is example2.com, without the > > > > preceding List index. And the body says Page not found. > > > > > > > > > What's in the browser's address bar for that page? > > > > It's https://example2.com/mailman3/lists/ > > And when you get the Page not found, is it a browser 404 error or a > Postorius error page? > > > > > > > What's in Postorius domains view? > > > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > > > Why are you going to http://localhost:8000/? You should be able to see the > domain's view at https://example1.com/mailman3/domains/ or > https://example1.com/mailman3/domains/ or by just clicking Domains in > Postorius top nav bar. > > > > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. > > > Again you should be able to go to https://example1.com/admin or > https://example2.com/admin. If these don't work, you need to add directives > in your web server to proxy them to http://localhost:8000/admin > > -- > 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 > 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… > > This message sent to lars(a)lamasti.net

2 years, 4 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Mark Sapiro

On 06/17/2016 12:16 PM, Bill wrote: > Hi, > > I'm looking for some information on Mailman3 administration. I've found > that it's not yet packaged by any of the common Linux distros - Debian, > Ubuntu, Mint, RedHat, Centos, Fedora, Suse, Arch etc so I have some > concerns about the amount of upkeep that running Mailman3 will entail. > > I know that Mailman2 is available as a package on the above distros, but > we would really like to take advantage of the kludge-free, virtual > domains feature on Mailman3. > > I've been asked by a local non-profit provider to assist them in moving > their 200+ mailing lists from an outdated Sympa list server to > Debian8/Postfix/Mailman. One of their chief concerns is the amount of > extra administration, over and above normal list administration, that > Mailman3 will require in the form of manual updates and maintenance. > > We are in the evaluation and design stage right now, but could use any > pertinent advice about supportive distros, available packages, the > amount of extra administration involved or perhaps, in a worst case > scenario, alternate list managers supporting a virtual domains feature > similar to Mailman3. > > Thanks for your help, > > Bill McGrath > President, Vancouver Linux Users Group > https://vanlug.bc.ca I've copied this post and set Reply-To: to the Mailman 3 users list <mailman-users(a)mailman3.org>. Please join at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/> before replying there. That said, we are working on packaging for a more turn-key installation, but we aren't there yet. I've installed a couple of instances including the one at lists.mailman3.org, and it does require extra work. Some of the work in my case is because I want to run all the Mailman pieces from the heads of their branches rather than what's in PyPI, but even without that, installation is significantly more work than installing a distro's package. I will be writing up my experiences, but that's not done yet either. I will say that once you have Mailman 3 installed and running, updating (which I do frequently, but which doesn't need to be done unless you want specific updates/fixes) is pretty easy. As far as alternatives are concerned There is an up to date Mailman 2.1 branch with better virtual domain support at <https://code.launchpad.net/~msapiro/mailman/vhost>, but I think in the long run, you'd be better off with Mailman 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Mailman 3 on Fedora - Core only ?

by Mark Sapiro

On 6/13/20 2:17 AM, Lars Bjørndal wrote: > I'm about to set up a new list, and want to try out Mailman3. > > The only component available in Fedora, is the Mailman core package. I find that strange as <https://lists.fedoraproject.org/> is Mailman 3 and the core developer who did most of the HyperKitty development works or did work for Fedora. > With the /usr/libexec/mailman3/mailman command, I was able to create a > list, and add a member throug the sub commands create and members. > > How can I read out the list configuration from here, and change > settings? Do I then need to install/use other components, or is there > other possibilities, e.g. using the shell command? You can do anything through `mailman shell`, but it can be cumbersome. You can also do most things via the REST API <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>, but that too is cumbersome if doing it, e.g., with `curl`. > If I get a message that needs moderation, can I do the decision from cli, > or how do I do that? You should be able to do it via a reply to LIST-confirm+<token>@example.com, but this currently doesn't work. See <https://gitlab.com/mailman/mailman/-/issues/169>. To do it in `mailman shell` is something like: $ bin/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.moderator import handle_message >>> from mailman.interfaces.action import Action >>> action = Action.discard # to discard >>> action = Action.reject # to reject >>> action = Action.accept # to accept immediately >>> action = Action.defer # to continue with subsequent tests >>> rq = IListRequests(m) >>> rq.held_requests <generator object ListRequests.held_requests at 0x7f5431dda048> >>> list(rq.held_requests) [] >>> # when you have requests this is a list of (id, type) tuples >>> # type is 1 for message, 2 for subscription and 3 for unsubscription >>> id = 'integer request id from above' >>> handle_message(m, id, action, comment='reason if rejecting') This is obviously not practical, but you could make a script to accept the token that you know and an action and maybe a comment to do the actual handling. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/23/21 12:43 AM, Marco Marinello wrote: > Dear Mark, > > I upgraded the pypi packages as you suggested but the problem remains the same. > Tried also installing from git heads but always get > > ==> /opt/hyperkitty_django/hyperkitty.log <== > ERROR 2021-10-23 09:42:42,523 30765 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls > WARNING 2021-10-23 09:42:42,523 30765 django.request Unauthorized: /hyperkitty/api/mailman/urls > > ==> /var/log/mailman/mailman.log <== > Oct 23 07:42:42 2021 (30888) HyperKitty failure on http://127.0.0.1:8080/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key must be > sent over the Authorization HTTP header. > </p></body></html> (401) Those messages look correct for HyperKitty 1.3.5, if mailman-hyperkitty is not sending the key as expected. The particular condition causing those messages is there is no "Authorization" header in the headers of the request from mailman-hyperkitty and there is also no "key" parameter in the request as there would have been with mailman-hyperkitty 1.1.0 This would seem to say that both HyperKitty 1.3.5 and mailman-hyperkitty 1.2.0 are doing the right thing, but somehow the request headers are not getting through in the http request from mailman-hyperkitty to HyperKitty. What is your setting for base_url in mailman-hyperkitty.cfg? Is there some redirect or other situation going on in serving the request to HyperKitty that could cause headers to get lost? > For information, how does your release cycle work? I prefer installing from a source rather than pypi. Is the master normally stable? When a packages lands on pypi? We are a small, all volunteer project and we don't have a fixed release schedule. We make releases when we feel enough change has been accumulated to warrant on or when there is a serious issue to fix. The heads of the gitlab branches are generally usable. There was actually a situation briefly where the mailman-hyperkitty changes for this issue were merged before the HyperKitty changes. See https://gitlab.com/mailman/hyperkitty/-/merge_requests/354#note_693162778 but situations like this are rare. The servers at lists.mailman3.org and mail.python.org run the heads of the gitlab branches (I update them regularly) so you can generally be confident that they work. > I'll stick on 1.3.4 / 1.1.0 for the moment. There are several changes in HyperKitty 1.3.5. See https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 5:41 PM, Ruth Ivimey-Cook wrote: > >>> My reason for thinking, in my original post, that the wrong host >>> address is being used is that the ConnectionError above contains >>> 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only >>> present as >>> the listen address on the core web service and does not appear in >>> the >>> config for postorius. >> The ConnectionError above comes from requests.request (docs at >> <https://requests.readthedocs.io/en/master/>). Client only provides a >> URL in the call to request and the URL is the baseurl + the path and the >> baseurl is MAILMAN_REST_API_URL which you have as >> http://greyarea-post:8870. Entries above have >> http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? >> >> I suspect a DNS lookup issue. How does greyarea-web1 resolve >> greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS >> rather than relying on /etc/resolv.conf and/or /etc/hosts. > > No, ignore that... I edited the FQDN down to the hostname in the email > for simplicity, but even if it was in the log the hostname does map > properly (i.e. host greyarea-post and host greyarea.cam.ivimey.org > return the same thing). Is the above a typo. You are saying greyarea.cam.ivimey.org. Did you mean that or greyarea-post.cam.ivimey.org as in the http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 log messages? > In referring to the ConnectionError from: > > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > > if you reconstruct the url passed in it was presumably: > > "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk" I don't think so. I think it was http://greyarea-post:8870/3.1/domains/ch-bc.org.uk and requests.request couldn't resolve that to the correct IP. If you look at Mailman client <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/re…> you'll see it makes the URL from the baseurl passed to the instantiation of the Connection class which occurs at <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/cl…> which in turn is called from Postorius at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…> which makes the baseurl argument from '%s/3.1' % settings.MAILMAN_REST_API_URL. -- 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: PermissionError: [Errno 1] Operation not permitted

by Mark Sapiro

On 6/21/21 2:28 PM, Sarah H wrote: > The system we are running mailman 3 on crashed, it filled the drive, and when it was restarted and the issue cleared I found that mailman3 will not start, it returns the following: > > Jun 21 14:12:29 mailman[513274]: Traceback (most recent call last): > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/bin/mailman", line 11, in <module> > Jun 21 14:12:29 mailman[513274]: load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 829, in __call__ > Jun 21 14:12:29 mailman[513274]: return self.main(*args, **kwargs) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 782, in main > Jun 21 14:12:29 mailman[513274]: rv = self.invoke(ctx) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke > Jun 21 14:12:29 mailman[513274]: return super().invoke(ctx) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke > Jun 21 14:12:29 mailman[513274]: return _process_result(sub_ctx.command.invoke(sub_ctx)) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1066, in invoke > Jun 21 14:12:29 mailman[513274]: return ctx.invoke(self.callback, **ctx.params) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 610, in invoke > Jun 21 14:12:29 mailman[513274]: return callback(*args, **kwargs) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/decorators.py", line 21, in new_func > Jun 21 14:12:29 mailman[513274]: return f(get_current_context(), *args, **kwargs) > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/cli_control.py", line 91, in start > Jun 21 14:12:29 mailman[513274]: status, lock = master_state() > Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/master.py", line 104, in master_state > Jun 21 14:12:29 mailman[513274]: os.kill(pid, 0) > Jun 21 14:12:29 mailman[513274]: PermissionError: [Errno 1] Operation not permitted > Jun 21 14:12:29 systemd[1]: mailman3.service: Control process exited, code=exited status=1 > Jun 21 14:12:29 systemd[1]: mailman3.service: Failed with result 'exit-code'. > > this is via starting as root with systemctl start mailman3, or as the user mailman using /opt/mailman/venv/bin/mailman start This is probably due to a stale lock. See https://gitlab.com/mailman/mailman/-/issues/913. Assuming mailman is not running, you need to remove Mailman's var/locks/* Similar issues can occur if `bin/mailman start` is run as the mailman user but has previously been run as root. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/3/22 4:01 PM, Michael Heseltine wrote: > Hi Mark, > I tried out "pip install mistune==2.0.0rc1" (as I got hyperkitty via pip) which worked and let me move forward a little further once more, but still I get an error from "mailman-post-update": > >> # /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 >> Compressing... done >> Compressed 2 block(s) from 104 template(s) for 1 context(s). >> + /opt/mailman/mm/bin/django-admin compilemessages >> Traceback (most recent call last): >> File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> >> sys.exit(execute_from_command_line()) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line >> utility.execute() >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 413, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 354, in run_from_argv >> self.execute(*args, **cmd_options) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 398, in execute >> output = self.handle(*args, **options) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/commands/compilemessages.py", line 113, in handle >> self.compile_messages(locations) >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/commands/compilemessages.py", line 130, in compile_messages >> self.stdout.write( >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 155, in write >> self._out.write(style_func(msg)) >> UnicodeEncodeError: 'latin-1' codec can't encode character '\u201c' in position 5: ordinal not in range(256) This looks like an issue with some message catalog which is declared as character set `latin-1` but contains a unicode left_double_quote character. Unfortunately, `django-admin compilemessages` compiles, at least in my test installation, 1583 message catalogs from 19 different projects, so finding the problem file is difficult and I don't know how to narrow it down. However, this is the next to last step in mailman-post-update and isn't important if your installation is English language only and the last step is optional and runs /opt/mailman/mm/bin/django-admin update_index to rebuild the search index for HyperKitty and you can just run that one step if you want. At this point, you probably have no archives so this should take almost no time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Mailman3 on python3.13 debian testing package

by Mark Sapiro

On 2/12/25 23:12, Thomas Krichel wrote: > > Feb 13 06:49:56 2025 (857955) Uncaught runner exception: 'pathlib._local.PosixPath' object does > not support the context manager protocol > Feb 13 06:49:56 2025 (857955) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 179, in _one_iteration > self._process_one_file(msg, msgdata) > ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 272, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 111, in _dispose > self._func(mlist, msg, msgdata) > ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 89, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/lib/python3/dist-packages/mailman/mta/base.py", line 167, in deliver > callback(mlist, message_copy, msgdata_copy) > ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate > decorator.process(mlist, msg, msgdata) > ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 250, in process > process(mlist, msg, msgdata) > ~~~~~~~^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 88, in process > header = decorate('list:member:regular:header', mlist, d) > File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 212, in decorate > template = getUtility(ITemplateLoader).get(name, mlist, **extradict) > File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 211, in get > path, fp = find(default_uri, mlist, code) > ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/utilities/i18n.py", line 157, in find > for search_path in raw_search_order: > ^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/mailman/utilities/i18n.py", line 117, in search > templates_dir = str(resources.enter_context( > ~~~~~~~~~~~~~~~~~~~~~~~^ > files('mailman').joinpath('templates'))) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.13/contextlib.py", line 528, in enter_context > raise TypeError(f"'{cls.__module__}.{cls.__qualname__}' object does " > f"not support the context manager protocol") from None > TypeError: 'pathlib._local.PosixPath' object does not support the context manager protocol > Feb 13 06:49:56 2025 (857955) SHUNTING: 1739429396.7636604+dba2fc372ce4c206e3bb753c1162bc3b768b7528 > Feb 13 06:49:56 2025 (857955) SHUNTING: 1739429396.7636604+dba2fc372ce4c206e3bb753c1162bc3b768b7528 > > Then there are repeated messages that hyperkitty can't archive the > message. Lots of them. > > No email reaches the list. I did not notice, but now the listowner > has written to me. Because the messages are being shunted because of the above exception which is a Python 3.13 issue https://gitlab.com/mailman/mailman/-/issues/1190 fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1309. Once you fix that issue by either downgrading Python or installing the changes from https://gitlab.com/mailman/mailman/-/merge_requests/1309 you can reprocess those messages with `mailman unshunt` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: messages go to shunt queue

by Danil Smirnov

Thanks Mark! The change provided has fixed the issue. Danil On Thu, Sep 10, 2020 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/10/20 6:43 AM, Danil Smirnov wrote: > > Hi guys, > > > > I've faced weird Core behaviour after the last upgrade of the docker > > images. All the messages sent to a list now go straight to shunt queue > with > > the following error in the logs: > > > > --- > > Sep 06 22:41:32 2020 (27) Traceback (most recent call last): > ... > > File "/usr/lib/python3.8/site-packages/mailman/rules/dmarc.py", line > 217, > > in is_reject_or_quarantine > > for record in txt_rec.items[0].strings) > > KeyError: 0 > > Sep 06 22:41:32 2020 (27) SHUNTING: > > 1599432092.4326646+4cbb58a0dd5d9705946ca583835e63ec175536e3 > > > See <https://gitlab.com/mailman/mailman/-/issues/743>. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 9 months

[MM3-users] Re: User display name entry field input ignored

by Christian

Okay. What if I want to change the name from "None" to "firstname lastname" ? How can that be accomplished please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Sunday, June 26, 2022 5:22 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: User display name entry field input ignored On 6/26/22 08:03, Christian via Mailman-users wrote: > Whether I try and add users using mass subscribe, or individually, it > seems the display name field entry is ignored. The default is then > "none" for the user. Please advise. Thank you! If the address you are mass subscribing is already known to mailman, i.e., is an existing user, it is that user that will be subscribed with that user's display name, even if it is None. If that address is not an existing user, the user will be subscribed with the display name you provide. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 10 months

Search results for query "sapiro"