Mutiple enqueues to the conversion channel

Question

Hi ,
I did set up a conversion where an AV product
scans an message before sending to the next channel ( basically ims-ms,tcp-local or tcp_intranel ) for delivery.
Recently I noticed that if I send an e-mail to 2 recipients(for instance) , a double copy of the message is enqueued the conversation channel and the AV product scans twice the same message ...
By adding the multiple keywords to the channel option , I can improve things so that if my 2 recipients are to be dequeued to the same channel it is scanned once ( for instance the 2 recipients are to be delivered local delivery)
But if it has to be delivered to 2 different channels ( for instance local and extranet) , it is still scanned twice.
Any option I am missing ? Can I instruct the channel to work only on the envelope of the message ?
Any help appreciated.
Thanks

Answer 1

I see there at least 2 reallly good ideas
Yep, that's how the conversion channel works.First one knowning that Sun suggests to use the
conversion channel for AV purpose , scanning based on
recipients rather than envelope is just a fantastic
for system usage.Our recommendations do change, as we incorporate new features, and our partners add new features, too.
Currently, the conversion channel is the recommended route IF the virus scanner is to be run via command-line. There are indeed some tradeoffs involved with the conversion channel, especially the inherent overhead of starting new processes for each message, address expansion before conversion, and such. This puts a limit on maximum throughput.
>
If your virus scanner works via smtp, you can use
the "aliasdetourhost" keyword instead, and send
such before address expansion. this requires
5.2hf2.02 or later.Second one, if my AV does why should I bother using
iMS , I just use my AV/SMTP package ? While we find that most AV packages are very good at AV, most of them (all I have seen), aren't very good at being a well-behaved SMTP server. The skills that are useful for writing an AV package are very different from those required to create a well-behaved SMTP product.
We find that when most folk expose an AV's smtp port to the general internet, you can get lots of problems, including:
Dropped messages
error messages
much higher load on the AV hardware.
To help deal with such, we recommend using Sun JES' MTA to "wrap" the AV system. By accepting all mail with our MTA, you first get the ability to reject mail that's not addressed to actual users, the ability to throttle connections, to "fix" many types of badly-formed messages, etc.
The new "aliasdetourhost" keyword allows you to select an incoming channel's messages to be sent to an AV system and to accept those messages back into the queue, at high performance, without starting up a new process for each message, and only once per message, even if it's addressed to all of your users. . . .
>
Likely a bad idea, but I have no idea what you did. . .
Thanks for the input even without a clear idea.