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

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Odhiambo Washington

On Sat, Oct 28, 2023 at 7:19 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/23 01:59, Odhiambo Washington wrote: > > Running an install on Debian12 VM. Getting a new error message that I > > haven't seen previously: > > > > (venv) mailman@debian12:~$ mailman-web compress > > Compressing... Invalid template socialaccount/login_cancelled.html: > Invalid > > block tag on line 7: 'element', expected 'endblock'. Did you forget to > > register or load this tag? > > Invalid template account/verified_email_required.html: Invalid block tag > on > > line 7: 'element', expected 'endblock'. Did you forget to register or > load > > this tag? > > > These templates are part of django_allauth. What is your version of > that? There are backwards incompatible changes in version 0.58. See > > https://github.com/pennersr/django-allauth/blob/main/ChangeLog.rst#backward… (venv) mailman@debian12:~$ pip freeze | grep django-all django-allauth==0.58.0 If you have 0.58 try > ``` > pip install django_allauth\<0.58 ``` > After that, I end up with: (venv) mailman@debian12:~$ pip freeze | grep django-all django-allauth==0.57.0 And then `mailman-web compress` is happy. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 9 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Thanks Mark! I changed the outgoing.py per cut&paste because I didnt know, whow th patch a python file ... But succeeded: /var/log/mailman3/mailman.log Apr 08 19:08:10 2020 (9234) Master started Apr 08 19:08:12 2020 (9241) bounces runner started. Apr 08 19:08:12 2020 (9263) virgin runner started. Apr 08 19:08:12 2020 (9259) out runner started. Apr 08 19:08:12 2020 (9255) lmtp runner started. Apr 08 19:08:12 2020 (9259) Cannot connect to SMTP server localhost on port 25 [Errno 13] Permission denied: '/var/lib/mailman3/cache/7d/c6/7dc6d1a99a5ecf2b2241d6d0958a2bc704e32238150e5cc273f6779b124bd04f' Apr 08 19:08:12 2020 (9237) archive runner started. .... Checked the ownership .... ls -la: /var/lib/mailman3/cache drwxrwx--- 3 root root 4096 Nov 9 22:27 61 drwxrwx--- 3 root root 4096 Feb 3 17:37 6c drwxrwx--- 3 root root 4096 Nov 12 11:59 71 drwxrwx--- 3 root root 4096 Nov 6 12:01 72 drwxrwx--- 3 root root 4096 Feb 5 21:52 7d drwxrwx--- 3 root root 4096 Feb 5 23:05 8b drwxrwx--- 3 root root 4096 Nov 12 23:41 94 drwxrwx--- 3 root root 4096 Nov 7 08:31 ae drwxrwx--- 3 root root 4096 Nov 12 23:40 fa /var/log/mailman3/mailman.log .... Apr 08 19:08:19 2020 (9259) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 100, in deliver self.decorate(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate decorator.process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 264, in process process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 73, in process for archiver in IListArchiverSet(mlist).archivers: 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 600, in __init__ for archiver in config.archivers: File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 260, in archivers archiver = call_name(class_path) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 70, in call_name return named_callable(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/archiving/mhonarc.py", line 46, in __init__ config.archiver.mhonarc.configuration) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 335, in external_configuration cfg_path = str(expand_path(resources, path)) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 80, in expand_path cfg_path = resources.enter_context(path(package, resource + '.cfg')) File "/usr/lib/python3.7/contextlib.py", line 426, in enter_context result = _cm_type.__enter__(cm) File "/usr/lib/python3.7/contextlib.py", line 112, in __enter__ return next(self.gen) File "/usr/lib/python3.7/importlib/resources.py", line 188, in path yield Path(reader.resource_path(resource)) File "<frozen importlib._bootstrap_external>", line 932, in resource_path File "<frozen importlib._bootstrap_external>", line 941, in is_resource File "<frozen importlib._bootstrap_external>", line 95, in _path_isfile File "<frozen importlib._bootstrap_external>", line 87, in _path_is_mode_type File "<frozen importlib._bootstrap_external>", line 81, in _path_stat File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 114, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Apr 08 19:08:19 2020 (9259) SHUNTING: 1586365699.6492867+798bd45a31fb2b8d5fd24a481a3cf95710994bf7 Apr 08 19:08:19 2020 (9259) out runner exiting. Apr 08 19:08:19 2020 (9234) Master watcher caught SIGTERM. Exiting. Apr 08 19:08:19 2020 (9234) Master stopped Changed the ownership for /var/lib/mailman3/cache to list:list and from that point my lists are responding. Same problem occurs before fort he list-directory, which I corrected some days ago. Is the ownship misconfiguration a coincidence or did I made a mistake somewhere?? Thanks for your assistance! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Mittwoch, 8. April 2020 00:23 An: MM3 Users <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 2:40 PM, Wolfgang Bock via Mailman-users wrote: > Yes, I assume that means telnet localhost 25 succeeds. Try the attached patch to mailman/runners/outgoing.py. It should log more about the actual exception. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 20:25:44 CEST schrieb Mark Sapiro: > On 10/13/22 10:55, Eggert Ehmke wrote: > >> It shouldn't have been necessary to apply any patch. The head of the > >> GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > > > > strange, I still had the line with the (not working) > > from mistune.scanner import escape_html, escape_url > > > > maybe because the migration step was not working at that time? > > It should have nothing to do with migrations. The command > ``` > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > ``` > run as the mailman user with your venv active should have set the > content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > to be the same as > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer. > py, but it didn't. I wonder what else didn't get upgraded? Clearly it did do > something because mistune was upgraded. In the meantime I run pip install --upgrade --force-reinstall git+https://gitlab.com/mailman/hyperkitty@master and that installed the correct renderer.py. Should I do this with all packages? > If you run `pip freeze` in your active venv,, what versions do you see > for the things you upgraded? Do they look for example like > ``` > HyperKitty @ > git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a28 > fd7803 ``` Yes that version is installed.

