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

[MM3-users] Re: Custom Archiver

by Mark Sapiro

On 4/1/23 09:39, pknowles(a)tpnsolutions.com wrote: > I'm playing around with installing Mailman Core, and want to have messages on a "per-list" basis sent to a special "archiver" address which I intend to make archives available at via a custom built "read-only" IMAP client. > > How would I go about having messages sent to this external address, short of adding the address as a subscriber? See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/archiving/prot… for an example of an archiver that implements Mailman's IArchiver interface. You could make something similar with an archive_message() method that sends the message to your IMAP server, or possibly you could just implement your IMAP client to serve messages from the existing var/archives/prototype/ hierarchy. Messages for lists with the prototype archiver enabled are stored there in maildir format by list name. To enable the prototype archiver, you may need to put [archiver.prototype] enable: yes in your mailman.cfg. To make your own archiver, create a python module, say my_archive.py, that defines a My_Archive class implementing the IArchiver interface. Put that module somewhere where mailman can import it and put something like [archiver.my_archiver] class: import.path.my_archive.My_Archive enable: yes where import.path.my_archive.My_Archive is the actual path that is imported. For example if Mailman is installed in a venv, you could put my_archiver.py in the venv's site-packages directory and then the class would be just class: my_archive.My_Archive -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Mark Sapiro

On 1/16/23 07:58, jaboyib556--- via Mailman-users wrote: > > However, I saw reports of EMWD being a one-man show and the owner sadly passing away in 2021; but I've also seen threads here referring to the Affinity and Empathy projects in 2022. It wasn't clear to me if EMWD is still an active business and Affinity and Empathy are still active offerings. Does anyone here have any direct contact/relationship/experience with EMWD/Affinity/Empathy following the owner's passing? Or knowledge of any other offerings publicly available today that are similar to Affinity/Empathy? I have had some contact, but not much. As far as I know, they are still in business and offering list hosting including Mailman 3 lists with Affinity and Empathy. They no longer offer support for installation and maintenance of Mailman on other people's servers. When we first were developing Mailman 3, we designed it in a modular fashion with a REST API for the core engine so that users who were so inclined could develop their own web UIs for archiving and list management. We also recognized that we needed to develop our own to make a complete package. Thus, we developed HyperKitty and Postorius for that, but we have always hoped that the community would develop others (hopefully open source and Python based). As far as I know, it was only EMWD that did this and for business reasons, kept it proprietary. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: My django container keeps getting shutdown by oom-killer

by Mark Sapiro

