Search results for "sapiro" - lists.mailman3.org

[MM3-users] Lessons learned and a couple little gotcha for newbies

by William Oliver

I just finished, with great help from Mark Sapiro on the list, a new installation of mailman3. I used the instructions at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/insta… and https://docs.mailman3.org/en/latest/install/virtualenv.html There were a couple of gotchas that I didn't see well documented. 1) I got the error django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site- packages/mistune/scanner.py) when I ran 'mailman-web migrate' The fix was trivial: I just added the lines: from mistune.util import escape_html from mistune.util import escape_url to /opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py It's not hard to search for those definitions, but if someone doesn't know a smattering of python, it might not be obvious. 2) Similarly, migrate (using postgres) also gave the error: File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/backends/postgresql/utils.py", line 6, in utc_tzinfo_factory raise AssertionError("database connection isn't set to UTC") I was able to find a discusson of this one at https://stackoverflow.com/questions/68024060/assertionerror-database-connec… which had me downgrade to an older version of psycopg2-binary: pip install psycopg2-binary==2.8.6 There might be a different fix, but this worked. 3) When I ran the test "uwsgi --ini /etc/mailman3/uwsgi.ini" I got the error: ModuleNotFoundError: No module named 'settings' This was also trivially fixed by adding the path: export PYTHONPATH=$PYTHONPATH:/etc/mailman3 in /opt/mailman/.bashrc 4) Sometimes when I rebooted the machine, when I ran 'systemctl start mailman3' I'd get the error that mailman wouldn't start because the lock was stll there. I never could figure out where the lock was, so I worked around it by replacing ExecStart=/opt/mailman/venv/bin/mailman start with ExecStart=/opt/mailman/venv/bin/mailman start --force in /etc/systemd/system/mailman3.service I'm sure there's something bad about doing that, but it works for me, so far. 5) I had a problem with mail to outside people not being delivered while mail to the local host was delivered. It turned out that this was because in my mailman.cfg I had "smtp_host:my.listserver.tld when it should have been localhost. The error was "relay access denied." To fix this, I had to add my.listserver.tld to "mynetworks" in /etc/postfix/main.cf, ie change: mynetworks = 127.0.0.0/8 10.0.0.0/24 to mynetworks = 127.0.0.0/8 10.0.0.0/24 111.222.333.444 <--- my ip address However, Mark Sapiro (a God) told me this was because I had changed a line in the [mta] section of mailman.cfg. I had changed smtp_host: localhost to smtp_host: mydomain.tld Here's the thing. The reason I did this was because the instructions at https://docs.mailman3.org/en/latest/config-core.html give this as their model: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com <---- not localhost smtp_port: 25 The instructions are good, but there are a few places where one size does not fit all, I guess. 6) A second error in delivery to outside addresses resulted in an "Access denied" error. A search on the internet revealed that this had to do with (for me) smtpd_recipient_restrictions in postfix. See, for instance: https://know.mailsbestfriend.com/postfix_error_relay_access_denied_noqueue_… Changing this fixed things. I'm not sure, but I think this shows up mostly with installations that include dovecot. 7) If you are using virtual domains in postfix, you need to use the "unusual postfix configuration" in https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap 8) You need to manually set the local virtual host for mailman3. Somehow, I got the impression from the installation instructions that this was done automagically to the default x.mydomain.tld if your domain is mydomain.tld. It doesn't. 9) Follow the instructions verbatim, and follow them in the order provided. I installed postfix and nginx out of order, and it did OK, but once you get into the python virtual environment, it is easy to miss something if you don't do it in order. 10) Jot down lots of notes. This is one of the more complicated installations I've done, mostly because it involved configuring a zillion packages to talk to each other: Postfix, nginx, postorius, hyperkitty, django, and others (I'd never heard of "whoosh" or "sass" for instance). All of these can be unforgiving with configuration errors. The default installation instructions assumed a number of packages I'd never used. I'm an apache/dovecot/mysql kind of person, and I had to switch to nginx/postgres to use the instructions as the written defaults. I'm sure I could have used apache and mysql, but it would mean trying to figure out what didn't work without following the installations verbatim. I'd never even heard of postorius, hyperkitty, or django. So, it was easy to get confused a bit. Taking notes of changes I made was important in being able to back out of disastrous choices. Plus, once I'd installed it on one machine, I sat down and installed it on another machine, and it was very useful to have written down how I fixed an issue when it came up again -- and I didn't remember exactly what I had done. 11) Make multiple sequential backups of configuration files. I went down a couple of paths I shouldn't have gone down. For instance, with the vmap issue, I got it in my head that it was a postfix configuration issue, not a mailman issue. So I kept changing things in postfix. Once I was told that it was in *mailman* I had to set the virtual host, I needed to back out of about 8 tweaks I'd made to main.cf in /etc/postfix. If I hadn't been making main.cf.backup.01, main.cf.backup.02, etc. I would have had to spend another few hours trying to remember what inappropriate changes I had made. This is particularly true for me because I am not a great typist, and when I try to retype something to back out, there's a reasonable chance I'll mistype something and it still won't work. With these backups, I don't have both manually back out of things *and* proof my typing again and again. It's a lot easier to delete backups once things are working than to try to remember what you did late at night after a couple of bourbons. 12) Choose one set of installation instructions and follow it. Don't try to mix instructions from different tutorials unless you really know what you are doing. I didn't. For instance, there's a different set of mailman3 installation instructions at: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 It does things a little differently. It's useful to look at that when you are debugging why something's not working, but you can get into some trouble trying to do both installations at the same time -- which I found myself doing when something wasn't working. It didn't help. billo

