- Mailman-users - lists.mailman3.org

ONLY moderator senders messages
by erlonmz＠hotmail.com 21 Dec '18

21 Dec '18

how to configure the mailman 3 for only moderators to send messages?

1 0

Mailman3 via Docker and NGINX
by brian＠emwd.com 19 Dec '18

19 Dec '18

I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there: server { listen 80; server_name `sitename.com`; location /static/ { alias /opt/mailman/web/static/; } location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation? Thank you for any assistance, Brian Carpenter

4 9

Templates
by David Krantz 19 Dec '18

19 Dec '18

Hi. How do I set a template for one specific list? I want one list to have a special footer template. I have tried updating the database (template table) without effect so apparently the database is not used for templates or some kind of fallback is used to set it to the generic footer. Of course I also tried to restart mailman after that operation to try to rule out any caching-related problem. I want to use a file://-path as that is the least painful way of doing it. I also would like a solution to place a file in a special location. My current templates are in a .../var/templates/site/en/ structure with names like list:member:generic:footer.txt Cheers // David

4 14

Newbie Wants To Know About Multiple Lists
by Christopher Garwood 19 Dec '18

19 Dec '18

Howdy, I am new to Mailman and there are so many things I would like to know. Before I try to find out how to install and configure the software, I need to know if, how and what is required for us to set up this software to deal with more than one email list. I am working with a plan to setup a CentOS VPS on which Mailman will be hosted. The objective is to host and administrate mailing list for the 3 entities that I am directly involved with. These lists must function completely unrelated to each other including the email addresses from which the emails & news letters are sent from. If this is possible can I be given information or a link to how it can be done and what is required?

2 2

disable-by-bounces
by erlonmz＠hotmail.com 19 Dec '18

19 Dec '18

copying a question already made here last year "I want to delete members automatically from a mailing list if the delivery has failed after a certain time of attempts because his mailbox has been removed or his mail server has been shutdown." at the time Mailman 3 was in version 3.1, today we are in 3.2. is this option available?

2 1

Button unsubscribe
by erlonmz＠hotmail.com 17 Dec '18

17 Dec '18

how to put a button unsubscribe in the message together with the part " LIST mailing list -- LIST@domain To unsubscribe send an email to LIST-leave@domain' I want to put this button in the emails to the users unsubscribe. it would already send the confirmation tolkien. my question is, has some place where generated tolkien is saved in mailman files?

3 4

Hyperkitty archives - new list not archived
by vaarcilal＠eafit.edu.co 12 Dec '18

12 Dec '18

Hi!! I'm running mailman 3.2 on Ubuntu server 18.04. Installed it via pip inside a conda virtual environment. I'm having problems related to hyperkitty on which I'd really appreciate some help. When I try to access the archives of a mailing list named 'test-nov' it redirects me to 'example.com/hyperkitty/list/test-nov@example.com/', where a 404 appears and a 'No archived mailing-list by that name.' message is thrown by hyperkitty.views.mlist.overview. I'm not very experienced with django, so I could have made a mistake on any configuration. I have not configured an MX for my mail server yet, so I'm able to send emails but I can't recieve emails for my lists. Is this somehow related to a misconfigurated MTA? Which logs should I take into account? Regards, Vincent.

2 5

Mailman3-Web lots of database queries
by Stefan Tatschner 10 Dec '18

10 Dec '18

Hey! I recently set up a mailman3 instance and it works quite nice. I use the debian packages from buster. After running the thing for a few days, I realized an unexpected network load (my postgres database is on a separate machine). Turning the postgres log on revealed that mailman3 constantly queries the database: [...] 2018-11-17 16:33:15.417 UTC [8304] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.385901+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.663 UTC [8305] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.621505+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.664 UTC [8306] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.624011+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.908 UTC [8308] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.870547+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.910 UTC [8307] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.871611+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.152 UTC [8310] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.116762+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.154 UTC [8309] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.114878+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.390 UTC [8311] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.358211+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.393 UTC [8312] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.359704+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.634 UTC [8313] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.596602+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.636 UTC [8314] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.598296+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.882 UTC [8315] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.842795+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.884 UTC [8316] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.841916+00:00'::timestamptz) LIMIT 1 [...] Is this behaviour intended? Stefan

4 12

Re: [Mailman-Users] Mailman 3 on Ubuntu 18.04
by Odhiambo Washington 09 Dec '18

09 Dec '18

On Sun, 9 Dec 2018 at 22:37, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/9/18 10:14 AM, Odhiambo Washington wrote: > > > > In my quest to run Mailman3, I obtained a VM running Ubuntu 18.04 and > > started on getting to run Mailman3. > > I found this link -> https://github.com/iomarmochtar/mailman3_ei > > It has instructions which looked fairly simple to get Mailman3 installed. > > However, I did encounter some hitches since the script is not meant for > > Ubuntu. > > > First, a more appropriate list for Mailman 3 is > mailman-users(a)mailman3.org > <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. > I am shifting to that list, after this. > > Also, we find it very difficult to address issues arising from third > party packages and how-tos. See <https://wiki.list.org/x/12812344>. > > And, there is a Mailman 3 package for Debian/Ubuntu > > apt install mailman3-full > In all my searching, I never found this in any documentation. I must have been searching in the wild, or my FreeBSD-mindedness got me stuck to containers and VENVs. > > With a few runs and observing the logs and modifying the script at every > > step it encountered and error, I finally managed to install Mailman3. It > > seems this is what you guys call a virtual environment in the Linux > world? > > :-) > > > I think the virtual environment in this case is a Python thing, not a > Linux thing. > I agree with you on that. > <snip> > > > Much of what I snipped is specific to > <https://github.com/iomarmochtar/mailman3_ei>, the details of which I'm > not interested in learning. > That is fine. I have put it aside for now. > > > >>From this point now is where I need help - serious help in smoothening > > things up and getting to understand these venv stuff! > > > > So I did run 'service mailman3 start' but this seems to be waiting for > too > > long to drop me back into the CLI. > > I also run 'systemctl start supervisord' and that seems to work. What I > am > > not sure is whether 'systemctl stop supervisord' actually does what it is > > expected to do because after I execute it, I still see processes running > > that I think are related. > > > > So far, I have been able to access the webUI on my VM using > > https://N.N.N.N:9090 > > I created a domain. > > But when I create a test list, I get an error - and I do not have a clue > > which logfile would have the error details - nginx or mailman... (I am > 100% > > new to nginx). > > > The nginx logs generally aren't too useful. Both Mailman core and Django > write logs. Core's log is probably in var/log/mailman.log where is > defined in mailman.cfg as var_dir. Django's log is defined in Django's > settings in the LOGGING setting. > Which file contains Django's settings? > > So now, I am stuck at: > > 1. Creating the mailing list > > 2. Getting to know whether the archiver is installed and running > > 3. Knowing is there are cron jobs to be running (Mailman2 type of > thinking!) > > > See > <http://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs > > > and > < > http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > > > Great to see that. I'll read and see if I make heads or tails of the writeup. > > Ultimately I need to figure out: > > 1. How the mailman queue runners are started and stopped > > mailman start > Why not systemctl mailman start?? Just wondering, as that is what I am seeing is common in Ubuntu. Does this make the components start after a reboot? > > 2. Migrate s few lists from Mailman2 to this Mailman3 > > mailman import21 > <django management> hyperkitty_import > Please show me where that is documented. I have to pull my lists from an old machine to this new one. > > 3. Mailman3 should use MySQL storage and Exim4 as the MTA (I have > > configured these bits in mailman.cfg) > > > You also need to configure MySQL in Django. See the DATABASES setting in > the Django settings. > So, when you talk about Django settings, you are referring to mailman.cfg file??? :-) I have spent all my weekend till now, trying to figure all this out. Life seems a little easier with mm2.x .... Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

2 1

Do not send email "The results of your email commands"
by erlonmz＠hotmail.com 07 Dec '18

07 Dec '18

Hello guys. Have to configure the mailman3 for not to send the e-mail " The results of your email commands" when an email is sent to "-leave@" and "-join@" ?? Sorry for my English, i from another country.

3 2