Search results for "Postorius" - Mailman-users

Re: Installing mailman 3

by Rafael Mora

Look: [root@localhost mailman]# find / -name mailman.cfg /etc/mailman.cfg /root/var/etc/mailman.cfg /root/mailman/src/mailman/config/mailman.cfg /root/dev/mailman/mailman/src/mailman/config/mailman.cfg /var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/postorius/var/etc/mailman.cfg /mailman/mailman/src/mailman/config/mailman.cfg /mailman/mailman/build/lib/mailman/config/mailman.cfg /mailman/mailman/var/etc/mailman.cfg El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > There must be another config file being picked up. Have a look at the > mailman.cfg search order explained here [1]. > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' > to be sure. You'll want to delete any in the search path and then rerun > 'mailman info'. > > [1] > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > -Kyle > > -- Atentamente / Best Regards Ing. Rafael Mora

9 years

Countdown to the 3.1 release

by Barry Warsaw

Previously I mentioned the three big outstanding branches that I'd like to land for Mailman 3.1 Core, the templates branch, the MySQL support branch, and the unsubscription workflow branch. I've now also gone through all the bugs previously targeted to milestone 3.1, and there are only three left: https://gitlab.com/mailman/mailman/milestones/2 I think these are important enough to fix for 3.1 and I welcome merge requests while the other three branches are ongoing. Please take a look at any other bugs not assigned to milestone 3.1 and let me know if you think any are serious enough to block the 3.1 release. I'll say in advance that I'm going to be brutal in assessing them, because 3.1 really needs to be released soon! Note too that there may be blockers for Postorius, Hyperkitty, and mailman.client, but I haven't looked at those subprojects yet. How close are they to being release ready? Cheers, -Barry

10 years

Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

Re: [MM3-users]Re: Is it possible to grant all users the ability to Create List

by tibor.molnar＠waltoninstitute.ie

Hi, I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: Superuser: Can do everything. AnonymousUser: Can view list index and info pages. Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how?

5 years

Re: Error downloading CSV for 1,300 members

by Mark Sapiro

On 2/23/23 10:45, Jose Bernal wrote: > Any suggestions on troubleshooting downloading a modest-size CSV file for a > list with 1,300 members? Clicking "CSV Export" on smaller lists works > fine, but on this larger list I get this error in mailman-web.log: > > Thu Feb 23 10:03:32 2023 - uwsgi_response_write_body_do(): Broken pipe > [core/writer.c line 429] during GET /mailman3/postorius/lists/ > members.list.ocdla.org/csv_view/ (172.31.54.89) > OSError: write error This is probably due to a timeout in uwsgi. This thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> is about timeouts when downloading archives, but the same considerations apply. To increase the worker timeout for uwsgi, set the harakiri option. See <https://uwsgi-docs.readthedocs.io/en/latest/Glossary.html#glossary> and <https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: Try to Implement Template for The message sent to subscribers when a subscription confirmation is required

by Stephen J. Turnbull

Gerald Vogt writes: > Why would you double book port 80? That's really a bad idea and > causes issues like the one you see... When I read that I assumed that nginx would resolve in favor of the narrower interface:port declaration. If double-booking is happening, nginx should be issuing an error, or (nginx being pretty picky in my experience) even refusing to start. Anyway, OP should look for messages about problems binding to ports in the nginx and uwsgi logs. > Your "INTERNAL" server binds to 127.0.0.1 port 80, only. That's not quite true. Normally the WSGI service will bind to another port for Postorius/HyperKitty, typically 8000. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Thanks Mark for your time. I will follow your recommendation and try mailman bundler again, with care so that new conflicts won't occur as happened yesterday. Mailman bundler docs, in the first paragraph, refer to combined installation of GNU Mailman, Postotius, and Hyperkitty. Does that mean that mailman.client will be installed later separately? My CentOs 7 distribution does not offer python3.4.pip. https://pypi.python.org/pypi/pip offers pip 8.1.2 in two versions: Python Wheel pip-8.1.2-py2.py3-none-any.whl (md5, pgp) Source pip-8.1.2.tar.gz (md5, pgp) Which one should I choose? I also notice that postfix is required. yum offers the following options: pcp-pmda-postfix.x86_64 : Performance Co-Pilot (PCP) metrics for the Postfix (MTA) postfix.x86_64 : Postfix Mail Transport Agent postfix-perl-scripts.x86_64 : Postfix utilities written in perl postfix-sysvinit.noarch : SysV initscript for postfix spamass-milter-postfix.noarch : Postfix support for spamass-milter postgrey.noarch : Postfix Greylisting Policy Server pypolicyd-spf.noarch : SPF Policy Server for Postfix (Python implementation) sqlgrey.noarch : Postfix grey-listing policy service Which of these options are useful? Which ones are unnecessary? Again, thanks very much for your time and hope that the other subscribers in this list find this thread adequate. Haven't found the link on our distribution list profile settings for uploading an avatar. Best regards, Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining) 2016-05-28 14:06 GMT-04:00 Mark Sapiro <mark(a)msapiro.net>: > On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > > > In order to avoid compatibility issues, I reinstalled CentOs 7. > Firewalld, Apache and BIND are operational. I also installed Python 3.4 at > http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; > however I understand that Python 2.7 is still available and am confused > about usage of each version. > > > Mailman 3 consists of several pieces. There is a core engine which is > Python 3. The core does the basic email list management and exposes many > options and settings via a RESTful API. > > There is also mailman.client which provides Python bindings for the REST > API. This is Python 2. > > We also provide a web management UI, Postorius and an archiver, > HyperKitty. These are Django applications and all of this is Python 2. > > There are other pieces as well. > > > > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if > you quickly let me know how to install it. I do not wish to use mailman > bundler. > > > This is only the core. You can install it with > > python3 setup.py install > > either in a python 3 virtualenv or not, but this will only give you the > core. > > I suggest you see the docs at <http://docs.list.org/en/latest/>, and if > you don't want to use bundler, see > <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the > recommended way to set up a working, non-development Mailman suite. > > In short, the core requires Python 3.4, most of the rest of the suite > requires Python 2.7 because of dependencies not yet ported to Python 3. > > -- > 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/ >

10 years, 1 month

Re: config incoming email in my domain cpanel

by Mark Sapiro

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>) 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Mark Sapiro

On 5/19/20 5:57 AM, Ralf Wiegand wrote: > (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, openid, postorius, sessions, > sites, socialaccount > Running migrations: > Applying contenttypes.0001_initial...Traceback (most recent call last): ... > File > "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", > line 221, in names_digest > h = hashlib.md5() > *ValueError: error:060800A3:digital envelope > routines:EVP_DigestInit_ex:disabled for fips* > > > > Hello group, I am running into this error. any idea what is going > wrong here? This is a Django issue, not Mailman per se. The migration that's failing is django/contrib/contenttypes/migrations/0001_initial.py. A brief search seems to indicate that this won't work with NSS FIPS. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

8 years, 9 months

Mailman-users search results for query "Postorius"