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

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Sat, 25 Jul 2020 at 22:11, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/25/20 11:37 AM, Odhiambo Washington wrote: > > On Sat, 25 Jul 2020 at 19:58, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> This is a packaging glitch with the flufl modules. Remove and reinstall > >> them. > >> > >> pip uninstall flufl.bounce flufl.i18n flufl.lock > >> pip install flufl.bounce flufl.i18n flufl.lock > >> > >> > > It would appear that luck isn't just on my side: > > > > root@gw:/opt/mailman/mm # pip uninstall flufl.bounce flufl.i18n > flufl.lock > ... > > > You need to run these pip commands in your venv. I.e. do this > > > [root@gw /opt/mailman/mm]# source /opt/mailman/mm/venv/bin/activate > > before the pip uninstall and pip install. > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> That has solved the problem. Thank you very much. I have taken note of that. for my NOTES. Finally, I have adapted your init script to get some rudimentary one that I could use on FreeBSD. I have to change /opt/mailman to be owned by mailman3:mailman3 (because I have "live" MLs on this server, using mailman-2.1.34. I am not sure if they can co-exist. I suppose they could, but what might be the security implication, if any?? This is what the init script looks like (rudimentary!!): (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 ### BEGIN INIT INFO # Provides: GNU Mailman # Short-Description: Mailman3 Service # Description: service control for Mailman3 ### END INIT INFO PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: DESC="GNU Mailman service" DAEMON=/opt/mailman/mm/bin/mailman NAME=mailman USER=mailman3 GROUP=mailman3 # Needed by click export LANG=en_US.UTF-8 # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 # Load the VERBOSE setting and other rcS variables #. /lib/init/vars.sh # Define LSB log_* functions. # Depend on lsb-base (>= 3.2-14) to ensure that this file is present # and status_of_proc is working. #. /lib/lsb/init-functions case "$1" in start) [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" # use --force to remove a stale lock. /usr/local/bin/sudo -u $USER $DAEMON start --force ;; stop) [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" /usr/local/bin/sudo -u $USER $DAEMON stop ;; status) /usr/local/bin/sudo -u $USER $DAEMON status ;; reopen) /usr/local/bin/sudo -u $USER $DAEMON reopen ;; restart) log_daemon_msg "Restarting $DESC" "$NAME" /usr/local/bin/sudo -u $USER $DAEMON restart ;; *) echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 exit 3 ;; esac It does start mailman3 for sure, but also complains after a few seconds with the message: (venv) [root@gw /usr/local/etc/rc.d]# */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: DeprecatedWarning: Call to deprecated function __init__(...). API class may be removed in a future release, use falcon.App instead.* * **kws)* But: (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman 11677 - Is 0:00.01 /usr/local/bin/python /usr/local/mailman/bin/mailmanctl -s -q start (python2.7) 15860 - S 0:07.86 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s (python2.7) 16310 - S 0:07.43 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s (python2.7) 16928 - S 0:07.07 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s (python2.7) 17335 - S 0:07.47 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s (python2.7) 17975 - S 0:07.02 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s (python2.7) 18419 - S 0:20.06 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s (python2.7) 19015 - S 0:07.13 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s (python2.7) 19131 - I 0:00.15 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s (python2.7) 27273 - Is 0:01.64 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/master --force -C /opt/mailman/mm/mailman.cfg (python3.7) 28526 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=archive:0:1 (python3.7) 28627 - I 0:01.77 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=bounces:0:1 (python3.7) 28988 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=command:0:1 (python3.7) 29341 - S 0:01.69 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=in:0:1 (python3.7) 29978 - S 0:01.68 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=lmtp:0:1 (python3.7) 30843 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=nntp:0:1 (python3.7) 31541 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=out:0:1 (python3.7) 31675 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=pipeline:0:1 (python3.7) 32181 - S 0:01.77 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 (python3.7) 33166 - I 0:01.65 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=retry:0:1 (python3.7) 33694 - S 0:01.70 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=virgin:0:1 (python3.7) 34600 - S 0:01.69 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=digest:0:1 (python3.7) 41250 - S 0:00.01 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 (python3.7) 41533 - S 0:00.01 /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/runner -C /opt/mailman/mm/mailman.cfg --runner=rest:0:1 (python3.7) 98450 - I 0:00.45 httpd: mailman-web (httpd) 59886 0 S+ 0:00.00 grep mailm Assuming that I am using mod_wsgi with Apache, and that I have configured apache right using https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… .. should I be able to access the MM3 web UI?? At that point, I am feeling somewhat confused as to what to try next. (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log Jul 25 22:53:16 2020 (40670) Master started Jul 25 22:53:18 2020 (42036) bounces runner started. Jul 25 22:53:18 2020 (45205) out runner started. Jul 25 22:53:19 2020 (41191) archive runner started. Jul 25 22:53:19 2020 (46670) retry runner started. Jul 25 22:53:19 2020 (44567) nntp runner started. Jul 25 22:53:19 2020 (43069) in runner started. Jul 25 22:53:19 2020 (46960) virgin runner started. Jul 25 22:53:20 2020 (45720) pipeline runner started. Jul 25 22:53:20 2020 (47326) digest runner started. Jul 25 22:53:20 2020 (43755) lmtp runner started. Jul 25 22:53:20 2020 (45922) rest runner started. [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: http://127.0.0.1:8001 (45922) [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 Jul 25 22:53:21 2020 (42743) command runner started. How do I access the web UI for MM3 now? Thanks in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

