Search results for "Postorius" - Mailman-users

Re: moving lists to another server

by Mark Sapiro

On 11/17/23 00:51, Odhiambo Washington wrote: > I am scratching my head bald trying to figure out how to bring in this > other MM3 site and list into my existing server, especially with regard to > the DB backend. > > The list - let's call it users(a)domainX.name was using MySQL backend and > had a separate DB for Mailman core and Mailman web. > I believe combining these into one isn't a problem. But getting to merge > this DB into my current one is what I am not sure about. This is https://gitlab.com/mailman/postorius/-/issues/13 which is a real need, but doesn't yet exist. I think the easiest thing for the archives is to forget the Mailman web DB and just export the archive as a mbox from the other site (if it's large, exporting the entire archive will time out so you have to do it in pieces). Then you can use hyperkitty_import to import it. For the list data, it's probably easiest to just create the list manually and go through the settings in Postorius and make them match, although you could dump the mailinglist table entry where list_id = 'users(a)domainx.name' and load that, but you'd need to edit the id field in the dump to match the id on your server. That leaves the members. Doing this with a DB dump/load would be very complex because while the member table has a list_id field which is the id of the list's entry in the mailinglist table and can be used to select the relevant members, these records also link to entries in the address, preferences and user tables and matching them would be an issue. I think a custom script would be required. If I were doing this, I would make a separate database on my server with a copy of the data from the other server and then try to make a script that would extract data from the other database and add it to mine. Alternatively you could just dump the members from the other servers with the `mailman members` command perhaps separately for regular and the different digest types and then add them with the `mailman addmembers` command. This wouldn't get all their attributes, but it could work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: New platform administrators

by Abhilash Raj

On Tue, Sep 18, 2018, at 1:14 PM, Simon Hanna wrote: > On 9/18/18 5:42 PM, Hellen Cubero wrote: > > Hello! > > I would like to know how to add a new site administrator to the mailman 3.2 > > platform. Can you help me please? > > You are probably referring to Postorius the webui? > > If yes, you just add another superuser. If the admin is enabled, you can > just visit https://you-url/admin sign in, and create a new user with > staff and superuser permissions. > > You can also do that on the cli using ./manage.py createsuperuser A better way would be to ask them to sign-up as a regular user and then you can go into the Admin Console (/admin) and add flags for Superuser for the user you want to promote. Create Superuser and Django's create user interfaces don't tie up with all-auth, which creates problems because their EmailAddress records aren't created, like they should be. -- thanks, Abhilash Raj (maxking)

8 years, 1 month

Re: Default setting for Delivery status

by Mark Sapiro

On 10/10/22 15:31, Mark Dale via Mailman-users wrote: > > Where and how do I set the default setting of "Delivery status" to be > "Enabled". It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… > I'm not seeing any clues in mailman3-web/settings.py > > At the moment, a new subscriber is neither "Enabled" or "Disabled". That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: Wrong info in moderation mail when held due to match of a header rule

by tlhackque

On 17-Oct-20 18:40, Mark Sapiro wrote: > On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: >> I might also add the rule number or config filename:line, as in >> >> Header "{name}": rule in {file}:{n} matched value "{value}" >> >> This would be helpful when backtracking from a rejected message to the >> cause. >> >> A sample expansion might be: >> >> Header "X-Spam": rule in foo.conf:83 matched value "yes" > > These rules are not in a configuration file. They are in the headermatch > table in the database and the rules for a particular list are exposed on > the Header filters tab in Postorius or at the REST > lists/LISTNAME/header-matches endpoint. > > Perhaps something like > > {name}: header match rule, pattern "{pattern}" matched value "{value}" > > example: > > subject: header match rule, pattern "sex|long|list|of|other|bad|words" > matched value "This is a post about filtering based on words like sex in > the subject." > > but that could be just adding more clutter. > I considered including the regex in each message, but that seemed redundant - and potentially long. Thus the pointer. Perhaps number the rules for each list, and use that index? The ROWID would seem to be a candidate for the number. Then Postorius could simply number the rules in its tab; the REST API can add the ROWID as a rule_ID field in the returned JSON. (The fact that it's a ROWID rather than an index or unique name is an implementation detail.) If many rules are anticipated, it might want an endpoint or option to fetch a rule by ID. Then it would be easy to drill down on a specific event for diagnosis. e.g. shunt_reason: (or whatever) { cause: "header_match" header: "subject" header_value: "This is a post about filtering based on words like sex in the subject." rule_id: 47 /* or pattern_id? */ } displays as subject: header match rule 47, matched value "This is a post about filtering based on words like sex in the subject." and lists/LISTNAME/header-matches/47 returns { rule_id: 47 pattern: "sex|long|list|of|other|bad|words" position: 3 /* Whatever else is in your table... I haven't looked since I postponed using MM3. eg */ comment:"Required by policy 869.202" last_updated_by: "Corporate Prude" last_updated_on: "1-Apr-1762" }, while lists/LISTNAME/header-matches returns an array of those structures, presumably as today. With those capabilities, the UI can be enhanced so that clicking on a shunted message gives the summary reason, and clicking on the summary gives the regex. I expect that the header and value will be sufficient for understanding an issue most of the time. Looking at the regex is less common, and only necessary when it needs to be updated... I still think that it is more readable and less verbose to order the message as a declarative sentence: Header "subject": rule 47 matched value "sex" but that may be a matter of personal taste. The UI can sort that out... Note that from your description, using ROWID may cause rules in a particular list to have gaps in the rule numbering. I don't think that's a big issue, though Postorious could paper that over - perhaps use the position attribute. Doesn't seem worth doing something more complex. The advantage is that it doesn't require any DB change now. But aliasing it to "rule_id" allows for any future demand to name the rules or use some other numbering scheme. I may have some details wrong - I found mm3 not ready for my needs and am thus out of date - but I hope the high level approach that I outlined is useful.

