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

[MM3-users] Re: Active archivers and archiving and thread question.

by Mark Sapiro

On 3/30/22 11:21, bob B via Mailman-users wrote: > Digging into the mailman3 world, and want to check my logic... > > We normally don't use archives, so I have "archive policy" set to "Do not archive this list" for our lists. However, the "archives" button is still there on the list info page, and if users go into it, they don't see anything, But they can click "start a new thread" which sends a message to the list, but since archiving is turned off, that message does not show up there. > Am I understanding that correctly? > > if I have "Active archivers" disabled, that hides that area from the users, correct? You need to have hyperkitty unchecked in Active archivers to prevent the Archive button from appearing on the info page. Archive policy = Do not archive this list will prevent HyperKitty from creating an archive for that list. If there is one at, e.g., https://example.com/archives/list/list@example.com/ you can delete it and Archive policy = Do not archive this list will keep it from being recreated. > Any reason why these are separated? why have an active archiver, if archiving is turned off -OR- archives are turned on, but no active archiver? They probably shouldn't be completely independent. If Archive policy = Do not archive this list, that should probably deactivate any Active archivers for the list, but arguably, one might want to temporarily stop archiving and then restart it without having to remember which archivers were active. At a minimum, setting Archive policy = Do not archive this list should probably remove the Archive button from the info page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Emails about moderation are sent to list owners, want them sent to moderators instead

by Mark Sapiro

On 7/2/22 1:56 AM, Elias Rudberg wrote: > Hello, > > This is about GNU Mailman 3.3.3 (Tom Sawyer). > > For each list there are both "owners" and "moderators". As I understand > it, the idea is that owners have the power to change configuration for > the list, while moderators have more limited power, they can only > moderate but not change configuration. Correct. > When an email is sent from a non-member to a list that requires > moderation in such a case, an email with subject like "[listname] post > from [sender] requires approval" is sent to the list owners. I would > like those emails to be sent to moderators instead. Such notices are actually sent to the LISTNAME-owner@... address, received by Mailman and resent to all the owners and moderators. Both owners and moderators should receive the message. > The reason why I want it to work that way is that list owners sometimes > want to delegate the work of moderating to the moderators. List owners > then want to keep the power to change list configuration, but they do > not want to be bothered by individual moderation emails. > > Is there a way to configure mailman3 to make it send moderation emails > to moderators instead of owners? As I said, the notices are sent to both owners and moderators. There is no simple configuration to change this. Change would require modifying mailman/handlers/owner_recipients.py or possibly defining a sub-class of mailman.pipelines.OwnerPipeline which overrides the _default_handlers method and arranging for that to be used. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/5/21 6:43 AM, marcus.granath(a)gmail.com wrote: > > So what I basically try do achieve is to have only the following addresses to be allowed to send announcements (e-mails) on the mailman3 list, and all others that are member of the mailman3 list will just receive the e-mails. The usual "announcements" are sent out as the "no-reply" address (that actually are not really part of the mailman3 list) ;-) > > no-reply(a)abc.com ("fake address" that actually are not really part of the mailing-list) > peter(a)abc.com > david(a)abc.com > marcus(a)abc.com > > How to achieve this kind of filter with mailman3? Header filters is not the way to do this. First set both "Default action to take when a non-member posts to thelist" and "Default action to take when a member posts to the list" to either Hold for moderation or Discard (no notification). Reject is not recommended because of backscatter from spam posts with spoofed From: addresses. Then ensure all members Moderation Action is set to None or List Default (two names for the same thing). Now, no one can post. To allow your set of users to post, you have choices. The easy way but not secure against spoofing is to set the Maderation Action for the three allowed members to List Default and toi create a non-member for no-reply(a)abc.com and set it's moderation action to List Default. The more secure way is to leave everyone moderated, set a moderator password for the list and post with an Approved: header or pseudo header. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/27/22 01:23, Odhiambo Washington wrote: > > I have actually deactivated mine, and life is still good with my MM3. > > And just so that my mind is in the clear, there are three ways of getting > the full MM3 functionality, viz: > 1. Mailman core, Django's cluster, and Gunicorn > 2. Mailman core, Django's cluster, and uWSGI > 3. Mailman core, Django's cluster, and mod_wsgi Yes, and possibly there are other WSGI interfaces, but offhand I don't know. > And something that has not been quite clear to me: What is the purpose of > Django's cluster in all this? django_q <https://django-q.readthedocs.io/en/latest/> is an app for Django that can process tasks asynchronously in the background so they don't block the foreground. qcluster manages those tasks. > I am asking because on my FreeBSD server, I usually see not less than 30 > PIDs for: > > /opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/django-admin > qcluster --pythonpath /opt/mailman/mm/ --settings settings (python3.9) > > And there is a time I found it having 240 PIDs. > Would there be a problem if I limit the number of workers to "8"? Some of those may be orphaned. On servers I manage, I regularly stop all mailman3 services to install updates and on one of these servers (only mail.python.org) where there are resource issues, when the services are stopped, there are still orphaned qcluster processes. I have this ``` #! /bin/bash if status qcluster | grep -q 'running' ; then echo qcluster is running exit fi ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill ``` to get rid of the orphans -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: GDPR - save subscriptions confirmation emails

