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

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Thu, Dec 26, 2024 at 1:27 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On December 25, 2024 2:01:27 PM PST, Odhiambo Washington via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > members --role nonmember LISTSPEC | wc -l > > 13 > > What do you get if you do > ``` > mailman shell -l LISTSPEC > ... > >>> len(list(m.nonmembers.members)) > (venv) mailman@eu:~$ mailman shell -l LISTSPEC Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LISTSPEC mailing list In [1]: len(list(m.nonmembers.members)) Out[1]: 873 In [2]: -- 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]

11 months, 2 weeks

[MM3-users] Re: new list not working

by Mark Sapiro

On 3/10/23 09:03, Christian via Mailman-users wrote: > > Again, that's only the post being delivered to Mailman. What comes after > that in the log? > > Mar 10 08:39:28 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Mar 10 08:39:28 2023 (1005) Peer: ('127.0.0.1', 55662) Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) handling connection Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'LHLO > zarathustra.ccalternatives.org' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'MAIL > FROM:<christian(a)naturalintelligence.us> SIZE=3498' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) sender: > christian(a)naturalintelligence.us Mar 10 08:39:28 2023 (1005) ('127.0.0.1', > 55662) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) recip: > redlatinleg(a)lists.ccalternatives.org > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'DATA' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) >> b'QUIT' > Mar 10 08:39:28 2023 (1005) ('127.0.0.1', 55662) connection lost Mar 10 > 08:39:28 2023 (1005) ('127.0.0.1', 55662) Connection lost during > _handle_client() Mar 10 08:44:05 2023 (1005) Available AUTH mechanisms: > LOGIN(builtin) PLAIN(builtin) Mar 10 08:44:05 2023 (1005) Peer: > ('127.0.0.1', 54800) Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) > handling connection Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> > b'LHLO zarathustra.ccalternatives.org' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'MAIL FROM:<> > SIZE=1139191' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) sender: <> Mar 10 08:44:05 > 2023 (1005) ('127.0.0.1', 54800) >> b'RCPT > TO:<medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org>' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) recip: > medialist-bounces+kkeys=courier-tribune.com(a)lists.ccalternatives.org > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'DATA' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) >> b'QUIT' > Mar 10 08:44:05 2023 (1005) ('127.0.0.1', 54800) connection lost Mar 10 > 08:44:05 2023 (1005) ('127.0.0.1', 54800) Connection lost during > _handle_client() Mar 10 08:45:15 2023 (1005) Available AUTH mechanisms: > LOGIN(builtin) PLAIN(builtin) Mar 10 08:45:15 2023 (1005) Peer: > ('127.0.0.1', 38820) Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) > handling connection Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> > b'LHLO zarathustra.ccalternatives.org' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'MAIL FROM:<> > SIZE=1155595' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) sender: <> Mar 10 08:45:15 > 2023 (1005) ('127.0.0.1', 38820) >> b'RCPT > TO:<medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org> > ' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) recip: > medialist-bounces+john.harbin=blueridgenow.com(a)lists.ccalternatives.org > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'DATA' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) >> b'QUIT' > Mar 10 08:45:15 2023 (1005) ('127.0.0.1', 38820) connection lost Mar 10 > 08:45:15 2023 (1005) ('127.0.0.1', 38820) Connection lost during > _handle_client() There are no messages from the out runner process. it isn't running or it's hung. > And have you checked if Mailman's out runner is running? Note that if it > died for some reason and wasn't restarted or used up its restarts, > restarting Mailman core won't start it. You need to stop Mailman core and > then start it. > > OK I DID THAT Did the mail start flowing? > Are there files in mailman's var/queue/out/ or var/queue/shunt/ directories? > > root@zarathustra:/opt/mailman/mm/var# ls -la queue/out total 4416 > drwxrwx--- 2 mailman mailman 4096 Mar 10 04:44 . > drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. > -rw-rw---- 1 mailman mailman 1126829 Mar 10 04:39 > 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak > -rw-rw---- 1 mailman mailman 1083682 Mar 8 20:00 > 1678334445.1113052+b43224b03f1ba2aa2610301331195b0cbaa151b7.pck > -rw-rw---- 1 mailman mailman 1083744 Mar 8 20:00 > 1678334445.1324928+10c5ec711b7a4364407685b7899a9e8ea25a1a8b.pck > -rw-rw---- 1 mailman mailman 1083680 Mar 8 20:00 > 1678334445.1501603+f2d2895ae7fa80ad387df77ffa17361294fe781c.pck > -rw-rw---- 1 mailman mailman 2922 Mar 9 07:49 > 1678376944.9032273+9923c3da8724cff6ff71b585d1971a90a0ae65cb.pck > -rw-rw---- 1 mailman mailman 2862 Mar 9 07:49 > 1678376944.9125621+2635b96fc6cd2ebb98a2c60a269d07517c1f5046.pck > -rw-rw---- 1 mailman mailman 2886 Mar 9 07:57 > 1678377458.4585488+73f68f6f05d6ee64020e05c8ba2569378e4238f0.pck > -rw-rw---- 1 mailman mailman 6600 Mar 9 07:59 > 1678377564.335885+63793d373c7668947ce4ef2c4a89644ba288d775.pck > -rw-rw---- 1 mailman mailman 8290 Mar 9 08:25 > 1678379122.8619912+bfba87ac1c5e97473ea9c9645a99719d11179308.pck > -rw-rw---- 1 mailman mailman 5966 Mar 9 08:48 > 1678380525.743866+d6f70271750015293a249f9ffae8200367eee509.pck > -rw-rw---- 1 mailman mailman 6124 Mar 9 13:01 > 1678395691.1910245+9e087862cd317d77af8586d5390d60d483af8123.pck > -rw-rw---- 1 mailman mailman 2789 Mar 9 13:31 > 1678397516.4386168+14bb385ad36166aef4a23e1d2b9dd92b50af254d.pck > -rw-rw---- 1 mailman mailman 2752 Mar 9 13:31 > 1678397516.4514658+00546161e5310c988ca3b4d0be4c4a96d3295969.pck > -rw-rw---- 1 mailman mailman 2321 Mar 9 13:58 > 1678399097.1614358+b7b3bfa9cdef9ada94045eed945862664aff065e.pck > -rw-rw---- 1 mailman mailman 2390 Mar 9 13:58 > 1678399097.172284+7188ab4729863b3781c0890ec3b1be7de642454a.pck > -rw-rw---- 1 mailman mailman 6031 Mar 9 14:07 > 1678399672.4968731+2caeb7c82672c9051be407b1cdb7a8b21a87d348.pck > -rw-rw---- 1 mailman mailman 2095 Mar 9 14:08 > 1678399689.8167183+199b2da6cd1f8a00d10c1cd79ccc6cbcb4bdd503.pck > -rw-rw---- 1 mailman mailman 7179 Mar 9 14:08 > 1678399689.8327854+a8d1dc73e5979bde43dccf48caa9bc58de575f41.pck > -rw-rw---- 1 mailman mailman 8357 Mar 9 14:19 > 1678400356.5360696+62b6dce2428e420d6cb53c337c61db69a6fe4d44.pck > -rw-rw---- 1 mailman mailman 5939 Mar 9 14:28 > 1678400903.3894706+d3f5dad6c67057edd0f2888e193dd71de14d2bf9.pck > -rw-rw---- 1 mailman mailman 2096 Mar 10 04:43 > 1678452191.4875023+2e00a89aa5454f965d35a7b8be6a4f620944b8a1.pck > -rw-rw---- 1 mailman mailman 7181 Mar 10 04:43 > 1678452191.4984088+1fd6f3aff9ef79aff269f4edc920f2424a8b35b7.pck > -rw-rw---- 1 mailman mailman 6036 Mar 10 04:44 > 1678452252.847286+552f758b7fca32c2f082bd922f68de1f850dec2d.pck Was this before or after you stopped and started Mailman core. If before, what is the situation now? Is mail being delivered? If after, is there still a 1678316345.5510073+678e72d483278a233b12cc38ebc3786fbfd50a44.bak file in que/out? If this file is still there, it is hanging the out runner. Stop Mailman, move this file aside and start Mailman and see if the rest of the messages are processed. If that fixes it, there is something in that one message causing this. You can examine it with `mailman qfile`. That message arrived at Wed Mar 8 14:59:05 2023 (1678316345.5510073 is a time stamp) and is apparently causing the problem. If moving it aside fixes things, you can send it to me off list and I will try to figure out what the issue is. > root@zarathustra:/opt/mailman/mm/var# ls -la queue/shunt total 12 > drwxrwx--- 2 mailman mailman 4096 Mar 8 12:07 . > drwxr-xr-x 14 mailman mailman 4096 Mar 8 12:07 .. > -rw-rw---- 1 mailman mailman 447 Apr 26 2021 > 1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck This is an old shunted message. The exception that caused it and a traceback were written to mailman.log on April 26 2021. If you still have that log, the exception and traceback will show what happened. In any case, `mailman qfile queue/shunt/1619433583.1513886+2626ca223f3fc4368f6cf90fecc1e0e50705c36a.pck` will show the msg and its metadata. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Help with fresh debian install

by Jonas Meurer

Mark Sapiro: > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> [...] >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. The Debian package uses user `list` for this. It also provides a command `mailman-wrapper` which takes care of running mailman commands as this user. It would be awesome if the upstream /usr/bin/mailman command could take care of this automatically, making the wrapper command obsolete. Cheers jonas

6 years, 2 months

[MM3-users] Re: Cron of Mailman notify is not working

by Shashikanth Komandoor

Thank you Mark Sapiro. I have tried as per your suggestion but failed unfortunately might be because of my improper setup. But I learnt one thing and fixed it and would like to share with you so that you may correct me if I am wrong or it would be useful for others. I observed that the "notify" subcommand can be run only while I am in the /var/lib/mailman/mailman directory where my mailman core is installed (through GITHUB). And moreover I installed all the components of the mailman using the root user only and so there is no mailman user on my machine. And hence I wrote the below entry in the crontab directly and found it is working fine. 00 08 * * * cd /var/lib/mailman/mailman; /var/lib/mailman/venv3/bin/python /var/lib/mailman/venv3/bin/mailman notify Please correct me if my analysis is wrong or please also suggest me if I could work it out in a more optimal manner.

5 years, 10 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Mark Sapiro: >> $ grep ^EMAIL settings.py >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 > > but is this perhaps overridden in a settings_local.py file? I don't have a local settings file. I cloned the suite from GitLab[1] master branch and modified the existing settings.py, based on Mailman's documentation. [1] https://gitlab.com/mailman/mailman-suite.git I just verified that EMAIL_BACKEND is not redefined anywhere: $ grep -r 'mail\.backends' . Binary file ./__pycache__/settings.cpython-38.pyc matches ./settings.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' ./settings.py:# EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' I commented out the "if DEBUG == True" lines, which explains match number three. As far as I can see, the mail backed definition for Django is as it should be. I could provide the differences between my settings.py and the Git HEAD version if you think that might help. -Ralph

5 years, 8 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/16/21 9:59 PM, Mark Dadgar wrote: >> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >> >> Error messages below. >> >> rebuild_index fails with the same error. >> >> This is with django version 3.0.12. > > > django.utils.six was removed in Django 3.0. See > <https://pypi.org/project/django-utils-six/> for a work around > replacement. I.e. in your venv do > > pip install django-utils-six OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. I really appreciate the support of this community in general and you in particular, Mark. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

[MM3-users] Re: CSV import for mass subscription

by Odhiambo Washington

On Fri, Sep 20, 2024 at 7:43 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/20/24 01:26, Markus Grandpré wrote: > > Dear list, > > > > we noticed that there is a function to convert the member list into a > > CSV format and save it.Therefore, we would like to know if the > > implementation of a CVS import for mass subscription is already planned? > > If not, how can we submit a corresponding feature request? > > The exported CSV is just a list of email addresses, and that could be > easily just pasted into the mass subscription form. > Why was it called a CSV? Appropriateness or future plans to download a true CSV? -- 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

[MM3-users] Re: Post log?

by Mark Dadgar

On May 5, 2020, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/5/20 5:28 PM, Mark Dadgar wrote: >> Is there the equivalent of the post log from mailman 2.x available? > > It's not a separate log as it was in Mailman 2.1, but the information is > in the smtp log. For example, here are a couple of entries relating to > your post to which I'm replying: > > May 06 00:29:15 2020 (27320) > <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> smtp to > mailman-users(a)mailman3.org for 238 recips, completed in > 39.014487743377686 seconds > May 06 00:29:15 2020 (27320) > <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> post to > mailman-users(a)mailman3.org from mark(a)pdc-racing.net, 4429 bytes Ahh. I saw a ton of entries of the first type but missed the entries of the second type (it was a big file), which were the ones I needed. Thanks for the pointer. The script is up and running nicely now. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 7 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 3:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/18/20 2:23 PM, Mark Dadgar wrote: >> >> There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. >> > ... >> Could this somehow be related to my recent migration from sqlite3 to postgres? > > I think it's quite likely that that migration is involved and your > database is now corrupted in some way. Exactly how or in what way, I > don't know, but it seems likely to me that that's the issue. Oh good. Any thoughts on how to salvage ~20 years of list archives? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: MTA authentication and smtpd_sender_login_maps

by Jan Eden

On 2022-11-25 11:44, Mark Sapiro wrote: > On 11/25/22 11:00, Jan Eden via Mailman-users wrote: > > > > I obviously do not want to add an entry to the map file for each mailing > > list created by someone on the server. Is there a way to > > programmatically create a sender login map with Mailman? > > > You could modify mailman/src/mailman/mta/postfix.py to create a > smtpd_sender_login_maps file with the desired content or you could create a > script that creates the file using data in the generated > var/data/postfix_lmtp. If the latter, you might be able to create a plugin <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do…> > to run the script whenever a list is created or deleted Thanks! I feel rather stupid, but the obvious and really simple solution is a wildcard entry for the SASL user in controlled_envelope_senders: @lists.domain.org mailman_sender(a)domain.org Sorry for realizing this *after* bothering you. - Jan

3 years

Search results for query "sapiro"