Search results for "Postorius" - Mailman-users

Where does sender postorius@ come from?

by Jens Günther

I just realized, that mails for registering an account and/or resetting ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why are they not sent from MAILMAN_ADMIN_EMAIL? The problem is: - an account is trying to register with a mailaddress from a HostEurope-server - HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to verify that a mailaccount exists - mail is then bouncing, b/c those are not answered (shoud I?): status=bounced (host [80.237.138.5] said: 550-Sender verification is required but failed. - bounce then can't be processed, since mailaccount does not exist :-D status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself) Am I missing something are shouldn't it be better to send those mails from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender callouts or change anything, HostEurope has been a little bit of a pain in the ... with mailinglists and not much help at all). Thanks in advance, Jens.

2 years, 9 months

Re: Core, Hyperkitty and Postorius releases

by Guillermo Hernandez (Oldno7)

On 15/5/21 0:29, Odhiambo Washington wrote: > > > On Sat, May 15, 2021 at 1:08 AM Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org>> wrote: > > > On 14/5/21 23:52, Odhiambo Washington wrote: > >> Which OS are you using? > > FreeBSD. > > > > > As Mark pointed, you probably have installed the textproc/sassc > port (or > package). I'ts an equivalent for sass. Do the config as advised. > > I have mailman3 installed and running smoothly in a pair of 12.2 > RELEASE > FBSD servers. > > There is a thread about this installations that can help: > https://forums.freebsd.org/threads/mailman-3.61050/post-488128 > <https://forums.freebsd.org/threads/mailman-3.61050/post-488128> > > > > I will look into this. I know FreeBSD has a mailam3 port, The mailman3 port runs, but aaaaaall the other apps needed, just no. Following the FreeBSD ports route ended in a failure. In the previous post on the link I explained all the failed tries. > but I have mailman2 in production and the port installs to > /usr/local/mailman I had mailman2 indeed. And migrated to mailman3 all my lists (17 in one server, 2 in other). One of them with more than 8000 suscribers. I know it's not much, but in that thread you can find example config files than you can compare. They are working. > so I have to be careful - install mailman3 in /opt, then plan on > hosing mailan2 and moving mailman3 to it's place after migration. > It's not simple. Yes, I know. I did. Best luck. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 10 months

Re: Migration from old server to new server failed

by Helio Loureiro

Hi, Thanks for the tip. Now I can see hypperkitty available. But I'm still seeing some errors. Feb 22 14:16:56 2024 (2062795) HyperKitty failure on http://127.0.0.1/archives/api/mailman/archive: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> (500) Feb 22 14:16:56 2024 (2062795) Could not archive the message with id < AM6PR07MB592539392144457915580AF992752(a)ABCD.externaldomain.com> Feb 22 14:16:56 2024 (2062795) archiving failed, re-queuing (mailing-list cn-lratci-op.mailman3.domain.com, message < AM6PR07MB592539392144457915580AF992752(a)ABCD.externaldomain.com>) Feb 22 14:16:56 2024 (2062795) Exception in the HyperKitty archiver: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Feb 22 14:16:56 2024 (2062795) Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Which might be a minor issue since now I can access the web page and login is working again. Thanks a lot! Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 22 Feb 2024 at 11:31, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Thu, Feb 22, 2024 at 12:49 PM Helio Loureiro <helio(a)loureiro.eng.br> > wrote: > >> Hi, >> >> Any suggestions here? >> > > [snip] > > >> > I'm using uwsgi via apache: >> > > Okay. > > >> > (venv) mailman@new-mailman3 ~ (v3.1.1)> more >> > /etc/apache2/conf-enabled/mailman3.conf >> > Alias /mailman3/favicon.ico /local/mailman/web/static/favicon.ico >> > Alias /mailman/favicon.ico /local/mailman/web/static/favicon.ico >> > Alias /favicon.ico /local/mailman/web/static/favicon.ico >> > Alias /mailman3/static /local/mailman/web/static >> > Alias /mailman/static /local/mailman/web/static >> > Alias /static /local/mailman/web/static >> > >> > <Directory "/local/mailman/web/static"> >> > Require all granted >> > </Directory> >> > >> > <IfModule mod_proxy_uwsgi.c> >> > ProxyPass /mailman3/favicon.ico ! >> > ProxyPass /mailman/favicon.ico ! >> > ProxyPass /favicon.ico ! >> > ProxyPass /mailman3/static ! >> > ProxyPass /mailman/static ! >> > ProxyPass /static ! >> > ProxyPass /mailman3 >> > unix:/local/mailman/var/uwsgi.sock|uwsgi://localhost/ >> > ProxyPass /mailman >> > unix:/local/mailman/var/uwsgi.sock|uwsgi://localhost/ >> > #ProxyPass /mailman3 http://localhost:8000/ timeout=180 >> > #ProxyPass /mailman http://localhost:8000/ timeout=180 >> > #ProxyPass / http://localhost:8000/ timeout=180 >> > </IfModule> >> > > Mostly I can only see the "Page not found" error. So let's try just the > standard config (using TCP socket) as documented and see. > In the documented configuration, I can see that you do not have > "ProxyPreserveHost On" in your configuration, but to be honest, I am not > sure of that is the problem. > Let's try doing this the standard way, according to the documentation at > https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… > : > Let's also log and analyze what Apache says. Use the config below, please. > > ``` > Alias /static "/local/mailman/web/static" > <Directory "/local/mailman/web/static"> > Require all granted > </Directory> > > ErrorLog ${APACHE_LOG_DIR}/mm3-error.log > CustomLog ${APACHE_LOG_DIR}/mm3-access.log combined > LogLevel info > > <IfModule mod_headers.c> > RequestHeader unset X-Forwarded-Proto > <If "%{HTTPS} =~ /on/"> > RequestHeader set X-Forwarded-Proto "https" > </If> > </IfModule> > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > ``` > > Did you say you're logging both Mailman Core and Mailman Web to > /var/log/mailman.log? Can you please separate them for clarity? > Is your settings.py the same as the one at > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > with the exception that you're using MySQL? > > -- > 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] >

