Mailman 3 March 2016 - Mailman-Developers

Re: [Mailman-Developers] Need more information about the GSoC idea 'GitLab/development tools integration'
by Richard Damon March 13, 2016

March 13, 2016

On 3/12/16 4:19 PM, Wasim Thabraze wrote: > Hello everyone, > > The GSoC idea states 'a tool that will take a thread from a Mailman > mailing list and..'. I just wanted to know what are the different ways to > extract a thread from a mailing list. > > I'm actually trying to understand the idea from a couple of days but in > vain. I couldn't even find documentations related to thread extraction. > > Does a thread has any unique id? If yes, how should I extract the thread > using the id? > > Any links that would help me in understanding it in a much more better way? > > > > Awaiting reply. > > > Thank You > > > Regards, > Wasim > The normal definition of the 'Thread' is a chain of message linked by In-Reply-To: and References: headers to Reference-Id: headers. Every email message has a unique Reference-Id: header to identify it. When a person replies to that message, their email program is supposed to add a In-Reply-To: header with the Reference-Id of the message it is a reply to, or a References: header with a copy of the References: header of the message being replied to with the Reference-Id of the replied to message added at the beginning (and possibly ones at the end trimmed if the header gets too long). This chain defines a 'Thread'. One wrinkle is with plain text digest users, they tend to not have the Reference-Id of the message they are replying to (one of the limitations of the plain text digest) so they tend to break threads. The one big issue here is that they also often send a message by replying to the digest, so two messages that refer to the same message in In-Reply-To: or References: headers might not want to be linked together as a thread if the common Message-Id isn't present (it is likely the digest). I think this is what the current mailman 2 archives do.

3 2

Patch for HyperArch
by Sebastian Hagedorn March 13, 2016

March 13, 2016

Hi, we recently needed to rebuild a rather old list archive. The oldest mails are from 2001, and as far as I could tell the last complete rebuild happened in 2005. When we ran "arch --wipe" now, it failed: Aktualisiere HTML f?r Artikel 1412 Schreibe Archivzustand in Datei /var/lib/mailman/archives/private/linux-users/pipermail.pck Traceback (most recent call last): File "./arch", line 201, in <module> main() File "./arch", line 189, in main archiver.processUnixMailbox(fp, start, end) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 587, in processUnixMailbox a = self._makeArticle(m, self.sequence) File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 688, in _makeArticle mlist=self.maillist) File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 264, in __init__ self.__super_init(message, sequence, keepHeaders) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 186, in __init__ self._set_date(message) File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 601, in _set_date self.fromdate = time.ctime(int(self.date)) ValueError: timestamp out of range for platform time_t Obviously the mails that caused this error were broken, but a previous version of arch was able to build the archive regardless. I wrote the following patch to work around the problem (I wrote it for 2.1.18, but I checked that the code looks the same in 2.1.21): --- /service/HyperArch.py 2014-07-16 13:01:11.000000000 +0200 +++ HyperArch.py 2016-03-07 11:25:34.000000000 +0100 @@ -598,7 +598,14 @@ def _set_date(self, message): self.__super_set_date(message) - self.fromdate = time.ctime(int(self.date)) + try: + self.fromdate = time.ctime(int(self.date)) + except ValueError: + syslog('error', + 'Archive error. Date %s is invalid.', + int(self.date)) + self.date = str(int(time.time())) + self.fromdate = time.ctime(int(self.date)) def loadbody_fromHTML(self,fileobj): self.body = [] If an exception is caught, the date is simply set to the current time. -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

3 16

Need more information about the GSoC idea 'GitLab/development tools integration'
by Wasim Thabraze March 12, 2016

March 12, 2016

Hello everyone, The GSoC idea states 'a tool that will take a thread from a Mailman mailing list and..'. I just wanted to know what are the different ways to extract a thread from a mailing list. I'm actually trying to understand the idea from a couple of days but in vain. I couldn't even find documentations related to thread extraction. Does a thread has any unique id? If yes, how should I extract the thread using the id? Any links that would help me in understanding it in a much more better way? Awaiting reply. Thank You Regards, Wasim

1 0

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .
by Stephen J. Turnbull March 12, 2016

March 12, 2016

