Search results for "Postorius" - Mailman-users

Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, Not a very good response. (venv) mailman@new-server ~ (v3.3.9) [0|1]> mailman-web check postorius Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 158, in get_app_config return self.app_configs[app_label] KeyError: 'postorius' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in handle app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in <listcomp> app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 165, in get_app_config raise LookupError(message) LookupError: No installed app with label 'postorius'. (venv) mailman@new-server ~ (v3.3.9) [0|1]> mailman-web check hyperkitty Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 158, in get_app_config return self.app_configs[app_label] KeyError: 'hyperkitty' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in handle app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/check.py", line 56, in <listcomp> app_configs = [apps.get_app_config(app_label) for app_label in app_labels] File "/local/mailman/venv/lib/python3.10/site-packages/django/apps/registry.py", line 165, in get_app_config raise LookupError(message) LookupError: No installed app with label 'hyperkitty'. (venv) mailman@new-server ~ (v3.3.9) [0|1]> mailman-web migrate -h usage: mailman-web migrate [-h] [--noinput] [--database DATABASE] [--fake] [--fake-initial] [--plan] [--run-syncdb] [--check] [--prune] [--version] [-v {0,1,2,3}] [--settings SETTINGS] [--pythonpath PYTHONPATH] [--traceback] [--no-color] [--force-color] [--skip-checks] [app_label] [migration_name] Updates database schema. Manages both apps with migrations and those without. positional arguments: app_label App label of an application to synchronize the state. migration_name Database state will be brought to the state after that migration. Use the name "zero" to unapply all migrations. options: -h, --help show this help message and exit --noinput, --no-input Tells Django to NOT prompt the user for input of any kind. --database DATABASE Nominates a database to synchronize. Defaults to the "default" database. --fake Mark migrations as run without actually running them. --fake-initial Detect if tables already exist and fake-apply initial migrations if so. Make sure that the current database schema matches your initial migration before using this flag. Django will only check for an existing table name. --plan Shows a list of the migration actions that will be performed. --run-syncdb Creates tables for apps without migrations. --check Exits with a non-zero status if unapplied migrations exist. --prune Delete nonexistent migrations from the django_migrations table. --version Show program's version number and exit. -v {0,1,2,3}, --verbosity {0,1,2,3} Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output --settings SETTINGS The Python path to a settings module, e.g. "myproject.settings.main". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used. --pythonpath PYTHONPATH A directory to add to the Python path, e.g. "/home/djangoprojects/myproject". --traceback Raise on CommandError exceptions. --no-color Don't colorize the command output. --force-color Force colorization of the command output. --skip-checks Skip system checks. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 17 Dec 2023 at 04:15, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Helio Loureiro writes: > > > Well... not that good. Now it is mailman3-web that doesn't work. > > > > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > > System check identified no issues (0 silenced). > > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate > > Traceback (most recent call last): > [omitted] > > LookupError: No installed app with label 'migrate'. > > > > Any idea why migrate isn't working and saying it is installed? > > Management commands aren't applications, so they wouldn't be valid > arguments to "mailman-web check" in any case. > Try "mailman-web check postorius" or "mailman-web check hyperkitty" to > see how the application argument works. You should get the report > "System check identified no issues (0 silenced)." as above. > > Then try "mailman-web migrate -h". > If that returns help output, the migrate command is installed and can > be run (the help string is part of the migrate module, not part of > mailman-web itself). > > Why do you think "mailman-web migrate" isn't working? Most likely > "migrate" is working as designed, but it is doing nothing because > something about the way you transported the database originally caused > mailman-web to think its database schema is up-to-date even though it > is not (as happened with the mailman database). > > Unfortunately this database is managed by Django, not by Alembic, and > I don't know offhand how to discover and tell Django the actual schema > version and then ask it to run any new migrations. > > Steve > > >

1 year, 6 months

Re: Welcome Message

by Abhilash Raj

