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

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/24/23 14:36, Jens Günther wrote: > > - Shall I create all the mo-files (the other folders also only contain > the po)? If so, how would it be possible? > - How can I make it persistent? (probably it should be included in the > repo!? also another thread or an issue regarding maxxking's repo!?) We probably should distribute .mo files too, although currently they are explicitly excluded. I'll see if we have a good reason for not distributing them. > Exactly. What I was wondering: for the welcome-messages I did not have > explicit templates for those lists/domains/site that I wrote in German, > it has to be from the predefined templates, which are stored elsewhere > the in the mo-files!? (actually I don't get this point exactly but > wouldn't bother, if the above works). The templates are actually included in the mailman.po files so that they can be translated all in one place on weblate. However they are not retrieved from there. There are templates for some but not all supported languages in the mailman/templates/ directory in the installation and these are used by default, but these are not up to date in all cases with those in the mailman.po files. That should be fixed as well. In my case, for the servers I maintain, I update from the heads of the gitlab branches whenever there are significant changes and part of that process compiles the .mo files and updates the templates with scripts at https://gitlab.com/mailman/mailman/-/blob/master/generate_mo.sh and https://gitlab.com/mailman/mailman/-/blob/master/update_lang_templates.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Connection lost during _handle_client()

by Mark Sapiro

On 11/28/24 9:17 AM, Alain D D Williams wrote: > > /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are > being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck > The process doing this is a 'qrunner' The .bak file is the one currently being processed by the `out` runner. The others are waiting to be sent. I don't know why they are continually being dequeued and requeued I suggest you stop Mailman core and then examine these files with `mailman qfile` to see if there is some issue with one or more of them, but this seems unlikely. More likely is some issue with the `out` runner itself, but I have no idea what that would be except that issues like this can be caused by files in Mailman's var/templates/ directory that aren't readable by the Mailman user (often caused by running `mailman import21` as root). > I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log > > [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) This looks like some kind of DOS attack. Look at the GET requests in the web server log. > /var/lib/mailman3/queue/shunt/ contains 4 .pck files. For each of these, there should be an entry in mailman.log indicating the exception with a traceback. Look for entries in the log ending with a `SHUNTING` message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu > sends an email to a list, Mailman gets the email, processes it and would try to send that email to all members with a sender field as: 'joe.student(a)university.edu'. plus listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Mark Sapiro

On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. This format vs. plain text digests was a user option in Mailman 2. > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius. If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool. > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? It is the intent that Postorius will eventually expose all these settings. We're not there yet. At present you could possibly do this by interacting with mailmanclient, although I'm not certain the settings are exposed there. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 9 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/10/21 6:37 AM, Duane Raymond wrote: > Hi Mark, > > I think I have it working thanks to some hints in your questions. here is the process I took in case others experience it the same or in case anyone wishes to comment! > > When I use the mailman shell comment it seems to reflect just what you posted (I also tried test.campaigningforum.com and got the same result): > (venv) mailman@mail:/opt/mailman/mm$ mailman shell -l test(a)campaigningforum.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 test(a)campaigningforum.com mailing list > >>> > > Was there something beyond running this and getting the output I was supposed to enter? Was an error expected if one members doesn't have an associated address record? Did you enter this following the initial >>> prompt? >>> for mbr in m.members.members: ... if mbr.address is None: ... print('user: {}, user.addresses: {}'.format( ''' mbr.user, mbr.user.addresses)) ... If so, it was expected to print the representation of the user object and that objects addresses list fo any member whose address attribute is None. ... > This time the posting was archived and I did get an acknowledgement of the post, but despite having the option "Receive own postings" set to "yes", I didn't receive it. As you have determined, this is a googlemail issue. See <https://wiki.list.org/x/4030680>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Mark Sapiro

On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://gitlab.com/mailman/mailman/-/issues/385 which was fixed in Mailman 3.2.0 by https://gitlab.com/mailman/mailman/-/merge_requests/333. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Bug in 2.1.36?

by Mark Sapiro

