On Tue, 2012-08-14 at 11:53 -0400, Wietse Venema wrote: > The scheduler API (actually a protocol) would then receive requests > containing (sender, recipients) and it would reply with one or more > (sender, transport, nexthop, recipients) responses. The scheduler > would append these to its per-transport-per-destination queues.
This would be great! I think the only thing missing in the reply is a field indicating whether the sender is SASL-authenticated, so that one can differentiate between an outgoing message sent by a local user and a redirect. Andre
