Search results for "Postorius" - Mailman-users

Re: restrict sending to owner/moderator

by Mark Sapiro

On 09/18/2017 02:28 AM, m.dohmen(a)xconnect.de wrote: > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. And on 09/19/2017 10:52 AM, David Krantz wrote: > > I have just tested a variant of this as I got curious: You find the > member you want to be able to send emails without moderation, then set > Administrative Options to "Accept Immediately (bypass other rules)". > That works. I have found no other ways, though. Or you may wish to set the owners/moderators subscriptions to "Default processing" which will still apply subsequent rule checks. I.e., set Default action to take when a member posts to the list to Reject (with notification) and set an appropriate notice (currently can't be set in Postorius - set it via 'mailman shell') and set Default action to take when a non-member posts to thelist to Discard or perhaps Reject but this creates backscatter. Then ordinary members have Moderation set to List default and owners/moderators have it set to Accept or Default. The problems with this are sall the owners/moderators need to be subscribers and there are maintenance issues with adding/removing owners/moderators. A better way to do this by sharing a "moderator password" for the list among the authorized posters. See <http://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.html> for how this is done to pre-approve posts. Then set the list to Discard/Reject all posts, and people who know the "moderator password" can still post. There is still an issue in that the password needs to be changed and redistributed when people become unauthorized, but this is more secure as regular moderation can be fooled by spoofing the sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

Re: integrating mm3 with postfix / lmtp

by Mark Sapiro

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

Re: Member Issue Discovered

by Abhilash Raj

I am a bit late to this thread, but I am going to try to respond to some of the points raised in the thread. On 10/19/20 7:42 PM, Brian Carpenter wrote: > On 10/19/20 10:23 PM, Mark Sapiro wrote: >> And the import21 created the user and address records for this user. > Does the same thing for a new subscriber as well. So there is no pathway > to change a real name that is associated with an email address. None. > Zilch. Yes, this is a limitation of the REST API, the display_name attribute can't be updated. Hence, Postorius can't provide a way for anyone to update the name. I have opened an issue for this[1] and I think it should be allowed. [1]: https://gitlab.com/mailman/mailman/-/issues/786 > I am admin for a list. Users got subscribed with bulk import during > transition from MM2 to MM3. > So in a sense I am responsible for adding these to a db. BUT there is > no way for me to remove them. Only mailman admin with access to the db > can do it manually. The fact that a user's memberships & User as an entity that owns email address is a design choice that Mailman developers made after some experience of using and administering Mailing lists running on Mailman 2. It was annoying to have to manage several different passwords and accounts to manage membership on same mailing list server. The policy decision that Mailman would allow a user/address to exist even if there are no subscriptions on it isn't un-resonable in certain environments and maybe it is in some. I don't think anyone here denies that either of those behavior could be an expectation from someone using Mailman. But Mailman is an open source project with decent amount of extensibility via HTTP API & Python plugin system. If the default policy doesn't match the expectations of some users, I don't think it is difficult to cleanup users/address with 0 subscriptions in a nightly cron script. It is trivial with some basic scripting and we are happy to help out with such a mechanism. I wouldn't be opposed to directly adding a command in Core that lets you clean up all sorts of stuff. On Wed, Oct 21, 2020, at 10:20 AM, Apollinaris Schöll wrote: > There might be a handful of these. > > But the bigger problem is a user can’t be removed entirely. > > User can delete account and unsubscribe from all lists. But the email > and user name is still kept in the db. Just tested with Affinity > List admin can’t do it either. Front-ends like Affinity should be able to implement such a policy by checking subscriptions of an address on every un-subscription call and delete the user & address if it comes out to be 0. The API is documented here[2], but if there are gaps in there like I mentioned above in my email, please open issues so we know about them. [2]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > I think the correct action is to remove all records if a email is > unsubscribed from all lists and that user has not registered for an > account. > If a user has registered for an account all information including > display name must be removed from that particular list subscription. > It should not matter if a user unsubscribes or a list admin > unsubscribes. There shouldn’t be any data kept. Also, like mentioned above, as a list admin, you can request the Site Admin to get the address fully scrubbed or if this is an expectation from all list admins, the Site Admin has the ability to automate such a task. The fact the Mailman doesn't do it by default is because the definition of "correct" action is different. User should have the ability to delete themselves from the system and if it doesn't wipe everything yet from database, it should be considered a bug in Postorius and be fixed. Postorius track users separately than Core, so the it should make sure to delete in both places and there are appropriate APIs in core to delete Users and Addresses. Now, the ability in Postorius to edit the display_name. The side effect of the model where User is a Site level thing, makes it impossible to customize user's display_name on a per-list basis, for both list admin and the user themselves. That is a trade-off and it is possible that there were use-cases where that was desirable in Mailman 2, but with the superior subscription management functionality in Postorius, I feel the decision is justified. I respect that some of y'all think that it probably isn't if it doesn't suit you particular use cases. From the thread, I gather than folks mostly agree that a list admin shouldn't be allowed to edit a user's display name. Site Admins however should be able to edit that, which brings me to next point. Like Mark brought up, there is definitely a big missing feature of User management in Postorius. This future management page would be for Site Admins (Superusers) to manage Users and have the ability to change pretty much everything about users including their addresses, memberships and preferences and also be able to wipe off the users from all the databases if they want to. If there are more features than that which folks think should be a part of this, please feel free to add to it. As it is hopefully implied from the description, it is a big task and needs substantial chunk of time, part of which this hasn't been picked up yet. > > > > > > > > On Oct 21, 2020, at 1:43 AM, Jörg Schulz <info(a)joergschulz.de> wrote: > > > > So, the issue seems to be, like in the following scenario > > > > We imagine a list server for the domains fruiteaters and meateaters. > > We have two listadmins, anna (fruit) and carl (meat). They don't share anything. > > We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com > > > > He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. > > While he can do so using two different email addresses, he cannot do so using > > > > wormy wonder <hunger(a)eatall.com> > > fritz the cat <hunger(a)eatall.com> > > > > as from: addresses because all requests will be matched to the one email address. > > > > Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. > > > > So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. > > > > So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. > > > > Not optimal for some rare conditions - that's the way it seems to be??? > > _______________________________________________ > > 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/ > _______________________________________________ > 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

Re: Default Setting for 'Results per Page' and other Web Pull-downs

by Mark Sapiro

On 5/5/23 14:25, Dave Hall via Mailman-users wrote: > > My question: when I go to any page that has a list (of lists, of members, > or archives), there are pulldowns like 'Results per page' that seem to > reset to the minimum number when I refresh the page. There are others like > 'Hide inactive' on the Archives page. What I'm looking for is a per-user > way to customize these values so I don't have to keep on setting them to > the value I prefer. > > If that is available in a later release then I have something to look > forward to. If not, it sure would be nice to have. No, it is not available. You can submit a wishlist issue at https://gitlab.com/mailman/postorius/-/issues/new for Postorius and https://gitlab.com/mailman/hyperkitty/-/issues/new for HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Installing MM3 requires Django<1.11

by Henrik Rasmussen

Two questions regarding Mailman 3 installation: 1) The Mail server setup at http://docs.mailman3.org/en/latest/devsetup.html#set-up-a-mail-server isn't described yet. Instead it refers to https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends, but it doesn't say which file I have to change. According to https://www.webforefront.com/django/setupdjangoemail.html the file is called settings.py, but the only settings.py I can find at this stage is the /opt/mailman/postorius/example_project/settings.py file. According to http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-postorius, "Postorius and HyperKitty both come with example_project directories with basic configuration so you can try them out. For this tutorial, however, we'll be using a project that combines both instead.". In what file should I change the mail settings then? 2) While installing Hyperkitty*) I got the error message "Django 1.11rc1 is installed but Django<1.11 is required by {'django-haystack'}". As I have slavishly followed the installation guide including http://docs.mailman3.org/en/latest/devsetup.html#set-up-django-mailman3, I wonder why a non-supported Django version was installed. *) http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-hyperkitty Regards Henrik

