That's certainly possible, but I see no reason for clients to connect to
barracuda at all, and it's up to the client configuration which host
they connect to. Having authenticating clients submitting elsewhere also
allows barracuda to be configured to reject all local domains, as they
would all be forged, making the appliance a little more effective. Plus,
barracuda doesn't need to handle authentications at all this way.
My impression is that QMT with spamdyke is equally as effective as
barracuda, so why waste money and resources on barracuda? Also note that
with any front-edge device, spamdyke on QMT becomes virtually ineffective.
To each his own though.
Thanks.
--
-Eric 'shubes'
On 12/06/2014 11:45 AM, Rajesh M wrote:
i recently had a barracuada tech guy visit me
as far as i understand all users will connect to barracuda appliance -- it
monitors both mx (incoming mails) and also outgoing emails (authenticated
senders) for outgoing spam.
incoming emails will be filtered and sent to the qmt box and forward it to qmt
box
qmt box smtp service will accept connections only from barracuda.
pop3 / imap users will download emails from qmt box but send via barracuda
server.
rajesh
----- Original Message -----
From: Eric Shubert [mailto:[email protected]]
To: [email protected]
Sent: Sat, 06 Dec 2014 11:34:40 -0700
Subject: [qmailtoaster] Re: smtp auth
I'm not sure you want to do this. This would make barracuda an open
relay, allowing it to send to *any* domain, not just the ones local to
your QMT.
Are your clients submitting to barracuda or QMT?? I was thinking that
barracuda was handling only MX (incoming) traffic. What's the point of
having barracuda handling submissions?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