Harshit Bansal writes: > Basically, a style will be having three levels of viewability: > 1: System wide : A style having this level of viewability will be > visible to all the domains as well as the lists. It will be available > to all the list owners for copying however the site owners will have > the option to make it either read-only or editable. I don't see a real advantage to having this editable by list owners, since it's copyable. On the other hand, "styles" are not just display, but also include security/privacy features. Eg, a rogue editor could DoS the whole site by adding .* as a ban or discard expression in spam filtering. I think probably it's OK to have styles editable only by owner. However, the owner might be a group of users. How about inheritability? The difference between inheritance and copying is that if the template changes, with inheritance the derived configurations change too, with copying they don't. > 2: Domain Wide : A style having this level of viewability will be > visible to all the lists within a specific domain. However, the domain > owners would have the option to make it read-only or editable. Same as above. > 3: List Specific : A style having this level of viewability will be > visible to a specific list. > > Not only this, all stylable attributes will be divided into three categories: > 1: Site owner level attributes : Only site owners will have the > permissions to edit these attributes. As above, "owner" should be allowed to be a group. > 2: Domain owner level : Site owners as well as domain owners can > edit these attributes. Ditto. > 3: List owner level : Site owners as well as domain owners as well as > list administrators will have the permissions to edit these > attributes. > @Steve I think this system also addresses the issues that you pointed > as now all the permissions will be enforced in the mailman core > instead of Postorius. Yes. > Also while working out the implementation details, I came across a new > problem which is as follows: > Suppose, we have three style A, B and C. B inherits from A and C > inherits from B. Now, suppose someone decides to delete style B then > how can we deal with this situation. Persistence across Mailman restarts of course needs to be carefully dealt with, but we deal with the basic issue in the usual Unix way: a style which is "deleted" just loses its entry in the admin-visible directory of styles, but it is not actually deleted from the database until all references are gone.

2 1

Re: [Mailman-Developers] Help regarding an error during installation
by Abhilash Raj March 12, 2016

March 12, 2016

Hi Daman, On 03/10/2016 07:18 AM, Daman Singh wrote: > Hello everyone! > > I am trying to install mailman for development using mailman-bundler. I > followed the instructions given here > http://mailman-bundler.readthedocs.org/en/latest/ , but i am facing a > problem. > When i run buildout command i get an error saying,"no module named 'zlib'" > but on running ipython, when i import zlib it works all right. When running buildout in mailman-bundler, it generally creates a virtualenv of its own, which might not have 'zlib not installed in it. Just look for the virtualenv that gives this error(it could be venv-3.4, that bundler makes for running mailman in), activate that, and install 'zlib in there. I am not sure where is this error coming from, but for general python projects, this is a general solution. -- thanks, Abhilash Raj

3 2

To GET STARTED
by Pabitra Lenka March 12, 2016

March 12, 2016

Greetings Developers, I am a newbie.I would like to contribute to your organization.Can anyone get me started.? -- Cheers, Pabitra Lenka Department of Information Technology Class of 2018 IIIT Bhubaneswar

1 0

INTEREST IN IMPLEMENTING Message queue based email archiver
by Okusanya Damilola March 12, 2016

March 12, 2016

Sir, My name is Okusanya Oluwadamilola. I am currently enrolled for my Masters programme at Saint Cloud State University at St.Cloud Minnesota. I played around with Apache ActiveMQ last semester and have some basic Python skills. Could you shed some more light about the project? Thanks for your prompt and favourable response. Sincerely, Okusanya OIuwadamilola.

1 0

Re: [Mailman-Developers] Introduction + Interested in the GSoC idea 'Preset list settings templates (aka list styles)' (Devendra Vyas)
by Abhilash Raj March 11, 2016

March 11, 2016