3 years, 7 months

[MM3-users] Re: how to administrate mailman3 in CLI ?

by testeur

Sorry. I didn't see in the good place. when i see parameters here : https://URL/mailman3/postorius/accounts/per-subscription-preferences/ the options or the specific language chosen (not for the ui) for the list is finally changing when i use the code used before... i should use shell with mailman user. ok i note it. I ve seen this link about python script to manage mailman3 by shell : https://fog.ccsf.edu/~msapiro/scripts/ (thx you) Regards, On 23/09/2023 17:33, Mark Sapiro wrote: > On 9/23/23 07:40, testeur via Mailman-users wrote: >> >> |# mailman shell -l testlist(a)domain.tld | > > It looks like you are running `mailman shell` as `root`. You should > always run mailman commands including starting mailman as the Mailman > user, never as root. Running thing as root can create things that > later can't be read by the mailman user. > >> ||>>> from mailman.interfaces.action import Action >>> for mbr in >> m.members.members: mbr.moderation_action = Action.defer |||commit()| >> >> |||>>> from mailman.interfaces.action import Action |||||||>>> >> english = getUtility(ILanguageManager).get('en')| >>> for mbr in >> m.members.members: || mbr.preferences.acknowledge_posts = False >> mbr.preferences.delivery_mode = DeliveryMode.regular >> mbr.preferences.delivery_status = DeliveryStatus.enabled >> mbr.preferences.hide_address = False >> mbr.preferences.preferred_language = english >> mbr.preferences.receive_list_copy = False >> mbr.preferences.receive_own_postings = True|commit()|| > > > I'm not sure what the above actually says. The interaction should look > like > ``` > >>> from mailman.interfaces.action import Action > >>> english = getUtility(ILanguageManager).get('en') > >>> for mbr in m.members.members: > ... mbr.preferences.acknowledge_posts = False > ... mbr.preferences.delivery_mode = DeliveryMode.regular > ... mbr.preferences.delivery_status = DeliveryStatus.enabled > ... mbr.preferences.hide_address = False > ... mbr.preferences.preferred_language = english > ... mbr.preferences.receive_list_copy = False > ... mbr.preferences.receive_own_postings = True > ... > >>> commit() > ``` > Actually, importing Action is not necessary as it is among the things > defined by default in `mailman shell` in interactive mode. > >> Before the shell command, the web interface was with an other >> language (i tested with italian one) and other options preferences, >> but after the shell command, after a web interface refresh, it >> doesn't change. > > > The above shell interaction sets the preferred_language for all list > members to english. This has nothing to do with the language for the > web UI. This is set by Django. See > <https://docs.djangoproject.com/en/4.2/topics/i18n/translation/#how-django-d…>. > >