3 years, 10 months

[MM3-users] Re: Mailman3-Web lots of database queries

by Abhilash Raj

On Thu, Nov 22, 2018, at 2:14 AM, Stefan Tatschner wrote: > On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > > No. This is not normal. This is apparently coming from Django qcluster. > > At least it is qcluster that uses the django_q_ormq table, but these > > repeated queries are not normal, at least I don't see them in the sites > > I administer. > > These calls are normal, since qcluster polls the database at a high > rate: > > https://django-q.readthedocs.io/en/latest/configure.html#poll > > Fortunately this setting can be reduced, but yeah, polling happens > though. So, if you are using Django's ORM to keep the task states in Django Q, this is bound to happen depending on how frequently do you run tasks. In Hyperkitty, we have some minutely tasks, which means the polling is going to be high. You can however, configure Django Q to store the tasks outside of database in a better high-speed in-memory database like Redis for example[1] for queuing the tasks. Other options like MongoDB, Amazon SQS is also available. [1]: https://django-q.readthedocs.io/en/latest/configure.html#redis > > Stefan > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

7 years, 8 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 11. Dezember 2019 um 09:55 Uhr -0800 schrieb Mark Sapiro: >Here's a revised script: [...] >Now we expect to see the hash of each message-id followed by the >message-id followed by the exception for the offending message. Success! This time it crashes with the expected exception. I've attached the shell transcript. As expected, it's a spam message. I've uploaded the offending file here for you to look at: <https://ftp.secretchronicles.org/misc/Q5PQZI4QEE4C42XNZMXESSKDCSZBUT4T> This way I don't risk getting caught by spam filters. I'm going to put that down quickly again, though, I don't want to distribute spam messages. Now that the problem is identified, I'm going to purge it from both database and file system. Thank you for your help. If you need any further information for debugging the problem, please tell me. >As to why you didn't receive owner notices about the held spam, perhaps >they were spam filtered or somehow otherwise lost. Maybe. I'll ensure I update quickly when the new Ubuntu LTS comes out to get that functionality. Installing Mailman not via the repos is not really an option for me; this list is for a hobby project and should run with as low maintenance effort as possible (i.e. automatic updates). Thanks a lot. Marvin -- Blog: https://mg.guelker.eu

6 years, 8 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Dadgar

