Search results for query "sapiro"
- 6228 messages
[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'
by Shashikanth Komandoor
Hi Mark,
Any suggestions over my earlier email? I am waiting for your
reply.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Oct 27, 2020 at 1:16 PM Shashikanth Komandoor <
shashikanth.komandoor(a)gmail.com> wrote:
> Hi Mark,
>
> Thank you for your help. I have traced the versions of
> different components of mailman 3. I am downloading through GIT LAB because
> I need to modify the code according to my organization's requirements like
> to add SMS notifications when a mail is waiting for pending approval and so.
>
> With your help, I have found out the commits I am using in my
> environment. I got them using the way you suggested "git log". That may be
> helpful for you to help dummies like me.
>
> *### Mailman Core Version ###*
>
> *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded*
> *Merge: 98cf97b 0bca998*
> *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>*
> *Date: Thu Oct 15 14:02:36 2020 -0700*
>
> * Merge branch 'template' into 'master'*
>
> * Clarify the posting instruction in the list welcome message.*
>
> * See merge request mailman/mailman!723*
>
> *### django-mailman3 Version ###*
>
> *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40*
> *Merge: ea2b33a c091e43*
> *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>*
> *Date: Thu Oct 15 00:40:51 2020 +0000*
>
> * Merge branch 'fix-ci' into 'master'*
>
> * Use GHCR for the CI image*
>
> * See merge request mailman/django-mailman3!108*
>
> *### Hyperkitty Version ###*
>
> *commit 36f43466763c2686cf4d69c982ea64b956c30939*
> *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>*
> *Date: Mon Oct 5 04:54:44 2020 +0000*
>
> * Use GH registry to pull CI image.*
>
> *### Mailmanclient Version ###*
>
> *commit aaa529808e2d61899f90509da4ea802a70d2c8ff*
> *Merge: ff39dd8 8670751*
> *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>*
> *Date: Thu Oct 15 01:09:32 2020 +0000*
>
> * Merge branch 'fix-ci' into 'master'*
>
> * Use GHCR for the CI image*
>
> * See merge request mailman/mailmanclient!130*
>
> *### Mailman Hyperkitty Version ###*
>
> *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0*
> *Merge: 35ff801 04deff5*
> *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>*
> *Date: Fri Jun 19 18:15:57 2020 +0000*
>
> * Merge branch 'fix_25' into 'master'*
>
> * Add a test for the presence of surrogates in the stringified message.*
>
> * Closes #25*
>
> * See merge request mailman/mailman-hyperkitty!7*
>
> *### Mailman-suite Version ###*
>
> *commit 3b8780f26d544cb333970eae43ccffc7e34314aa*
> *Merge: 74e7927 4463b31*
> *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>*
> *Date: Sat May 30 00:32:40 2020 +0000*
>
> * Merge branch 'doc_mb4' into 'master'*
>
> * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.*
>
> * See merge request mailman/mailman-suite!8*
>
> *### Postorius Version ###*
>
> *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e*
> *Merge: 61242d2 321310c*
> *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>*
> *Date: Thu Oct 15 00:43:14 2020 +0000*
>
> * Merge branch 'fix-ci' into 'master'*
>
> * Use the GHCR registry for CI image.*
>
> * See merge request mailman/postorius!549*
>
> I have removed only mailmanclient and re-cloned it from gitlab and
> ran the python setup.py develop command. But still the same error.
>
> Is there anything else I can do to get rid of that error.
>
> Thanks in advance.
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
> <#m_6854939421424022049_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote:
>
>> On 10/26/20 6:10 PM, Shashikanth Komandoor wrote:
>> >
>> > How to find out the versions of the each and every component
>> > of the mailman 3 like mailman core, mailmancilent, postorius,
>> > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so,
>> > after installation?
>>
>>
>> cd to the directory in which you cloned the gitlab project for the
>> component and do `git log`
>>
>>
>> > If I am running an old mailmanclient or older version of any
>> > other mailman component, please suggest how to upgrade either one or
>> > multiple components based on the requirement. Is there any link that
>> > would help me to upgrade ?
>> >
>> > I have used the
>> > link https://docs.mailman3.org/en/latest/devsetup.html to install the
>> > mailman 3 components. I expected that the procedure followed in this
>> > link would install the latest versions of the mailman 3 components.
>> > Please correct me if I am wrong. Is there any latest version
>> > compatibility table ?
>>
>>
>> If you installed each of mailman, mailmanclient, django-mailman3,
>> postorius and hyperkitty according to instructions like
>>
>> $ cd ~/mailman
>> $ git clone https://gitlab.com/mailman/mailmanclient.git
>>
>> Then set up mailmanclient:
>>
>> $ cd mailmanclient
>> $ python setup.py develop
>> $ cd ..
>>
>> from that document, you should have the latest version. If that is the
>> case, `git log` in the mailmanclient directory should begin like
>>
>> commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master,
>> origin/master, origin/HEAD)
>> Merge: ff39dd8 8670751
>> Author: Abhilash Raj <maxking(a)asynchronous.in>
>> Date: Thu Oct 15 01:09:32 2020 +0000
>>
>> Merge branch 'fix-ci' into 'master'
>>
>> Use GHCR for the CI image
>>
>> See merge request mailman/mailmanclient!130
>>
>> commit 8670751caff689733751ef323ef521c4a3fa1237
>> Author: Abhilash Raj <raj.abhilash1(a)gmail.com>
>> Date: Wed Oct 14 17:36:58 2020 -0700
>>
>> Use GHCR for the CI image
>>
>> commit ff39dd8f03a820f442f2251553c444370df3b914
>> Merge: 80ebed4 76d44e1
>> Author: Abhilash Raj <maxking(a)asynchronous.in>
>> Date: Fri Aug 7 19:35:05 2020 +0000
>>
>> Merge branch 'invite' into 'master'
>>
>> Add support for inviting an email address to join a list.
>>
>> See merge request mailman/mailmanclient!129
>>
>> or if you did this before Oct 15, maybe it starts with
>> commit ff39dd8f03a820f442f2251553c444370df3b914
>>
>> The particular commit you need for your issue is
>>
>> commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583
>> Merge: c8dcb1e 28d1c3a
>> Author: Abhilash Raj <maxking(a)asynchronous.in>
>> Date: Sat May 16 08:02:21 2020 +0000
>>
>> Merge branch 'held-count' into 'master'
>>
>> Add a new get_held_count() API to get a count of held messages.
>>
>> See merge request mailman/mailmanclient!122
>>
>>
>>
>> Note that unless you intend to do actual development of Mailman 3, you
>> should be following
>> <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather
>> than <https://docs.mailman3.org/en/latest/devsetup.html>.
>>
>> --
>> 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/
>>
>
>
> --
> Thanks & Regards,
> Shashi Kanth.K
> 9052671936
>
>
>
>
--
Thanks & Regards,
Shashi Kanth.K
9052671936
5 years, 7 months
[MM3-users] Re: Issue converting table charset to utf8mb4 on mysql
by Helio Loureiro
Ok. Thanks for the clarification.
Just a heads up: something went wrong. Very wrong. I had to revert the
database to the last backup.
But not on mailman3. It was on mailman3web.
Apparently things got really bad after I converted tables django_q_ormq and
hyperkitty_sender. After that hyperkitty got into cyclical crashes.
Best Regards,
Helio Loureiro
https://helio.loureiro.eng.br
https://github.com/helioloureiro
https://mastodon.social/@helioloureiro
On Sun, 24 Mar 2024 at 01:24, Mark Sapiro <mark(a)msapiro.net> wrote:
> On 3/23/24 12:14, Helio Loureiro wrote:
>
> > So the question is whether it is possible to change the types in this
> table.
> >
> > MariaDB [mailman3]> desc pendedkeyvalue;
> > +-----------+----------------+------+-----+---------+----------------+
> > | Field | Type | Null | Key | Default | Extra |
> > +-----------+----------------+------+-----+---------+----------------+
> > | id | int(11) | NO | PRI | NULL | auto_increment |
> > | key | varchar(255) | YES | MUL | NULL | |
> > | value | varchar(20000) | YES | MUL | NULL | |
> > | pended_id | int(11) | YES | MUL | NULL | |
> > +-----------+----------------+------+-----+---------+----------------+
> > 4 rows in set (0.001 sec)
> >
> > key and value are varchar. Can any of them be changed to text instead?
> > Perhaps even both?
>
>
> I wouldn't bother. The keys and values in the pendedkeyvalue table
> should all be OK as latin1. That's why that table wasn't included in the
> migration at
>
> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/alemb…
>
> --
> 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/
> Archived at:
> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
>
> This message sent to helio(a)loureiro.eng.br
>
2 years, 2 months
[MM3-users] Re: HyperKitty Question
by Samir Faci
Sorry about this, I had a draft ready to go sitting there for the past few
hours.
I stand corrected. I'm not sure what combinations of factors fixed this
but it's all good now.
base_url: https://lists.domain.org/hyperkitty/ worked. I have an
archive and about 50 emails of me talking to myself while testing all this
out.
Thank you for all the help Marc and everyone else on the list.
--
Samir Faci
On Mon, May 4, 2020 at 7:36 PM Mark Sapiro <mark(a)msapiro.net> wrote:
> On 5/4/20 6:11 PM, Samir Faci wrote:
> >
> > I have nginx running with multiple website being serviced from the same
> > server.
> >
> > I updated the config where port 80 gets redirected to SSL.
> >
> > I tried setting mailman3-hyperkitty.conf to both:
> >
> > base_url: http://localhost/hyperkitty> base_url:
> https://lists.domain.com/hyperkitty/
> >
>
> Either should be OK, possibly dependent of your nginx config.
>
> > But neither seem to be working. Does hyperkitty require traffic to be
> > going over port 80?
>
>
> No. https should work. Can you go to
> https://lists.domain.com/hyperkitty/ in a browser?
>
> Do you have api_key: set in mailman3-hyperkitty.conf and is it set to
> the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django
> settings.
>
> Note the value needs to be quoted in
>
> MAILMAN_ARCHIVER_KEY = 'the_value'
>
> and not in
>
> api_key: the_value
>
> because the former is a Python string and the latter is a config value.
>
> --
> 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/
>
--
Thank you
Samir Faci
https://keybase.io/csgeek
6 years
[MM3-users] Re: RDS CA changes
by Hirayama, Pat
Thanks, Mark. That's what it looked like to me, but I wanted someone with more expertise / experience to weigh in.
Have a great day!
Pat Hirayama
Pronouns: he/him/his
Systems Engineer
IT | Systems Engineering
Fred Hutchinson Cancer Center
O 206.667.4856
phirayam(a)fredhutch.org
________________________________
From: Mark Sapiro <mark(a)msapiro.net>
Sent: Monday, August 12, 2024 10:49
To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>
Subject: [MM3-users] Re: RDS CA changes
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 8/12/24 10:23, Hirayama, Pat wrote:
>
> As near as I can tell from reading the Mailman 3 docs, and looking at my mailman.cfg and settings_local.py ... I don't know that Mailman 3 is using certificate verification for the PostgreSQL connection. At least, I can't see anything in those configuration files that suggest this. Does anyone know if this is the case – or which configuration file I should look at to verify? Will my Mailman 3 be ok if the DBAs go ahead and update the certificates on their end?
There are two places where the database access is defined. They are the
[database] section in mailman.cfg and the DATABASES definition in
Django's settings.
I don't see a way in either of these to specify TLS for the connection,
possibly it is set on the PostgreSQL side. In any case, I don't think
there'd be any issue if the DBAs go ahead and update the certificates on
their end.
--
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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm…
Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma…
This message sent to phirayam(a)fredhutch.org
1 year, 9 months
[MM3-users] Re: Command Emails not Working
by Brinson, Jason T
As requested:
Posfix log (journalctl -u | grep demo-list):
Apr 22 11:14:16 cc-postoffice-01 postfix/qmgr[523389]: E6943400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1853, nrcpt=1 (queue active)
Apr 22 11:14:48 cc-postoffice-01 postfix/lmtp[523634]: F1957400A9D: to=<demo-list+1a65bace2719a299598865b8e3bf7b78d1ec0a5f(a)mailman.cc.gatech.edu<mailto:demo-list+1a65bace2719a299598865b8e3bf7b78d1ec0a5f@mailman.cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.59, delays=0.5/0.01/0.01/0.07, dsn=2.0.0, status=sent (250 Ok)
Apr 22 11:14:50 cc-postoffice-01 postfix/qmgr[523389]: 089D0400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=20898, nrcpt=1 (queue active)
Apr 22 11:14:50 cc-postoffice-01 postfix/lmtp[523634]: 089D0400A9D: to=<demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>>, orig_to=<demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok)
Apr 22 11:14:50 cc-postoffice-01 postfix/qmgr[523389]: 40995400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1322, nrcpt=1 (queue active)
Apr 22 11:14:52 cc-postoffice-01 postfix/qmgr[523389]: 1063C400A9D: from=<demo-list-bounces+jbrinson3=gatech.edu(a)cc.gatech.edu<mailto:demo-list-bounces+jbrinson3=gatech.edu@cc.gatech.edu>>, size=21257, nrcpt=1 (queue active)
Apr 22 11:20:47 cc-postoffice-01 postfix/qmgr[523389]: 9D5E0400A3C: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1860, nrcpt=1 (queue active)
Apr 22 11:21:56 cc-postoffice-01 postfix/lmtp[526023]: EEB2640083E: to=<demo-list+ae434bc0e6da7e08d0b66c8abf94e259e0c5e8a1(a)mailman.cc.gatech.edu<mailto:demo-list+ae434bc0e6da7e08d0b66c8abf94e259e0c5e8a1@mailman.cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.28, delays=0.26/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok)
Apr 22 11:21:57 cc-postoffice-01 postfix/qmgr[523389]: C12EA40083E: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=1326, nrcpt=1 (queue active)
Apr 22 11:21:57 cc-postoffice-01 postfix/qmgr[523389]: C6D87400A9D: from=<demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu>>, size=24425, nrcpt=1 (queue active)
Apr 22 11:21:57 cc-postoffice-01 postfix/lmtp[526023]: C6D87400A9D: to=<demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>>, orig_to=<demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu>>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0/0.01/0.01, dsn=2.0.0, status=sent (250 Ok)
Apr 22 11:21:59 cc-postoffice-01 postfix/qmgr[523389]: A72C940083E: from=<demo-list-bounces+jbrinson3=gatech.edu(a)cc.gatech.edu<mailto:demo-list-bounces+jbrinson3=gatech.edu@cc.gatech.edu>>, size=24784, nrcpt=1 (queue active)
Postfix_lmtp:
demo-list(a)mailman.cc.gatech.edu<mailto:demo-list@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-bounces(a)mailman.cc.gatech.edu<mailto:demo-list-bounces@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-confirm(a)mailman.cc.gatech.edu<mailto:demo-list-confirm@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-join(a)mailman.cc.gatech.edu<mailto:demo-list-join@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-leave(a)mailman.cc.gatech.edu<mailto:demo-list-leave@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-request(a)mailman.cc.gatech.edu<mailto:demo-list-request@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-subscribe(a)mailman.cc.gatech.edu<mailto:demo-list-subscribe@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
demo-list-unsubscribe(a)mailman.cc.gatech.edu<mailto:demo-list-unsubscribe@mailman.cc.gatech.edu> lmtp:[127.0.0.1]:8024
Postfix_vmap:
demo-list(a)cc.gatech.edu<mailto:demo-list@cc.gatech.edu> demo-list(a)mailman.cc.gatech.edu<mailto:demo-list@mailman.cc.gatech.edu>
demo-list-bounces(a)cc.gatech.edu<mailto:demo-list-bounces@cc.gatech.edu> demo-list-bounces(a)mailman.cc.gatech.edu<mailto:demo-list-bounces@mailman.cc.gatech.edu>
demo-list-confirm(a)cc.gatech.edu<mailto:demo-list-confirm@cc.gatech.edu> demo-list-confirm(a)mailman.cc.gatech.edu<mailto:demo-list-confirm@mailman.cc.gatech.edu>
demo-list-join(a)cc.gatech.edu<mailto:demo-list-join@cc.gatech.edu> demo-list-join(a)mailman.cc.gatech.edu<mailto:demo-list-join@mailman.cc.gatech.edu>
demo-list-leave(a)cc.gatech.edu<mailto:demo-list-leave@cc.gatech.edu> demo-list-leave(a)mailman.cc.gatech.edu<mailto:demo-list-leave@mailman.cc.gatech.edu>
demo-list-owner(a)cc.gatech.edu<mailto:demo-list-owner@cc.gatech.edu> demo-list-owner(a)mailman.cc.gatech.edu<mailto:demo-list-owner@mailman.cc.gatech.edu>
demo-list-request(a)cc.gatech.edu<mailto:demo-list-request@cc.gatech.edu> demo-list-request(a)mailman.cc.gatech.edu<mailto:demo-list-request@mailman.cc.gatech.edu>
demo-list-subscribe(a)cc.gatech.edu<mailto:demo-list-subscribe@cc.gatech.edu> demo-list-subscribe(a)mailman.cc.gatech.edu<mailto:demo-list-subscribe@mailman.cc.gatech.edu>
demo-list-unsubscribe(a)cc.gatech.edu<mailto:demo-list-unsubscribe@cc.gatech.edu> demo-list-unsubscribe(a)mailman.cc.gatech.edu<mailto:demo-list-unsubscribe@mailman.cc.gatech.edu>
-----------------
Jason "Shae" Brinson (They/Them)
IT Support Professional Sr.
Georgia Institute of Technology
College of Computing
801 Atlantic Drive NW
Atlanta, GA 30332
Phone: 404-894-7065
Email: jason.brinson(a)cc.gatech.edu<mailto:jason.brinson@cc.gatech.edu>
From: Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>>
Date: Wednesday, April 22, 2026 at 12:13
To: mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org><mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org>>
Subject: [MM3-users] Re: Command Emails not Working
On 4/22/26 08:47, Brinson, Jason T via Mailman-users wrote:
> Hello,
>
> I have an issue where command emails (-join, -request, etc.) are getting routed to the list itself (and being moderated).
What's in your Postfix mail.log for these messages?
Whats in Mailman's var/data/postfix_lmtp and var/data/postfix_vmap files?
--
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>
To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org>
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
This message sent to jbrinson3(a)gatech.edu<mailto:jbrinson3@gatech.edu>
-----------------
Jason "Shae" Brinson (They/Them)
IT Support Professional Sr.
Georgia Institute of Technology
College of Computing
801 Atlantic Drive NW
Atlanta, GA 30332
Phone: 404-894-7065
Email: jason.brinson(a)cc.gatech.edu<mailto:jason.brinson@cc.gatech.edu>
From: Mark Sapiro <mark(a)msapiro.net>
Date: Wednesday, April 22, 2026 at 12:13
To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>
Subject: [MM3-users] Re: Command Emails not Working
On 4/22/26 08:47, Brinson, Jason T via Mailman-users wrote:
> Hello,
>
> I have an issue where command emails (-join, -request, etc.) are getting routed to the list itself (and being moderated).
What's in your Postfix mail.log for these messages?
Whats in Mailman's var/data/postfix_lmtp and var/data/postfix_vmap files?
--
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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
This message sent to jbrinson3(a)gatech.edu
1 month, 1 week
[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'
by Shashikanth Komandoor
I have run the below commands for sure:
$ cd mailmanclient
$ python setup.py develop
And as you have suggested, I navigate to mailmanclient directory and ran
the git log to provide you the version output.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Wed, Oct 28, 2020 at 12:12 PM Mark Sapiro <mark(a)msapiro.net> wrote:
> On 10/27/20 11:08 PM, Shashikanth Komandoor wrote:
> > Thank you Mark for your response.
> >
> > All the mentioned versions of all the components are taken from my
> > currently running system only in which I am facing the issue.
>
> Did you run
>
> $ cd mailmanclient
> $ python setup.py develop
>
> as it says at <https://docs.mailman3.org/en/latest/devsetup.html>
>
> I do not understand exactly how the various components are installed in
> your installation, so I can't tell you what is wrong, but the version of
> mailmanclient that gives you the AttributeError: 'MailingList' object
> has no attribute 'get_requests_count' is not the one whose latest commit is
>
> ### Mailmanclient Version ###
>
> commit aaa529808e2d61899f90509da4ea802a70d2c8ff
> Merge: ff39dd8 8670751
> Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in>
> Date: Thu Oct 15 01:09:32 2020 +0000
>
> Merge branch 'fix-ci' into 'master'*
>
> Use GHCR for the CI image*
>
> See merge request mailman/mailmanclient!130*
>
> because that one won't have this error.
> --
> 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/
>
--
Thanks & Regards,
Shashi Kanth.K
9052671936
5 years, 7 months
[MM3-users] Re: Cron error
by Mark Sapiro
On 10/25/20 6:14 AM, Gordon Dickens wrote:
> Hi Mark, and other helpful souls,
> This cron error continues to occur at 12AM several times each week
> but not each day
> .Here is the output from the error message that is sent to the mailman3
> admin:
>
> Traceback (most recent call last):
> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 216, in lo
> ck
> os.link(self._claimfile, self._lockfile)
> FileExistsError: [Errno 17] File exists: '/var/lib/mailman3/locks/dbcreate.lck|s
> lc.mailhub4u.com|19728|1804933663424130229' -> '/var/lib/mailman3/locks/dbcreate
> .lck'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/usr/bin/mailman", line 11, in <module>
> load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')()
> File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
> return self.main(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/click/core.py", line 716, in main
> with self.make_context(prog_name, args, **extra) as ctx:
> File "/usr/lib/python3/dist-packages/click/core.py", line 641, in make_context
> self.parse_args(ctx, args)
> File "/usr/lib/python3/dist-packages/click/core.py", line 1089, in parse_args
> rest = Command.parse_args(self, ctx, args)
> File "/usr/lib/python3/dist-packages/click/core.py", line 940, in parse_args
> value, args = param.handle_parse_result(ctx, opts, args)
> File "/usr/lib/python3/dist-packages/click/core.py", line 1477, in handle_pars
> e_result
> self.callback, ctx, self, value)
> File "/usr/lib/python3/dist-packages/click/core.py", line 96, in invoke_param_
> callback
> return callback(ctx, param, value)
> File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in init
> ialize_config
> initialize(value)
> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 218, in
> initialize
> initialize_2(propagate_logs=propagate_logs)
> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 177, in
> initialize_2
> config.db = getUtility(IDatabaseFactory, utility_name).create()
> File "/usr/lib/python3/dist-packages/mailman/database/factory.py", line 50, in
> create
> with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')):
> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 334, in __
> enter__
> self.lock()
> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 248, in lo
> ck
> elif self._read() == self._claimfile:
> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 442, in _r
> ead
> with open(self._lockfile) as fp:
> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate
> .lck'
>
> Then, the contents of the /var/lib/mailman3/locks directory is as
> follows:
>
> -rw-rw---- 1 list list 80 Oct 25 00:00
> 'dbcreate.lck|slc.mailhub4u.com|19728|1804933663424130229'
> -rw-rw---- 2 list list 78 Oct 26 2020 master.lck
> -rw-rw---- 2 list list 78 Oct 26 2020
> 'master.lck|slc.mailhub4u.com|25024|3254783301248355113'
>
> I have since removed the file
> 'dbcreate.lck|slc.mailhub4u.com|19728|1804933663424130229'.
> .
> Also, I had previously changed the permissions on the
> /var/lib/mailman3/locks directory to give universal read/write
> permissions::
>
> drwxrwxrwx 2 list list 4096 Oct 25 08:11 locks
>
> Also, as user = list, I am able to create, edit and delete files in
> that directory which really doesn't make any sense because mailman3 is
> also running as user = list when it creates the Permission denied
> error.
> Does anybody have an idea as to what is going on here and how to fix
> it?
The FileExistsError is possibly due to some kind of race condition
between two `mailman` commands. Are you perhaps running both `mailman
digests --periodic` and `mailman notify` via cron at midnight each
night? If so, try running one if them a minute later.
The permissions error is on reading the lock file itself. I don't
understand what is causing that, but I doubt permissions on the locks
directory are involved.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
5 years, 7 months
[MM3-users] Re: Importing config and archives only partially succeeded?
by Eric Broens
Thanks for your prompt reply.To import the config and archives I ran the commands as outlined in Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation :
mailman import21 foo-list(a)example.com /path/to/mailman2/foo-list/config.pck
python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox
After running these commands the archives became available for most of the mailinglists. I didn't run the Django admin command with arguments "update_index_one_list" to build the indices for each mailinglist seperately.
After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage.
Best regards,Eric
On Sunday, December 13, 2020, 12:12:46 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote:
On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote:
> Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3.
> Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails.
> The imported members and other settings are correctly shown in the postorius page.
> Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails.
Did you specify --no-sync-mailman when you ran hyperkitty_import? If so
did you run the django sync_mailman job when you finished importing?
--
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, 5 months
[MM3-users] Re: Help with some 'withlist' configuration changes
by Mark Sapiro
On 6/23/21 6:30 AM, David Partain via Mailman-users wrote:
> Hi,
>
> Firstly, a repeat that I have a relatively broken (and soon to be fixed, I hope) installation of mailman3 based on Ubuntu 18.04 distrib packages (3.1.1-9) that stumbles along by me dealing with a bunch of things by hand that I hope'll go away once I'm up to the current version.
>
> In this set-up, I get a fair number of items shunted. Since I have this wonky version where stuff isn't always exposed in the web interface, I have to fix these things by hand. An example is that something gets shunted because of too many recipients, where I do:
>
> sudo -u list mailman withlist somemailmanlist
> m.max_num_recipients = 0
> commit()
> sudo -u list mailman unshunt
>
> I've managed to find a number of these, such as m.max_message_size, m.require_explicit_destination, and m.administrivia.
There is some other issue here as these things should only cause a
message to be held, not shunted. Some exception is being thrown in the
process of holding the messgage, and thaty is the real issue. What are
the tracebacks in Mailman's mailman.log for these shunts?
> My questions are undoubtedly foolish, but here goes:
>
> 1. Is there any way to print the entire 'm' structure? If so, I'd perhaps be able to figure out the answers to my other questions.
dir(m)
or maybe you want
>>> for x in dir(m):
... if not x.startswith('_'):
... print(f'{x}: {m.__getattribute__(x)}')
...
> 2. Is there a way for me to correct the following shunt-ing issues with 'withlist'? I've been unable to figure out how...
>
> a. 'moderation_reasons': [ 'Message has no subject'] / 'rule_hits': ['no-subject']
>
> b. Some things get caught as 'rule_hits': ['nonmember-moderation']. However, if I look in the (web-based) config, it shows that non-members should be accepted but the messages are shunted nonetheless. I don't know what to look for in 'm' or how I might clear these messages.
As I note above, these things are reasons to hold the message. The
shunting occurs because something is going wrong in the holding process.
Find the errors and tracebacks in Mailman's mailman.log to see what the
real issue might be.
> 3. I have no idea what these are telling me to do about digest messages. Suggestions? This is the entire info I get from 'mailman qfile':
>
> ------------------------------------------------------snip snip----------------------------------------------
> [----- start pickle -----]
> <----- start object 1 ----->
>
> <----- start object 2 ----->
> { '_parsemsg': False,
> 'digest_number': 457,
> 'digest_path': '/var/lib/mailman3/lists/somelist/digest.31.457.mmdf',
> 'lang': 'en',
> 'listid': 'somelistid',
> 'version': 3,
> 'volume': 31,
> 'whichq': 'digest'}
> [----- end pickle -----]
> ------------------------------------------------------snip snip----------------------------------------------
That is telling you there was in issue in sending the digest, the
mailbox for which is
/var/lib/mailman3/lists/somelist/digest.31.457.mmdf. Unshunting that
will retry sending that digest.
> 4. I have some that have 'rule_hits': [] (it's empty) but are shunted nonetheless. I can't see anything weird other than one of the messages has a utf-8 subject. Any ideas?
>
> 5. Some messages that were sent to -request addresses (e.g., subscribe messages, confirm, approve messages) are being shunted. What should I do with these?
You need to find the errors in the log and figure out what the
underlying issue is. I'm guessing it's a permissions issue, possibly
because of having at one time rum `mailman start` as root causing files
to be created and owned by root and not be readable/writable by the
Mailman user.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
4 years, 11 months
[MM3-users] Re: Mailman REST API not available. Please start Mailman core.
by Christian
I followed instructions provided here. Well, I rebooted the server and I'm
getting the same error again at the web page of
"Mailman REST API not available. Please start Mailman core."
I again found locks in /opt/mailman/mm/var/locks . Once I removed them I
could start mailman.
Perhaps I made a boo boo. I want mailman to start without locks upon reboot.
Help! (thanks)
-----Original Message-----
From: Mark Sapiro <mark(a)msapiro.net>
Sent: Wednesday, February 12, 2025 1:12 PM
To: mailman-users(a)mailman3.org
Subject: [MM3-users] Re: Mailman REST API not available. Please start
Mailman core.
On 2/12/25 12:05, Christian via Mailman-users wrote:
> That worked.
>
> Now on
> https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-m
> ailman
> -automatically it says
>
> "Pay attention to the config file output above and make sure that you
> see /etc/mailman3/mailman.cfg there. If the config path is different,
> you should make sure to create a new config file at
> /etc/mailman3/mailman.cfg and re-run the command."
>
> Well...mailman info yields
>
> GNU Mailman 3.3.5 (Tom Sawyer)
> Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file:
> /opt/mailman/mm/mailman.cfg db url:
> postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman
> devmode: DISABLED
> REST root url: http://localhost:8001/3.1/ REST credentials:
> restadmin:restpass
>
> Should I create a new config file at /etc/mailman3/mailman.cfg ?
You can, but the easiest thing is just replace the line
Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg"
in /etc/systemd/system/mailman3.service with
Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg"
--
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/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/
NYAIOPZ3PLQCPT3QPLLRKMOUY52UORBM/
This message sent to csa(a)web-analysts.net
1 year, 3 months