Search results for "Postorius" - Mailman-users

Re: config incoming email in my domain cpanel

by tlhackque

I think you're confused. You already have mail.labbrands.com set up as the MX record for labbrands.com. And it has an A record with the same address as your webserver. So if you're getting e-mail on that domain, there's another e-mail server running on that IP address. You can't have 2 servers on port 25. In that case, as has been noted before, you'll need to setup a relay in that server, not a firewall redirect. Depending on your MTA, you would need to relay to your internal server. And make sure your firewall setup allows your MTA to do this. We can see it's EXIM: telnet mail.labbrands.com 25 Trying 192.185.51.89... Connected to mail.labbrands.com (192.185.51.89). Escape character is '^]'. help 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 -0500 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. 214-Commands supported: 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP quit 221 gator4137.hostgator.com closing connection Connection closed by foreign host. Or, consolidate all your e-mail to one server - which is a lot easier to manage unless you have a really big operation. Postfix is probably the right choice, but requires more setup. Although Mailman3 configuration is not well documented (as you've discovered), you may want to get help from someone with more general network and mail experience. You're now into territory that is, as Simon indicated, not Mailman-specific. On 03-Aug-17 16:28, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) escribió: > >> On 08/03/2017 01:22 PM, Rafael Mora wrote: >>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) >> escribió: >>>> You need to forward port 25 for SMTP mail delivery and if you want the >>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >>>> for http and/or port 443 for https >>>> < >>>> >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>>>> . >>> I mean for incoming mail redirected from my hostgator hosting, because >> when >>> I suscribe an email address MM3 sends a confirmation email, so I have to >>> reply to be suscribed to the list. >> >> As I said, for mail delivery you need to forward port 25 to the Mailman >> server. >> > Ok so I'll redirect in my zentyal firewall the port 25 to my local centos7 > with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > >> >> -- >> 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 >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> -- This communication may not represent my employer's views, if any, on the matters discussed.

8 years, 5 months

Re: admin/login/ cannot be accessed

by Abhilash Raj

On Wed, Dec 11, 2019, at 9:25 AM, jean-christophe manciot wrote: > Ubuntu 20.04 > python3-django 2:2.2.6-1ubuntu1 > python3-django-hyperkitty 1.3.1 (built from sources) > mailman3-full 3.2.2-1 Which version of Django are you using? > > Nginx server configuration: > ``` > ... > ######## > # Static > ######## > location /favicon.ico > { > alias <mysite_dir>/static/hyperkitty/img/favicon.ico; > } > location /static/favicon.ico > { > alias <mysite_dir>/static/postorius/img/favicon.ico; > } > location /static/ > { > alias <mysite_dir>/static/; > } > > ####################### > # Upstream uwsgi server > ####################### > location / > { > include /etc/nginx/uwsgi_params; > uwsgi_pass 127.0.0.1:<uwsgi_server_port>; > } > ... > ``` > where: > - <mysite_dir> is a symlink to <django_dir>/static > - <uwsgi_server_port> matches the one defined in ```/etc/mailman3/uwsgi.ini```: > ``` > [uwsgi] > # Port on which uwsgi will be listening. > uwsgi-socket = 127.0.0.1:<uwsgi_server_port> > ``` > The config looks good to me in a quick glance. > All 3 systemd services run fine: > - mailman3 > - mailman3-web > - qcluster > > I'm trying to login to the django administration pages. > I get the django administration login page at: > https://mysite/admin/login/ > Logging in with the admin credentials leads to: > ``` > This site can’t be reached > The webpage at https://mysite/admin/login/ might be temporarily down or > it may have moved permanently to a new web address. > ERR_HTTP2_PROTOCOL_ERROR > ``` > This is very strange because it is the URL which I used to get the > login page in the first place. Looking at the error, it seems like something somewhere is re-directing to HTTP/2 or the request is based off of HTTP/2 and all the components in the stack don't support HTTP/2, leading to the error message. I haven't played a lot with HTTP/2 yet so I am not sure which specific component in the stack could be incompatible here. > > If I launch a test web server at another port with: > ``` > <django_dir># python3 manage.py runserver <mysite_ip_address>:8080 > Performing system checks... > > System check identified no issues (0 silenced). > December 11, 2019 - 17:50:48 > Django version 2.2.6, using settings 'settings' > Starting development server at http://<mysite_ip_address>:8080/ > Quit the server with CONTROL-C. > ``` > and access it at ```http://<mysite_ip_address>:8080/admin/login/``` to > login with the same credentials as before, I get through and all the > django administration lines appear, although in a degraded layout: > ``` > Site administration > Accounts > Email addresses Add Change > Authentication and Authorization > Groups Add Change > Users Add Change > Django Mailman 3 > Mail domains Add Change > Profiles Add Change > ... > ``` > Any idea what could be happening here? Degraded layout is due to missing static files since the development server that you spun off doesn't serve static files. So, that is okay. > _______________________________________________ > 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, 1 month