[MM3-users] Re: postfix malformed address with confirm replies

by Stephen Mats Mats

> On Feb 28, 2021, at 01:32, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Mark Sapiro writes: >> On 2/27/21 4:36 AM, Stephen J. Turnbull wrote: > >>> is legal, and I think that most servers will accept it, but RFC >>> 5321 sets a limit of 64 octets on mailboxes[1], and your >>> confirmation mailbox is 67 octets. >> >> Since the -confirm+<token> part is fixed at 49 octets, this would imply >> a limit in list names of 15 octets. Ouch! > > I'm pretty sure we would have run into this before, if there were a > lot of servers out there imposing this limit. 15 octets is pretty > darn short, there are probably quite a few list names out there longer > than that. Not to mention that the RFC itself says "you SHOULD NOT be > a jerk about this". :-) So I don't think this is a big problem in > practice, and I hope Steve can reconfigure the obstructive server to > not be so picky. > To be clear the 'obstructive server’ is mailman-core. :) [ec2-user@ip-172-31-18-xxx ~]$ telnet 172.19.199.2 8024 Trying 172.19.199.2... Connected to 172.19.199.2. Escape character is '^]'. 220 mailman-core GNU Mailman LMTP runner 2.0 LHLO ip-172-31-18-xxx.us-west-2.compute.internal 250-mailman-core 250-SIZE 33554432 250-8BITMIME 250 HELP MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> 250 OK RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu> 553 5.1.3 Error: malformed address RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55(a)mm3.aca-aws.s.uw.edu> 250 OK quit 221 Bye Didn’t really dig but my guess would be the LMTP from aiosmtpd.lmtp is actually throwing the 553. For a bit of context, of the 25,801 mailman2 lists we have here at University of Washington 5,211 have names longer than 15 characters (we don’t have any lists with multibyte characters in their names). Our longest list name is 33 characters. I didn’t dump every config to see the number of lists that subscribe_policy set to confirm or confirm and approve. But I expect it’s a small minority. steve > For Mailman, I doubt we need a full SHA1 (?) for the purpose. We can > truncate the thing, probably opportunistically (ie, so the whole > confirmation mailbox fits in 64 octets, or we could even parse the > bounce message and resend only if we run into a problem). > > Steve > _______________________________________________ > 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/

4 years, 6 months

[MM3-users] Non-ascii characters missing from Pipermail archive txt and gz downloads

by Mark Dale

