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

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 04:35, Thomas Stein wrote: > > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE This is a packaging issue in the Debian/Ubuntu package and should be reported to Debian. See the BREAKING CHANGE item in the 1.3.10 section at <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. You need to add `allauth.account.middleware.AccountMiddleware` to the MIDDLEWARE setting in your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > Is nntp common enough these days to be a useful default runner? > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > resources (yet another Python interpreter running) for a fairly edge > case of mailing list <--> nntp transits. You raise an interesting point. By default, the runner runs, but if there are no lists gating to usenet, its queue is always empty and it mostly sleeps between waking, finding its queue empty and going back to sleep. A more significant use of resources is every (default) 5 minutes spawning `mailman gatenews` which goes through a startup process and then looks at every list figuring out there's nothing to do. We could default mailman.cfg to contain `start: no` in the runner.nntp section so people would need to enable it if they wanted it. What do others think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/9/19 11:16 AM, kelly.close(a)lrewater.com wrote: > I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. > > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… Thank you for this. I'm sure it will be helpful. One caveat. The Mailman 3 package for Ubuntu 18.04 is core version 3.1.1. This version when used with the MySQL back end database can have a serious issue. It doesn't affect the PostgreSQL back end database, only MySQL and maybe MariaDB, and it is fixed in Mailan core 3.2.0. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Can't open PID file after start.

by Mark Sapiro

On 4/21/20 10:16 PM, Torge Riedel wrote: > Hi, > > today there were some package upgrades on my server for python3. Just to > be safe I did a "systemctl restart mailman" afterwards. Calling > "systemctl status mailman" gave me the following output: > ... > Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... > Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner > Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file > /opt/mailman/var/master.pid (yet?) after start: No such file or directory > Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. > > Should I treat the PID message as an info or is it an error and > something is now broken? The file is there (content is 24182) and > timestamp is from the time where I restarted mailman. It's normal and just info. The key is "yet?" The [Service] section in Mailman's systemd service file references /opt/mailman/var/master.pid as PIDFile and systemd looks for it before Mailman has created it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 10:49 AM, Mark Dadgar wrote: > > Here’s what I get when I attempt the above commands: > > root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell > Python 3.8.2 (default, Apr 27 2020, 15:53:34) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. The `django-admin` command that is being run doesn't itself point to your settings. In my case, I run django-admin via a wrapper that contains ``` #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ ``` The critical things are the exports of PYTHONPATH and DJANGO_SETTINGS_MODULE. The former is the path to where your settings module lives and the latter is its name without the .py extension. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: aborted connection

by Mark Sapiro

On 2/19/22 14:14, Sandor Dibuz wrote: > > It's the mailman quarterly cron job: > > # Every 15 minutes, gate messages from usenet to those lists which have > the gateway configured > */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman > gatenews; fi > > And I have no gateway enabled for any of them. Will have to find out > what mailman exactly does. And change MariaDB to verbose logging. First, If your Mailman core version is >= 3.3.5, you shouldn't be running gatenews via cron. Mailman's nntp runner runs it. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… But, that probably isn't it because in Mailman >= 3.3.5, running gatenews via cron should produce this error The gatenews command is run periodically by the nntp runner. If you are running it via cron, you should remove it from the crontab. If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the environment. However, since you have no lists using a news->mail gateway, you don't need to run gatenews at all so just remove it from the crontab. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: How to let mailman log every single email that it sends out?

by Mark Sapiro

On 9/9/23 09:13, Mohsen Masoudfar wrote: > Thank you, Mark, but Sorry, I don't see them there. > I read that the mta log level should be set to debug in order to see them. > When I send an email to a list with +3000 subscribers and need to see in the log email has been sent to each of those email addresses If you want to see individual recipient emails in /var/log/mail.log, the best way is to enable VERP in mailman. I.e., set ``` verp_delivery_interval: 1 ``` in the [mta] section of mailman.cfg. Then you should see entries like: > Sep 9 16:14:31 mail postfix/qmgr[1158516]: 7561EFC0A5: from=<mailman-users-bounces+mmasoudf=aaas.org(a)mailman3.org>, size=1276, nrcpt=1 (queue active) > Sep 9 16:14:33 mail postfix/smtp[1831181]: 7561EFC0A5: to=<mmasoudf(a)aaas.org>, relay=aaas-org.mail.protection.outlook.com[104.47.59.138]:25, delay=1.6, delays=0.01/0/0.35/1.2, dsn=2.6.0, status=sent (250 2.6.0 <169427602883.1158168.2180174954874478353(a)mail.mailman3.org> [InternalId=4823248279498, Hostname=IA1PR20MB6503.namprd20.prod.outlook.com] 10538 bytes in 0.177, 58.037 KB/sec Queued mail for delivery) in /var/log/mail.log for each recipient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: mail loops back to myself

by Mark Sapiro

On 6/9/25 05:06, Florian Sukup wrote: > > The setup has historic reasons. However I can eliminate reverse.rrr.com > completely and replace it by host.xxx.com. Right now reverse.rrr.com has > an A-record pointing to the host's ip address. Eliminating reverse.rrr.com completely and replacing it by host.xxx.com would be good. This will help. Also if I look up the A record for reverse.rrr.com either locally or at aaron.ns.cloudflare.com there isn't one. This will be moot if you replace reverse.rrr.com with host.xxx.com. >> What is the output from `postconf -n`? >> > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > append_dot_mydomain = no > biff = no > compatibility_level = 2 > inet_interfaces = all > inet_protocols = all > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/var/lib/mailman3/data/postfix_lmtp > mailbox_size_limit = 0 > message_size_limit = 0 > mydestination = localhost, localhost.localdomain, arvak This needs to include $myhostname Also, including reverse.rrr.com would help with your current setup, but instead you should just eliminate reverse.rrr.com completely and replace it by host.xxx.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 5 days

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > Hi, > > I have installed mailman3 with postfix. The server is working fine. To > protect the IPs from blacklisting, I want to relay all emails from > postfix/mailman to external SMTP servers like O365, Gmail, or our exchange > server. I would not recommend using O365 or Gmail as outgoing MTAs. I don't really know about )365, but I don't think Gmail likes you to send mail via a gmail server if it is not From: (or maybe envelope from or both) a gmail or googlemail address. > Could you please confirm is this possible. And how to do its configuration. It is possible and there are two ways to do it. You can configure this in Postfix to relay all outgoing mail via some other server. You can configure it in Mailman by setting in the [mta] section of mailman.cfg smtp_host: smtp_port: and presumably for authentication smtp_user: smtp_pass: Also see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… and following for other relevant settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:01 PM, maszap(a)tin.it wrote: > Thank you, > but using roundcube, i can send email to all domains. That doesn't mean Mailman can. > These are just the lines I added to /etc/postfix/main.cf > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp You may need to add relay_domains = hash:/var/lib/mailman3/data/postfix_domains to your postfix main.cf. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Look in Mailman's smtp.log. You are looking for messages like: <timestamp> (pid) <message-id > post to <list-id> from <poster> nnn bytes and <timestamp> (pid) <message-id > smtp to <list-id> for nn recips, completed in nn.nnn seconds If the 'nn recips' matches the expected number of list members, the message was delivered to the MTA for all the recipients. If it then wasn't delivered to some of them, that's an issue with the MTA. Check the MTA's logs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Search results for query "sapiro"