Search results for "Postorius" - Mailman-users

Re: ModuleNotFoundError: No module named 'mailman_web'

by Stephen J. Turnbull

gordon(a)dickens.com writes: > the mailman3 service always exits immediately after the command > "systemctl start mailman3". This is normal, The mailman command forks a separate daemon to manage all Mailman processes, then exits. > when I browse to the mailman3 web interface then I get the > following error: > > Something went wrong > Mailman REST API not available. Please start Mailman core. This is not normal. It could be that Mailman is running but Postorius and Mailman disagree about which port. What does "systemctl status mailman" say, in full? (As above, it will say Mailman has exited. What's important is if it says there are other errors detected.) What does "journalctl -S HH:MM -u mailman -x" say? HH:MM should be a minute or so before you most recently started mailman with systemctl. What does "ps -e -f -u mailman" say? There should be a dozen or so processes running. Does systemctl stop mailman /opt/mailman3/venv/bin/mailman start work better? The systemd commands are useless, but you can check that the runners are active with the ps command above. Failing all that, does rebooting help? Steve

1 year, 11 months

Re: Internal Server Error on installing Mailman 3 using PIP

by Mark Sapiro

On 10/28/20 11:04 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As you have suggested in my earlier issue, I have implemented > the latest stable version of mailman 3 through the URL > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > . > > But after the installation through the above URL, when I > tried running the command *elinks http://localhost:8000/postorius/lists > <http://localhost:8000/postorius/lists>* or *elinks > http://localhost:8000/admin <http://localhost:8000/admin>*, I got the error > as *Internal Server Error*. > > I don't find any specific log in mailman.log or in > mailmansuite.log. > > Is there any way to solve this issue ? > You need to hire a consultant who understands Mailman 3 installation to help you with this. The help you need is beyond the scope of this list. I am not available as a paid consultant. I do not do that work. See <https://wiki.list.org/x/4489296> for a partial list of people who do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

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

4 years, 9 months

Re: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

Re: Message Sent to A Re-Created List Results In Error

by Abhilash Raj

On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us wrote: > I created a list in the Postorius interface, used it, and then deleted it. A > week or so later, I re-created the list, and things were fine thru the > creation and subscription process. But when I sent a message to the list, a > "550 user unknown" error was sent back. Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs. > > > I tried to determine if this is a known issue by searching the issues in > Gitlab; but didn't find anything. But wanted to ask if this was a known > issue or not? I personally don't remember seeing such an issue, but Mark or others might know. > > > > Thanks. > > > > - Matt Alberti > > _______________________________________________ > 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)

4 years, 10 months

Re: Postorius claims 2 messages held when there are none - out of sync

by Ken Alker

--On Monday, June 26, 2023 2:32 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 11:53 AM, Ken Alker wrote: >> >> Is the var/messages hierarchy also where all the archived emails are >> stored for future viewing via the web interface? > > > No. They are stored in the hyperkitty_email and hyperkitty_attachment > tables in the database. What else is stored in /var/messages, if not archives? I see 4711 messages in that directory (which I presume would be as many messages are in the archive database). If there is a write-up on this, feel free to point me to it. I found <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode…> but this isn't really answering my question. >>> Also, there is a long thread at >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thr >>> ea d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be >>> relevant. >> >> I have never used the mailman shell before, but based on the referenced >> thread I learned to do this (note that the thread also taught me how to >> rewrite it to narrow down to just the list with issues so I didn't >> delete held messages in other lists, if my case): >> >> for verification: >> >> venv) mailman@speedy:~/web/logs$ mailman shell -l >> sbarc-list(a)lists.netlojix.com >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list >> >>> requests = IListRequests(m) >> >>> first = True >> >>> for request in requests.held_requests: >> ... key, data = requests.get_request(request.id) >> ... if first: >> ... first = False >> ... print(m.list_id) >> ... print (f"""\ >> ... Sender: {data['_mod_sender']} >> ... Subject: {data['_mod_subject']} >> ... Date: {data['_mod_hold_date']} >> ... Reason: {data['_mod_reason']} >> ... """) >> ... > >> and then to delete the two messages: >> >> (venv) mailman@speedy:~/web/logs$ mailman shell -l >> sbarc-list(a)lists.netlojix.com >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list >> >>> requests = IListRequests(m) >> >>> first = True >> >>> for request in requests.held_requests: >> ... key, data = requests.get_request(request.id) >> ... if first: >> ... first = False >> ... print(m.list_id) >> ... print(f'request id: {request.id}, deleting') >> ... requests.delete_request(request.id) >> ... >> sbarc-list.lists.netlojix.com >> request id: 27, deleting >> request id: 28, deleting >> >>> >> >> The result of this, however, was that the web interface still claimed I >> had two held messages. I wasn't sure if there was some cron-type >> "sweeper" process I had to wait to auto-run or if I had to manually do >> something to create an update. I then realized that the sample script >> had a ' >>> commit ()" ' at the end, which I'd missed. So, I >> re-entered the script (but it didn't spit out that it deleted anything >> this time) and got an error when I did the commit. > > Was this in the same `mailman shell` interaction or a new one? What was > the error? I am pretty sure I started over entirely (ie. exited via ctrl-D and restarted). It was a syntax error, but in reviewing, I see now that I'd copied the example exactly, and I included the trailing quote mark. After some experimentation and reading, I see now that that should not have been there. >> So, I figured the messages HAD >> been delete and the commit wasn't really necessary. When I went back >> to the web interface, the number of held messages was at 0 and I no >> longer get the original error when clicking on "Held messages", so my >> issue is solved. But this does leave me with some educational questions: >> >> 1) Did I affect something somehow with my "commit", or was there a job >> that cleaned things up (if so, what job)? > > > I'm not sure of the sequence of events, but I think you probably looked > in Postorius before you quit `mailman shell` and then you quit `mailman > shell` with ctrl-D which did an implicit commit. I didn't think so, but I'll certainly buy that. So, I'm assuming by this you are implying that there is no helper function that needed to run and the number of held messages should have dropped to zero immediately upon a refresh of the web page? >> 2) Is the "commit" even necessary (I saw it in someone else's script in >> the thread)? > > It is necessary to explicitly commit() or quit with ctrl-D to actually > update the database. Got it. Thanks. That explains why I didn't see any deletions when I re-ran the script the second time (after likely exiting with ctrl-D first). >> 3) Is there a way to save a script and then execute it via shell rather >> than typing it in every time (it appears from the examples that people >> are typing them in every time, which is super tedious; I didn't paste >> for fear of doing something damaging, but maybe that would work)? > > > Yes, you can save a script in the bin/ directory in your venv and run it > with `mailman shell -r`. See `mailman shell --details`. > > >> 4) Are the request.id's of the messages dynamic/changing, or are they >> fixed for life? I thought I'd delete based on exact request.id without >> looping but I was afraid maybe they were changing over time and that >> this wouldn't be a good idea. Might be nice to know for the future. > > The request.id is constant for that request object. The request object is > fixed for a specific held message request. I.e., a specific held > message's request object and its request.id and other attributes are > fixed until that request is handled. So if I run the script, exist the shell, then come back in again, I can't rely on the request.id being the same? I'd need to re-run the script and get a new request.id?