Mailman 2.1.34 Debian 10 Postfix Hi I'm hoping someone can shine a light on character encoding issue I've encountered. A plain-text email with non-ascii characters in the body gets posted to the list. As per Mark Sapiro's guide I've captured the incoming message to file. - https://www.mail-archive.com/mailman-users@python.org/msg73469.html The message is received by Mailman with the non-ascii characters displaying correctly. The header of that message has: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 8bit In the list's mbox file and archive webpage, the message displays the non-ascii characters correctly. In the archive's downloaded .txt (and also .gz) file, the non-ascii characters are missing and displayed as "?". I've copied the message text in below, from both the correct one from the email and the erroneous .txt file. Hopefully they won't get scrambled up when I send this. Any advice on getting the non-ascii characters written into the archive .txt file would be gratefully received. Thanks, Mark === Message text as okay in mbox and as shown on the archive webpage === If one goes by the definition of veḷippaṭai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi āmpal does not conform to that definition since in the case of aruvi āmpal in Patiṟṟuppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression aṭai aṭuppu aṟiyā is already there to clarify that āmpal is a number and not a flower. Thus, aruvi simply provides information in addition to aṭai aṭuppu aṟiyā that āmpal is not a flower. The modern commentator Aruḷampalavaṉār also does not call it veḷippaṭai. === === Message text with missing characters in te archive's txt and gz downloads == If one goes by the definition of ve?ippa?ai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi ?mpal does not conform to that definition since in the case of aruvi ?mpal in Pati??uppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression a?ai a?uppu a?iy? is already there to clarify that ?mpal is a number and not a flower. Thus, aruvi simply provides information in addition to a?ai a?uppu a?iy? that ?mpal is not a flower. The modern commentator Aru?ampalava??r also does not call it ve?ippa?ai. ===

4 years, 5 months

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Abhilash Raj

> On Jul 9, 2021, at 9:15 AM, christopher.claus(a)tgcamberg1848.de wrote: > > Mark Sapiro wrote: >>> ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. >>> WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer >>> It appears you created the new template with Postorius, but there is an >> issue for Postorius templates. Possibly your Django setting for >> POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. >>> Obviously I have a problem with the hostname. I set >>> [code] >>> POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 >>> [/code] >>> where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost >>> [code] >>> wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamberg... >>> [/code] >>> will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? >>> If that works, yes. > > Hi Mark, > > thanks for your reply and excuse my delay. I was very busy in the last weeks but made some tests. Newly created templates with POSTORIUS_TEMPLATE_BASE_URL=http://localhost:8000 did not work. I changed it to my fqdn - at the moment I am able to access the template via this URl (e.G. http://lists.example.de:8000/postorius/api/templates/list/homepage.lists.ex…) > But if I try to send an email I got the following error: You want the URL at which Postorius (postorius) is available from Core (mailman-core container). The default for that in the container images is set to http://mailman-web:8000. Does that not work for you? If you want to verify, you want to exec into the Core’s container (`docker exec -it mailman-core bash`) and see if you can curl the URL from inside there. If you are using the default docker-compose-postorius.yaml then there is a /etc/hosts entry created by docker for the mailman-web container, hence `http://mailman-web:8000` works there (but it won’t work on the host, since docker doesn’t modify the host’s /etc/hosts). There might also be a bug in play here which would cause such connection refused errors when subscribing/unsubscribing when there was a template configured for the list. Is that the case for you or are you seeing always when trying to send the email (which would imply that the Web container simply isn’t reachable from Core). -- thanks, Abhilash Raj (maxking)

4 years

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:24 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Fri, May 14, 2021, at 2:16 PM, Odhiambo Washington wrote: > > On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > > > > > /usr/local/include/sass > > > > > > > > That is the only thing found that is in the base system. > > > > > > And that's the one you want. What is it's mode? > > > > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > > total 104 > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > > > I imagined I needed an executable. > > This sounds like a result of you running `pip3 install sass`, probably > with sudo > which failed mid-way due to the exception you posted above. > Closer to the truth! It failed. I was running this from within the virtualenv. > Which OS are you using? FreeBSD. > On debian/ubuntu, you can install: > > sudo apt install sassc > Do I need to install sassc in the base OS or in the virtualenv? > I am not exactly sure how it got removed during your upgrade > to the new version of Mailman since it shouldn't affect your system > packages. > The funny part is my MM3 used to run. Mark took so much hand-holding for me to get it running. Then one day I used the update process and things got hosed. The happy part is that I had not put any production lists on MM3 as I hadn't developed the confidence of managing it. Did you install Mailman initially using system packages or instructions > provided at [1]? > > [1]: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… No. I relied on https://wiki.list.org/DOC/Mailman%203%20installation%20experience. This is way back! Your new link is recent, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 3 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Odhiambo Washington

