On 11/21/2007 6:36 AM, Igor Smitran wrote:
> Isn't port 25 needed for incoming mails? If you block port 25 how will
> some other sender out of your domain be able to send you an email?
> For example, if [EMAIL PROTECTED] wants to send you an email then he
> will come to your port 25 and deliver the email. He will not be able to
> do smtp auth because he is not your user.
> Or am i wrong?
>
> Igor
>
Absolutely. I'm not trying to block port 25. Of course I want to allow
other MTA's to connect.
What I am trying to do is block unencrypted authentication requests from
users trying to send outbound mail. I want to force them to have to use
the SSL service I've setup on port 465. As it stands, customers could
use unencrypted authentication even though I've provided a secure
option. I want to make that unavailable to them.
As I said, it was quite easy to do this with my qmailrocks machine. I'm
just trying to figure out how to accomplish the same thing on a
qmailtoaster box.
Adam
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