On 11/12/25 17:10, Hirayama, Pat wrote: > > This always happens overnight, usually after midnight, though one time it was around 10:40. I don't see any crontab entries that correlate. And the after midnight issues don't always happen at the same time, so it seemed unlikely that it was a crontab job that was causing it > > I finally looked at the host (rather than the logs of each container) and realized that the oom-killer was killing django-admin. As a temporary workaround, I've limited memory on the mailman-django-uwsgi container to 4 GiB (though, since I just did that this morning, I won't know until after midnight (presumably) if it worked or not), and set the RestartPolicy to always. The above suggests it's one of the Django daily jobs that's hitting the OOM. These jobs are appname - jobname - when - help -------------------------------------------------------------------------------- django_extensions - cache_cleanup - daily - Cache (db) cleanup Job django_extensions - daily_cleanup - daily - Django Daily Cleanup Job hyperkitty - orphan_emails - daily - Reattach orphan emails hyperkitty - recent_threads_cache - daily - Refresh the recent threads cache hyperkitty - sync_mailman - daily - Sync user and list properties with Mailman I don't offhand know which of these might be a memory hog. Further, if one of these dies for out of memory, I don't see it affecting more than that job, not the entire service. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/17/23 9:42 AM, Mark Sapiro wrote: > On 12/17/23 9:10 AM, eboltz(a)lhtservices.com wrote: >> Mark, >> >> Here is my postconf -n >> >> alias_database = hash:/etc/aliases >> alias_maps = hash:/etc/aliases >> always_add_missing_headers = yes >> append_dot_mydomain = no >> biff = no >> compatibility_level = 2 >> default_destination_concurrency_limit = 15 >> default_destination_recipient_limit = 30 >> header_checks = regexp:/etc/postfix/header_checks >> header_size_limit = 409600 >> inet_interfaces = all >> inet_protocols = ipv4 >> local_recipient_maps = proxy:unix:passwd.byname $alias_maps >> hash:/var/lib/mailman3/data/postfix_lmtp >> mailbox_size_limit = 0 >> mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain >> myhostname = lists.example.com >> mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 >> myorigin = /etc/mailname >> readme_directory = no >> recipient_delimiter = + >> relay_domains = hash:/var/lib/mailman3/data/postfix_domains >> relayhost = [mail.smtp2go.com]:587 >> smtp_always_send_ehlo = yes >> smtp_sasl_security_options = noanonymous >> smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem >> smtp_tls_security_level = may >> smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache >> smtp_use_tls = yes >> smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) >> smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated >> defer_unauth_destination >> smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem >> smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key >> smtpd_tls_security_level = may >> transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp >> unknown_local_recipient_reject_code = 550 >> virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap > > > It looks like you are now following > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. > > >> What would I have to do to ensure that MM3 and postfix (same new >> server) use the newly created lists.example.org domain, which only >> exists within Postfix when setting up the Postorius domain and lists? >> I want to have it so that whatever the list name is, for example >> 'Staff(a)lists.example.org' will route through Postfix correctly. > > > Have you set an alias_domain for the lists.example.org domain? > > What are the contents of /var/lib/mailman3/data/postfix_vmap and > /var/lib/mailman3/data/postfix_lmtp? If you feel it is necessary to > anonymize the domains in these, please only change the tld so we can see > the actual subdomains. However, it looks like you don't need to follow <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> as lists.example.org is not a virtual_alias_domain. You just need to add lists.example.org to mydestination, assuming lists.example.org and lists.example.com are actually different domains, and follow <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/27/21 1:36 PM, William Oliver wrote: > > When I send a message to the list from *any* of these three, the > mailman3 accepts it and attempts to broadcast it out. It is delivered > sucessfully to the local email address, but it looks like there's a > relaying problem with external addresses. > > In the syslog snippet below, note that the fp145(a)libertyfp.org mail is > delivered, but the mail to the recipients at billoblog.com get an > "Access denied" ...> > Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: NOQUEUE: reject: RCPT > from mail.libertyfp.org[2.56.57.28]: 554 5.7.1 <billo(a)billoblog.com>: > Recipient address rejected: Access denied; > from=<testlist-bounces+billo=billoblog.com(a)libertyfp.org> > to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> > > Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: disconnect from > mail.libertyfp.org[2.56.57.28] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 > quit=1 commands=7/8 It appears that the MX for billoblog.com is not accepting mail from your server. Can you send non-mailman mail from this server to this address? If not, you need to contact billoblog.com to fin wht they are blocking your mail. > I tried changing the smtp port in mailman.cfg to 587, but that didn't > change anything. because the issue is not in delivery from Mailman to Postfix. It is in delivery from Postfix to billoblog.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: CPU usage when idle

by Mark Sapiro

On 5/28/25 08:27, roughnecks via Mailman-users wrote: > > It's the manage.py qcluster whatever is called. I have shut down MM for > the time being, because I'm not fully motivated to have it running, so I > can't be more accurate right now. I don't know how qcluster is configured in the Debian packages (which are out of date and possibly buggy anyway). You may be using django-q <https://django-q.readthedocs.io/en/latest/> and if so, you should migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both typically use memcached as a backend. Settings that control this are typically ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` and possibly a setting like `'workers': 2,` (default is the CPU count of the system but see <https://django-q2.readthedocs.io/en/master/configure.html#f1>). ``` CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION': '127.0.0.1:11211', } } ``` although the default if not set is ``` CACHES = { "default": { "BACKEND": "django.core.cache.backends.locmem.LocMemCache", } } ``` It is the `'orm': 'default'` setting that says to use Django's CACHES. See <https://django-q2.readthedocs.io/en/master/brokers.html#django-orm>. You can get info about what qcluster is doing with `manage.py qinfo` and monitor things with `manage.py qmemory` and `manage.py qmonitor`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 8:28 PM, dancab(a)caltech.edu wrote: >> In either case, the bounce message (fake DSN) should have contained a >> message body like >> Mail to user(a)example.com failed at outgoing SMTP >> with the actual user's address. These fake DSNs are sent in the case >> where the outgoing MTA refuses a message from Mailman so there is no >> actual failure DSN. > > Thanks. I think I'm missing how I can configure Mailman so that the actual user's address is used. I think you are missing the point. This is a pseudo DSN. If it were a real DSN it would be something like From: mailer-daemon@somewhere To: listname-bounces@listdomain However, there is no real DSN because Mailman has gotten a reject in it's attempt to deliver to the outgoing MTA so it creates it's own pseudo DSN for the failure. Another way of looking at this is if you configured Mailman to deliver to a local MTA and configured that MTA to relay to your remote MTA, your local MTA would accept the message and then receive the 5xx status upon delivery to the Remote MTA and would then send an appropriate DSN back to the list-bounces address. Since you are skipping the local MTA part, Mailman gets the 5xx status upon delivery to the remote MTA and creates it's own DSN for itself. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

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