by Mark Sapiro

On 06/03/2018 12:34 PM, contact(a)maadix.net wrote: > Thanks Selva for you answer. > > In my Mailman 3 installation there is no /var/log/mailman/subscribe Correct. Mailman 2.1 had a subscribe log. Mailman 3 does not. Many things are logged in the 'mailman' log, but subscription confirmations are not. > I have logs about confirmations emails in > mailman/var/logs/smtp.log > > the format is the following: > > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO > mails.example.com' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL > FROM:<contact(a)maadix.net>' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: > contact(a)example.net > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT > TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: > prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' > > So, one solution that comes to my mind is to grep this log file. > > This is not a perfect solution and the full confirmation email is still > missing. > > I am not sure if this would be GDPR compliant. Also, while I don't think it is currently possible to confirm a subscription via REST, not to mention Postorius, it may be in the future and this would bypass email all together. I think the best thing is to implement logging. Of course, you might be able to get your MTA to save all mail to the LIST-confirm address to a separate mailbox in addition to delivering it to Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/26/19 12:17 PM, Alain Kohli wrote: > Thanks for the great explanation, that helped a lot! I'll try to work on > that issue if I find some time. In the meantime it would be neat to try > to clean up the old messages right before the backup. How can you > distinguish messages that have been moderated already? I couldn't really > find that in the database or the models. You could run the following in `mailman shell` $ /path/to/mailman shell Welcome to the GNU Mailman shell >>> lm = getUtility(IListManager) >>> ms = getUtility(IMessageStore) >>> for mlist in lm.mailing_lists: ... requestdb = IListRequests(mlist) ... for rq in requestdb.held_requests: ... key, msgdata = requestdb.get_request(rq.id) ... if msgdata['_request_type'] != 'held_message': ... continue ... msg = ms.get_message_by_id(key) ... print(msg['Message-ID-Hash']) ... U6QVO2GXMEQ5ZDQR2XCLDOH2FXPKJTWX 32HA6GKYE5FOVORLER7YAC3264BHG264 JM4NP3JRXBKKAL7UMM5XEXX644DQBAFJ L7FX6XKOOBP3YFFXUHA6EEJCQXX5BCHX DOJX55MRY6OYPZ4XFFTAQDD4I5MWJ3AD >>> What that prints is the names of all the files in the var/messages/ hierarchy which are currently held messages. Presumably the others are ones already handled. You could modify the above to write the list to a file and then wrap the whole thing in a shell script which would make the list and then do something like for f in `find var/messages -type f`;do n=`cut -d / -f5 <<<$f` for keep in `cat list` ;do k=0 if [ $n == $keep ] ;then k=1 break fi done if [ $k -eq 0 ]; then rm $f fi done in the above, list is the list of names to keep bade by the first script and -f5 in the cut command assumes the list from find is lines of the form var/messages/TJ/YF/TJYF5FETCRLOQZJ2H6Y4PMZP6M7GNLES. i.e. two subdirectories between messages/ and the file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 9/16/22 10:49, Dan Caballero wrote: > > We're seeing some messages having the .bak files in the out queue for up to 30, 40 or even 60 minutes. I've increased the number of in and out runners to 8 each. Is there a way to know which runner has which message? If the .bak files eventually go away, this is because the message has a large number of recipients and delivery to the MTA is slow. For the out runner, look in Mailman's smtp.log for messages of the form: <message-id> smtp to <list> for nn recips, completed in tt.ttt seconds to see how long it's taking. If it seems too long (even with full VERP, it should be at least 5 to 10 recips per second), there are things you can do in the MTA to speed processing. In particular, don't do recipient validation at incoming smtp time - possibly configure an alternate submission port for Mailman to use. It shouldn't be necessary to slice the in runner and it processes very quickly. To answer your question, queue entries have a name of the form <timestamp>+<hex hash> with a .pck or .bak extension. The entry is assigned to a particular runner based on the first bits of the hash. For 8 slices this is the first 3 bits of the hash, so if the first hex digit of the hash is 0 or 1, that out queue entry will be processed by the out:0:8 runner; if it's 2 or 3, that out queue entry will be processed by the out:1:8 runner and so on through e or f processed by the out:7:8 runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Mailman 3 database restore unexpected behavior

