Search results for "sapiro" - lists.mailman3.org

[MM3-users] [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by William Oliver

On Fri, 2021-12-24 at 21:12 -0800, Mark Sapiro wrote: > On 12/24/21 8:22 PM, William Oliver wrote: > > > > I clicked on that, and it took me to a page where I could add > > servers. > > So, I added my real domain (libertyfp.org) It successfully added > > it, > > so I decided that I clearly didn't need "example.com" as a server, > > and > > deleted it using the same page. > > > > Immediately, I got an "internal server error" and have now lost all > > web > > interfaces. I tried restarting the daemons and rebooting the box, > > to > > no avail. > > > You have to set SITE_ID in your Django settings to the correct value > for > your site. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > > Joy! You are a lifesaver. I had to guess at the ID number, but "2" worked. Just out of curiosity, if I could not have guessed a valid ID number and did not have the admin interface, how could I have figured out what site IDs were available? Thanks. billo

4 years, 5 months

[MM3-users] Re: Archive search failing on one list

by Mark

On 2023-09-24 13:28, Mark Sapiro wrote: > On 9/23/23 19:19, Mark wrote: >> >> Yes, the query returns a result and the case in "name" matches that in >> the query ... >> >> select * from hyperkitty_mailinglist where name like >> 'listname(a)domain.com' >> >> id | 91 >> name | listname(a)domain.com >> display_name | Listname >> description | ... >> subject_prefix | [Listname] >> archive_policy | 1 >> created_at | 2023-09-21 08:55:36.385239+2 >> list_id | listname(a)domain.com > > Is that really what you get for list_id? It should have a dot, not at > as listname.domain.com. > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models.mailinglist import MailingList >>>> mlist_name = 'listname(a)domain.com' >>>> mlist = MailingList.objects.get(name=mlist_name) >>>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> >>>> > ``` My bad. I was in too much of a hurry when redacting. The list_id is as you say: listname.domain.com

2 years, 8 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Allan Hansen

All, Appreciation to Brian for bringing this up. After upgrading to MM3, a lot of legitimate users' subscriptions on my lists have been disabled even though they still get at least some messages (according to them), while some were correctly disabled. Yes, I need to be informed of bounces, because when the accounts get disabled, I don't want my reply to be 'Huh? I don't have a clue why.' I reported this before. Yours, Allan On 3/26/21, 14:08 , "Brian Carpenter" <brian_carpenter(a)emwd.com> wrote: On 3/26/21 2:59 PM, Mark Sapiro wrote: > They are being bounced by a downstream MTA. If you want to know why, you > have a few choices. You can mail the address yourself and hopefully get > a DSN back. You can install this patch: I would think any mail administrator for a mailman server would want to know why bounces are happening. I never saw this issue with Mailman 2. Did it exist? Is the patch going to make it to the next version of Mailman 3 core? Are there any plans to make bounce processing more transparent to server admins so we can troubleshoot delivery issues? -- Brian Carpenter Harmonylists.com Emwd.com _______________________________________________ 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/

5 years, 2 months

[MM3-users] Re: Moving existing lists to a new domain

by Jeremy Stanley

On 2024-09-18 16:36:50 -0700 (-0700), Mark Sapiro wrote: > On 9/18/24 10:13, Jeremy Stanley wrote: [...] > > Since all the lists for the given domain will be moving to the same > > unused new domain on the existing server, and can move at the same > > time, I suppose this could be done through (offline if necessary) > > backend database update queries. [...] > ``` > UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = > 'old_domain'; > ``` [...] > ``` > UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE > mail_host = 'new_domain'; > ``` > For HyperKitty, similar changes need to be made to the > hyperkitty_mailinglist table. The `name` column entries need to be changed > from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column > entries need to be changed from `listname.old.domain` to > `listname.new.domain` Preparing to test this, I poked around the schema a bit and noticed that the domain names are also embedded as strings in the following fields: django_mailman3_maildomain.mail_domain django_site.domain django_site.name domain.mail_host Can anyone think of any additional tables/columns which would need updating for this? I'll see if scanning a dump of the full DB content turns up anything I might be missing too. Thanks again! -- Jeremy Stanley

1 year, 6 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Abhilash Raj

> On Nov 1, 2021, at 9:07 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/31/21 10:42 PM, Simon Coggins wrote: >> Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: >> https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 >> But it’s not in 1.3.5: >> https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 > > > Yes, I was mistaken. That code was merged on 14 Feb 2021 and is not in Postorius 1.3.4 which was released on 2 Feb. It should have been in 1.3.5 and I don't know why it is not at https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49, but that is moot in any case. > 1.3.5 was a security release with no fixed included. It was branched off from 1.3.4 and only the security fix was applied. One Gitlab pro tip is when you are trying to determine which particular release a particular commit is included in, you can click on the the “…” three dots next to "parent 6096958a master” just under the title and it will show all the tags and branches that this commit is included in. https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3… for example, is included in 1.3.6b1, 1.3.6 and jquery and master branch. -- thanks, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Re: Show diplay_name in a list

by Abhilash Raj

On Mon, Sep 30, 2019, at 6:33 AM, Joel Lord wrote: > On 9/29/19 5:59 PM, Mark Sapiro wrote: > >> Any idea what I was missing there? > > Often, member.display_name doesn't exist or is "None". > This seems to also be the problem that I submitted a while back (6 > months ago?) that the notification to the moderator of subscription > requests, which should include both display name and email address of > the requestor, only has the email address. We've been trying to track > the problem down in code but it keeps going deeper and deeper... This should be the UI trying to unconditionally convert a Python object to string. Name string transforms correctly, but since the absence of a name is denoted by a None object (as opposed to an empty string ''), the renderer mindlessly converts it to "None". It could be fixed with a simple {% if member.display_name is not None %}{{ member.display_name }}{% endif %} in the right place in the Django template. > > -- > Joel Lord > Web Administrator, Alpha Psi Omega Grand Cast > etc... etc... etc... > _______________________________________________ > 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, 7 months

[MM3-users] Re: Whitelist non subscriber

by Stephan Krinetzki

Mark Sapiro wrote: > On 08/06/2018 06:43 AM, Stephan Krinetzki wrote: > > > The steps are as follows, right? > > - Add users to the list and give the role "nonmember" > > - Set moderation action ('defer' or 'accept') > > Right. Good. So i understand it :) > > > > The only thing missing in the documentation is a note on how to do > > this via the Admin API. Who can explain that to me? > > Can you be more specific about what you are looking for? If by "Admin > API" you mean the REST API, are you asking how to interact with it or > what specific POST/PUT/PATCH commands to send? > > Or are you asking about the 'mailman shell' command? > With Admin API I mean the REST API from the localhost. Whether it's the REST API, the Mailman shell or the Admin API, I personally don't care. The only important thing is that we can set and use this role. However, I think that's settled anyway, since you're writing > > Also, we want to expose the nonmember role in Postorius and enable > setting moderation action for nonmembers, but we didn't get that in MM > 3.2/Postorius 1.2. So the whitelistening is not working at the moment, right?

7 years, 9 months

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Joachim Schrod

Mark Sapiro writes: > > > I maintain a mailing list for a private holiday where people don't > > subscribe themselves; I subscribe them. I have vetted their email > > address beforehand. (The subscribers are mostly not able to handle a > > verification email, nor any email-based workflow at all.) Is there a > > configuration option for a mailing list that sets "Pre Verified" to > > true as a default? > > > This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed > by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was > later extended by > https://gitlab.com/mailman/postorius/-/merge_requests/945 however these > are not available until Postorius 1.3.14 which is not yet released. > > These add a setting, POSTORIUS_DEFAULTS, which can be used to set these > defaults. E.g., setting > > POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True} > > will set the default for Pre Verified to True. So far, the only defaults > that can be set in this manner are mass_subscription_pre_confirm, > mass_subscription_pre_approve, mass_subscription_pre_verify and > mass_subscription_invite and those not until Postorius 1.3.14, but more > may be added. Thanks a lot for this info -- I'm looking forward for an upcoming Postorius 1.3.14 release! ;-) :-) Happy holidays and a good new year to everyone, Joachim

1 year, 5 months

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Abhilash Raj

> On Mar 27, 2021, at 3:03 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/27/21 2:08 PM, Brian Carpenter wrote: >> I was testing out the process of rejecting an incoming subscription >> request. Choosing the reject option for a moderated subscription request >> does send out a rejection notice but it gives no reason for the >> rejection. > ... >> Is there a place somewhere in Postorius to provide a rejection reasons >> for moderated subscription requests? Does Mailman 3 core provide this >> via its REST api but it is just not revealed in Postorius yet? > > > It's in Postorius since 1.3.3. If in the held message view, you click > the subject of a held message, you get a popup dialog the shows the > message with options to also show headers or the raw message. There is > also a dropdown t=o set the poster's moderation action and a box for a > reject reason if you click the reject button in the dialog. > > Do you not see this? I guess Brian was asking about Subscription Requests. Support for specifying reason when rejecting subscription requests has been added in master and will be a part of next release, 1.3.5 most probably. -- thanks, Abhilash Raj (maxking)

5 years, 2 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Andreas Barth

* Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: > > > --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro > <mark(a)msapiro.net> wrote: > > >On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: > >> > >>My conclusion: > >>I ask you to consider these experiences in an update for the mailman3 > >>packages in debian bullseye. It would save time, questions and nerves. > > > > > >Issues with Debian packaging should be directed to Debian. > > Or as previously discussed, the debian packages should be avoided entirely. I strongly disagree with that statement. Distribution packages have their own up- and downsides. Of course, how they are done is to be discussed with the distribution, so: if something is wrong with a debian package, please follow the instructions on bugs.debian.org on reporting bugs. However, they have the advantage that they're integrated with the distribution. They have the disadvantage that they're stable for some time - that is why it's called a stable release. If they have all the features someone wants, they usually work fine (and my first mm3-installation was the default debian package). If one looks for bleeding edge, of course that's not what one can expect from a distribution package - but that's also a feature. Andi

4 years, 6 months

Search results for query "sapiro"