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

[MM3-users] Re: Template Ignored?

by Mark Sapiro

On 2/17/22 08:04, Stephen Daniel wrote: > Mailman3 people -- > > I created a new list, and used postorius to create a template for " > list:user:notice:welcome". I then used the mass subscription feature to > add myself to the list, having checked "pre-confirmed", "pre-approved", and > "pre-verified". > > I received a welcome message that appears to be the default welcome > message. It certainly wasn't what I put into my template. > > Any suggestions on how I get mailman to use my template? Things I might be > doing wrong? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a full URL by appending `/api/templates/list/list.example.com/list:user:notice:welcome` to that where `list.example.com` is the actual list_id of your list, and go to that URL, what do you get? -- 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: Broken web UI after upgrade

by Mark Sapiro

On 12/14/22 08:15, Odhiambo Washington wrote: > After upgrading MM3 and running all the post-update tasks and even > re-indexing all the posts, I have ended up with a somehow "broken" > hyperkitty. > The archives display on a browser six, to say the least. > The site is public, so I can share the link: https://list.rc.org/archives/ > > What should I do in order to fix this? > Are you asking about the lack of style or the "No archived list yet."? The former indicates an issue in your web browser with accessing the `static` directory or an issue with the django admin collectstatic or compress commands. I don't know about the latter - could it be because all the archives are private and I'm, not logged in? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Mark Sapiro

On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- 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: Any possible way to reduce robot spam accounts?

by Mark Sapiro

On 7/20/23 20:42, Franklin Weng wrote: > > Thank you. When I set it in my settings_local.py, I clicked register > and got an error: > > ModuleNotFoundError at/accounts/signup/ > No module named 'django_mailman3.views.user_adapter' > > (In the document the path is /etc/mailman3/settings.py but I installed > it with Debian packages so I guess the path is somewhat different, and I > thought setting in setting_local.py should work too. It seems work > since it gave me the error above.) > > Do I have to install something else? Or disable some other options? What is the version of django_mailman3 in your Debian package? As it says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for these settings to work." -- 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: Mailman issues after re-boot

by Mark Sapiro

On 9/29/23 12:53, paulrubin37(a)gmail.com wrote: > > When I tried to use mailman-web I get this error: > > django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE This is because you have django-allauth>=0.56. If your django-mailman3 version is <=1.3.9 you can downgrade django-allauth with ``` pip install django-allauth\<0.56 ``` Or you can find where in your django settings MIDDLEWARE is defined and add ``` 'allauth.account.middleware.AccountMiddleware', ``` to the list, however if you have a /etc/mailman3/settings.py like the one at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… the imports from mailman_web.settings.base, you need to add the following to /etc/mailman3/settings.py ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` Note either downgrade django-allauth or update MIDDLEWARE, but not both. -- 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: WSGI: gunicorn and uwsgi

by Mark Sapiro

On 6/9/19 3:18 AM, andrew.bernard(a)gmail.com wrote: > Using the Ubuntu 19 packages for all the mailman suite, uwsgi is the Python WSGI server included. I have now switched over to a full build from current source from gitlab, following Mark Sapiro's excellent instructions. Thank you. > It would appear that the current code has the use of gunicorn built in. Is gunicorn the preferred way now to run the mailman Django apps? Is it worth spending time converting everything to use uwsgi, or should I go with the flow and use gunicorn? The "built-in" gunicorn is used only by core to provide the REST API interface. This replaced the former standard library wsgiref module to improve performance. It is completely independent of whatever WSGI server you use for Django. > What are the advantages of gunicorn over uwsgi? I can't comment intelligently on that. For a long time I used Graham Dumpleton's mod_wsgi with Apache for wsgi support, mostly for MoinMoin. I have no experience with uwsgi. When I set up MM 3 on lists.mailman3.org, the server was already using nginx so I arbitrarily chose gunicorn for that. On mail.python.org I started using mod_wsgi, but at one point there was an issue due apparently to an SSL library mismatch following an upgrade, but before the cause was recognized, I switched to gunicorn to get things up. On a third server I manage, I use mod_wsgi for MoinMoin which is Python 2.7. I found setting up both Python 2.7 and Python 3 versions of mod_wsgi on the same server to be daunting, so I went with gunicorn for Mailman 3 on that server too. My choices of gunicorn over uwsgi were an initial arbitrary choice followed by familiarity for subsequent choices. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Different (official?) documentations available - what is the correct one?

by Mark Sapiro

On 2/14/19 9:12 AM, Torge Riedel wrote: > Hi, > > I've found two different documentations: > > http://docs.mailman3.org/en/latest/index.html > > https://mailman.readthedocs.io/en/latest/README.html > > Where the first one looks to me like the official documentation (when > looking at the URL), the second one looks more up-to-date. > > Is there a reason behind it? They are both part of the official docs. The first is the overview of the entire documentation suite. The second is the documentation for Mailman core. The link in the first bullet item, 'Mailman Core - the mailing list manager core (required)' actually is to <https://mailman.readthedocs.io/en/latest/> which is another name for <https://mailman.readthedocs.io/en/latest/README.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: join via webform

by Mark Sapiro

On 6/19/19 4:50 AM, mailman3(a)malevil.cc wrote: > Is there a simple possibility to join a mailinglist besider writing a mail to list-join(a)example.com? I know you can register and then join a list, but thats only possible for public lists It is also possible for unadvertised lists. You can go to `lists/list@domain` and subscribe even though the list is not advertised. > and I would like to have such a very simple webform for a specific list where you just enter your email address and then get the confirmation mail. I guess there was something like this with mailman2 You can do this by having your web form do the subscription via the REST API. See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html> and <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/membership.h…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Moderation not working?

by Mark Sapiro

On 11/24/20 2:53 PM, peter(a)chubb.wattle.id.au wrote: > > The only think I noticed after trawling through all the configs is > there was no moderator address set up. In Mailman 2.1 that meant the > list owner would be asked to moderate. I've added a couple of > addresses to see what happens next Held message notices, both immediate if set and summary (assuming the appropriate cron is active) are sent to all owners and moderators. This is the same for MM 3 and MM 2.1. > For other lists on the same mailman instance I *am* seeing moderation > requests for non-member postings --- but they had explicit moderator > addresses configured. The explicit moderators should not make any difference. Plus, a message being held and an owner/moderator notice of the held message are two separate things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/27/22 05:22, Stephan Krinetzki wrote: > > I think there is a communication problem in the chain: > > apache -> uwsgi -> mailmancore/API ->database > > but i can't dig deeper there. Let me know if i should provide more details or logs It seems that this part of the chain apache -> uwsgi -> mailmancore/API is not experiencing delay. It is involved with every Postorius request, most of which seem to have no issues. It is only this one piece mailmancore/API ->database that seems to have an issue and only with this one DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX query. However, like you, I have no idea as to what you could do further to debug this. -- 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

Search results for query "sapiro"