On Tue, Dec 20, 2022 at 9:50 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Tue, Dec 20, 2022 at 3:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/17/22 23:22, Odhiambo Washington wrote: >> > >> > I have dropped the DB, recreated, ... >> >> When you created the DB did you specify `CHARACTER SET utf8mb4`, e.g. >> >> CREATE DATABASE mailmansuite CHARACTER SET utf8mb4 >> > > Yes. That is what I do at the minimum for my databases unless specific > instructions exist against it. > So it seems like I have done everything that is commonly expected, but the > import still fails on several messages. > It turns out that all this time I was barking up the wrong tree! I was having all my modifications in /etc/mailman3/*. When I did run 'mailman info', the information that came out is that mailman was actually reading /opt/mailman/mm/mailman.cfg I then just moved all the files I had put in /etc/mailman3/ to /opt/mailman/mm/. There is a WARNING on https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install which says one must create the config file as /etc/mailman3/mailman.cfg How to force mailman to read that file is something I haven't understood, but turns out to be what has taken me days trying to get things right. Ultimately, when I did the import, there was only one email from the archives that failed to be imported - which I honestly don't mind, but maybe there is a solution for this "'utf-8' codec can't encode character '\udcae' in position 331: surrogates not allowed" ?? (venv) [mailman@gw ~/mm]$ /opt/mailman/mm/bin/django-admin hyperkitty_import -l kictanet(a)lists.kictanet.or.ke /usr/local/mailman2/archives/private/kictanet.mbox/kictanet.mbox Importing from mbox file /usr/local/mailman2/archives/private/kictanet.mbox/kictanet.mbox to kictanet(a)lists.kictanet.or.ke 21%*Failed adding message <1260802782.6596.1350003565(a)webmail.messagingengine.com <1260802782.6596.1350003565(a)webmail.messagingengine.com>>: 'utf-8' codec can't encode character '\udcae' in position 331: surrogates not allowed* Computing thread structure Synchronizing properties with Mailman 915 emails left to refresh, checked 0 767 emails left to refresh, checked 0 Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list kictanet(a)lists.kictanet.or.ke'. (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, 8 months

[MM3-users] Re: "Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'

by Simon Liebold

Am 28.05.2017 um 21:16 schrieb Mark Sapiro: > > I just tested this on another list on this server. and both 'delete > message' and 'delete thread' worked for me with the latest release > Hyperkitty 1.1.0, django_mailman3 1.1.0 and Django-1.10.7. > > Did you get to the confirmation page and then get the 500 or did the 500 > come before getting the confirmation page? Is there a full traceback in > mailman_web.log? > I didn't find a 'delete message' button. But "Delete this thread" went straight to the 500. Both, Hyperkitty and django-mailman are up-to-date with master. ERROR 2017-05-28 13:04:14,496 29835 django.request Internal Server Error: /hyperkitty/list/simsimmer@lists.simonliebold.de/thread/4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM/delete Traceback (most recent call last): File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/contrib/auth/decorators.py", line 23, in _wrapped_view return view_func(request, *args, **kwargs) File "/opt/mailman/hyperkitty/hyperkitty/lib/view_helpers.py", line 141, in inner return func(request, *args, **kwargs) File "/opt/mailman/hyperkitty/hyperkitty/views/message.py", line 306, in delete form = MessageDeleteForm(initial={"email": initial}) File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/forms/forms.py", line 96, in __init__ self.fields = copy.deepcopy(self.base_fields) File "/usr/lib/python2.7/copy.py", line 190, in deepcopy y = _reconstruct(x, rv, 1, memo) File "/usr/lib/python2.7/copy.py", line 328, in _reconstruct args = deepcopy(args, memo) File "/usr/lib/python2.7/copy.py", line 163, in deepcopy y = copier(x, memo) File "/usr/lib/python2.7/copy.py", line 237, in _deepcopy_tuple y.append(deepcopy(a, memo)) File "/usr/lib/python2.7/copy.py", line 163, in deepcopy y = copier(x, memo) File "/usr/lib/python2.7/copy.py", line 230, in _deepcopy_list y.append(deepcopy(a, memo)) File "/usr/lib/python2.7/copy.py", line 163, in deepcopy y = copier(x, memo) File "/usr/lib/python2.7/copy.py", line 230, in _deepcopy_list y.append(deepcopy(a, memo)) File "/usr/lib/python2.7/copy.py", line 174, in deepcopy y = copier(memo) File "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/forms/models.py", line 1168, in __deepcopy__ result.queryset = self.queryset.all() AttributeError: 'NoneType' object has no attribute 'all' Simon

8 years, 3 months

[MM3-users] Re: Database problem after system upgrade

by Odhiambo Washington

On Wed, Nov 15, 2023 at 11:34 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > Thanks a lot. > > [Odhiambo] > > > From the above output, I'd try two things: > > > > 1. Is the database really running? > > > > ``` > > $ sudo -u postgres psql > > ``` > > > > 2. Can mailman connect to the database: > > > > ``` > > psql -h localhost -U mailman -d mailman -W > > ``` > > > > What does those two commands give you? > > I found that I did need to change the pg_hba.conf to get authentication to > work. > > When I no start Mailman, I get the following: > > Traceback (most recent call last): > File "/opt/mailman3/venv/bin/mailman", line 8, in <module> > sys.exit(main()) > ^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1130, in __call__ > return self.main(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1055, in main > rv = self.invoke(ctx) > ^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/bin/mailman.py", > line 69, in invoke > return super().invoke(ctx) > ^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1657, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 1404, in invoke > return ctx.invoke(self.callback, **ctx.params) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman3/venv/lib64/python3.11/site-packages/click/core.py", > line 760, in invoke > return __callback(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/click/decorators.py", > line 26, in new_func > return f(get_current_context(), *args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/commands/cli_control.py", > line 91, in start > status, lock = master_state() > ^^^^^^^^^^^^^^ > File > "/opt/mailman3/venv/lib64/python3.11/site-packages/mailman/bin/master.py", > line 104, in master_state > os.kill(pid, 0) > PermissionError: [Errno 1] Operation not permitted > > > But which operation are not permitted, how to find the cause? > That message is cryptic to me, but @Mark Sapiro <mark(a)msapiro.net> might know. Could you please see if there are stale lock files in /opt/mailman3/var/locks/ that could be preventing mailman3 from starting? If there are two files there, delete them and try starting mailman3 again. Beyond that possibility, I now remain clueless :) -- 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]

1 year, 9 months

[MM3-users] Re: Installation Wooes

by Samir Faci

I manually patched up the bug since It seems it only occurs once or twice in the code base. Here's my next question. Hopefully this isn't off topic, but trying to get postfix to work with mailman and I keep on getting relay denied issues. /var/log/mailman/smtp.log May 04 02:06:20 2020 (136767) <158855797827.136760.10970401726993928773@lists> smtp to booh(a)lists.domain.org for 1 recips, completed in 0.016954421997070312 seconds May 04 02:06:20 2020 (136767) <158855797827.136760.10970401726993928773@lists> post to booh(a)lists.domain.org from booh-owner(a)lists.domain.org, 5180 bytes May 04 02:06:20 2020 (136765) ('198.199.98.177', 42734) Data: b'QUIT' May 04 02:06:20 2020 (136765) ('198.199.98.177', 42734) connection lost May 04 02:06:20 2020 (136765) Connection lost during _handle_client() May 04 02:06:21 2020 (136767) <158855797827.136760.10970401726993928773@lists> recipients refused: {' csgeek(a)domain.com': (554, b'5.7.1 <csgeek(a)domain.com>: Relay access denied')} May 04 02:06:21 2020 (136767) <158855797827.136760.10970401726993928773@lists> smtp to booh(a)lists.domain.org for 1 recips, completed in 0.022742748260498047 seconds May 04 02:06:21 2020 (136767) <158855797827.136760.10970401726993928773@lists> post to booh(a)lists.domain.org from booh-owner(a)lists.geekbeacon.org, 5496 bytes, 1 failures May 04 02:06:21 2020 (136767) <158855797827.136760.10970401726993928773@lists> delivery to csgeek(a)domain.com failed with code 554, b'5.7.1 <csgeek(a)domain.com>: Relay access denied' These are the changes I have in postfix that seem relevant. /etc/postfix/master.cf mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} /etc/postfix/main.cf compatibility_level = 2 recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = lists.domain.org mydestination = $myhostname, localhost.localdomain, localhost, $mydomain, lists.domain.org Any help is appreciated. -- Samir Faci On Sat, May 2, 2020 at 1:40 PM Andrew Hodgson <andrew(a)hodgson.io> wrote: > Mark Sapiro <mark(a)msapiro.net> wrote: > >On 5/2/20 12:51 AM, Samir Faci wrote: > >> A few questions about an Ubuntu install. > >> > >> i'm getting this behavior: > > >> AttributeError: module 'time' has no attribute 'clock' > > > >> I'm on python 3.8.2 > > > >It time.clock() went away in Python 3.8. Mailman versions older than > >3.3.0 are not compatible with Python 3.8. You need to upgrade Mailman > core. > > I think this is a bug in Ubuntu 20.04. > > Python3 package is: > Python3 3.8.2-0ubuntu2 > https://packages.ubuntu.com/search?suite=focal&keywords=python3 > Mailman3 is: 3.2.2-1 > https://packages.ubuntu.com/search?suite=focal&keywords=mailman3 > > Andrew. > _______________________________________________ > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 4 months

[MM3-users] Re: mailman3 not working for mailman21 lists

by Stephen J. Turnbull

blup(a)fortytwo.ch writes: > First I did create the list with the old name and imported the old > configs with mailman import21. As the list did not work then, I > deleted it and created it again (with the same manual configuration > as for the new list that's working). OK. So as far as you know the configurations of list1 and list2 on Mailman 3 are identical, at least in the case where you have deleted list1 and recreated by hand. > I don't have a qfiles directory. Try queue/, especially look for the out[going], pipeline, and shunt subdirectories. > > Is the 'outgoing' qrunner still running? (ps ax | grep outgoing) > > no Sorry, I got that wrong. Mark recommends this: ps -fwwA|grep runner=|sed s/.*runner=// and gave this as sample output: archive:0:1 bounces:0:1 command:0:1 in:0:1 lmtp:0:1 nntp:0:1 out:0:1 pipeline:0:1 rest:0:1 retry:0:1 task:0:1 virgin:0:1 digest:0:1 rest:0:1 rest:0:1 so it looks like the process name of the runner is "out", not "outgoing". Besides checking for the "out" runner, also check for "pipeline", which has been known to fail in the past. > But once more: list1 was working fine as long as mailman21 was used > and stopped working when switching to mailman3. I don't expect spam > filters that worked with mailman21 to stop working with mailman3. Mailman 3 is a complete rewrite, essentially no Mailman 2 code was left untouched because of the pervasiveness of the change of the fundamental string type str from encoded bytes to abstract characters. I don't expect behavior to change, but I certainly am not going to rule anything out when trying to diagnose problems based on so little information. > I have more or less no Python knowledge (i.e. I can read and > understand Python but can't write it). Could you please give me > detailed command by command instructions. Thanks. I'll take a look at it tomorrow, but I can't promise results until the weekend if I can't write a script in 30 minutes. Normally Mark Sapiro would handle this kind of thing, but he's offline for a couple weeks so you've got me. My knowledge is mostly on the email protocols side of things (Internet message format, authentication protocols), not the internal processing. I'll do what I can, but if I can't do it real quick it's probably going to take me several hours, which I'm not going to have until the weekend. Steve

3 years

Search results for query "sapiro"