9 years, 7 months

Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 8:55 AM, Kevin Hurtley wrote: > > It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. The issue with the way Postorius displayed all the subscription requests was that it wasn't possible for the moderator to distinguish request waiting moderator approval from those waiting user confirmation, and in general a moderator shouldn't approve a request waiting user confirmation, but this thread shows there is sometimes a need for a moderator to be able to deal with these. I have reopened <https://gitlab.com/mailman/postorius/issues/314>, and will look at fixing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

Re: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman

by Simon Hanna

On 11/08/2017 12:03 AM, Abhilash Raj wrote: > New images are available on quay.io and, moving forward, the rest of > the image builds will also be moved to Quay[4][5]. Since docker deployment is currently the recommended install, with manual installs using the master branches for "experts" I wonder why you are using Quay. It looks like it's a non-free system. Why use Quay but refuse to use a non-free translation system like transifex? > These images are built using git-heads *only* if they are passing our > test suite and are re-generated weekly. You should be aware that while > all these components are tested with their individual test suites, their > combination might sometimes not be stable. This will get you > updates/bug-fixes much faster :) This contradicts what you said in my merge request for Postorius https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 You either use released versions, or make sure that the master branches are always compatible. You can't have both with the current development model. > If this campaign succeeds, here is a road map of what I intend to get > done: Sounds great, what is the limit where the campaign succeeds? What will happen to the funds if it doesn't? > - Add Admin Dashboard project from GSoC 2014 (maybe?) Didn't find anything using google. What is that project about? > - Add better testing of container images and provide deployment > instructions for Kubernetes & Docker Swarm To be honest, I don't think we should all in on containers. Yes they are nice, but I guess most people would prefer distro packages. Even if people want containers, I for instance would prefer plain systemd-nspawn > - Improve the container images to work with new micro-services > architecture, > to achieve scaling and redundancy in services. The current bottleneck is the rest api from core. IMO bulk actions, filtering and sorting should be added there before trying to have multiple postorius/hyperkitty instances serving the same core...

