On Apr 15, 2013, at 01:05 PM, Sreyanth wrote: >Just hide the boilerplate in the email, giving a link to click. When clicked, >use js to unhide the boilerplate. This would not anyhow require separate >storage. Suggest me something if this is bad!
A problem you would have to work out with this approach is how to properly integrate this when a site/list could have multiple enabled archivers, some or all of which are remote to the Mailman system. Remember that in MM3 we won't have an integrated archiver like Pipermail that we can just assume will be there. Even the web ui isn't as tightly integrated any more. This doesn't mean you can't still do this. See for example the additions our stable url proposed add-ons to RFC 5064 as an example of how you would have to think about this. -Barry _______________________________________________ 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