1 year, 11 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Thu, 30 Jul 2020 at 20:45, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/30/20 1:53 AM, Odhiambo Washington wrote: > > > > os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") > > > Try changing this one line in wsgi.py to > > os.environ["DJANGO_SETTINGS_MODULE"] = "settings" > That option did not work. > > If that doesn't work, try adding these two lines following the line > > import os > > > import sys > sys.path.insert(0, '/opt/mailman/mm') > This works - I mean changes the error message to [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote 197.232.81.246:63962] /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: UserWarning: Markdown renderers are not available. Install 'readme_renderer[md]' to enable Markdown rendering. [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client 197.232.81.246:63962] AH01630: client denied by server configuration: /var/spool/mailman-web, referer: http://mm3-lists.my.server/mm3/mailman3/lists/ There is NO /var/spool/mailman-web anywhere. It has not been created. You mentioned that it should be created automatically, IIRC. root@gw:*/opt/mailman/mm* # ls -al total 116 drwxr-xr-x 8 mailman3 wheel 512 Jul 29 10:06 . drwxr-xr-x 7 mailman3 wheel 512 Jul 28 14:17 .. drwxr-xr-x 8 mailman3 wheel 512 Jul 25 22:16 .sass-cache -rw-r--r-- 1 mailman3 wheel 0 Jul 29 10:06 __init__.py drwxr-xr-x 2 mailman3 wheel 512 Jul 30 21:12 __pycache__ -rw-r--r-- 1 mailman3 wheel 2372 Jul 28 13:16 _settings_local.py drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:42 bin -rw-r--r-- 1 mailman3 wheel 248 Jul 25 14:37 gunicorn.conf -rw-r--r-- 1 mailman3 wheel 266 Jul 26 15:34 gunicorn.conf.py -rw-r--r-- 1 mailman3 wheel 0 Jul 28 12:19 init.py lrwxr-xr-x 1 mailman3 wheel 24 Jul 25 14:39 logs -> /opt/mailman/mm/var/logs -rw-r--r-- 1 mailman3 wheel 445 Jul 28 11:37 mailman-hyperkitty.cfg -rw-r--r-- 1 mailman3 wheel 1291 Jul 26 17:12 mailman.cfg -rw-r--r-- 1 mailman3 wheel 15516 Jul 27 16:32 settings.py -rw-r--r-- 1 mailman3 wheel 16069 Jul 28 13:15 settings_local.py -rw-r----- 1 mailman3 wheel 5914 Jul 27 17:35 settings_local.py.2 -rw-r--r-- 1 mailman3 wheel 15831 Jul 27 16:21 settings_local.py.BAK drwxr-xr-x 9 mailman3 wheel 512 Jul 25 22:16 static -rw-r--r-- 1 mailman3 wheel 1395 Jul 25 14:35 urls.py drwxr-xr-x 12 mailman3 wheel 512 Jul 30 21:12 var drwxr-xr-x 5 mailman3 wheel 512 Jul 26 17:11 venv -rw-r--r-- 1 mailman3 wheel 1271 Jul 30 21:03 wsgi.py -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 16/9/21 16:40, Mark Sapiro wrote: > On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to provide the list moderators a way to change the moderation >> flag for users from whichever it is (normally "list default >> processing") to "hold for moderation" and viceversa (to "list >> default" or to "accept") >> >> I understand that it could be done via console script (That's the way >> I did on mailman2: I made two commands using "withlist", one to hold, >> moderar.py, and other one to accept, desmoderar.py. I show you below) > > > Are you asking what the equivalent MM 3 scripts would be? > More or less: I'm asking for a general direction here. I think I cannot use tthe "withlist" method as before, inside a python script, and I'm not sure how to do it. I've been reviewing all the command docs that I've found, but I have no clear way. I need a shell or a python script that I can pass the list and the mail address to put on hold/hold (that way the moderators can log in a special account thhat asks for the address to hold/unhold). I did it in mailman2 whith the bin/withlist command, but now whithlist seems to be an alias for shell and is interactive.Thats not my goal) > >> But I think I'm not the only one that could use as an improvement a >> way to do this on postorius/web. > > > Postorius allows a list owner or site admin to set Moderation for list > members and non members at e.g. > https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Yes, I know that. But the owner cannot be 24/7 attending the lists (as we all know), and could need a help hand from moderators. Not just from accepting mails on hold, but to put on hold a member (and be capable of reversing it) when the netiquete dissapears completely and some thread becomes a flame and all goes south. I'ts the admin capability I miss the most for moderators in mailman. > Currently, a list moderator who is not an owner cannot do this, but a > moderator can set Moderation for the sender of a held post when > handling the post. But I'm talking about a moderator can put a member mails in hold when it is marked to accept. To prevent putting more gas in the fire. > >