Re: [Spam] Installation Help on Ubuntu 18

by Odhiambo Washington

On Sun, 26 Jul 2020 at 18:22, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 12:37 AM, Stephen J. Turnbull wrote: > > > > That's not our guide, we don't support it, and at least I don't > > recognize the author offhand, can't speak for the rest of the team. > > > The author has been involved in a few threads on this list. > > > > Now that our NO WARRANTY notice is out of the way, I will say that > > guide is written in very good style, with great attention to detail > > and appropriate warnings about delicate parts of the procedure. If > > you end up succeeding with it, I'll add a link to it to our docs. > > > It is currently linked from the first paragraph at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. > I followed the steps outlined in the subject document and got mailman3 running. However, what is missing in that document is the process of setting up a webserver for accessing the MM3 UI. I have spent two days trying to figure out that aspect and discovered a few things (I could be wrong in what I think): 1. For one to use the uwsgi.ini that is dropped in /etc/mailman3/ by the installation process, the uwsgi daemon must be installed: *apt install uwsgi-core uwsgi* 2. The uwsgi.ini must be linked in the directory where the uwsgi daemon looks for config files: *cp /etc/mailman3/uwsgi.ini /etc/uwsgi/apps-available/uwsgi.ini* *ln -s /etc/uwsgi/apps-available/uwsgi.ini /etc/uwsgi/apps-enabled/uwsgi.ini* 3. The uwsgi daemon needs to be started *systemctl start uwsgi* root@lists:/etc/mailman3# ps ax | grep wsgi 5838 ? S 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5841 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5842 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log Now that uwsgi daemon is running, the last step would be to configure the webserver to serve the MM3 pages. The apache config snippet dropped by the mailman3 install process in /etc/mailman3/apache.conf contains: <BEGIN> Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> <END> I added those to a virtualhost where I am running mailman2.x, but I couldn't access any of the defined aliases: https://lists.my.site/mailman3/static/ - gives "You don't have permission to access this resource." Apache says AH01276: Cannot serve directory /var/lib/mailman3/web/static/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive I am stuck at that point ... -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 5 months

Re: Upgrade path

by David Krantz

Hi. Getting back to this... Some log of what I'm doing. * First git fetch; git pull on all parts. Started new envs to simplify rollback etc. * activate the new 3.5 venv. ( I run the commands one at a time, but this is more compact in text form:) > cd git/mailman; python setup.py build; python setup.py install > cd ../mailman-hyperkitty; python setup.py build; python setup.py install > deactivate activate 2.7 venv, then > cd ../mailmanclient; python setup.py build; python setup.py install > cd ../django-mailman3; python setup.py build; python setup.py install > cd ../postorius; python setup.py build; python setup.py install > cd ../hyperkitty; python setup.py build; python setup.py install So far no errors. Just warnings. Backups: * deployment directory (as user with rw in directory) > tar -cvzf backup.tgz deployment_directory * postgres databases (as user with postgres-priv) > pg_dump maiman | gzip -9 > mailman.bak.gz > pg_dump mailmanweb | gzip -9 > mailmanweb.bak.gz Create new .wsgi-file based on mailman-suite (I used the kludge in the script to get the python path correct) Change apache2.conf to point to new venv and new wsgi-version Updated the mailman3wrapper.sh I use for init to start the service. I could not get hyperkitty interface to run so I deactivated it and set mailman as index instead. It complains that a column is missing, but I cannot get the migrate script to run so I decided that I do not need the archiver as I currently don't use it. So I will have to get back to this and either remove the archiver completely or get it to run. So the line with ^$ in urls.py now is url(r'^$', RedirectView.as_view(url=reverse_lazy('list_index'))), instead, and the line "hyperkitty," is commented in the django application list. cheers. // David On Tue, Aug 8, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/08/2017 04:42 AM, David Krantz wrote: >> >> What is the rekommended way to upgrade to the newest version? (newest >> _usable_ version, of course)? Is it docker-only with a migration from >> the current solution to a docker based? If so, any ideas or pointers >> on how to go about this? > > > You may find this wiki article helpful <https://wiki.list.org/x/17891998>. > > I started with bundler on both this (lists.mailman3.org) and the > mail.python.org installs, but have been updating from the heads of the > various gitlab branches since very early on. > > At the moment, these installations are somewhat ahead of the 3.1 > release, but I am not updating as the latest core has dropped Python 3.4 > support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu > 14.04) servers. (I will probably install 3.6 from source at some point.) > > Please feel free to ask here if you have more specific questions. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 3 months

