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

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

by Stephen J. Turnbull

Mark Sapiro writes: > Presumably that's the 'Recipient address rejected: User unknown in > virtual alias table' message, but I see no virtual_alias_domains in > your posted main.cf. I'm pretty sure that what's going on here is that the message is coming in from outside, Postfix runs down the various relays (including local delivery) available, none matches, the last in line is virtual aliases, and that table is empty so the user is unknown. That's the only way I can see the sender_canonical_maps variable affecting *recipient*-based decisions, by making it look like the sender is local, and so enabling delivery to non-local addresses. Why a Mailman list appears to be non-local is a question I am not sure. My guess is myhostname = localhost because Postfix doc says mydomain "is derived from $myhostname by stripping off the first part (unless the result would be a top-level domain)," so literally "localhost" is the only deliverable domain left, and some-list(a)the.actual.dom doesn't work. Except that the.actual.dom should be in postfix_domains.db, so ... ???? Steve

1 year, 8 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

On 24/06/2020 00:20, Mark Sapiro wrote: > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ > > Do you see this domain there? If so, delete it. I hadn't logged in as admin before, so having done so I can now confirm that having done so this screen shows "0 mail domains" Because I could, I then visited "VIEW SITE" and see a mailing lists page, which is I think the same one I have been trying to visit, except of course now I am logged in. I do now see the correct, and only, mailing list configured on the core server. Returning to the previous "maildomain" page, that now shows the expected mailing list as well. Other admin pages seem to be working fine as well. I think, possibly, that it is now installed and working. ... But I don't know why. Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 2 months

[MM3-users] Re: timezone in hyperkitty

by matthew_saunders＠harvard.edu

Mark Sapiro wrote: > On 6/29/20 12:18 PM, Marco Marinello wrote: > > I'm expirencing the same behaviour in Postorius. Is > > it possible to set a default timezone for new users? Already set it in settings_local.py > > but not having any effect, still seeing "Africa/Abidajin" in new users. > > Do you mean the users time zone as displayed in the user's profile? This > is a Django setting and the default should come from the TIME_ZONE > setting in settings_local.py, at least if USE_TZ is set True I'm seeing the same behavior on my development site, and I was even able to reproduce this when I created my account on this very site moments ago using OAuth. If you check the django_mailman3_profile table in the DB, I expect you'll see that my timezone record is blank (since I haven't touched it from the Accounts page). FWIW, it's empty... not NULL, since there's a not-null constraint on this field. Is it possible to have this set to a default (non-empty) value somehow? TIME_ZONE & USE_TZ isn't doing it.

5 years, 1 month

[MM3-users] Re: What to backup?

by Alain Kohli

I have noticed that especially the var/messages directory has a rather considerable size compared to the rest. What exactly is this for and what would be the consequences if that was lost? And more generally, would not backing up var/ at all only result in the loss of some short term data (e.g. messages that are held or currently processed) or would long term data also be lost? Or in other words, what exactly would be non-recoverable if that isn't backed up? On 5/22/19 5:21 PM, Mark Sapiro wrote: > On 5/22/19 6:31 AM, Alain Kohli wrote: >> Hi >> >> What exactly are we supposed to include in our mailman backups? >> Obviously the database, but are there any other files that should be >> included to make sure we can properly restore? > > I would backup all of Mailman's var/ directory. Additionally, I would > backup the directory where Haystack's backend search engine stores its > indices. For the default Whoosh backend with default settings this is > the fulltext_index/ directory in the same directory as your Django > settings.py file. >

6 years, 3 months

[MM3-users] Re: Manual setup - permissions

by Tobias Hachmer

Hi Mark, thanks for your response. On 9/23/19 1:29 AM, Mark Sapiro wrote: > On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: >> >> Now, running the scheduled tasks (which run from user+group "nginx") for >> django I ran into permission problems, because the nginx user can't >> access/write to the needed files in /opt/mailman3/core/... >> >> I would appreciate any hints how to run the different peaces of mailman3 >> with the correct user/groups/permissions. > > > Set up everything as user:group mailman3:mailman3. I.e., > > chown -R mailman3:mailman3 /opt/mailman3/web > > and set the uwsgi service to drop privileges to user+group "mailman3". So simple, now the scheduled tasks are working, but the whole web service did not work because the web server user nginx can't access and write to the uwsgi socket anymore /opt/mailman3/web/project/run/uwsgi.sock. # chown -R nginx:mailman3 /opt/mailman3/web This works for all. But isn't it a security risk that e.g. manage.py and settings.py is read- and writeable by the webserver? Regards, Tobias

5 years, 11 months

[MM3-users] Re: xapian db corruption - xapian.DatabaseCorruptError: Couldn't read enough (EOF) ??

by Odhiambo Washington

On Mon, Jul 29, 2024 at 9:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/24 03:27, Odhiambo Washington via Mailman-users wrote: > > Today, my hourly cron job has generated an error and continues to do so > > every hour: > > > > ``` > > Subject: Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs > hourly > > ``` > > > > Not sure what caused this. Perhaps a reboot when the cronjob hadn't > > completed? And a possible manual remedy would be to wipe the indexed db > and > > let the cron run again? > > > Or maybe just run `/opt/mailman/mm/bin/django-admin rebuild_index Nice to know. I just deleted the contents of the xapian_index folder and then ran the cronjob. Solved. -- 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, 1 month

[MM3-users] Re: User cannot reset password

by Greg Newby

On Sun, Aug 11, 2024 at 11:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/24 10:56, Greg Newby wrote: > > I imported MM2.1 lists to Mailman3 (using import21 - details are in my > > previous messages to mailman-users), and have had a couple of reports of > > people for whom the password reset function via "Forgot password" on the > > list login screen doesn't work as expected. > > > Django (web) accounts (Postorius and HyperKitty) are separate from > Mailman core. Users inported from MM 2.1 do not have web accounts. They > have to sign up, not request a password reset. > 1. Will the new (Django) and imported (Postorius) usernames automatically be matched to the same email address? The goal is for someone to use the web-based front end to manage their migrated subscriptions. 2. How can I customize the email that went to users who selected "Forgot password?" ( You are receiving this email because you, or someone else, tried to access an account with email I didn't find that string in the source code. Thanks as always! ~ Greg

1 year

[MM3-users] Re: Search problem in 3.2.1?

by Mark Dadgar

On Oct 22, 2019, at 6:44 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/22/19 7:51 AM, Mark Dadgar wrote: >> Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). > > > How did you install ElasticSearch. What ElasticSearch version? From .deb, version 5.6.16. > This is a bug in HyperKitty. We've never encountered it, but the code at > <https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/views/search.p…> > only considers the whoosh and xapian backends and needs to be updated > for elasticsearch. I've reported that at > <https://gitlab.com/mailman/hyperkitty/issues/263>. Hmm, maybe I’ll take another shot at getting Xapian running then. Whoosh ran for 5+ days trying to index my archive of 556,000+ messages before I gave up. Thanks for your help, Mark. Much appreciated. If we ever bump into each other here in the Valley, I owe you a beer or 9 for all the value I’ve gotten from mailman over the years. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 10 months