2 years, 3 months

Message-Footer after migrating to Mailman3

by christopher.claus＠tgcamberg1848.de

Hello together, I migrated a number of lists from mailman2 to mailman3 using the import functionality. Everthing works fine and the new lists are in use. Currently I´m using the maxking-docker-images with postorius: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.5 (default, Feb 19 2021, 09:27:16) [GCC 9.3.0] After this migration I started a refactoring with the list-styles specially with message-footers. Already the old lists in mailman2 were confused in some configuration details an I was clear to import this "misconfiguration" and clean it up afterwards. But this was much more difficult than expected: some lists are using a footer (from the mailman2-config) and there is no record in the template-section visible. Further I found no configuration item which points to this "old" footer. I found the file [code] /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt [/code] which includes the old footer: [code] _______________________________________________ $display_name Mailingliste -- $listname Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} [/code] but no configuration item to disable this behaviour. I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used - in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. In the logfiles I found an error and a warning: [code] ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer [/code] Obviously I have a problem with the hostname. I set [code] POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 [/code] where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost [code] wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… [/code] will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. Best regards, chrclaus

4 years, 5 months

Re: Enforcing SSO and subscription options

by Stephen J. Turnbull

via Mailman-users writes: > Thank you for the reply. Ultimately, I ended up digging deeper > into the allauth docs, per your suggestion, and I went a little bit > further with the "SOCIALACCOUNT_ONLY" option. It turns out that > the errors I were seeing were related to the sign up button > referencing a view that didn't exist. You have to do this, I suspect (I am unsure that removing the reference from urls.py would protect you from A Sufficiently Smart Miscreant, and if it did you'd still get the error, so why not remmove the code and remove all doubt!) > I solved this in an admittedly ugly way, by removing the sign up > button from the postorius and hyperkitty templates. You do not have to do it this way. There is a search path for templates, and you can remove those buttons from copies stored in a directory earlier in the path. I use /etc/mailman3/templates/..., but they can go anywhere convenient that won't be overwritten by an upgrade. The worst that could happen is the copies get removed, and then you get the error, which you fix.

8 months

Re: username

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > I would like to create/pre-populate all the postorius usernames for > our list owners/list moderators using their university net > username. Is there a way to do that? You can create Django users via the Django admin interface (typically the ".../admin" sibling to the ".../postorius" and ".../hyperkitty" URLs. It shouldn't be too hard to automate this, but I don't know of such a script. Django channels might be a better place to ask for that. But after that things may get complicated. Are you migrating from an existing list server and want to link the new users to existing lists? I think this can be done as long as you link the appropriate owner addresses to each user. Hopefully those are algorithmically related to the network login (ie, address = username@domain). Also, if by "network login" you mean a SSO protocol such as SAML, you can populate users directly from a service provider such as Shibboleth. There's a well-known protocol called REMOTE_USER that Django participates in. There are a couple of speed bumps you may run into, but it's hard to be specific without more information on your particular situation. Steve

2 years, 4 months

Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Tuesday, March 15, 2022 10:29 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/22 11:16, Quanah Gibson-Mount wrote: >> Hello, >> >> We have a constant issue with confirmation emails for subscribers >> getting lost and then the subscriber contacting us because their posts >> to the list never show up. Is there a way I can, as an administrator, >> do the confirmation on their behalf or in some other way promote them to >> being a member from non-member? > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/MJOOH23W6EKZO7GI5HRDKB4S733JEEVG/ > > If they don't have an outstanding subscription waiting user confirmation, > you can just mass subscribe them. > > If they do and your Postorius and Mailman core is reasonably up to date, > you can find the pending request at Subscription requests -> Pending > Confirmation, delete it and then mass subscribe them. Hi Mark, Thanks for the response. Unfortunately I'm currently stuck with the junk shipped by Debian. Yet another reason to move to a standalone install and avoid their broken packages. Regards, Quanah

3 years, 7 months

Mailman-users search results for query "Postorius"