On Wed, Apr 17, 2019, at 1:41 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > If the URL for template is wrong, or Postorius is down for whatever reason, > > the subscription will fail with the error that you saw before. > > Explain URL for template. You mean "POSTORIUS_TEMPLATE_BASE_URL"? That > is not wrong. I am confident of that. It is back to > "http://mailman-web:8000". I can successfully ping mailman-web:8000 > from bash. POSTORIUS_TEMPLATE_BASE_URL is used to create the template urls, yes. > > > > I logged out of Postorious and subscribed using the > > > subscribe form on > > > the info page and the change to the welcome template showed up. So it > > > looks like being logged in as admin while trying to subscribe someone > > > was what was causing the problem. Is that a bug I discovered? > > I suspect stopping-restarting and re-creating the template (idk, if you > > really did that) might have something to do with it. I am not sure if this > > is a bug unless you can reliably reproduce this. > > This error is absolutely reproducible. It even impacts other list > admins who are trying to use a custom welcome message and subscribing a > member while logged into Postorious. Everything else is working fine on > this server and I followed your directions precisely when I set this > server up. Please help. Can you reply here with the output of this query on your server: $ curl --user restadmin:restpass -L http://172.19.199.2:8001/3.1/lists/mailman-users.mailman3.org/uris Please replace "restadmin:restpass" with the username password of the rest api, if you have customized it. It not leave it as it because that it the default. Also, replace "mailman-users.mailman3.org" with the the List-ID of your mailing list. (replace @ with .) in your posting address. If you don't have curl, choose whatever http client you have. > > Thanks, > Brian > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

Re: Hyperkitty on Debian 12

by Michael Oberrauch

On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key > used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a > subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > Hi Markus, we are also running MM3 on Debian 12 from Package Repositories. First of all, you should not try to directly switch user (su) to the lists user, it's generally intended to executes commands as that user, if necessary; either using `runuser`, `sudo`, or `su -c`. However, the prepackaged scripts `mailman-wrapper` and `mailman-web` already do this and therefore you ca run those as root without permission problems. On Debian there are two relevant users for MM3: the list user runs mailman core, whereas the www-data user runs Postorius and Hyperkitty. So you have to make shure, that the www-data user can access the .mbox files while importing. Hope that helps. Cheers, Michael -- Michael Oberrauch (er/ihm) Computerreferent Fachschaft Mathematik/Physik/Informatik/Chemie Studentische Vertretung Technische Universität München Boltzmannstraße 3 85748 Garching eMail: oberrauch(a)fs.tum.de Tel: (+49) 089 289 18545 Fax: (+49) 089 289 18546 https://mpic.fs.tum.de

1 year, 2 months

Error after upgrading mailman3

by Gelpi Andrea

Hi, in my installation the command mailman notify does not exist. Checking the debian packages I noticed the I could upgrade mailman form 3.2.1 to 3.2.2; mailman-web form 20180916-8 to 20180916-10; python3-django-hyperkitty from 1.2.2 to 1.3.2 I did it with apt-get install After that when I try to go to a postorius page the error Mailman REST API not available. Please start Mailman core in mailman log I found: May 4 15:13:08 posta mailman3[10259]: Cannot import runner module: mailman.runners.rest.RESTRunner May 4 15:13:08 posta mailman3[10259]: Traceback (most recent call last): May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 55, in make_runner May 4 15:13:08 posta mailman3[10259]: runner_class = find_name(class_path) May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name May 4 15:13:08 posta mailman3[10259]: module = import_module(module_path) May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module May 4 15:13:08 posta mailman3[10259]: return _bootstrap._gcd_import(name[level:], package, level) May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 1006, in _gcd_import May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 983, in _find_and_load May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 677, in _load_unlocked May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap_external>", line 728, in exec_module May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/runners/rest.py", line 27, in <module> May 4 15:13:08 posta mailman3[10259]: from mailman.rest.wsgiapp import make_server May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 25, in <module> May 4 15:13:08 posta mailman3[10259]: from falcon.routing import map_http_methods, set_default_responders May 4 15:13:08 posta mailman3[10259]: ImportError: cannot import name 'map_http_methods' from 'falcon.routing' (/usr/lib/python3/dist-packages/falcon/routing/__init__.py) I think there is a dependency error somewhere. Is there a way to solve it? Thank You -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 1 month

Re: An archive/read-only list on a full setup?

by Mark Sapiro

