I would suggest that there is something very broken here: there seems to be a problem with communication between the email system (mailman core…?) and HyperKitty.
On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty . I don’t know if other list members received it in their email inboxes or not.
Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives . However, I never received an email copy of his message from the list.
So, what’s going on?
What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well.
> On 2017.11.21, at 06:31 , Cameron Smith <ccsmith(a)mail2.cetsi.com> wrote:
> I, too, have been struggling with messages not showing up , although the conditions are somewhat different.
> What I have found works to make all of the messages appear is the following, which you might try:
> sudo docker-compose exec mailman-web ./manage.py runjobs yearly
>  https://firstname.lastname@example.org/thread/…
>> On 2017.11.21, at 04:41 , Thor Atle Rustad <thor.rustad(a)gmail.com> wrote:
>>>> When I send a message from the Postorius interface, it is neither sent
>>>> or stored. I briefly see this message: "Your reply has been sent and is
>>>> being processed.", and then nothing happens.
So I installed a crontab for list and read about configuring the DB (I think
I'll use SQLite). I got to http://docs.mailman3.org/en/latest/config-web.html
. Because of the dollar sign, I assume that the commands are to be run as
list. Here's what I did:
root@lists:~# sudo list
sudo: list: command not found
root@lists:~# su list
This account is currently not available.
root@lists:~# ls /var/list
ls: cannot access '/var/list': No such file or directory
root@lists:~# locate mailman-suite_project
root@lists:~# mkdir /var/list
root@lists:~# chown list.list /var/list
root@lists:~# su list
This account is currently not available.
root@lists:~# man su
root@lists:~# su -s /bin/bash list
list@lists:~$ cd mailman-suite_project
bash: cd: mailman-suite_project: No such file or directory
list@lists:~$ mkdir mailman-suite_project
list@lists:~$ cd mailman-suite_project
list@lists:~/mailman-suite_project$ python manage.py createsuperuser
python: can't open file 'manage.py': [Errno 2] No such file or directory
list@lists:~/mailman-suite_project$ locate manage.py
Which manage.py should I use?
Lanthanidia deliciosa: What the kiwifruit would be
if it weren't so radioactive.
Using Docker. Suppose I've overcome
https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use
the templates/site/no directory for my customized templates. Yes, it seems
to be working, no hickups when national characters are used in the
the welcome message still says "Welcome to the "listname" mailing list" in
English. Is it possible to change that?
Hi everyone :),
This is my first post in this group, so let me thank all of the developers
for incredible work with Mailman3. Special congratulations goes to new
project leader, Abhilash :)
I've been using Mailman2 from over 15 years, and recently decided that it
is time to upgrade. For several days I'm playing with all of the components
of the system. Currently everything looks to be working nicely :)
Mailman-core, Mailman-suite (Postorius, Hyperkitty) installed directly, not
using docker containers.
The last step was integration with MTA. I've configured Postfix and
Mailman-core according to:
But messages send to the list address are not delivered to the list :( I've
started to investigate whats happening and realize that Postfix can not
connect to mailman using LMTP. It seems that mailman is not listening on
Nov 24 13:12:31 lists postfix/lmtp: connect to
127.0.0.1[127.0.0.1]:8024: Connection refused
I've checked log files, but haven't realize anything unusual . Any ideas
where I could try to find cause of the problem ?
My mailman.cfg file MTA section:
Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation.
I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps.
I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken.
Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org.
It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals.
My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced.
And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader.
If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient.
This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate.
Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best
way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention.
I have had this working before, so I guess it's a simple setup error.
When I send a message from the Postorius interface, it is neither sent out
or stored. I briefly see this message: "Your reply has been sent and is
being processed.", and then nothing happens.
I have installed maxking's docker-mailman and copied my old setup with
basic stuff like passwords and such. The only new thing is that I'm now
running in userspace by putting in /etc/subuid and subguid:
and in /etc/docker/daemon.json:
So I get the following ownership in /opt/mailman:
drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core
drwx------ 19 10070 10000 4096 nov. 21 09:27 database
drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web
(I have created a user named mailman with uid 10100 so, in reality, it says
"mailman" there instead of 10100 but I guess that is irrelevant here)
According to http://docs.mailman3.org/en/latest/config-core.html, I have to
add "@daily mailman digests --send" to the crontab. Which crontab does it go
in? In the system crontab, the thing after the time is the username, and
there's no user named "mailman" in /etc/passwd. Or should I put a script in /
loi mintu se ckaji danlu cu jmaji
As you all know I have been working on container images for Mailman 3.
We now have a new "rolling" tag for both mailman-core and
mailman-web images. These images have latest source installed
for every Mailman component. You can find more information about them
on the website .
New images are available on quay.io and, moving forward, the rest of
the image builds will also be moved to Quay.
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 :)
As most of you already know, Mailman 3 is the new and improved version
with extra features, better security and much better architecture. We
released Mailman Suite 3.0 in April 2015 and have come a long ways since
then. Mailman Suite 3.1, release May 2016, was aimed to provide
feature-parity with Mailman 2.x series and we think we _almost_ hit that
Apart from no monthly password reminders, Mailman 3 has a much better
Administrator/User interface, REST API for scripting, a really awesome
archiver, support for multiple domains, support for external plugins,
support for SSO/social login and so much more!
I love working on Mailman and would enjoy being able to do so full time
for next 6-8 weeks. Mailman 3 is not very far from becoming the default
version everyone would use, but it still needs some work to get there. I
need help from you, the users of Mailman, to get us there. If you or
your organization would like to move to (or, already moved to) Mailman
3, I urge you to donate to us.
There are options to donate using Credit Card, Paypal, Bitcoin, Wire
(of any currency), Check and money order.
If this campaign succeeds, here is a road map of what I intend to get
- Move Django apps(UI/Archiver) to Python 3 (or bilingual)
- Fork `mailman import` command to provide an upgrade path to Mailman
3.x from Mailman 2.x
- Fix MySQL compatibility in Core
- Changes in Postorius:
- Add support for missing options that are already exposed in Core’s
- e.g. Support for setting templates
- Find the commonly used options that are not exposed in Core, add
them to Core's API and add to Postorius
- Add Admin Dashboard project from GSoC 2014 (maybe?)
- Add better testing of container images and provide deployment
instructions for Kubernetes & Docker Swarm
- Improve the container images to work with new micro-services
to achieve scaling and redundancy in services.
- Administrator/User documentation for Postorius & Mailman
- (optional) Fork [mmcli](https://github.com/rajeevs1992/mailmancli)
project from Rajeev, fix if there is anything missing and add it as
additional command line tool to work with Mailman Core. Maybe pull it
under Mailman umbrella.
Except for these, if there is something more important that is
preventing the adoption of Mailman 3 from your end, we can discuss them.
I'd like to mention that I have been working on Mailman 3 for quite some
time now and I intend to implement every single item on the list. You
donations would help it get done much sooner, hopefully in time for 3.2
release schedule (at PyCon US 2018).
You can follow the progress of this campaign here.