2 years

Re: Creating users via RestAPI / User-Management - a bunch of questions

by Stephen J. Turnbull

Mark Sapiro writes: > On 6/20/25 06:39, Christian Schneider wrote: > > What I stumble upon is the RestAPI calls to create a "working" > > user (with the ability to login via WebUI). > > When I follow the manual (from the url above) I create a user > > (including password) that appears in the PostgreSQL database. If you mean you create a User with password via the REST API, this password is useless. It is not visible to the Django user management code, and there is no way for a user to log in to Mailman via the REST API -- the only one who can log in via REST is the superuser. > > Even when I (via WebUI) set the user as "approved" this user is > > not able to log in... I'm not sure how this works, exactly, but I think what you need to do via REST API is 1. Create the User. 2. Give it an email Address (this probably is automatic, I don't know if you can create a "bare" user without an email address at all). 3. (probably optional) Set that address as verified. Then through the Postorius interface you should be able to look up that user via the email address. That should create a Django user if one doesn't exist for that email address. I don't recall if Postorius allows you to set the user's password. You may have to go via the Django admin interface (the /admin location which is sibling to /mailman3 and /archives). I'm not sure how to find that user (I don't know what the user's account name in Django is, hopefully you can look up the user via the email). > > I assume this restriction is in accordance to the fact that there > > is not equivalent Django user. I don't think there can be a Postorius access to a Mailman user without a Django user. > > (There was a mail in the archive of the MM3 user group...stating > > that one has to use the Django RestAPI to create the appropriate > > user) > > The above is correct. The Mailman REST API only deals with Mailman > core. Mailman core knows nothing about Django. Right, if you want to do the whole thing in a script you'll have to access Django. > > How will a social account provider (like oidc) linkage (in > > Django) fit in this concept? > > Will oidc-accounts be copied to the Django's user database (or > > PostgreSQL db) or is it an on-the-fly check against the > > oidc-provider? (I assume second option) > > What are the status-flags (staff status/superuser status/active > > status) of the linked oidc-accounts? (Can I specify the status > > flags?) > > I don't offhand know the answers to that, but I think logging in > via a social account provider creates a Django user.. I can't speak for generic social accounts, but it definitely did that for a Shibboleth-based SSO setup. Just pass the login credentials provided by Shibboleth through to the social account stuff (verrrry carefully :-), and everything just works. Social auth gets the bare minimum information from the idP as far as I know (didn't look into it carefully). At least in my case all we got from Shibboleth was a display name (the personal name) and an email address (not even an verifiable auth token, they trusted their network that much). Users could set passwords but they didn't work (Django could only be accessed by users logged in to the network, and if you logged out, the request triggered by the redirect back to the login page would log you right back in again! Freaky...). > > A conceptual thought: > > When "user1" (with email user1(a)example.com) is known to django > > via oidc linkage and I create "user1" (also with email > > user1(a)example.com) via RestAPI calls (following the url > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > > do I have a "complete" user then? That depends on how the social auth is set up. Most likely the account is linked to the email, Django trusts that email if validated by the idP, and it will create a Django user to manage it if one doesn't already exist. If you are accessing Postorius or HyperKitty, that app will trust the email because it trusts Django, and it will create a Mailman user as Mark described if one doesn't already exist. (I don't think the Django and Mailman user-ids need to match, even.) I'm not sure what happens if you create the Mailman user and assign it that email address independently of creating the Django user. I think it should "just work" to log in via Django as long as the idP vouches that the email is authentic. Note that there's one glitch remaining -- I'm pretty sure[1] that if you have an existing Mailman user, and the email address is in the unconfirmed state in Mailman, you'll have to confirm it to subscribe to lists and probably to do any other work with that user logged in by that address. You can do that via "one-time key" email dance, or via the Mailman REST API though. (It may be possible to do that via the Django admin API as well, but obviously you can't do that with Postorius, or anybody could claim any address.) Short version: > > I mean a user who is able to login and who can be assigned to a > > list as admin (e.g.) (In this case I would not have to care > > about the Django user database... ;-)) > > If the user can log in to the web UI with an associated email > address, if that address is an admin of a list, the logged in user > can admin the list. Footnotes: [1] Actually, I'm not sure at all but you *should* have to confirm! -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

8 months, 3 weeks

Re: Error -- postorius Un-handled exception

by Stephen J. Turnbull

Mark writes: > After working my way through your suggestions with no joy I > discovered to my embarrassment that I hadn't created the > "mailman-hyperkitty.cfg" file. Once created all was well. We really should create a "mailman-lint" utility that checks for things like that. > This was of course after I had begun the installation process again > from scratch. My apologies for the waste of bandwidth and your > time. It's not a waste. There are reasons for having these random include files, but they do make configuration more complex, and these stumbles more likely. I did myself in on the postfix-pgsql patch: not using postmap, the postfix.cfg doesn't need a postmap_command setting right? Wrong! "Wasted" my own time there. :-D Anyway, ask here, somebody probably has done the same before. Maybe it will come up again and you can go, "when I had that error ...." ;-) > couple of issues that others might also stumble over: > > 1. Installing Xapian needed clang. It didn't like gcc I'm pretty sure that installing Xapian requires the C++ compiler (vendor and version) that was used for the packaged library. With the last year I've definitely compiled a Haystack package for Xapian using GCC, clang didn't work and neither did my existing GCC nor the most recent GCC, I had to look up how Ubuntu had compiled it to find the right version (9.3). > 3. For the user "mailman" to access the databases I needed to > change the owner to mailman (even though all privileges has been > granted) ... Can confirm. This was NOT necessary in November 2022; it is now. Probably a PostgreSQL > 13 thing, but since the change is sane and simple I didn't bother to investigate further. Steve

2 years, 1 month

Re: User management page [was: Changing subscription address]

by Abhilash Raj

> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Core implementation details, so I beinging this here from Mailman > Users @ mailman3.org. > > Abhilash Raj writes: > >> I have started working on designing a User management page[2] in >> Core which should make it easy for superuser to manage several >> things about a User, including the ones that don’t have an account >> in Postorius to manage their own. > > I don't understand this design with a "page in Core”. Typo :( Page in Postorius is what I meant to say. > I was thinking > about this kind of problem, and tentatively came to the conclusion > that any reference to something that can be resolved to a User should > generate a Django account for that User in Postorius or HyperKitty. Is that necessarily required? Every user in Django has a corresponding user in Core, but the converse isn’t true and I am not sure if that is even required. The purpose of a Django account is to manage my own email addresses and subscriptions. An admin can manage a Core User that does or doesn’t have a Django account. The only thing that changes is what they can do with that user. See below for my thoughts on the actions an admin would be able to perform. The high level design of that user management page is that it will provide a list of Users straight from Core. When you go to an individual User’s management page, You will be able to see: - Does the user have a Django account? - All Subscriptions for the User - All addresses of the User You will be able to perform following actions: - Add or remove a user’s address - Verify or un-verify an address - Set any address as primary for the user - Update display name of the user - Update address on any of the subscriptions If the User has a Django account, you also be able to: - Manage the User’s password *if* they are using password for login and not social auth. - Reset “social login” for the user? - View some of the RO info about the Django User model, like last login, superuser status or few other attributes that we feel is useful for admin in any situation. What I am on fence about: - Provide a full blown preferences menu to the admin for that user. This will also make the UI extremely complex to see and implement. > Authorization to use that account would still require authentication > via the usual email verification dance, or some level of admin > privilege. > > The thing is that emails that have not been added to a User are > unique. They will be the only Address attached to User created to > manage them until authenticated, and transitively the only address > attached to an automatically-created Django account (since those are > 1-1 with core Users if they exist AFAIK). In Core, when a new address (email1) comes in, a Mailman User(user1) is created for it. But, when you have an account in Django with a different email (email2) and a different Mailman user (user2) and you add a second email (email1) to your account and are able to prove ownership by verifying the address, Django will ask Core to add that second address (email1) to your Mailman user (user2) and absorb “user1”. This process is already implemented. However, if two Django accounts are created for “user1” and “user2” then situation becomes more tricky and currently we don’t have a way to resolve that short of delete one of the accounts and add the addresses to other account. > What's missing here is the ability to merge core Users and their > corresponding Django accounts. Doing this with nothing more than the > usual email verification dance is not *obviously* provably secure to > me, so we need to be careful, but I think it probably will turn out to > be as secure as you can get. It seems to me that User merging is the > most pressing problem of this kind. (At least, it affects me on a > couple of list hosts, as well as on GitHub and GitLab.) > >> [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 > > I'll take a look tomorrow or early next week. It is far from actually usable, so you can actually skip it for now ;-) I can announce it when it is in semi-usable state. -- thanks, Abhilash Raj (maxking)

4 years, 11 months

Re: Link to account

by Mark Sapiro

On 4/11/23 12:04, Lars Bjørndal wrote: > Thanks a lot. Maybe I've done a mistake, it doesn.t work. > > At the bottom of /etc/mailman3/settings.py I have: > > ROOT_URLCONF = 'urls' > > `cat /etc/mailman3/urls.py` > > [...] > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('lists/mailman3/', include('postorius.urls')), > path('lists/archives/', include('hyperkitty.urls')), > path('lists/', include('django_mailman3.urls')), > path('lists/accounts/', include('allauth.urls')), > path('lists/admin/', admin.site.urls), > ] > > In Apache config for the domain, I now have: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3" > ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives" > ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts" > ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin" > ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile" > </IfModule> > > Restarted mailmanweb, httpd and mailman3. > > If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser. > > So what's wrong, do you think? You followed https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… literally. The literal instructions where to access everything via URLs like https://mydomain.org/lists/.... If you were to replace `lists` with `mailman3` everywhere in the abpve, you would then access HyperKitty via a URL like https://list.punktskriftutvalget.no/mailman3/archives/ and Postorius via https://list.punktskriftutvalget.no/mailman3/mailman3/ If that's not what you want, it's more complicated and some things might not be possible. What exactly do you want for access to Postorius, HyperKitty, user accounts, user profiles and the Django admin UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: Installing mailman 3

by Rafael Mora

For testing purpose I turned back to false the DEBUG var and everything started working fine with HyperKitty I don't understand... this is the trace when I click Login from Postorius to HyperKitty [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 What should I check? El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

Re: Introducing Mailman Web project

by Abhilash Raj

On Mon, Mar 25, 2019, at 5:25 PM, Ralph Seichter wrote: > * Abhilash Raj: > > > For this reason, I decided to combine all the projects together into > > a Django project which can be easily installed and run: > > > > $ pip install mailman-web > > # Export Settings for commands to just work. > > $ export DJANGO_SETTINGS=mailman_web.settings > > $ django-admin migrate > > $ django-admin runserver > > I've tried things a bit differently so I can use the latest version from > GitLab, and Things Go Boom(TM): > > $ python3.7 -m venv venv > $ . venv/bin/activate > $ pip install -U pip setuptools > $ git clone https://gitlab.com/mailman/mailman-web.git > $ cd mailman-web/ > $ cp docs/mailman-web-example.toml mailman-web.toml > $ pip install . > $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate > Traceback (most recent call last): > [...] > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/views/user.py", line 34, in <module> > from postorius.models import List, MailmanUser > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/models.py", line 223, in <module> > class EmailTemplate(models.Model): > File > "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/django/db/models/base.py", line 95, in __new__ > "INSTALLED_APPS." % (module, name) > RuntimeError: Model class postorius.models.EmailTemplate doesn't > declare an explicit app_label > and isn't in an application in INSTALLED_APPS. > > Did I miss something? So, that's my fault ;-) The example configuration is actually not a working example, but only used for demonstrating how to write a TOML config. But I see that it actually should be a valid configuration, I'll open an issue and fix that. Can you instead remove mailman-web.toml and then again try: $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate This should mostly probably work :) -- thanks, Abhilash Raj (maxking)

6 years, 11 months

Re: How to subscribe members without sending unsubscribe message

by Stephen J. Turnbull

Flo via Mailman-users writes: > Thank you. I don't why I don't find these things in Postorius > easily? There's a common saying among user interface developers that "'intuitive' just means 'what you're used to'". It's not a "you" problem, it's that people have different notions of where such things "should be found" based on their unique experiences. In this case, the "mass subscription" tool has controls for all the things you might care about, including the welcome message. The "mass removal" tool does not, but once you've used "mass subscription", a control for the goodbye message is a reasonable expectation. I think we should add it: https://gitlab.com/mailman/postorius/-/issues/638 -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

Mailman-users search results for query "Postorius"