Search results for "Postorius" - Mailman-users

Re: Assistance with mailman3

by Andy Yen

Hi Abhilash Thanks for the response. Tried your suggestion I ran the command "pip install -U falcon==1.4.1" and started mailman but still getting same error. ==> var/logs/mailman.log <== Mar 15 10:10:43 2019 (3004) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ return super().__call__(environ, start_response) File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line 248, in __call__ responder, params, resource, req.uri_template = self._get_responder(req) File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line 664, in _get_responder route = self._router_search(path, req=req) TypeError: find() got an unexpected keyword argument 'req' Mar 15 10:10:43 2019 (3004) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 Kind regards Andy On Wed, Mar 13, 2019 at 12:51 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Mar 13, 2019, at 8:47 AM, ayen(a)afilias.info wrote: > > Hi all > > > > I'm pretty new to mailman but been trying to install mailman 3 and been > > running into issues, following the documentation at > > http://docs.mailman3.org/en/latest/prodsetup.html > > installed Python 3.6, nginx, ruby-sass > > then with pip installed whoosh mailman-hyperkitty postorius hyperkitty > > mailman > > > > tried to start mailman core, symlinked master and runner -> /usr/bin/ > > (otherwise it wouldn't run) > > mailman core starts but when I hit the api url I get this in the logs > > > > File > > > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", > line 50, in wrapper > > rtn = function(*args, **kws) > > File > > > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", > line 218, in __call__ > > return super().__call__(environ, start_response) > > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > > 248, in __call__ > > responder, params, resource, req.uri_template = > > self._get_responder(req) > > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > > 664, in _get_responder > > route = self._router_search(path, req=req) > > TypeError: find() got an unexpected keyword argument 'req' > > Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 > > > > and on frontend "A server error occurred. Please contact the > administrator." > > Inside your virtualenv, please run: > > $ pip install -U falcon==1.4.1 > > This should fix the above error. > > > > > that leads to my gnu not working and throwing keyerrors for postorius. > > > > I'm using a clean install of ubuntu 18.04 but have also tried to > > install on centos 7 with no success. > > > > Are there any missing dependencies or steps that I've missed any > > assistance would be appreciated. > > > > Andy > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > thanks, > Abhilash Raj (maxking) >

7 years, 4 months

Re: old usernames appearing in mailman.log

by Ken Alker

--On Monday, June 26, 2023 5:03 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 10:57 PM, Ken Alker wrote: >> >> I have studied the output, looked at the code lines referenced in the >> Traceback, and I can't figure out the problem (I feel like the sad guy >> on the side of the street with his hood up staring into the engine bay >> with stream pouring out and not knowing what to do next). I did some >> analyses on the log file and determined that there are 71 messages it is >> having problems processing and there are 71 messages "stuck" in >> /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to >> process each message about 20 times). > > > Each time there is a new post, it retries all the messages in the spool/ > directory. > > >> Since upgrading to V3.3.8 I've >> not seen new messages get stuck like this (although it's only been >> running smoothly for 24 hours now and there hasn't been much activity). >> But I'm suspecting there was something awry between the conversion from >> V2 to V3 in February and me installing V3.3.8 that caused this (based on >> message time stamps). It is HIGHLY likely these messages are in the >> archiving spool as a result of me unshunting the shunt queue and that >> they are copies of the messages that got delivered to the subscribers >> when I did that... but are now hung up in the archiving process. > > > Are new messages being archived OK. If so, that is a real mystery. It > says mailman-hyperkitty can talk to hyperkitty and archive new messages, > but it can't talk to hyperkitty when attempting to process a queued > message. Ahhh! I had convinced myself that new messages were being archived, but now that you ask, they ARE NOT. I may have said they were at some point, and I apologize if I did. Now I feel less confused. It appears that archiving stopped when I did the migration from "Debian package layout" to "source layout" and upgraded to V3.3.8. I'll bet I munged a config file or two. I was struggling with what to keep from Debian layout and what to bring over from the source install instructions and I haven't gone back through to clean them up. I had previously figured it could not be a configuration issue since some messages were making it into the archive and some were not, but now that I see NONE are making it, this makes the problem less daunting. >> Following is an excerpt from mailman.log. Note that the "first >> section" (from DOCTYPE at top to 404 at bottom) is repeated four times >> (maybe not identical; but similar) (so I did not include it to save >> room) before the Traceback appears. >> >> Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list >> found >> Jun 25 00:13:04 2023 (386086) ACCEPT: >> <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> >> Jun 25 00:13:04 2023 (386090) HyperKitty failure on >> https://lists.netlojix.com/hyperkitty/api/mailman/urls: > > I just went to that URL and got a 404. This is a serious problem. > https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should > return some documentation of the API. > > https://lists.netlojix.com/archives/api/ does work and returns the > expected information. > > Your urls.py file probably contains in its urlpatterns list > ``` > re_path(r'^mailman3/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ``` > The simplest fix is to add > ``` > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > ``` > to that list. I see many ursl.py files all over the system, but none that appear to be where I'd expect them to be for processing by any executables. Is this a file I should have copied over and edited, or created from scratch and somehow missed? I don't see anything about it in the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html> (although I do see a post from last July from someone stating it got missed in the instructions back then). > Another way to fix this is in your mailman-hyperkitty.cfg, you have > ``` > base_url: https://lists.netlojix.com/hyperkitty > ``` > Change that to > ``` > base_url: https://lists.netlojix.com/archives > ``` Done, and restarted both services, but I'm not seeing a difference when I go to <https://lists.netlojix.com/hyperkitty/api/> (I was getting a "Page not found", and still get that). > but it wouldn't hurt to add the `^postorius/` and `^hyperkitty/` patterns > to urls.py anyway.

