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

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/11/25 04:45, Mark Sapiro wrote: > On 10/10/25 3:46 PM, Flo via Mailman-users wrote: >> >> /var/lib/mailman3/web# sqlite3 mailman3web.db >> SQLite version 3.46.1 2024-08-13 09:16:08 >> Enter ".help" for usage hints. >> sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON >> site_id = django_site.id; >> ... >> ... >> 8|lists.example.com|7|7|Lists of Example|lists.example.com >> sqlite> >> > > The fields in order are: > > 1. the id of the django_mailman3_maildomain entry > 2. the mail_domain in the django_mailman3_maildomain entry > 3. the site_id the django_mailman3_maildomain entry > 4. the id of the django-site entry > 5. the domain name in the django-site entry > 6. the display name in the django-site entry > For me it looks like that 5 is the display name and 6 the domain name > The important things are 2. and 5. which are the mail host and the web > host that you see in the Postorius domains view. 3. and 4. are what we > joined on so they will always be the same. They aren't related to 1. > which is just sequentially assigned when entries are created. 1., 3. and > 4. being equal in some cases is a coincidence. > > The question is what are the other 2 entries. In particular are all 3 > values for 2. different and all 3 values for 5. different or are some > the same? > > If 2 of those entries have the same value for 5. and different values > for 2., that explains the issue when accessing Postorius at 5. because > that web host does not have a unique mail host. > For each of the lines mail_domain (field 2) is the same as the domain name (field 6, if I am right). Any domain name (and mail_domain, which has the same value) differs from the ones in any other line. So they are unique. Flo

5 months, 3 weeks

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

by Stephen J. Turnbull

