- Mailman-users - lists.mailman3.org

Re: Configure MM3 with separate IMAP Mailserver
by Clemens Leider 02 Jan '23

02 Jan '23

Hi Mark, much appreciated! This is for sending messages, right? How about the recieving part…I read different things around that i need multiple mailboxes created, postfix installed, relays, ASMTPDirect etc…can you guide me a bit here, please? I havent found that one instruction that would solve this for me until now. Would just like to avoid to have to administer my own mailserver locally, if i have a perfectly configured one with my provider. CL

2 1

Extracting mailing list users
by Jan Eden 02 Jan '23

02 Jan '23

Hi, I would like to export users of my mailing lists including their full name (if present). The export button in Postorius creates a CSV with addresses only, and the tool bin/list_members mentioned in the [Mailman 2 FAQ] does not seem to be available in Mailman 3. I have full access to the server/database, so scraping the web interface with [Mark's script] seems unneccessary. Is there an SQL statement (or an equivalent of bin/list_members) to extract the data? Thanks, Jan [Mailman 2 FAQ]: https://wiki.list.org/DOC/How%20do%20I%20extract%20%28export%29%20a%20list%… [Mark's script]: https://www.msapiro.net/scripts/mailman-subscribers3.py

6 19

Configure MM3 with separate IMAP Mailserver
by clemens.leider＠gmail.com 02 Jan '23

02 Jan '23

Dear all, we have managed to setup MM3 following the docker Installation concept/Tutorial. So far so good. However now i am struggeling with connecting to MTA. We are using imap server of our hosting provider.how to integrate that properly? Google was not too much of help unfortunately…looking for some tutorial or howto/step by step if possible. Thanks in advance CL

2 1

Web UI setup
by Lars Bjørndal 31 Dec '22

31 Dec '22

Thanks a lot for all your valuable help! I've followed the guide at <https://docs.mailman3.org/en/latest/install/virtualenv.html> I need to run mailman 2 and mailman 3 in parallel until I've migrated all lists, on several domains. I created the file /etc/httpd/conf.d/mailman3.conf with the content <VirtualHost *:80> ErrorLog logs/mailman3-error_log CustomLog logs/mailman3-access_log common RewriteEngine on RewriteCond %{HTTPS} off [NC] RewriteRule ^/mailman3(/.*) https://%{HTTP_HOST}/mailman3$1 [L,R=permanent] </VirtualHost> <VirtualHost *:443> ErrorLog logs/mailman3-error_log CustomLog logs/mailman3-access_log common include conf.d/certref.inc SSLEngine on </VirtualHost> <location /mailman3> ProxyPass http://localhost:8000 </location> The idea is to prepare mailman3 for several virtual domains. When I connect to lamasti.net/mailman3, the title is example.com. How can I change that? Thanks Lars

2 1

Apache
by Lars Bjørndal 31 Dec '22

31 Dec '22

I have already Apache installed and running for mailman2 and other resources. How do I serve mailman3 from Apache for the respective domains? Thanks in advance Lars

3 3

Early release of mailman 3.3.8 possible?
by Torge Riedel 31 Dec '22

31 Dec '22

Dear list / devs, is it possible to release 3.3.8 early? As far as I can see it is a prereq for my planned upgrade of the server from Ubuntu LTS 20.04 to Ubunto LTS 22.04. I use MySQL in my setup (own installation in venv), so my installation is affected by #1044, which is closed in 3.3.8 Also Ubuntu LTS 22.04 comes with Python 3.10 (https://packages.ubuntu.com/search?suite=jammy&keywords=python3) where the support is also stated earliest for 3.3.8 (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…) Am I right with my findings? I planned to upgrade the server until end of this year, because there is less traffic in the last days of a year. But I think unless 3.3.8 is not released, I cannot update the server. Kind regards Torge

4 5

MM2 -> MM3 Migration
by Odhiambo Washington 31 Dec '22

31 Dec '22

I looked at my list archives and saw that the latest post was on Dec 8, 2022. Then, because I wanted to import any posts that happened from 8th to now(), I looked at two posts: 1. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This talks about 'hyperkitty_import *--since=01.01.2022* -l mylist@mydomain my-mbox-file' 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html Which talks about 'hyperkitty_import *--since='1990-01-01'* -l mylist@mydomain my-mbox-file' I am concerned about the implication of the date format here, especially because our species from America write their dates differently than the British, even though the British colonized us all :P Well, I haven't looked at the manpage (--help) before posting this, and I know I should, but even without that, does Mailman speak American or British English when it comes to the date format? :-) In my case, I have done this: ' hyperkitty_import --since='2022-12-08' -l mylist@mydomain my-mbox-file' After that I ran: /opt/mailman/mm/bin/django-admin update_index_one_listmylist@mydomain And I am hoping that I will have the posts since Dec 8 to Dec 29 showing up in my archives. However, I am not sure. Hope someone can explain to the audience. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 5

Twitter OAuth2
by Odhiambo Washington 31 Dec '22

31 Dec '22

I'd like to integrate Twitter OAuth as part of the Social Accounts in my setup. I have gone through https://django-allauth.readthedocs.io/en/latest/providers.html#twitter, but cannot find the config options to add to my settings. Does someone have a config block setting for "SOCIALACCOUNT_PROVIDERS =" ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 15

combine postorius and hyperkitty into one Apache vhost
by Wolfgang Rosenauer 29 Dec '22

29 Dec '22

Hi, I'm in the process to set up a new mailman3 site. (Migrating from mailman2) There are RPMs for my distribution which integrate postorius and hyperkitty with uwsgi. The provided samples assume that both are running in different vhosts what I would like to avoid. Since I couldn't find any uwsgi examples for that I'm experimenting heavily but still having issues. I might just miss a simple thing (hopefully). My current apache config: Alias "/mailman/static" "/srv/www/webapps/mailman/postorius/static" ProxyPassMatch ^/mailman/static ! ProxyPass /mailman unix:/run/uwsgi/uwsgi-postorius.sock|uwsgi://localhost-postorius/ Alias "/archives/static" "/srv/www/webapps/mailman/hyperkitty/static" ProxyPassMatch ^/archives/static ! ProxyPass /archives unix:/run/uwsgi/uwsgi-hyperkitty.sock|uwsgi://localhost-hyperkitty/ This currently assumes that postorius just gets a mailman/ prefix and hyperkitty archives/ This setup immediately fails because of the urlpatterns filter in these components. For testing purposes I changed the patterns in urls.py slightly and I could make it work for me. BUT: This cannot be the solution, can it? Isn't there an easier way to allow these components to run under a different document root? Something slightly unrelated but causing issues in some edge cases also is that Django? does not detect the request url properly. For some functionality e.g. when I want to login to Django admin under /archives/admin (even after modifying urls.py) I get a redirect after the form which shows that my initial path was not recognized as /archives/admin but /archive//admin instead. So the last character is replaced with a / Any hints for me? Thanks, Wolfgang

3 3

hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header
by Odhiambo Washington 29 Dec '22

29 Dec '22

I worke up to 959 such entries in my mailmanweb.log: ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:49:57,784 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:05,746 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,022 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,183 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,273 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,353 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-12-27 22:50:06,435 82073 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. What might have been the cause of this? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 4