Search results for "Postorius" - Mailman-users

Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

In the OpenDev Collaboratory we've got a bunch of separate Mailman 2.1 vhosts we've started migrating into a single Mailman 3.3.7 server, desiring to take full advantage of its improved multi-domain support. For the most part everything is working great (kudos to everyone who maintains the software and documentation, it's excellent). One of the things our users noticed fairly quickly was Hyperkitty on the second vhost was incorrectly showing the FQDN of the first vhost near the top of its pages. This is covered in the FAQ of course, and seems to imply that what we want is to switch the SITE_ID from 1 to 0 in our settings.py in order to take advantage of magic domain-guessing behavior. So far so good. Unfortunately, SITE_ID = 0 seems to explicitly require the addition of "mail hosts" (or "mail domains" from Django's perspective), and all the web routing returns error pages for any list sites besides the first one since, by default, our server did not have these predefined. What's odd is that, if I log into Postorius as admin and visit the "manage domains" page, suddenly the database gets populated with mail hosts for all of the FQDNs associated with our imported mailing lists. I would not have expected merely visiting that page as an admin to have a side effect of adding entries for the "missing" mail hosts, is that an intentional behavior or merely a bug? Once these entries are automatically added by visiting that page, they're all associated with the one "web host" ("site" in Django) we have for the server, and now the list filtering functionality in Postorius breaks and any of the vhosts all display the full set of mailing lists on the server rather than only those associated with a particular vhost (note that this seems to only be confusing Postorius, Hyperkitty has them correctly filtered still). Okay, so it looks like this is because the mail hosts are all tied to the one web host. We can create additional "sites" in the Django admin UI and then switch the association of the mail hosts to those distinct web hosts. But after doing so, the first vhost still seems to show an unfiltered list of all lists in Postorius (Hyperkitty continues to be fine), while Postorius on the other vhosts correctly shows their filtered sets of lists instead. I also noticed when mailman-web is starting up, its log claims the first site is being set as the "default domain," so have to wonder if that's related to this behavior. Should we create an extra web host to serve as the "default" so that all our typical vhosts get the expected list filtering behavior, or am I completely off-base and there's a much better approach I've missed? Sorry this is so long, I feel like I have at most a tenuous grasp of the details and variables involved, but hopefully it makes sense to someone. Thanks in advance for any recommendations or guidance. -- Jeremy Stanley

3 years, 2 months

Re: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 06:52, Frank Steinberg wrote: > Hi, > > I’ve added links to some templates to give owners and moderators > shortcuts to the postorius UI for moderation tasks, e.g., I’ve added > > https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> > > Unfortunately those lines seem to exceed a certain limit and get > folded, so that they appear as, e.g. > > https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> > messages > > (or similar) and are not directly useful. How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? Also are those lines of the form https://... <https://...> what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? -- 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: 400 Bad Request when administrator tries to selectively override member options

by Mark Sapiro

