Sorry if I have been too vague or unclear.

Try thinking about how to tie all those tools together. That is what we are doing.

You are right about multi-talented servers. We have the code that makes an MTA do more than be just an MTA. However, we are not looking for a multi-talented MTA. We just want a good solid, extensible MTA. To a point, all MTAs are extensible as are all web servers, but certain web servers outshine others in that area. I am not certain if any MTAs outshine other MTAs in this way as well. It is starting to sound like there are four primarily used MTAs that fit the bill. Sendmail is something that keeps getting dogged for security (which is why we are looking elsewhere as well).

Using Perl in Apache is not the same thing as using perl in IIS or other web servers. I was unsure of any (if any) difference in MTAs in the same respect. It seems that there are few differences and those differences are less important than MTA functionality, speed, security and manageability. Which to me says basically, forget about any considerations in relation to how perl might be *plugged* into an MTA or how an MTA might call out to perl, just focus on the MTA as an MTA only and make sure certain minimum requirement for externalizing functionality can be met. Correct me if I am wrong.

And, thanks for your input anyway. Sometimes when I have not had time to sit down and create a presentation I do not have the clearest message. Good habit to take a few hours first.