Search results for "Postorius" - Mailman-users

Re: Default values for lists in Mailman 3

by Markus Grandpré

Thank you very much for your answer. Best regards, Markus Am 19.09.24 um 22:03 schrieb Mark Sapiro: > On 9/19/24 05:46, Markus Grandpré wrote: >> Dear list, >> >> I would like to activate the invitation setting for all lists as >> default. In Mailman 2.1 I have done this in the file </etc/mailman/ >> mm_cfg.py>: >> >> >> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >> >> >> How can I do this in Mailman 3? > > There is a draft merge request at https://gitlab.com/mailman/ > postorius/-/merge_requests/930 which implements a framework for setting > Postorius defaults and creates a setting to set the default for pre- > verified on the mass subscription page. Once merged, this can easily be > extended to provide a default for Invitation. > > In the mean time, you can only do this by patching src/postorius/forms/ > list_forms.py like > ``` > --- a/src/postorius/forms/list_forms.py > +++ b/src/postorius/forms/list_forms.py > @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): > > invitation = forms.BooleanField( > label=_('Invitation'), > - initial=False, > + initial=True, > required=False, > help_text=_( > 'If checked, the other checkboxes are ignored and the > users will ' > ``` >> Can I also transfer other default values like: >> >> ... >> DEFAULT_SERVER_LANGUAGE = 'en' >> DEFAULT_SEND_REMINDERS = 1 >> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >> DEFAULT_PRIVATE_ROSTER = 2 >> DEFAULT_ARCHIVE = Off >> DEFAULT_ARCHIVE_PRIVATE = 1 >> ... >> >> from the very same configuration file to Mailman 3? Is there a >> documentation of the default values for lists in Mailman 3? > > This is done by creating a list style with the desired defaults. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/ > docs/styles.html for documentation of styles and see https://gitlab.com/ > mailman/example-mailman-plugin for an example of creating a plugin in > Mailman core to make a persistent style. > > There is no specific doc for the list settings. You need to look at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/ > base.py for the various settings and https://gitlab.com/mailman/ > mailman/-/blob/master/src/mailman/styles/default.py to see which default > classes are applied for various styles. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 months, 1 week

Postorius extremely slow on some of the mailinglists

by Stephen J. Turnbull

Eric Broens via Mailman-users writes: > Mainly "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" > takes a long time. The only thing I can think of is that something weird is happening with requests (held messages) on those lists. The runner is waiting on the database server, and eventually timing out, I think. I believe you will find the corresponding messages under $var_dir/messages (var_dir is usually set in mailman.cfg, if not I believe it defaults to /usr/local/mailman3/var). Unfortunately I don't know how to link those entries to the messages in that directory tree. You can "grep -ri '^list-id:.*<your.list.id>$' messages" for held posts via the problem list if you have list ID on (that's the default for recent Mailman) and if that's not going to work you could use "grep -rF 'your(a)list.id' messages" for a less precise search. It's not a good idea to delete them from the file system (I think Mailman is robust to that but I'm not sure). However, if one looks like spam you could try working at a slightly lower level than Postorius by using mailmanclient directly. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…. If that doesn't work (for example listing the requests for a list times out the same way in mailmanclient), you could try directly querying the database server to see what's going on. The check for an unusual number of requests that might be an attack is to connect to the database server with its command line utility. I'm not on CLI terms with MySQL but for PostgreSQL it's $ su - mailman $ psql mailman=> select mailing_list_id, count(mailing_list_id) from _request group by mailing_list_id; mailman=> select id, list_id from mailinglist; and you can append " where id = $mailing_list_id" to the second to the second one to find the List-Id for a specific mailing list. That's just plain SQL including the count function as far as I know, so should work in any backend that Mailman can use. If you're handy with SQL you could do all that with a join but I'm not. ;-) > Any idea why this happens and how it can be solved? Aside from a really astonishingly large number of pending requests (as tested above with count()), perhaps there's something in the requests themselves. If there aren't literally thousands of requests for a problem list you can list them with mailman=> select key, mailing_list_id from _request; Look for odd characters in the key field. One oddity that I'mm pretty sure is not a problem is something of the form "\r\n <message-id>" (my instance lists those fine). There's a bug in Exchange (IIRC) which sometimes includes invalid characters (specifically "[" and "]") in message IDs which I believe we worked around only quite recently, although I don't recall if it affected APIs for requests. Control characters and non-ASCII might also cause trouble, If your database server is MySQL, is it set up to handle the full range of Unicode (I think the option is utf8mbcs)? Lacking that is known to cause problems when headers and maybe body contain emoticons or other extended Unicode characters. Again I don't recall if crashing the REST runner is a known symptom. If none of the above works, there's always the "hit it with a hammmer" approach. Have you tried restarting both Postorius and Mailman? How about restarting the database server? How about all three? As a last resort, it's probably possible to delete the requests from the filesystem and the database by hand. But I don't want to think about that unless absolutely necessary. Steve

5 months, 3 weeks

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 5:02 AM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > > > >> > >> > >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >> wrote: > >> > >> /bin/sh: sass: Permission denied* > >> > >> > >> > >> Did you check the permissions on your sass binary? > >> > > > > My mailman installed in /opt/mailman/mm > > > > find /opt/mailman/ -type f -name sass > > > > yielded nothing! > > > > Try `which sass` > root@gw:/usr/home/wash # su mailman3 (venv) [mailman3@gw /usr/home/wash]$ which sass (venv) [mailman3@gw /usr/home/wash]$ There is no sass. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

Re: Splitting hosts: mta&core vs postorius

by samuel.d.darwin＠gmail.com

