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

[MM3-users] Re: mailman 3.x upgrade and downgrade

by C. Souza

Ok, thanks! On Tue, Jul 12, 2022 at 1:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/22 9:35 AM, C. Souza wrote: > > > > I can't see the mistune package, maybe it wasn't a requirement for that > > version of mm3. > > > > 1 Package Version > > 2 ------------------- ---------- > > ... > > 39 HyperKitty 1.3.3 > > > Correct. It is not a requirement until HyperKitty 1.3.5 > > -- > 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/ >

3 years, 9 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 5:40 PM, Paul Arenson wrote: > >> Assuming MUA means a mail application. And if that mail application has no reply list function then the setting doesn't work. MUA means Mail User Agent which is another name for mail application, YES. > Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) > >> It is the presence of the >> List-Post: header in the message that allows the MUA to offer/process >> the "reply-list" function. > > Ok, I asked how to make it ANNOUNCE ONLY and you said to use "allow_list_posts is False" which is the same as "Include the list post header". Not exactly. You asked what settings were different between discussion style and announce only style. What I answered was that the only setting that differed as set by the style was what Postorius calls "Include the list post header". What I didn't say explicitly was that this is not sufficient to prevent posting to the list. > So does this mean that for a subset of users I cannot make it ANNOUNCE ONLY? And is it some other setting (send to moderator) that prevents it from being a DISCUSSION list? What exactly do you want? You found some info on configuring an announce only list and I referred you to a FAQ on that subject. Both of these do not directly address Mailman 3, but they do give useful information. I am going to stop guessing at what you want to accomplish, so tell me what you want to happen when someone sends a post to the list either from HyperKitty or by email. What should happen to the message? What if anything should be sent to the user? Should this behavior be the same for all users or just a subset. If a subset, how do you identify that subset and what should happen when others attempt to post? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: moving lists to another server

by Mark Sapiro

On 11/20/23 00:58, Odhiambo Washington wrote: > > What is the command to export the archive as a mbox from the DB? > I can't figure out which option it is by looking at 'mailman-web -h'. Normally you do this on the old server via the HyperKitty web UI which has download buttons which do things like https://example.com/archives/list/list@example.com/export/list@example.com.… or for a partial archive https://example.com/archives/list/list@example.com/export/list@example.com-… However, in your case I don't think you have the old installation working any more so the above won't help. > BTW, how will ' mailman addmembers' treat a file containing: > ``` > Firstname Lastname <email@address> > Onlyname <email2@address> > ``` Correctly. It will import email@address with display name = 'Firstname Lastname' and email2@address with display name = 'Onlyname'. > I have opted for the simple way to do this: > 1. Create the site in Django Admin and create/configure the list in > Postorius > 2. Add the members from the file dump, with delivery set to regular. > 3. Send the members an email informing them that they need to set their > delivery preferences. > > I am stuck on the issue of exporting the archives to mbox file as already > stated above. Perhaps you can export the mbox via the web UI on the old server or maybe temporarily create a second mailman-web on your server with the old mailman-web database and use that web UI. Otherwise, if you have a working mailman-web that can access this database, you could try something like ``` $ mailman-web shell >>> from hyperkitty.lib.compat import get_list_by_name >>> mlist = get_list_by_name('list_name_only', 'list_domain') >>> with open('output.mbox', 'wb') as fp: ... for email in mlist.emails.order_by("archived_date").all(): ... fp.write(email.as_bytes() + b'\n') ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Update a member's display_name

by Mark Sapiro