9 years

Re: New Mailman Releases

by Odhiambo Washington

On Wed, Oct 26, 2022 at 10:16 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On 10/26/22 12:32, Odhiambo Washington wrote: > > > > > > On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in > > <mailto:maxking@asynchronous.in>> wrote: > > > > Hi, > > > > I am pleased to announce several new releases for GNU Mailman > project. > > > > 1. Mailman Core 3.3.6 [1] > > 2. Postorius 1.3.7 [2] > > 3. Hyperkitty 1.3.6 [3] > > 4. Mailmanclient 3.3.4 [4] > > 5. Django-mailman3 1.3.8 [5] [snip] > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > > recommended if you are doing a new install for longest support. 3.10 > is > > supported for Django apps, but Mailman Core is missing that due to > one > > of the core dependencies not support 3.10 yet (aiosmtpd). > > > > > > > > Hello @Abhilash Raj <mailto:maxking@asynchronous.in> > > > > Thank you and the whole MM3 team for all the free work you do to make us > > have mailing lists :) > > > > I have a question regarding the Python version. > > I have a very recent installation of MM3, via the Virtual Environment > > method, running smoothly - so far. > > The Python version that got installed is 3.10.6 > > > > wash@lists:~$ sudo su - mailman > > (venv) mailman@lists:~$ which python > > /opt/mailman/mm/venv/bin/python > > (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V > > Python 3.10.6 > > (venv) mailman@lists:~$ mailma > > mailmail3 mailman > > (venv) mailman@lists:~$ mailman --version > > GNU Mailman 3.3.5 (Tom Sawyer) > > (venv) mailman@lists:~$ > > > > 1. What does the incompatibility with Python-3.10 portend for my setup > > and anyone else with Python-3.10? > > The bug in aiosmtpd is a bit weird and has to do with how the test cases > in aiosmtpd and Python 3.10 changes interact with SSL. For the intents > and purposes of Mailman, we don't use SSL for the communication between > MTA and aiosmtpd, so there _shouldn't_ be any issuer with your setup. > Relief! > Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a > Python venv with 3.10, but that depends on which version of pip you are > using since the newer versions have better support for such management. > I followed the HOWTO by the late BC <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> for my installation. I did not have to choose any specific version of pip. I just used what was in the system at that time, which was based on the Python version on the system. > > 2. Is it possible to downgrade the Python in a Venv down to 3.9 without > > breaking the installation? > > You can keep the current installation running and create a 2nd > installation by simply creating a 2nd venv with 3.9. Something like, > `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and > when you are done and ready to switch, you can update all the paths in > various places to use update 'venv-3.9' instead of 'venv'. > That procedure seems way too much work for someone not so well versed with the PATHs used in MM3. Since I don't remember ever having to install aiosmtpd (not even sure what it is!) I believe I should not worry. 'pip3 list | grep smtpd' yielded nothing in my install. Is that expected? Or aiosmtpd is part of the core? In case you encounter any issues, you can always revert back to older > 'venv' in the paths wherever the are needed and bring back the old > install. Venvs are good for multiple installs so you can switch back and > forth pretty easily. > Talking of moving between VENVs, you did not mention about migrating the lists/list data between then :-) > > > > And finally, is there documentation/procedure to upgrade a VENV install > > in this case? > > You don't want to upgrade venv is what i've heard, you should always > create a new one if you are bumping python versions. > Noted. And only Python versions, right? Like 3.10 to 3.11? > If you are just upgrading packages in the existing venv, then you can > follow: > > https://docs.mailman3.org/en/latest/upgrade-3.2.html Thank you for this. I have a request: Is it possible for someone to update the HOWTO that was done by Brian to include the process of updating MM3? I can see that he created a heading that was supposed to have the procedure. I am assuming it should be a few simple additions - but I am not quite sure (see below): (1) Pre-upgrade First, you need to stop the running Mailman services before the upgrade to make sure that you don’t end up in a bad state. You can stop the three systemd services: $sudo systemctl stop mailman3 $sudo systemctl stop qcluster $sudo systemctl stop gunicorn (2) Then you need to switch to mailman user, activate the virtualenv: $ sudo su mailman $ source /opt/mailman/mm/venv/bin/activate (3) Upgrade package Finally, upgrade your packages: Here, I am a little confused. The official MM3 documentation says the below: *(venv) $ pip install -U mailman postorius django-mailman3 hyperkitty mailman-web* However, thee howto by BC, there was no installation for django-mailman3 and mailman-web. So I am unable to map 1:1 what needs to be done to upgrade to these 5 components of 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] What should I add to the command line below so that everything is updated? (venv) mailman@lists:~$ pip install -U mailman postorius hyperkitty mailman-hyperkitty Sorry to bother you so much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

4 years

Re: Mailman upgrade results in page not found error

by Andrew Hodgson

Abhilash Raj wrote: >On 11/3/22 18:30, Andrew Hodgson wrote: >> I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of having https://lists.hodgsonfamily.org going to the correct place? >> urlpatterns = [ >> path( >> '', >> RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), >> ), >> path('mailman3/', include('postorius.urls')), >You _probably_ had DOMAIN/postorius as your URL? If that's the case, replace the 'mailman3/' above with your old 'posotorius/' in your new urls.py. >That should fix the problem you are having with 404 because you browser probably remembers the old URL and tries to auto-redirect root path to /postorius. Yep that was it. I actually left it be in the end as users were accessing the new page fine. I had to update mailman-hyperkitty with the new URL as archiving wasn't working but that has now been done and everything seems to be back to normal on the new setup. Thanks. Andrew.

4 years

Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi Mark, thanks for correcting my assumption. Based on your information I have been able to identify the suspect message file in /var/lib/mailman3/messages, replace the suspect file with another file, update the file permissions and successfully load the held messages page. This allowed me to discard the suspect message and other held messages are then available for review again. In case the steps below help someone else who is having this issue here are the steps I followed with my initial search string redacted: Searched all files in messages folder for matching string: cd /var/lib/mailman3/messages grep -ir [REDACTED] * Finds string in one file: Binary file HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV matches Check whether file can be parsed using mailman command: mailman qfile ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Throws a matching error: [----- start pickle -----] <----- start object 1 -----> Traceback (most recent call last): File "/usr/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 97, in main args.func(args) File "/usr/lib/python3/dist-packages/mailman/commands/cli_qfile.py", line 81, in process printer.pprint(obj) File "/usr/lib/python3.6/pprint.py", line 139, in pprint self._format(object, self._stream, 0, 0, {}, 0) File "/usr/lib/python3.6/pprint.py", line 161, in _format rep = self._repr(object, context, level) File "/usr/lib/python3.6/pprint.py", line 393, in _repr self._depth, level) File "/usr/lib/python3.6/pprint.py", line 405, in format return _safe_repr(object, context, maxlevels, level) File "/usr/lib/python3.6/pprint.py", line 555, in _safe_repr rep = repr(object) File "/usr/lib/python3/dist-packages/mailman/email/message.py", line 45, in __repr__ return self.__str__() File "/usr/lib/python3.6/email/message.py", line 135, in __str__ return self.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) Move suspicious file out of messages: mv ./HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV /root/20200914/ held_messages page still throws 500 error. Checking debug log, it is now because the database references a file that is no longer there. Can I just copy a parseable file to the path of the bad file so I can delete it or do I need to remove the reference from the database? Copy some other file: cp ZZ/B2/ZZB24ADTZ2BOKBWTQWI7KG4XACGR6DTJ HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV Still throws an error but this time it's a permissions error. mailman can't access the copied file: ls -l HE/D7/ -rw-r----- 1 root root 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chown list:list HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV chmod g+w HE/D7/HED7SJLGJXTJ35AESY32AZXYPXDEVUVV ls -l HE/D7/ -rw-rw---- 1 list list 78472 Sep 14 12:48 HED7SJLGJXTJ35AESY32AZXYPXDEVUVV held_messages now loads OK. Cheers, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, 12 September 2020 06:17 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

6 years, 1 month

Mailman-users search results for query "Postorius"