Search results for "Postorius" - Mailman-users

Re: Deactivate list without deleting it?

by Barry Warsaw

On Jan 14, 2018, at 09:45, Colin Watson <cjwatson(a)ubuntu.com> wrote: > > I'm experimenting with a port of Launchpad's mailing list infrastructure > to Mailman 3. If Barry's reading, he may remember that this is no > trivial task, so I'm very definitely not promising that it will be done > any time soon. :-) For those of you not up on your history, this is interesting for several reasons. I was originally hired by Canonical 11 years ago to integrate Mailman with Launchpad. At the time Launchpad was not free software, so a lot of the design of the integration had to work within those constraints (LP was released under the AGPL in 2009 IIRC). At the time it was painful, especially because it had to keep two completely databases in sync in both directions — not an easy task! Add to that the fact that Mailman 2.1 doesn’t really have a database, just a bunch of pickle files. :) I’m proud that the mailing list feature of Launchpad eventually became pretty darn solid, with much credit to Colin, Curtis Hovey, and many of my other wonderful former colleagues on the Launchpad team and at Canonical. This experience also heavily influenced my thinking about the design for Mailman 3, and led directly to the REST-based API. Launchpad has a REST API, spearheaded by Leonard Richardson, who literally wrote the O’Reilly books on web services. And while there were some compromised on “pure” REST in Launchpad, the discussions we had at that time committed my thinking to as pure an approach as I was capable of doing. > However, for the most part it looks relatively > tractable with the aid of the plugin improvements in Mailman 3.2.0; I > have the rough outline of a plugin that implements much the same feature > set as our current pile of monkey-patches against Mailman 2.1 in a much > nicer way. Very cool! You’ve provided some clarification in a follow up, and I’ll respond there. Apologies for being a little disjointed. One of the things that may really help you, but which doesn’t exist in a fully baked way in Core is the ability to set web hooks for various events. Core does have an event notification system (via zope.events) and that’s used to inform other parts of the Core about things like subscriptions/unsubscriptions, etc. Where web hooks would be useful is if some event in Core needs to inform Launchpad of that event. However, it’s possible that this falls under the plugins you’ve thought about - and while not general purpose, I’m positive you could do the same kind of MM3->LP notifications that you might find necessary, in custom plugins. > Ideally, I'd like mailing lists to have a "deactivated" state in > addition to full deletion. In this state, the list would appear > nonexistent for most purposes: incoming email would be rejected, I forget whether LP uses Exim or Postfix. At least for the latter, it would be fairly easy (if involving a database migration) to include an “active” or “enabled” flag which would be consulted when regenerating the Postfix transport files. I would add this to the MailingList model and make it available through the REST API. Then the LP team admin can toggle this on and off as desired. I also wouldn’t use the IArchiver interface for disabling HyperKitty access to the archives, but I’ll respond in more detail in the next follow up. > Postorius would deny its existence, etc. You’ve clarified that Postorius isn’t needed for Launchpad, since it provides what effectively takes it places in the simplified administration u/i. Cheers, -Barry

8 years, 6 months

Re: remove website example.com via django interface

by Alexander Inzinger-Zrock

Am 26.03.25 um 16:23 schrieb Odhiambo Washington: > > > On Wed, Mar 26, 2025 at 6:09 PM Alexander Inzinger-Zrock via > Mailman-users <mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org>> wrote: > > remove website 'example.com <http://example.com>' via django interface > or > "how to rush jourself off your feet" > > > **Disclaimer: don't try this at home** > > > in believe to replace the display of 'example.com > <http://example.com>' in the > postorius-webinterface i logged into django-interface, under 'website' > (very bottom of the left menu) i added my new website and then deleted > 'example.com <http://example.com>'. > > Result: i can't access my webinterfaces any more, neither django nor > postorius. > > > Questions: > > 1. Does somebody know about the correct approach to change the > displayed > url in the postorius-webinterface? > > > The displayed URL should be the one you configured in Nginx or Apache. > example.com <http://example.com> is usually SITE_ID=1. > It's possible to rename it in Django admin UI to whatever you want - > like mywebsite.name <http://mywebsite.name> > > 2. does somebody perhaps know how to revert those removal via CLI or > other ways? > > > ``` > SQL: select * from django_site; > ``` > Whatever ID shows for the one you created, stick that ID to settings.py > and restart mailmanweb. works again. Thank you so much. for anyone stumbling accross, 1. setting in settings.py is: #: Current Django Site being served. This is used to customize the web host #: being used to serve the current website. For more details about Django #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ SITE_ID = 2. and correct database would be 'mailmanweb' (according to manual). greetings, aiz > > -- > 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 > <http://www.catb.org/~esr/faqs/smart-questions.html>]

