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

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 03/17/2017 03:59 AM, Anders Nilsson wrote: > > I do have problems with some lists occasionally going into some kind of > shunt mode, where alla mails sent to them gets shunted. In the Mailman > log I get entries for each shunted email: > > Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows > were found for one_or_none() ... > File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", > line 70, in process > archiver_set = IListArchiverSet(mlist) mailman/handlers/rfc_2369.py is adding the List-* headers. Here it is looking up all the archivers that are enabled for this list. ... > File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", > line 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() and here we are in code that is trying to see if there are any system enabled archivers that are not already associated with this mailing list and if so, add them to the archivers enabled for this list. The above is the last line of exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() which is querying the archivers enabled for this list for the name of a system enabled archiver and expects to find at most one entry > File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", > line 2733, in one_or_none > "Multiple rows were found for one_or_none()") but finds more than one. > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > Mar 17 11:54:11 2017 (6217) SHUNTING: > 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 So the cause is there appear to be multiple database entries for this list and some archiver name, but I don't know how that can happen. I have not seen this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 10/04/2018 12:19 AM, Henrik Rasmussen wrote: > > Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. 3.2.0a1 was never an 'official' release. It could be any HEAD version between June 4, 2017 and Jul 10, 2018. The --periodic option was added April 28, 2018. > When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). Are there accumulated messages for the digest when you run the command?. I.e., is there a var/lists/listname.lists.example.com/digest.mmdf file with messages in it? Are there list members receiving digests? If so, there should be something in Mailman's smtp.log. > As I understand, using --sent should send a digest immediately (except when used with --dry-run). Correct,if there is one to send. > As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? It is Kilobytes. > Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? The digest size threshold has no effect on whether or not a digest is sent by 'mailman digests'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Add domain to Mailman, can't create list with that new domain

by Mark Sapiro

On 10/17/24 13:41, Andy Matthews wrote: > > and then rebuilt kubernetes, I found that when I hit the API to get all lists, the list mailman(a)foobar.com existed, and was the default. I could create lists against foobar.com but could no longer create them against mydomain.com. > > So it looks like when you're initially configuring mailman you have to create your first mailing list, and whatever domain you use becomes your "primary domain". I don't know where this is documented, but could someone confirm this behavior for me so that I know that I'm on the right path? And previously you wrote: > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> Did you commit() after doing the above? I'm not sure how kubernetes fits in to this, but `mailman create` for a list in an unknown domain will create the domain unless -D or --no-domain is specified. See `mailman create --help`. Mailman core has no concept of `primary domain` which is why it's not documented. Are you creating lists via REST as you posted previously. If so, the domain must exist, but if you created domains as above, they should exist as long as you committed your changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Mark Sapiro

On 2/5/25 13:03, Ron / BCLUG wrote: > > I've been digging into MM3 resource usage vs MM2 and have been > wondering: are there any other runners that can be disabled, or invoked > via cron job to run every $interval then exit again? The task runner is a candidate. It only actually does anything at intervals defined by the run_tasks_every setting in the [mailman] section of mailman.cfg, default 1 hour https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…, but it still wakes up and comes into memory every sleep_time which defaults to 1 second. If just having the runners sleep longer works for you, you can set, e.g. ``` [runner.task] sleep_time: 10m ``` to only wake up the task runner every 10 minutes. If you really want it gone, you could put ``` [runner.task] start: no ``` in mailman.cfg to prevent starting it as a persistent runner, and make a python script like: ``` #!/opt/mailman/mm/venv/bin/python from mailman.core import initialize from mailman.runners.task import TaskRunner initialize.initialize() TaskRunner('task')._do_periodic() ``` and run that periodically via cron. I'm not certain, but I think task runner is the only runner for which it's that simple. > Second question, similar topic but MM2: how to disable NNTP? (if that's > what this is doing): > > /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Put this in mm_cfg.py del QRUNNERS[QRUNNERS.index(('NewsRunner', 1))] or if you already have some modifications to the QRUNNERS list in mm_cfg.py, make the appropriate adjustment to remove the NewsRunner entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/5/22 14:46, Allan Hansen wrote: > I asked the poster of one message what he had done. > Apparently, he had put the list address (just one list, according to him) in the Bcc: field. > The message was then held for moderator approval and, when approved, sent out without a body. > > Another message was stopped because it did not have a subject field. > Again, it was approved and then sent out without a body. I just did a test of a message with no Subject. It was held for no subject and when accepted was delivered. in all cases, the notice to the admin, the message in the held message view, the message delivered to the list members and the archived message; the message body was intact I did the same test with implicit destination with the same result. I even tried posting the same message to list(a)example.com and list+z(a)example.com resulting in two held messages which I accepted one at a time and the only difference was only the first accepted message was archived by HyperKitty because of the duplicate Message-ID:. Both were archived with content in the prototype archive. If you are really on Mailman 3.3.7, your result should be the same. Even on 3.3.5 which first introduced the possibility of content being lost, this shouldn't happen on posts to a single list You could try these same tests on a test list on your installation. I would be interested in your result. If it is the same as mine, there must be some other condition affecting this although I don't know what it would be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

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