On 5/8/21 1:17 PM, ieso(a)johnwillson.com wrote: > This is probably Design Intent, but I'd just like to confirm. > > When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set. > > Screenshot: https://ibb.co/pzM5Z4m > > It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list. > > But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation. What Postorius version is this? I just tried it on Postorius 1.3.5b1 (The HEAD of the gitlab branch), and for a user with no options at all set at the list level, I was able to set `Receive own postings` only with no problem. I think this is https://gitlab.com/mailman/postorius/-/issues/178 fixed in Postorius 1.2.0 by https://gitlab.com/mailman/postorius/-/merge_requests/321 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Wed, Feb 27, 2019, at 12:04 PM, Danil Smirnov wrote: > Hi, > > After upgrading my PostgreSQL from 9.2 to 9.6, I was able to up postorius container. > But when I try to open UI, I'm getting 500 Internal Server Error all the time - either for /postorius/lists/ as well as for /admin/. > I've checked all the logs but haven't found anything there which can bring some light at the issue. Just error 500... > > I've checked: > - nginx logs: just error 500 > - mailman-web docker container logs: no errors > - mailman-web (postorius) logs: mailmanweb.log is empty, uwsgi*.log with some errors > - mailman-core logs: no errors > > I've also called curl localhost:8000 from inside the mailman-web container and got the same 500 Internal Server Error. > > Could you guys advise what else should I check? We would need to figure out if it is Core or Web causing the 500 errors. So, what errors are you looking at in uwsgi*.log? Do you see any successful requests in mailman core's mailman.log? > > With my best regards, > Danil > > > пт, 22 февр. 2019 г. в 09:12, Danil Smirnov <danil(a)smirnov.la>: >> Hi Abhilash, >> >> Thank you for the quick resolution, but I'm still unable t start the container: >> https://github.com/maxking/docker-mailman/issues/309 >> >> DB migrations are failing. >> >> Danil >> >> вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: >>> Hi Abhilash, >>> >>> Thank you for the explanation, I've created a report: >>> https://github.com/maxking/docker-mailman/issues/307 >>> >>> Danil >>> >>> >>> >>> сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: >>>> On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: >>>> > Hi, >>>> > >>>> > I'm interesting in Mailman3 deployment with archiving feature completely >>>> > disabled. >>>> > >>>> > I've tried to deploy Core + Postorius using this docker-compose >>>> > template: >>>> > https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… >>>> > >>>> > Unfortunately Postorius version came with this template is quite outdated: >>>> > 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I >>>> > see version 1.2.3. >>>> > >>>> > I've also checked image maxking/postorius:rolling but it seems >>>> > irrelevant/broken (container exits with error). >>>> > >>>> > Are there newer Postorius docker image I can use? >>>> >>>> No, but if you could report the failure and error that you, maybe the Maintainer can help >>>> fix that issue you have? >>>> >>>> P.S. I maintain those images. The Postorius image is kind of neglected since there are >>>> fewer people using it, but I'd be happy to fix any error that you see. >>>> >>>> Package ugprades are merely a version number bump in Dockerfile :) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

6 years, 11 months

Re: postorius only show 50 owner lists

by Abhilash Raj

On Fri, Mar 1, 2019, at 3:14 PM, elalelopez(a)gmail.com wrote: > Hi, > > I have installed mailman3 suite on Debian 9. > > And postorius only lists up to 50 addresses when filter by owner: > > https: //lists.domain/mailman3/postorius/lists/? role = owner > > A first query in the database returns all the lists, but then, when it > makes the subsequent queries for each list, it ends when it reaches 50. Which database do you mean here? I think it is because it is paginated, do you see the pagination on the index page below the list of 50 lists? > Any ideas? > > regards > _______________________________________________ > 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, 11 months

Re: Pck files stuck in out queue

by Mark Sapiro

On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Thu, May 13, 2021, at 1:46 PM, Odhiambo Washington wrote: > > > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for each components: >> >> Mailman Core 3.3.3: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> Postorius 1.3.4 https://docs.mailman3.org/projects/postorius/en/latest/news.html >> Hyperkitty 1.3.4 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html >> >> Minimum supported Python version is 3.6. >> >> You can install them using: >> >> $ pip install --upgrade postorius hyperkitty mailman >> >> We have also recently been working on making the installation instructions[1] to be >> more detailed and added a new FAQ[2] section for administrators where I hope >> to capture common questions from mailman-users list. >> >> Feedback or Merge Requests to improve these docs are welcome. You can either >> send an email or open an issue on Gitlab (easier to track) here[3]. >> >> [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > Hi Abhilash, > > What's the reason behind the exclusion of MySQL & Apache instructions in the installation instructions? :-) Really no reason, the intent was to pick some options in that page and point to additional documentation for using other alternatives. I will be more than happy to accept patches to add the documentation about alternatives like MySQL and Apache and other variations in the tech stack. Just add a new page under install/ and add a "Note" in the above page to point to it. I had documented some time ago how to contribute to our documentation[1] and folks on this list would be happy to answer any questions regarding contribution too. [1]: https://docs.mailman3.org/en/latest/documentation.html -- thanks, Abhilash Raj (maxking)