1 year, 4 months

Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

3 years

Re: Auto discard after max_days_to_hold not working.

by Mark Sapiro

On 4/28/25 07:59, Stephen J. Turnbull wrote: > > This doesn't seem to be exposed in Postorius. It's not all that old > in Mailman 3 (April 2020) so it's possible that it is not moved from > Mailman 2 to Mailman 3 by the migration scripts. This is comments in postorius/forms/list_forms.py ``` # TODO: Expose after this functionality actually works in Core. # max_days_to_hold = forms.IntegerField( # min_value=0, # label=_('Discard held posts after'), # required=False, # help_text=_( # 'No. of days after which held messages will be automatically' # ' discarded.')) ``` `mailman import21` will import the setting, but per the above comment, it doesn't yet work. The setting exists and is exposed in REST, but it appears it is not actually implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/21/20 6:21 AM, r.woithe(a)callassoftware.com wrote: > Hello, > Version: > Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) > Mailman Core API Version 3.0 > Mailman Core Python Version 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0] > > But the Error was there allready before the update have been done. That means the Mailman-Core changed but the error persisted. What is the full traceback from this error? Mailman 3 has not supported Python 2 since 3.0 beta4. It is not clear what is invoking /usr/lib/python2.7/httplib.py, but if it is Mailman core, something is seriously amiss in the way it's installed. Even Postorius and HyperKitty have not supported Python 2 for quit some time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 6:05 PM, William Oliver wrote: > > So.. if I need to do it myself, can you point me to what file I need to > create/modify in the /opt/mailman/mm tree to set up the alias? Assuming you have Postorius working, just go to the Domains view, edit your domain and add an Alias Domain. Otherwise, you can do this in mailman shell, e.g. ``` $ mailman shell 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. >>> dm = getUtility(IDomainManager) >>> d = dm.get('example.com') >>> d.alias_domain = x.example.com >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: message duplication and an NNTP related error

by Mark Sapiro

On 2/23/26 13:56, Laurens Kils-Huetten wrote: > > I have recently installed mailman3 on a Debian trixie system. How? By following <https://docs.mailman3.org/en/latest/install/virtualenv.html>, installing Debian packages or ?? > While I managed to set up most of it (the mailing lists, postorius and > also a working gateway to our inn2 news server) I'm seeing a weird > duplication of messages, that seems to be related to the error > messages posted below. What is the result from the command `mailman conf -s nntp`? What are all the settings for the list at Settings->Newsgroup Gateway in Postorius? > When I switch off gating to nntp the duplication stops. Also only mail > messages are duplicated, not the postings on the news server. > > Any pointers as to what to look into, or how to remedy this problem > are greatly appreciated :) > > Thanks, > > Laurens > > here come the error logs: > Feb 23 20:39:08 2026 (2776528) ACCEPT: <e4938b85cbd75c0b04867514fc0b8ad9(a)betola.de> > Feb 23 20:39:10 2026 (2776528) ACCEPT: <e4938b85cbd75c0b04867514fc0b8ad9(a)betola.de> The above duplicate post comes before the following error, so I don't think the error is related to the duplication. > Feb 23 20:39:12 2026 (2776530) <e4938b85cbd75c0b04867514fc0b8ad9(a)betola.de> NNTP error for test(a)grenzland.club > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/runners/nntp.py", line 94, in _dispose > conn.post(fp) > ~~~~~~~~~^^^^ > File "/usr/lib/python3/dist-packages/nntplib/__init__.py", line 916, in post > return self._post('POST', data) > ~~~~~~~~~~^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/nntplib/__init__.py", line 909, in _post > return self._getresp() > ~~~~~~~~~~~~~^^ > File "/usr/lib/python3/dist-packages/nntplib/__init__.py", line 492, in _getresp > raise NNTPTemporaryError(resp) > nntplib.NNTPTemporaryError: 441 Can't set system Injection-Info header field This is a response from your nntp server. Note: the above traceback indicates that this nntplib is standard-nntplib from PyPI which is normally only installed if Python is 3.13. If this is Python 3.13 and you have installed Mailman from other than the head of the gitlab branch, see <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 11:21 PM, David Partain via Mailman-users wrote: > > I removed /usr/share/mailman3-web/settings_local.pyc quite some time > ago, have restarted both mailman3 and mailman3-web numerous times since > then, and today I restarted uwsgi this morning. > > No new settings_local.pyc has yet been created. Ideas..? No. Restarting Mailman core won't help with this. I don't know what's involved in restarting mailman3-web, but I think that restarting it and uwsgi should be enough and a new settings_local.pyc would be created the next time a django process is invoked (e.g., by visiting a Postorius or HyperKitty web page). If this isn't happening, I don't know why. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Flo

