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

[MM3-users] Re: Caching problem with templates

by Mark

On Thu, 2025-06-26 at 18:36 -0700, Mark Sapiro wrote: > > You can delete the cached entry from the database via `mailman shell > as in > >>> cm = getUtility(ICacheManager) > >>> uri = 'the_uri_from_the_template_table' > >>> cm.get(uri, expunge=True) > >>> commit() > ``` > > You can also delete the entry from the file_cache table, but if you > do > that, the actual file containing the cached data will remain. To > remove > it, > > Rather than doing any of the above, if you want to manipulate the > database, just set the expires_on column in the file_cache table > entry > to a date in the past. > Hi Mark, Thank you for this information. I've given the options a good workout over the last couple of days and found that: 1. Deleting the cache via the mailman shell does the job, but is beyond me to script. There are numerous lists and list owners updating their templates. 2. Changing the expires_on date (to a date in the past) in the file_cache table didn't prevent the cached entry from being used; 3. What did work was removing the records in the file_cache table PLUS removing the corresponding files in var/cache/*/*/* -- for example: /opt/mailman/mm/var/cache/3a/2f/* This I was able to script in bash and cron to run every minute. A hack I know, but it's working for now. I've attached the script in case it's of use to anyone else. (mailman_clear_template_cache.txt) Note: change <USER> in the script to what suits. Does Mailman really need to cache the templates? It seems to be an unnecessary complication. Anyways it happy days again. Thank you again, very much. Your guidance was appreciated immensely as always. Best, Mark

1 year

[MM3-users] Re: Change Member's Address

by alain williams

On Tue, Jan 13, 2026 at 11:14:04AM -0800, Mark Sapiro wrote: > >>> um = getUtility(IUserManager) > >>> addr = um.get_address('address_to_change') > >>> addr.email = 'new_address' > >>> commit() > ``` > However, the preferred way is for the user to log in, go to > https://whatever/accounts/email/, add the new address to their account, make > it primary, go to the list info page at https://whatever/lists/LIST, and if > their Subscription Address is still the old address (because they weren't > subscribed by primary address), click Manage Subscription and change it, and > then possibly remove the prior address. That should be trivial for any user to do that - certainly I, and others on this list, would not have a problem. However: many of my users would find those instructions baffling, they can just about manage email - on a good day. Like it or not it is sometimes easier for me to do that sort of thing than try to explain it to them. In the past I have done it by running up MySQL and hacking the table directly. I host several mail lists, some of which I do not manage - my 'clients' do that and, with a bit of hand holding have learned to add/remove/... people to lists via the web interface. They do not know what the mailman shell is - and I would not want to give them shell access to the machine. So: it would be really useful if the list manager were able to do this via the web interface. Please! -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

6 months, 1 week

[MM3-users] Re: Moving/cloning mailman3

by Abhilash Raj

Just take a dump of the database and move to other one, almost everything is stored in database. Outside of database, if you need to move log files and currently pending emails in shunt or held queue (broken or pending emails), you need to move the 'var' directory of Core and it's configuration. If you are using docker installation, database container holds the database and '/opt/mailman/core/var' is what you are looking for. Thanks, Abhilash Raj (Apologies for top post) On October 18, 2017 1:29:58 PM PDT, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/18/2017 11:10 AM, Mark Sapiro wrote: >> On 10/18/2017 08:56 AM, Dmitry Makovey wrote: >>> Hi, >>> >>> I am drawing a blank looking for documentation for mailman3 >migrations. >>> How can one dump existing settings for mailman and import it into >>> another instance? >> >> >> The Mailman 3 command 'mailman import21' is what does this >> ><http://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.ht…>, >> however there are issues in that not all 2.1 settings are imported at >> all or correctly and in at least one case on an announce only list, >the >> membership wasn't imported. >> >> I intend to work on this, but haven't got as far as even documenting >the >> problems, much less coming up with fixes. > > >isn't above more about MM2 -> MM3 moves? I can't file .pck files for >MM3 >setup thus assuming there are some other files/commands I need to >tackle >to move MM3 from host to host. > > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 9 months

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Thomas Krichel

Mark Sapiro writes > For older releases you can add > ``` > [runner.nntp] > start: no > ``` > to mailman.cfg Following this advice, I reverted the change I made to /usr/lib/python3/dist-packages/mailman/utilities/modules.py Then I believe I implemented Mark's suggestion root@server~# diff /etc/mailman3/mailman.cfg~ /etc/mailman3/mailman.cfg 312c312,318 < jump_chain: hold \ No newline at end of file --- > jump_chain: hold > > ## dont't start nntp because library is missing > > [runner.nntp] > start: no > ok, but root@server~# systemctl status mailman3.service × mailman3.service - Mailman3 server Loaded: loaded (/usr/lib/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-02-05 23:36:35 UTC; 9min ago Duration: 2month 3w 6d 6h 21min 31.400s Invocation: 746a7d496ddd47f6a63795e55348b6f9 Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 416285 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) Mem peak: 74.2M CPU: 1.712s Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 935, in _load_unlocked Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap_external>", line 1026, in exec_module Feb 05 23:36:34 server mailman3[416285]: File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed Feb 05 23:36:34 server mailman3[416285]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_gatenews.py", line 24, in <module> Feb 05 23:36:34 server mailman3[416285]: import nntplib Feb 05 23:36:34 server mailman3[416285]: ModuleNotFoundError: No module named 'nntplib' Feb 05 23:36:35 server systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Feb 05 23:36:35 server systemd[1]: mailman3.service: Failed with result 'exit-code'. Feb 05 23:36:35 server systemd[1]: Failed to start mailman3.service - Mailman3 server. Feb 05 23:36:35 server systemd[1]: mailman3.service: Consumed 1.712s CPU time, 74.2M memory peak. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 21797th day.

1 year, 5 months

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

by Onyeibo Oku

On Sat Oct 22, 2022 at 9:56 PM WAT, Mark Sapiro wrote: > On 10/22/22 13:07, Onyeibo Oku wrote: > > On Sat Oct 22, 2022 at 7:44 PM WAT, Mark Sapiro wrote: > >> The specific error you reported refers tp > >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > >> > >> what does > >> ``` > >> ls -l > >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > >> ``` > >> show? > >> > > > > See below: > > > > command: > > ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > > > > output: > > -rw-r--r--. 1 mailman mailman 7.8K Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > > > This is actually strange. What does `pip --version` in your venv show? > Did you do anything to install mailman and other packages in your venv > other than `pip install`. > > I ask because I don't think there should be *egg-info directories in > /opt/mailman/venv/lib/python3.10/site-packages/ at all. In particular, > in addition to the actual code directories, I only see files and > directories with names ending in nspkg.pth and dist-info. > It is strange indeed. So I decided to start all over again. I deleted both "mm" and "venv" folders and recreated "venv" first. I noted that after reinstalling the virtual environment pip was at version 21.3.1. I assumed that version may be buggy and upgraded to pip 22.3 before performing subsequent installations. Next came the wheel package, followed by psycopg2. I checked the /opt/mailman/venv/lib64/python3.10/site-packages/ path to confirm that things were clean. All good -- no egg-info/* folders. I then installed mailman. Now Mailman starts, and stops as desired when running as mailman user (both in virtual and non-virtual environments). However, running the service via systemd still fails. I now get a different traceback: Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most recent call last): Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/bin/mailman", line 8, in <module> Oct 23 03:43:00 mail.server.tld mailman[19410]: sys.exit(main()) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1130, in __call__ Oct 23 03:43:00 mail.server.tld mailman[19410]: return self.main(*args, **kwargs) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1054, in main Oct 23 03:43:00 mail.server.tld mailman[19410]: with self.make_context(prog_name, args, **extra) as ctx: Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 920, in make_context Oct 23 03:43:00 mail.server.tld mailman[19410]: self.parse_args(ctx, args) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1613, in parse_args Oct 23 03:43:00 mail.server.tld mailman[19410]: rest = super().parse_args(ctx, args) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 1378, in parse_args Oct 23 03:43:00 mail.server.tld mailman[19410]: value, args = param.handle_parse_result(ctx, opts, args) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 2360, in handle_parse_result Oct 23 03:43:00 mail.server.tld mailman[19410]: value = self.process_value(ctx, value) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/click/core.py", line 2322, in process_value Oct 23 03:43:00 mail.server.tld mailman[19410]: value = self.callback(ctx, self, value) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/bin/mailman.py", line 95, in initialize_config Oct 23 03:43:00 mail.server.tld mailman[19410]: initialize(value) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 217, in initialize Oct 23 03:43:00 mail.server.tld mailman[19410]: initialize_1(config_path) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/core/initialize.py", line 122, in initialize_1 Oct 23 03:43:00 mail.server.tld mailman[19410]: mailman.config.config.load(config_path) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 142, in load Oct 23 03:43:00 mail.server.tld mailman[19410]: self.push(filename, user_config.read()) Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 148, in push Oct 23 03:43:00 mail.server.tld mailman[19410]: self._post_process() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 160, in _post_process Oct 23 03:43:00 mail.server.tld mailman[19410]: self.ensure_directories_exist() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/mailman/config/config.py", line 262, in ensure_directories_exist Oct 23 03:43:00 mail.server.tld mailman[19410]: with Lock(lock_file): Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/flufl/lock/_lockfile.py", line 461, in __enter__ Oct 23 03:43:00 mail.server.tld mailman[19410]: self.lock() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/flufl/lock/_lockfile.py", line 328, in lock Oct 23 03:43:00 mail.server.tld mailman[19410]: self._write() Oct 23 03:43:00 mail.server.tld mailman[19410]: File "/opt/mailman/venv/lib64/python3.10/site-packages/flufl/lock/_lockfile.py", line 492, in _write Oct 23 03:43:00 mail.server.tld mailman[19410]: with open(self._claimfile, 'w') as fp: Oct 23 03:43:00 mail.server.tld mailman[19410]: PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958240354' Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE

3 years, 9 months

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 30 Jun 2020, at 8:22, Florian Schulze wrote: > On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > >> On 6/29/20 1:38 AM, Florian Schulze wrote: >>> Hi! >>> >>> After upgrading to HyperKitty 1.3.x I get the following error for >>> qcluster: >>> >>> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >>> 300, >>> in pusher >>> task = SignedPackage.loads(task[1]) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 31, >>> in loads >>> serializer=PickleSerializer) >>> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >>> line >>> 38, in loads >>> return serializer().loads(data) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 44, >>> in loads >>> return pickle.loads(data) >>> AttributeError: Can't get attribute 'process_task_result' on <module >>> 'hyperkitty.tasks' from >>> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >>> >>> How do I recover from that? It seems like there are still persisted >>> tasks in the qcluster queue using the old code from 1.2.x with the >>> old >>> locking implementation. >> >> Have you stopped ans started qcluster since upgrading? > > Yes > >> Are you running the Django periodic jobs? > > They were disabled because of the errors (someone else did the > upgrade). I have enabled them again and will watch it and report back. The cronjobs seem to work fine, no errors so far. The queue doesn't seem to change at all. In "qmonitor" there is nothing listed and the statusline remains the same at ORM default Queued 303(118) Success 100 Failures 0 Regards, Florian Schulze

6 years

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

by Onyeibo Oku

On Wed, 19 Oct 2022 23:38:05 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Judging from the traceback, Onyeibo Oku's > /opt/mailman/venv/bin/mailman is quite different from mine which is > just ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: > 'mailman==3.3.5','console_scripts','mailman' __requires__ = > 'mailman==3.3.5' import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', > 'mailman')() ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv? > True mine is different: **************** /opt/mailman/venv/bin/mailman ************ #!/opt/mailman/venv/bin/python # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' import re import sys # for compatibility with easy_install; see #2198 __requires__ = 'mailman==3.3.5' try: from importlib.metadata import distribution except ImportError: try: from importlib_metadata import distribution except ImportError: from pkg_resources import load_entry_point def importlib_load_entry_point(spec, group, name): dist_name, _, _ = spec.partition('==') matches = ( entry_point for entry_point in distribution(dist_name).entry_points if entry_point.group == group and entry_point.name == name ) return next(matches).load() globals().setdefault('load_entry_point', importlib_load_entry_point) if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit(load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')()) *************** end of /opt/mailman/venv/bin/mailman *********** I have tried setting environment path (PYTHONPATH) by specifying either "Environment" or "EnvironmentFile" in /etc/systemd/system/mailmain3.service. None works. I had: EnvironmentFile=/opt/mailman/.systemd_vars where the contents of .systemd_vars are: PYTHONPATH=/usr/lib64/python310.zip:/usr/lib64/python3.10:/usr/lib64/python3.10/lib-dynload:/usr/lib64/python3.10/site-packages:/usr/lib/python3.10/site-packages:/opt/mailman/venv/lib64/python3.10/site-packages:/opt/mailman/venv/lib/python3.10/site-packages At this point, I am frustrated. Is there something else I can do to get mailman3 on this server? from a frustrated Onyeibo

3 years, 9 months

[MM3-users] Re: Nested lists possible

by Stephen J. Turnbull

Mark Sapiro writes: > Mailman 2.1 had a regular_include_lists feature that would allow > specifying another list whose members would receive posts to this > list. I think that is what you are looking for. Unfortunately, that > feature has not yet been implemented in Mailman 3. Implementing regular_include_lists is the "right" way to do this, but it may take a while. If your "inner" users are somewhat sophisticated, you could have *two* inner-lists, one with address "inner-list-members(a)your.domain" which the inner-list members sign up for but is not advertised, and has no decorations such as subject tag and footer. The other would be named "inner-list(a)your.domain", would have "inner-list-members" as its only subscriber, and it would be the advertised posting address and provide the decorations. Complete the hack by subscribing "inner-list-members" to "outer-list". You can make "inner-list" a "by-list-owner-only" subscription policy, and have a description directing users to sign up "inner-list-members" instead. Not optimal, but it's a one-time annoyance for each subscriber and the list traffic looks the way I think you want it (decorations for posts to the outer list are outer-list for everybody including inner-list members, decorations for posts to the inner list are inner-list). You could also do this with all posts going to inner-list getting inner-list decorations, by requiring that outer-list subscribers subscribe to outer-list-members, which provides the outer-list decorations (I think this can be done but it will be confusing to list admins). Then "outer-list" would have no decorations and the sublists as the only subscribers. "inner-list" would have its own decorations. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 2 days

[MM3-users] Re: List description as sender

by Henrik Rasmussen

Mark Sapiro wrote: > On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: > I think your choices are: > > 1) Don't configure the list as anonymous. I've just tested it on a list which was imported from Mailman 2, but changing the list to announced doens't seem to affect the From: Thread-Topic: Test 201809241228 Date: Mon, 24 Sep 2018 10:28:32 +0000 Accept-Language: da-DK, en-US Content-Language: da-DK X-MailFrom: me(a)ku.dk X-Mailman-Rule-Hits: member-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address From: Testliste for Mailman-administratoren <project(a)lists.example.com> The list config is : { 'acceptable_aliases': [], 'admin_immed_notify': False, 'admin_notify_mchanges': False, 'administrivia': True, 'advertised': True, 'allow_list_posts': True, 'anonymous_list': True, 'archive_policy': 'never', 'autorespond_owner': 'none', 'autorespond_postings': 'none', 'autorespond_requests': 'none', 'autoresponse_grace_period': '90d', 'autoresponse_owner_text': '', 'autoresponse_postings_text': '', 'autoresponse_request_text': '', 'bounces_address': 'project-bounces(a)lists.example.com', 'collapse_alternatives': False, 'convert_html_to_plaintext': False, 'created_at': '2014-12-05T14:16:33.126729', 'default_member_action': 'hold', 'default_nonmember_action': 'reject', 'description': 'Testliste for the Mailman administrator', 'digest_last_sent_at': '2018-09-24T10:28:39.309653', 'digest_send_periodic': True, 'digest_size_threshold': 30.0, 'digest_volume_frequency': 'monthly', 'digests_enabled': True, 'display_name': 'project', 'dmarc_mitigate_action': 'no_mitigation', 'dmarc_mitigate_unconditionally': False, 'dmarc_moderation_notice': '', 'dmarc_wrapped_message_text': '', 'filter_content': False, 'first_strip_reply_to': True, 'fqdn_project': 'project(a)lists.example.com', 'http_etag': '"29465efe640811a7f2880b879c65c2f2651c3ac3"', 'include_rfc2369_headers': True, 'info': '', 'join_address': 'project-join(a)lists.example.com', 'last_post_at': '2018-05-25T08:10:54.222183', 'leave_address': 'project-leave(a)lists.example.com', 'list_name': 'project', 'mail_host': 'lists.example.com', 'max_message_size': 30000, 'moderator_password': None, 'next_digest_number': 17, 'no_reply_address': 'noreply(a)lists.example.com', 'owner_address': 'project-owner(a)lists.example.com', 'post_id': 91, 'posting_address': 'project(a)lists.example.com', 'posting_pipeline': 'default-posting-pipeline', 'reply_goes_to_list': 'explicit_header', 'reply_to_address': 'me(a)ku.dk', 'request_address': 'project-request(a)lists.example.com', 'send_welcome_message': True, 'subject_prefix': '[project]', 'subscription_policy': 'confirm_then_moderate', 'volume': 10} Henrik Rasmussen

7 years, 10 months

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

by Ruth Ivimey-Cook

On 21/06/2020 04:52, Mark Sapiro wrote: > On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: >> ... the Body of reply, with the JSON text: >> >> { >> "start": 0, >> "total_size": 1, >> "entries": [ >> { >> "alias_domain": null, >> "description": null, >> "mail_host": "ch-bc.org.uk", >> "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", >> "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" >> } >> ], >> "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" >> } > > All these self_link references are generated from self.api.path_t which > is a reference to (in the case of 3.1) > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… > which gets the host portion from config.webservice.hostname, i.e. the > value of hostname in the webservice section of mailman.cfg, and actually > <sigh>, looking back at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > that's exactly where you said you set it to 0.0.0.0. > > Change that to greyarea-post Problem is, if I do that (which I did in the beginning), the core rest service listens on localhost / 127.0.0.1 (it obviously recognises that as the , and so cannot be connected to by anything. That is why I set it to 0.0.0.0 to begin with, and what the documentation implies (fairly strongly) that this parameter is about. IMO, the hostname parameter needs to be split up into a "what address should the rest of the world use to address me" and separately "what address(es) should I listen on". Multiple listen addresses enable multihomed hosts to get the right connectivity, too. Would that be hard? Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

6 years, 1 month

Search results for query "sapiro"