Search results for "Postorius" - Mailman-users

Re: HTML post only showing as attachment

by Mark Sapiro

Mark Sapiro wrote: > On 7/4/19 7:13 AM, andrew.bernard(a)gmail.com wrote: >> I have a post come in that is in HTML and has an >> image attached. It is distributed fine to email subscribers. Hyperkitty shows a blank >> message, with the in an html attachment, and the image as a jpg attachment. >> >> Why doesn't the text show in Hyperkitty? > > Because there is no plain text. Non text/plain parts including text/html > parts are "scrubbed" and stored aside. If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

Docker mailman3 delete social logins, did something change?

by bob B

I want to remove the social logins from mailman3 in docker. I found this info https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… but the link to the default shows *************** INSTALLED_APPS = [] DEFAULT_APPS = [ 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', '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', ] ***************** However when I go to the bug https://github.com/maxking/docker-mailman/issues/283 it shows ********* INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ******** The two examples are different so what should it be? I tried to add it in both ways and when I do I get bad gateway and he mailman website is broke. I have not setup any domains yet, just setup the admin password,. For example this breaks my website cat /opt/mailman/web/settings_local.py ALLOWED_HOSTS = ['127.0.0.1','localhost','REDACTED','REDACTED','REDACTED','REDACTED','REDACTED'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'REDACTED' EMAIL_PORT = 25 INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', ) ************************************************************************* And I have even removed anything? What should my /opt/mailman/web/settings_local.py look like?

5 years

Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/16/23 8:00 AM, eboltz(a)lhtservices.com wrote: > Installed MM3 on Debian 11, followed the steps from the MM3 website. > > I'm running into issues with Postfix headers. I can only get postfix to send emails to/from the list if I set the sender_canonical_maps in the main.cf file. I don't want to have to use that as I'd like the recipient to receive the following in their email header: <Subscriber> via <List Name> <FROM:LIST@DOMAIN>. But if I do the sender_canonical_maps, then the <FROM:LIST@DOMAIN> and all email headers are overwritten by the maps email address. In Postorius -> Settings -> DMARC Mitigations set DMARC mitigation action to Replace From: with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

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

Re: Functionailty of web host domains

by Mark Sapiro

On 06/15/2018 12:37 PM, Johannes Winter wrote: > > For each domain you can specify a "web host". But when I specify a > different one than the default for one domain, and make it accessible > with specifying `DJANGO_ALLOWED_HOSTS`, all mailinglists from the other > web hosts are also shown when I access the second site. > > So does this 'web host' option have a meaning, or is it just an alias > for the first site? This is a 'site' as implemented in Django <https://docs.djangoproject.com/en/2.0/ref/contrib/sites/>. I.e., it provides ways to do different things or retrieve different content based on site, but I don't see that either Postorius or HyperKitty makes use of it in this way. -- 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

Re: Showing sender as ... via ... list

by Wolfgang Bock

Dear Mark, many thanks. Works! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Samstag, 6. November 2021 16:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Showing sender as ... via ... list On 11/6/21 4:40 AM, Wolfgang Bock via Mailman-users wrote: > > Here is my question: > > What do I have to configure to get my lists to show the sender like in > this > list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org In Postorius go to Settings->DMARC Mitigations and set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to Yes. -- 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/

4 years, 10 months

Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/22/24 23:07, Gerald Vogt wrote: > > For testing I have set > > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' > > to the URL of our main domain, however, if I test an anonymous subscribe > through the list info page I still get the timeout error This will have no effect unless you delete and recreate the template in Postorius because simple changing the setting won't change the `uri` in the template table. > I can access > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… with curl and immediately get the response. Can you do that as the Mailman user?, e.g. ``` sudo -u mailman curl http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… ``` assuming the Mailman user is `mailman`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 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, 5 months

Re: global preferences

by Mark Sapiro

Again, please don't hijack threads. Post a new topic by composing a new message to mailman-users(a)mailman3.org, not as a reply to another list message. On 5/3/23 07:59, Christian via Mailman-users wrote: > Are checks and changes to global preferences for all lists to be made via a GUI or is it editing settings.py directly please? Thank you! You can set your global preferences via Postorius (select Mailman settings from the drop-down at the right of the top nav bar). These are the settings for the user that will apply if there is no applicable list-based or address-based setting. They are specific to the user. The defaults for these are defined in mailman/core/constants.py. They are Mailman core settings and have nothing to do with Django's settings.py. -- 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

Re: opt in/out for hidden lists

by Abhilash Raj

On Mon, Jul 1, 2019, at 4:04 AM, mailman3(a)malevil.cc wrote: > Is it possible to change the default value for list visibility? > Sometime when my list admins create a new list they forget to check > that they should be hidden, I think that should be the default value > anyway because its a potentially security issue when a list is unwanted > visible... It is not yet respected by Postorius, which chooses the first option in the list as the default one, but you can set the default-style in Core. If you want to help fix this, there is an open issue[1] about it on the bug tracker. [1]: https://gitlab.com/mailman/postorius/issues/310 > _______________________________________________ > 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

Mailman-users search results for query "Postorius"