Search results for "Postorius" - Mailman-users

Re: Postorius endless loading on Sign in / Register then "Internal Server Error"

by Mark Sapiro

On 6/9/20 12:16 PM, Jacob Bargery wrote: > Pre-cursor, I am in a new position to learn on the go and new to Linux but have been tasked with setting up a List Serv and they wanted Mailman 3 with Postorius and HyperKitty. Running on Ubuntu 20.04 LTS using Postfix and MySQL. I can open up the initial pages. With no Lists created yet. I can open up Register, Login, and Forgot Password but when I submit anything it spins the loading icon for a long time then reads" > > "Internal Server Error > The server encountered an internal error or misconfiguration and was unable to complete your request. Apache/2.4.41 (Ubuntu) Server at groups.smccme.edu Port 80" ... > This is a traceback I could find from another attempt: > > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call > raise MailmanConnectionError('Could not connect to Mailman API') > mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API What are your Django settings for MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' Those match the defaults defined in mailman/config/schema.cfg [webservice] # The hostname at which admin web service resources are exposed. hostname: localhost # The port at which the admin web service resources are exposed. port: 8001 # Whether or not requests to the web service are secured through SSL. use_https: no # The administrative username. admin_user: restadmin # The administrative password. admin_pass: restpass If all that seems to match, what happens if you try telnet localhost 8001 If that doesn't work, but telnet 127.0.0.1 8001 works, there is some issue with `localhost` involving /etc/resolv.conf or /etc/hosts, most likely an ipv6 definition like ::1 localhost in the latter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

I did upgrade one of my mailman3 server after Abhilasj announcement: "I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 1 <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> 2. Postorius 1.3.7 2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5]" I did it via pip and all seems to be working, but when I try to discard or accept any message via postorius it shows a Forbidden 403 error CSRF verification failed. In my settings.py I have commented out these variables: # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' I've been messing with them whith no results. It's like it lacked some value in some template... Can someone, please, point me in the right direction? Thanks in advance -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 9 months

Re: When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.

by Mark Sapiro

On 10/30/19 2:08 AM, Henrik Rasmussen wrote: > > It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. That's probably correct, but not the exact reason. > However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. > > I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? To understand, you need a bit of background. The basic engine that manages lists, subscriptions, users, etc. is Mailman core. Core does not provide any web UI. It only provides a REST API for use by other components. It is possible to run Mailman core only without any web UI, but management would need to be done directly via the REST API and/or `mailman shell` which is not particularly convenient. Because Mailman would not be too useful without a web management UI and a web based archiver, we provide Postorius and HyperKitty for these functions. These are only one possibility. One could build an entirely different web UI or other application to communicate with core via its REST API, but few if any have done so. Postorius and HyperKitty are Django projects and run under Django. The account that you see (Postorius top right) is a Django account. Core knows nothing about this. Core knows about users and addresses in its own database which is entirely separate from Django's accounts. These user/address records in core is where the user's display_name is kept. So when a user/address is added to a list, if core already knows that user/address, it just links that to the list and doesn't update the display_name, but if it doesn't know the user/address, it creates it and uses the supplies display name. It appears there is a mechanism within Postorius to detect a change in the name associated with a Django user and update core, but this is separate from subscribing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Using REST api to subscribe member

by Brian Carpenter

I have a development server that only has Mailman core installed on it. I used a virtual environment to do the installation but I did not install Postorius or Hyperkitty as I am currently working on developing a custom u.i. for Mailman 3. My programmer said the following: "I have a problem with mailman on development server ... I was trying to add member to a list using REST api, but to no avail. After I tried all possible and impossible things, I finally looked at the logs. Error I found in log file is: IsADirectoryError: [Errno 21] Is a directory: '/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/templates' I guess mailman was looking for a template for welcome mail, and failed for some reason. I also guess this has something to do with locale or language settings I tried googling, but couldn't find anything" The log that gave the error was /opt/mailman/mm/logs/mailman.log My programmer tried it on another server that has both Postorius and Hyperkitty working and the api call worked, i.e. added the member to the list and sent out a welcome email. So what else do I need to install to be able to use the api to add members to a list using a non-postorius interface? Any assistance would be appreciated. Thanks, Brian

