Search results for "Postorius" - Mailman-users

Re: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/26/23 11:29, Mohsen Masoudfar wrote: > > I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. > I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. DMARC mitigations were introduced in Mailman 3.1.0. They should be available in 3.1.1. They were first exposed in Postorius 1.1.0. Where are you looking for DMARC mitigations? > The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. > > I get in the logs messages like below with several Queue-ids: > > Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] > Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) > Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed This only says that some Amazon MTA has relayed a bounce to Mailman. It says nothing about why the message bounced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Shashikanth Komandoor

Thank you Mark for you response in time. On Tue, Aug 11, 2020 at 9:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > > I am currently automating a few things using the CURL commands but > only > > postorius related as of now. Now I have a requirement. > > > > I need to create a lot many users and their mapping email ids through > > Site Administration almost daily. But it is becoming to do the same > through > > Graphical Interface. > > > > So, I just want to know the CURL commands that can be used to create > the > > user accounts and email ids mapped to user accounts. > > The accounts you are talking about are Django accounts. You cannot > create these via CURL to the Mailman core REST API. > > You might find > <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 9 months

Re: Moderation not working?

by Mark Sapiro

On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: > > Hi Folks, > Running a shiny new instance of mailman3, as per the Debian package > (version 3.2.2) but the moderation doesn't seem to work. WE got > hit by a heap of spammers overnight, even though the 'hold for > moderation' bit is set for non-members (and now for members too). If the action for member posts was accept ot default processing at the time, perhaps the spam spoofed a member address in one of From:, Reply-To:, Sender: or the envelope sender, > Emails seem just to get straight through. Even now with both member and non-member actions set to hold? > Any advice on how to debug this? Would upgrading to a later version > using pip help? An upgrade probably won't help. This should work in your version. For one of the mail's, check all 4 addresses, From:, Reply-To:, Sender: and the envelope sender (available in the MTA logs). Note that Reply-To: and/or Sender: may have been modified by the list. Then see if any of those addresses matches a member or a non-member and what the specific moderation action is for that address. Also check the list's accept_these_nonmembers which is probably not exposed in your version of Postorius but which you can see via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: Add an extra option for "Delivery status" for users?

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/19/25 12:50 PM, Thomas Ward via Mailman-users wrote: > > We have a unique case where we have a user we want to disable for mail > > receiving, etc. for the reason "Disabled by IT Security Team" but I > > don't even know if it's possible to add a delivery status that is that > > custom. > At a minimum, you would need to add that choice to the > DeliveryStatus(Enum) in mailman/interfaces/member.py and the choice and > its description to the DELIVERY_STATUS_CHOICES tuples in > postorius/forms/fields.py. I don't know offhand if that would be > sufficient, or if more would be required. In postorius/views/user.py, you also need to add it to `UserPreferencesView,delivery_status_disabled_fields`. Otherwise users will be able to reenable from a security disable. In Mailman core, it's not absolutely necessary, but I think you should handle it the same as `by_moderator` in mailman/commands/cli_members.py, mailman/commands/cli_addmembers.py, and mailman/commands/cli_syncmembers.py. The mention of `by_moderator` in mailman/utilities/importer.py is irrelevant since the new `by_security` (or whatever you call it) doesn't exist in Mailman 2. In mailmanclient, you *may* want to update docstrings in mailmanclient/asynclient.py and mailmanclient/restobjects/mailinglist.py. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 1 week

Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple writable. SQLite version 3.16.2 2017-01-06 16:32:41 Enter ".help" for usage hints. BR Ugnius > On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >> >> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? > > No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. > > The doc mentions that it is "development" server[1][2]. > > [1]: # Run the Django's "development" server at localhost:8000 > [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project > > Perhaps it should be more descriptive about what does it mean. > >> >>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> >>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>> >>> You only need one of those, since they both do the exact same thing. Please remove >>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>> >>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>> May mailman processes are next: >>>> >>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>> >>>> Looks like there are no double. Nothing more is running. >>>> >>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> >>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>> >>>>> >>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>> > Hi. All the project installation is under the same user / path and >>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>> > to set in postorius, hyperkitty shows list as public) >>>>> > I have found work around - it is possible to change list as private in >>>>> > "admin" page. >>>>> > I started to get issues with runjobs after I have created couple of >>>>> > new lists with "no archive" option. >>>>> >>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>> >>>>> > >>>>> > If as owner user from project home I run: >>>>> > >>>>> > django-admin mailman_sync >>>>> > >>>>> > Traceback (most recent call last): >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>> > line 84, in _execute >>>>> > return self.cursor.execute(sql, params) >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>> > line 383, in execute >>>>> > return Database.Cursor.execute(self, query, params) >>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>> > >>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>> > "django-admin runjob new_lists_from_mailman" >>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>> > END TRACEBACK >>>>> > >>>>> > I did not find information how to fix this. It was worked without errors >>>>> > before. >>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>> > to work. >>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>> > again. >>>>> > I did not check other jobs, but I think what is related to database, >>>>> > will get errors. >>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>> > >>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>> > mailman creates database file size 0, django-admin runjobs start >>>>> > working, but of course postorius stops working. I did it for testing. >>>>> > I have returned this database file back, postorius started to work >>>>> > again, but django-admin runjobs does not work, error: "database read >>>>> > only". >>>>> > Please help me how to fix this issue. >>>>> > _______________________________________________ >>>>> > 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/ >>>>> > >>>>> >>>>> -- >>>>> thanks, >>>>> Abhilash Raj (maxking) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years, 8 months