Ibiam Chihurumnaya via Mailman-users writes: > 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. Those defaults *are* set in the mailman_web settings files. You can override them in /etc/mailman3/settings.py, but often you don't need to. > I also didn't notice them in schema.cfg in mailman. This is for Django, whose configuration is in /etc/mailman3/settings.py, with defaults set in the mailmanweb package in your venv's site-package in the files in .../mailman_web/settings/. > smtp_port is currently set to 25, and I do have an outgoing MTA > listening on localhost:25. If Mailman can distribute posts that way, Django should be able to send mail with the default settings. > Nothing shows up in the MTA logs about this particular email. Not sure what to say about that. I'm not sure Postorius or Django log outgoing mail messages but I think they use the mailmanweb.log file by default if they log mail at all. (This is separate from the MTA logs which should record any connections from localhost and mail submitted.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month, 2 weeks

[MM3-users] Re: Moderate mails from owner

by Abhilash Raj

On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: > On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > > > However, this is apparently not relevant because both the Member and > > Non-Member actions are Hold. Thus, the post should be held unless it has > > an Approved: header with the list's moderator_password attribute if > > there is one, or it matches a Header filter rule with an accept action. > > At the risk of getting this really wrong - I have only limited MM3 > knowledge - I will ask what is, I fancy, a closely related question ... > > My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From > the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find > anything to identify Postorius which is the only interface I have to the > system. > > From symptoms seen and described by others, I have deduced that the > Postorius admin-per-user moderation options of "Default processing" and > "List default" mean that a user may be set (by default on the rootsweb > system!) to use the system default moderation settings rather than the > list default settings. "Default Processing" means the default pipeline defined in List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This pipeline is system wide and is defined in source code, so it can't be customized by site administrator. > > Are my deductions correct? And if so, could this be the explanation of the > issue detailed in this thread? > > Apologies if I'm barking up entirely the wrong tree, Malcolm. > > -- > Malcolm Austen <malcolm.austen(a)weald.org.uk> > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years

[MM3-users] Re: Mailman3 on FreeBSD

by Abhilash Raj

On Sat, 12 Aug 2017 18:10:49 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/12/2017 04:51 PM, Barry Warsaw wrote: > > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> > > wrote: > >> > >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however > >> I don't see any indication as to what I should put in this file > >> and if it was in /usr/local/etc/mailman.cfg then how would mailman > >> find it? > > > > It wouldn’t by default. Right now Mailman does not search > > for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult > > change to add. I’m not sure whether that would makes sense as a > > general default or not. I’m not up on the FreeBSD conventions and > > standards here; can you explain why /usr/local/etc is preferred > > over /etc on that distro? > > > I was hoping Abhilash would chime in here, because I think John is > using the docker image and there's probably a specific path for > mailman.cfg. As per his first message, I think John is using the prod setup from the documentaion[1]. I don't have anything much to add on top of what Barry mentioned, it looks like something is wrong with the Python install and missing Sqlite3 module. The documentation does mention the paths where Core looks for configuration file and anything else can be specified using -C or MAILMAN_CONFIG_FILE environment variable. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > As far as what goes in it, it could even be empty if you want to > accept all the defaults, but you probably want at least > > [mailman] > site_owner: real_person(a)example.com > > I expect if you do > > find -name mailman.cfg > > in your installation, you'll find at least examples. > thanks, Abhilash

8 years, 7 months

[MM3-users] Re: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Thomas Ward

On 10/19/23 13:41, Mark Sapiro wrote: > On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: >> I noticed some unusual behavior in Mailman3 stable release on PyPI >> and such. Namely, there are instances where replies are being >> processed and the prefix tags are simply being **lost** and dropped >> by Mailman3, instead of being properly prepended where they're >> supposed to go. >> >> Is this a known bug or does it need its own bug in the gitlab tracker? > > > Are you sure you are looking at messages from the list and not > messages received by direct To:, CC: or BCC:? > > I have never seen an issue where list posts would sometimes have the > subject prefix prepended and sometimes not. If you are seeing this, we > would ideally like to see a thread in the hyperkitty archive where > some of the messages have the prefix in the message view and some > don't, or at least see some of the raw Subject: headers. This might be a MUA quirk because we (read: my employer, like my other messages) are using Outlook which we all know does Weirdness. Upon examination of the actual message's source it has the proper subject line with a prefix: > Subject: [Test] Emailing Test But the way this is displayed in Outlook is weird. It may be that Microsoft is seeing the message as CC'd (reply-all was used!) and then stripping prefix, etc. because it realized there was some stupidness or such at the message-id level or something. This is looking more like a MUA issue because my other address which is subscribed and uses Thunderbird to access the mailbox instead sees the headers right with the proper prefix, suggesting this is something specific to Outlook as a MUA. Thomas

2 years, 5 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/5/23 01:13, Odhiambo Washington wrote: > > > > So in my case, I should at least increase the value of > > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? > > > It probably isn't even set in your case and defaults to 900 if it isn't > set. I have never seen this config option in any of the settings files and so believe that no one has it set - except the DEVs, maybe. > Yes, you can set it to a larger value. If your archive search > engine is woosh and your archive is even moderately large, 1800 probably > isn't nearly enough. Yes, my archive search engine is whoosh. And my archives size is 2.5GB+ For starters I will make it 3600 and observe next time. > There was no indication of timing in your OP, but you should determine > when that cron job started and when the error was > reported. The difference is the absolute minimum you should set > for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin > to that. > Sadly I deleted the email. I will have to determine those aspects next time. I need to make a request for a small improvement on the documentation at: https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… The problem I am facing (the subject of this thread is that of a race between the "monthly hyperkitty update_and_clean_index" job and the hourly "hyperkitty update_index job" Would it be possible to add such details to the section, so that it is clear what the corn jobs do and perhaps what can lead to such race conditions (if that's not too much to ask)? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: Mailman 3 stops delivering to a domain after too many bounces

by Tim Cutts

> On 12 Jul 2022, at 16:28, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/12/22 12:34 AM, Julian Kippels wrote: >> Hi, >> We have recently upgraded from Mailman 2 to Mailman 3. Since then I >> have observed many user reports that mails to mailing lists don't reach >> all members. My suspicion is that there are too many "dead" members on >> those lists. This was not a problem on Mailman 2, but has become a >> problem on Mailman 3. It seems to me that for example Mailman 3 sends >> mails to the first 5 existing member addresses from domain A, then >> encounters several (20 or so seems to be the threshold) "dead" member >> addresses from domain A that generate a bounce and then does not even >> attempt to reach the remaining 800 member adresses from domain A and >> only sends to members on domain B and domain C. >> Is there a way to globaly ignore bounces and send out mails to all >> members of a list, no matter what? > > > Mailman's outgoing runner should not be quitting because of bounces at SMTP time. It seems like there may by some issue causing Mailman's outgoing runner to die. What's in Mailman's var/queue/shunt/ and Mailman's var/logs/mailman.log. Good point. Mailman3 needs a great deal more RAM than Mailman2, especially if you’re running the web and core on the same machine. I used to comfortably run my small mailing list server on a 1GB VM, but on Mailman3 I found it often ran out of memory and bits of mailman3 would get shot by the kernel’s OOM killer, and had to move to a larger VM. So I’d check your kernel logs and see if you’ve got OOM messages in there. Tim