On 4/11/23 09:36, Andreas Schamanek wrote: > > I have a working full installation of mailman3, postorius and hyperkitty > (on Debian 11). Now I wanted to host the archive of a remote list, and I > am wondering how to do this properly. > > After I found no documentation and no posting I simply created a list in > mailman3 with only 1 dummy member. The list address is subscribed to the > actual remote list. So, messages arrive and are archived. But that's not > optimal because hyperkitty thinks it's a normal list where it should be > read-only and do not allow subscriptions etc. > > What's the proper way to set up a hyperkitty-only list? There really isn't one as HyperKitty is intended to archive Mailman lists, however, it is possible to have a list in HyperKitty without a corresponding Mailman list. Thus, in your case you could just remove the Mailman 3 list you created and leave the HyperKitty list. Then you have an issue with posts, so you can keep sending the posts to be archived to the prior list address, but arrange for the incoming MTA to pipe mail to that address to a process. That process would do the following. Add a Unix From_ line at the beginning of the message and write the result to a temp file. Invoke a command like django-admin hyperkitty_import --no-sync-mailman --since 1990-01-01 \ -l list(a)example.com /path/to/the/tempfile where list(a)example.com is the actual HyperKitty list. This will archive the message. The addition of a Unix From_ line is to make the message file look like a mbox. Since there is no Mailman list, attempts to post or reply directly from HyperKitty will fail, although such attempts using email software will probably succeed in archiving the mail, and mail directly to that list address will be archived, but such messages won't go to the remote list. This may not be any better than what you're currently doing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: "The content of this message was lost."

by Jens Günther

You have to incorporate these 2 changes: https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs and https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs We made it persistent in the Dockerfile of mm-core, so that it will be rewritten every time when building the container: COPY ./moderator.py /usr/lib/python3.8/site-packages/mailman/app/moderator.py COPY ./test_moderation.py /usr/lib/python3.8/site-packages/mailman/app/tests/test_moderation.py It is already fixed in Postorius 3.3.6, but it's not clear, when maxxking's containers will be bumped to that version. Am 09.09.22 um 16:33 schrieb skenny(a)scss.tcd.ie: > I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). > > This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. > > In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read > > The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list. > > I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? > > Thanks for any advice. > Stephen > > PS: > The Mailman web interface "System Information" link reports: > Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > _______________________________________________ > 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, 9 months

Re: Moderator e-mails only going out once a day

by Odhiambo Washington

On Mon, Apr 21, 2025 at 10:16 PM dgoldsmith--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > I am having a similar issue as Joe. > > Our Mailman 3 server is running on Rocky Linux 9.5. It is deployed using > a Python virtual environment. > > (venv) [mailman@<server> shunt]$ mailman info > GNU Mailman 3.3.9 (Tom Sawyer) > Python 3.9.21 (main, Dec 5 2024, 00:00:00) > [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] > config file: /etc/mailman3/mailman.cfg > <output trimmed> > > Mailman 3.3.9 > Postorius Version 1.3.10 > HyperKitty version 1.3.9 > Postfix = 3.5.25-1.el9 (may have some newer bits backported into it - RHEL > way) > Django version = 4.2.13 > > Output of the for loop Mark provided above shows that all the lists on the > server have admin_immed_notify set to True. > > Here is the activity from the mailman.log file when I send a message to > the list and it gets held: > > Apr 21 19:11:37 2025 (2564) sans-faculty: DMARC lookup for > dgoldsmith(a)sans.org (_dmarc.sans.org) found p=reject in _dmarc.sans.org. > = v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email > Apr 21 19:11:37 2025 (2564) HOLD: sans-faculty(a)mlm.sans.org post from > dgoldsmith(a)sans.org held, message-id= > < > SJ0PR18MB5112D63A7D9F3851A4A6B0C0AEB82(a)SJ0PR18MB5112.namprd18.prod.outlook.com>: > The message comes from a moderated member > > No further activity indicating it sends (or attempts to) a notice to the > list admins/mods about a held message. > Assuming you did run the mailman shell command and the output was: ```List sans-faculty(a)mlm.sans.org Immed notify True``` What do you have in your MTA logs around the same time? Nothing? That would imply that for this list, you have set "Default action to take when a non-member posts to the list" to "Discard" If you change that setting to "Hold for moderation", then you will receive a notification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 month, 3 weeks

Re: There are currently no mailing lists!?

by Odhiambo Washington

