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

[MM3-users] Re: logrotate

by Odhiambo Washington

On Wed, May 3, 2023 at 2:38 AM Mark Sapiro <mark(a)msapiro.net> wrote: > Please don't hijack threads. Post a new topic as an original post, not > as a reply to an old thread. > > On 5/2/23 15:45, Christian via Mailman-users wrote: > > I noticed that my mailman logfiles are not being rotated. I followed the > > instructions in > > > https://mail.python.org/archives/list/mailman-developers@python.org/message/ > > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ > > > Those instructions are for Mailman 2.1. > > > > Now when I try and run logrotate I get the following error > > > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file or > > directory > > error: stat of /opt/mailman/mm/error.log failed: No such file or > directory > > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > > directory > > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file or > > directory > > error: stat of /opt/mailman/mm/smtp.log failed: No such file or > directory > > root@zarathustra: > > > > What am I doing wrong please? > > Here's a logrotate script I use: > ``` > /opt/mailman/mm/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null > || true > if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mm/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > ``` > A couple of caveats. The first line of the postrotate script may be > wrapped. `sudo ... true` is all one line. > > That line could also be > ``` > /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true > ``` > I.e., it either has to run as the mailman user or specify the > --run-as-root option. > > Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't > in /opt/mailman/mm/var/ those paths need adjusting. > > Finally, there may be an issue with `mailman reopen` in the postrotate > scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 > > In my case, I took a different approach with Django's logging configuration: [snip] 'handlers': { 'file': { 'level': 'INFO', 'class': 'logging.handlers.TimedRotatingFileHandler', 'filename': '/opt/mailman/mm/var/logs/mailmanweb.log', 'when': 'D', # specifies the interval 'interval': 1, # defaults to 1, only necessary for other values 'backupCount': 5, # how many backup file to keep, 5 days 'formatter': 'simpleRe', }, }, [snip] I have not been rotating the other log files as my list is not a high-volume one so logs aren't growing much. Plus I only rely on the logs for diagnostics, not for records ;( -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 years, 4 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Eggert Ehmke

I have this in my mailman3.service file: [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop That works fine. Am Dienstag, 25. Oktober 2022, 07:06:57 CEST schrieb Onyeibo Oku: > On Sun, 23 Oct 2022 08:00:19 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/22/22 21:29, Onyeibo Oku wrote: > > > Now Mailman starts, and stops as desired when running as mailman > > > user (both in virtual and non-virtual environments). However, > > > running the service via systemd still fails. I now get a different > > > traceback: > > > > > > Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most > > > > > recent call last): > > ... > > > > > Oct 23 03:43:00 mail.server.tld mailman[19410]: with > > > open(self._claimfile, 'w') as fp: Oct 23 03:43:00 mail.server.tld > > > mailman[19410]: PermissionError: [Errno 13] Permission denied: > > > '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958 > > > 240354' Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: > > > Control process exited, code=exited, status=1/FAILURE > > > > What are ownership and permissions on /opt/mailman/mm/var/locks/ > > > > Assuming they are > > > > drwxr-xr-x mailman mailman > > > > it must be the case that systemd is not running the > > `/opt/mailman/venv/bin/mailman start` command as the `mailman` user. > > I suspect this is a Fedora issue. I note that > > https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administ > > ering-systemd/#_service_parameters does not mention User or Group. You > > might try replacing > > ``` > > ExecStart=/opt/mailman/venv/bin/mailman start > > ExecReload=/opt/mailman/venv/bin/mailman restart > > ExecStop=/opt/mailman/venv/bin/mailman stop > > > > with > > > > ExecStart=sudo -u mailman /opt/mailman/venv/bin/mailman start > > ExecReload=sudo -u mailman /opt/mailman/venv/bin/mailman restart > > ExecStop=sudo -u mailman /opt/mailman/venv/bin/mailman stop > > ``` > > This does not work. Systemd says it cannot find sudo (file). After > updating in the commands "sudo" to "/bin/sudo" afterwards Systemd throws > a different error message: PermissionError on /bin/sudo > > This is tiring. At this moment I am left with the possibility that > SELinux may be in the way. I cannot think of a way to prove this > hypothesis. This is speculation. Perhaps I should try another > installation method other than Virtual. I found Mailman3 in Fedora > repository. Yes, it is packaged. May be I should try that or perhaps I > should try the git version. I'd be happy to have a functioning Mailman > before Friday. > > > Regards > Onyeibo > _______________________________________________ > 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, 10 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

I don't think this reply got to the mailing list, so I am sending it again, sorry if its a duplicate. On Sat, 13 Mar 2021 00:33:58 -0500, Mark Sapiro wrote: > > On 3/12/21 7:36 PM, John Covici wrote: > > Hi. I am having a great deal of difficulty installing mailman3 using > > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > > mailman3. > > > > What I have done so far is to install the mailman3 packages from my > > repository and got this: > > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > > version 3.3.2 (apparently the core), postorius version 1.3.3 and > > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. > > > Are these gentoo packages? If so, I have no idea how they are > configured. Anyway I can tell, there was no configuration (we call them use flags) they just seemed to install the files in what seems to be the correct places. > > > > Now trying to read your documentation, it seems it wants me to > > reinstall some packages using pip in the home directory of the mailman > > user in a python virtual environment, that was the first thing. But I > > would like to avoid multiple package managers wherever possible -- > > gentoo is already a lot of maintainance without dealing with pip's > > maintainance. The binaries also seem to be different from my gentoo packages. > > > Our documantation generally covers installing from source. If you are > installing gentoo packages, you should be looking at gentoo docs and > going to gentoo for help. > > We recommend installing Mailman and the web components in a virtualenv, > but it is not a requirement. We also suggest that postgresql is a better > choice than MariaDB. > I sort of am installing from source, gentoo installs from source. No one on the gentoo users mailing list seems to be able to help me, except to tell me to use a different mailing list mechanism called mlmmj. > > > So, how do I proceed with getting mailman3 up and working, configuring > > the database, configs, etc and I guess after doing that upgrading > > mailman2 and getting sendmail to interface properly with mailman3? > > Importing lists from Mailman 2 is done with the `mailman import21` > command. See > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. > Importing archives is done with the Django management > `hyperkitty_import` command. See > <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> > > For sendmail, see > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Thanks. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 6 months

[MM3-users] Re: Confusing mailman user model

by Gilles Filippini

Gilles Filippini a écrit le 19/07/2020 à 19:10 : > Gilles Filippini a écrit le 19/07/2020 à 18:00 : >> Mark Sapiro a écrit le 19/07/2020 à 17:30 : >>> On 7/19/20 8:10 AM, Gilles Filippini wrote: >>>> Hi, >>>> >>>> I'm trying to understand the Mailman user model, and I'm confused about >>>> the respective roles of tables 'auth_user' and 'user'. >>> >>> >>> auth_user is a Django auth table. These are the users listed in the >>> Django admin web UI. >>> >>> user is Mailman core's users. >>> >>> >>>> Both have an 'id' column referred to as 'user_id' when used as a foreign >>>> key. But there seems to be no relation at all between them as they use >>>> different ids for the same user. >>> >>> >>> Right, they are unrelated. >>> >>> >>>> Our mailman server was migrated from mailman2 to mailman3 about 1.5 year >>>> ago, and there is an inconsistency I'd like to fix: >>>> 2 of our users have a registered Mailman account with their respective >>>> email addresses in table 'auth_user', but these very same addresses in >>>> the 'address' table are linked to another old admin account in the >>>> 'user' table. >>> >>> Their Mailman account is the 'old' one. the auth_user account is a >>> Django account >>>> >>>> Then if add one of these addresses as a domain owner, it it the old >>>> admin address which is selected instead. How could I fix that? >>> >>> >>> That's because domain owner in a Mailman thing and involvs the Mailman >>> user. You could delete the Django users via the Django admin UI and then >>> re-register them via Postorius. That *might* work. >> >> When login into postorius, it is the Django account that is used, right? >> Then how is the mailman account retrieved from there? It seems UUIDs are >> used in the process, but I fail understanding how, so far. Wouldn't it >> be safe to retrieve the new Mailman account associated to these Django >> users, and link there emails from 'address' table' to them? > > Reading the mailman-web source code I understand now that the mailman > account is retrieved from the Django account email address. Then both > users are tied to the same old mailman admin account, and deleting then > registering them again won't change anything on this aspect. > > Would this work? > 1- For both addresses, update their record in table 'address' to set > 'user_id' to null > 2- On their next login to Mailman-web, a new mailman account would be > created and associated with their own email address. Done that, and it worked. Thanks, _g.

6 years, 1 month

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Odhiambo Washington

On Sun, 26 Jul 2020 at 18:22, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 12:37 AM, Stephen J. Turnbull wrote: > > > > That's not our guide, we don't support it, and at least I don't > > recognize the author offhand, can't speak for the rest of the team. > > > The author has been involved in a few threads on this list. > > > > Now that our NO WARRANTY notice is out of the way, I will say that > > guide is written in very good style, with great attention to detail > > and appropriate warnings about delicate parts of the procedure. If > > you end up succeeding with it, I'll add a link to it to our docs. > > > It is currently linked from the first paragraph at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. > I followed the steps outlined in the subject document and got mailman3 running. However, what is missing in that document is the process of setting up a webserver for accessing the MM3 UI. I have spent two days trying to figure out that aspect and discovered a few things (I could be wrong in what I think): 1. For one to use the uwsgi.ini that is dropped in /etc/mailman3/ by the installation process, the uwsgi daemon must be installed: *apt install uwsgi-core uwsgi* 2. The uwsgi.ini must be linked in the directory where the uwsgi daemon looks for config files: *cp /etc/mailman3/uwsgi.ini /etc/uwsgi/apps-available/uwsgi.ini* *ln -s /etc/uwsgi/apps-available/uwsgi.ini /etc/uwsgi/apps-enabled/uwsgi.ini* 3. The uwsgi daemon needs to be started *systemctl start uwsgi* root@lists:/etc/mailman3# ps ax | grep wsgi 5838 ? S 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5841 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log 5842 ? Sl 0:00 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/uwsgi.ini --daemonize /var/log/uwsgi/app/uwsgi.log Now that uwsgi daemon is running, the last step would be to configure the webserver to serve the MM3 pages. The apache config snippet dropped by the mailman3 install process in /etc/mailman3/apache.conf contains: <BEGIN> Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> <END> I added those to a virtualhost where I am running mailman2.x, but I couldn't access any of the defined aliases: https://lists.my.site/mailman3/static/ - gives "You don't have permission to access this resource." Apache says AH01276: Cannot serve directory /var/lib/mailman3/web/static/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive I am stuck at that point ... -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 1 month

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-01-30 12:08:10 -0800 (-0800), Mark Sapiro wrote: [...] > Domains can be created via Postorius or via the Mailman Core REST API that > postorius uses or implicitly by the `mailman create` command when creating a > list in a new domain. However, none of this can create a new site. You can > do this through the Django admin site at sites/site/add/. > > See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you > can use to do this programmatically. Thanks, I'm still doing my best to wrap my brain around how Django uses database migrations to create sites (seems like a very strange use of a migration, I'm only accustomed to seeing them applied for database schema updates). Once I work out how to script site creation, I'm still not completely finding the explanations I need for how to map them to domains in Mailman though. The Mailman documentation about domains says "Domains are how Mailman interacts with email host names and web host names" but doesn't actually go on to say (that I can find anywhere) how it actually associates them. I can see in the API docs that a POST to the domains endpoint will create a new domain with a specific mail_host FQDN, but there's some association somewhere of that to a web host (Django site), right? How is that set or manipulated through the API? Or is that something which has to be set directly in Django's data structures instead? To recap, on creation of a mailing list server I want to populate it automatically with multiple lists on different domains and have dynamic SITE_ID=0 domain guessing performed so that the correct site name and list filtering is performed depending on which domain name is used in a URL the client requests. I believe I need to have the automation perform the following steps: 1. Instantiate the Mailman installation and run initial migrations with SITE_ID=1 in order to avoid the problem mentioned in the docs about not using SITE_ID=0 until the tables have been populated, then switch the settings.py to use SITE_ID=0 once done. 2. Create the individual sites I need in Django (Mailman web hosts) by creating and applying database migrations. 3. Create the individual domains I need in Mailman (Mailman mail hosts) through its REST API. 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond to what web hosts. As I said, I'm still trying to understand how to make step 2 happen (Django has a steep learning curve for me), but beyond that I'm unsure how to do step 4 at all. I can do all of this through the WebUI of course, and have confirmed that it works as expected when I do, I'm just trying to work out the automation so that our other sysadmins don't have to perform these steps by hand the next time we need to rebuild the server. Thanks again for all the help so far, and for any additional insight anyone may have into how I can correct my mental model of all this. -- Jeremy Stanley

3 years, 6 months

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 1:31 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/14/22 11:04, Odhiambo Washington wrote: > > So I thought I have everything running. Fresh install of MM3 on > > Ubuntu-22.04. > > > > I have created a list in postorius - it has the same name as my old list > in > > MM2. > > > > [image: MM3.png] > > Your image didn't make it through content filtering. > The image only showed a listing of the MLs that I created via postorius. > > What is the fully qualified name of the list > skunkworks(a)lists.my.co.ke > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 > skunkworks(a)lists.my.co.ke /var/list/lists/skunkworks/config.pck > > Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE > > Try 'mailman import21 -h' for help. > > > > Error: No such list: skunkworks(a)lists.my.co.ke > > Apparently the list you created is not named skunkworks(a)lists.my.co.ke Apparently so, because: mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists No matching mailing lists found mailman@lists:~$ Which is surprising, given this: https://imgur.com/a/LPrh42K > > What am I missing? > > The Mailman 3 list skunkworks(a)lists.my.co.ke including that exact domain > must exist in order to import to it. Try > > /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke root@lists:/home/wash# su - mailman mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/commands/cli_lists.py", line 184, in create mlist = create_list(fqdn_listname, owners) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/app/lifecycle.py", line 100, in create_list call_name(config.mta.incoming).create(mlist) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 93, in create self.regenerate() File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 133, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, 127, Key has expired Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

4 years, 1 month

[MM3-users] Re: What to backup?

by Alain Kohli

Thanks for the great explanation, that helped a lot! I'll try to work on that issue if I find some time. In the meantime it would be neat to try to clean up the old messages right before the backup. How can you distinguish messages that have been moderated already? I couldn't really find that in the database or the models. On 5/26/19 8:18 PM, Mark Sapiro wrote: > On 5/26/19 7:00 AM, Alain Kohli wrote: >> I have noticed that especially the var/messages directory has a rather >> considerable size compared to the rest. What exactly is this for and >> what would be the consequences if that was lost? > > When a message is held for moderator approval, a pickle of the message > is stored in the var/messages directory and an entry pointing to it is > made in the message table in the database. An entry is also made in the > list's pending requests. These are required so the held message can be > handled. > > There is an issue in that when these messages are handled these aren't > removed. See <https://gitlab.com/mailman/mailman/issues/257>. > > Thus, most of what's in the var/messages directory is old, but there are > also currently held messages there that would be lost. > > You could periodically remove older messages, but this would leave > entries pointing to them in the message table in the database which > could cause errors but probably not. > > The real solution is a fix for > <https://gitlab.com/mailman/mailman/issues/257>. > >> And more generally, would not backing up var/ at all only result in the >> loss of some short term data (e.g. messages that are held or currently >> processed) or would long term data also be lost? Or in other words, what >> exactly would be non-recoverable if that isn't backed up? > > That depends in part on what your backend database is. If it's SQLite, > the database is probably in the var/data directory. If not, you need to > be backing up the MySQL or postgreSQL mailman database. > > var/archives contains archived messages for the 'prototype' archiver and > messages that are queued for hyperkitty. > > var/cache contains a cache of recently used templates. > > var/data may contain a SQLite database and may contain Postfix mappings. > The Postfix mappings can be regenerated by the `mailman aliases` command. > > var/etc may contain your mailman.cfg if you don't point to a different one. > > var/lists contains accumulated messages for the next digest for your lists > > var/locks contains locks and should probably not be restored from a backup > > var/logs contains Mailman's logs. > > var/messages is discussed above. > > var/queue contains Mailman's current queues. Except for 'shunt' this is > all things currently in process. > > var/templates may contain custom templates. > > Also, I didn't mention it before, but your Django settings.py and > settings_local.py should also be backed up. >

7 years, 3 months

[MM3-users] Re: Post-installation documentation?

by David Newman

On 11/25/21 1:16 PM, Mark Sapiro wrote: > On 11/25/21 10:56 AM, David Newman wrote: >> >> Thanks for this. After setting these variables and restarting mailman3 >> and mailmanweb, the mailman user still cannot find a hyperkitty_import >> command (neither can root, btw). Again, I installed MM3 and >> Django/Postorius/Hyperkitty using the venv and web docs previously >> referenced. > > > Don't run mailman or django admin commands as root. This causes issues > when files are created by root and can't be read by mailman. Understood, thanks. I'd only tried root to determine if there was a permissions issue, where hyperkitty_import really did exist but wasn't available to the mailman user. > > What django admin command are you running? As the mailman user, with venv activated: (venv) mailman@lists:~$ hyperkitty_import -l testlist(a)lists.domain.com /var/lib/mailman/archives/private/testlist.mbox/testlist.mbox 'testlist' and 'lists.domain.com' are redactions; they are correct in the given command, but the command fails because the system can't find hyperkitty_import. (BTW Also, because I'm looking to migrate from Mailman 2.1 installed from Debian packages, all the 2.1 stuff is owned by the 'list' user. I'd changed ownership of the above private archive to mailman:mailman for the command not to complain about permissions. > If you don't set > DJANGO_SETTINGS_MODULE in the environment and you have activated your > virtualenv and run `mailman-web` as the django admin command it will set > /etc/mailman3/settings.py as the settings. I'd run these two environment commands as the mailman user with virtualenv activated: export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/etc/mailman3/settings.py Am I being overly literal here with 'settings' in that first command? Asking because 'mailman-web check' runs clean before running these commands and returns this error afterward: ModuleNotFoundError: No module named 'settings' Either way, the hyperkitty_import command still isn't found. >> On the plus side, all lists now appear in the admin web page. However, >> lists created from the admin page do not appear in a site list page, >> even though all lists are in the same site/domain. > > > By default, only lists that you are owner, moderator or subscriber for > are shown. What if you click Filter by Role and select All? Same result. In this case, the ID of the admin and list owner are the same. > > >> Finally, how to make these exports permanent? I did not see this >> covered in the migration doc above. This is on a Debian system where >> the mailman user's shell is bash. Is this simply a matter of adding >> environment variables in the mailman user's .bashrc file? > > You can do that but as I note above, if you run `mailman-web` you > shouldn't need to. You can add a `source /opt/mailman/venv/bin/activate` > command as mentioned at > https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtua…. Yes, this is what I have in mailman's .bashrc file. I'd followed that venv doc for initial installation, and it activates the virtualenv whenever launching a shell for mailman. dn

4 years, 9 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/08/02 19:02, Mark Sapiro wrote: > On 8/2/24 09:43, Roland Giesler via Mailman-users wrote: > >> Ah, so I just have to figure out why the LMTP runner is not running. > > Stop Mailman core and then start it. You must stop and then start as > opposed to restart. > > If lmtp runner is not running after that check > /var/log/mailman3/mailman.log for possible reasons. You can also check > that log for reasons why it isn't currently running. > > You can also check /var/log/syslog* for events like out_of_memory that > might have killed it. I do now have the lmtp runner on port 8024. # netstat -tunap | grep 8024 tcp 0 0 192.168.161.103:8024 0.0.0.0:* LISTEN 46730/python3 In mailman.cfg I set it to listen on the LAN address instead of 172.0.0.1, since I'm expecting mails from my external MTA server. In the logs of the MTA I see this however: warning: do not list domain fast.za.net in BOTH virtual_mailbox_domains and relay_domains Mailman creates these entries, but postfix doesn't like it. I don't see any mail delivered to the mailman yet. Is this the problem? In the MTA postfix main.cf: relay_domains = hash:/etc/mailman3/data/postfix_domains cat /etc/mailman3/data/postfix_domains # AUTOMATICALLY GENERATED BY MAILMAN ON 2024-08-05 07:20:17 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. fast.za.net fast.za.net and also local_recipient_maps=$virtual_mailbox_maps, hash:/etc/mailman3/data/postfix_lmtp cat /etc/mailman3/data/postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2024-08-05 07:20:17 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @fast.za.net domain. test(a)fast.za.net lmtp:[192.168.161.103]:8024 test-bounces(a)fast.za.net lmtp:[192.168.161.103]:8024 test-confirm(a)fast.za.net lmtp:[192.168.161.103]:8024 test-join(a)fast.za.net lmtp:[192.168.161.103]:8024 test-leave(a)fast.za.net lmtp:[192.168.161.103]:8024 test-owner(a)fast.za.net lmtp:[192.168.161.103]:8024 test-request(a)fast.za.net lmtp:[192.168.161.103]:8024 test-subscribe(a)fast.za.net lmtp:[192.168.161.103]:8024 test-unsubscribe(a)fast.za.net lmtp:[192.168.161.103]:8024 Then there's: virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf cat /etc/postfix/virtual-mailbox-domains.cf dbpath=/home/user-data/mail/users.sqlite query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 FROM aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM auto_aliases WHERE source LIKE '%%@%s' When I run that query in sqlite3, it returns no records, so I'm not sure how this is supposed to work. %s to me means that first argument, so is this used in python and then %s is the argument sent to this query? The bottom line of this all is that a new signup message that I reply to is being received by box2.gtahardware,co.za, but not by mailman3 and I cannot find the point where it fails in the logs.

2 years, 1 month

Search results for query "sapiro"