Search results for "Postorius" - Mailman-users

Re: Issue with Held Messages

by Mark Sapiro

On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: > > No matter what action I set for member posts (Hold for moderator, > Reject) they are always delivered. I don't know why this would be. Perhaps the member's moderation is set to Accept immediately - you can see this on ther member's options page in Postorius when logged in as a list owner. When the message is delivered, what are the X-Mailman-Rule-Hits: and X-Mailman-Rule-Misses: headers? > When I tried from a non-member email address, the message got held but > when I try to see it I get a Server Error (500) page. The log files shows: > > ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server > Error: /mailman3/lists/test.mydomain.com/held_messages > Traceback (most recent call last): ... > File > "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", > line 443, in held > moderation_reasons=entry['moderation_reasons'], > KeyError: u'moderation_reasons' This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 11 months

Unable to download attachments from HyperKitty

by Derek Lambert

I’m having an issue downloading attachments from HyperKitty. The download begins as expected, but never progresses. Eventually it times out. I imagine the browser is expecting data matching the content-length header, but never receives it. Inspecting the contents of the download file reveals (address varies): <memory at 0x7f148fcb9588> I’ve been able to work around the issue with the following patch: --- env/lib/python3.7/site-packages/hyperkitty/models/email.py.orig 2018-12-06 21:38:39.544448735 +0000 +++ env/lib/python3.7/site-packages/hyperkitty/models/email.py 2018-12-06 23:01:39.923239421 +0000 @@ -309,7 +309,7 @@ def get_content(self): folder = self._get_folder() if folder is None: - return self.content + return self.content.tobytes() filepath = os.path.join(folder, str(self.counter)) if not os.path.exists(filepath): logger.error("Could not find local attachment %s for email %s", I haven't been able to replicate the issue with the HyperKitty tests, presumably the issue is somewhere in the Django <-> uwsgi <-> nginx stack. My configs are based on mailman-suite and maxking/docker-mailman. I've tried stripping out all the performance tweaks from my uwsgi and nginx configs, but no change. Versions: HyperKitty 1.2.1 Postorius 1.2.3 Django 2.1.7 nginx 1.14.1 uwsgi 2.0.18 Python 3.7.2 Has anyone come across this before? Derek Lambert

7 years, 5 months

Re: New Mailman Releases

by Abhilash Raj

On 10/26/22 12:32, Odhiambo Washington wrote: > > > On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in > <mailto:maxking@asynchronous.in>> wrote: > > Hi, > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > All the releases are published to PyPI and you can find links to all > the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > <https://docs.mailman3.org/en/latest/> > > A full list of changelogs are available below: > > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> > [2]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> > -- Something weird is going on with the page missing the bullets. > [3]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6> > [4]: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… <https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien…> > [5]: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst> > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > recommended if you are doing a new install for longest support. 3.10 is > supported for Django apps, but Mailman Core is missing that due to one > of the core dependencies not support 3.10 yet (aiosmtpd). > > > > Hello @Abhilash Raj <mailto:maxking@asynchronous.in> > > Thank you and the whole MM3 team for all the free work you do to make us > have mailing lists :) > > I have a question regarding the Python version. > I have a very recent installation of MM3, via the Virtual Environment > method, running smoothly - so far. > The Python version that got installed is 3.10.6 > > wash@lists:~$ sudo su - mailman > (venv) mailman@lists:~$ which python > /opt/mailman/mm/venv/bin/python > (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V > Python 3.10.6 > (venv) mailman@lists:~$ mailma > mailmail3 mailman > (venv) mailman@lists:~$ mailman --version > GNU Mailman 3.3.5 (Tom Sawyer) > (venv) mailman@lists:~$ > > 1. What does the incompatibility with Python-3.10 portend for my setup > and anyone else with Python-3.10? The bug in aiosmtpd is a bit weird and has to do with how the test cases in aiosmtpd and Python 3.10 changes interact with SSL. For the intents and purposes of Mailman, we don't use SSL for the communication between MTA and aiosmtpd, so there _shouldn't_ be any issuer with your setup. Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a Python venv with 3.10, but that depends on which version of pip you are using since the newer versions have better support for such management. > 2. Is it possible to downgrade the Python in a Venv down to 3.9 without > breaking the installation? You can keep the current installation running and create a 2nd installation by simply creating a 2nd venv with 3.9. Something like, `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and when you are done and ready to switch, you can update all the paths in various places to use update 'venv-3.9' instead of 'venv'. In case you encounter any issues, you can always revert back to older 'venv' in the paths wherever the are needed and bring back the old install. Venvs are good for multiple installs so you can switch back and forth pretty easily. > > And finally, is there documentation/procedure to upgrade a VENV install > in this case? You don't want to upgrade venv is what i've heard, you should always create a new one if you are bumping python versions. If you are just upgrading packages in the existing venv, then you can follow: https://docs.mailman3.org/en/latest/upgrade-3.2.html -- thanks, Abhilash Raj (maxking)

3 years, 9 months

Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 13:11 -0800, Mark Sapiro wrote: > On 2/19/22 12:41 PM, William Oliver wrote: > > > > So, I can just kill the listname user altogether? > > > As far as Mailman is concerned, Yes. > > No joy. I deleted the list as well, and recreated it with the same name -- and the error repeated. I created a list with a different name, and there's no error. I must have really screwed something up in dovecot. Happily, this is a small list, so I'll just migrate everybody to the newly named "listname2". So.. as an aside, it was a bit of a hassle to copy and paste all the usernames from the "Users" list in Postorius to the "Mass subscribe." The only way I could see to do it was copy and paste them one at a time. That worked OK for me, since it's a small list, but that made me wonder if there was a way to select, say, 100 users out of Users and subscribe them all to a list. billo

4 years, 5 months

Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 9:21 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/23 08:11, Quanah Gibson-Mount wrote: >> Hi, >> >> We frequently end up with users who never receive their email to confirm >> their account, leaving them in a netherworld where they cannot become >> list members. If I try to subscribe them via the mass subscribe >> option, it says I can't because their subscription is pending. If I >> go to subscription requests, it says there are 0. If I go to >> "non-members" in the UI, I can find them, but I don't see an option to >> convert them to members. > > > Subscription requests says 0 because it only counts those pending > moderator approval, but if you pull down the menu and select Pending > Confirmation, it should show the request and enable you to delete it, and > then mass subscribe will work. The only elements that have a drop down menu are: Users Mass operations There is no "Pending Confirmation" with either of these. Note: Postorius Version 1.2.4 --Quanah

3 years, 2 months

Re: Domain Resolving Issue

by Abhilash Raj

On Thu, Mar 7, 2019, at 11:36 AM, brian(a)emwd.com wrote: > I am running a Mailman 3 server with about 5 list domains configured on > it. Most of them resolve quickly both to Postorius and HyperKitty. > However there is one domain that resolves very slowly. Once it does, > access to other pages/tasks go quickly. If you don't do anything with > that domain in the browser after about 5 minutes, it takes its time > again to resolve. What could be causing this? The webserver is Nginx. > Not sure if this is a Mailman 3 issue or not. It is unlikely that this has anything to do with Mailman. The faster access after first time is probably due to local caching of DNS entries. Try checking your DNS servers for the domains and how long they take to respond. Your browser is probably just waiting more for DNS response. Mailman should be responding with similar lag for all the domains. > > 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)

7 years, 5 months

Re: API privileges question for mailman3

by Mark Sapiro

On 10/14/21 12:41 PM, bob B wrote: > In mailman3 documentation it says: > "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost." > > So I just wanted to confirm there is no way to limit API access? For example I have a group that wants to use API access to mange their mail lists, but from what I can gather, if I give them access to the API they would have access to ALL the mail lists etc.. I would suspect this is even true if I give them their own domain? > > Is there anyway to limit access via the API to certain lists etc..... No, there isn't. If Postorius is not suitable for some reason, you would need to implement an application on the host to provide a user interface to the API with appropriate authentication and controls. There are some ideas but no actual code at <https://gitlab.com/mailman/lemme>. -- 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: Weird startup problem after upgrade

by Odhiambo Washington

On Fri, Dec 2, 2022 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/2/22 08:21, Odhiambo Washington wrote: > > I am facing an odd situation in which MM3 doesn't start successfully on > > reboot, but I can start it manually. > > This is a venv install. > > This started after I did an upgrade (pip install --upgrade mailman > > postorius hyperkitty mailman-hyperkitty) followed by the requisite > > collectstatic|compress|compilemessages|migrate > > post-update commands. > > > Was the venv activated when you ran pip? > Yes. > > You should also include django-mailman3 and mailmanclient in the > packages to be upgraded although they are dependencies and "should" > upgrade anyway. > I did not include them in the list of packages to be upgraded because I did not explicitly install them when I installed my server. In BC's HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> which is what my MM3 server is based, they were never part of the modules (app?) installed explicitly. > Also, at least one person has noted that --force-reinstall was required > to get all dependencies upgraded > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > I can try this as well and report back. > > Secondly, it appears that the upgrade did NOT change the versions for the > > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > > the latest. > > > What does `pip freeze` in the venv show for versions? > Here is the listing: https://pastebin.ubuntu.com/p/tMGDxjKwJ8/ > > > Thanks in advance for any insights into what could be causing this. > > > How do you start it manually? `mailman start` or `systemctl start > mailman3`? systemctl start mailman3 > What's the content of /etc/systemd/system/mailman3.service? > root@lists:/home/wash# cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mysql.service postgresql.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid User=mailman Group=mailman ExecStart=/opt/mailman/mm/bin/mailman start ExecReload=/opt/mailman/mm/bin/mailman restart ExecStop=/opt/mailman/mm/bin/mailman stop [Install] WantedBy=multi-user.target A special note that before I did this upgrade, the startup wasn't an issue. I can actually go back to where I was, because I have complete backup of my venv before the update, but it would be great to figure out why things are the way they are now. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 8 months

Re: Multiple domain problem

by Lars Bjørndal

On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > I have lists on two domains, example1.com and example2.com. The mail > > interface works perfectly. However, connecting a browser to > > example1.com, I get the title List index - example1.com, and the web > > interface seems to work fine. > > > > If I connect to example2.com, the title is example2.com, without the > > preceding List index. And the body says Page not found. > > > What's in the browser's address bar for that page? It's https://example2.com/mailman3/lists/ For the domain that works, it is https://example1.com/mailman3/lists/ Please note that I've changed mailman to mailman3 for the complete installation. > What's in Postorius domains view? I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > What's in the Django admin sites view. Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Thanks Lars

3 years, 5 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?

3 years, 1 month

Mailman-users search results for query "Postorius"