Search results for "Postorius" - Mailman-users

Re: Enforcing SSO and subscription options

by Stephen J. Turnbull

via Mailman-users writes: > Thank you for the reply. Ultimately, I ended up digging deeper > into the allauth docs, per your suggestion, and I went a little bit > further with the "SOCIALACCOUNT_ONLY" option. It turns out that > the errors I were seeing were related to the sign up button > referencing a view that didn't exist. You have to do this, I suspect (I am unsure that removing the reference from urls.py would protect you from A Sufficiently Smart Miscreant, and if it did you'd still get the error, so why not remmove the code and remove all doubt!) > I solved this in an admittedly ugly way, by removing the sign up > button from the postorius and hyperkitty templates. You do not have to do it this way. There is a search path for templates, and you can remove those buttons from copies stored in a directory earlier in the path. I use /etc/mailman3/templates/..., but they can go anywhere convenient that won't be overwritten by an upgrade. The worst that could happen is the copies get removed, and then you get the error, which you fix.

3 months, 4 weeks

Message-Footer after migrating to Mailman3

by christopher.claus＠tgcamberg1848.de

Hello together, I migrated a number of lists from mailman2 to mailman3 using the import functionality. Everthing works fine and the new lists are in use. Currently I´m using the maxking-docker-images with postorius: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.5 (default, Feb 19 2021, 09:27:16) [GCC 9.3.0] After this migration I started a refactoring with the list-styles specially with message-footers. Already the old lists in mailman2 were confused in some configuration details an I was clear to import this "misconfiguration" and clean it up afterwards. But this was much more difficult than expected: some lists are using a footer (from the mailman2-config) and there is no record in the template-section visible. Further I found no configuration item which points to this "old" footer. I found the file [code] /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt [/code] which includes the old footer: [code] _______________________________________________ $display_name Mailingliste -- $listname Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} [/code] but no configuration item to disable this behaviour. I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used - in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. In the logfiles I found an error and a warning: [code] ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer [/code] Obviously I have a problem with the hostname. I set [code] POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 [/code] where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost [code] wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… [/code] will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. Best regards, chrclaus

4 years

Re: username

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > I would like to create/pre-populate all the postorius usernames for > our list owners/list moderators using their university net > username. Is there a way to do that? You can create Django users via the Django admin interface (typically the ".../admin" sibling to the ".../postorius" and ".../hyperkitty" URLs. It shouldn't be too hard to automate this, but I don't know of such a script. Django channels might be a better place to ask for that. But after that things may get complicated. Are you migrating from an existing list server and want to link the new users to existing lists? I think this can be done as long as you link the appropriate owner addresses to each user. Hopefully those are algorithmically related to the network login (ie, address = username@domain). Also, if by "network login" you mean a SSO protocol such as SAML, you can populate users directly from a service provider such as Shibboleth. There's a well-known protocol called REMOTE_USER that Django participates in. There are a couple of speed bumps you may run into, but it's hard to be specific without more information on your particular situation. Steve

2 years

Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Tuesday, March 15, 2022 10:29 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/22 11:16, Quanah Gibson-Mount wrote: >> Hello, >> >> We have a constant issue with confirmation emails for subscribers >> getting lost and then the subscriber contacting us because their posts >> to the list never show up. Is there a way I can, as an administrator, >> do the confirmation on their behalf or in some other way promote them to >> being a member from non-member? > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/MJOOH23W6EKZO7GI5HRDKB4S733JEEVG/ > > If they don't have an outstanding subscription waiting user confirmation, > you can just mass subscribe them. > > If they do and your Postorius and Mailman core is reasonably up to date, > you can find the pending request at Subscription requests -> Pending > Confirmation, delete it and then mass subscribe them. Hi Mark, Thanks for the response. Unfortunately I'm currently stuck with the junk shipped by Debian. Yet another reason to move to a standalone install and avoid their broken packages. Regards, Quanah

3 years, 3 months

Re: attachment.html

by Sam Darwin

Thanks for making this change! It's a big improvement! Another random idea, not required, - using javascript, literally disable or enable all the settings which are disabled or enabled by 'Filter content'. So if someone tries to set 'Convert html to plaintext', they can't, until 'Filter content' is enabled On Mon, Jun 26, 2023 at 10:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 6:22 PM, Mark Sapiro wrote: > > > > You are correct that the UI is not clear on what settings depend on > > Filter content. We need to fix that. > > I've created an issue for this at > https://gitlab.com/mailman/postorius/-/issues/584 and committed a fix at > https://gitlab.com/mailman/postorius/-/merge_requests/815 > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to samuel.d.darwin(a)gmail.com >

1 year, 11 months

Re: moving lists to another server

by Stephen J. Turnbull

Stephen J. Turnbull writes: > 2. There are similar issues for mailman-web (especially host names). > I have not thought about them at all, so I'll leave that for the > interested reader. ;-) Mark's right about this. I think Postorius and other configs will take care of themselves except for the users' tables which can be handled as Mark suggests, and the HyperKitty archives themselves are most easily handled by exporting to mbox and importing into the new site. > 7. Apply any changes made in 6 to your configs, and read the foreign > dumps into your system, and you should be ready to go for the > distribution part. Not sure about host and webserver > configuration for mailman-web, though. I just remembered one thing (among many, I'm sure): you probably need to create directories under $var_dir/lists for each foreign list. I'm pretty sure this is done by the "mailman create" function, not on the fly. The source for "mailman create" would be another good place to look for tasks you (or your script) need to perform and changes needed to database values in the SQL dump scripts. Steve

