Robert Spier wrote:
I'm saying do something like this:
Create a set of wrapped plugins....
my-smtp-forward
my-qmail-queue
my-qmail-qmqpc
We know what order they will run in because it is defined in the
config file.
No, I get that alright, but I want to be able to do "tricksy Hobbit" things like
this:
[EMAIL PROTECTED] smtp-forward 1 12.38.22.128
[EMAIL PROTECTED] smtp-forward 2 12.38.22.130
[EMAIL PROTECTED] qmail-queue 3
where I first attempt to deliver to the dspam appliance and if that fails (for
example because the address is a list which doesn't have a profile in dspam),
then I try and deliver to the main SMTP server, and if /that/ fails (because the
machine is down for maintenance), then I queue it locally to try again later.
I want the wrapping to be at the "queue this message" level rather than at the
individual queue type. What this will wind up doing (for me at least) is
pulling the queue configuration out of config/plugins into a dedicated config
file, where I can do all sorts of very specific routing at the back end (since I
host some domains on different servers). I don't think it will wind up looking
that much more complicated in the end, but it will be much more flexible.
John
