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

[MM3-users] Re: Spam sent to list owner causes bounce increment for list owner

by Allan Hansen

Hi Mark, Thank you for the explanation, and it all makes sense. I prefer your verp_probes solution, as I do prefer to have my list work concentrated in one place. I did have 5 bounces on the list - I guess a lot of spam is happening due to the holidays. I noticed a big uptick myself. Thanks again, Allan > On Dec 18, 2023, at 10:30, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 12/18/23 9:59 AM, Allan Hansen wrote: >> Hi all, >> Someone sent a spam message to the list owner (me) of one of my lists. Then I got booted from the list. >> The scenario in more detail: >> The list server forwards the message to me, as I’m the list owner. This message is sent from <list>-bounces+hansen=rc.org(a)list.rc.org to hansen(a)rc.org. >> My service provider’s spam filter rejects the spam (correctly) in a message and informs the list server. >> The list server sends a message to <list>-bounces+hansen=rc.org(a)list.rc.org (the fake sender) saying that the message to hansen(a)rc.org (the recipient) could not be delivered because it was spam. >> The list server also blames hansen(a)rc.org (me) for the bounce and increments my bounce score, which, to me, is unfair. >> So I wonder: >> Is the Mailman host at list.rc.org at fault for not catching the spam before it reaches the list server? (One could argue that) > > Depends on what kind of spam filtering if any you have on incoming mail to list.rc.org. > >> Is my rc.org service provider at fault for sending the bounce message to the server instead of the to the original sender? > > Absolutely not. The envelope sender of the mail was set by Mailman to <list>-bounces+hansen=rc.org(a)list.rc.org in order to enable automated bounce processing. rc.org correctly sent the bounce to the envelope sender. > >> Is Mailman at fault for thinking that the bounce message was caused by a list message FROM me, instead of a bounced message TO the list owner? > > Arguably, yes, but not based on FROM. FROM has nothing to do with it. The message was sent TO you so if it bounces, it is a message to you that bounced, so you are the one bouncing this message. All Mailman knows is a message was sent to you and it bounced so it's your address that is bouncing. It doesn't matter whether this was a post to the list that bounced or a message to <list>-owner. A bounce is a bounce. > > Note that this list's bounce processing is very aggressive. If you got removed from the list after one bounce, the list must have Bounce score threshold = 1 and Bounce disable warnings = 0. You might consider adjusting these. > > There is an easy fix for this. Set `verp_probes: yes` in mailman.cfg. Then when your bounce score reaches threshold, instead of disabling/removing you, Mailman will send a probe message to you. It will only disable/remove you if the probe bounces which it presumably won't. > > Another avoidance would be to use an address for the owner which is not the address of a member. Then if the owner address bounces, nothing is done because the bouncing address isn't a list member. > > -- > 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 hansen(a)rc.org

2 years, 9 months

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Sunday, November 5, 2017 12:09:53 PM EST Mark Sapiro wrote: > When you run > > mailman info > > it will report among other things the location of 'config file:'. The > user who owns this file is the user that should run the > > mailman digests --send > > command. I.e., it should be in that user's crontab or in something like > '/etc/cron.d/mailman' with that user specified. > > Also see <https://gitlab.com/mailman/mailman/issues/436>. /etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, my laptop, and my new Mailman box. ALL files in /etc (except links, which are lrwxrwxrwx and I didn't check what they point to) are owned by root.root or owned by root.<other> and not group writable, except one, the directory /etc/ mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are you saying that Mailman should be able to change its own config file? Pierre -- Don't buy a French car in Holland. It may be a citroen.

8 years, 11 months

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

by Odhiambo Washington