On 8/25/25 23:36, Mark Sapiro wrote: > On 8/25/25 12:42, Flo via Mailman-users wrote: >> Hi, >> >> I have setup in Debian Trixie mailman3-full and came that far, that I >> have created a mailing list. I can sent emails to the members. > > Your primary support resource for the Debian package is Debian. See > https://wiki.list.org/x/12812344 > That's right. > > You need to add 'django.contrib.humanize' to the INSTALLED_APPS list in > settings.py. If you Debian packages don't do this, it should definitely > be reported to Debian. > In /usr/share/mailman3-web/settings.py there is: INSTALLED_APPS = ( ... 'django.contrib.humanize', ... ) And POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8001' I think this has also something to do with it. But looks correct for me. Flo But maybe the path

11 months, 1 week

About the path forward [was: ... regarding message acceptance]

by Stephen J. Turnbull

I'm not Mark, but .... :-) "Plans", you ask? Hmm.... Pawel Grzywaczewski writes: > Any plans to implement message acceptance based on another list? I think that most Mailman 2.1 features are plausible proposals for Mailman 3. While we don't make decisions based on user voting, we do care about user requests. If you want to make a formal request, post a request for enhancement (ie, issue) on our GitLab issue tracker, and post a link here so other interested people can follow it. > What about adding list1 as member to list2? In Mailman 2.1 there > was an 'umbrella' feature I think it doesn't exist in Mailman3. > Any plans to add it? Same as above. I don't know Mark's plans, but he's been active on these lists. I myself hope to have some time for development later in the summer, but I've been away from the code for quite a while, and have at least two prior projects I've expressed interest in. I have no idea about Abhilash or Terri's time, except that they're always busy, and there are a couple of other developers who might drift back in at some point if something exciting starts happening. However, these kinds of additions described above are somewhat more complicated in Mailman 3 than they were in Mailman 2. We have added the ability to identify groups of lists as domains (and therefore have multiple lists by the same name if they are each in a different domain), and the ability to identify groups of email addresses as users. This means that there are more opportunities for unfortunate things to happen. For example, a user might have a particular address for posting to a particular list, and be unhappy if they were accidentally "unmasked" when they posted by a different address, and that post was accepted because those addresses are both owned by the same user. Whether you think this one is a "real problem" or not, we need to do more than a little thinking about such things as we improve Mailman. We missed the window for GSoC this year. We've had excellent success in getting students (I don't think we were ever denied a slot we asked for), so prospects for next year are good. I myself am looking at mandatory retirement in a couple of years, and am planning to ramp up development/consulting activity over this period. So I know a year is a long time, but we are actively supporting existing features, and intend to continue development for the foreseeable future. Finally, Brian Carpenter and EMWD are actively developing alternatives to Postorius and HyperKitty. (Affinity and Empathy, respectively; I believe Affinity is already in beta, Empathy I don't know about status). You can find out more about them in the Mailman Developers <mailman-developers(a)python.org> archives and in the archives of this list. These are independent friendly projects, not hostile forks. You may find them to provide more straightforward access to configurations you want, although they do depend on Mailman core for much "back office" functionality, and obviously they're less mature than Postorius and HyperKitty. But they have the advantage of targeting a much more mature Mailman core, so they'll catch up fast. EMWD hosts a lot of Mailman lists and hosts, so I for one would consider a request for features from Affinity developers to be representative of many list owners.[1] Footnotes: [1] Not to deprecate Empathy, but the relationship between core and any archiver is pretty much "arm's length". Archiver features are mostly independent of the core.

6 years

Mailman-users search results for query "Postorius"