Search results for "Postorius" - Mailman-users

HyperKitty failure

by horvath.arpad.szfvar＠gmail.com

Hi, I try to connect mailman3 to hyperkitty, but there is no success so far. You can see the details below. How can I solve the problem? As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on the same server, so I guess localhost won't work. In mailman-hyperkitty.cfg there is a line: base_url: http://lists.xxx.hu/hyperkitty/ /etc/mailman3/mailman-web.py includes "*" in ALLOWED_HOSTS I have an error message in /var/log/mailman3/mailman.log Dec 30 21:41:23 2021 (126976) HyperKitty failure on http://lists.xxx.hu/hyperkitty/api/mailman/archive: (405) Dec 30 21:41:23 2021 (126976) Exception in the HyperKitty archiver: Dec 30 21:41:23 2021 (126976) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError In /var/log/mailman3/web/mailman-web.log WARNING 2021-12-30 20:41:23,816 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive [pid: 127032|app: 0|req: 101/101] 109.230.236.204 () {38 vars in 592 bytes} [Thu Dec 30 20:41:23 2021] GET /hyperkitty/api/mailman/archive?key=lHzJB%2FzfSWUrbPKZ84JNSlLXHVyCDt8T => generated 0 bytes in 1 msecs (HTTP/1.1 405) 6 headers in 189 bytes (1 switches on core 0) WARNING 2021-12-30 20:41:23,854 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive On Debian 11, I have these packages ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty Thanks, Arpad

4 years, 2 months

Re: Can't subscribe on new site/domain

by Flo

On 10/9/25 19:19, Mark Sapiro wrote: > On 10/9/25 5:02 AM, Flo via Mailman-users wrote: >> Hi, >> >> I added a new site in Django: lists.example.com >> >> Usually I click on 'view site' and I can add a Domain in Postorios. In >> this case I get an error message and I need to add a Domain in Django. >> Then I can go to 'view site'. >> >> I can create a mailing list there. However when I send an email to be >> subscribed, I get the following in mailman.log (and nothing else >> happens): >> >> >> Oct 09 13:46:24 2025 (110452) deque: do_confirm_verify >> Traceback (most recent call last): > ... >> File "/usr/lib/python3/dist-packages/mailman/model/domain.py", line >> 177, in __getitem__ >> raise KeyError(mail_host) >> KeyError: 'lists.example.com' > > It appears you don't have a domain in Mailman core with mail_host = > 'lists.example.com'. > > Do you see one in Postorius' domains view? If not, perhaps you need to > add it. > I can see it in Postorius. I have created the a simialar site before and deleted the site and then again created this one. Maybe the database is messed up? I have deleted site - group - list now. And created the site again. If I go to 'view site' I see all mailing lists on the server and not only from this site/domain. This is the first thing where it shows irregularities. Flo

4 months, 3 weeks

Re: django fake users

by roberto