4 years, 9 months

Re: templates

by Odhiambo Washington

If you don't have any templates in the file system and none in the DB table, then you must go to Jerusalem and pray, because you don't have any and nothing will work the way you want. It's either or! On Thu, May 4, 2023, 21:14 Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. > > > > > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Thursday, May 4, 2023 10:58 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: templates > > On 5/4/23 10:33, Christian via Mailman-users wrote: > > I'm having issues with my lists. For each list I have created a > > template [ list:user:action:subscribe ]which has a prospective > > subscriber have to consent to list rules before they are subscribed. > > This template I created is listed in Postorius for each list. I have > > noticed that there are no other templates listed in Postorius. > Furthermore, there is no 'lists' > > subdirectory under Mailman's var/templates/. > > > When you set a template in Postorius it saves it in the > postorius_emailtemplate table in the database and tells Mailman core to get > the template from Postorius via a URI to a Postorius API. > > -- > 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/ > QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to csa(a)web-analysts.net > > _______________________________________________ > 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 odhiambo(a)gmail.com >

2 years, 9 months

Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/19/19 6:33 PM, kevin(a)coastalaska.org wrote: > We have a couple of people trying to subscribe to our list but receive an error similar to: > {"title": "409 Conflict", "description": "Subscription request already pending"} > > If I try to Mass Subscribe them in Postorius I get this error: > HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' > > In Postorius I don't see them hung up in Subscription requests. Postorius since 1.2.3 does not show subscription requests waiting user confirmation, only those waiting moderator approval. Thus, if the list's subscription policy is confirm or confirm then moderate, the subscribing user will be sent an email requesting confirmation. If the user hasn't answered that email, the request is pending user confirmation, and since 1.2.3, you won't see it in Postorius. [Update: this is fixed in 1.2.4] > What to do? 1) have the user find the confirmation request email and confirm, or 2) wait for the request to expire (default 3 days) 3) using mailman shell or the REST api or direct interaction with the database, find the token and confirm it. A shell example is ``` mailman shell -l your.list.id Welcome to the GNU Mailman shell The variable 'm' is the your.list.id mailing list >>> util = getUtility(IPendings) >>> list(util.find(mlist=m,pend_type='subscription')) ``` This returns a list of items like ('hex_token'), {'token_owner': 'subscriber', 'email': 'user(a)example.com', 'display_name': 'Jane User', 'when': '2019-04-09T01:26:08', 'type': 'subscription', 'list_id': 'your.list.id'}) You then do ``` >>> util.confirm('hex_token') ``` Note that https://gitlab.com/mailman/postorius/issues/314 which was responsible for removing the subs waiting user confirmation from the Postorius listing suggested "there could be a different place to see the ones pending user approval, so that a moderator can look and/or delete those.", but that hasn't been done. [Update: this is fixed in 1.2.4] -- Mark Sapiro mark(a)msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Re: postorius ssl-certificates for virtual hosts

by Wolfgang Bock

Am 15.11.2019 um 02:21 schrieb Mark Sapiro: > Your Apache config needs to define separate a VirtualHost for each > domain, either by IP address or ServerName, and each VirtualHost points > to its own SSL certificates. Thanks for your info, that did it. I had to include the text of the apache.conf in all my apache-config-files for my virtual-domains. >> If I set use_https to yes in mailman.cfg I get on the website for all lists: >> >> postorius: Something went wrong >> Mailman REST API not available. Please start Mailman core. >> >> >> Does your setting in settings(_local).py for MAILMAN_REST_API_URL have >> an https scheme? That doesn't solve the problem. I changed that in mailman-web.py (MAILMAN_REST_API_URL = https://localhost:8001) and after that in mailman.cfg (use_https: yes). But got the same errormessage on postorius website. Regards Wolfgang

6 years, 3 months

Mailman-users search results for query "Postorius"