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

[MM3-users] Re: Extracting mailing list users

by Jan Eden

On 2022-12-30 10:29, Mark Sapiro wrote: > On 12/30/22 03:25, Jan Eden via Mailman-users wrote: > > On minor issue: All user names with > > non-ASCII characters appear with quoted-printable encoding (e.g. > > =?utf-8?q?J=C3=BCrgen?=). Is there a way to output UTF-8 instead of QP? > > I just created https://gitlab.com/mailman/mailman/-/issues/1048 for this. I > think this patch > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -104,10 +104,10 @@ def display_members(ctx, mlist, role, regular, digest, > if nomail is not None: > if member.delivery_status not in status_types: > continue > - if email_only: > + if email_only or not address.display_name: > print(address.original_email, file=outfp) > else: > - print(formataddr((address.display_name, > address.original_email)), > + print(f'{address.display_name} <{address.original_email}>', > file=outfp) > > ``` > (line may be wrapped) will fix it. Excellent – thank you! - Jan

2 years, 6 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

David Bremner <david(a)tethera.net> writes: > Mark Sapiro <mark(a)msapiro.net> writes: >> >> Thank you. I tested that DSN with current flufl.bounce and it is >> recognized as a temp failure for the reported address and that in turn >> should just be ignored by Mailman's bounce runner and not reported as >> unrecognized. >> >> What version of Mailman core is this and what version of flufl.bounce? >> > > Sorry, meant to reply on list with the rest of the details, but got > distracted by making dinner. So it sounds like the problem is old > versions of flufl.bounce. > > This particular machine is running debian oldstable, so things are a bit > out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look > into upgrading at least flufl.bounce. Oh. It's actually 3.0.1. Still not new enough, but 3 years newer. d

3 years, 8 months

[MM3-users] Re: emails to list missing from archive after upgrade

by Quanah Gibson-Mount

--On Thursday, January 18, 2024 8:13 PM -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/24 19:57, Quanah Gibson-Mount wrote: >> >> Ok, I've found them in /var/lib/mailman3/archives/hyperkitty/spool, so >> it does seem like the issue is the indexer hasn't run. Not sure what >> process controls that. > > > That's not the issue. There was an exception in mailman-hyperkitty's > communication with HyperKitty. You will find the errors and tracebacks in > mailman.log. Once you fix the issue, whatever it is, the messages will be > archived. mailman-hyperkitty retries all the messages in > /var/lib/mailman3/archives/hyperkitty/spool with each new post. Thanks Mark! The debian upgrade munged the hyperkitty config. Once that was fixed and a new message posted to the list, everything got archived as it should have been. Regards, Quanah

1 year, 5 months

[MM3-users] Re: Your Dashboard

by Allan Hansen

All, Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. Time to visit gitlab? Yours, Allan Hansen hansen(a)rc.org > On Feb 11, 2020, at 12:26 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/11/20 11:00 AM, Mark Dadgar wrote: >> On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >>> everytime I receive a mail for moderation it says: >>> >>> At your convenience, visit your dashboard to approve or deny the >>> request. >>> >>> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. > > > There's no overall dashboard per se. The message actually refers to > whatever web UI you use to manage the list. The default template for > this message is non-specific because it comes from Mailman core, and > core doesn't know if you are using Postorius or some other web > management system or non at all, and even if it were to assume > Postorius, it doesn't know the URL. > > >>> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >>> >>> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? > > > As I said, there is no overall dashboard in Postorius, just the > individual list management pages. > > >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via Postorius. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 4 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thank you for your prompt response Mark, Στις 2019-09-18 19:12, Mark Sapiro έγραψε: > Is only one list affected, and is it all messages from this list or > only > some? Just two messages from this certain list. Subsequent messages and other activity seems to work properly > Do some deliveries of the problem message succeed? > I think not, the IndividualDelivery lines list all all recipients (list is small so I was able to check) > Postfix can return a 421 status > and drop the connection if there are too many invalid local recipients, > although I don't know if this would apply in the VERP case. Well there is no connection to postfix at all when the runner starts and the "Cannot connect to SMTP server" log shows up. Otherwise I'd have seen something in the postfix logs or tcpdumps in localhost.

5 years, 9 months

[MM3-users] Re: export/import list?

by Dave McGuire

On 8/22/23 17:59, Mark Sapiro wrote: >> I'm moving from sqlite3 to postgres; I can handle that migration. >> But I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone >> else) know of any schema changes? I spot-checked the first few and >> they looked the same, but before going through all of them I figured >> I'd just ask here. > > Schema changes are handled automatically by alembic. The migrations are > defined in /mailman/database/alembic/versions/. Your current version is > is stored in the database in the alembic_version table. When Mailman > core is started, all migrations from your current version to the latest > version will be applied to bring your database up to date. I.e., you > don't need to be concerned about schema changes upon upgrade. They are > handled automatically. Brilliant! Thank you Mark. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

1 year, 10 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/ >

9 years, 1 month

[MM3-users] 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

7 years, 9 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Odhiambo Washington

On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > Am 2024-04-26 00:52, schrieb Mark Sapiro: > > On 4/25/24 14:01, Thomas Stein wrote: > >> Am 2024-04-25 22:03, schrieb Mark Sapiro: > >>> > >>> I don't know how things are arranged in the Debian/Ubuntu package, > >>> but you may have a settings.py which at the end does something like > >>> ``` > >>> try: > >>> from settings_local import * > >>> except ImportError: > >>> pass > >>> ``` > >>> If that is the case, adding the above snippet to the end of > >>> settings_local.py should work. > >> > >> Yes, that's the case. I added the snippet in question to > >> settings_local.py but this leads to another error: > >> > >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> > >> from settings_local import * > >> File "/usr/share/mailman3-web/settings_local.py", line 194, in > >> <module> > >> x = list(MIDDLEWARE) > >> ^^^^^^^^^^ > >> NameError: name 'MIDDLEWARE' is not defined > >> dpkg: error processing package mailman3-web (--configure): > > > > Yes. I understand. In your case, MIDDLEWARE is only defined in > > settings.py and not in settings_local.py. As I understand it originally > > you added > > ``` > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to settings.py and you say it didn't help. I don't know why that > > wouldn't work as long as there is no setting for MIDDLEWARE in > > settings_local.py and you added that after the MIDDLEWARE setting in > > settings.py. > > When you say it didn't help, do you mean you still get the > > > > django.core.exceptions.ImproperlyConfigured: > > allauth.account.middleware.AccountMiddleware must be added to > > settings.MIDDLEWARE > > > > message or something else? I note that the original post in this thread > > refers to /etc/mailman3/mailman-web.py which is presumably where the > > package ultimately puts the Django settings, and I don't know what > > `dpkg --configure` is doing. > > > > One thing you could try is in settings_local.py, put > > ``` > > from settings import MIDDLEWARE > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to work around the NameError. > > After that I get: > > File "/usr/share/mailman3-web/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' > (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > > I guess I'll wait for the new package for now. > How about adding: MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) in settings_local.py And how about you use the virtualenv method <https://docs.mailman3.org/en/latest/install/virtualenv.html> for more peace of mind in the future? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

Search results for query "sapiro"