On Feb 15, 2021, at 10:14 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. >> >> The resulted in a broken web interface. >> >> Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. >> >> Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. >> >> Anyone got a solution to this? > > > From the tracebacks it looks like Django is broken. I would suggest > starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ > aside and create a new venv > > virtualenv /opt/mailman/mm/venv/ > > and then activate it and pip install everything. Ok, that worked. THANK YOU. My lists are back up. The CPUs getting pounded by some failing process is back, though. I’ll post about that separately. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Wed, Jan 31 2018, Mark Sapiro wrote: >> I have verp_delivery_interval = 10 ... > > Which says only every 10th message will be VERPed. You want > verp_delivery_interval = 1 to VERP every message. Hi, Why? The smtp relay host would get much more outgoing messages. With verp_delivery_interval = 10, only 10% of the messages would be personalized. Shouldn't this be enough to detect sooner or later, that a recipient address is no more valid? Or is it important, to detect such failure immediately? > The message does appear in the mail log, but until the issues below are > fixed, even if Mailman receives it, you won't see it. Ok. For now, I could do a grep of the syslog messages of Postfix, for example once per month, to check for DSNs. > They should be processed by Mailman and scored as bounces for the > recipient if recognized and forwarded if not (depending on settings), > but they currently are only stored. Ok. >> The question for me is: does the remote MTA needs a fix (i.e. the >> Message-ID is required by some RFC), or mailman (i.e. a DSN without >> Message-ID should be acceptable)? > > I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. Thanks! That means, that I won't need to teach Postfix to add a Message-ID to the DSNs. :) Kind regards, -- Peter

8 years, 6 months

[MM3-users] Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210530 09:19]: > Mark Sapiro writes: > > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > > > Membership adapter is a Mailman 2 feature that allowed use of an > > > external membership database (such as a corporate LDAP system). I > > > thought it was ported to Mailman 3 but maybe not. > > > Actually, it's not quite that simple. Mailman 2.1 defines a > > MemberAdaptor class, [...]. > > The Mailman 3 analog of this is the IMember interface defined in > > mailman/interfaces/member.py and implemented in mailman/model/member.py > > OK, but for Andi it is "simple" in the sense that he doesn't have an > existing MemberAdapter, so the plan is "Implement the IMember interface". Not sure if this is the right approach, or if it wouldn't be more appropriate to "just" replace the dependency on allauth in postorius, and do all the magic in the frontend only (because that's where people actually subscribe). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands. That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not? Andi

5 years, 2 months

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

On 12/28/21 6:15 PM, William Oliver wrote: > So, I have successfully installed mailman3 and it's working great. > However, the way it works now, if someone goes to the domain website, > he or she will get the mailman page. I'd prefer that it work something > like: > My > www.example.com goes to a home page > lists.example.com goes to the mailman3 page > mail.example.com goes to a roundcube page > > > I'm using nginx I'd asked about this a few weeks ago for a MM3 host running Ngnix with a few virtual domains, one of which runs Roundcubemail as its default. Mark Sapiro suggested the following, and it seems to be working OK. You'll need these lines in the Nginx config file for each virtual host you define. # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff dn

4 years, 7 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marcus Bautze

Hi, Am 07.06.2024 um 06:22 schrieb Mark Sapiro: > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "Thank you, archiver is now starting. Now there's another > problem:". Does this mean messages are being archived in HyperKitty or > are they accumulating in (I think the Debian path is) > /var/lib/mailman/archives/hyperkitty/spool/? They are in /var/lib/mailman3/archives/hyperkitty/spool/, i doesn't find them in the HyperKitty-archives. > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py > and this are the same Keys." To be clear, in mailman-web.py the key is > quoted and in mailman-hyperkitty.cfg it is not. E.g., in > mailman-hyperkitty.cfg > > api_key: Some_key here is the key unquoted: api_key: *** > > and in mailman-web.py > > MAILMAN_ARCHIVER_KEY = 'Some_key' here's the Key quoted: MAILMAN_ARCHIVER_KEY = '***' > > What are your versions for mailman-hyperkitty and HyperKitty? > HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 > and if I recall corectly, at least one Debian package was shipped with > this incompatibility > i found: python3-django-hyperkitty 1.3.7-1 python3-mailman-hyperkitty 1.2.1-1 mailman3-full 3.3.8-2~deb12u1 (no other hyperkitty-related packages) -- Marcus Bautze marcus(a)mbautze.de

2 years, 2 months

Search results for query "sapiro"