[MM3-users] Re: Moderation Action Changed After Import

by Brian Carpenter

On 2/12/21 4:21 PM, Mark Sapiro wrote: > Yes, You did the right thing. I was mislead by "He said the previous > moderation was the list's default which was hold for moderation." which > is Mailman 3 terminology. > > The list does need to be created first, but it should be a new list with > no members, owners, etc., not an operational Mailman 3 list. > > So, it seems that most of the members of the MM 2.1 list were moderated > and the list's member_moderation_action was Reject. Is this not the case? Sorry for the wrong terminology I can't confirm what was set on the old MM2 list as it is no longer accessible. I am just going on the word of the List Owner. My opinion is that the moderation for those list members were set to Reject on the previous MM2 list. I am mainly interested to see if you know of this happening to anyone else and/or perhaps there is an existing bug that could impact the moderation settings of imported MM2 lists. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 6 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-25 22:03, schrieb Mark Sapiro: > On 4/25/24 12:34, Thomas Stein wrote: >> >> I'm not sure how to add that to my django settings. Adding: >> >> x = list(MIDDLEWARE) >> x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> MIDDLEWARE = x >> >> did not help. Any hints? > > I don't know how things are arranged in the Debian/Ubuntu package, but > you may have a settings.py which at the end does something like > ``` > try: > from settings_local import * > except ImportError: > pass > ``` > If that is the case, adding the above snippet to the end of > settings_local.py should work. Yes, that's the case. I added the snippet in question to settings_local.py but this leads to another error: File "/usr/share/mailman3-web/settings.py", line 503, in <module> from settings_local import * File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> x = list(MIDDLEWARE) ^^^^^^^^^^ NameError: name 'MIDDLEWARE' is not defined dpkg: error processing package mailman3-web (--configure): I hope you can helo again. cheers, t.

1 year, 4 months

Search results for query "sapiro"