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

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Jim Popovitch

On Wed, 2021-03-24 at 14:00 -0400, Jim Popovitch via Mailman-users wrote: > On Wed, 2021-03-24 at 10:57 -0700, Mark Sapiro wrote: > > On 3/24/21 7:58 AM, Brian Carpenter wrote: > > > On 3/24/21 9:54 AM, Ralph Weber wrote: > > > > Comments received directly from one of the people who developed the > > > > AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively > > > > established that AWS Mailman is *not* intended to interact with AWS > > > > SES when receiving email messages > > > > > > I don't think there is a Mailman 4 and the person who is marketing his > > > services under that name is sending a confusing message to the public. > > > > Danil Smirnov owns both the mailman3.com and mailman4.com domains. > > Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". > > In response to our request, the following is included at the bottom of > > <https://mailman3.com/>;;: > > > > Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain > > used to coordinate development of the Mailman 3 free software suite. The > > Mailman 3 core developers are not involved with Mailman3.com, and cannot > > answer any questions or provide any support related to its operations. > > If you are looking for resources for development of the Mailman 3 free > > software suite, please see mailman3.org. > > > > Yes, this is all ripe for confusion ... > > Just to add, Danil also owns mailman2.com, and I own (and parked) > mailman2.org. Apologies to this list and Danil who has informed me that mailman2.com is not theirs. This of course means that there is another stakeholder out there somewhere.... ;) -Jim P.

4 years, 1 month

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

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:12 AM, Odhiambo Washington wrote: > > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: > >> > >>> There is still some confusion on my part about the directives in the > file > >>> so allow me to seek some clarifications. > >>> > >>> The following are the contents of a file I have created and placed in > my > >>> Apache Includes/ directory. > >>> I was hoping that with it, I can now access http://lists.my.server/mm3 > >> and > >>> get the UI. > >>> > >>> <CUT> > >>> > >>> # Global section > >>> WSGIDaemonProcess mailman-web display-name=mailman-web > >>> maximum-requests=1000 umask=0002 user=mailman3 \ > >>> group=mailman3 > >>> > >> > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > >>> \ > >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > >>> WSGIRestrictSignal Off > >>> > >>> <VirtualHost *:80> > >>> ServerName lists.my.server > >>> ServerAdmin odhiambo(a)gmail.com > >>> > >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in > >> the > >>> # provided example so I kept it. I also made changes to > WSGIDaemonProcess > >>> # based on my own mod_wsgi experience elsewhere.) > >>> > >>> ErrorLog /var/log/myserver-error.log > >>> LogLevel debug > >>> > >>> # This goes in the VirtualHost block for the domain. > >>> > >>> # Mailman 3 stuff > >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this > >>> directory supposed to be and what/who creates it and with what > >> permissions?* > >> > >> > >> It is created/updated by the mailman-post-update script based on CONFDIR > >> and STATIC_DIR. > >> > > > > The fact that I have run the mailman-post-update script and these > > directories aren't created means there is a problem in my setup, yes? > > > If your mailman-post-update script is essentially the same as > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > and it ran successfully, it would have created opt/mailman/mm/static and > populated it. What was the output when you ran it? > > > Yes, I have these files: > > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > > /opt/mailman/mm/settings.py > > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > > /opt/mailman/mm/settings_local.py > > > Is there an empty /opt/mailman/mm/__init__.py file? > No. root@gw:/usr/local/mailman # ls -al /opt/mailman/mm/ total 88 drwxr-xr-x 8 mailman3 wheel 512 Jul 26 14:55 . drwxr-xr-x 6 mailman3 wheel 512 Jul 26 18:38 .. drwxr-xr-x 8 root wheel 512 Jul 25 22:16 .sass-cache drwxr-xr-x 2 mailman3 wheel 512 Jul 26 16:35 __pycache__ drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:42 bin -rw-r--r-- 1 mailman3 wheel 248 Jul 25 14:37 gunicorn.conf -rw-r--r-- 1 mailman3 wheel 266 Jul 26 15:34 gunicorn.conf.py lrwxr-xr-x 1 mailman3 wheel 24 Jul 25 14:39 logs -> /opt/mailman/mm/var/logs -rw-r--r-- 1 mailman3 wheel 370 Jul 25 14:32 mailman-hyperkitty.cfg -rw-r--r-- 1 mailman3 wheel 1291 Jul 26 17:12 mailman.cfg -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 settings.py -rw-r--r-- 1 mailman3 wheel 15805 Jul 26 21:22 settings_local.py drwxr-xr-x 9 mailman3 wheel 512 Jul 25 22:16 static -rw-r--r-- 1 mailman3 wheel 1395 Jul 25 14:35 urls.py drwxr-xr-x 12 mailman3 wheel 512 Jul 26 19:30 var drwxr-xr-x 5 mailman3 wheel 512 Jul 26 17:11 venv -rw-r--r-- 1 mailman3 wheel 1170 Jul 26 11:39 wsgi.py > > > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > > confusion with the instructions at some point in the reading > > of some documentation previously (in my previous attempt last year!) and > > had noted that in my NOTES. I'll change this once things get clear for > me. > > Also, the fact that one of the init scripts > > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > > in your "reflection" page was calling sudo :) > > > It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user > as it should. Have you set > > USER=mailman3 > in yours? > Yes. However, that also means the /opt/mailman should be owned by mailman3, right? So I wasn't quite mistaken. PS: There is the issue with qcluster, which doesn't seem to have been documented in details from your "experience". I see the configuration file and the init script, but not how to install it, or whether the procedure already installed it. Kindly clarify. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 years, 9 months