Hello, yes we talk about django users who are not subscribing to any list only to the django user managment. Automatically removing this users like described above with a cron job is a good idea, but i would more like to avoid this users. Obvious this users are created by a bot, would it not be helpfully to use any kind of captcha? Am 17.01.21 um 12:24 schrieb Andrew Hodgson: > Stephen J. Turnbull wrote: > >> r.woithe(a)callassoftware.com writes: >>> is there a opportunity to avoid django fake users? >>> Because of it is not stopping, further and further fake users are > subscribing. >> Require moderator approval for subscribing. > I don't think this would help the issue. What I am seeing here is users signing up through Postorius using the sign up option which then creates an account in Django (but not Mailman). Yesterday alone I had over 700 of these accounts created. I don't know whether they pass email confirmation or not (I don't see this in Django admin), however they don't get added as users in Mailman and they don't attempt to subscribe to any list. > >> It may be possible to do something automatic, but you need to explain how you know these users are "fake", and it has to be something that can easily be detected with a few lines of Python. If it becomes at all complex, it will almost surely make trouble for "real" subscribers. > I agree, this is why I am taking the route of running a regular Cron job to delete the users as explained earlier. > > Andrew.

5 years, 1 month

Re: 3rd Party Account is not working

by Stephen J. Turnbull

kwp.klein(a)gmail.com writes: > Here is my /mailamn/config/mailman-web/settings_local.py. I get an error message > > curl http://172.19.199.3:8000/postorius/lists/ > curl: (7) Failed connect to 172.19.199.3:8000; No route to host > Please comment out all the lines that are not necessary. This is not a Mailman problem; curl can't connect to the Mailman host because there's no way to get there from here. We may not be the best place to ask about network problems. That said, we'll do what we can. We need to know what your network configuration is. I assume that 172.19.199.1 and 172.19.199.3 are on the same subnet, and that 172.19.199.3 is the host for Postorius. Where is Mailman core? Do you have HyperKitty installed? On what host? I assume that 172.19.199.1 is the host with the MTA for this network. I don't know if this is related to your original problem "Server error An error occurred while processing your request." However, if the network is not working properly Mailman is going to be very unhappy. > MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = '172.19.199.1' > EMAIL_PORT = 25 > USE_SSL = False > > INSTALLED_APPS = ( [...] > 'allauth', > 'allauth.account', > 'allauth.socialaccount', I think you may want to disable allauth.socialaccount as well. > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > #'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > #'allauth.socialaccount.providers.google', > ) > _______________________________________________ > 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/ > >

5 years

Re: Hyperkitty import from mailman2

by Marvin Gülker

Just a suggestion -- if your list didn't have any e-mails in the last month, the front page will show it as inactive. Dig into the archive links on the left side to actually see your e-mails. I've been bitten by that behavior as well. The front page simply doesn't show e-mails older than a month. Look here: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… No emails on the front page. Now go here: https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch… Well there. Greetings Marvin Am 23. December 2017 um 01:05 Uhr +0200 schrieb Sten Aus <sten.aus(a)eenet.ee>: > Hi > > Thank you Mark and Simon for your input! > > I can see imported list from Hyperkitty GUI, but it's inactive. > I can confirm that I can see those emails from command line (python shell > shows Email Objects). > > Import shows everything is OK: > > # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v > 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > Only emails after 2010-01-01 00:00:00+02:00 will be imported > Importing from mbox file /tmp/test.mbox to test(a)list.domain.com > /--some 22 emails being imported here --/ > 22 emails read > 22 email added to the database > 22 emails are stored into the database > Computing thread structure > Synchronizing properties with Mailman > Warming up cache > The full-text search index will be updated every minute. Run the 'manage.py > runjob update_index' command to update it now. > > # python2 manage.py update_index --settings settings > Indexing 50 emails > NB! Only 6 of them are archived from new list (which has been created from > Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to > different lists). > > > I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the > same django application. > Also tested with running server directly and then connecting to a port 8000, > but I guess it does not matter, because both of them are using Python > script. > > I have not yet managed to set up cron tasks, as this is relatively new > installation, but I have ran them manually. Also, I have done update_index > (runjob update_index and manage.py update_index, both ways). > > > SQLite database shows emails, for example there's a thread > FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django > error: No Thread matches the given query. > > > As Postorius and Hyperkitty are in the same Django, they share sqlite > database (mailman/web/database.db). Mailman has it's own database in > mailman/var/data/mailman.db. > > > Happy holidays > Sten > > > On 22/12/2017 21:09, Simon Hanna wrote: > > On 12/22/2017 03:39 PM, Sten Aus wrote: > > > Hi > > > > > > I have installed mailman3 - it looks very great! > > > > > > Now I wanted to try import from mailman2 mbox, so i did: > > > > > > python2 manage.py hyperkitty_import --settings settings > > > --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com > > > /tmp/test.mbox > > > > > > It shows that it have sucessfully imported all emails and I can see > > > them from database (sqlite3), but I cannot see them from GUI > > > (hyperkitty). Only thing I can see is this inactive "test" list. > > > > > How did you try to access them using Hyperkitty? Can you try doing that > > while logged in as a django superuser? Could you try using a permalink > > for a message? If you can access the files from the database you should > > be able to construct the urls using the list name and the > > message_id_hash of a message. You should try this using DEBUG=True in > > the settings.py. The URL would be similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… > > > > > > Another option would be to check if you can access the data using a > > python shell. > > > > `python manage.py shell` to open a python shell preconfigured for > > Hyperkitty and then input the following two lines: > > > > from hyperkitty.models.email import Email > > Email.objects.all() > > > > > > This should print out all the messages that are stored in the database. > > (You can limit them by appending "[10:]", or any other python slice) > > > > What do you see in the UI? Is it somewhat similar to > > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 2 months

Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by ugniusviln＠gmail.com

I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about: 1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run. I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size. $ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add. Except uwsgi.ini, I have only 2 configuration files in mailman-suite project directory: settings.py and mailman.cfg So I do not understand what did I configured badly. 2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup.

6 years, 6 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Allan Hansen

They need to resubscribe to each list they want the new address to be used for. Subscriptions involves permissions from the moderators. It’s not a simple process, especially if you are on many lists. Yours, Allan Hansen hansen(a)rc.org > On Feb 12, 2021, at 8:47 , Andreas Barth <aba(a)ayous.org> wrote: > > * Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: >> hansen(a)rc.org writes: >>> b. The ability of members to change their addresses for all lists >>> they are subscribed to. >> >> What exactly do you want here? I can think of a number of ways to >> implement that, depending on whether the old address is to be >> deactivated from the lists, unsubscribed from the lists, or deleted >> from the Mailman and/or Postorius Users. There may be other >> variables to consider, as well; I haven't thought about this. AFAICS >> this is not a trivial feature, and I'd really like to hear from people >> who want "something like" this about exactly what they want and their >> use cases. Or we'll release an insufficiently designed feature that >> causes somebody hundreds of problems.... > > I thought user could do that if they have an web account, and multiple > mail addresses are associated with the account? Or does my memory > serve me wrong there? > > > Andi > _______________________________________________ > 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/

5 years

Re: Mailman 'requests' API call timeout when there are a number of pending members

by Abhilash Raj

On Thu, Jan 14, 2021, at 6:52 PM, Alan So wrote: > We are currently testing latest mailman suite and notice that the > requests API call will timeout if there are a number of pending > requests. > > Since the latest Postorious allow unchecking Pre confirm and Pre > approved during mass subscribe, our support staff tried to add large > number of email addresses to the list. We then found that we cannot > click into the list from the web UI to administer it and an error > message showing that "Mailman REST API not available. Please start > Mailman core." Further checked that the requests API call failed to > complete when we click the list on the web interface. > > Looks like the UI should not try to load all the pending members just > for the sake of showing the number of pending requests. Of course in > normal situations, there should not be that many pending requests. This issue has been partially mitigated by [1] making the list's index page better. Also, subscriptions pending confirmation from User don't affect the speed of the page showing subscriptions pending user confirmation. However, there is more to be done by adding support for pagination, which is reported here [2]. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/559 [2]: https://gitlab.com/mailman/postorius/-/issues/420 > _______________________________________________ > 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: New domain cannot set set host

by Mark Sapiro

On 11/28/24 10:19 AM, Alain D D Williams wrote: > On Wed, Nov 27, 2024 at 12:42:41PM -0800, Mark Sapiro wrote: >> On 11/27/24 12:18 PM, Alain D D Williams wrote: >>> >>> But it is not in table mailman3web.django_site >>> >>> Please how do I do this ? >> >> Add the domain as a site in the Django web admin UI. > > I did not see this y/day and created the entry in table django_site using SQL. > This might be the cause of the other problems that we have been talking about. It's not likely that this is the cause. > I must admit to finding django daunting -- something that I know nothing about; > I ran "mailman-web --help" and was non the wiser. > > I found the following which did not help either: > > https://docs.mailman3.org/en/latest/django-primer.html Yes, Django can be daunting. It is certainly possible to implement alternatives to Postorius and HyperKitty that use some lighter weight, non-Django framework, and it was always our hope that someone would do this and contribute it. A few years ago, EMWD did implement alternatives using PHP, but at least in part due to the untimely death of EMWD's principal, those remain proprietary. That said, if you follow the installation doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you shouldn't need much Django knowledge beyond that and https://docs.mailman3.org/en/latest/django-primer.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman

by Abhilash Raj

On Wed, Nov 8, 2017, at 04:38 AM, Simon Hanna wrote: > On 11/08/2017 12:03 AM, Abhilash Raj wrote: > > New images are available on quay.io and, moving forward, the rest of > > the image builds will also be moved to Quay[4][5]. > Since docker deployment is currently the recommended install, with > manual installs using the master branches for "experts" I wonder why you > are using Quay. For those who don't know about it, Quay is a container registry offering from CoreOS. The main reason why I chose to move to Quay, from DockerHub that we are currently using, is security. Some parts of both Dockerhub and Quay are open source and some aren't. There isn't a very clear boundary/transparency in what technologies they use. Both are free to use for open source projects. However, Quay provides an improved security model with RBAC to push images from build server, without having to put my account password on the build server. It also includes a (open source) security scanner for images, which looks for vulnerabilities in packages included in the image so that I can re-build them if one is found. There are open source registries available, most popular of which I know is provided by Gitlab. However, I feel Quay is better for my current workflow, which involves lots of bash scripts for building and testing images on public CI system for rolling releases. Given more free cycles, I do intend to have a better build pipeline and possibly use Gitlab's own registry to distribute images. > It looks like it's a non-free system. Why use Quay but refuse to use a > non-free translation system like transifex? > > These images are built using git-heads *only* if they are passing our > > test suite and are re-generated weekly. You should be aware that while > > all these components are tested with their individual test suites, their > > combination might sometimes not be stable. This will get you > > updates/bug-fixes much faster :) > This contradicts what you said in my merge request for Postorius > https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 > > You either use released versions, or make sure that the master branches > are always compatible. You can't have both with the current development > model. Not exactly, I still believe all our git-heads should be compatible with released (i.e. stable) versions of dependencies, regardless of the fact that we maintain those dependencies. Also, there is at least one test per-project which tests with git-heads of dependencies we maintain, so that we know if we make any incompatible changes. I am not sure what in the current development model prevents us to do both? The story for container images is different than testing with git-heads. We need better integration testing for the entire suite to be stable in conjunction, rather than independently. In fact, containers might be the perfect way to actually do the integration testing. > > If this campaign succeeds, here is a road map of what I intend to get > > done: > Sounds great, what is the limit where the campaign succeeds? What will > happen to the funds if it doesn't? > > - Add Admin Dashboard project from GSoC 2014 (maybe?) > Didn't find anything using google. What is that project about? https://www.google-melange.com/archive/gsoc/2015/orgs/gnu_mailman/projects/… > > - Add better testing of container images and provide deployment > > instructions for Kubernetes & Docker Swarm > To be honest, I don't think we should all in on containers. > Yes they are nice, but I guess most people would prefer distro packages. > Even if people want containers, I for instance would prefer plain > systemd-nspawn Like Barry mentioned, it doesn't have to be all-or-nothing. There is work being done on distro packaging for Debian and I am ready to help others trying to do the same for other distros! Systemd-nspawn isn't really a production grade tool to use containers. I am not sure about how much it adheres to the OCI specs, but if it does, it should not matter which deployment tool you are using with images. I wouldn't mind adding configurations for systemd-nspawn in the documentation, contributions are most welcome. > > - Improve the container images to work with new micro-services > > architecture, > > to achieve scaling and redundancy in services. > The current bottleneck is the rest api from core. IMO bulk actions, > filtering and sorting should be added there before trying to have > multiple postorius/hyperkitty instances serving the same core... I didn't say they will be served from the same core ;-) Yes, the Core's API can be further improved to be more efficient. But that doesn't prevent us from scaling. I understand there are issues around multiple instances of containers, but I have ideas to get around most of them. -- Abhilash Raj maxking(a)asynchronous.in

8 years, 3 months

Mailman-users search results for query "Postorius"