On 06/26/2012 10:53 PM, Pak Ogah wrote:
On 06/27/12 11:03, Eric Shubert wrote:
How to disable clam av and simscan for local to local mail
transcations.
Regards,
Rajamani
if you have 2 separate servers (MX w/ POP3 server and SMTP server) like
I have
then you can ask your users to use SMTP server for outgoing
after that you can configure simscan on SMTP server not to scan incoming
message from your local networks / authenticated users
---------------------------------------------------------------------
I like having message retrieval and message transports (submission and
reception) on separate hosts. Submission and reception could even be on
separate hosts. This effectively segregates roles, and allows for better
tailoring and tuning as well as scaling.
I don't see though how you'd tailor simscan to accomplish this while
still having all smtp traffic (submission and reception) being processed
by a single qmail instance. Simscan can be tailored according to the
recipient domain or address. I think that Raja is wanting to tailor
scanning according to the sender as well. Perhaps Pak is meaning that
he's separated submission/smtp from reception/smtp as well and just
didn't mention it.
This could be accomplished if you:
a) create a separate host for submissions (port 587)
b) configure all users to use the submission host's url (and port 587)
for their outbound smtp. It might be desirable to disable smtp-auth on
port 25 on the incoming smtp host.
c) disable clamav on the submission host, using one record for each
local domain in the simcontrol file.
Thanks Pak!
FWIW, it's my intention to make things easier in the future to create
these separate roles for QMT. It's fairly easy to do now using virtual
machines, but I'm hoping to be able to segregate things in a single QMT
host as well. If you'd like to keep up on such developments, please
subscribe to the devel list and strike up a conversation.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
