Search results for "Postorius" - Mailman-users

Re: Apache Configuration for Subdomain

by Mark Sapiro

On 7/26/22 14:20, Mail Person wrote: > Ok, progress with tinkering some. Using the below configuration I can manually navigate to lists.example.com/mailman3/postorius/lists/ and all is working fine. If I go to lists.example.com/mailman3 it for some reason redirects to lists.example.com/mailman/postorius/lists/ which generates a 404. This is a uWSGI issue. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost Others have found that changing this to ``` ProxyPass /mailman3/ unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ``` fixes it. Note the added slashes after `mailman3` and `localhost`. See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Going to lists.example.com also hits a 404. Here > RewriteEngine on > RewriteCond %{SERVER_NAME} =lists.example.com [OR] > RewriteCond %{SERVER_NAME} =www.lists.example.com > RewriteRule ^ https://%%7BSERVER_NAME%7D%%7BREQUEST_URI%7D [END,NE,R=permanent] You're redirecting http to https, but have you defined a VirtualHost for port 443? Just copy your <VirtualHost *:80> block to a <VirtualHost *:443> block. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 4:42 PM, Peter Adebahr via Mailman-users wrote: > > I have a fresh setup of MM3 on Ubuntu 20, installed by apt-get. It seems > to be running fine so far, except for some (to me) strange behaviour: > > When posting to the list as a non-subscriber, I see the mail coming in > on mailman's smtp.log, then it vanishes. No notice of this mail being > hold is sent to the sender, no notice to the moderator, and logging into > Postorius as owner of the list, it is not showing up in "Held messages" > > "Hold for moderation" has been set. Set in "Default action to take when a non-member posts to the list"? If that is the case, find the non-member in Users -> Non-Members and look at the Non-member Options link. What is the "Administration options Moderation" setting? for that non-member? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Re: Mailman not able to process "big" requests

by Darren Smith

Our installation at https://lists.rootsweb.ancestry.com has around 33,000 lists and somewhere around 1.5 million members. We have lists with 5,000+ members. Note that I haven't tried any mass subscriptions. When we upgraded from mailman 2 to mailman 3, we used the old .pck files and ran the import on each of the lists. It did take about 6 weeks to do the full import all 33,000 lists. I'm not joking. As for sending messages - there isn't any problem sending that many messages out, but then we are also not trying to subscribe list members at the time. We are, though, in the process of importing the old archives from our old mailman 2 system. This doesn't seem to affect the rest of the system. We have seen some inefficiencies in the new system, such as the front page of postorius - loading all of the information for 200 lists (if the user set the "lists per page" to 200) was bringing down the system. We have our own metadata system to be able to search for lists by state/region/surname (ours is a genealogy mailing list system), so we had to replace the front page with our own "find a list" functionality. The other main problem was the page where a user can see what lists they subscribe to. That page was also a denial of service if the user had several hundred lists they are subscribed to. And for a genealogy mailing list system, this is common. We have actually ended up creating our own API layer (only accessible on the local machine) and make certain calls to it for the most painful of the issues. One of these days (when we get a moment to breathe) we are going to post some of our changes to the project so that we can ditch our own API and just use the internal REST API. To be fair, the inefficiencies are not necessarily with mailman or the rest API itself - but with Postorius making hundreds of calls to load a single page. Though if the API supported loading multiple lists at once instead of having to load them serially, that might help as well. So while we have not seen any timeout issues on the call to mass subscribe users, we HAVE found several other calls that are effectively a denial of service and have gotten around them ourselves, with plans to contribute to the project in the near future. -Darren On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/24/2018 12:36 AM, Abhilash Raj wrote: > > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > > >> We also have a problem with sending out emails to "large" (>50) groups, > >> as they seem to not getting sent out at all. Do you have any idea what > >> the problem here could be? > > > > Which MTA are you using? What do you see in mailman's logs and MTA's > logs? > > > > I haven't seen this kind of problem before with Mailman 3. This very > list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > > Nor have I seen this issue. This list currently has 158 non-digest > members. There are several @python.org Mailman 3 lists with over 100 > non-digest members including the active yt-users(a)python.org list with > 301 members, and I have gotten no reports of an issue like this. > > Also, there are over 600 lists at <https://lists.fedoraproject.org/>, > and I don't think this is an issue there either. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years

Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 6:50 PM, Mark Sapiro wrote: > On 3/20/19 5:43 PM, Ralph Seichter wrote: >> With archiving enabled, mail is sent with headers like the following: >> >> Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> >> List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> >> List-Post: <mailto:foo-users@lists.example.com> >> List-Subscribe: <mailto:foo-users-join@lists.example.com> ... > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ > > Then at https://lists.example.com/postorius/domains/, the Web Host for > the example.com domain needs to be lists.example.com I didn't look carefully enough at your example. If the mailto: links are @lists.example.com, then that is the Mail Host at https://lists.example.com/postorius/domains/ for which the Web Host needs to be lists.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