[MM3-users] Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Abhilash Raj

On Sun, Mar 10, 2019, at 9:00 AM, Torge Riedel wrote: > Am 10.03.19 um 16:44 schrieb Mark Sapiro: > > On 3/10/19 8:18 AM, Torge Riedel wrote: > >> I deleted the existing "example.com" and added a new one > >> "lists.mydomain.de". > >> > >> Now the admin (django) interface always gives "An error occurred while > >> processing your request". After one of the first navigation clicks I saw > >> a message that "site with id 1 is missing". > > > > In your Django settings your have > > > > SITE_ID = 1 > > > > which pointed to the example.com domain you deleted. > > > > You need to override this in settings_local.py. Probably > > > > SITE_ID = 2 > > > > but if that doesn't work, try '0' > > > Ah, thank you Mark. That makes a kind of sense. I changed the database > directly to fix it. And renamed example.com to lists.mydomain.de. Now > the error is gone. > > I'm wondering why the initial database set up of postorius (?) adds > "example.com". Is there a way to directly add my domain instead? > Somewhere in settings_local.py? Django does that and there doesn't seem to be a way to override that to something else during initial migration. Or nothing I have found yet. Only way is to edit "example.com" to something you'd like or add another domain entry and change SITE_ID to point o that. > _______________________________________________ > 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)

6 years, 2 months

[MM3-users] Re: Problem updating mailman

by Brian Carpenter

Mark Sapiro wrote: > On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't > > remember consciously > > installing that because it was never in the guide I followed (which is your > > own writeup). > > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > > > > '[' False == False ']' > > mkdir -p /opt/mailman/mm/static > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > /opt/mailman/mm/bin/django-admin compress > > CommandError: An error occurred during rendering > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > > /bin/sh: sass: not found > > > > You can't just uninstall rubygem-sass. You have to replace it. Here's > one recipe for Ubuntu > cd /usr/local/lib > # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the > # appropriate version. > wget > https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5-... > sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz > sudo chmod -R o-w dart-sass > sudo ln -s dart-sass/sass /usr/local/bin/sass > rm dart-sass-1.32.5-linux-x64.tar.gz > Then you should see the command > sass --version > prints > 1.32.5 > Then, because dart-sass doesn't recognize the short form -t option for > --style, you have to edit your settings(_local).py and change > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > to > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass --style compressed {infile} {outfile}'), > ('text/x-sass', 'sass --style compressed {infile} {outfile}'), > ) I had to do a new installation of Mailman 3 with Postorius/Hyperkitty today and these directions were very helpful. Thank you, Mark.

