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

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hello, On Fri, Sep 30, 2022 at 08:53:38PM +0000, Andy Smith wrote: > On Fri, Sep 30, 2022 at 01:16:10PM -0700, Mark Sapiro wrote: > > I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which > > was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this. > > So that probably answers that then. Hmm, I wonder about the best way > to proceed. The next stable release of Debian will have something > that calls itself 4.0-2 and looks like it is fixed there: > > https://salsa.debian.org/python-team/packages/flufl.bounce/-/blob/master/fl… It seems that this package version can be downloaded and installed in Debian stable (bullseye): https://packages.debian.org/bookworm/all/python3-flufl.bounce/download It isn't recommended to mix packages from different releases of course, but the changes seem quite minimal and it fixes the problem for me. Cheers, Andy

3 years, 4 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

> On Tue, 3 Jan 2023 09:46:00 -0800 > Mark Sapiro <mark(a)msapiro.net> wrote: > This is all configured in your web server. It needs to proxy requests > for lists.website.tld to gunicorn and depending on the web server, > may need more. E.g. see > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > for nginx. I have fixed this. > > Set SITE_ID = 0 in your Django settings. Also see > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > Actually "SITE_ID = 1" solved that instead. I also had to go into the database and update the values (django provided 'example.com' by default and that was problematic). Yaaay! The mailing-list is up and running. I am super grateful to the mailman support here in this list. Thank you so much Mark, Stephen J, and Eggert. I have more questions but I think it is better to start a new thread for that. Best regards Onyeibo

3 years

[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, 11 months

[MM3-users] Getting connection timed out

by Stephen J. Turnbull

blackout69 writes: > Il 23/05/21 01:21, Mark Sapiro ha scritto: > > Can you successfully telnet to port 25 on mail.simail.it from the > > Mailman server? > No > > If you can connect (via telnet) to port 25 on mail.simail.it from the > > Mailman server, then I'd suggest stopping and restarting Postfix. > > if i try from the mail server i get > > telnet mail.simail.it 25 > Trying 217.27.113.30... > telnet: Unable to connect to remote host: Connection timed out mail.simail.it is ignoring your mail server. This is not a Mailman problem. 1. Check to see if that server has a stated policy for "abusive" mail and some way of getting back in their good graces. 2. Check if your mail server is in the RBLs. Some of them are very aggressive about adding IPs and domains. 3. Try writing the postmaster at mail.simail.it. 4. Ask your subscriber(s) at mail.simail.it to write their postmaster. Steve

4 years, 8 months

[MM3-users] Re: File in /var/lib/mailman3/queue/bounces/

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [211212 05:41]: > On 12/11/21 6:29 PM, Andreas Barth wrote: > > > >in my local installation there is a file in > >/var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how > >to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in > >queue/bounces and now queue/shunt. > > > I suspect the issue is that bounce runner is not running. If you > grep Mailman's mailman.log for `bounces` I suspect you will see that > it has died and not restarted. You may or may not find additional > information in the log as to why it died, but in any case restarting > Mailman should start everything again. Thanks for your answer. Actually I didn't find anything in the log, but according to ps the bounce runner is actually not running. A restart of mailman fixed the issue for me. Andi

4 years, 2 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Ron / BCLUG

Mark Sapiro wrote on 2024-04-10 14:09: > I suspect you are not starting the services with your venv active. > What's in your mailman3.service and mailman3-web.service files? Thanks for the pointer! I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` somehow. I changed that to match the docs, did the `systemctl daemon-reload`, etc. but still had similar problems. I went through all my config files carefully, I wiped the static folder completely and rebuilt it, and I finally have the last piece of the puzzle in place and my web interface is working! I'm not sure which change actually fixed the issue though. (When looking at "Available lists" my header has "example.com" in the top-left corner?!?) Thank you! I think I need to backup what I have and do a clean re-install so I have a better grasp of what's going on with all these components. Mailman3 looks quite nice, gotta say! rb

1 year, 10 months

[MM3-users] Re: New domain cannot set set host

by Alain D D Williams

On Wed, Nov 27, 2024 at 12:42:41PM -0800, Mark Sapiro wrote: > On 11/27/24 12:18 PM, Alain D D Williams wrote: > > > > But it is not in table mailman3web.django_site > > > > Please how do I do this ? > > Add the domain as a site in the Django web admin UI. I did not see this y/day and created the entry in table django_site using SQL. This might be the cause of the other problems that we have been talking about. I must admit to finding django daunting -- something that I know nothing about; I ran "mailman-web --help" and was non the wiser. I found the following which did not help either: https://docs.mailman3.org/en/latest/django-primer.html -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 2 months

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

1 year, 1 month

[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, 4 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.

6 years

Search results for query "sapiro"