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

[MM3-users] Re: Question to add "alias" address in list by group

by Mark Sapiro

On 4/28/22 08:43, Pierre Malard via Mailman-users wrote: > > These are authorized alternate email addresses. For example A@domain is subscribed to the Z list of which only members can contribute but we also want to authorize some other address of A (A@domain2, …) as an « alternative" email contributor. > In the Mailman2 version this was called "accept_these_nonmembers" and it actually got added to that "non-members" list in mailman3. There is still an accept_these_nonmembers list in MM 3, but it is intended to support only regexps. For individual addresses, the preferred method is to create a nonmember record and set it's moderation action to default processing. The current import21 will import *_these_nonmembers in this way. I.e., import regexps into *_these_nonmembers and create nonmembers with appropriate moderation action for non-regexp addresses. However, the better method for your use case is for A@domain to add A@domain2, … as additional addresses. This can be done by the user via the web UI or via REST https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: About the link destination of the logo image of the homepage

by Mark Sapiro

On 09/29/2018 09:06 AM, Ooyama Yosiyuki wrote: > At next page: > https://www.gnu.org/software/mailman/ > > Despite the fact that "Mailman" is written in the logo on the upper left of the screen, > However if I click the logo image on the upper left of the screen,then it is to move to https://www.gnu.org/software/ > > I think it is strange. Yes it is strange, but it is an artifact of the fact that the same page is used at all of <http://www.list.org/>, <https://www.gnu.org/software/mailman/>, <http://www.list.org/>, <http://mailman.sourceforge.net/> and <http://mirror.list.org/>, and only the www.gnu.org site has extra pieces in the path to the home page. However, it can be fixed and I've done so. Thanks for the report. > In the Wikipedia English version, the following address is introduced as mailman's website. > www.gnu.org/software/mailman/ It probably should be <http://www.list.org/>, but that's up to wikipedia. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Where to find disabled members?

by Mark Sapiro

On 11/4/24 19:28, Bill Oliver wrote: > > a) See who is disabled, and > b) un-disable them by hand > > or... do I just have to wait seven days for them to automatically get > un-disabled? They do not get automatically re-enabled ever the user or you has to manually re-enable delivery. For an individual user, in Postorius you can click the user in the members list and see their delivery status and reset it. To deal with the whole list membership for a list, you can do ``` $ shell -l list(a)example.com 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 list(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` If you just want to list them ``` >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: disabled users

by Mark Sapiro

On 10/25/23 11:58 PM, Servizio Informatico U.I.C.I. Sezione territoriale di Brescia wrote: > Hello, > > Thank you for your answers. The problem is: > > I have a lot of user disabled for too many bounces. These users have the > same provider that, probably, has some limits of number of mail that can > be delivered from the same server. This causes timeout connections and, > mailman creates correctly a bounce. Timeouts and other types of throttling should be retried and not result in a permanent failure until the retries fail for days. > So I would like to discover a way to reset bounce limits so they can be > re enabled to receive. I tried also to unsubscribe and resubscribe users > but it does not change anything. Unsubscribing and resubscribing a user creates a new subscription with delivery enabled and bounce score of zero, but this is not necessary. As Steve pointed out in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you can re-enable delivery for a user by clicking the address in the membership list and then setting Delivery status to enabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/30/24 17:54, Mark wrote: > > In the new installation, are the template.uri (in the mailman DB) > records written as http://localhost:8000/... ? No. In both the installation that worked and the one that didn't, they were https://msapiro.net/..., but I don't think it would have mattered. When I reinstalled, I kept the same database, I only rebuilt the venv. As I have said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, this is all strange. My logs from the failure show the web server getting the request and serving the template with a 200 status and then after 5 seconds which is the specified timeout a requests.exceptions.ReadTimeout error is logged in mailman.log. The exact same code is executed whether by a rest runner gunicorn worker or via some other Mailman core runner, but only the rest runner fails. Further, a reinstalled venv on the failing server has no error, and another server which has a venv identical to the failing one except for Python micro version also has no error. I can't begin to understand what the underlying cause might be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try > using --force > mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/6/25 14:40, via Mailman-users wrote: >> Is your login a member of the list? > > It's supposed to be – when I click „Manage subscription” in the very same thread, it reveals that I'm subscribed. This is why I can't subscribe again. Yet I still can't post from HyperKitty, however I can by e-mail. > > However, when I checked the member list, I also found my address as a „nonmember” (besides being listed as „member” too). I removed myself as „nonmember”, but I still can't post to the list from HyperKitty. What response do you get when you click `reply` on a message? and what when you click `Start a new thread`. Do you get an error immediately or do you get a composition dialog and only get an error when you click `Send`. What do the errors look like? What do you see in Django's logs when you do this? What HyperKitty version is this and is it installed from PyPI or is it a downstream package? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: migration from 2.1 - owners and moderators

by Mark Sapiro

On 10/23/20 5:31 PM, Alex Schuilenburg via Mailman-users wrote: > > Most of the lists migrated so far don't have moderators, just owners. > However, when these lists have messages requiring moderation, the owners > dont get notified of held messages - unlike 2.1 where they did. Is this > a change or is there something I am missing in the configuration? As Brian said, owners as well as moderators should be notified. These notices are sent immediately if admin_immed_notify is True. If not, only periodic notices are sent. This needs to be run by cron. > I have the minute/quarterly/hourly etc cron jobs running, although I > have had to tune down the frequency of minute to hourly as it takes 6.5 > minutes to run* - but I doubt this is the cause. Those are Django tasks and don't affect this. You also need to run `mailman digests --periodic` to send periodic digests (see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>) and `mailman notify` to send periodic moderator notices (see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Postorius & multi domain

by Mark Sapiro

On 4/22/20 8:14 AM, Gelpi Andrea wrote: > > I search internet for a while and I discovered that using > FILTER_VHOST = True > seems to solve the problem. > >>From posotrius config page: > > FILTER_VHOST > Filter the list of available lists in Postorius and Hyperkitty > depending on the domain they are being currently served from. Mailman 3 > supports multiple domains in a single installation. > > But it doesn't work. I got err 500 form apache. FILTER_VHOST is currently broken unless each domain has the same value for the web and email domains. See the thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > Were can I find an explanation or a how to configure the system to have > 2 webserver with different domains working on the some server as it was > with mailman 2? If each domain has the same value for the web and email hosts, FILTER_VHOST will work. Currently though if you have domains like web host = lists.example.com and email host = example.com, FILTER_VHOST is broken. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Sapiro

On 5/8/20 2:11 PM, Mark Dadgar wrote: > > The easy fix was to edit the [mta] setting in mailman.cfg to deliver email via the submit port instead, which has no filtering applied to it: > > smtp_host: localhost > # using the submit port bypasses spamassassin filtering on outgoing list email > smtp_port: 587 > smtp_user: mm3send <— I created this user for this purpose > smtp_pass: <password-for-mm3send-user> > > This works great and can be applied to any email filtering. We tend to do this differently. For example, on mail.python.org which currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends about 135,000 individual messages per day from the two Mailman instances, we define in /etc/postfix/master.cf 127.0.0.1:8026 inet n - - - - smtpd -o smtpd_authorized_xforward_hosts=127.0.0.0/8 -o mynetworks=127.0.0.0/8 -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_data_restrictions= -o receive_override_options=no_unknown_recipient_checks -o smtpd_milters=inet:127.0.0.1:8891 Then port 8026 only accepts locally generated mail and only does dkim signing (milter on port 8891) and essentially no other checks. Then in the [mta] section in mailman.cfg we only need smtp_port: 8026 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Search results for query "sapiro"