1 year, 7 months

Re: How can I remove anything added by Mailman 3 to the forwarded email

by Mark Sapiro

On 5/9/22 06:00, gscaglia(a)ksdata.it wrote: > I need to use Mailman 3 exclusively for forwarding emails to my customers divided by type. > > The emails must arrive exactly as they are, without any additions, and the lists are managed only by me: the customer ignores that he is subscribed to a list and receives the message as if it were one to one. > > How can I remove anything added by Mailman 3 to the forwarded message, therefore also the links for managing my membership (unsubscribe and modify)? In Postorius do the following: In Templates set list:member:regular:footer empty In Settings: in List Identity set Subject prefix empty in Alter Messages set Personalize None Filter content No Anonymous list No Include RFC2369 headers No Include the list post header No First strip reply to No Reply goes to list No Munging in DMARC Mitigations set DMARC mitigation action No DMARC mitigations in Archiving set Archive policy Do not archive this list -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: installation

by Mark Sapiro

On 11/21/20 10:42 AM, Christian Stalberg via Mailman-users wrote: > I am working through installing mailman3 on Ubuntu 20.04.1 LTS / apache > 2.4.41 / postfix 3.4.13 and have a couple of questions. > > > > I've installed Django, cloned the mailman-suite repo, installed and tested > apache with Mod_wsgi [ according to > https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/ ] > and it worked fine. Now I am at 'Setting up a WSGI' server in the MM3 > instructions where it says I am to configure uwsgi.ini file. Does that .ini > file go in /opt/mailman/mailman where other .ini files reside? You are mixing apples and oranges. The doc at <https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/> uses mod_wsgi in apache, It doesn't use uwsgi at all. > In setting up the apache virtual server [ according to > https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl > ight=apache#apache-with-mod-wsgi ] I do not find a postorius.wsgi which > WSGIScriptAlias points to. The file in your WSGIScriptAlias directive should be the wsgi.py file in mailman-suite/mailman-suite_project/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Unable to retrieve <800 members of Mailman list through Curl command

by Shashikanth Komandoor

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values. I am almost running 2000 lists with 128 GB RAM and 24 Cores on a single VM and on which all the mailman 3 components are running. It is observed for most of the lists having members more than 500 is displaying "Mailman REST API not available. Please restart Mailman Core" message on the postorius window and on running the CURL command over REST API of Mailman it is reaching the time limit 30 seconds and showing the below error. *curl: (52) Empty reply from serverNo JSON object could be decoded* The same behavior is observed on browsing the held messages for few lists either through the browser or through CURL and REST API. How to resolve this issue ? What other details I can provide to make you get an idea ? -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

4 years, 5 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)

6 years, 3 months

Mailman-users search results for query "Postorius"