Re: [Mailman-Developers] mailman
I've been checking all the logs for hints, but I have a feeling I missed a big hint in there now. I'll try 3.0.2, thanks On 03/31/2016 10:30 AM, Stephen J. Turnbull wrote: treal tv writes: > The problem is that when python 3.4 makes a virtualenv, it somehow pulls > in falcon1.0.0rc1... even if you have falcon0.3.0 installed. Barry has that pinned to < 1.0 in 3.0.3, do a diff against 3.0.2 (or maybe just grep the logs) and you should find out how to stop that. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] mailman
I should also mention that I've done a full sweep of my system to make sure falcon 1.0.0rc1 isn't hiding anywhere. I can only suspect it's built into some other package and I need to hunt it down. On 03/31/2016 10:18 AM, treal tv wrote: The problem is that when python 3.4 makes a virtualenv, it somehow pulls in falcon1.0.0rc1... even if you have falcon0.3.0 installed. I've spent the last couple days fighting with this exact problem and trying to find ways to trick python 3.4 to not pull in falcon 1.0 when making a virtualenv, no solution yet though. I suspect I'm going to have to rebuild python 3.4.4 a few times before getting it. On 03/31/2016 10:09 AM, Christian Schoepplein wrote: Hi Aditya, On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote: I'm sorry for the misdirect. I'm myself a beginner here! Absolutely no problem, every hint is welcome :-). I'm also a beginner with mailman 3 and absolutely no python expert :-(. To be honest it is not easy to understand the full procedure of installation of all needed components for mm3, at least if you like to install not the mailman_bundler package. There are so many sites with documentation and it is not easy to find out what is the right one. A step to step guide to install all components, which also beginners or not python programmers do understand, would be great. Maybe there is some kind of such a guide, but I haven't found it. And if it is not, I'd like to help to create such a guide, but I'd need support from people with mor knowledge of python and all the things which are needed. This issue on gitlab is probably the same as the one you are facing. The fix recommended is the installation of falcon 0.3.0.1 or 0.3 [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503 If I understand it correctly, I already have a newer version of falcon installed: root@mm3:/opt/mailman-bundler# find . -name *falcon* ./venv-3.4/lib/python3.4/site-packages/falcon ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info ./venv-3.4/bin/falcon-bench root@mm3:/opt/mailman-bundler# But as said before, I'mno python expert... Ciao and thanks again for your help, Schoepp ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] mailman
The problem is that when python 3.4 makes a virtualenv, it somehow pulls in falcon1.0.0rc1... even if you have falcon0.3.0 installed. I've spent the last couple days fighting with this exact problem and trying to find ways to trick python 3.4 to not pull in falcon 1.0 when making a virtualenv, no solution yet though. I suspect I'm going to have to rebuild python 3.4.4 a few times before getting it. On 03/31/2016 10:09 AM, Christian Schoepplein wrote: Hi Aditya, On Do, Mär 31, 2016 at 07:17:50 +0530, Aditya Divekar wrote: I'm sorry for the misdirect. I'm myself a beginner here! Absolutely no problem, every hint is welcome :-). I'm also a beginner with mailman 3 and absolutely no python expert :-(. To be honest it is not easy to understand the full procedure of installation of all needed components for mm3, at least if you like to install not the mailman_bundler package. There are so many sites with documentation and it is not easy to find out what is the right one. A step to step guide to install all components, which also beginners or not python programmers do understand, would be great. Maybe there is some kind of such a guide, but I haven't found it. And if it is not, I'd like to help to create such a guide, but I'd need support from people with mor knowledge of python and all the things which are needed. This issue on gitlab is probably the same as the one you are facing. The fix recommended is the installation of falcon 0.3.0.1 or 0.3 [1]https://gitlab.com/mailman/postorius/issues/122#note_4509503 If I understand it correctly, I already have a newer version of falcon installed: root@mm3:/opt/mailman-bundler# find . -name *falcon* ./venv-3.4/lib/python3.4/site-packages/falcon ./venv-3.4/lib/python3.4/site-packages/falcon-1.0.0rc1-py3.4.egg-info ./venv-3.4/bin/falcon-bench root@mm3:/opt/mailman-bundler# But as said before, I'mno python expert... Ciao and thanks again for your help, Schoepp ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] adding to REST
I hadn't considered this yet. I had planned to help with patches so yeah, I think i'll be rebuilding from the repo! Thanks, I hadn't even thought about that yet. On 03/14/2016 06:24 PM, Simon Hanna wrote: In case you want to turn in patches (merge requests) then having a repo is a must. And if you don't plan to turn in patches it's still useful. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] adding to REST
I might be misunderstanding you, Simon, but should I not be using Mailman 3 built with the bundler if I intend to modify/further build on the code? I've been working off one built with the bundler for the last couple months and it's tolerated the mods I made without issue but I'd rather switch to source built sooner rather than later if it's going to matter in the future. On 03/14/2016 03:31 PM, Simon Hanna wrote: On 03/14/2016 07:25 PM, Dominic Dambrogia wrote: Hi, My name is Dominic. I contacted this mailing list last week about list moderation and post approval. My problem was not being able to set a list password via the REST api. I need this for nonmember approval of posting to a mailing list via email in the "Approved: *list password*" style in the first line of the email like the default request for moderation email suggests. I'd like to go ahead and tackle this problem personally. I would appreciate some insight on where to start looking in the project itself. I've only installed the bundler and used REST so far, so my knowledge of how the python code works so far is minimal. Any insight is greatly appreciated, thanks. - Dominic If you want to actually develop mailman, you shouldn't use bundler for that. Check out the following two pages that help you with some git knowledge and setting up your dev environment. http://wiki.list.org/DEV/HowToContributeGit http://wiki.list.org/DEV/SetupDevEnvironment You should create an issue on gitlab https://gitlab.com/mailman/mailman/issues if there isn't one already. This issue can be used to discuss specifics about the implementation. You could try the irc channel #mailman on freenode for help in case you need something. You can of course also post to this list. All the code regarding the rest interface lives in src/mailman/rest I hope this get's you started, Simon ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/trealtv%40yandex.com Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Mailman 3 custom footer
Hey Barry! I'm a few days late to respond to this, but I just wanted to let you know I found this immensely useful, and my footer looks just like how I want it to be :) We are using Mailman 3 in production in a corporate environment. I'm willing to deal with the re-structuring of Mailman when 3.1 comes around :) Thanks again Barry. On 02/26/2016 07:24 PM, Barry Warsaw wrote: On Feb 25, 2016, at 02:36 PM, treal tv wrote: I'm looking to modify the contents of this footer so it says something slightly different. However, I can't find anywhere with Mailman 3 to change anything about the footer. I'll describe what you have today, but it's likely the exact details will change at some point (maybe for 3.1 if my ideas pan out). Still, how it works today still contains the basic scheme for how I want it to work in the future. The thing to remember is that while Core needs to send out emails with various templates, it can't make any assumptions about what is on the web front-end, so text like footers can't contain URLs and such by default. Yes, this is a bit of a mess right now because you'll still see substitutions like $listinfo_url in some templates, even though these can't be correctly filled in. So there are two parts to this answer. The first is finding the template to use for the footer[*], and then filling in all the placeholders. You've found the footer-generic.txt template, but how is this used? Every mailing list currently has an attribute called `footer_uri`, and this is set in the list style. I've previously described how style works so I won't go down that detour here. Suffice to say that the default style sets footer_uri to `mailman:///$listname/$language/footer-generic.txt`. Notice two things about this uri. * It has a `mailman:` scheme. * It has some $-placeholders. What happens is that in the decorate handler, when the footer is put on the outgoing message, we first substitute some useful information into the uri's placeholders. The values should be obvious: $listname gets the fqdn_listname value and $language gets the preferred_language.code. So for mailing list al...@example.com using Italian as its preferred language, the footer_uri gets transformed into mailman:///al...@example.com/it/footer-generic.txt. Now we start to look that up. Of course, if the scheme were http: or https:, we'd just issue a request to that url and use whatever we find. The intent is that in Postorius or some other CMS or web resource repository, you'd be able to define a custom template appropriate for your site. You'd set the list's footer_uri to something like https://my.cms.example.com/footer.txt and since there are no placeholders, Mailman just grabs the text at that url and viola! you've got your footer. Supporting the placeholders allows your CMS to provide different footers for different lists, and of course you'll want to provide different footers for different human languages. But okay, now we have mailman:///al...@example.com/it/footer-generic.txt and we have to look that up. What are the rules for mailman: urls? mailman: urls are shorthand for internal resources, homed in the source code directory on the file system. The search order is well documented, but not easily discovered so here's the documentation: https://gitlab.com/mailman/mailman/blob/master/src/mailman/utilities/i18n.py#L53 You can see how there's a search hierarchy, such that if you only want a single template for all your lists on the site, you can define it once on the file system, and Mailman will just find that one. Similarly, you could have a template that applies to all lists within the same domain, or have list specific templates. So, bottom line is, drop a file in the template_dir defined in your mailman.cfg and set your list's footer_uri to a mailman: url that points here, and Bob's your uncle. Now the second step alluded to earlier. Once you've located the template, the template *itself* can have substitution placeholders, and for message headers and footers (i.e. message decorations) they get filled in here: https://gitlab.com/mailman/mailman/blob/master/src/mailman/handlers/decorate.py#L228 So you can see how your template can contain information about the mailing list's name, hostname, description, etc. `extradict` comes into play (or at least *should* ) when messages are personalized, such that some information specific to the user could be added, e.g. their unsubscribe link. This may not be fully plumbed out right now though. Briefly then, how will this be different in the future? I'm still working out the design, but roughly, there will be a new ITemplateManager that holds mappings between template names, a context (e.g. mailing list, domain, or site), URIs, and "resource dictionaries". This ITemplateManager would be a top-level REST resource so Postorius and other REST clients could directly manipulate these mappings. Then you'd be able to say, through REST, "
[Mailman-Developers] Mailman 3 custom footer
I saw an older message where someone was asking how to customize the footer for mailman 3. https://mail.python.org/pipermail/mailman-users/2015-October/079965.html It didn't seem to ever be answered, and I couldn't find any follow up in this list's archives. This is a problem I'm struggling with now - I also found the footer-generic.txt from the source where the exact footer I'm seeing is coming from. https://gitlab.com/mailman/mailman/blob/master/src/mailman/templates/en/footer-generic.txt I'm looking to modify the contents of this footer so it says something slightly different. However, I can't find anywhere with Mailman 3 to change anything about the footer. Any help is greatly appreciated! Thank you! ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
