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

[MM3-users] Re: mailman changeaddress: Address already exists; can't change

by Mark Sapiro

On 10/10/24 8:58 AM, joelbrownstein(a)computer.org wrote: > Hi, > > We migrated ~100 lists from mailman2 to mailman3 (very nice!) including > 6000 distinct email addresses ("subscribers"). > > I would like to run the mailman changeaddress command to do a global change of email for a member that moved. But they have other subscriptions using their new email, so both the old and new address are migrated to mailman3 as distinct "members", which prevents the mailman changeaddress from making the change with error: > > $ mailman changeaddress "EMAIL_1" "EMAIL_2" > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address "EMAIL_2" already exists; can't change. There is a major difference between MM 2.1 and MM 3 in this respect. In MM 2.1, a list member is an email address that bears no relation to any other member of this or any other list. In MM 3, there is a user which corresponds to a person which has one or more email addresses which can be members of lists with various roles. What happened here is importing the MM 2.1 lists created a user for EMAIL_1 and subscribed it to some lists an created a separate user for EMAIL_2 subscribed the other lists. You can't change EMAIL_1 to EMAIL_2 because EMAIL_2 is already a separate user. There are two ways to deal with this. You can use `mailman findmember EMAIL_1` to list all of EMAIL_1's memberships and edit that to make a shell script that will do `echo EMAIL_2|mailman addmembers -f - LISTNAME> to add EMAIL_2 to all of EMAIL_1's lists and then do `mailman delmambers -m EMAIL_1 --fromall` You could do direct database manipulation. First get the id and user_id of the address table entries for email = EMAIL_1 and EMAIL_2. If we call them aid_1, uid_1, aid_2 and uid_2, do ``` UPDATE member SET address_id = aid_2, user_id = uid_2 WHERE address_id = aid_1; ``` Caveat: I haven't done this. I think it should work, but no guarantees. Backup the database first in case of problems. After doing either of the above, there will still be a user with address = EMAIL_1, but that user should have no subscriptions. You can delete that user via Postorius and if desired the remaining user with address EMAIL_2 could add EMAIL_1 as another address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did not interrupt the running process... It's running, but I cannot see anything El vie., 21 jul. 2017 a las 16:08, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:00 PM, Rafael Mora wrote: > > Yes I did ran it in the env2 python2 virtualenv, it > > says: ERR_CONNECTION_REFUSED > > I stopped the firewalld service and it's still refused > > > After you ran 'manage.py runserver' did you leave that terminal window > open with that process running? If you control-C or interrupt it in any > way, it stops listening. > > > > I installed uwsgi, should I put the config inside mailman.cfg?? > > > Not yet. That's for production. I don't think you're there yet. > > -- > 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, 3 months

[MM3-users] Re: Postorius not HTML-decoding < to "<" characters

by Mark Sapiro

> > Does that mean the DB has data with mismatched tags in it? The database has exactly what list members receive by email. What we are talking about is how this is rendered in HyperKitty. > Interestingly, the quoted part of my message has < where my message > has proper less-than and greater-than for the Apache tags. > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > It's inconsistent with the archive rendering mode at lists.mailman3.org. Here's what's going on. In normal text, mistune disables HTML tags by converting `<` to the html entity `<`, but your browser renders the HTML entity `<` as `<` so you see what was written. The issue here is the text you quoted was originally in a markdown code block, i.e. preceded and followed by lines of three backticks. Code blocks are intended to be seen literally as written so they are wrapped in <pre><code> ... </code></pre> tags in the HTML and also HTML escaped. The problem is the tag disabling converts `<` to `<` but then the HTML escaping converts `<` to `&lt;` which your browser then renders as `<` rather than `<`. (aside, it will be interesting to see how that is rendered in the archive) If HyperKitty is set to render as plain text rather than markdown it doesn't interpret code blocks so this doesn't happen. There are other anomalies with the markdown rendering, e.g., as pointed out by Jeremy at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Those notwithstanding, we prefer markdown rendering for this list because often people post Python snippets or `mailman shell` interactions and enclosing those in markdown code blocks renders them much better. > I haven't currently got an instance that I can test on but will keep > this in mind when the time comes to migrate. > > Should the rendering at lists.mailman3.org get modified, please share > the procedure. > > > > Testing: less-than and greater-than around a tag: > > <Location /mailman/accounts/signup> > > Testing: less-than and greater-than around a tag in a quoted block: > > > <Location /mailman/accounts/signup> Both the above tests look fine in the archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Mark Sapiro

On 10/31/18 5:57 AM, Thomas G wrote: > Hi, > > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… > > I changed "sender" for this; > # Sender > try: > from_str = header_to_unicode(message['From']) > from_name, from_email = parseaddr(from_str) > from_name = unidecode.unidecode(from_name).strip() What is unidecode? > except (UnicodeDecodeError, UnicodeEncodeError): > raise (ValueError("Non-ascii sender address", message)) > > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown(a)unknown.com" > else: > sender_address = "unknown(a)unknown.com" > print("Non-ascii sender addre -- Sender address replaced by ", > sender_address) > > I got this output (example): > |Non-ascii sender address -- Sender address replaced by > stephaneblipblopstlablipblopgmailcom > It's not really perfect, I'm working to do something better, but basically > it's works. The original code intends to provide some value for the email address where parseaddr returns a null address. You have an address, and you would do better to remove the non-ascii from the address than to try to make and address out of the sanitized real name. Your issue is parseaddr() returns an email address with non-ascii. I would suggest that instead of > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown(a)unknown.com" > else: > sender_address = "unknown(a)unknown.com" you do > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > sender_address = from_email.encode('ascii', errors='replace').decode("ascii").strip() > I think that there is a issue in the original code: > Because : "" raise ValueError("Non-ascii sender address", message) "" > > The second part will be never call: It will if there is no exception. > if not sender_address: > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown" > sender_address = "{}(a)example.com".format(sender_address) > else: > sender_address = "unknown(a)example.com" > > If you bypass : "" raise ValueError("Non-ascii sender address", message) > "", by a simple print(), you will get an error due to an unassigned > variable (sender_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

