Search results for "Postorius" - Mailman-users

Re: Something wrong with my Hyperkitty base_url?

by Abhilash Raj

On Mon, Oct 2, 2017, at 12:29 PM, Andrew Hodder wrote: > from django.conf.urls import include, url > from django.core.urlresolvers import reverse_lazy > from django.views.generic import RedirectView > from django.contrib import admin > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('hk_root'))), > url(r'^hyperkitty/', include('hyperkitty.urls')), > #url(r'^postorius/', include('postorius.urls')), > url(r'', include('django_mailman3.urls')), > url(r'^accounts/', include('allauth.urls')), > # Django admin > url(r'^admin/', include(admin.site.urls)), > url(r'^hyperkitty/admin/', include(admin.site.urls)), > I removed the archives from the base_url, it still errors out just > with a different path:> > ValueError: <h1>Not Found</h1><p>The requested URL > /api/mailman/archive was not found on this server.</p>> > Now I should note, I'm running the web ui for hyperkitty on nginx with > http://FQDN/hyperkitty/ (where the non-/hyperkitty/ path would just go > to postorius). That is what you should be using for hyperkitty's `base_url` then: http://<whatever django is listening on>/hyperkitty/ > > > > > > Sincerely, > > Andrew Hodder Systems Administrator Support Operations, Afilias E- > mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 > 416.646.1541> > On Mon, Oct 2, 2017 at 3:22 PM, Abhilash Raj > <maxking(a)asynchronous.in> wrote:>> >> >> On Mon, Oct 2, 2017, at 12:17 PM, Andrew Hodder wrote: >> > Finally have everything stood up and working, except for >> > HyperKitty mailman plugin. I'm getting a path issue of sorts I >> > can see in the archiver.log (have it set to debug log level in the >> > mailman core): >> > >> > Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): >> > File "/opt/mailman/venv3/lib/python3.4/site- >> > packages/mailman_hyperkitty-1.0.2- >> > py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in >> > _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv3/lib/python3.4/site- >> > packages/mailman_hyperkitty-1.0.2- >> > py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in >> > _send_message raise ValueError(result.text) ValueError: <h1>Not >> > Found</h1><p>The requested URL /archives/api/mailman/archive was >> > not found on this server.</p> >> > >> > >> > My base_url in the mailman-hyperkitty.cfg: >> >> Can you show the contents of 'urls.py' in mailman-suite or whatever>> Django project you are using to deploy hyperkitty? That would >> give more>> ideas about whether the '/archives/' URL is valid or not. >> >> >> -- >> Abhilash Raj >> maxking(a)asynchronous.in -- Abhilash Raj maxking(a)asynchronous.in

8 years, 8 months

Re: Maximum number of recipients error

by Abhilash Raj

On Mon, Mar 18, 2019, at 10:57 AM, Mark Sapiro wrote: > On 3/18/19 10:40 AM, brian(a)emwd.com wrote: > > I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: > > > > "An error occured: Unknown attribute: max_num_recipients" > > > > I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? > > > It works for me. It was added by > <https://gitlab.com/mailman/postorius/merge_requests/358>, but it > requires Mailman core >= 3.2.1. What's in the docker image you're using? > This may be an issue for <https://github.com/maxking/docker-mailman>. It is an issue for images repo. I haven't yet updated to the latest releases, sorry! > > -- > 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, Abhilash Raj (maxking)

7 years, 3 months

Re: Notifying owners of membership changes but not moderators

by Mark Sapiro

On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Re: Moderator e-mails only going out once a day

by dgoldsmith＠sans.org

I am having a similar issue as Joe. Our Mailman 3 server is running on Rocky Linux 9.5. It is deployed using a Python virtual environment. (venv) [mailman@<server> shunt]$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.9.21 (main, Dec 5 2024, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] config file: /etc/mailman3/mailman.cfg <output trimmed> Mailman 3.3.9 Postorius Version 1.3.10 HyperKitty version 1.3.9 Postfix = 3.5.25-1.el9 (may have some newer bits backported into it - RHEL way) Django version = 4.2.13 Output of the for loop Mark provided above shows that all the lists on the server have admin_immed_notify set to True. Here is the activity from the mailman.log file when I send a message to the list and it gets held: Apr 21 19:11:37 2025 (2564) sans-faculty: DMARC lookup for dgoldsmith(a)sans.org (_dmarc.sans.org) found p=reject in _dmarc.sans.org. = v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email Apr 21 19:11:37 2025 (2564) HOLD: sans-faculty(a)mlm.sans.org post from dgoldsmith(a)sans.org held, message-id= <SJ0PR18MB5112D63A7D9F3851A4A6B0C0AEB82(a)SJ0PR18MB5112.namprd18.prod.outlook.com>: The message comes from a moderated member No further activity indicating it sends (or attempts to) a notice to the list admins/mods about a held message.

