>> there is no attempt made to distinguish between local or external SMTP connections.

I always thought that the "intent" was to do just that, so maybe there should be a mechanism similar to that used by SpamHalter.

Thank you for your time.  I consider this resolved.  You guys do great work here!

[pi]

Maybe I should be asking this at the ClamWall website, but frankly, this site is much more responsive with similar users and similar issues.

I have the latest Mercury (4.62) and ClamWall (1.4.096) and ClamAV (0.95) provided by Hideout, but I don't think this is a version-related issue.  The system has been performing this way all the while, and I'm just now getting around to asking a question about it.

I am using MercuryS, C, P, D, SpamHalter, and ClamWall.  My questions concern ClamWall.  The Basic settings have checkboxes for "Leave messages from local senders untouched" and "Do not call antivirus on messages from local senders".  What's the difference here, and what's the logic behind the fact that checking the first will lock out the second?

My second question is, why, regardless of which of the above two are checked, does ClamWall still process my outbound email?  I send a simple test-message from a local machine (not the Mercury Server) at address 192.168.12.100, and the ClamWall log shows that it processes it on the outbound path.  SpamHalter does not do this... it has a nice, all-encompassing, "Local IP networks" setting where I enter 192.168.0.0/16.  ClamWall has no such setting, so I assume it uses the "Local domains" of the Mercury Core, but it doesn't seem to matter what I put in the Local domains list.  If not for the aforementioned checkboxes, how do I tell ClamWall to not waste cycles checking outbound mail from my local machines?

Which brings me to my last, unrelated question:  This has always been confusing.  Should the "Local domains" settings in the Core have all of my individual machines and their local IPs listed?  Right now it just has "names" for the Mercury Server machine, and the domain it represents, as per the Manual.

Thanks.

If I interpret the ClamWall manual correctly the "Leave messages from local senders untouched" option means that those messages will not be handled by ClamWall at all, while the second option ( "Do not call antivirus on messages from local senders") stops AV scanning while checks for banned extensions still will take place. That will as well explain the logic for disabling the second option if the first is selected.

Again according to the manual these options can exclude messages produced by the local mail system, but messages received by SMTP are always checked even if the sender is in your local network.

The local domains section in Mercury should only list domains (hostnames and IPs), not anything else that might be local.

/Rolf 

Thanks for the quick response.

That begs the question then, what exactly is the definition of a "local sender"?   It makes sense to me that a local sender would/could be any machine on the local LAN, or any machine that I might specify as a "local sender", but specified where, or how?  It's not a big deal that it processes outbound mail in this situation, but it just doesn't make sense that I can't configure the "logic", when apparently ClamWall wants to provide a method.

I think the wording may be a bit misleading here. ClamWall will allow you to exclude messages produced by the local mail system, i.e. produced by Mercury itself, added by direct network delivery by Pegasus clients, or added directly to the queue by some other application running on the same server (like webmail), but there is no attempt made to distinguish between local or external SMTP connections.

/Rolf