5 years, 4 months

Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/6/24 1:33 AM, Odhiambo Washington wrote: > > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > >> Odhiambo Washington writes: > >> > >> > The odd thing is that the HOWTO that he followed never involves the > >> > manipulation of any urls.py at all - it's not even mentioned at any > >> > point. So obviously the issue is caused by something else and I > >> > suspect something within Apache needs to be re-evaluated in the > >> > guide. > > > The HOWTO installs mailman-web which contains a urls.py. > > >> > >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" > >> URI paths. It is quite unclear to me how this works at all with > >> either the > >> > >> path('mailman3/', include('postorius.urls')), > >> path('archives/', include('hyperkitty.urls')), > >> path('postorius/', include('postorius.urls')), > >> path('hyperkitty/', include('hyperkitty.urls')), > >> > >> version of urls.py or the reverse order version > >> > >> path('postorius/', include('postorius.urls')), > >> path('hyperkitty/', include('hyperkitty.urls')), > >> path('mailman3/', include('postorius.urls')), > >> path('archives/', include('hyperkitty.urls')), > > > This is an issue with Django. I'm not sure of the exact mechanism, but > consider the first of the above two sets. If you go to the mailman3/ URL > that gets redirected to the postorius/ URL. I.e. two paths that > ultimately reference the same thing wind up considering the second path > as the canonical path and redirecting the first path to the second. > > I was not initially aware of this when I added the postorius/ and > hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of > making either set of paths work, and I added those paths after the > mailman3/ and archives/ paths, and this version got released as > mailman-web 0.0.8. That caused the recommended Apache config to fail > because now the mailman3/ and archives/ paths were redirected to the > postorius/ and hyperkitty/ URLs which are not in the recommended Apache > config. > > I have since reordered the paths in mailman_web/urls.py, but that > version isn't yet released. Thus the issue. See > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for some background. > > > > My thinking then is that the documentation at > > > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > > needs to be fixed by adding the missing bits, > > > What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will > fix the issue. > Hi Mark, Thank you for making it much clearer. Is it possible that an Apache directive like below will fix everything (albeit discreetly with sysadmins driving blindly)? ProxyPass "/" "http://127.0.0.1:8000/" As was suggested by Mr. Turnbull (and previously by you on another thread)? It will be simpler, but leaves almost everyone (except the Devs) blind to the fact there exists a urls.py somewhere that determines the mappings? Maybe a note about it in the documentation will help? -- 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, 4 months

MM3 Bounces status

by Ruth Ivimey-Cook

Hi, I have some lists which are used primarily as a distribution method (rather than chat) and the person who uses these lists doesn't have access to the detailed MM logs and is not interested in that. It would be very helpful for message bounces (& any other anomalous events, if any) were to be available to that person for each message that is sent out, in a manner similar to mailgun et al. I know something of the bounce processing MM3 does, but it seems to be totally hidden from e.g. the postorius end of things (unless I'm missing something?). Is there a way for bounce events to be emailed to the list owner, or for something to be available in postorius to show this info? If not in the standard package, do other people have ad-hoc solutions to this issue? My ideal option would be for a configurable per-message email or postorius link that reports the number of emails to send (=number in mlist), the number on 'no-mail', the number sent successfully (=no bounce?), the emails of those who bounced (with bounce score), and emails of blocked sends (eg by multiple bounces). So for example: Bounce report for listname: Email Subject: Announcement Sent: today at time From Email: user(a)example.com received (today at time) To List: listname(a)example.com with 100 subscribers; 89 successful; 4 bounces; 3 blocks; 4 nomail; Bounces: - foo(a)bar.example.com (no mailbox) - bar23(a)foo.example.com (timeout) - alice(a)baz.example.org (mailbox full) - bob(a)example.net (bounce-reason) Blocked: - foo(a)bob.example.com (score 3) - bar23(a)alice.example.com (admin ban) - alice(a)alice.example.org (score 2) I suspect that my ideal option would require changes to the internal processing, because MM would need to keep more information about bounces than I think it currently does. It might also need to retain more information about LMTP delivery statuses? Thanks in hope? Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog:http://www.ivimey.org/blog LinkedIn:http://uk.linkedin.com/in/ruthivimeycook/

10 months, 1 week

Re: First time mailman installation

by Roland Giesler