3 years, 11 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Mark Sapiro: > What is the complete log message from uwsgi-error.log? I'll attach a typical log file to this message. It shows startup messages followed by a recorded confirmation email. User name and domain are obfuscated, but other than that the log is unchanged. -Ralph *** Starting uWSGI 2.0.18 (64bit) on [Sat Mar 28 20:55:36 2020] *** compiled with version: 9.3.0 on 26 March 2020 13:58:28 os: Linux-5.5.13-gentoo #1 SMP Thu Mar 26 10:24:38 CET 2020 nodename: wedjat machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 8 current working directory: /var/lib/mailman detected binary path: /var/lib/mailman/venv/bin/uwsgi chdir() to /var/lib/mailman/suite/ your processes number limit is 256427 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to TCP address 127.0.0.1:8002 fd 8 Python version: 3.8.2 (default, Feb 26 2020, 08:14:41) [GCC 9.2.0] Python main interpreter initialized at 0x56443febc210 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x56443febc210 pid: 21912 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 21912) spawned uWSGI worker 1 (pid: 21916, cores: 2) 19:55:38 [Q] INFO Q Cluster pizza-illinois-golf-magnesium starting. 19:55:38 [Q] INFO Process-1:1 ready for work at 21921 19:55:38 [Q] INFO Process-1:2 ready for work at 21922 19:55:38 [Q] INFO Process-1:3 ready for work at 21923 19:55:38 [Q] INFO Process-1:4 ready for work at 21924 19:55:38 [Q] INFO Process-1:5 ready for work at 21925 19:55:38 [Q] INFO Process-1:6 ready for work at 21926 19:55:38 [Q] INFO Process-1:7 ready for work at 21927 19:55:38 [Q] INFO Process-1:8 ready for work at 21928 19:55:38 [Q] INFO Process-1:9 monitoring at 21929 19:55:38 [Q] INFO Process-1 guarding cluster pizza-illinois-golf-magnesium 19:55:38 [Q] INFO Process-1:10 pushing tasks at 21930 19:55:38 [Q] INFO Q Cluster pizza-illinois-golf-magnesium running. Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [lists.domain.tld] Please Confirm Your E-mail Address From: postmaster(a)domain.tld To: OBFUSCATED(a)gmail.com Date: Sat, 28 Mar 2020 20:08:15 -0000 Message-ID: <158542609570.21916.15168402908994348907(a)wedjat.domain.tld> Hello from lists.domain.tld! You're receiving this e-mail because user OBFUSCATED has given yours as an e-mail address to connect their account. To confirm this is correct, go to https://lists.domain.tld/accounts/confirm-email/Mg:1jIHkd:x8NSjzCkP5ifX6V39… Thank you from lists.domain.tld! lists.domain.tld -------------------------------------------------------------------------------

5 years, 4 months

[MM3-users] Re: mailman-core installation on debian stretch/maria-db

by Wolfgang Bock

