Currently the default (and only) protocol options supported are to enable all messages and disable all "no reply" options. This means Kilter is receiving and sending many messages that are redundant for a given set of filters.

Phase 1 of this project is to add manual intervention, allowing a user to specify a set of message options a filter needs.

• For message options, each filter can request just the messages they require. The full set of messages negotiated with an MTA is then the union of messages required by all filters.

• For the MAX_DATA_SIZE_* (MDS_*) options the largest value requested will be used and the runners of any filters requesting smaller values will spilt the data appropriately.

• Support for Skip should already be implemented, it should always be requested if available and simulated if not.

• For the rest of the options, they will be requested if any filter requests them if available and the results adjusted appropriately for each filter. Edit: make selection of adjustments through optional parameters on Session methods.