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

[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

10 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

8 months, 1 week

[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, 1 month

[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

5 years, 7 months

[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

5 years, 7 months

[MM3-users] Re: Database Schema - v3.2.1 to v3.3.3

by Mark Sapiro

On 4/4/23 21:28, Dave Hall via Mailman-users wrote: > Hello. > > Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external > MySql databases for Mailman3 and Mailman3-web. I am in the process of > migrating to v3.3.3. It would be easiest to perform this upgrade one > server at a time, but this would mean that for a short time I would have > v3.2.1 and v3.3.3 using the same databases. > > I am wondering if there are any MySql schema differences between the two > versions. If there are, having the two different versions 'cohabitating' > won't work.. As far as the Mailman3 database is concerned there are at least 3 migrations between 3.2.1 and 3.3.3 in mailman/database/alembic/versions. Namely: 2d2d0ef0828f_add_tag_column.py, 83339e4039da_add_usenet_watermark.py and d151c0b8d6f7_bounce_parameters.py. As far as Mailman3-web is concerned, this is presumably a Debian/Ubuntu Mailman3-web package upgrade. There may be migrations in django_mailman3/migrations/, hyperkitty/migrations/ and postorius/migrations/ that affect this depending on what the specific version updates are in that upgrade. In any case, there are schema differences for Mailman core between 3.2.1 and 3.3.3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Hyperkitty on Debian 12

by Mark Sapiro

On 3/26/24 00:06, Markus Grandpré wrote: > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... This warning is harmless, but to eliminate it set ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your django settings. > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available Probably Debian creates the `list` user without a login shell. ``` sudo -i -u list ``` may work. If not, you can always prefix commands with `sudo -u list ` as in ``` sudo -u list mailman-web hyperkitty_import \ -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ /var/mailman21/testlist.mbox ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 9/11/24 15:21, Dan Caballero wrote: > Mark, > > Do you have any tips for scripting the setting changes via mailman shell -l somelist(a)caltech.edu or a python script to run. eg. mailman shell -r dmarcsettings.py? > > We have a number of lists that email Gmail addresses either directly or via aliases and virtual email domains using Google Workspace. If your Mailman version is >=3.3.9 you can add `^.*(a)gmail\.com` to each list's `dmarc_addresses` to apply `dmarc_mitigate_action` to any mail From: a `(a)gmail.com` address. A `mailman shell` interaction to do that and set `dmarc_mitigate_action` to munge_from for all lists is like ``` $ /opt/mailman/mm/bin/mailman shell 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. >>> for mlist in getUtility(IListManager): ... mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') ... mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from ... >>> commit() ``` If your Mailman is older than 3.3.9 or you don't want to use dmarc_addresses, replace the line ``` ... m mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') with ... mlist.dmarc_mitigate_unconditionally = True ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Mailmansuite.log Entries

by Mark Sapiro

On 12/1/20 5:16 PM, Brian Carpenter wrote: > I see the following log entries in mailmansuite.log: > > INFO 2020-11-28 00:00:52,242 29142 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-28 00:01:00,600 29142 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-11-29 00:00:52,135 15513 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-29 00:01:00,192 15513 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-11-30 00:00:52,484 22622 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-30 00:01:00,758 22622 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-12-01 00:00:50,246 11946 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-12-01 00:00:59,688 11946 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > > I assume this is a result of importing archives from a MM2 mbox file. > This happen months ago however. Why are these entries still showing up? Those come from the HyperKitty sync_mailman job which is run by hyperkitty_import if you don't specify --no-sync-mailman, but is also one of the Django daily jobs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: postfix malformed address with confirm replies

by Mark Sapiro

On 2/28/21 1:07 PM, Stephen Mats Mats wrote: > > > To be clear the 'obstructive server’ is mailman-core. :) > > [ec2-user@ip-172-31-18-xxx ~]$ telnet 172.19.199.2 8024 > Trying 172.19.199.2... > Connected to 172.19.199.2. > Escape character is '^]'. > 220 mailman-core GNU Mailman LMTP runner 2.0 > LHLO ip-172-31-18-xxx.us-west-2.compute.internal > 250-mailman-core > 250-SIZE 33554432 > 250-8BITMIME > 250 HELP > MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> > 250 OK > RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu> > 553 5.1.3 Error: malformed address > RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55(a)mm3.aca-aws.s.uw.edu> > 250 OK > quit > 221 Bye Thanks for the info. I'll investigate further. It looks as though the LMTP runner (server actually) is responding with the 553 and then the sending MTA is retrying with a truncated local part, but of course that doesn't work because the token won't be found. I will look at trying to convince Mailman's LMTP to accept the longer local part or barring that to get the confirm command to accept the truncated token. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Search results for query "sapiro"