3 years, 1 month

Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 7:03 PM, Paul Arenson wrote: > > MAILMAN 2 > What I got from the Mailman 2 Wiki is "How to restrict the list so only authorized persons can post (moderation). If there is an option like that in Mailman 3 I want that. There is, but you can't do it the best way. See below. > SUMMARY > I want to be able to reply personally to the user if necessary without his or her message going to the list. So something like moderation. > > So let me take a guess: > > Default action to take when a non-member posts to the list AND > Default action to take when a member posts to the list > > should be set to HOLD FOR MODERATION? That will work and is probably what you want anyway. Your own posts will also be held, but you can just accept them. Alternatively, you could set your own Moderation setting to Accept or Default Processing so your posts won't be held, but don't do that as it allows anyone to post by spoofing your address in From:, Sender: or Reply-To: or the envelope sender. The best way to post without the post being held is pre-approval with an Approved: <password> header, where <password> is the list's moderator_password, but you can't set that in postorius so it won't work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

Mailman 3 Container Images v0.1

by Abhilash Raj

Hi Everyone, I have been working on containerizing Mailman 3 so that it becomes easier to test and try Mailman 3. There are two images in total: * maxking/mailman-core : This consists of Mailman Core and includes the plugin to enable the Hyperkitty Archiver. * maxking/mailman-web : This consists of a full Django installation and run the Mailman's Web UI components. It has Mailman Client, Postorius & Hyperkitty. The images are built from the Dockerfiles hosted on Github[3] in case you want to look at it. You can find most of the documentation about these images at https://asynchronous.in/docker-mailman/. The version of the internal components included in each image is available here[7]. The images are versioned and the process is documented[4], please have a look before you use them. Also, the images are signed and I encourage you to verify them before using. The process of how-to verify is also documented. Docker Compose is a tool written in Python makes is very easy to deploy connected-images and take the pain out of writing long long commands for spinning of containers. There is a sample `docker-compose.yml` file in the Github repository mentioned above which is kind-of tested to be able to spin off these images in vanilla condition (without any customization/configuration). You can report issues, comments or concerns in the Github repo[6]. [1]: https://hub.docker.com/r/maxking/mailman-core/ [2]: https://hub.docker.com/r/maxking/mailman-web/ [3]: https://github.com/maxking/docker-mailman [4]: https://asynchronous.in/docker-mailman/#release [5]: http://semver.org/ [6]: https://github.com/maxking/docker-mailman/issues [7]: https://github.com/maxking/docker-mailman/wiki -- thanks, Abhilash Raj

9 years, 1 month

Re: Redundant and load balanced Mailman3

by Abhilash Raj

On Thu, Sep 17, 2020, at 8:31 AM, Pawel Grzywaczewski wrote: > Hi, > > Can someone share some hints about how to deploy redundant and load > balanced Mailman3? What are your recommendations and best practices? > For example what components to put on the same VM? Can we have 2VM with > Mailman core/Postorious/Hyperkitty/django-mailman/mailmanclient > connecting to one (the same) database? How to load balance mail routing > (incoming)? The current implementation of Mailman is good for vertical scaling but not that great for horizontal scaling and redundancy. The web frontend, Postorius & Hyperkitty, are pretty much stateless and can be horizontally scaled and redundantly deployed easily. I am not going to recommend how to handle redundancy for database, because I am not the best person for that and I honestly don't know anything beyond using a "cloud managed" database from cloud providers for HA. Mailman Core is a bit hard to run redundantly mostly because of it's reliance on filesystem for some data like email queues, held messages, shunted messages etc. You can potentially have two running instances, one on standby and failover to other instance. You'd need to synchronize the var directory between them using *some* mechanism, rsync or NFS or something. Although, you want to make sure that they both aren't sending out emails at the same time. > Thanks! > Paweł > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

Re: Special Characters Issue when using Wordpress HTML messages

by Mark Sapiro