by 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>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:04 AM, Andrew Bernard wrote: > > Where is the Django config area for the > pip installed modules? It is this that I find obscure. The short answer is wherever you put it. If you look at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which Abhilash mentioned, you'll see what I do. Abhilash mentioned creating the virtualenv in /opt/mailman/. I actually have another level below that, /opt/mailman/mm/, but this is only for convenience to separate things as I also have directories for the git branches and for local patches, so if we are just working with /opt/mailman/, you can put your Django settings.py and settings_local.py files there. I also put various other config things there like Mailman's var/ directory Django's static/ directory mailman.cfg mailman-hyperkitty.cfg gunicorn.conf and an empty __init__.py file so Django can import settings. Then I create a /opt/mailman/bin/ directory and in that I put small bash scripts to run things. for example: opt/mailman/bin/mailman contains #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ opt/mailman/bin/django-admin contains #!/bin/bash . /opt/mailman/venv/bin/activate cd /opt/mailman/ export PYTHONPATH=/opt/mailman/ export DJANGO_SETTINGS_MODULE=settings django-admin $@ and opt/mailman/bin/gunicorn contains #!/opt/mailman/venv/bin/python import sys sys.path[0:0] = [ '/opt/mailman/', ] import os os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' import gunicorn.app.wsgiapp if __name__ == '__main__': sys.exit(gunicorn.app.wsgiapp.run()) Then I use those commands to run Mailman, Django and gunicorn. Some of this may not be directly applicable to you, but I hope it gives you the basic idea. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: How to change the language in mailman3

by Mark Sapiro

On 7/17/20 9:44 AM, Massimo Zappalà wrote: > Hi everyone, > Mark thanks for the reply. > My installation was done on Debian Buster by installing the mailman3-full package > > I can't find the path you indicated: >> Mailman core in mailman/messages/ >> Hyperkitty in hyperkitty/local/ >> django-mailman3 in django-mailman3/local/ >> postorius in postorius/local/ > Maybe some packages are missing? I doubt things are missing. I can't keep track of where all the downstream packages put things, but look in /usr/lib/mailman and/or /var/lib/mailman or use tools like `find` or `locate`. >> To set language for Django (i.e. hyperkitty and postorius) see >> https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-di.... > What are the files to be edited? settings_local.py >> For Mailman core, set [mailman] default_language: in mailman.cfg. > Ok Done > >> You also need to (re)generate the .mo file which can be done with the >> generate_mo.sh script. > I can't find the script It probably isn't included in the Debian package. This is what it does. #!/bin/bash # This script generates .mo files from all the .po files in the source. echo 'Generating mo files for GNU Mailman ...' for file in `find -name 'mailman.po'` do echo $file msgfmt $file -o ${file/po/mo} -v done >> For Django, you need to generate .mo files with >> django_admin compilemessages > Where should this be written? You give the compilemessages subcommand to whatever command you use for django-admin or manage.py or whatever the Debian package calls it. -- 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

[MM3-users] Re: mailman.log file owned by 'list' user

by Mark Sapiro

On 1/7/23 14:14, Mike Wertheim wrote: > I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 > that was done by someone else. > > Mailman is running as a non-privileged (non-root) user called 'xyz'. On the > day that Mailman was installed, that non-privileged 'xyz' user was able to > execute mailman commands successfully to create, view and modify lists. The Debian package uses 'list' as the Mailman User. Whoever did the installation apparently tried to change that to 'xyz' and did an incomplete job. > A couple of days later, when the 'xyz' user tried running those same > mailman commands, they failed with this error: PermissionError: [Errno 13] > Permission denied: '/var/log/mailman3/mailman.log' > > Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: > -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log > > When I did a 'ps' command, I saw that all of the mailman processes are > running as user 'xyz'. No processes were running as the user 'list'. > > It seems that some process is rotating the mailman.log file at midnight, > and the newly-created mailman.log is being owned by user 'list'. > > Can anyone explain why this is happening, and how to fix it? It is happening because the logrotate script (maybe /etc/logrotate.d/mailman3) sets the user to 'list'. change that to 'xyz'. Also sudo chown -R xyz:xyz /var/log/mailman3/ and wait for the next issue to arise. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/27/25 05:44, Kim Sunggun via Mailman-users wrote: > Hello, > > /opt/mailman/venv/lib/python3.9/site-packages/django/conf/global_settings.py:EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/settings/base.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' OK. > I installed mailman3 in rhel 9 based on https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > I set up Postfix as the MTA. I added the code as mentioned in the document. > > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = > hash:/opt/mailman/mm/var/data/postfix_domains These are good but not relevant to your issue. They affect delivery of incoming mail to Mailman. Your issue is with outgoing mail from Django. There are various settings that affect this SMTP connection as described at https://docs.djangoproject.com/en/5.1/topics/email/#smtp-backend The defaults are EMAIL_HOST = "localhost" EMAIL_PORT = 25 and for the optional settings EMAIL_HOST_USER = "" EMAIL_HOST_PASSWORD = "" EMAIL_USE_TLS = False EMAIL_USE_SSL = False EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = None Have you set any of those to other than default in your Django settings? If not, what do you get if you run this python snippet as the Mailman user ``` import smtplib connection = smtplib.SMTP(host='localhost', port=25) ``` If you have, you can specify them as args to smtplib.SMTP, e.g. ``` connection = smtplib.SMTP(host='localhost', port=25, username='...', password='...') ``` or if EMAIL_USE_SSL is True, ``` connection = smtplib.SMTP_SSL(host='localhost', port=25, username='...', password='...', ssl_keyfile='...', ssl_certfile='...') ``` See https://github.com/django/django/blob/ea1e3703bee28bfbe4f32ceb39ad31763353b… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

Search results for query "sapiro"