On 2024/07/25 08:51, Odhiambo Washington wrote: > On Wed, Jul 24, 2024 at 12:23 AM roland--- via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > I have installed mailman3 on Ubuntu including postorius & > hyperkitty (from the packages). > > I have questions now which are not quite clear to me from the docs: > > > Hi Roland, > > Which guide did you use to install mailman3? I simply installed it from Ubuntu packages. > > 1. How do I specify my mail server details (which is my own server > running postfix, etc) > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… That is a guide that provides basic info, but there's not reference to secure protocols, so I suppose it's just a bit dated. I have a great, secure couple of server (running power-mail-in-box), so I don't want to venture into the manual mail-server setup territory, with all it's accompanying spam and security requirements. The mailings list should just use one (or more) or those servers. As I have written in another post I made, I have set the (apparently) appropriate parameters in the mailman.cfg, but I still get "relay access denied" from my external MTA, which mean that authentication is not even attempted, or am I mistaken? > 2. How do I create new lists from the postorius UI, or can I only > do that in the config files or the command line console for mailman3? > > > Once everything is up and running and you have the Postorius UI, you > can always use the Django Admin interface to manage stuff. > It's available at https://FQDN-FOR-YOUR-SITE/admin > <https://FQDN-FOR-YOUR-SITE/admin>. > How do you log in? You create a "superuser" account using CLI, then > use it. Now that depends on how you installed MM3. I figured that out already. Thank you. Roland

1 year

Mailman Suite release announcement

by Abhilash Raj

Hi All, I am pleased to announce new releases for Mailman Suite, including - Mailman Core 3.3.0 (Tom Swayer) - Mailmanclient 3.3.0 - django-mailman3 1.3.0 - Postorius 1.3.0 - Hyperkitty 1.3.0 This is a feature release and also includes a bunch of bugfixes. I am really really thankful to a lot of contributors who have helped out with this release. It is really nice to see Mailman 3 gaining more users and contributors. Python 3.5 is the minimum supported version, but all the releases have been tested to work with Python 3.5-3.7. This is the last release to support Python 3.5 since it has been in security only maintenance mode for a while now. Some of the highlights of this release includes: Mailman Core 3.3.0 - Support for ARC signing. Thanks to Gene Shuman and Stephen Turnbull. - Many many improvements to "mailman import21" command. Thanks to Mark Sapiro. - Addition of French templates. Thanks to Stéphane Parunakian. - A better and more scalable REST API server using Gunicorn. - Support for SMTPS/STARTTLS. Thanks to J08ny. A full copy of change log is available at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html Postorius 1.3.0 - Many more settings for MailingList configuration exposed, including preferred language, digest related settings. - Support for FILTER_VHOST to filter MailingLists based on the serving domain. Thanks to Nate Coraor. - Ability to write MailingList info in Markdown to render info in HTML instead of Plaintext. A full copy of change log is available at: https://postorius.readthedocs.io/en/latest/news.html Hyperkitty 1.3.0 - Unread messages, when logged in, are more easily recognizable with blue envelope icon. - Improved thread view with colored background for quoted parts of messages. - Improved readability on small screens by removing the indentation in thread view. A full copy of the change log is available at: https://hyperkitty.readthedocs.io/en/latest/news.html All the packages are available to download from PyPi (https://pypi.org) https://pypi.org/project/postorius/ https://pypi.org/project/hyperkitty/ https://pypi.org/project/django-mailman3/ https://pypi.org/project/mailman/ https://pypi.org/project/mailmanclient/ -- thanks, Abhilash Raj (maxking)

5 years, 10 months

Postorius List members

by Alain D D Williams

I have a test list with a few members. For each member it is showing me: Address, Delivery mode, Moderation action, bounce score. It is NOT showing Delivery status (Enabled, Disabled, Disabled by owner, ...). The only way of seeing this is by clicking on the email address (Subscription options). Is it possible to add delivery status to the summary where many users are shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of what is happening to users. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

8 months, 2 weeks

Re: postorius not displaying mailman logo

by Mark Sapiro

On 3/22/22 02:34, sekamug--- via Mailman-users wrote: > it seems the browser fails to access the directory where the pictures are stored. I have checked and mailman is the owner of that directory. The static directory is accessed directly from your web server, not via proxy to some wsgi server. For example, this list's web UI is served via nginx and we have the equivalent of ``` location /static/ { alias /opt/mailman/web/static/; } ``` For apache, something like ``` Alias /static/ /opt/mailman/web/static/ <Directory "/opt/mailman/web/static/"> Require all granted </Directory> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Mailman-users search results for query "Postorius"