4 years, 3 months

[MM3-users] Re: Template for Password Reset Email

by Mark

On 2024-11-18 01:38, Mark Sapiro wrote: > On 11/17/24 16:57, Mark wrote: >> >> I can see the French text for the "Password Reset Email" in the >> django.po file. And running the compilemessages command reports the >> "django.po" for French is okay and up to date. Should I be recompiling >> the ".mo" file? > > No, It's fine. The issue is the language context for this message has > nothing to do with any Mailman list's preferred language. > > Again, see > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > > If all the lists on your server are French, you could set > > LANGUAGE_CODE = 'fr' > > in your Django settings. Otherwise, the user's browser has to include > an Accept-Language: header specifying French as the most preferred > language in it's request. > > Also note the ordering of SessionMiddleware, LocaleMiddleware and > CommonMiddleware in the above doc. I have recently updated the various > places where we suggest or supply MIDDLEWARE settings, but you may > find that your settings have LocaleMiddleware after CommonMiddleware > and you should fix that. It's just the one list that is using French. Others are in English I've edited the order of the middleware settings in this file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/settings/base.py I reordered as below, restarted everything but no joy :-( ... at Line 76 ... MIDDLEWARE = ( 'allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ... I'm thinking this is not the file I'm looking for. Apologies for my cluelessness here.

6 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

Hello! Just to let you know, the problem with the email reception was that I was thinking that the email was coming from my hostgator panel, but I was wrong, it's coming from Google (as I use gmail) so that was the problem, I have to open the port 25 to any computer not just my hostgator server.. Have a great day. Bye. On Thu, Aug 3, 2017, 16:25 tlhackque via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 03-Aug-17 17:14, Rafael Mora wrote: > > > > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > You've said you're working with labbrands.com <http://labbrands.com > >. > > > > labbrands.com <http://labbrands.com> has address > 192.185.51.89 > > mail.labbrands.com <http://mail.labbrands.com> has address > > 192.185.51.89 > > www.labbrands.com <http://www.labbrands.com> is an alias for > > labbrands.com <http://labbrands.com>. > > > > telnet proves that Exim is running on that IP address. Either you're > > running it, or hostgator is redirecting the SMTP ports. > > > > You added: > > lists.labbrands.com <http://lists.labbrands.com> has address > > 190.145.27.66 > > > > Presumably that's a different machine. > > > > So that now needs an MX record, and a firewall routing. > > > > > > I added the MX record on our hostgator hosting like this: > > image.png > > > > Is it correct??? > > > No. And sending images to the mailing list doesn't get you help. > > You set up lists.labbrands.com as a secondary server, not an independent > mail domain. This will cause you serious grief. > > You need to get some help from a more suitable list. Setting this up is > not mailman-specific, and getting it right is more than a quick note. > > Try the Postfix documentation & mailing lists. > > > > > > > And the SPF > > records ... and spam and virus filters, and all the other stuff > > you need > > to setup an independent, public-facing smtp server. > > > > But at least you won't have to relay. > > > > Good luck. > > > > On 03-Aug-17 16:55, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > > >> I think you're confused. > > >> > > >> You already have mail.labbrands.com <http://mail.labbrands.com> > > set up as the MX record for > > >> labbrands.com <http://labbrands.com>. And it has an A record > > with the same address as your > > >> webserver. > > >> > > > I'm working with the hostgator mailserver, we are not running a > > local > > > mailserver. > > > > > > As suggested I added an A record like this: > > > [image: image.png] > > > > > > Is it correct? is it redirecting to my Ip so I can redirect it to > my > > > postfix/mm3 server? > > > > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > > >> server running on that IP address. You can't have 2 servers > > on port > > >> 25. In that case, as has been noted before, you'll need to setup > a > > >> relay in that server, not a firewall redirect. Depending on > > your MTA, > > >> you would need to relay to your internal server. And make sure > > your > > >> firewall setup allows your MTA to do this. > > >> > > >> We can see it's EXIM: > > >> > > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > > >> Trying 192.185.51.89... > > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > > (192.185.51.89). > > >> Escape character is '^]'. > > >> help > > >> 220-gator4137.hostgator.com > > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > > Aug 2017 15:47:48 > > >> -0500 > > >> 220-We do not authorize the use of this system to transport > > unsolicited, > > >> 220 and/or bulk e-mail. > > >> 214-Commands supported: > > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > > >> quit > > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > > closing connection > > >> Connection closed by foreign host. > > >> > > >> Or, consolidate all your e-mail to one server - which is a lot > > easier to > > >> manage unless you have a really big operation. Postfix is > > probably the > > >> right choice, but requires more setup. > > >> > > >> Although Mailman3 configuration is not well documented (as you've > > >> discovered), you may want to get help from someone with more > > general > > >> network and mail experience. You're now into territory that is, > as > > >> Simon indicated, not Mailman-specific. > > >> > > >> On 03-Aug-17 16:28, Rafael Mora wrote: > > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > > >> escribió: > > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > > >>>> escribió: > > >>>>>> You need to forward port 25 for SMTP mail delivery and if > > you want the > > >>>>>> web UI (Postorius and HyperKitty) accessible from the > > outside, port 80 > > >>>>>> for http and/or port 443 for https > > >>>>>> < > > >>>>>> > > >> > > > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > > >>>>>>> . > > >>>>> I mean for incoming mail redirected from my hostgator > > hosting, because > > >>>> when > > >>>>> I suscribe an email address MM3 sends a confirmation email, > > so I have > > >> to > > >>>>> reply to be suscribed to the list. > > >>>> As I said, for mail delivery you need to forward port 25 to > > the Mailman > > >>>> server. > > >>>> > > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my > local > > >> centos7 > > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > >>> > > >>> > > >>>> -- > > >>>> Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> > > >>>> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >>>> > > >> -- > > >> This communication may not represent my employer's views, > > >> if any, on the matters discussed. > > >> > > >> _______________________________________________ > > >> Mailman-users mailing list > > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > >> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >> > > > > -- > > This communication may not represent my employer's views, > > if any, on the matters discussed. > > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > 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, 9 months

[MM3-users] Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gilles Filippini

Mark Sapiro a écrit le 23/04/2020 à 19:02 : > On 4/23/20 2:48 AM, Gelpi Andrea wrote: >> >> I saw the change in the file. >> >> As I'm not a programmer How can I test your fix? >> >> My system was installed via Debian 10 stable repository. >> >> I upgrade with testing repository postorius, django and mailmanclinet >> >> Postorius V 1.3.2 >> Django V. 2.2.12 >> Django filters V 2.1.0 >> Djanog mailman V 1.3.2 >> mailmanclient V 3.3.0 > > > I don't know where the Debian package puts things, but you have to find > the location of postorius/views/list.py. Something like > > locate views/list.py On debian this file is part of the python3-django-postorius package, and is installed here: /usr/lib/python3/dist-packages/postorius/views/list.py > > should find it. Then you need to download > <https://gitlab.com/mailman/postorius/-/merge_requests/500.diff> and > edit it to remove the first 15 lines so the first remaining line is the > > diff --git a/src/postorius/views/list.py b/src/postorius/views/list.py > > line. Then make a backup copy of postorius/views/list.py and run the command > > patch postorius/views/list.py path/to/500.diff > > where postorius/views/list.py is actually the full path to > postorius/views/list.py and 500.diff is the edited file you downloaded. You'll have also to remove the compiled files from the __pycache__ directory: $ sudo rm /usr/lib/python3/dist-packages/postorius/views/__pycache__/list.cpython-*.pyc > Then restart uWSGI. If anything goes wrong, restore your backup copy of > postorius/views/list.py and restart uWSGI. The best way to restore is to force the re-installation of the package: $ sudo apt-get install --reinstall python3-django-postorius It will take care of the compilation part. _g.

5 years

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Tue, Dec 27, 2022 at 11:23 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: > > ... > >> I don't want to put more noise in the list. But I'm confused because > >> I always updated via pip the apache mod_wsgi thinking is was needed > >> for my configuration. If it is not, I will stop updating it. > > > > Based on the above you ARE using Apache mod_wsgi and if you are still > > also running uwsgi as > > > > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > > > > that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) and > see how it goes. > > Again, thanks for your kind support. > I have actually deactivated mine, and life is still good with my MM3. And just so that my mind is in the clear, there are three ways of getting the full MM3 functionality, viz: 1. Mailman core, Django's cluster, and Gunicorn 2. Mailman core, Django's cluster, and uWSGI 3. Mailman core, Django's cluster, and mod_wsgi And something that has not been quite clear to me: What is the purpose of Django's cluster in all this? I am asking because on my FreeBSD server, I usually see not less than 30 PIDs for: /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/django-admin qcluster --pythonpath /opt/mailman/mm/ --settings settings (python3.9) And there is a time I found it having 240 PIDs. Would there be a problem if I limit the number of workers to "8"? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Setting up Admin Account

by Stephen J. Turnbull

Pierre Abbat writes: > On Friday, November 17, 2017 1:51:15 PM EST Simon Hanna wrote: > > You are not supposed to create the directory mailman-suite_project but > > clone the mailman-suite project from gitlab and use it. > > None of the manage.py commands listed by your search are the right ones. > > The correct one is the one included in the repository of mailman-suite > > It appears that setting up Mailman 3 requires knowledge of Django, which I > don't have. I'm going to try something else. You're welcome to do so since you know your needs better than we do, but please allow me to advise you that running Mailman 3 in most cases doesn't require knowledge of Django as long as (1) you follow the instructions *exactly*, and of course (2) assuming those instructions are correct. Mailman 3 being just on the edge of becoming the industry standard for mailing list managers, yes, assumption (2) is occasionally violated. In my experience, (1) is a more frequent source of user troubles. Either way, we[1] are one heck of a lot faster at responding than most commercial and open source products when users have trouble. And we do have reason to lay claim to "industry standard". Footnotes: [1] By "we" I really mean Mark Sapiro, Abhilash Raj, and off and on Simon Hanna. It's rare that it takes as much as 24 hours to get attention from one of them, and if Mark can handle it, usually you get an immediate solution. I haven't been able to keep up for months, but I hope to get back into the rotation soonish (in the new year). -- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years, 5 months

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Oops, premature send. I did grep through the whole mailman core code base for "del", and didn't come up with anything that looks like it would delete fields like Content-Type and Message-ID (assuming the default for anonymous_list_keep_headers, I wish I had thought to ask about that, but who changes it?) I assumed Content-Type is modified by direct assignment in handlers that delete parts or transform them to a different MIME type. I wonder if his Python is old enough to not recognize negated regexps? That should be logged in errors. Or (as you guessed), the '(?!x-)' regexp (or the whole content of anonymous_list_keep_headers) has been removed? Stephen J. Turnbull writes: > Mark Sapiro writes: > > > This apparently confuses the Python email package so that the > > get_payload() method returns a list of strings rather than a list of > > message objects. > > Yes, I got that far too. I'm guessing that in the absence of a > Content-Type, which then *should* default to text/plain, the email > package goes ahead and detects the MIME headers anyway (although I > don't think it should do that) and breaks the message into MIME > parts. I would think we'd raise an Exception here. > > If there's a reason for the email package to do that detection > (*shrug*, it seems to work), then the dispatching in _handle_text > should be done on the Python type rather than the MIME Content-Type. > > I forget exactly how the code is structured, the relevant dispatching > may be in _dispatch or in _dispatch_meth. > > 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/ >

2 years, 8 months

Search results for query "sapiro"