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

[MM3-users] Re: Footer variables

by Mark Sapiro

On 3/2/26 11:03, Mark Sapiro wrote: > > Are there `Exception in "hyperkitty" archiver` messages in mailman.log, > or if you have set a path: in the [logging.archiver] section of > mailman.cfg, in that file? Actually, there won't be those messages. The code in question is <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/decor…> The fact the ${hyperkitty_url} is replaced with an empty string indicates that line 79 does not raise an exception but rather sets archive_url to the empty string. This is the only way that the replacement dictionary would contain the key `hyperkitty_url` and if it didn't contain that key, the resultant footer would contain literally `${hyperkitty_url}` You could try in `mailman shell` ``` $ mailman shell -l list.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.example.com mailing list >>> from mailman.email.message import Message >>> msg = Message() >>> msg['Message-ID'] = '<xxx(a)example.com>' >>> for archiver in IListArchiverSet(m).archivers: ... if archiver.system_archiver.name == 'hyperkitty': ... print(f'URL: {archiver.system_archiver.permalink(m, msg)}') ... ``` This should print something like URL: https://example.com/archives/list/list@example.com/message/FMB3KJSE74FUTZBV… Does it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Mark Sapiro

On 9/19/19 12:02 AM, Henrik Rasmussen wrote: > Abhilash Raj wrote: >> On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: >>> each other, but Postfix is trying to deliver mail via lmtp to >>> [172.19.199.2]:8024. Mailman's lmtp runner should be running and >>> listening on port 8024. Either that is not the case or that port is not >>> exposed to Postfix on IP 172.19.199.2. >>> Right, that is what I was wondering, you verify that by using telnet >> on the specified IP and Port (172.19.199.2:8024). > > Yes, the postfix container listens on 172.19.199.2:8024 > ``` > [root@postfix /]# nc -v 172.19.199.2 8024 > Ncat: Version 7.50 ( https://nmap.org/ncat ) > Ncat: Connected to 172.19.199.2:8024. > 220 mailman-core GNU Mailman LMTP runner 2.0 > ``` This seems to say that the Postfix container can connect to 172.19.199.2:8024 and receive the greeting from Mailman's lmtp runner. So, why can't Postfix send to 172.19.199.2:8024? The only log entry you postes just says "Sep 18 10:07:47 postfix postfix/qmgr[98]: warning: mail for [172.19.199.2]:8024 is using up 7844 of 7844 active queue entries". What other log entries relate to attempts to send to 172.19.199.2:8024? You may have to go back to when this first started to see them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: required cron entries?

by Mark Sapiro

On 1/1/21 12:37 AM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [201231 19:28]: >> On 12/31/20 2:49 AM, Andreas Barth wrote: >>> Looking in the source code, there is a ./cron/crontab.in.in however >>> references to scripts in port_me/ directory. >> >> That's all old Mailman 2.1 stuff. ignore it. > > Can we replace that by a mailman3 cron tab? (I'm happy to write that > as merge request if useful, but I assume that should be done rather by > opening a bug report and using gitlabs features and not inline per > mail) Yes, the ideal workflow is to open an issue on GitLab and then open a merge request to fix it. However, I don't think we need a sample crontab as we have <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs> which should be enough. I think the real solution is to just remove the mailman/cron directory and at least some of the mailman/port_me/ files. The cron/crontab.in.in file is just a distraction. For the port_me files, we have: checkdbs.py - this function is handled by `mailman notify` disabled.py - handled by core's bounce processing show_config.py - handled by `mailman conf` and these for which no MM 3 equivalent exists and which could be helpful in implementing a corresponding `mailman` subcommand: config_list.py export.py find_member.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: No e-mail distribution after import of archive

by Mark Sapiro

On 11/11/24 23:33, Markus Grandpré wrote: > Dear Mr. Sapiro, > > on our test system we noticed the problem that after importing a mailing > list archive from a Mailman system v2.1 into a Mailman system v3.3.8, > e-mails are no longer distributed via this mailing list. E-mails that > are written to the list find their way into the archive, but they are > not sent to any member of the list. > > Before the archive was imported, writing an e-mail to the list and > distributing this e-mail via the list was not a problem. Unfortunately, > we cannot find any indication of this issue in the log of the mailman > system v3.3.8. Please help us to further analyze and solve this problem, > as we are planning to import 188 archives into our new productive > mailman system v3.3.8 during the next months. Nothing in HyperKitty should affect Mail delivery from the list. The symptom you see could result in a file in Mailman's mailman/templates/lists/<THIS.LISTS.ID>/<LC>/ directory not being readable by the Mailman user. Check ownership and permissions on everything in var/templates/ See the latter part of the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Note that if this is the issue, something other than hyperkitty_import did it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Mark Sapiro

On 2/13/26 05:41, Ibiam Chihurumnaya via Mailman-users wrote: > Mark Sapiro wrote: >>> OK, this is Django. The default EMAIL_BACKEND from >> mailman_web/settings/base.py is >> django.core.mail.backends.smtp.EmailBackend and unless you've changed >> that or added overrides various other defaults are >> EMAIL_HOST = "localhost" >> EMAIL_PORT = 25 >> EMAIL_HOST_USER = "" >> EMAIL_HOST_PASSWORD = "" >> EMAIL_USE_TLS = False >> EMAIL_USE_SSL = False >> EMAIL_SSL_CERTFILE = None >> EMAIL_SSL_KEYFILE = None >> Are those appropriate? Do you have an outgoing MTA listening on >> localhost:25? What's in it's logs? > > I don't have any of those set, didn't realize I needed to have them set, the docs didn't make it obvious too. > I also didn't notice them in schema.cfg in mailman. You normally don't need to set any of those. The defaults should be fine for a local MTA listening on port 25, however what's in /etc/hosts for localhost. If it's the IPv6 address ::1, I suggest changing it to 127.0.0.1. > smtp_port is currently set to 25, and I do have an outgoing MTA listening on localhost:25. > Nothing shows up in the MTA logs about this particular email. Again, whats the address for `localhost` in /etc/hosts? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Mark Sapiro

On 1/27/23 05:53, Odhiambo Washington wrote: > On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Note that when following >> https://docs.mailman3.org/en/latest/install/virtualenv.html you create >> /etc/mailman3/settings.py and it contains >> ``` >> from mailman_web.settings.base import * >> from mailman_web.settings.mailman import * >> ``` >> to establish a base set of settings that can be augmented or overridden >> in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn contains >> ``` >> HAYSTACK_CONNECTIONS = { >> 'default': { >> 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', >> 'PATH': "fulltext_index", >> ``` >> which is a relative path for fulltext_index and may need to be set to an >> absolute path. >> > > Mi Mark, > > I have read this page - > https://docs.mailman3.org/en/latest/install/virtualenv.html and further - > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config > - without clicking any external links. > I still don't see the HAYSTACK_CONNECTIONS in the settings.py included on > that page. > I am missing something obvious, no? Please reread what I wrote above. HAYSTACK_CONNECTIONS is not in the suggested settings.py but it is in mailman_web.settings.mailman and is imported by the suggested settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[Test] posting here

by Mark Sapiro

This is a list post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 3 months

[Test] Test after reboot

by Mark Sapiro

-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 3 months

[Test] Test after second reboot

by Mark Sapiro

-- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 3 months

[Test] Re: Is there anybody out there?

by Mark Sapiro

On 03/17/2016 11:54 AM, Florian Fuchs wrote: > Ping! Pong! -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 3 months

Search results for query "sapiro"