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

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Dan Caballero

> But I am confused as to your goal. Previously when the list was > anonymous, all replies went to the list. Maybe your goal is to have list > replies be addressed to <list-name(a)caltech.edu> rather than Last Name, > First Name via list-name <list-name(a)caltech.edu>. If that is the goal, > you could try setting Reply goes to list setting to Reply goes to list. > That will set a Reply-To: list's short description > <list-name(a)caltech.edu>. That may be what you want as long as the > responder's MUA honors Reply-To: over From: > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Thanks. I had forgot to mention that we did also configure the DMARC mitigation to show the sender's email. You're correct about us looking to set the "reply-to" to the list address instead of the sender. I've done some testing and this is close to what we need. However, I seem to be having an issue with the option for "Explicit Reply-to set; no Cc added". The messages are still including a Cc field with the sender's email. Is there another setting that affects the Cc field? Thanks again.

9 months, 3 weeks

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Stephen J. Turnbull

Mark Sapiro writes: > Then the people who developed the web based management UI (Postorius) > and archive UI (HyperKitty) chose to develop those within a Django > framework and Django has its own concept of User separate from Mailman > Core and that is where the disconnect occurs. > > It's not that Mailman Core lacks what you want. It's that Django doesn't > use it. I think that's mostly right, in terms of the features that users miss. However, as far as I know, Mailman core does lack facilities for identification, authentication, and authorization of connections to the REST API. And that means that the front ends have to handle this. I would guess that's why the web interfaces are built around Django user authentication. I think it would be possible to have somewhat tighter integration between the Django "web users" and the Mailman core User objects, but it's not necessarily going to be trivial. I see that Abhilash is pretty optimistic, but I fear this this is going to be a long-tail situation where we're going to be seeing core user vs. web-gui user integration issues in 2030 (maybe by then only 1 every 450 days ;-). I have some ideas, maybe in a couple weeks I can sketch them out. Steve

5 years, 9 months

[MM3-users] Re: customized welcome message

by Nils

On 12/7/23 22:40, Mark Sapiro wrote: > How and to what did you set the URL for the template? What does the > database query > > SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; > > show? http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD This value can't work. Now it makes sense that it gets redirected and the use of localhost also explains why it didn't show in any of the virtual hosts log files that I was checking until it was redirected. However, I didn't set that value. I edited the template at postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can just select a template type and then I get one textarea input field for the content. The value in the database is set automatically, when I create a template in postorius (and is also automatically removed when I delete a template there). I can't edit this value without manually changing it in the database. > This is very old. Current Postorius is 1.3.10. 1.2.4 is from February > 2019. The Debian/Ubuntu packages are out of date. We recommend > installing via the doc at > https://docs.mailman3.org/en/latest/install/virtualenv.html The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) very soon. The Debian/Ubuntu packages sure have their downsides but once they work, they update automatically and require very little maintenance.

2 years, 3 months

[MM3-users] Re: Hyperkitty messages stuck in spool

by Andrew Hodgson

Stephen J. Turnbull wrote: >Mark Sapiro writes: > > On 11/18/21 6:38 AM, Andrew Hodgson wrote: > > > > > > Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? > > > > I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. > >If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. Thanks. Andrew.

4 years, 4 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 9:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/25/22 01:14, Odhiambo Washington wrote: > > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > >> > > > > I have uncommented the line "WSGIScriptAlias /user-profile > > /opt/mailman/mm/wsgi.py", > > I don't see any definition for it in urls.py as well. Perhaps that's the > > issue? > > > It is defined in django_mailman3/urls.py which is referenced by > > re_path(r'', include('django_mailman3.urls')), > I have seen that now. > > When I uncomment /user-profile, I end up with an ugly URL: > > https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ > > > > So instead of aliasing the /user-profile, I have decided to add another > > definition to urls.py: > > re_path(r'^user-profile/', include('allauth.urls')), > > Which I think gives me a cleaner URL: > > https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ > > It shouldn't include `allauth.urls`. That URL is appropriate if you > aren't logged in, but what do you get when you are? > > Go to https://lists.mailman3.org/user-profile/ and log in if necessary > and you'll see what it should look like. > Here when I log in. I land on the /archives ( https://lists.mailman3.org/archives/?sort=popular) I then head to the dropdown and click "Account " and I am taken to https://lists.mailman3.org/user-profile/ (very clean URL!) and that's the same thing I am seeing on my server at the moment.. When I comment out the edit I had on /etc/mailman3/urls.py and uncomment to /user-profile alias in the VHOST, I end up with 1. https://mm3-lists.kictanet.or.ke/user-profile/mailman3/lists/ - once I am logged in 2. https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ - when I click on "Account " # I hope you can see the duplication of /user-profile, which is ugly. However, your server isn't using mod_wsgi, I believe, so I shouldn't be comparing it to mine. I just don't like the extra URLs being added. > I also had to alias /accounts, which then brings me to: > > https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I > believe > > is fine because one gets the > > option to either login or signup. > > > > And I think that "/account" and "/user-profile" are synonymous. > > They are in your instance because of > > re_path(r'^user-profile/', include('allauth.urls')), > > but they should not be. > I have changed that, as already pointed out, but with consequences :) There must be a way to not have "/user-profile/user-profile" > >> It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time > >> (I now use gunicorn on all the sites I manage), but when I did I think I > >> had > > > > > >> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > >> > >> and all the URLs were like https://example.com/mm3/mailman3/..., > >> https://example.com/mm3/archives/..., etc. > >> > > > > I already had gunicorn working too, but I just need to also figure out > this > > mod_wsgi. > > > Why? Intellectual curiosity or do you have an actual need. > It's out of intellectual curiosity actually. The bottom line is with mod_wsgi, whatever you have in your > WSGIScriptAlias is going to be prepended to the URL path. If you don't > want anything prepended, you need > ``` > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > ``` > but then in order for user-profile to work, you need to replace > ``` > re_path(r'', include('django_mailman3.urls')), > ``` > in urls.py with the urlpatterns from django_mailman3/urls.py > ``` > re_path(r'^user-profile/delete$', delete_account, > name='mm_user_account_delete'), > re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), > ``` > and also add > ``` > from django_mailman3.views.profile import delete_account, user_profile > ``` > to the imports in urls.py > And with that, I am now happy with what I am seeing. Again, thank you very much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: [Mailman-Users] Web interface for users (not admins)?