Hi Devendra, On 03/11/2016 05:52 AM, Devendra Vyas wrote: > Hi! All > Congratulations for getting selected in GSoC'16 > > I'm Devendra Vyas(@skat00sh), final year undergrad at The LNMIIT Jaipur. > I've been learning Django framework from past couple of months. I recently > worked upon this website: http://www.scholfin.com/- A Scholarship Search > Engine. Apart from it, currently working on my B.Tech project relating to > Tweet Analysis, using Python-SciKit. I've a fairly good background in > algorithms and data-structures, qualified for ACM-ICPC Regionals. I'm new > to open source contribution and recently started contributing to > GNU-Mailman(Postorius, as of now). > > I saw the ideas page and was interested in the project:Preset list > settings templates (aka list styles). As of now I've setup postorius and > mailman3. I wanted to ask, is there any warm-up task for the project? Also, > is it possible for the mentors to review the proposal before the actual > submission? There is no specific warmup task for any project, we just encourage you to choose one issue from the issue tracker of the projects and solve that. Also, you can follow up on the ongoing discussion of this project with another interest student on -developers (this) list, it will give you a very good idea about how to get started in this project. I don't think it would be an issue you want reviews on your proposal before the actual submission deadline. > Thanks and regards > Devendra > -- thanks, Abhilash Raj

1 0

Re: [Mailman-Developers] Discussion On Project Idea "Preset List Settings Templates" .
by Barry Warsaw March 11, 2016

March 11, 2016

Thanks for following up here Harshit. Here are some of my thoughts/ramblings. On Mar 09, 2016, at 10:51 PM, Harshit Bansal wrote: >I think the "Permissions Systems" would have nothing to do with the >core. It would be related to Postorius. We will have to create a style >model separately in Postorius which would store the style name and the >user who created it. Then only the user who has created the style >would be granted the permission to edit it. Mailing lists have a clear ownership chain. At the top is the system administrator who has access to the shell. They get to do things no one else can, such as create Python files. Ultimately, they should be able to create immutable styles which serve as the baseline for all other style options. These are immutable because they are defined in Python code. The sysadmin can delegate style customizations to the server/site owner, which is a defined role in the core's model. The IUser interface defines a flag `is_server_owner` to define this permission. The server owners can delegate to domain owners. The IDomain interface has a `owners` attribute which can contain users that have this permission. Domain owners can then delegate to list owners, and of course there is an `owners` attribute on the IMailingList interface. Mailing lists also have moderators but those users wouldn't have permission to change list styles. Here's where it gets complicated. At each level, it should be possible to say "I delegate settings X, Y, and Z to the level below and they can change it to anything they want." But they should also be able to say, "I do not allow the level below to change settings A, B, and C." For example, a domain owner might say, "you list owners can change your welcome messages to anything you want, but you cannot change the footers because for legal reasons this text must appear on every message." So you have several things you want to be able to specify about each attribute in a style. You want to be able to delegate permission to change a style attribute going down the hierarchy, but you also want to be able to have any particular style attribute delegate its value up the hierarchy. E.g. a list owners could say "I don't really care about the filter_types, just use whatever is in the parent style." It's likely that the permissions would only be enforced in Postorius, although we can think about how the core would enforce the permissions. The core would definitely support the deferring of style values back up to parent styles. One other thing to think about is whether some styles will be allowed or disallowed for various domains or mailing lists. E.g. should some styles only be allowed for example.com and others for example.org, or can all of them be allowed for any mailing list on the system? I think at the very least, some segregation based on domain would be useful. Cheers, -Barry

3 2

Introduction + Interested in the GSoC idea 'Preset list settings templates (aka list styles)' (Devendra Vyas)
by Devendra Vyas March 11, 2016

March 11, 2016

Hi! All Congratulations for getting selected in GSoC'16 I'm Devendra Vyas(@skat00sh), final year undergrad at The LNMIIT Jaipur. I've been learning Django framework from past couple of months. I recently worked upon this website: http://www.scholfin.com/- A Scholarship Search Engine. Apart from it, currently working on my B.Tech project relating to Tweet Analysis, using Python-SciKit. I've a fairly good background in algorithms and data-structures, qualified for ACM-ICPC Regionals. I'm new to open source contribution and recently started contributing to GNU-Mailman(Postorius, as of now). I saw the ideas page and was interested in the project:Preset list settings templates (aka list styles). As of now I've setup postorius and mailman3. I wanted to ask, is there any warm-up task for the project? Also, is it possible for the mentors to review the proposal before the actual submission? Thanks and regards Devendra -- It is not your qualifications but your exposure in life that makes you who you are. Devendra Vyas Final Year,Comp. Science B.tech , The LNMIIT Jaipur(Raj.) Ph no. (+91)9460053732

1 0