Re: [Mailman-Developers] From the creation of a ThreadID
Bill Janssen has one too, I forget it it's based on amk's or not, but it's current. See thread in email-sig: http://mail.python.org/pipermail/email-sig/2012-January/000882.html On Sat, Apr 7, 2012 at 2:54 AM, Toshio Kuratomi a.bad...@gmail.com wrote: On Fri, Apr 06, 2012 at 12:10:22AM +0900, Stephen J. Turnbull wrote: Some Message-IDs will not have corresponding messages but that's always a problem with threading (see http://www.jwz.org/doc/threading.html, and RFC 5256). There are other problems with threading that need to be dealt with as well, such as References being inconsistent across messages in the same thread and people who continue a thread with a new message, etc. Looks like amk coded jqz's algorithm into a python library too: https://github.com/akuchling/jwzthreading All other links to that code that I found (on amk.ca and bitbucket) were broken so someone may want to clone that/ask andrew what's going on with it :-) -Toshio ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/stephen%40xemacs.org Security Policy: http://wiki.list.org/x/QIA9 ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] Integrating HyperKitty with Mailman3
I believe that after integrating HyperKitty with mailman, there will be archiver['hyperkitty'] which can be used to archive the messages. Am i correct? http://packages.python.org/mailman/src/mailman/archiving/docs/common.html#sending-the-message-to-the-archiver I know that mailman3 offers pluggable architecture, but still after going through some documentation it is not apparent to me how exactly HyperKitty will be integrated with mailman3. Can somebody briefly explain and point out to relevant files in source code ? -- Aamir Khan | 3rd Year | Computer Science Engineering | IIT Roorkee ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] From the creation of a ThreadID
On Apr 6, 2012 10:49 AM, Toshio Kuratomi a.bad...@gmail.com wrote: 1) don't publish thread-ids, but just message-ids... for example, a thread URL could be allowed to reference the message-id of 'any' message in the thread They could then include more than one message-id, making them resiliant to a lost messageid later. if some messageid are lost, hopefully a url someone is holding onto has another messageid that was not lost. This sounds good. So instead of relying on the first message-id of the thread we internally keep a mapping of all message-ids and stableurl hashes to either an internal message-id or a tree of messages in the thread. I think of this as keeping a mapping from rfc822 message-id to internal thread-id. I think you are using different words to say the same thing. When deleting messages, always retain the message-id and stableurl hashes for that message in the mapping. That way a url that pointed to the thread by that message-id will continue to function even though the message itself has been deleted. Perhaps I misunderstood. If you are going to have a record of the deletion (i.e. you can keep a deleted message around in some form), this problem becomes much easier. I thought this desire was to have stable urls and threads when you rebuild and a message is missing. Absolutly if there is a message 'deletion' feature, it should delete the message contents but leave a 'stub' that links the message-id and references/in-reply-to, so it can help hold the thread together during a rebuild. My memory is foggy, but I think we used a technique like this in Yahoo Groups. ___ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