[MM3-users] Re: How to delete non-users

by Mark Sapiro

On 9/16/22 11:19, Allan Hansen wrote: > Hi all, > > This is a bit of an emergency: > > I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. > For individuals I have been able to delete their non-membership and they then could subscribe properly. I don't understand. the fact that an address is a non-member of a list should not impact subscribing that address as a member. > I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. What is actually happening when the non-member attempts to subscribe as a member? What do they do and what it the result? > I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). > > Can anyone help me find out how to > a. delete all non-members of all my lists If you have access to `mailman shell` you could do: ``` $ mailman shell 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. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> commit() ``` > b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) nonmembers are an integral part of Mailman 3's architecture. The basic idea is a nonmember has a moderation action and setting a nonmembers moderation replaces MM 2.1's adding that address to one of *_these_nonmembers (The legacy *_these_nonmembers attributes still exist, but only to support regexps). It would require extensive modification to not create nonmembers. However, I still don't understand why the presence of a nonmember record is an issue. -- 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: 500 Internal Server Error on specific list pages

by Mark Sapiro

On 7/30/20 9:05 AM, Johnny Cison wrote: > The Mailman logs contain the following: > > Jul 30 10:32:11 2020 (26190) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, > in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 215, in falcon.api.API.__call__ > (falcon/api.c:2872) > File "falcon/api.py", line 189, in falcon.api.API.__call__ > (falcon/api.c:2419) > File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 346, in > on_get > archiver_set = IListArchiverSet(self._mlist) > File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line > 135, in __call__ > adapter = self.__adapt__(obj) > File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line > 151, in __adapt__ > adapter = hook(self, obj) > File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, > in adapter_hook > return sitemanager.queryAdapter(object, interface, name, default) > File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line > 348, in queryAdapter > return self.adapters.queryAdapter(object, interface, name, default) > File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line > 353, in queryAdapter > return self.adapter_hook(provided, object, name, default) > File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line > 363, in adapter_hook > result = factory(object) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line > 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() > File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2793, > in one_or_none > "Multiple rows were found for one_or_none()") > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() This is a known issue <https://gitlab.com/mailman/mailman/-/issues/657>. There are two entries for the same `mailing_list_id` and `name` in the listarchiver table in the database. We don't know how this happens, but you need to delete one (either one) of the duplicates. Also see the recent thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. If you have any idea about how this might have occurred in your case, let us know. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 9:23 AM, Mohsen Masoudfar wrote: > > 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. > After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" This is <https://gitlab.com/mailman/mailman/-/issues/417> fixed by <https://gitlab.com/mailman/mailman/-/merge_requests/329> in Mailman core 3.2.0. Either upgrade Mailman core or set it via `mailman shell` > 2- I checked the python files and found this file, where, it seems, the default value is defined: > /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 > > I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: > The message is being held because: The message is larger than the 40 KB maximum size Changing that file only affects the default setting for new lists. It doesn't affect any existing list. To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like $ /opt/mailman/mm/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 >>> m.max_message_size 40 >>> m.max_message_size = 0 >>> commit() > 3- I totally agree that the most important issue is the fact that the message vanished with the production list. > I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. > > 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ OK, but what if anything is in Mailman's mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 3:41 PM, David Newman wrote: > > There are 24 messages in the shunt queue, the most recent of which is a > digest from 0000 hours today. The test messages I sent later today are > not there. > > There are also 13 messages in the out queue. I can't read these as the > filenames appear to change on every invocation of ls. I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/* >> Are there errors and tracebacks in var/logs/mailman.log? Every message in the shunt queue should have an exception and traceback logged in mailman.log. > But the Postfix log doesn't show it being distributed to me or anyone else. Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log? > Oddly, neither of the two list owner emails (me and someone else) show > this message in the archive via the admin panel. However if I log in as > the list owner directly to the archives: > > https://lists.domain.tld/archives/ > > I can see today's test posts if logged in as the list member, but do not > see the posts if logged directly into the archive as the Django superuser. That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can. > The nondelivery of list mail is more serious than the archive problem, > though. Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why? I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory. I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with `mailman qfile` and unshunt (reprocess) them with `mailman unshunt`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I made a change for test purpose on the mailman.cfg file and I got this: (env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running? How do I solve this? 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, 3 months

[MM3-users] Re: Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server

by Mark Sapiro

On 11/28/24 12:01 AM, peterrflores(a)hotmail.com wrote: > > Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? This is how things work. See for example https://mail.python.org/mailman3/?all-lists - each of those lists has its own settings. There are also `unadvertised` lists on that server, e.g. https://mail.python.org/mailman3/lists/capi-sig.python.org/ > Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. Mailman core provides a REST API for list management. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - this interface is only protected by a user name and password, so it is normally only available via `localhost` as wider access is not very secure. Postorius uses this API via the python bindings described at https://docs.mailman3.org/projects/mailmanclient/en/latest/ > Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. A list can be anonymous id desired which means the sender of a post is not identified in any headers of the distributed email. HyperKitty archives can be private, i.e. accessible only to list members. The membership list can be restricted to only list owners/moderators or available to list members as well via list settings. There is currently no support for encrypted email. Full access to a list's settings and other info via Postorius is limited to logged in users who are either a `superuser` or an owner of the list. moderators have more limited access, list members may be allowed to see the membership. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

Search results for query "sapiro"