On Mon, Jul 22, 2024 at 9:06 PM Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > I recently upgraded Debian 10 'buster' and when I logged in to Postorius in > the browser I got the ' Mailman REST API not available. Please start > Mailman > core' message. So I started it up from the command line doing 'sudo -u > mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded > You upgraded Debian from Buster to what??? Bullseye or Bookworm? Why not just 'sudo systemctl start mailman'? > Starting Mailman's master runner > Generating MTA alias maps > mailman@lists: > > Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists > ' > in my browser I get the message ' There are currently no mailing lists.' > Meanwhile their archives exist. Are the lists actually gone or ? > The lists are there since your DB is intact and your venv is intact as well. > > What am I doing wrong/what's going on here please? Thank you in advance. > I suspect your Python was upgraded to a version different than the one you use to create your virtualenv in the 1st place. If that is the case, you'll need to create a new virtualenv and migrate the data. > One more thing...I am running mailman core version GNU Mailman 3.3.5, Core > API Version 3.1, and Core Python Version 3.7.3. > Is there a reason you did not upgrade MM3 core and MM3 Web all this time? Anyway, check the version of Python used to build your virtualenv against the system version after you upgraded: # cat /opt/mailman/mm/venv/pyvenv.cfg home = /usr/local/bin include-system-site-packages = false version = 3.11.2 executable = /usr/local/bin/python3.11 command = /usr/local/bin/python -m venv /opt/mailman/mm/venv If older than the system version, you just need to build a new virtualenv and migrate the data. HTH. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months, 3 weeks

Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, I can't find any log entry which indicate a problem with this subscription request. The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. The token is found in the pended table: +-----+------------------------------------------+---------------------+ | id | token | expiration_date | +-----+------------------------------------------+---------------------+ | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | +-----+------------------------------------------+---------------------+ These are the relevant entries in the pendedkeyvalue table: +------+--------------+-------------------------------------+-----------+ | id | key | value | pended_id | +------+--------------+-------------------------------------+-----------+ | 1130 | type | subscription | 115 | | 1131 | list_id | "********************" | 115 | | 1132 | email | "***********************@*********" | 115 | | 1133 | display_name | "" | 115 | | 1134 | when | "2021-01-06T16:17:38" | 115 | | 1135 | token_owner | "moderator" | 115 | +------+--------------+-------------------------------------+-----------+ Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Thanks in advance, Eric On Friday, January 15, 2021, 11:42:47 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- 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, 5 months

Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Thu, Sep 30, 2021 at 4:09 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Thu, Sep 30, 2021, at 2:20 AM, Odhiambo Washington wrote: > > On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > >> > >> > >> > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> > >> wrote: > >> > > >> > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > > >> >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: > >> >>> 1. Confirmation emails to Users has wrong domain name (example.com > !) > >> >>> <https://docs.mailman3.org/en/latest/faq.html#id1> > >> >>> < > >> >> > >> > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > >> >>> > >> >>> > >> >>> This happens when your reverse (SSL) proxy isn’t setting up the > correct > >> >>> headers when proxying requests. Fix this by setting the right > >> >>> proxy_set_header directives: > >> >> ... > >> >>> How is this supposed to be mitigated in Apache when using WSGI? > >> >>> > >> >>> My config: > >> >>> > >> >>> WSGIDaemonProcess hyperkitty threads=25 > python-path=/usr/local/mailman > >> >>> user=mailman group=mailman > >> >>> WSGIPythonHome "/usr/local" > >> >>> WSGIProcessGroup hyperkitty > >> >> > >> >> > >> >> You are using mod_wsgi and not proxying at all, so this is not > relevant > >> >> in your case. > >> >> > >> >> Are you actually seeing this issue? If so, it might be related to > >> >> > >> >> > >> > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > >> >> > >> > > >> > My issue is related to this, but the documentation referred to is not > for > >> > the faint-hearted! > >> > I can't make head or tails of it. > >> > >> Click on “Domain” in Postorius from the top bar, which should take you > to > >> the Domains page. > >> > >> For your domain (in the “Mail Host” column), see the corresponding “Web > >> Host” column, it should look something like: > >> > >> lists.mailman3.org (lists.mailman3.org) > >> (Edit) > >> SITE_ID = 1 > >> > > > > Mine looks different, slightly. But there is no example.com at all. > > > > [image: Abhilash.png] > > > > > > > >> > >> on a new-ish version of Postorius. > >> > > > > I have the newest versions of everything, having installed only > yesterday. > > > > > >> > >> If it doesn’t show the right values and instead shows “example.com” for > >> you, click on the “Edit” link, which will take > >> you to a page that will allow you to edit both the values. > >> > > > > It shows the right values, but with "SITE_ID = 2". In my > settings_local.py > > I have SITE_ID = 1. > > I suppose the example.com is the one tied to SITE_ID = 1 and that is > what I > > have in my settings_local.py. > > That is most likely what is happening. > > > Should I edit my settings_local.py? > > Yes, please update it to have SITE_ID = 2 to correspond to the site you > want and restart. > Thank you very much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 8 months

Mailman-users search results for query "Postorius"