Search results for "Postorius" - Mailman-users

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/10/2016 12:52 AM, Barry Warsaw wrote: > > Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. Done. There is one "temporary" commit in my MR to work around <https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass. >> I can also work on Postorius. Also in this vein I have a question. >> Should the DMARC settings be added to the Alter Messages tab in the List >> Settings view or would it be better to have a separate DMARC Mitigations >> tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I have a WIP MR at <https://gitlab.com/mailman/postorius/merge_requests/194> that adds a tab. Maybe Florian and Terri can look at that and chime in. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 6 months

Re: Email to list owner on list creation only sent when using mailman create --notify command

by Mark Sapiro

On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Re: Templates

by Barry Warsaw

On Sep 23, 2017, at 10:36, David Krantz <gazorg(a)gmail.com> wrote: > > 1. I do not know how to force a cache invalidation on a template. So > only way to change is to set a new name on the file and change the uri > there. Unpractical. No, restarts do not work. With Mark’s help you figured out how to use file templates, which is probably best for your use case. URL templates will be best when using a CMS or other system that allows you to upload templates into them. I can imagine Postorius one day supporting this feature. The way to do cache invalidation for the template you added to the database would be (let’s say for mailing list alpha(a)example.com) $ mailman shell -l alpha(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the alpha(a)example.com mailing list >>> getUtility(ITemplateManager).delete('list:member:generic:footer', m.list_id) More information is provided here: https://gitlab.com/mailman/mailman/blob/master/src/mailman/interfaces/templ… http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html Cheers, -Barry

8 years, 8 months

Re: Settings for https support

by Abhilash Raj

On Thu, Jan 16, 2020, at 5:15 AM, Dieter Leupold via Mailman-users wrote: > Hi, > > I configured Postorius (via Apache2) to use https, which looks fine. But > the connection to hyperkitty failed with "code 400, message Bad request > syntax". I tried serveral settings....without success. Could you give me > an example, which settings are to configure? > Thanks for your help! When you say "connection to hyperkitty failed", did you mean in the browser or when archiving the emails? If it is in browser, you can add `DEBUG=True` in your settings.py and get more details, which can be helpful to determine what is happening here. I am not completely sure why would HK have problem when P works fine, given that they are both served from the same Django server. > -- > > Dieter > > > _______________________________________________ > 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, 5 months

Installing Mailman3 under a Python Virtual environment running on RHEL9

by Andy Macheta

Hi, So tried, without much success, to get Postorius working on my Mailman3 server and every internet trick& tip I tried did not work so decided to take a new approach as recommended at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Used this reference: https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ would also work with Red Hat. Fell at the first hurdle with no packages available called "python3-dev" or "python3-venv" Is there anyone that has managed to install a running version of Mailman3 that has a working GUI whether it is on bare metal or Python virtual environment and if so, could they kindly let me know how they did it?? The closest I've come is a running command line version of Mailman3 which is fine for me of course but not for anyone else as they like access via web browser. Thanks in advance, Andy Macheta

2 years, 1 month

Re: Mailman3 is wrongly display name a list member

by Allan Hansen

Thank youi, Stephen. Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still show up as 'B'. Now, for the workaround: " If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists." I modified the above workflow to: Removed the address from all the lists. Set the account display name to 'A' in Django. Verify that she is not subscribed to any list at all. Deleted the email address in Django (under 'Email addresses'). Resubscribed her as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still has 'B' when I list it in Postorius. Further: When I search for 'Email addresses' in Django's list of emails (by account or email), it no longer exists. When I search under 'Users' (by account or email), it exists with 'A' as the display (which she entered when she created the account). Then since the email does not exist, under 'Email addresses' in Django, I go to 'Add email address', enter her account name and address. This gives and error: 'Select a valid choice. That choice is not one of the available choices.' I get this error no matter which 'Save...' button I press. I then tried to get into REST as per your advice here: " I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) " I get this, after setting myself up as user mailman (which works when entering mailman commands): mailman@list:~/scripts$ python3 Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from mailman.testing.documentation import dump_json Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'mailman' Looking around, I found mailman related stuff in /opt/mailman/mm and a file called 'mailman' in opt/mailman/mm/bin but hesitated editing your command above to: /opt/mailman/mm/mailman.testing.documentation (I don't want to mess up my system). So no go... Sorry for ranting. __ Please: 1. Always use the display name and email set up in the account everywhere. 2. Allow the member to change her display name using the account UI. 3. Allow the member to change her address and apply the new address to all list subscriptions. Yours, Allan On 1/11/22, 7:20 , "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

4 years, 5 months

Re: Rendering HTML for moderation

by Mark Sapiro

On 10/28/19 1:37 AM, Gila Halpern wrote: > Hi, new member here doing some research for my boss. Does Mailman 3 allow > HTML rendering in the moderation queue, or only plain text? I'm asking > because our list mod doesn't have time to check each image in a submission > individually, so we currently don't allow images, but the boss wants to > allow them. Postorius displays only plain text of a held message with HTML and images shown as attachments, and clicking an HTML attachment link will download the HTML and what happens depends on the browser, but if there are image parts referenced in the HTML, they will be separate links to download and won't render along with the HTML. However, is the list is set to notify the moderators of held messages, the notice will imclude the entire message which should render properly in the moderator's MUA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Re: Filter who can send on mailman3 list?

by Stephen J. Turnbull

Marcus Granath writes: > Sorry, but actually I can not find any "Users dropdown" to select > "Non-Members" at any Postorius in my web interface. :-( > Maybe, could it be that I am actually not the admin of the mailman3 > server, I'm "just" the admin of my mailman-list - so just admin for > my mailman-list and not for the mailman server? I think if you are *moderator* you should be able to see the Subscribers list, but maybe you need to be *list owner*. You definitely do not need to be *server admin* to see the Subscribers list. I'm not sure if the *server admin* has a way to see a sitewide Users list (other than using the mailman command line tool or directly from the database). Is it possible that you have multiple logons on the server, one of which you have subscribed to lists and the other is a user with administrative privileges? I know that burns me regularly. Steve

5 years, 2 months

Re: Adding users

by horvath.arpad.szfvar＠gmail.com

In my lists there are no big changes. I just need to add one or two persons a year as choir members doesn't change too much. I try to find out the parameters of the mailmanclient.Client I guess the URL is the REST root url from the output of the `mailman info` command I tried to add the admin username and the password with which I log into the postorius page. Or the rest admin is a different one? In [2]: mmc = mailmanclient.Client( ...: "http://localhost:8001/3.1/", ...: "admin", ...: "somepassword", ...: ) In [3]: mmc.get_list('korus') But that gives me this error /usr/lib/python3/dist-packages/mailmanclient/client.py in get_list(self, fqdn_listname) 354 :rtype: :class:`MailingList` 355 """ --> 356 response, content = self._connection.call( 357 'lists/{0}'.format(fqdn_listname)) 358 return MailingList(self._connection, content['self_link'], content) /usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py in call(self, path, data, method) 125 error_msg = response.text 126 --> 127 raise HTTPError(url, response.status_code, 128 error_msg, response, None) 129 if len(response.content) == 0: HTTPError: HTTP Error 401: REST API authorization failed

3 years, 7 months

Mailman-users search results for query "Postorius"