6 years

Re: Mailman Header Behavior

by Samir Faci

Perfect, Thanks. Is there a way to set this as a default for all new lists being created? Still working on the new styles, I imagine that can be set there during the selection of the list type. -- Samir Faci On Fri, May 15, 2020 at 9:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/20 9:31 AM, Samir Faci wrote: > > > > Is there a way to force mailman to ensure that the list name shows up in > > the from field? > > In Postorius Settings -> DMARC Mitigations set DMARC mitigation action > to Replace From with list address and set DMARC Mitigate unconditionally > to Yes. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

6 years, 5 months

Re: Unable to remove non-member

by Mark Sapiro

On 9/29/20 4:54 AM, Brian Carpenter wrote: > On 9/29/20 12:40 AM, Mark Sapiro wrote: >> Is that all it said? The code says it is >> >> The user could not be removed: <error message> >> >> Where <error message> is the relevant HTTP error. > > It says: > > The user could not be removed: > > Nothing comes after the colon. > I see the issue. when mailmanclient processes the delete request from Postorius it calls the REST API DELETE method with the URL lists/<listname>/<role>/<address> and the address is `quoted` with urllib.parse.quote_plus, co in this case, the URL becomes lists/<listname>/nonmember/z_email%2Fdomain.org.za(a)domain.org.za This is all fine except the REST API doesn't call urllib.parse.unquote_plus to change the %2F back to slash. This is now reported at <https://gitlab.com/mailman/mailman/-/issues/774>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Re: Django Internal Server Error on held_messages

by Mark Sapiro

On 3/24/22 04:02, Hasan Berkay Çağır via Mailman-users wrote: > Hello, > > We've been running a Mailman3 instance with Debian 10's official package: > > Mailman Core Version: GNU Mailman 3.2.1 (La Villa Strangiato) > Mailman Core API Version: 3.0 > Mailman Core Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] > > For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email: > > """ > Internal Server Error: /postorius/lists/list.example.com/held_messages As Andrew suggests, you will probably find exceptions with tracebacks in Mailman core's mailman.log. This is probably /var/log/mailman/mailman.log in the Debian package. If you find such and you can't determine the problem from them, post one here. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Mark Sapiro

On 3/31/25 06:26, Philip Bondi wrote: > My /etc/mailman3/urls.py is empty. > > Should I, like it indicates in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > cp /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py /etc/mailman3/urls.py > chown mailman:mailman /etc/mailman3/urls.py > and add to /etc/mailman3/settings.py > > ROOT_URLCONF = 'urls' You can do all of that, but it's probably unnecessary. What is in /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py? compare it to https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > After completing above, https://systemdatabase.ca/mailman3 still gives > Service Unavailable It appears that https://systemdatabase.ca/postorius works so the issue is almost certainly that your urls.py is missing path('mailman3/', include('postorius.urls')), -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: > >Hi Mark, > > > >Actually all this stuff happens inside the container after it's started > >and > >initialized without errors. I didn't amend the image anyhow. > > > >Also I have the configuration based on docker-compose.yaml provided in > >the > >repository which works just fine for mailman-web image. > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > >fails > >with 500 error... > > > >Now answering your questions: > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > >what > >> is set for Q_CLUSTER? > >> > > > >I've checked settings.py inside the container and I haven't found any > >of > >the mentioned configurations there. > > > >Does the manage.py that's being run here point to the right > >settings.py? > >> > > > >No clue. > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > >configured image? > > > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > Because I am a dum dum ;-) > > Will work on removing those crons and stuff. Would be nice if you > opened an issue on Github so that I don't forget. Should now be fixed in the latest image. > > >Danil > > > > > > > >> -- > >> 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/ > >> > >_______________________________________________ > >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/ > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- thanks, Abhilash Raj (maxking)

7 years, 8 months

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, 9 months

Mailman-users search results for query "Postorius"