by Mark Sapiro

On 4/5/25 13:00, megabrutal--- via Mailman-users wrote: > Hi Everyone, > > I've recently installed Mailman3 and still testing it. I tried to reply to a topic on my own list while also being a superuser from HyperKitty, but I got this error message: > > "This list is moderated, please subscribe to it before posting." Is your login a member of the list? > Then why I even see the archive of the private list? What might be wrong? You can see the private archive because you are logged in as a superuser. > One thing that might confuse the system is that I added a secondary e-mail to my account. I thought it would allow me to post from any of my addresses, but it seems like it's not the case, looks like I can only subscribe with one of the addresses. How did you add that email? When you find yourself at https://example.com/mailman3/users and click Manage, do you see the expected addresses? > It also looks like HyperKitty has trouble matching up the addresses, as it lists 4 participants for the conversation, while 2 of them is my account, the other 2 is my test address. In reality, it should list 2 posters. This is normal. Hyperkitty lists participants by address whether or not the addresses are linked to the same user. -- 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: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 2:27 PM, Ken Alker wrote: > --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> The 404s are addresses im HyperKitty's sender table for whih there is no >> corresponding Mailman user. There are multiple possible reasons for this. > > And that is OK, right? Sure. It only means that there are messages in the archive that are From: addresses that aren't currently Mailman users. >> If the behavior has stopped it's probably because the periodic Django >> jobs are not being run - this is bad. > > I see this in the logs from just after midnight: > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > Followed by a huge amount of HTML (strange). This is all from one post. The first is normal it just says that Mailman's var/public_suffix_list.dat doesn't exist, but it should be retrieved from https://publicsuffix.org/list/public_suffix_list.dat and then saved at var/public_suffix_list.dat so it doesn't need to be retrieved from the web again until the saved copy is older that the configured dmarc.cache_lifetime (default = 7 days, so that message) after which time the message will be 'Cached copy of public suffix list is out of date' The second is acceptance of the post. The third is a failure in archiving the message. Th HTML should contain an error message with a traceback which should help determine the problem. > Is there a way to kick it into re-running whatever it does at midnight > so I can test this again after putting the public suffix list back? I > assume I can just execute "mailman-web runjobs daily", but will this > mess things up, or is it OK to run it mid-day without stopping anything > first? Midnight is a coincidence in this case. the above are all due to the post with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> The cached var/public_suffix_list.dat should now be there with a timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) > Is the last (third) log line excerpt simply a result of the first, or do > I have something else messed up? The third is not because of the first. It is because of some issue with archiving that post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 06:24, Jens Günther wrote: > > I find those changes, but: in the merge request there is mentioned a > /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po > > -> but I don't find a mailman-de.po ... is it maybe that? That file was for a test only. The German message catalog is at mailman/messages/de/LC_MESSAGES/. That directory should contain a mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be created. The source distribution contains a generate_mo.sh script to generate these for all languages, but you can do the German one by changing to the mailman/messages/de/LC_MESSAGES/ directory in the running installation and doing msgfmt mailman.po -o mailman.mo >> Please be more specific than `all types of system mails`. Which >> specific message subjects are not translated. > > It's exactly as mentioned in issue 993 the welcome and goodbye-messages > that I don't see translated. > > But also other examples: > - bounce-mail for the user that moderator approval is necessary (there > the text is in german, but the reason is in english) > - approval-mail for moderator (also text is in german, but subject and > reason in english) I'll look into these. If you don't have the mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the reason, but there may be a bug. -- 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

Search results for query "sapiro"