mailman-web migrate error

by pashdown＠xmission.com

I'm migrating from Ubuntu 20.04, mailman 3.2.2, postgresql 12 to Debian 13, mailman 3.3.10, postgresql 17. After migrating the postgresql databases and assuring the perms and passwords work, this is what I get with a "mailman-web migrate": (user(a)domain.com) redacted from the original # mailman-web migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, \ sessions, sites, socialaccount Running migrations: Applying account.0003_alter_emailaddress_create_unique_verified_email... OK Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying account.0006_emailaddress_lower...Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_\ email_987c8728_uniq" DETAIL: Key (user_id, email)=(24, user(a)domain.com) already exists. The above exception was the direct cause of the following exception: The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() ~~~~~~~~~~~~~~~^^ File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 436, in execute self.fetch_command(subcommand).run_from_argv(self.argv) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 412, in run_from_argv self.execute(*args, **cmd_options) ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 458, in execute output = self.handle(*args, **options) File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 106, in wrapper res = handle_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", line 356, in handle post_migrate_state = executor.migrate( targets, ...<3 lines>... fake_initial=fake_initial, ) File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( state, plan, full_plan, fake=fake, fake_initial=fake_initial ) File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( state, migration, fake=fake, fake_initial=fake_initial ) File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/usr/lib/python3/dist-packages/django/db/migrations/migration.py", line 132, in apply operation.database_forwards( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ self.app_label, schema_editor, old_state, project_state ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3/dist-packages/django/db/migrations/operations/special.py", line 193, in database_forwards self.code(from_state.apps, schema_editor) ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/migrations/0006_emailaddress_lower.py", line 11, in forwards EmailAddress.objects.all().exclude(email=Lower("email")).update( ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ email=Lower("email") ^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 1206, in update rows = query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1984, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql cursor.execute(sql, params) ~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( ~~~~~~~~~~~~~~~~~~~~~~~~~~~^ sql, params, many=False, executor=self._execute ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: duplicate key value violates unique constraint "account_emailaddress_user_id_email_987c8728_uniq" DETAIL: Key (user_id, email)=(24, user(a)domain.com) already exists.

2 months

Re: Held messages not delivered after approval

by Krinetzki, Stephan

Hi Mark, >That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely >caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. You are my hero! After "patching" the outgoing.py file with the error messages I got Aug 06 09:52:51 2025 (443278) Cannot connect to SMTP server 127.0.0.1 on port 25: HTTPSConnectionPool(host='lists.example.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/hpc-admintreffen-info.lists.example.com/list:member:regular:footer (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)'))) And was shocked. Why is there an SSL Certificate Error? Why can't python requests verify the certificate? So I googled a bit and found, that we can fix this be editing the cacert.pem of certifi. I did, but the error was still there. So I checked my https VHost (Apache btw) and there was a wrong chain in it. Oof. An error, that a browser does not see, but any ssl client. I fixed it and boom - everything works again. Thank you again and thank you Stephen for trying to resolve the problem 😊 -- Stephan Krinetzki IT Center Gruppe: Anwendungsbetrieb und Cloud Abteilung: Systeme und Betrieb RWTH Aachen University Seffenter Weg 23 52074 Aachen Tel: +49 241 80-24866 Fax: +49 241 80-22134 krinetzki(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 5, 2025 6:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Held messages not delivered after approval On 8/5/25 02:06, Krinetzki, Stephan wrote: > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost > on port 25 > > The last error is a very often in the mailman.log: That's a misleading message. It's been improved by https://gitlab.com/mailman/mailman/-/merge_requests/1362, however usually the underlying issue is inability to access a header or footer template when decorating the message. This in turn is most likely caused by some template(s) in Mailman's var/templates/ directory being owned by `root` or some other non-mailman user and not readable by the Mailman user which in turn most likely results from running `mailman import21` as root. Bottom line - check that all sub-directories and files in Mailman's var/templates/ directory are searchable and readable by the Mailman user. -- 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 krinetzki(a)itc.rwth-aachen.de