On Thu, Dec 26, 2024 at 7:24 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/25/24 15:02, Odhiambo Washington via Mailman-users wrote: > > > > (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 > > > Then it appears that your version of mailman/commands/cli_members is > broken. Compare it to > > https://gitlab.com/mailman/mailman/-/raw/master/src/mailman/commands/cli_me… That's right. This one does what is expected. -- 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, 9 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 25, 2017 7:53:39 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/25/2017 01:08 PM, Fabian A. Santiago wrote: >> Hello, >> >> I have mm3 up and running via docker (courtesy of >maxking/docker-mailman) but when i send an email to my test list, it >bounces back claiming user unknown. it states: >> >> <"lmtp:[172.19.199.2]:8024"@>: unknown user: >> "lmtp:[172.19.199.2]:8024" >> >> looking at the email source, it seems as though the message is trying >to be delivered to: >> >> Final-Recipient: rfc822; "lmtp:[172.19.199.2]:8024"@<my email >server's FQDN> >> Original-Recipient: rfc822;test123@<my list's email domain> >> >> all of various alias transport maps are defined in postfix's main.cf. >not sure where to go from here. does anyone have any clues? > > >For the docker image, the tables have to be defined in Postfix as >regexp: tables. Are they? Yes they are. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 11 months

[MM3-users] Re: Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 18/2/21 11:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I want to contribute making it via Weblate, since it is already done > via gitlab repository (thanks to Mark Sapiro for approving the merge > requests), making a revision and editing them if needed, but I cannot > see how to make it in a consistent way, as I cannot determine how to > edit each template in the Weblate UI. I've tried to access via the > file name (accessing via msgid as for your example) of the > template... but I cannot access them by this way, or I'm missing > something. >> >> Can you, please, point me in the right direction on how to do it? > > Forget this, I've just found how to do it. Selecting by "key/context" > and the name of the file seems to do the trick. Done. Now the Weblate translation of templates is consistent with the gitlab src repository.

5 years, 8 months

[MM3-users] Re: Hyperkitty

by Onyeibo

On Mon, 30 Jan 2023 14:43:54 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 13:17, Onyeibo wrote: > > > > The mails don't have that header. I suspect I may have to > > investigate SELinux. > > > I think it's unlikely a SELinux issue unless you mean it's an issue > writing the log, but if there are any entries at all in mailman.log, > that should be OK. > YES. There were entries in the log. They are good entries. There were no alarming entries. I was right. Selinux was preventing Python {name connect} to a mailman path. After resolving that, all Archives built/updated. Now I see entries in the log about receiving mails and archiving them. I also see the archived messages via Hyperkitty web interface. Super! However, I no longer receive my own message to the list. That was working before. The post arrives at the List and gets archived but I don't see it via my mail client -- looks like Mailman is now recieving but not posting back to the subscriber. Strange

3 years, 8 months

[MM3-users] Re: Remove old bounces in bouncedir

by Stephan Krinetzki

Mark Sapiro wrote: > On 3/10/22 00:31, Stephan Krinetzki wrote: > > Mark Sapiro wrote: > > If you are referring to messages in Mailman's bounces queue, if these > > are not processed and removed within 15 minutes of arrival, Mailman's > > bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > > > > The process it self is there > > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > > > > I don't understand what's happening. If the bounces runner is processing > it's queue, those .pck files should be processed and deleted. > Are there errors in /opt/mailman/var/logs/mailman? Nope. Only the daily info, that it runs. For today: Mar 14 03:15:34 2022 (21507) Task runner evicted 25336 expired pendings Mar 14 03:15:43 2022 (21507) Task runner deleted 3696 orphaned workflows Mar 14 03:16:09 2022 (21507) Task runner deleted 7965 orphaned requests Seems to be okay > If you examine (some of) those files with mailman qfile do you see > anything strange? Nope. Just regular Bounce Files. > Is there an ownership/permissions issue? Sometimes people run Mailman or > some Mailman command as root and things get owned by root and then > when Mailman is later run as mailman it can't delete or maybe even > read them. Nope: /opt/mailman/var/queue/bounces ls -altrh | head total 12G -rw-rw---- 1 mailman mailman 37K Jan 5 09:51 1641372708.3212914+fc901998d5e2ace166db31ace6d77081b0c7650c.pck -rw-rw---- 1 mailman mailman 42K Jan 5 09:52 1641372768.1659493+7afbcddc270547485732252874adcc27e04c9983.pck -rw-rw---- 1 mailman mailman 42K Jan 5 09:52 1641372768.2633681+73c527870449492689fd30502b73f455a191701e.pck -rw-rw---- 1 mailman mailman 7.7K Jan 5 09:58 1641373138.119037+2d5dd400e989db3303517b900d7f2b312d4cd7b5.pck -rw-rw---- 1 mailman mailman 7.7K Jan 5 09:58 1641373139.585048+ee824dec757735ef8bd8139ee0cd858cc7c92606.pck -rw-rw---- 1 mailman mailman 288K Jan 5 09:58 1641373139.846666+d75af26011eb1a8ef5673d9ee13c5425daec2bd4.pck -rw-rw---- 1 mailman mailman 288K Jan 5 09:59 1641373140.024808+be60d1d97590d77eaec46751524d1bfe7a2f9ee7.pck -rw-rw---- 1 mailman mailman 289K Jan 5 09:59 1641373140.8432257+678f545d176008a5483b8bc6747aebc2b84a7f4e.pck -rw-rw---- 1 mailman mailman 288K Jan 5 09:59 1641373141.505824+c253072ebeb3f07b2b455725ace225abdd621b22.pck As you can see, there are old messages (not 3 years old, but some months old) > > If you are referring to bounce messages in the message store > > (var/messages/), there have been issues with those not being removed, > > but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. > > Is the size of the /opt/mailman/var/messages directory very big? Nope, it's 1.9GB at the moment. I don't think that's big. Is there anyway to run the bounce runner manually and get the debug output of it?

4 years, 7 months

[MM3-users] Re: Another interesting error...

by Darren Smith

"It's in Mailman's database in the 'message' table." I can see the message table - is there a way to see where it is marked as "held"? All I'm seeing in that table is id, message_id, message_id_hash, and path. I'm wanting to be able to query for held messages for a given mailing list, as there are currently over 98,000 entries in the message table. -Darren On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 01:31 PM, Darren Smith wrote: > > So it appears that there was a message sent to one of our mailing lists > > that was put into the held message queue. However, when attempting to go > to > > the message to do the moderation, the web page returns and Error 500. > > > > Looking in the mailman log, I found this: > > > > Apr 23 14:21:02 2018 (17878) REST request handler error: > > Traceback (most recent call last): > > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line > 137, > > in run > > self.result = application(self.environ, self.start_response) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/database/transac > > tion.py", line 50, in wrapper > > rtn = function(*args, **kws) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/wsgiapp.py" > > , line 214, in __call__ > > return super().__call__(environ, start_response) > > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", > > line 227 , in __call__ > > responder(req, resp, **params) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 167, in on_get > > resource = self._make_collection(request) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/helpers.py" > > , line 159, in _make_collection > > for resource in collection] > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/helpers.py" > > , line 159, in <listcomp> > > for resource in collection] > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 157, in _resource_as_dict > > resource = self._make_resource(request.id) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 100, in _make_resource > > make_header(decode_header(resource['subject']))) > > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in > > make_he ader > > h.append(s, charset) > > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in > > append > > s = s.decode(input_charset, errors) > > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > > illegal multibyte sequence > > > > It LOOKS as if there might be a character in the email somewhere - > possibly > > in the subject or sender fields? - that is somehow unexpected. > > > It appears that the Subject: header is RFC 2047 encoded and there is an > encoded word with charset gb2312 that contains an invalid encoding. > > The message is apparently defective, but this kind of defect shouldn't > cause a 500 error. > > I can't tell for sure from the traceback if this is Postorius or some > other application accessing the REST api. Is it Postorius or something > else? > > > > I am attempting to find the held message - can someone point me where I > can > > go to see the message so that I can see what might be causing the > problem? > > > It's in Mailman's database in the 'message' table. > > -- > 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/ >

