Re: [Mailman-Users] Setting MM 3 attributes
On 2/27/20 10:18 PM, Mark Sapiro wrote: >>> Setting Maximum message size works in current Postorius. What version do >>> you have? >> >> I'm running 1.1.2; it's from the Ubuntu repo. > > Actually, the issue is Mailman core, not Postorius. max_message_size was > not exposed in REST before version 3.2.0. Ahh I see. I sure wish the distribution packagers would do a better job of keeping up with new releases. I'm an old-school UNIX guy, very much accustomed to building everything from source (under SunOS, Ultrix, etc) and I still maintain that these package management systems create more problems than they solve. ;) I got motivated and tried setting that variable via the mailman shell, and it worked a treat. Thanks again for hitting me with the clue bat. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Setting MM 3 attributes
On 2/27/20 9:08 PM, Mark Sapiro wrote: > On 2/27/20 5:44 PM, Dave McGuire wrote: >> >> Not to hijack, but is it possible to set the maximum message size by >> the mailman shell? I've a problem with that in one of my MM3 lists, I >> really need to set that, but the web interface does not allow me to set >> it. I get the dreaded "Unknown attribute: max_message_size" error. >> Could you loan me a clue? > > Not only does this not really belong in this thread, it doesn't even > belong on this list.> > <https://lists.mailman3.org/mailman3/lists/mailman-us...@mailman3.org/> > would be a better place, but since you asked... Yeah, I figured, sorry about that Mark. > Setting Maximum message size works in current Postorius. What version do > you have? I'm running 1.1.2; it's from the Ubuntu repo. > Yes you can set it in mailman shell > > mailman shell -l l...@example.com > > The variable 'm' is the l...@example.com mailing list >>>> m.max_message_size = 100(or whatever you want to set it to) >>>> commit() >>>> I've made a note of it, and will give it a shot tomorrow. Thanks, and I'm sorry for the OT post! -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The last release from the GNU Mailman project
On 2/27/20 8:01 PM, Mark Sapiro wrote: >> Bounce processing will still not be available for new users of Mailman >> which is my big concern. I assume new lists will have to have those >> settings adjusted via the Mailman shell? > > Sure it will. All the settings have reasonable defaults just like MM 2.1 > > bounce_info_stale_after: 7d > bounce_notify_owner_on_disable: True > bounce_notify_owner_on_removal: True > bounce_score_threshold: 5 > bounce_you_are_disabled_warnings: 3 > bounce_you_are_disabled_warnings_interval: 7d > process_bounces: True > > True, until they are exposed in some list admin UI they will need to be > set via mailman shell or the REST API, but bounce processing will work > out of the box in Mailman core 3.3.1. Not to hijack, but is it possible to set the maximum message size by the mailman shell? I've a problem with that in one of my MM3 lists, I really need to set that, but the web interface does not allow me to set it. I get the dreaded "Unknown attribute: max_message_size" error. Could you loan me a clue? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] The last release from the GNU Mailman project
On 2/27/20 3:40 PM, Brian Carpenter wrote:
>> If you want to port Mailman 2 to Python 3, you are welcome to do it. I
>> have said before that a much better use of time and resources would be
>> the implementation of a light weight, non-Django web UI for Mailman 3,
>> but I don't see anyone raising a hand to do either.
>
> I am doing that. I have hired a programmer and work beings for a new
> Mailman 3 UI next week.
Whoa, wow...does this mean (when it's ready) that we'll be able to
dump the steaming pile that is django??
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Now that Python 2 is dead in 2020 what are people's plans with mailman2?
On 4/10/19 12:25 PM, Mark Sapiro wrote: > The path forward is to increase the community of MM 3 users which will > result in more people contributing to the project and faster progress. On that note, I migrated my half-dozen lists (a few hundred recipients in total) to MM3 yesterday. I'm having a couple of minor issues, for which I will request advice as soon as I'm sure of what's happening, but overall the results have been positive. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] deleting archives, default sender addresses
On 2/27/19 1:15 PM, Mark Sapiro wrote: >>> See <https://gitlab.com/mailman/hyperkitty/issues/3> >> >> Ok, thanks for the pointer. I hate to as a stupid question, but how >> do I actually run that snippet? At an REPL prompt I assume, but are >> there imports, etc? > > You need to run the Django management command 'shell', e.g. > 'django-admin shell' or 'manage.py shell' or however you spell it. This > will give you a python shell and you enter the commands at the '>>>' > prompts. Ah! That worked perfectly. Is it obvious that I'm new to Django? ;) >>> DEFAULT_FROM_EMAIL = 'postorius@localhost.local' >>> >>> in your Django settings.py. Put your desired override in settings_local.py. >> >> Perfect! That worked. I could've sworn I set that last night and it >> didn't work, but perhaps I hadn't restarted Mailman. (it was late..) >> But I rebooted the VM this morning to install some patches. > > Rebooting will do it. Restarting Mailman won't as this is a Django > setting, not a Mailman setting. How to update that without a reboot > depends on how you run your Django wsgi app. With mod_wsgi, just > touching the wsgi.py file will do. With gunicorn, I just restart > gunicorn. I'm not sure about uwsgi, I don't use it, but see > <https://uwsgi-docs.readthedocs.io/en/latest/articles/TheArtOfGracefulReloading.html>. That makes sense. I was not aware that restarting Mailman would not restart Django. Thank you again, Mark, for your time. I appreciate your help. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] deleting archives, default sender addresses
On 2/27/19 12:09 PM, Mark Sapiro wrote: >> Hi folks. I'm a longtime Mailman 2 user, working with Mailman 3 for >> the first time (specifically v3.1.1) and things are going pretty well so >> far. I don't particularly like having to run it under Linux (we're a >> Solaris-based outfit) but I bit the bullet and built a VM for it. > > A much better list for Mailman 3 is mailman-us...@mailman3.org > <https://lists.mailman3.org/mailman3/lists/mailman-us...@mailman3.org/>. > Several Mailman 3 developers don't read this list. Oops, my apologies, thank you for the heads-up. I will subscribe over there shortly. > Also, have you tried > installing Mailman 3 on Solaris? It should work although there may be > some dependency gotchas. If you do succeed and it's not straightforward, > we'd appreciate your feedback. The problem isn't actually Solaris so much as it is SPARC. There's no SPARC back-end for Node.js, and the Node.js people don't seem interested in supporting that platform; apparently they think SPARCs are old or something. (There were SPARC processors in 1995...but not all SPARC processors are from 1995!) I think there's a better shot at it now, since they've made it portable enough to run on ARM, but still. >> I've hit two little snags, though. First, I created a test list and >> exercised it a bit, then deleted it...the archives are still in >> Hyperkitty, though. How can I delete those? > > See <https://gitlab.com/mailman/hyperkitty/issues/3> Ok, thanks for the pointer. I hate to as a stupid question, but how do I actually run that snippet? At an REPL prompt I assume, but are there imports, etc? >> Second, address confirmation emails are coming from >> postorius@localhost.local. I've dug and dug, and I've not been able to >> override it. There are numerous archived forum posts about this, and >> none of the proposed solutions I've found seem to work. Help? > > That is > > DEFAULT_FROM_EMAIL = 'postorius@localhost.local' > > in your Django settings.py. Put your desired override in settings_local.py. Perfect! That worked. I could've sworn I set that last night and it didn't work, but perhaps I hadn't restarted Mailman. (it was late..) But I rebooted the VM this morning to install some patches. Thank you, Mark, for your time and assistance. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] deleting archives, default sender addresses
Hi folks. I'm a longtime Mailman 2 user, working with Mailman 3 for the first time (specifically v3.1.1) and things are going pretty well so far. I don't particularly like having to run it under Linux (we're a Solaris-based outfit) but I bit the bullet and built a VM for it. I've hit two little snags, though. First, I created a test list and exercised it a bit, then deleted it...the archives are still in Hyperkitty, though. How can I delete those? Second, address confirmation emails are coming from postorius@localhost.local. I've dug and dug, and I've not been able to override it. There are numerous archived forum posts about this, and none of the proposed solutions I've found seem to work. Help? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2 and 3
On 03/30/2017 08:35 PM, Barry Warsaw wrote: Interesting. I know there's a pretty clear division between components in 3; can the web interface run on a separate machine and point to a remote instance of Mailman? Yep! It's somewhat important to keep in mind that the REST API of Core is a fully administrative API. It can be protected by some basic auth secrets, but nothing more than that, so just make sure that the Core REST API isn't published on some public IP address and you should be fine. Ok, very interesting. Thank you for the explanation. Running the management code on a different system is something I could probably make myself swallow. I'll have to decide at some point if the additional coolness of 3 is worth that hassle. From what I've seen so far, it may very well be. With the exception of the Node.js silliness, Mailman appears to be moving in a very good direction. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2 and 3
On 03/30/2017 08:08 PM, Barry Warsaw wrote: I'm afraid Node.js is still a requirement. Of the web interface of course. Technically those are optional components, but practically speaking if you want to control Mailman 3 via the web, that's the only option. Interesting. I know there's a pretty clear division between components in 3; can the web interface run on a separate machine and point to a remote instance of Mailman? -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2 and 3
On 03/30/2017 07:11 PM, Mark Sapiro wrote: Thinking about it some more, yes I believe it was Node.js. Apparently Node.js isn't quite portable enough to run on SPARC. I'm afraid Node.js is still a requirement. Ok. No Mailman 3 for us. :-( Thanks for your response. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2 and 3
On 03/30/2017 07:13 PM, Carl Zwanzig wrote: Does 3 yet run on anything other than Linux? The last time I looked at it, it looked to be pretty much Linux-only. (My company's Solaris-based mail servers aren't going away anytime soon.) Unless v3 is different from v2 in this regard, mailman doesn't have to run in the same OS instance as the MTA. Put mailman3 on a linux (or bsd) box and let the existing MTAs do their thing. You will have to deal with routing the mailman aliases to the mailman system, but that shouldn't be difficult. We could set that up here, but rather than set up another VM running a different OS just to support Mailman 3 isn't going to happen. We'll stick with 2. OTOH, node.js is available for solaris x86 (32 & 64 bit) on the nodejs.org site. If you're still running sparc servers aren't they getting a bit long in the tooth? Just because there were SPARC servers in 1995 doesn't mean ALL SPARC servers are from 1995, CZ...these aren't the ones we ran at Digex. ;) Our T3s and T4s are reasonably new and screaming fast. They'll get replaced when they're truly obsolete, rather than "salesman obsolete". That likely means ARM. (does Node.js run on ARM?) (Says the person still running his backup DNS on a Pentium P90 :).) Hey, if it serves the requests.. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2 and 3
On 03/30/2017 05:27 PM, Mark Sapiro wrote: Does 3 yet run on anything other than Linux? The last time I looked at it, it looked to be pretty much Linux-only. (My company's Solaris-based mail servers aren't going away anytime soon.) It should run on any *nix that supports Python 2, Python 3 and its dependencies. I know people have built it successfully on Mac OSX, at least for development/testing. Are there specific issues with Solaris that you think will be problems? Hi! I last looked at it about a year ago (which is a very long time in my world ;)) so the specifics are very fuzzy. I believe there was a dependency on a biggish package that was either Linux-only or x86-only. Would it have been Node.js? Thinking about it some more, yes I believe it was Node.js. Apparently Node.js isn't quite portable enough to run on SPARC. -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman 2 and 3
On 03/30/2017 12:16 PM, Mark Sapiro wrote: However: What is the state of Mailman 2 at the moment? I think it is still supported and developed. But will this change in the near or in the distant future? Mailman 2 is definitely end of life. I am the only one actively supporting it at this point and while I continue to offer help and fix bugs, it's not what I want to be doing. Mailman 3 is the future. 3.1 will be released probably after PyCon in May if not before, and while there will still be some things "missing" from the web admin UI (Postorius), and the migration tools for 2.1 lists are still buggy, we think 3.1 will be a viable replacement for Mailman 2.1. Does 3 yet run on anything other than Linux? The last time I looked at it, it looked to be pretty much Linux-only. (My company's Solaris-based mail servers aren't going away anytime soon.) -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