1 year, 2 months

Re: django 2.2.5 which is incompatible

by Abhilash Raj

On Mon, Sep 9, 2019, at 6:59 PM, Mark Dale wrote: > Hi, > > On Debian, in the process of setting up Mailman 3.3.0 I'm getting: > > $ pip3 install postorius > ... > django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have > django 2.2.5 which is incompatible. > ... > Successfully installed Django-2.2.5 ... This shouldn't be a problem and will be fixed in a future release. It is compatible with 2.2.5, but due to lack of a proper dependency resolution in pip, we don't end up with right version of a dependency. You can ignore this, for now. > > > > Which may or may not be causing a later error when creating superuser: > > ImportError: No module named django.core.management > What command did you run to do this? The error makes me feel you haven't activated either the virtualenv or you haven't installed things correctly. > > Am I missing the obvious somewhere? > > Thanks, > Mark > _______________________________________________ > 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)

6 years, 9 months

Re: Extracting mailing list users

by Jan Eden

On 2022-12-30 14:10, Odhiambo Washington wrote: > On Fri, Dec 30, 2022 at 1:57 PM Jan Eden via Mailman-users < > mailman-users(a)mailman3.org> wrote: > > > Hi, > > > > I would like to export users of my mailing lists including their full > > name (if present). The export button in Postorius creates a CSV with > > addresses only, and the tool bin/list_members mentioned in the > > [Mailman 2 FAQ] does not seem to be available in Mailman 3. > > > > I have full access to the server/database, so scraping the web interface > > with [Mark's script] seems unneccessary. Is there an SQL statement (or > > an equivalent of bin/list_members) to extract the data? > > > > Thanks, > > Jan > > > For MM3: > > (venv) [mailman@gw ~/mm]$ mailman members listname@domain --output > some_file.txt Thank you! This should have been obvious to me, but I never actually used the mailman command so far. On minor issue: All user names with non-ASCII characters appear with quoted-printable encoding (e.g. =?utf-8?q?J=C3=BCrgen?=). Is there a way to output UTF-8 instead of QP? - Jan

3 years, 5 months

Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 4:36 AM, alopez(a)ac.upc.edu wrote: > Hello, > I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. > I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. Because you are leaving mailman shell with exit() which doesn't commit changes. You deed to either explicitly commit with `commit()` or exit with control-D. Recent mailman shell will report in its banner Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. > On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? Your Postorius is too old to support alias_domain, and your Mailman core may be too - requires core >= 3.2.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: Ann: Mailman Core 3.3.5 is out

by Odhiambo Washington

On Wed, Sep 29, 2021 at 7:59 PM Brett Delmage via Mailman-users < mailman-users(a)mailman3.org> wrote: > On Wed, 29 Sep 2021, Eggert Ehmke via Mailman-users wrote: > > > Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I > would have > > to bypass the Debian installer. Or will there be Debian packages > available? > > Same question for Postorius 1.3.6 > > I am excited to see 3.3.5 with its many updates > available. Thanks to all the contributors. > > I would like to know this too, as I was just about to install parallel to > the Debian package(s). I expect there are many of us. > > Going forward, what is the best way to maintain a stable version of 3.3.5 > with security and defect fixes only, exluding new features? Is > picking and applying individual checkins on gitlab the only way? > If you install using the guide from Virtualenv Installation — Mailman Suite 3.3 documentation (mailman3.org) <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…>, then you can pretty much upgrade at will. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 8 months

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

by Abhilash Raj

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, 9 months

Re: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: > > I might also add the rule number or config filename:line, as in > > Header "{name}": rule in {file}:{n} matched value "{value}" > > This would be helpful when backtracking from a rejected message to the > cause. > > A sample expansion might be: > > Header "X-Spam": rule in foo.conf:83 matched value "yes" These rules are not in a configuration file. They are in the headermatch table in the database and the rules for a particular list are exposed on the Header filters tab in Postorius or at the REST lists/LISTNAME/header-matches endpoint. Perhaps something like {name}: header match rule, pattern "{pattern}" matched value "{value}" example: subject: header match rule, pattern "sex|long|list|of|other|bad|words" matched value "This is a post about filtering based on words like sex in the subject." but that could be just adding more clutter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Mailman-users search results for query "Postorius"