Hi Mark, thanks for your reply. In my debian apt-get install the "mysql+pymysq" sentence was now automaticly set. My Debian dbconfig-mysql dependency refers to maria-db. I had some problem of creating the database due to right-problems with dbconfig. So I created the database manually and set permissions to the database-user manually. The results were shown yesterday. Now I am stopping all efforts on fiddeling with mailman3, re-setup my server in order to get rid of all that python stuff and will use mailman 2.1 which runs without problems and does all things I need. A sql-membermanagement would be useful, but in this version not available. And wait for an official mailman upgrade within the debian stretch stable ... Thank you for your efforts. Regards Wolfgang Am 12.03.2018 um 02:24 schrieb Mark Sapiro: > On 03/11/2018 03:11 PM, Wolfgang Bock wrote: > >> -> After I set a symlink to /sbin/master another errormessage occurs >>>> 2. connection to maria-db >>>> In debian stretch maria-db is running. In my mailman.cfg I set: >>>> [database] >>>> class: mailman.database.mysql.MySQLDatabase >>>> url: >>>> mysql+pmysql://#username#:#user-pawo#@localhost/#databasename#?charset=utf8&use_unicode=1 >>>> >>> should that be mysql+pymysql ? >> -> Yes, according to: >> http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html >> -> Not right?? > > My point is you have 'mysql+pmysql' and you should have 'mysql+pymysql'. > You are missing the first 'y' in 'pymysql'. > > >> After that I decided to delete mailman via pip and took a new approach >> via debians apt-get ... mailman 3 >> >> So far so good, now new errormessage: >> >> Traceback (most recent call last): > ... >> AttributeError: module 'mailman.database.mysql' has no attribute >> 'MYSQLDatabase' > > Did you install the Debian dbconfig-mysql dependency? I don't know how > installation of mailman3-core determines which if any of the database > dependencies, but you need that for sure to support MySQL/MariaDB. > > >> Another question is, where can I find the sql-command within the >> database mailman3 like CREATE TABLE x and TABLE y as I created a >> database mailman3 which is empty?? > > The database may be empty because of the above error and the fact you > haven't yet done anything. > > All the database access is via SQLAlchemy and models defined in > Mailman's mailman/models/ directory. See > <http://mailman.readthedocs.io/en/latest/src/mailman/model/docs/model.html>. >

7 years, 5 months

[MM3-users] 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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

> On Dec 29, 2021, at 08:49, William Oliver <billo(a)billoblog.com> wrote: > > On Tue, 2021-12-28 at 18:23 -0800, David Newman wrote: >>> >>> [snip] >>> I'm using nginx >> I'd asked about this a few weeks ago for a MM3 host running Ngnix >> with a >> few virtual domains, one of which runs Roundcubemail as its default. >> >> Mark Sapiro suggested the following, and it seems to be working OK. >> You'll need these lines in the Nginx config file for each virtual >> host >> you define. >> >> # begin mailman3 stuff >> >> location /static/ { >> alias /opt/mailman/web/static/; >> } >> > [snip] > > > > No joy. This just makes it kind of work as the mailman interface when > it gets rewritten. > > My problem is that the url is getting referred to > domainname/mailman3/lists even when I don't want it to. That sounds like an nginx configuration problem, not a Mailman3 issue. One assumption in the MM3 web setup docs is that MM3/Django/Postorius/Hyperkitty are the only web services running. If they’re not, and there are other services running, you’ll need to tell Nginx where they are. The setup I provided is an excerpt and covers only how to point to MM3 in such a scenario. It does not cover how to point to something else as root at, say, www.domain.tld. This is off-topic for a Mailman3 list, but maybe check your default files in the sites-available directory, and also anything they point to, paying particular attention to where / points and which root directory you’re using. Same thing with any other config files in that directory. dn > Adding these > changes just (partially) loads the mailman3 interface when it gets > rewritten. > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. > > billo > > > > > > > _______________________________________________ > 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/