On 3/22/22 07:46, ryan.anderson.4--- via Mailman-users wrote: > Hello, > > We are having trouble where we are using a WordPress server send messages our to a few of our lists as HTML embedded messages. We do not want the messages to be shown as Plaintext, so we have that setting turned off in WordPress and in all our lists' settings. You can accept HTML and not convert it if in Postorius -> Settings -> Alter Messages, assuming Filter content is yes, ensure Pass types includes `text/html` or maybe `text` to include all text maintypes and both Collapse alternatives and Convert html to plaintext are set to No. > The messages come through just fine, but several characters are being changed to "?". Some of these include ` and - . They probably aren't ` and -, but rather things like Unicode Left Single Quote and En Dash. > We recently upgraded from 2.1 to 3.3 and we love the new system, other than the fact that our news messages are looking bad because of all the "?" in them. The charset was set to US-ASCII, but I have changed it to UTF-8 and that has not seemed to do anything. When you say you changed the character set to UTF-8, what did you do? If you set ``` [language.en] charset: utf-8 ``` in mailman.cfg and restart mailman core, that should allow those characters without replacing them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: 404 on fresh install (Debian11)

by Jeremy Stanley

On 2023-03-23 09:07:02 -0700 (-0700), Mark Sapiro wrote: [...] > bookworm (testing) and sid (unstable) do have current versions of > Mailman core and django-mailman3 and possibly mailman3-web > 0+20200530-2.1 has current Postorius and HyperKitty, but those are > generally not the Debian packages that most users would install. And those will also become out of date over time, because Debian is a stable server distribution so intentionally freezes the versions of software it supplies and backports only critical/security fixes to those increasingly outdated versions when warranted. Basically it's a question of whether users value stability with a bit of security support over newest versions of software and new features. The upstream Mailman packages on PyPI (and container images) cater to users who want the latest versions of the software, packages in stable server distros like Debian cater to users who want to safely go years between behavior changes in software. Both are valid choices, it just comes down to the user's specific situation. That said, when you have trouble with the packaged versions of software in Debian, the expectation is that you ask on Debian mailing lists and possibly report bugs in the Debian bug tracker, rather than burdening upstream software maintainers with details that might be specific to choices or mistakes in Debian's packages. The package maintainers in Debian generally forward bug reports upstream if they determine the issue you've encountered isn't related to how it's been packaged, isn't already fixed upstream (in which case they might backport the fix), et cetera. -- Jeremy Stanley

3 years, 4 months

Re: Howto: Mass import of nonmembers in several lists?

by Mark Sapiro

On 1/10/22 4:00 AM, Paul Paulchen wrote: > > So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. > I thought so, because the import21 command did this as well when we migrated to mailman3. You could script it with `mailman shell`. If you really want this, I'll help. > I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. > But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! You can't without modifying the code. > Hope I explained my case properly. I appreciate your responds! Thanks in advance. My question is why do you want to add these nonmembers. The only thing gained by adding a nonmember is the ability to set the nonmember's moderation action to other than the default, and you can handle that with the legacy * these non-members settings which take priority over the nonmember's moderation action anyway. Note that if a nonmember posts to a list, she will automatically be added to the list as a nonmember with default moderation action if she isn't one of the list's nonmembers already. -- 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

Re: disabling social login

by Abhilash Raj

On Mon, Nov 6, 2017, at 10:26 AM, Simon Hanna wrote: > On 11/06/2017 07:22 PM, Dmitry Makovey wrote: > > Hi, I'm trying to disable social login and running into troubles > > stepping on it's remnants all over the place. What's the proper sequence > > for disabling social login in MM3 install? > comment out 'allauth.socialaccount' and all social providers in the > INSTALLED_APPS in your settings.py This apparently doesn't work, Hyperkitty apparently depends on this to do some stuff. I haven't dug up in there, but the migrations would break if we remove this from INSTALLED_APPS. Instead, please let the 'allauth.socialaccount' be there, along with 'allauth.account' and 'allauth' and everything else related to allauth should be removed. It looks something like this: ```` INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ) ``` I tested this works, see [1]. [1]: https://lists.araj.me/postorius/lists/ > They shouldn't be enabled by default in the first place I guess, since > pretty much all of them require further setup in order to work > properly... > > How are you running MM3? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 9 months

Re: Internal server error instead of web interface

by Odhiambo Washington

On Wed, Nov 5, 2025 at 1:44 PM Christian H. Kuhn via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi all, > > https://lists.qno.de/mailman3 shows an internal server error. > > I followed https://docs.mailman3.org/en/latest/install/virtualenv.html > with MariaDB instead of PostgreSQL. > > Python 3.13.0 > pip 25.3 > mailman 3.3.11b > mailman-web 0.0.10.dev14?g0997bd > postorius 1.3.13 > > Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi > listens on [::1]:8000, apache2 is configured accordingly. Ports show up > in netstat. > > No errors show in logs. > > If /mailman3 was a directory, i would have thought of user permission > problems. But not with TCP ports. > > As :8000 is available, i would have thought that there is a problem with > uwsgi. Requests arrive there and are processed: > > [pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov > 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs > (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0) > > So uwsgi gets the request and delivers data. The problem seems that > apache2 does not get the result, and i cannot find any reason. Any help? > What do you have in the log files for mailman, mailmanweb, and Apache2? -- 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]

9 months

Mailman-users search results for query "Postorius"