On 11/12/21 1:06 PM, Joel Lord wrote: > I'm not sure if this is a bug or something about the new CSRF fix > doesn't get along with something I have (mis)configured, but this > definitely seems to be related. Sadly the script I use to backup > mailman before upgrading I recently stopped backing up the lists > themselves, so going back to 2.1.35 doesn't seem to be an option due to > the .pck file version bump. Here's the trace I get: > > Traceback (most recent call last): > File "/mailman/mailman-${domainslug}/scripts/driver", line 117, in > run_main > main() > File "/mailman/mailman-${domainslug}/Mailman/Cgi/admindb.py", line > 342, in main > print doc.Format() > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 352, in Format > output.append(Container.Format(self, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 267, in Format > output.append(HTMLFormatObject(item, indent)) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line 53, > in HTMLFormatObject > return item.Format(indent) > File "/mailman/mailman-${domainslug}/Mailman/htmlformat.py", line > 445, in Format > % csrf_token(self.mlist, self.contexts, self.user) > File "/mailman/mailman-${domainslug}/Mailman/CSRFcheck.py", line 53, > in csrf_token > mac = sha_new(secret + `issued`).hexdigest() > TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' > > Running Python 2.7.5 > . Thanks for the report. I think the issue is caused by the fix for https://bugs.launchpad.net/mailman/+bug/1949403 and can occur when a list admin is trying to handle moderator requests on a list that has no moderator password. I'll investigate and try to put out another fix later today. -- 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: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/16/23 05:34, Jeremy Stanley wrote: > > Clearly a total misreading on my part of the Django documentation to > which you referred earlier. It talks about having to feed Django > multiple settings.py files with different SITE_ID values and running > migrate to configure them, then links to the document on migrations > which starts out explaining how to use makemigrations to create > them. I took that to mean creating and configuring Django sites from > the command line required supplying customized database migrations. > > The particularly misleading bits are where it says: > > "To set the correct name and domain for your project, you can > use a data migration." > > "In order to serve different sites in production, you’d create a > separate settings file with each SITE_ID" > > It doesn't seem to talk about using django_admin at all (or if it > does, it's not mentioned by name, maybe assuming the reader knows to > use it in order to perform the necessary steps). Yes, that doc really isn't appropriate for your purpose, but it's the only one I could find on Django sites. Most of what it talks about is for more complex situations than ours and whatever bits are relevant are already done in Postorius/HyperKitty. Sorry for leading you astray. > Thanks for the clear examples! If these are available somewhere in > Django's documentation, I did a terrible job of searching for them. I don't think Django's docs address the simple task of adding a site. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Mark Sapiro

On 7/28/20 5:40 AM, Brian Carpenter wrote: > Ok, I see the other thread concerning this was deleted, along with my reply. Here it is again. It wasn't deleted. It's on another list - mailman-users(a)python.org. Here's my reply to your post On 7/27/20 7:13 PM, Brian Carpenter wrote: > > This is the client that I asking about in my post. She said what I did, did not work. This is what I did: > > 1. Get into a venv as user mailman > > 2. #mailman shell >>>> from mailman.model.mailinglist import MailingList >>>> mlist = MailingList('listname(a)listdomain.org') >>>> mlist.emergency = False >>>> commit() > ctrl-d (just to be on the safe side) > > Did I not follow your instructions correctly? That should work. I don't know why the result would be any different from what Johanna did. On 7/27/20 8:58 PM, Johanna Amann wrote: > As a small followup for anyone encountering the same problem in the > future - I ended up just changing the value in the database directly. > > So - an “update mailinglist set emergency = FALSE;” (or the equivalent > in the dialect of the database one uses) removes the emergency flag from > all mailing lists. That is another approach which is valid, but why the `mailman shell` method I suggested wouldn't do the same thing, I don't know. Of course, if you're doing multiple lists, this method is easier because just one simple query does them all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: equivalent mailman 3 commands from 2.0

by Mark Sapiro

On 10/25/21 9:16 AM, bob B wrote: > For my 2.0 environment, I have scripts to dump list info, but i can't find the equivalent in mailman 3, for some commands, for example I use: > > /usr/lib/mailman/bin/list_lists which equates in mailman3 to "mailman lists" > /usr/lib/mailman/bin/list_members which equates in mailman3 to "mailman members [listname]" > > But I also use > /usr/lib/mailman/bin/list_admins [listname] > /usr/lib/mailman/bin/config_list [listname] > > Are there equivalent command line commands to get this info in mailman3? for list_admins you can use `mailman members --role administrator [listspec]`. See `mailman members --help`. There is no mailman command equivalent to config_list at this time > The mailman3 "mailman withlist [listname]" takes me into an interactive prompt not sure where to go from there. From there you enter Python statements to do what you want. e.g. ``` $ /opt/mailman/mm/bin/mailman withlist -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 >>>for property in dir(m): ... if not property.startswith('_'): ... print(f'{property}: {m.__getattribute__(property)}') ... ``` You can also create scripts to run with the --run option, See `mailman withlist --details`. > I can use the API > > curl --user [ADMIN]:[password] http://[IP]]/3.1/lists/[listname]/config | python3 -m json.tool > > > But just curious if there is a command line equivalent like in mailman2? Not at this time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Search results for query "sapiro"