3 years, 8 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/07/30 22:39, Mark Sapiro wrote: > > It appears you have a situation where the MX for the Mailman domains > > is not the Mailman server. You need to configure the MTA on > > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > > You can to this by configuring that MTA to use transport_maps, etc as > > if it were the Mailman server. In order to get Mailman's generated > > files on the other server, you need to create a process to do that. > > When Mailman makes changes by adding or deleting lists or when it is > > started, it updates the postfix_lmtp and postfix_domains files and > > calls a command (normally postmap) to update the corresponding .db > > files. The command can be set by setting `postmap_command` in the > > `[postfix]` section in mailman.cfg. > > > I'm not able to find any documentation about `postmap_command`, not even > in the schema.cfg. If I have to provide method to update the > postfix_lmtp and postfix_domains on another server, then it would have > to something like sftp? mailman changes the files on the mailman server > (in a location I set) and then postmap_command copies those files to the > destination on the MTA server. Is that in principle what needs to be done? > > thanks again! > Read this thread and take a keen look at the solution provided by @Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 8 months

[MM3-users] GSoC task: shell completions for the 'mailman' utility was: Is there a bin/find_member in MM3

by Stephen J. Turnbull

Mark Sapiro writes: > mailman findmember -h > Usage: mailman findmember [OPTIONS] PATTERN IWBNI we had shell completions for bash and zsh at least. I've been out of it, should have got to this sooner, but GSoC org applications are open until Feb 3, so I'll try to rustle one up. If anybody is willing to serve as backup org admin and second mentor, please let me know. Qualifications: org admin fills out GSoC paperwork 2-3 times a season, keeps track of mentor-student relations, and usually serves as a mentor. Note: Mailman has never called on a backup org admin in 10+ seasons of GSoC. Mostly second mentors just read email a couple times a week and comment when they have something to contribute. No real Python-specific skills required, mostly hand-holding and occasionally pumping the brakes on hair-brained deviations from proposed work, and I guess you'd be uncomfortable if you're not comfortable with at least one high level language. Python is often characterized as "executable pseudo-code": it's easy to learn enough to mentor. Deep knowledge of Mailman is not needed for most projects (the bash completions project above is an example where zero knowledge is needed). Typically they add a feature, sometimes independent of Mailman internals, instead hooking into a well-defined API. Obviously Python skills are useful, and most projects will interface with Mailman code. However, it's not uncommon that I've learned Python skills during GSoC, mostly from studying the Mailman code (Barry is not known as the Friendly Language Uncle for Life aka FLUFL for nothing, you know), but often from the student. So it's a learning opportunity for most mentors. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Thomas Drillich

Hello Mark, thank you four your fast response, yes I use the default port 8024 netstat -atp: tcp 0 0 localhost:8024 0.0.0.0:* LISTEN 26555/python >grep MM3_LMTP_PORT /var/lib/exim4/config.autogenerated MM3_LMTP_PORT=8024 lines from exim4/mainlog 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) Am 06.05.20 um 20:55 schrieb Mark Sapiro: > On 5/6/20 10:54 AM, Thomas Drillich wrote: >> Hello, >> >> I tried to setup exim4 + mailman3 but it seems to stuck at lmtp delivery of mailman3. >> Could you give me a hint, to detect the reason of failure ? > ... >> # /etc/exim4/conf.d/transport/55_mm3_transport >> mailman3_transport: >> driver = smtp >> protocol = lmtp >> allow_localhost >> hosts = localhost >> port = MM3_LMTP_PORT >> rcpt_include_affixes = true > Have you defined MM3_LMTP_PORT and is it the same value as the > lmtp_port: setting in the [mta] section of mailman.cfg - default 8024? > > And is Mailman core and particularly its lmtp runner running and is it > listening on the relevant port? > > Is there more information about "all hosts for 'listen.td3.eu' have been > failing for a long time" in exim's logs? > > > _______________________________________________ > 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/ -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

5 years, 10 months

Search results for query "sapiro"