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

[MM3-users] Re: Must issue a STARTTLS command first when forwarding from old server to new server

by Mark Sapiro

On 11/14/24 15:53, jkoral(a)luc.edu wrote: > I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. > > Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS? This is all the MTA, not Mailman. As you suggest in a follow up, you should enable TLS on the old server. In Postfix main.cf, I think ``` smtp_tls_security_level = may ``` should do 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: Cannot Create New List

by Mark Sapiro

On 11/5/25 09:59, dap1--- via Mailman-users wrote: > As far as I know I did everything (except the /etc/mailman3 stuff) in the venv environment. Pip is not even available outside of mailman user. When I try to run pip again it says requirement already satisfied. I don't suppose there is a checkparms like in mailman2. I'm not aware of any Mailman 2.1 checkparams. There is check_perms, but I don't know if that's what you want. The fact remains that something is checking for `/usr/bin/django-admin`, finding it and then trying to run `flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely` If everything is in your venv, why is there a `/usr/bin/django-admin` and perhaps a `/usr/share/mailman3-web/manage.py`. These all look like artifacts from an install of the Ubuntu mailman-web package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: Header Filters

by Mark Sapiro

On 5/31/20 7:23 PM, Peter Adebahr via Mailman-users wrote: > > Hi *, > > we are trying to dispose of automatic replies like "out of office" etc. > > For these ends, we have set > > Header to "subject" (w/o quotes) > Pattern to ".*out.of.office.*" > Action to "Hold for moderation" This should hold any message that contains 'out of office' (case insensitively) anywhere in the Subject: - also the leading and trailing '.*' is superfluous as the pattern is matched with re.search - BUT this test is applied after member moderation so if the message is from a member and the member's moderation action is Accept either explicitly or via list default, the message will be accepted without applying further tests. You want the member's moderation action to be Defer so that additional checks such as header matching are applied. -- 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: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 6:07 PM, David Newman wrote: > On 1/7/22 4:32 PM, Mark Sapiro wrote: > >> I suspect an issue trying to connect to the MTA to send the messages. >> This can be caused by permission errors. Check permissions on >> Mailman's var/templates/* > > Bingo. This list had regular and digest footer templates with 0644 > permissions owned by root:root, and there was an exception and traceback > for the most recent message in shunt about the permissions issue. That comes from running `mailman import21` as `root`. Always run `mailman` commands as the Mailman user. > I've changed ownership to mailman:mailman and restarted the mailman3 > service. > > As soon as I fixed this, my inbox filled with test messages... Good! >> Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in >> mailman.log? > > Yes, lots. This might or might not be a different issue. It is exactly this issue which is now corrected. > As I mentioned earlier, the most recent message in shunt was from 0000 > hours today. There are many "Cannot connect" messages since then, but > none since fixing the issue above. The Cannot connect messages are from the issue of ownership of the templates and Mailman's out runner continually retrying the send. This is separate from the shunted messages. > Seems OK now. The superuser sees all posts after the unshunt action. So it appears that you ran `mailman unshunt` and the shunted messages were successfully processed, so whatever caused them to be shunted in the first place is fixed. Individual messages don't get shunted because of this template ownership issue, but it may be that digests do get shunted for this reason. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Source Installation Assistance

by Mark Sapiro

On 11/29/19 7:37 AM, actionmystique(a)gmail.com wrote: > mark.van.holsteijn＠gmail.com > I stumbled across the same issue as Brian Carpenter within a slightly different environment: > Ubuntu focal 20.04 > PostgreSQL 12.1-1 > > I tried to replace the following line in ```/usr/lib/python3/dist-packages/hyperkitty/migrations/0007_allauth_20160808_1604.py``` from ```python3-django-hyperkitty``` (1.3.0-1ubuntu1): > ``` > cursor.execute("SELECT 1 from social_auth_usersocialauth") > ``` > with > ``` > cursor.execute("SELECT 1 from information_schema.tables where table_name ='social_auth_usersocialauth' and to_regclass('social_auth_usersocialauth') is not null") > ``` > then > ``` > python3 manage.py makemigrations > ``` > leads to a different issue: We are working on a proper fix for this issue. See <https://gitlab.com/mailman/hyperkitty/merge_requests/200>. In the mean time, to work around this issue on a new install, the simplest change is to just delete the second to last line ``` migrations.RunPython(migrate_social_users), ``` from hyperkitty/migrations/0007_allauth_20160808_1604.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Mark Sapiro

On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > I am currently automating a few things using the CURL commands but only > postorius related as of now. Now I have a requirement. > > I need to create a lot many users and their mapping email ids through > Site Administration almost daily. But it is becoming to do the same through > Graphical Interface. > > So, I just want to know the CURL commands that can be used to create the > user accounts and email ids mapped to user accounts. The accounts you are talking about are Django accounts. You cannot create these via CURL to the Mailman core REST API. You might find <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/26/21 1:19 PM, Andreas Barth wrote: > > Re the "latest greatest", that's always the same question for all > software. If one is happy what comes from the distribution, I always > recommend to use that (or just use the currently developed stable > version, i.e. testing or unstable, perhaps even only for these > packages). If one needs something newer / else / specific local > patches, it's good to have documentation that helps. We're not talking bleeding edge here (although the server that supports this list and the python.org lists is bleeding edge). We are talking about installing the current releases from PyPI. Mailman 3 is still relatively young and there are many important features and fixes in the current releases that aren't in the Debian/Ubuntu packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Moderation request reminders

by Mark Sapiro

On 1/14/23 09:33, Allan Hansen wrote: > > I and my moderators are getting daily moderation request reminders. Is there a way to set them to be weekly instead? I looked around in the UI for it but did not see it. It started with my latest server upgrade. As list owner I get 50+ of these messages every morning and my modertors each get only one, but don't like it. This is `mailman notify` <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…> run by cron. > I still don't see a link for my moderators to see the membership lists even though the lists are set to allow it. Is that among the planned bug fixes? This is <https://gitlab.com/mailman/postorius/-/issues/369>. There is an abandoned MR at <https://gitlab.com/mailman/postorius/-/merge_requests/423> but see the recent notes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/29/24 03:09, Marco van Tol wrote: > > Right now I’m back at the original issue as I see no other solution than to go back to whoosh. > > Thanks! > > Marco van Tol > > Paste: > ---- > Indexing 194620 emails > [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like ``` SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; ``` and modify or delete it - it's probably spam anyway. -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 9/23/25 09:39, Stephen J. Turnbull wrote: > nirmal--- via Mailman-users writes: > > > Eventhough I have downgraded it. Archiving is not working. Kindly > > help me to solve. > > Does the subject have anything to do with this problem, or did you > reply to some other thread? > > If it's related to the problem, that's one problem. Most likely the > api_key setting in mailman-hyperkitty.cfg' doesn't match the > MAILMAN_ARCHIVER_KEY in 'settings.py', or possibly you have the wrong > quoting in one of the files. This could have happened in the > downgrade if you downgraded only some of the Mailman packages. Actually, this is an incompatibility issue. It results from mailman-hyperkitty < 1.2.0 in combination with HyperKitty >= 1.3.5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

Search results for query "sapiro"