5 months, 1 week

Re: Mailman, etc. upgrade woes and persistent bugs

by Abhilash Raj

On Wed, Feb 17, 2021, at 10:24 PM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > So it seems like we have some sort of agreement that we need all the > > roles to be able to see all the 4 states. > > I think it's more like there's disagreement about which roles need to > see which states, but for each role and each state, somebody thinks > that role needs to see that state. I think there's agreement that > it's harmless to allow everybody to see all states. > > > Roles here are basically Admin( i.e. list owner/moderator/site > > admin) and Subscriber. > > In this discussion, yes. However, if we're going to take the > discussion seriously, we should be more general than just this case. > I think we need to consider five roles. Starting with Brian's list of > List Owner, Moderator, List Member, and adding Anonymous (so that a > pre-login connection has a named role) and Site Owner for completeness. Yep, those are all the roles that even we recognize in Postorius. We also have the concept of Domain Owner, though that isn't really implemented yet. So, from this list, List Owner and above all will use the "by_admin" state to disable if they need to and they are the only ones who can set that state. > > > There is no access control to transition "from" any state but each > > value of non-enabled states is sort of a role's way to disable the > > delivery. Not all states are settable by all roles. > > Off-list, Ruth Ivey-Cook informs me that in "who sets what" both "who" > and "what" need to be considered is what she had in mind. So I think > that's exactly right and there's agreement. Nice. > > > 1. A subscriber can only transition from any to "enabled" or "by_user" > > state but can see if delivery was disabled "by_admin" or "by_bounces" > > as separate state in the Options page. > > 2. An admin can transition to "enabled", "by_user" and "by_moderator". > > I assume you mean "by_admin" instead of "by_moderator"? Ok, I've made a mess of it in my responses, the Core actually calls this value "by_moderator" but I have used them interchangeably in my emails. Sorry about that. https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/mem… > > > They should use "by_user" when acting on behalf of the user and other > > when there are any administrative reason to disable delivery, whatever > > that may be. I expect "by_admin" to be used sparingly, and I don't see > > any use cases for it. > > 3. Mailman itself will use the "by_bounces" to disable delivery due to > > bounces. > > > > Is that an accurate description? > > +1 for 1 -- 3 as written. Others' mileage may vary. Cool, thanks! > > Steve > > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

Re: Post-installation documentation?

by David Newman