8 years, 5 months

[MM3-users] Re: Python 3.13 compatibility

by Thomas Krichel

Mark Sapiro writes > If you do that and it results in a working system, you can then patch > mailman/utilities/i18n.py as follows Thank you. This works, and I can successfully import a first list configuration. > However there are other incompatibilities between the released Mailman > versions and Python 3.13. Hmm https://docs.mailman3.org/en/latest/install/virtualenv.html states "3.13 is recommended as it is the latest version of Python with which Mailman is tested." > At the moment, until updated packages are > released, in a Python 3.13 environment it is best to install all of mailman, > django-mailman3, postorius, hyperkitty and mailman-web from the heads of the > gitlab branches. I would love to see a command line for that. When I go to the gitlab page, https://gitlab.com/mailman/, I see a bunch of project that don't immediately correspond to pip package names. I am sure this would help other folks using 3.13 as they have been recommended to do. Thanks and cheers! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22213th day.

6 months, 2 weeks

[MM3-users] Re: Archiver "prototype" and disabling archiving at all

by Torge Riedel

Am 24.03.19 um 16:49 schrieb Mark Sapiro: > On 3/24/19 5:40 AM, Torge Riedel wrote: >> in the settings of a mailing list I can choose two archivers: >> "Hyperkitty" and "prototype". What is this archive "prototype" and how >> can I disable/remove/deinstall it? And how can I disable archiving at >> all, so no archiver can be chosen in the settings. > > The prototype archiver stores messages individually in > var/archives/prototype/LIST_NAME/. > > You can disable the prototype archiver by putting > > [archiver.prototype] > enable: no > > in your mailman.cfg. To disable all archiving, just remove all the > [archiver.*] sections from your mailman.cfg or set them to 'enable: no' > > Hi Mark, thanks. This disabled the archivers, but there is still the "Archives" link on top of the page. Is it possible to remove it? Cause there is nothing to see there. I tried commenting "'hyperkitty'," in INSTALLED_APPS, but then I got a 500.

7 years, 6 months

Search results for query "sapiro"