Re: mailman-web: ResponseNotReady

by Erin Justice

This looks similar to what I got when I installed mailman using sudo but then tried to start it using my standard user. I don't have a working install of mailman 3 at the moment to try it again for sure. -Erin > On Oct 18, 2017, at 9:00 AM, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > > > We've had an odd experience with mailman3 containers: > > ERROR 2017-10-18 15:47:09,448 60 django.request Internal Server Error: > /postorius/lists/ > Traceback (most recent call last): > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", > line 39, in inner > response = get_response(request) > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", > line 249, in _legacy_get_response > response = self._get_response(request) > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", > line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File > "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", > line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", > line 590, in list_index > choosable_domains = _get_choosable_domains(request) > File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", > line 524, in _get_choosable_domains > return [(d.mail_host, d.mail_host) for d in domains] > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 217, in __getattr__ > return self._get(name) > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 183, in _get > return self.rest_data.get(key) > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 172, in rest_data > response, content = self._connection.call(self._url) > File > "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line > 109, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", > line 1659, in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", > line 1399, in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", > line 1355, in _conn_request > response = conn.getresponse() > File "/usr/local/lib/python2.7/httplib.py", line 1108, in getresponse > raise ResponseNotReady() > ResponseNotReady > > It seems like mailman-core is still operating properly, but for some > reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? > > -- > Sr System and DevOps Engineer SoM IRT > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years, 6 months

Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Franklin Weng

Hi Stephen, Thanks for your explanation. Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> 於 2019年10月29日週二下午1:35寫道： > Franklin Weng writes: > > > However in the Archive section I couldn't see anything and all the > > lists were "inactive" and hence were hidden by default. > > If you can see that much, HyperKitty is running. > > Have you sent mail to the lists? Has it been delivered to subscribers? > Yes, mails to subscribers were delivered successfully. > > I confirmed that api_key set in the /etc/mailman3/mailman-hyperkitty.cfg > > and /etc/mailman3/mailman-web.py is the same. I also confirmed that the > > apache2 wsgi module has been loaded. > > > > In the mailman.cfg database is set to mysql and in the mailman-web.py > > database is set to sqlite3. Does it matter? > > I don't think they need to be the same. The HyperKitty and Postorius > databases are a Django database backed by an RDBMS (typically sqlite3, > PostgreSQL, or MySQL). The databases used by the Mailman core and the > Django webservices HyperKitty and Postorius are conceptually separate, > although they can be backed by the same RDBMS server. > As Tamas has said in the previous reply, my mailman is a fresh new install on Debian buster. I followed Debian.README and didn't change much. In Debian's setting, under /usr/share/mailman3-web/ are these files: manage.py settings_local.py -> /etc/mailman3/mailman-web.py settings_local.py.sample settings.py urls.py wsgi.py In the top of settings_locas.py there are comments saying that this file is to override default settings in /usr/share/mailman3-web/settings.py, so I suppose hyperkitty database should define here, though it is different from /usr/share/mailman3-web/settings.py. > > However, sqlite3 is likely to result in poor performance compared to > PostgreSQL or MySQL. > > You have to configure HyperKitty's database. In my sqlite3 test > installation it looks like this: > > # Top of settings.py. BASE_DIR is the directory containing settings.py. > BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__))) > > # 30-50 lines later: > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.sqlite3', > # This database file is in the same directory as settings.py. > 'NAME': os.path.join(BASE_DIR, 'hyperkitty.db'), > # Not used with sqlite3: > 'USER': '', > 'PASSWORD': '', > 'HOST': '', > 'PORT': '', > } > } > > Does the database file named by 'NAME' exist? > In the settings_local.py, it defines sqliet3 and the file of 'NAME' /var/lib/mailman3/web/mailman3web.db exists and is a sqlite3 format file. But in settings.py (which is supposed to be overridden by setting_local.py) it defines using postgresql, which doesn't exist in my Debian system. > There is no systemd service for Hyperkitty. > systemd runs Apache, which loads mod_wsgi, which runs Python, which > imports the HyperKitty package, which responds to web requests by > building pages dynamically using Django from information from Django's > database, which may be backed by MySQL, PostgreSQL, or sqlite3. > Sounds complicated, but it performs well once you get it properly > configured. Is there any log I can trace the executing path? It looks not complicated but I didn't know and couldn't find out how to check if it works correctly. For Apache2 mod_wsgi, the wsgi.conf in mods-enabled does not enable any configuration (all commented out) and when I use ps to check, uwsgi runs as: 14233 ? Ss 0:01 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini 14236 ? Sl 0:00 /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini The /var/log/mailman3/web/mailman-web.log is at https://pastebin.com/U3jHR6JS There seems to be something running but in the interface I still didn't see any results. Franklin

