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

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/4/20 12:31 AM, r.woithe(a)callassoftware.com wrote: > Hello, > every night at 00:00 i get an email by mailman3: > > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/django_extensions/management/commands/runjobs.py", line 34, in runjobs > job().execute() > File "/usr/lib/python2.7/dist-packages/hyperkitty/jobs/sync_mailman.py", line 37, in execute > sync_with_mailman() > File "/usr/lib/python2.7/dist-packages/hyperkitty/lib/mailman.py", line 147, in sync_with_mailman > sender.set_mailman_id() > File "/usr/lib/python2.7/dist-packages/hyperkitty/models/sender.py", line 57, in set_mailman_id > mm_user = client.get_user(self.address) > File "/usr/lib/python2.7/dist-packages/mailmanclient/client.py", line 192, in get_user > 'users/{0}'.format(address)) > File "/usr/lib/python2.7/dist-packages/mailmanclient/restbase/connection.py", line 99, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1616, in request > (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1358, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, headers) > File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1314, in _conn_request > response = conn.getresponse() > File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse > raise ResponseNotReady() > ResponseNotReady > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > START TRACEBACK: > END TRACEBACK I'm partly guessing, but this may be a REST timeout. What Mailman core version is this? the version affects what the REST server is. > Therefor i would like to know can i neglect this message ? Or is this message a hint for an Error i should investigate and looking for a solution ? Archived messages have a `mailman_id` which is Mailman core's `user_id` for the user that posted the message. The job itself runs through all the archived messages and finds those which have a null `mailman_id` and attempts to get the `user-id` from core and set the `mailman_id`. Normally, I think messages with null `mailman_id` would only be messages added with hyperkitty_import as opposed to normally archived posts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: How to set up mailman 3

by Mark Sapiro

On 03/25/2017 04:23 PM, David Krantz wrote: > > I did get things working with the bundler at last. Quite tricky and I have > deactivated archival. But I suspect that I should retrace a bit of that > work and upgrade to the latest versions. I miss a few functions from > mailman2, especially setting a limit for message size to discourage sending > larger files to the list. I also notice that there are no modbits per user > that I can reach from the web as admin. See <https://wiki.list.org/x/17891998> for help in upgrading your bundler install. The lack of the ability to set a member's moderation option from the web UI is fixed in versions later than installed by bundler. Also see <https://gitlab.com/mailman/postorius/issues/127> A list's message_size can't currently be set in Postorius. File an issue at <https://gitlab.com/mailman/postorius/issues/new>. >> Where did you find out about the bundler? I'd like to make sure we steer >> people to the current best recommendations: > > The documentation can be found on several places. The one that is best > formatted is this one. I used a worse formatted version of the same text > but right now I cannot find the link. > > https://mailman-bundler.readthedocs.io/en/latest/ > > I notice that you changed the text on the githlab project. Better. > > Now I have no idea of how upgrading the different components. I might start > from scratch although it probably should be possible to upgrade the parts. > The best option is probably to switch to mailman2, but that has > disadvantages when handling lists for multiple domains if I am correctly > informed and I already have a few domains... See <https://wiki.list.org/x/17891998>. > I also found that sending mails manually (telnet to port 25) with no > headers other than "Subject:" causes the "Held messages" tab to crash with > a 500-error. Log below my signature. This is fixed: <https://gitlab.com/mailman/mailmanclient/merge_requests/16>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Problem replying via Hyperkitty

by Mark Sapiro