by Stephen J. Turnbull

Mark Sapiro writes: > No, Posting from HyperKitty without using the "Use email software" > button is plain text only. That surprised me. There is the possibility of enabling Markdown in the viewer, but that's not a real solution for atechnical users who are used to mousing around, and by itself doesn't enable attachments. > There is no plan to add any sort of rich text capability. That doesn't surprise me. A number of things are possible, but I think that providing the mailto link give the atechnical user the best of both worlds: a quick text-based response or the comfort (? :-þ) of their usual mail client. One constraint that we have is that many of our users value "no Javascript" quite highly, so just dropping in the Electron-based editor du jour is something we don't want to do. By the way, Skip, if you decide that richtext followups are an important feature, earlier I mentioned EMWD's commercial offerings Affinity (for admin) and Empathy (for archiving). I don't know if Empathy offers more features for posting than HyperKitty does, but I encourage you to check with Brian Carpenter <brian(a)emwd.com>. These are commercial, closed-source (at least for now) offerings, but I believe rates are reasonable and support has a very good reputation. Regards, Steve

4 years, 10 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Wed, Dec 14, 2022 at 8:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > 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 lack of style is the main issue. > 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. > So I have tested this with Brave, Google Chrome, Firefox - all on MS Windows and I do clear the browser cache. > I don't know about the latter - could it be because all the archives are > private and I'm, not logged in? > Even when logged in, the situation is the same, unfortunately. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: Social signup?

by Duane Raymond

HI Mark, On Sun, 12 Mar 2023 at 22:06, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/12/23 13:56, Duane Raymond wrote: > > Is there a way to enable social signup (vs just login for existing > users)? > > It isn't at all clear or documented, but a user without an account can > go to the login page and login via a social account button and this will > create an account connected to that social account and log the user in. > Thanks for clarifying. Once I implemented social login, the buttons for social login did appear fine on the login page, but not on the signup page. I noticed for this list as well, there are no social signup buttons. So if it works, how does this happen? 1. Is there something I am missing adding to my settings.py and settings_local.py files to make it appear on the Posterius/Hyperkitty signup (vs login) page? (I searched but couldn't find anything) 2. Do I manually add this code to the Posterius/Hyperkitty signup template? 3. If a user tries to login via the login page and isn't registered will it be counted as a signup? 4. something else :-) I'm trying to get my head around where this is working from / what I need to do to get social signup obvious on the signup page (or other route) Cheers, Duane

3 years

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > We're really working on getting a consistent, workable installation > story and even getting some packaged solutions. I know we're not yet > there, but we're here to help when people run into problems. The site now works, but not the / url for the site. I get this error in the mailman-web.log (with a very long stacktrace before it) NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. 'hyperkitty.views.index.index' is not a valid view function or pattern name. I think that would correspond to this line in urls.py url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), but this corresponds exactly to what the example config says and I know of no other name for hyperkitty. Probably it is dependent upon understanding the url dispatching in Django but that takes some time to read up on. The interesting thing is that /archives works so it is just this redirect that has problems. I can probably get apache to do the redirect instead but that is not the most elegant solution. Then I of course have things to do on getting social logins to work. I currently get "DoesNotExist: SocialApp matching query does not exist." if trying to connect an account to google (which I started with). Not a showstopper as passwords do work. cheers // David

9 years

[MM3-users] Re: Where is postorius.wsgi?

by Peter Münster

On Thu, Jan 25 2018, Mark Sapiro wrote: > It's got a different name. It's in the above directory, at > example_project/wsgi.py Thank you. Unfortunately, it does not work... First I tried with python-3 (installed package was "apache2-mod_wsgi-python3"), but I got this error: Invalid command 'WSGIScriptAlias', perhaps misspelled or defined by a module n...ration Then, I tried with python-2 (installed package is now "apache2-mod_wsgi"), and this is the error message of apache: mod_wsgi (pid=18880): Target WSGI script '/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py' cannot be loaded as Python module. mod_wsgi (pid=18880): Exception occurred processing WSGI script '/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py'. Traceback (most recent call last): File "/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py", line 16, in <module> application = get_wsgi_application() File "/usr/lib/python2.7/site-packages/django/core/wsgi.py", line 14, in get_wsgi_application django.setup() File "/usr/lib/python2.7/site-packages/django/__init__.py", line 17, in setup configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup(name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) ImportError: No module named settings Could you help me please, to get Postorius working (and later also HyperKitty...)? TIA for your efforts, -- Peter

8 years, 2 months

Search results for query "sapiro"