The GNU Mailing List manager. https://git.neuromancer.sk/mailman.git/atom/src/mailman/pipeline?h=master 2012-03-23T17:36:58Z 2012-03-23T17:36:58Z Barry Warsaw 2012-03-23T17:36:58Z urn:sha1:56ebf923ff311b4c1d195d46c04cadca4940b638 how I think about them anyway. 2012-03-17T17:26:05Z Barry Warsaw 2012-03-17T17:26:05Z urn:sha1:ae15984804096db593d83740dcd4c158626eb22f 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 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 2012-03-16T02:06:22Z Barry Warsaw 2012-03-16T02:06:22Z urn:sha1:44ec37f890c7d4d35504d8f2e56c01abe8c60940 some new APIs I suspect. 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) 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. 2012-03-12T22:57:03Z Barry Warsaw 2012-03-12T22:57:03Z urn:sha1:3fe7d15a5c6e54cc0c201b10b9dd1329dffe2cd2 2012-03-05T18:27:14Z Barry Warsaw 2012-03-05T18:27:14Z urn:sha1:5350f4875fbe65055d045c44cfd2d4348cfeb5ec 2012-03-05T17:58:20Z Barry Warsaw 2012-03-05T17:58:20Z urn:sha1:f4b98f8b8e8b9fdcab8c352019f09b1469c93b24 - When doing individual deliveries, insert a 'member' key into the copy of the metadata dictionary for this recipient's delivery. This will contain the IMember of the recipient, if the recipient is a member of the mailing list. There will still be a 'recipient' key which will contain just the email address to deliver the message to. - Remove $user_password from header/footer placeholders. - Remove the 'personalize' key from the metadata dictionary and change decorate.process() to search only for the 'member' key. No need for both of them and the 'member' key contains more information. Plus, it allows us to do a more efficient member query in the delivery module some time in the future. - Move some of the LMTP log messages from mailman.runner to mailman.smtp.