On 7/26/22 07:39, Jeff wrote: > I am finally getting around to revisiting the problems I have been having with replying or posting through the web of my Mailman 3 installation. Posts or replies simply disappear. Here is the Django log section from when I did a test post today: > > [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b/addresses HTTP/1.1" 200 824 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 1195 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org HTTP/1.1" 200 480 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname(a)lists.domain.org/config HTTP/1.1" 200 3878 "-" "GNU Mailman REST client v3.3.3" > [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org/member/address%40domain.com HTTP/1.1" 200 544 "-" "GNU Mailman REST client v3.3.3" These definitely look like messages from mailman.log, not Django's log. There should be a message like Jul 26 17:53:33 2022 (2868) ACCEPT: <165888320457.2073.7552187924254439941(a)msapiro.net> preceded by a GET for the poster and followed (not necessarily immediatly by a message like Jul 26 17:53:34 2022 (2865) HyperKitty archived message <165888320457.2073.7552187924254439941(a)msapiro.net> to https://msapiro.net/archives/list/list@example.com/message/FF35XYJNXTCDX5FW… The last message above may be the GET for the poster, but if the others are missing, it's not surprising as the message wasn't sent. There may be something useful in Django's log. This is the file defined in the LOGGING dictionary in the settings file as ['handlers']['file']['filename']. Normally, nothing is logged there for a web reply, but some error might be logged there. -- 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: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Tue, 2021-03-02 at 13:54 -0800, Mark Sapiro wrote: > On 3/2/21 1:43 PM, Mark Sapiro wrote: > > Unless you want to remove the Ubuntu package and install everything with > pip, you need to just stick with what you have that at least partly > works and we'll try to determine how to fix the utf8mb4 issue. > > > In that vein, you need to remove any settings_local.pyc files and > restart uWSGI or whatever provides the Django wsgi interface in your > system. and see if that helps. > Hi, I removed /usr/share/mailman3-web/settings_local.pyc quite some time ago, have restarted both mailman3 and mailman3-web numerous times since then, and today I restarted uwsgi this morning. No new settings_local.pyc has yet been created. Ideas..? Cheers, David

5 years, 2 months

[MM3-users] Re: clarifying configuration

by Mark Sapiro

On 6/30/20 11:29 AM, trewtus+200629maitr(a)gmail.com wrote: > Hey Team, > I'm new to Mailman and after some failed attempts to install from git on CentOS8, I have just installed it on Ubuntu 20.04 using mostly aptitude. But it's not quite working and I want to increase the log level to better understand the problem. I did see another post that suggested that I add to /etc/mailman3/mailman.cfg > > [logging.template] > level: debug > > But that doesn't work for me. For example, after using that `mailman conf` doesn't list and debug values and as far as I can tell, the service, even after restarting, is not logging any more than it was. On the other hand, if I add > > [logging.smtp] > level: debug > > Invoking `mailman conf` will reflect that new loglevel. The settings in the logging.template section set defaults for the other logging.* sections. In particular, the logging.debug section sets `level: info` so setting [logging.template] level: debug will not affect the setting for logging.debug. See mailman/config/schema.cfg which is augmented by mailman/config/mailman.cfg and by your own mailman.cfg. > This started me down the path of trying to figure out the configuration system of mailman in hope that that will save me time down the road. I have read > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html but that doesn't seem to agree with what I'm seeing. > > For an additional example, my mailman.cfg file has a "logging.debian" section, but I don't see that section listed in the `mailman conf` output. Why would that be? Because you have installed the Debian/Ubuntu package and that setting is specific to that package and probably only defined in their local mailman.cfg. The reason you don't see it in `mailman conf`, is it's broken. Without a `-s/--section` argument, it only lists sections defined in schema.cfg. See <https://gitlab.com/mailman/mailman/-/issues/736>, <https://gitlab.com/mailman/mailman/-/merge_requests/666> and <https://pythonhosted.org/lazr.config/lazr/config/docs/usage.html>. If you do `mailman conf -s logging.debian` you'll see it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/2/25 17:21, Steve Brown via Mailman-users wrote: > In a list I administer, the From line in an incoming email shows [Poster's Name] via [List Name] <address for posting a reply> . I use Outlook as my client, but at least some other clients behave similarly. However, I have at least one subscriber who uses Mozilla's Thunderbird as his client, and periodically the format changes to something else, most recently to just [List Name <address for posting a reply> . I suspect this occurs from some combination of the way Thunderbird parses the header and the way it populates some kind of address book that makes autofill work, but I'm not sure. Is this a known problem? Is there an easy fix that will be stable? In the past, putting an association in his address book and removing others worked, but it didn't hold and he is frustrated. This From: is the result of DMARC mitigations. The actual From: header in the email is From: [Poster's Name] via [List Name] <address for posting a reply> where [Poster's Name] is the first non-empty value from - the display name in the original From: - tne display name in the posters member record - the poster's email address with the domain replaced with `---` How this header is rendered by any particular mail client (MUA) is up to that MUA and not something you can control. Note however that I use T-bird as my MUA and T-bird displays the From: in your mail from the list as From Steve Brown via Mailman-users <mailman-users(a)mailman3.org> Also, Mailman puts your original From: in a Reply-To: which T-bird displays as Reply-To Steve Brown <drstephenlbrown(a)gmail.com> Depending on your list's settings, the original From: might be in Cc: rather than Reply-To: And, if the T-bird user really needs to see the poster's name and it's not in any displayed headers, they can always view the source of the message and see the From: there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: mailman3-web and the django middleware problem

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 4/25/24 14:01, Thomas Stein wrote: >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >>> >>> I don't know how things are arranged in the Debian/Ubuntu package, >>> but you may have a settings.py which at the end does something >>> like ``` try: from settings_local import * except ImportError: >>> pass ``` If that is the case, adding the above snippet to the end >>> of settings_local.py should work. This has been reported to Debian and is fixed upstream in the Debian repositories -- see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062707 It should hit a sefver soon, as it was uploaded yesterday. I don't know how soon after that it'll hit the Ubuntu repos. Peter C

2 years

[MM3-users] Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 18:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > > > What I called "local admin" should have > > rights to add and remove members of, say, the poodle-regionA mailing > list. > > > By "local admin", do you mean "list owner", i.e., a list owner should be > able to see her own "hidden" lists. > > Is that what you mean, or to you envision some new category of user that > has more access than a list owner? > > -- > 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/ > I mean "list owner"

8 years, 3 months

[MM3-users] Re: Crash while importing archives

by Mark Sapiro

On 7/7/20 7:42 PM, Mark Dadgar wrote: > This is actually an mbox file generated by mailman3. > > (venv) mailman@mail:/opt/mailman/mm$ /opt/mailman/mm/bin/django-admin hyperkitty_import --since 2020-02-19 -l trackjunkies(a)pdc-racing.net /temp/archive/trackjunkies-new-1.mbox > Importing from mbox file /temp/archive/trackjunkies-new-1.mbox to trackjunkies(a)pdc-racing.net > \Traceback (most recent call last): > File "/opt/mailman/mm/venv/bin/django-admin", line 8, in <module> > sys.exit(execute_from_command_line()) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line > utility.execute() > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 375, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 323, in run_from_argv > self.execute(*args, **cmd_options) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/management/base.py", line 364, in execute > output = self.handle(*args, **options) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 327, in handle > importer.from_mbox(mbfile) > File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 152, in from_mbox > for msg in mbox: > File "/usr/lib/python3.8/mailbox.py", line 109, in itervalues > value = self[key] > File "/usr/lib/python3.8/mailbox.py", line 73, in __getitem__ > return self.get_message(key) > File "/usr/lib/python3.8/mailbox.py", line 781, in get_message > msg.set_from(from_line[5:].decode('ascii')) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 27: ordinal not in range(128) > > mailman 3.3.1 / core 3.1 > > Easy fix? I’m missing about 10 days' worth of archives as a result of this. There is a message in your mbox file with a '^From ' separator with non-ascii in the remainder of the line. This may be an unescaped '^From ' in a message body or an actual '^From ' separator. First get your mbox and find the last message successfully imported in the archive before this one. You can delete everything up to through that one. Then you can fix the bad message or just delete it from the remaining mbox and run hyperkitty_import start=... with this mbox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Expire non-members

by Mark Sapiro

On 2/7/26 12:33, John Price via Mailman-users wrote: > Is there a way to expire and delete (in mailman3 or via cron) > non-members? > > I've been running mailman3 for a couple of weeks now on a few mailing > lists, and on my big list specifically I'm seeing lots of spam to the > gcfl-join(a)gcfl.net email alias, which creates these non-members, but they > never confirm their subscription, so they remain in non-member limbo. They don't confirm their subscription because the don't have a subscription request. They have been added to the list as nonmembers because Mailman ensures there is an address record for all the sender addresses in a post regardless of the disposition of the post. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/incomi… Mailman 3 has a different model for dealing with nonmembers than does Mailman 2.1. There are still *_these_nonmembers list attributes, but these are intended to only be used for regexps. For individual addresses, it is intended that the address be a nonmember and the disposition of posts for that nonmember be handled by setting its moderation_action. Of course, this results in spam sender addresses becoming nonmembers which may not be desired, but can be useful. For example, on some lists I manage, nonmember posts are held for moderation. In moderating the post, if I determine it's spam, I discard it and in the same operation set the senders moderation action to discard so subsequent posts from that address are automatically discarded. However, if you want to remove nonmembers from a list, there is currently no mailman subcommand to do that. The `mailman delmembers` command only does members, not nonmembers. You can do it with `mailman shell` (withlist) something like ``` $ mailman shell -l list(a)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(a)example.com mailing list >>> for nonmember in m.nonmembers.members: ... nonmember.unsubscribe() ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

Search results for query "sapiro"