On 11/25/21 1:16 PM, Mark Sapiro wrote: > On 11/25/21 10:56 AM, David Newman wrote: >> >> Thanks for this. After setting these variables and restarting mailman3 >> and mailmanweb, the mailman user still cannot find a hyperkitty_import >> command (neither can root, btw). Again, I installed MM3 and >> Django/Postorius/Hyperkitty using the venv and web docs previously >> referenced. > > > Don't run mailman or django admin commands as root. This causes issues > when files are created by root and can't be read by mailman. Understood, thanks. I'd only tried root to determine if there was a permissions issue, where hyperkitty_import really did exist but wasn't available to the mailman user. > > What django admin command are you running? As the mailman user, with venv activated: (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox 'testlist' and 'lists.domain.com' are redactions; they are correct in the given command, but the command fails because the system can't find hyperkitty_import. (BTW Also, because I'm looking to migrate from Mailman 2.1 installed from Debian packages, all the 2.1 stuff is owned by the 'list' user. I'd changed ownership of the above private archive to mailman:mailman for the command not to complain about permissions. > If you don't set > DJANGO_SETTINGS_MODULE in the environment and you have activated your > virtualenv and run `mailman-web` as the django admin command it will set > /etc/mailman3/settings.py as the settings. I'd run these two environment commands as the mailman user with virtualenv activated: export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/etc/mailman3/settings.py Am I being overly literal here with 'settings' in that first command? Asking because 'mailman-web check' runs clean before running these commands and returns this error afterward: ModuleNotFoundError: No module named 'settings' Either way, the hyperkitty_import command still isn't found. >> On the plus side, all lists now appear in the admin web page. However, >> lists created from the admin page do not appear in a site list page, >> even though all lists are in the same site/domain. > > > By default, only lists that you are owner, moderator or subscriber for > are shown. What if you click Filter by Role and select All? Same result. In this case, the ID of the admin and list owner are the same. > > >> Finally, how to make these exports permanent? I did not see this >> covered in the migration doc above. This is on a Debian system where >> the mailman user's shell is bash. Is this simply a matter of adding >> environment variables in the mailman user's .bashrc file? > > You can do that but as I note above, if you run `mailman-web` you > shouldn't need to. You can add a `source /opt/mailman/venv/bin/activate` > command as mentioned at > https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtua…. Yes, this is what I have in mailman's .bashrc file. I'd followed that venv doc for initial installation, and it activates the virtualenv whenever launching a shell for mailman. dn

4 years, 1 month

Re: KeyError: 'subject_prefix'

by Abhilash Raj

On Sun, Nov 15, 2020, at 1:20 AM, Torge Riedel wrote: > Hi, > > today I had the following error in my inbox: > > KeyError: 'subject_prefix' > AttributeError: 'MailingList' object has no attribute 'subject_prefix' > > I checked the database, there is a column "subject_prefix", so I feel > it is something in the code causing the error. > > It's mailman 3.3.1 and I don't see a fix for such an error in the > Changes of 3.3.2 > Is the value of subject prefix for that list set to *something* in Mailman? You can check via API or if you have Postorius, you can go to List's settings page and under the "List Identity" tab there is a field. I am suspecting Hyperkitty wants to read this attribute but since it is not set in database, Core is skipping the field in API response for /list/<listid>/config which typically returns all the list settings. Abhilash > Kind regards > Torge > > Traceback (most recent call last): > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ > return self._get(name) > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 86, in _get > raise KeyError(key) > KeyError: 'subject_prefix' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/models/mailinglist.py", line 197, in update_from_mailman > value = getattr(mm_list, propname) > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ > self.__class__.__name__, name)) > AttributeError: 'MailingList' object has no attribute 'subject_prefix' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs > job().execute() > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/jobs/sync_mailman.py", line 36, in execute > sync_with_mailman() > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/lib/mailman.py", line 132, in sync_with_mailman > mlist.update_from_mailman() > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/models/mailinglist.py", line 199, in update_from_mailman > value = mm_list.settings[propname] > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ > return self._get(key) > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 88, in _get > return self.rest_data[key] > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File > "/opt/mailman/web/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 500: <html> > <head> > <title>Internal Server Error</title> > </head> > <body> > <h1><p>Internal Server Error</p></h1> > > </body> > </html> > > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > START TRACEBACK: > END TRACEBACK > _______________________________________________ > 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)

5 years, 1 month

Re: Question about adding addresses using the REST API

by Stephen Daniel

TL;DR: Listening to the advice, I will create and manage user/address pairs. I am in the process of porting a web site that is used to manage a small organization. The web site maintains a directory of users of that organization, and also allows them to subscribe/unsubscribe to a small set of interest-group mailing lists for that organization. The users are not tech savvy, and are not expecting or expected to manage their subscriptions through Postorius, nor do they have access (normally) to the archives. Indeed, the URL to Postorious will normally be turned off at the reverse proxy server that sits in front of both Postorious and the organization's website. The one-source-of-truth is the website's database. The website code has callouts for "subscribe <address> to <list>" and "unsubscribe <address> from <list>". I am trying to minimize the amount of code I write to implement the web site's callouts, to initialize the mailing lists when I port the organization to this new implementation, and make it relatively easy to keep the website's database and mailman3's database in sync. The impression I had from the docs was that unlinked addresses were a first class object. Since my website callouts only deal with addresses, this seemed a good mapping. However, I understand from this email thread that unlinked addresses are not the way to go, so I'll map <address> in the website database to <user>/<address> in mailman3. Thanks for the advice and feedback! -- Stephen Daniel On Sat, Jan 15, 2022 at 2:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/15/22 10:03 AM, Stephen Daniel wrote: > > > > The only way I've found to create a standalone address (not linked to any > > user) is to create a user with that address, unlink the address, then > > delete the user. > > > > Is there a more straightforward way to just create an address with no > user? > > > The more straightforward way is via the IUserManager create_address > method. This method is not exposed directly in REST, so you can't do it > via REST. > > My question is why do you want to? > > Granted when an unknown nonmember address posts to a list we create a > standalone address record, but maybe we should be creating a user too. > We don't because it's tricky. Suppose User A with address A posts to a > list from nonmember address B. We create the standalone address B record > as a nonmember, but now user A can add address B as another address. If > we also created User B, this would not be possible. > > But again, what is your use case for creating standalone addresses? > > > -- > 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

Mailman-users search results for query "Postorius"