The current implementation of [webservice] hostname is confusing and difficult to work with. It's not uncommon on a Linux server to have the following in the /etc/hosts file so that the machine resolves it's own name. This is not connected to mailman at all, it could just be general practice. /etc/hosts: 127.0.1.1 mailman.example.com mailman However, if you have that in place, and then this mailman config file. /etc/mailman/mailman.cfg [webservice] hostname: mailman.example.com port: 8001 mailman-core will only listen on localhost. Maybe you don't want that. It shouldn't be necessary to play games with /etc/hosts because the problem could be resolved this way: [webservice] hostname: mailman.example.com bind_to: 0.0.0.0 port: 8001 or [webservice] hostname: mailman.example.com listen: 0.0.0.0 port: 8001 Then any outgoing api messages or other communications would reference the so-called hostname, which remote clients would use, "mailman.example.com" . If the "listen" or "bind_to" field is absent, fall-back to the current behavior.

1 year, 6 months

hidden list is hidden even to the owner

by Mohsen Masoudfar

Hi, I am not sure, if it is designed this way, or I am doing something wrong. I created a list in MM3 as a hidden list, meaning: Show list on index page: NO and assigned the owner. When I login as Postorius web admin, I see the list on the list page which is listed as: (unadvertised*). This is fine. But when the owner or moderator login to Postorius they don't see the list at all. Of course if they add the list name at the end of the URL, they get to the list and as the owner can manage it too. My question is: I am just not sure, if I am missing something or this is how it is supposed to work? You could expect, that the owner or the moderator should see the list as (unadvertised*) too. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years, 1 month

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > /usr/local/include/sass > > > > That is the only thing found that is in the base system. > > And that's the one you want. What is it's mode? > root@gw:/usr/home/wash # ls -al /usr/local/include/sass total 104 drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h I imagined I needed an executable. drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/23/23 08:42, Odhiambo Washington wrote: > On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Thanks both of you. I didn't know Debian11 version is out of date. I will >> try using pip. >> > No. Debian 11 is _not_ out of date. It's just that the preferred and easy > to support installation method is using the virtualenv. The Debian stable mailman packages definitely ARE out of date. bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2. bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

Re: changing adverstised status

by Mark Stuart

I can confirm the issue is happening to me as well postorius 1.2.1 / Django 2.0.7. If you're logged in and go to the list setting page, check the radio button for 'Show list on index page' to 'No' and click save at the bottom, it reverts back to 'Yes'. Then it still shows up on the index page. I haven't tried the mmclient method to see if that works. -- Mark (stuieordie) On Wed, Aug 22, 2018 at 1:30 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Aug 22, 2018, at 1:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change "show > > list on index page" via the settings, but the value isn't saved. Is > > there a way to set advertised = False to a specific list via the shell? > > Could be related to > https://gitlab.com/mailman/postorius/merge_requests/352 > > The behavior of some of our boolean fields changed with newer releases of > Django, but it has been fixed in master branch. > > > > > Thanks & Regards, > > Alex > > > > (Kulturserver editorial staff) > > _______________________________________________ > > 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) > _______________________________________________ > 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/ >

6 years, 11 months

Assistance Needed for Ubuntu 22.04 Mailman3 Installation and Configuration

by smiithjohn90＠gmail.com

Hello Everyone, I'm trying to install Mailman3 on an Ubuntu 22.04 server right now, and I've run across a few obstacles that I'd like help with. I've followed the installation instructions, but I'm having trouble in a couple places, so I was hoping an experienced someone might help me out. This is what I have completed thus far: - I used the apt-get package manager to install Mailman3. - PostgreSQL was configured as the database backend. - Postfix was installed and set up to function as the Mail Transfer Agent (MTA). - Assemble Postorius, Hyperkitty, and the Mailman3 core. Problems I'm Having: Postorius and Hyperkitty Connectivity: I'm having problems making sure that the Mailman core is correctly connected to Postorius and Hyperkitty. I get a 502 Bad Gateway error when I try to access the web interfaces. Despite checking my specifications, I am unable to identify the problem. Problems with Email Delivery: I'm also having trouble with email delivery. Although Mailman appears to be receiving emails, it is not appearing to be sending any out. I think there might be a Postfix problem, but I'm not sure how to solve it. Generally Suggested Practices: Are there any particular security best practices I should be aware of when it comes to Mailman3 installations? I want to confirm that my configuration is both performance- and security-optimized. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://www.igmguru.com/salesforce/salesforce-developer-training https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I would be grateful for any advice or resources! It would be really beneficial if someone with a similar setup could share their settings or troubleshooting procedures. Thank you in advance.

11 months

User management page [was: Changing subscription address]

by Stephen J. Turnbull

Core implementation details, so I beinging this here from Mailman Users @ mailman3.org. Abhilash Raj writes: > I have started working on designing a User management page[2] in > Core which should make it easy for superuser to manage several > things about a User, including the ones that don’t have an account > in Postorius to manage their own. I don't understand this design with a "page in Core". I was thinking about this kind of problem, and tentatively came to the conclusion that any reference to something that can be resolved to a User should generate a Django account for that User in Postorius or HyperKitty. Authorization to use that account would still require authentication via the usual email verification dance, or some level of admin privilege. The thing is that emails that have not been added to a User are unique. They will be the only Address attached to User created to manage them until authenticated, and transitively the only address attached to an automatically-created Django account (since those are 1-1 with core Users if they exist AFAIK). What's missing here is the ability to merge core Users and their corresponding Django accounts. Doing this with nothing more than the usual email verification dance is not *obviously* provably secure to me, so we need to be careful, but I think it probably will turn out to be as secure as you can get. It seems to me that User merging is the most pressing problem of this kind. (At least, it affects me on a couple of list hosts, as well as on GitHub and GitLab.) > [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 I'll take a look tomorrow or early next week. Steve

4 years, 4 months

Mailman-users search results for query "Postorius"