On 1/17/19 8:45 AM, Nick Wynja wrote: >> user_manager = getUtility(IUserManager) >> u = user_manager.get_user('aperson(a)example.com') >> u.addresses[0].display_name = "Anne" >> commit() > > It seems this method updates the display_name for the user across all lists. Is there a way to update just a single instance of "member" of a list rather than the site-wide user? > > I've tried this: > > mailman shell -l test(a)example.com > >>>> mem = m.members.get_member('a(a)example.com') >>>> mem > <Member: a(a)example.com on test(a)example.com as MemberRole.member> >>>> mem.display_name > 'Anne' >>>> mem.display_name = "Anne P" > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: can't set attribute That's because mem.display_name is a "calculated" attribute. The definition of the IMember class says > display_name = Attribute( > """The best match of the member's display name. > > This will be `subscriber.display_name` if available, which means it > will either be the display name of the address or user that's > subscribed. If unavailable, and the address is the subscriber, then > the linked user's display name is given, if available. When all else > fails, the empty string is returned. > """) and > subscriber = Attribute( > """The object representing how this member is subscribed. > > This will be an ``IAddress`` if the user is subscribed via an explicit > address, otherwise if the the user is subscribed via their preferred > address, it will be an ``IUser``. > """) So there is no member display_name per se. The display_name is the display_name of the associated IUser or IAddress, and these are global. The bottom line is there is not a way to update just a single instance of "member" of a list rather than the site-wide user or address? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 3/31/23 14:17, Andrew Hodgson wrote: > Hi. > > Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in ``` --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 @@ -2,13 +2,13 @@ import os import sys -sys.path.insert(0, '/opt/mailman/mm') +sys.path.insert(0, '/etc/mailman3') # The above line is required. The next line doesn't hurt, but it doesn't work # because the PYTHONPATH environment setting is processed by Python's setup # and must be in the environment when Python starts to be effective. -os.environ['PYTHONPATH'] = '/opt/mailman/mm' +os.environ['PYTHONPATH'] = '/etc/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' import django django.setup() ``` Also, look at this ``` # If we delete the Django user and there is a Mailman user with no memberships # shall we delete the Mailman user too. DELETE_MAILMAN_USER = False # Shall we delete the Django user if there is a Mailman user with no # memberships or only if there is no Mailman user. DELETE_DJANGO_IF_MAILMAN = True ``` and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/26/24 09:21, Elias Rudberg wrote: > > Yes, there are strange-looking long queries there at the times when > these errors happen. > > Here is an example of what such a request URL looks like, where I have > replaced some parts with [...] to avoid including anything sensitive: > > Request URL: > https://[...ip-address...]/mailman3/postorius/lists/?widget=[...]svg[...]onload=confirm[...]xss-widget[...]&height=[...]svg[...]onload=confirm[...]xss-height[...]&screen=[...]svg[...]onload=confirm[...]xss-screen[...]&pass2=[...]svg[...]onload=confirm[...]xss-pass2[...]&redirect_to=[...]svg[...]onload=confirm[...]xss-redirect_to[...]&items=[...]svg[...]onload=confirm[...]xss-items[...]&string=[...]svg[...]onload=confirm[...]xss-string[...]&hidden=[...]svg[...]onload=confirm[...]xss-hidden[...]&f=[...]svg[...]onload=confirm[...]xss-f[...]&step=[...]svg[...]onload=confirm[...]xss-step[...]&role=[...]svg[...]onload=confirm[...]xss-role[...]&preview_nonce=[...]svg[...]onload=confirm[...]xss-preview_nonce[...]&date=[...]svg[...]onload=confirm[...]xss-date[...]&event=[...]svg[...]onload=confirm[...]xss-event[...] I see similar ones from time to time. > I looked up the IP address that those requests come from (all seem to > come from the same IP address) and that corresponds to a hostname called > something with "scanner" that looks like it belongs to some > cybersecurity company. There are also many other requests from that same > IP address, including things like "GET /file://etc/passwd" and similar, > so it looks like someone is bombarding us with various weird requests as > a form of "scanning" where they are trying to find vulnerabilities. That > could also explain why we see those "Internal Server Error" errors > recurring every day, if they run that vulnerability scan daily. Yes, I think these are attempts to find vulnerabilities. > So maybe those strange request URLs that lead to the error messages > "[Django] ERROR (EXTERNAL IP): Internal Server Error" that we are > seeing, are constructed by someone who is actively trying to trigger bugs. I don't think this is a DOS attack or an attempt to trigger bugs. I think they are attempts to find and then exploit vulnerabilities. > But anyway, no matter what strange request URL comes in, I guess the > "Internal Server Error" indicates something going wrong in Mailman or in > Django, a bug in how the request is processed? I'm not certain, but I think it's a Django issue rather than a Mailman issue. In my case, I don't get that many and I just ignore them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Johannes Rohr

Am 09.01.23 um 06:30 schrieb Mark Sapiro: > On 1/8/23 01:37, Johannes Rohr wrote: >> >> Am 16.09.21 um 01:13 schrieb Mark Sapiro: >>> >>> Currently Mailman 3 does not support whitelisting the members of >>> another list. >> >> Is this still true in the current version? I have been using this >> quite extensively with mailman2, so loosing it is the one major >> drawback of the migration. > > > Yes it is still true. This is > https://gitlab.com/mailman/mailman/-/issues/794 Thanks! I assume, there is a reason why this cannot be easily implemented, else it would have been. Asking because I know a number of people would make extensive use of this in MM2. Johannes

3 years, 4 months

[MM3-users] Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/7/22 16:11, Philippe B wrote: > I think that your last sentence helped us figure out what's going on. > > When Mailman generates a moderation message "To: LIST-owner" it actually delivers it to the address(es) of the LIST's moderator(s), which makes sense. No, it delivers the message to the union of the sets of owner addresses and moderator addresses. > In all the cases where we've seen that behavior, it turns out that the list involved didn't have any moderator, and we have site_owner set to "mailman"... You don't need to have moderators. The owners get the message too. > However, the lists had an owner, and we're not seeing those moderation messages being sent to their owner (instead). Is that something that needs to be configured explicitly somewhere? The only things that might affect this are if Settings -> Automatic Responses -> Autorespond to list owner is Respond and discard message or if the owners delivery_status is other than DeliveryStatus.enabled. Note that finding an owner's delivery status is tricky. The owner can find it in Postorius by going to https://www.example.com/mailman3/accounts/subscriptions/ and clicking on the entry for the list with role owner. This delivery status is not the same as the delivery status for the same address with a member role if there is one. For an admin you could do ``` $ bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> owner = m.owners.get_member('user(a)example.com') >>> owner.delivery_status <DeliveryStatus.enabled: 1> If you needed to set it here, you could do >>> owner.preferences.delivery_status = DeliveryStatus.enabled >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

sorry, in this directory: /var/lib/mailman/var/logs Thanks El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

Jan Eden wrote: > I tried setting permissions on /opt/mailman/fulltext_index to 777 > temporarily, but the issue remained (as expected). It occurs in the > Whoosh backend of Haystack (whoosh_backend.py, line 132-133): > > if self.use_file_storage and not os.path.exists(self.path): > > > > os.makedirs(self.path) > > > where self.path is referenced, which is defined in line 110 (as part of > the __init__ function): > > def __init__(self, connection_alias, **connection_options): > > super().__init__(connection_alias, **connection_options) > > self.setup_complete = False > > self.use_file_storage = True > > self.post_limit = getattr(connection_options, "POST_LIMIT", 128 * 1024 * 1024) > > self.path = connection_options.get("PATH") > > > > Unfortunately, I cannot see where the PATH key for connection_options is > defined. It is defined in the HAYSTACK_CONNECTIONS dictionary in your Django settings.

3 years, 5 months

Search results for query "sapiro"