Re: How to best disable message decoration for all lists defined for a domain

by Abhilash Raj

On Mon, Mar 18, 2019, at 2:27 PM, Ralph Seichter wrote: > Hello list. > > I have read [1] and [2], but I am not quite sure what the recommended > method is to completely disable message headers/footers and subject > modifications for *all* lists tied to a specific domain. Being new to > Mailman 3, I was actually surprised that there are no configuration > switches in the Web UI's settings for mailing lists that allow me to get > rid of unwanted message decorations. Yes, you are right and there aren't any ways to disable decorations. Can you please open an issue on Gitlab? As a workaround, you can set an empty domain level template for header and footer and remove the subject prefix. There is an issue open on Postorius[1] which doesn't allow empty templates, you need to add at least a blank space to create a template, which should result in similar looking message. [1]: https://gitlab.com/mailman/postorius/issues/331 > > [1] > https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/decorate… > [2] > https://mailman.readthedocs.io/en/latest/build/lib/mailman/rest/docs/templa… > > Thanks for your input. > > -Ralph > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 2 months

Re: High memory usage

by Stephen J. Turnbull

Philip Colmer writes: [Nothing about individual processes.] *Something* is using that memory. ps(1) should help identify it when your alarm is triggered, top(1) allows monitoring in realtime. For example, the information about the size of archives is interesting only if HyperKitty is using the memory. I guess it might be indicative of core usage since there's an awful lot of traffic, but core won't be reading archives into memory or anything like that, it doesn't even know or care where the archives are. It only knows where on the Internet to send messages so the archiver that lives there can add them. And I find it hard to imagine why Postorius would be consuming memory. > What is particularly curious for us is that we have four Mailman 3 > servers. Are these servers identically configured, or nearly so? If so, perhaps you can find "interesting" differences in memory usage across them. > Finally, and just FYI, we're using PostgreSQL for the database and > Xapian for the indexing engine. Either of those would be a weird cause. The point of an RDBMS is to store data in mass storage, although I suppose it's possible to write queries that would return huge quantites of data in memory. And the indexer is not a long-running process, as far as I know. So it should run, exit, and release memory. Again, if it's related to one of those it should turn up in ps.

4 years, 3 months

Re: Mass subscription and Delivery mode/status

by Odhiambo Washington

On Wed, May 14, 2025 at 10:48 AM Andreas Vetter < andreas.vetter(a)uni-wuerzburg.de> wrote: > Hello all, > we run a venv installation of "mailman postorius django-mailman3 hyperkitty > mailman-web". > When I mass subscribe (pre-verified) a new mail address into a list, the > Delivery mode appears as Regular in > /mailman3/lists/somelist.example.com/members/member/ > That is what I expect. > > When I click on the new mail address from there, i.e. > mailman3/lists/ > somelist.example.com/members/options/eimer@mail.org?role=member > the Delivery status is ----- instead of Enabled > and the Delivery mode is ----- instead of Regular. > In fact, all yes/no radio buttons are unset. > This is unexpected. What does ----- mean in that case? Is it unset and some > default (from the list?) is used? > You are looking at the subscriber-level configs. The ----- means that the list default settings are used. > After thinking another round about it: > Is the view > mailman3/lists/ > somelist.example.com/members/options/eimer@mail.org?role=member > only filled with values, when somebody (member, list owner or admin) > actively > set values and unfilled otherwise? > That's right. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year

Cannot locate manage.py

by Frank van den Heuvel

Hello, While following https://docs.mailman3.org/en/latest/migration.html, I want to execute: python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox Of course edited with values for my list. But I already get stuck in not being able to locate "manage.py". When I run "locate manage.py", I get: /opt/mailman/mm/venv/lib/python3.7/site-packages/django/conf/project_template/manage.py-tpl /opt/mailman/mm/venv/lib/python3.7/site-packages/example_project/manage.py /opt/mailman/mm/venv/lib/python3.7/site-packages/falcon/bench/dj/manage.py Which one is the right one? With kind regards and thanks for your work! Frank van den Heuvel BTW: This is a debian 10.2 with Mailman3: Django Version: 2.2.9 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.7.3 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/opt/mailman/mm/venv/lib/python3.7/site-packages'] Server time: Tue, 21 Jan 2020 08:34:45 -0800 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')

6 years, 4 months

Re: New messages not being archived

by Sarah H

The site is behind a proxy, yes. apache serves the client site redirecting 80 to 443 and serving SSL for the site then proxying to Nginx for postorius/hyperkitty at 8080. I've also tried going straight to 8080 bypassing the proxy internally using localhost or loopback to the same end result. The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius. Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver: I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines. [15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2" and at the start of the block: [15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname>

4 years, 10 months

Mailman-users search results for query "Postorius"