3 years, 7 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 10:29 -0800, Mark Sapiro wrote: > > > This is the issue. > > See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > for information on configuring Postfix with mailing lists in a > virtual > domain. > > Thanks, at least that changed the error :-) Clearly that was the problem, but it uncovered a new one -- the mailman vmap doesn't seem to be created. In the installation docs, it says about /opt/mailman/mm/data/postfix_vmap: "If this is done and the configured MTA is Postfix, Mailman will create an additional /path-to-mailman/var/data/postfix_vmap file with mappings from the example.com addresses to the corresponding addresses in the alias_domain and will use the alias_domain in the other files. " But, alas, I get a "temporary lookup failure" which isn't all that helpful. However, if I wander over to /var/logs/syslog, I see: Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: connect from localhost[::1] Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains: hash:/opt/mailman/mm/var/data/postfix_vmap: table lookup problem Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains lookup failure Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains: hash:/opt/mailman/mm/var/data/postfix_vmap: table lookup problem Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains lookup failure Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: NOQUEUE: reject: RCPT from localhost[::1]: 451 4.3.0 <billo(a)billoblog.com>: Temporary lookup failure; from=<mailman(a)libertyfp.org> to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 15:18:23 libertyfp postfix/smtpd[20254]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory and on and on. This looks like a clue to me -- that mailman3 did not automagically make postfix_vmap.db. Is there a "make-the-freaking-virtual- map-database" command in mailman3, or is this postfix thing? Should I just touch the thing and create an empty file? I'm a little scared to... The error message makes me think that it should be populated with something... Sigh. That's enough for today. I'm off to eat Christmas turkey. Thanks for all your help this morning. billo

3 years, 8 months

[MM3-users] translating templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 13/2/21 20:00, Mark Sapiro wrote: > Also note that the translations on weblate only affect strings in the > core code. The Mailman core templates are not currently translated in > weblate and there are currently no Spanish language templates. One would > need to create Spanish translations of all the templates in > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> > and submit a merge request to add them to a mailman/templates/es/ directory. I downladed the templates and I'm beginning the translation process, but I have a question. What language map has to be used? In my S.O. it's ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before having to do a remapping of the files after... It comes to my attention that three files have 0 bytes. -rw-r--r-- 1 Oldno7 wheel 382 14 feb. 00:22 domain:admin:notice:new-list.txt -rw-r--r-- 1 Oldno7 wheel 886 15 feb. 11:28 help.txt -rw-r--r-- 1 Oldno7 wheel 289 14 feb. 00:22 list:admin:action:post.txt -rw-r--r-- 1 Oldno7 wheel 120 14 feb. 00:22 list:admin:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 122 14 feb. 00:22 list:admin:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 133 14 feb. 00:22 list:admin:notice:disable.txt -rw-r--r-- 1 Oldno7 wheel 71 14 feb. 00:22 list:admin:notice:removal.txt -rw-r--r-- 1 Oldno7 wheel 59 14 feb. 00:22 list:admin:notice:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 257 14 feb. 00:22 list:admin:notice:unrecognized.txt -rw-r--r-- 1 Oldno7 wheel 45 14 feb. 00:22 list:admin:notice:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:digest:header.txt -rw-r--r-- 1 Oldno7 wheel 337 14 feb. 00:22 list:member:digest:masthead.txt -rw-r--r-- 1 Oldno7 wheel 154 14 feb. 00:22 list:member:generic:footer.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:regular:header.txt -rw-r--r-- 1 Oldno7 wheel 562 14 feb. 00:22 list:user:action:invite.txt -rw-r--r-- 1 Oldno7 wheel 753 14 feb. 00:22 list:user:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 739 14 feb. 00:22 list:user:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:user:notice:goodbye.txt -rw-r--r-- 1 Oldno7 wheel 281 14 feb. 00:22 list:user:notice:hold.txt -rw-r--r-- 1 Oldno7 wheel 439 14 feb. 00:22 list:user:notice:no-more-today.txt -rw-r--r-- 1 Oldno7 wheel 98 14 feb. 00:22 list:user:notice:post.txt -rw-r--r-- 1 Oldno7 wheel 568 14 feb. 00:22 list:user:notice:probe.txt -rw-r--r-- 1 Oldno7 wheel 273 14 feb. 00:22 list:user:notice:refuse.txt -rw-r--r-- 1 Oldno7 wheel 151 14 feb. 00:22 list:user:notice:rejected.txt -rw-r--r-- 1 Oldno7 wheel 353 14 feb. 00:22 list:user:notice:warning.txt -rw-r--r-- 1 Oldno7 wheel 532 14 feb. 00:22 list:user:notice:welcome.txt TIA.

4 years, 6 months

Search results for query "sapiro"