by Mark Sapiro

On 3/28/23 04:00, Tibor Molnar wrote: > Mailman3 built from source using virtual environment. > Version: > GNU Mailman 3.3.8 (Tom Sawyer) > Python 3.9.2 (default, Feb 28 2021, 17:03:44) > [GCC 10.2.1 20210110] > config file: /etc/mailman3/mailman.cfg > > Issue: > I have restored the database number of times recently and experienced that every time after restoration (an hour after) all members getting an email that they are unsubscribed due to bounces, however non of the users are actually unsubscribed from any lists. It looks like there are duplicates in database and all the duplicates are getting unsubscribed? > > Bounces message: > name(a)email.com unsubscribed from [listname] mailing list due to bounces That's an admin notice, not a notice to the user. > Only restoring two files: mailman3 and mailman3web > > Did anyone come acroos this behavior ? This seems sort of like <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, but it doesn't seem like that would be the issue here. > It is not right that after restoring a database all 1000 user get an email that they are unsubscribed, but they are actually not. > I may do something wrong during the restoring process. > Please advise me. The code that decides which users are to be removed is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p…> Somehow you must be restoring members whose delivery status is disabled by bounce and whose total_warnings_sent is >= the list's bounce_you_are_disabled_warnings. What do you get from this query on the mailman3 database SELECT email FROM member JOIN address ON address_id = address.id JOIN preferences ON member.preferences_id = preferences.id WHERE delivery_status = 3 AND total_warnings_sent > 0; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Hi Mark, As you have mentioned about implementation of "Auto discard after max_days_to_hold" in a next release. How do I install that release? I have installed mailman3 using pip in virtual environment and whenever I try to upgrade the release using pip install -U, it gives package already compiled and up to date. My Mailman version is as follows. Mailman version: GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.9 Rocky Linux 9.5 Regards, Hitachi. On Thu, May 1, 2025 at 12:51 PM Hitashi mancho <huhamails(a)gmail.com> wrote: > Thank you so much, Mark and Stephen, for the quick action and response. > Waiting for the next release. > > On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 4/28/25 10:55, Mark Sapiro wrote: >> > >> > `mailman import21` will import the setting, but per the above comment, >> > it doesn't yet work. The setting exists and is exposed in REST, but it >> > appears it is not actually implemented. >> >> >> This is now implemented for the next release. See >> https://gitlab.com/mailman/mailman/-/issues/1215 and >> https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman >> core and https://gitlab.com/mailman/postorius/-/issues/628 and >> https://gitlab.com/mailman/postorius/-/merge_requests/1001 for 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/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to huhamails(a)gmail.com >> >

8 months, 3 weeks

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 6/10/19 6:21 PM, andrew.bernard(a)gmail.com wrote: > is there a tutorial or some examples for using the mailman shell? Is there detailed documentation on it? What documentation there is is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > Anything I try to do such as the following fails: > > $ mailman shell > Welcome to the GNU Mailman shell > >>>> command('mailman shell --details') > Traceback (most recent call last): > File "<console>", line 1, in <module> > NameError: name 'command' is not defined >>>> You could just do `mailman shell --details` at a command prompt. Perhaps you saw the `command('mailman shell --details')` line in the docs at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> in any case, that requires two things to precede it. The first is part of the doctest infrastructure and is not evident in the docs. that step is from mailman.testing.documentation import cli The second step is in the docs and is command = cli('mailman.commands.cli_withlist.shell') If you do those two steps within `mailman shell`, then the step command('mailman shell --details') will work, but as I said, this is just the same as doing `mailman shell --details` at a command prompt. Beyond that, actually doing stuff within `mailman shell` requires some knowledge of Mailman interfaces, methods and objects as well as Python. Some of this is covered throughout the documentation at <https://mailman.readthedocs.io/en/latest/> but some can only be found in the source code itself. That said, all the interfaces and a few other useful functions are imported for you in `mailman shell` interactive mode. do `dir()` to see what these are. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Search results for query "sapiro"