Re: SMTP tls problem in OExpress 0x800cc0f
- From: "David Beaven" <technet@xxxxxxxxx>
- Date: Fri, 23 Sep 2005 12:40:35 +0100
Winfred
Thanks for your reply
This is not our standard SMTP VS but is used for staff to send email when
away using an IMAP client and resides on a front end server. It is
configured for port 587 and port 25.
What port number will be used to deliver to back end servers?
If it relays (for authenticated users only) to an external address it sends
to another bridgehead SMTP connector. What port will it use?
If I tick allow anonymous access the 454 5.7.3 error disappears but this
will allow unauthenticated users sending inbound mail which we don't want.
Any ideas what is causing this?
Outlook XP can send inbound on port 587 (with anonymous access allowed) but
Outlook Express does not work (is this a known issue in OE?)
Since TLS can be set in the exchange client authentication tab (under basic
authentication) I assume it requires secure authentication for passwords,
rather than the whole conversation (data part of smtp message) if you
specify 'require secure channel'?
Thanks
David
""Winfred Weng [MSFT]"" <v-wweng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:5XIOjnBwFHA.780@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi David,
>
> Thank you for posting here!
>
> Basically, by enabling Secure Sockets Layer (SSL) we protect traffic that
> travels from clients to the server, while Transport Layer Security (TLS)
> secure traffic between the source SMTP server and destination server. The
> default port for SMTP communication is 25. Since you have enabled the 587
> port on the SMTP Virtual Server on Exchange, it should work when we also
> configure the port 587 on the client. This issue may occur if the port 587
> has been occupied. We can use the following method to verify this:
>
> On your Exchange Server, go to a command prompt, and type the following
> command:
>
> netstat -an
>
> This command will display all active ports that are listening on all
> interfaces. Choose a port number that does not conflict with any of those
> ports that are in use. For example, you may consider using a port above
> 1024, such as 5000, to test if this works.
>
> However, I would like to let you know that generally it is not recommended
> to change the default port (25) for SMTP communication to another one.
This
> is because the destination SMTP server may not listen to the custom port
we
> configure (it is 587 in our scenario). In this case, after we enable the
> TLS encryption, even if we are able to deliver the email from the Outlook
> Express client to our Exchange Server using this custom port, the message
> may still fail to transfer to the destination server.
>
> For additional information, you can refer to the following Microsoft KB
> article:
>
> 829721 How to help protect SMTP communication by using the Transport Layer
> http://support.microsoft.com/?id=829721
>
> I hope the information above is helpful.
>
> If anything in my post is unclear, feel free to let me know.
>
> Have a good day!
>
> Thanks & regards,
>
> Winfred Weng
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
> This and other support options are available here:
>
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/common/international.aspx
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
.
- Follow-Ups:
- Re: SMTP tls problem in OExpress 0x800cc0f
- From: "Winfred Weng [MSFT]"
- Re: SMTP tls problem in OExpress 0x800cc0f
- References:
- SMTP tls problem in OExpress 0x800cc0f
- From: David Beaven
- Re: SMTP tls problem in OExpress 0x800cc0f
- From: David Beaven
- Re: SMTP tls problem in OExpress 0x800cc0f
- From: "Winfred Weng [MSFT]"
- SMTP tls problem in OExpress 0x800cc0f
- Prev by Date: max. number of SMTP Adresses attached to user object?
- Next by Date: Re: no headers in bounces?
- Previous by thread: Re: SMTP tls problem in OExpress 0x800cc0f
- Next by thread: Re: SMTP tls problem in OExpress 0x800cc0f
- Index(es):
Relevant Pages
|