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

[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

2 years, 10 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

4 years, 3 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

4 years, 11 months

[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

1 year, 1 month

[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"

7 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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 I installed uwsgi, should I put the config inside mailman.cfg?? El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 01:36 PM, Rafael Mora wrote: > > > > I visited http://192.168.1.42:8000 in my browser and I could not see the > > web UI. > > > What did you see? > > Did you run the Django web server? In your Python 2 virtualenv? > > python manage.py runserver > > -- > 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

7 years, 10 months

[MM3-users] Re: max_delivery_threads

by Sven Buesing

Hi, thank you for the clarification. Are there other ways to speed up the sending of personalized emails? Regards, Sven -----Ursprüngliche Nachricht----- Von: Mark Sapiro [mailto:mark@msapiro.net] Gesendet: Dienstag, 15. Oktober 2019 17:47 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: max_delivery_threads On 10/15/19 12:29 AM, Sven Buesing wrote: > Hi, > > we are currently running mailman version 3.3.0. > We want to enable max_delivery_threads - we want to send personalized mails > (To: ), and we hope that threading would speed things up - but it seems this > option has no functionality despite being documented in the schema.cfg. It is documented in schema.cfg, but it has never been implemented. -- 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/

5 years, 8 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Fri, Dec 30, 2022 at 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/30/22 03:12, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Try adding lists.kictanet.or.ke to Chosen sites along with > >> mm3-lists.kictanet.or.ke > > > > > > Even with that added, still same error. > > > Did you run `django-admin migrate` after uncommenting > 'allauth.socialaccount.providers.twitter', in your settings? > I always do whenever I change anything in settings. (venv) [mailman@gw ~/mm]$ /opt/mailman/mm/bin/django-admin migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. (venv) [mailman@gw ~/mm]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 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

4 years, 11 months

[MM3-users] Re: Two Questions: One General, the Other Specific

by Mark Sapiro

On 2/26/21 9:10 AM, David Wilson wrote: > > *Is there another site that might best communicate the future goals, > plans, objectives, and time frames for mailman3 or is the status of the > project at the state of being primarily reacting to problems, as > evidenced in this problem solving forum, at least as it seems to me, > with no offense meant or intended?* We are a small project with few volunteers and no paid staff. While we would like to be able to devote significant time to future goals, plans and objectives, often we only have time and resources to devote to fixing immediate issues. The way to get issues/objectives/etc. on our radar it to post them to the various sub-project issue trackers at <https://gitlab.com/groups/mailman>. > Something I find surprising is a problem described in an image grab > below relating to an inability to amend a list entry to include a name > to be associated with an email address, as if the data needs to be > immutable. When a workaround was unsuccessfully explored to delete the > entry and then resubmit an amended entry but with the same already > deleted email address, that was still refused, presumably because of > pointers to archived data don't permit, but this seems like a > particularly onerous restriction, or perhaps even a bug, or at least a > severe design constraint. *Is this item on an existing to do list?* There has been much discussion of this on this list. See for example the recent thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> This item is not on a ToDo list because even though <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> asked for an issue to be filed, the most interested person refused to do so because of his assessment of our priorities <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. And if you don't read the whole thread, at least see the response at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- 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

Search results for query "sapiro"