6 years, 6 months

Re: Where do I find the bounced messages?

by Mark Sapiro

On 12/20/22 02:29, Sörös Zoltán wrote: > Greetings, > I am running several lists under mailman3. I am getting notifications > about users being put on nomail because of their bounces - but I can > find no way to actually see the bounced messages. > > Do mailman3 store the received bounces? Where? They are stored in the message store in the database but only temporarily. > Is there any setting to forward these bounces to the list owner? There are two relevant settings. These are exposed in Postorius -> Settings -> Bounce Processing. They are: Notify owner on bounce increment - sends a notice to the owner including the DSN when a user's bounce score is incremented, but to a value less than the bounce threshold. Notify owner on disable - sends a notice to the owner including the DSN when a member's subscription is automatically disabled due to the bounce threshold being reached. -- 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

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:58 PM, David Newman wrote: > > On 1/14/22 6:35 PM, Mark Sapiro wrote: >> >> The place for feature requests for Mailman core (which this is) is >> https://gitlab.com/mailman/mailman/-/issues, however, this is not >> straightforward as Mailman core doesn't know if you even have >> Postorius or some other web management UI installed or what the URL to >> access it might be. Thus it's not just a simple matter of editing >> templates. It would also require a configuration setting for the base >> URL for the web admin UI and changes in logic to provide an >> appropriate replacement depending on whether or not the base URL was >> configured. > > Understood, thanks. Although this distinction is very important for > server admins, it's likely not meaningful for many list owners and > moderators. For them, MM2.1 sent an email saying "go here" and > MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. > > There is some pending template in use by default, just not one with a > URL included. All the templates have defaults and the defaults don't have URLs because these are unknown to core. > Is this something better handled in the venv and/or Web installation > docs? Or should I file a feature request for core, or Postorious or > someplace else? I think a feature request for core is appropriate. I'm only saying implementing this is a non-trivial change. What I do on sites I admin is put custom versions of all these domain:admin:notice:new-list.txt list:admin:action:post.txt list:admin:action:subscribe.txt list:admin:action:unsubscribe.txt list:admin:notice:pending.txt list:member:digest:footer.txt list:member:digest:masthead.txt list:member:regular:footer.txt list:user:action:invite.txt list:user:action:subscribe.txt list:user:action:unsubscribe.txt list:user:notice:post.txt list:user:notice:probe.txt list:user:notice:welcome.txt in /opt/mailman/mm/var/templates/site/en and at mail.python.org which also has German language lists, in /opt/mailman/mm/var/templates/site/de. That could be documented, but it would be preferable to be able to document just a base web management URL and then put a replacement such as $web_ui in the default templates and replace that with a URL if configured or some generic text otherwise. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Converting non-members to members

by Alan So

Postorius is not currently exposing non-members management. Our Mailman 2 users are currently using accept_these_nonmembers, hold_these_nonmembers and reject_these_nonmembers. We know that mailman import21 will change these to nonmembers entries in Mailman 3. Since list owners will still want to manage them, we tend to move all of them to members and turn off delivery status for them. However, we met some difficulties when we try to develop using mailman client. 1) If those non-members addresses already exist as members, we will encounter error when we subscribe for them: urllib.error.HTTPError: HTTP Error 409: b'Member already subscribed' 2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: moderation_action' 3) We cannot change the preference: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: delivery_status' Are there any better ways to enable the list owners to manage those previously configured nonmembers' addresses through the web? Otherwise, we probably need to have some manual effort to overcome the above three issues. We know that we can always do the above manually but we got a lot of lists to migrate to Mailman 3.

7 years, 4 months

Re: howto reallow a banned email ?

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: >> >> By mistake a user has been banned to post to mailman list. How can I >> allow him not only to post but also to become a member of a list ? >> >> I have not found any info on the web, or I have been unable to search >> correctly. > > > Do you have the Postorius web UI in your installation? If so go to the > list's Ban List and remove the unwanted entry. > > Or is this perhaps a Mailman 2 question? If so you'll find the ban_list > in the web admin UI at Privacy options... -> Subscription rules.

6 years, 10 months

Mailman-users search results for query "Postorius"