mailman.git/src/mailman/pipeline/docs, branch master The GNU Mailing List manager. https://git.neuromancer.sk/mailman.git/atom/src/mailman/pipeline/docs?h=master 2012-03-23T17:36:58Z Rename the src/mailman/pipeline directory to src/mailman/handlers since that's 2012-03-23T17:36:58Z Barry Warsaw 2012-03-23T17:36:58Z urn:sha1:56ebf923ff311b4c1d195d46c04cadca4940b638 how I think about them anyway. Merge the Pipermail eradication branch. The scrubber is also removed. 2012-03-17T16:54:26Z Barry Warsaw 2012-03-17T16:54:26Z urn:sha1:8e6cca71e8b6b0e79394aaf2c1d13d7cfce41c29 * Configuration variable `[mailman]filtered_messages_are_preservable` controls whether messages which have their top-level `Content-Type` filtered out can be preserved in the `bad` queue by list owners. * Configuration section `[scrubber]` removed, as is the scrubber handler. This handler was essentially incompatible with Mailman 3 since it required coordination with Pipermail to store attachments on disk. * Schema additions: - mailinglist.filter_action * Pipermail has been eradicated. 2012-03-16T22:58:17Z Barry Warsaw 2012-03-16T22:58:17Z urn:sha1:24991d17919f2715a7f2e875d2fb7fe72e53efcf * Configuration variable `[mailman]filtered_messages_are_preservable` controls whether messages which have their top-level `Content-Type` filtered out can be preserved in the `bad` queue by list owners. * Configuration section `[scrubber]` removed, as is the scrubber handler. This handler was essentially incompatible with Mailman 3 since it required coordination with Pipermail to store attachments on disk. * Schema additions: - mailinglist.filter_action Eradicate Pipermail. Everything but the scrubber test works. That will take 2012-03-16T02:06:22Z Barry Warsaw 2012-03-16T02:06:22Z urn:sha1:44ec37f890c7d4d35504d8f2e56c01abe8c60940 some new APIs I suspect. Schema change. After discussion at Pycon, we decided to change "real_name" to 2012-03-15T22:48:41Z Barry Warsaw 2012-03-15T22:48:41Z urn:sha1:ac0f1c3916e797f3a2261e9a2631e496fb90a8f1 "display_name" across the board. * `IMailingList.real_name` -> `IMailingList.display_name` * `IUser.real_name` -> `IUser.display_name` * `IAddress.real_name` -> `IAddress.display_name` * Schema changes: - real_name -> display_name (mailinglist, user, address) * The LMTP server now requires that the incoming message have a `Message-ID`, 2012-03-14T04:03:01Z Barry Warsaw 2012-03-14T04:03:01Z urn:sha1:80ac803cb2816dde0503671fd117ed134680de53 otherwise it rejects the message with a 550 error. Also, the LMTP server adds the `X-Message-ID-Hash` header automatically. The `inject` cli command will also add the `X-Message-ID-Hash` header, but it will craft a `Message-ID` header first if one is missing from the injected text. Also, `inject` will always set the correct value for the `original_size` attribute on the message object, instead of trusting a possibly incorrect value if it's already set. The individual `IArchiver` implementations no longer set the `X-Message-ID-Hash` header. Clean up a few documentation issues. 2012-03-12T22:57:03Z Barry Warsaw 2012-03-12T22:57:03Z urn:sha1:3fe7d15a5c6e54cc0c201b10b9dd1329dffe2cd2 Template indirection now also in effect for regular and digest headers and 2012-03-04T23:39:08Z Barry Warsaw 2012-03-04T23:39:08Z urn:sha1:40347db84550a85f43e6befa4641693200d30509 footers, using the same semantics and algorithm as for welcome and goodbye messages. Additional schema changes: - msg_header -> header_uri - msg_footer -> footer_uri - digest_header -> digest_header_uri - digest_footer -> digest_footer_uri * Stop adding the X-BeenThere header. 2011-11-06T23:20:08Z Barry Warsaw 2011-11-06T23:20:08Z urn:sha1:ac49e4c485345058d2ee582b9966f441b2349738 * Separate out the RFC 2369 header adding handler. * Dynamically calculate the `List-Id` header instead of storing it in the database. This means it cannot be changed. * Be sure to clean out any digest .mmdf files when the world is reset. Finally, all doctests are named .rst 2011-09-24T01:42:39Z Barry Warsaw 2011-09-24T01:42:39Z urn:sha1:48354a7e6814190455fb566947ab952062ecde76