Re: SMTP TLS

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Sep 1, 3:35 pm, wildgoosed <david.wildgo...@xxxxxxxxx> wrote:
On Sep 1, 2:09 pm, "Ed Crowley [MVP]" <cursp...@xxxxxxxxxx> wrote:





"Default" is your regular inbound SMTP.  "Client" is the client submission
port, which is now 587 to eliminate the need to enable relay on your regular
SMTP port to support POP and IMAP clients.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"wildgoosed" <david.wildgo...@xxxxxxxxx> wrote in message

news:6ff33013-7f75-4367-ad19-da0a540393c9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Aug 31, 7:10 pm, "Rich Matheisen [MVP]"

<richn...@xxxxxxxxxxxxxxxxxxxxx> wrote:
On Mon, 31 Aug 2009 11:20:10 -0700 (PDT), wildgoosed

<david.wildgo...@xxxxxxxxx> wrote:

[ snip ]

I'm pretty sure it is.

telnet 192.168.1.8 25 (local ip for this server)

220 london.ia.localMicrosoft ESMTP MAIL Service ready at Mon, 31 Aug
2009 12:16
:19 -0600
ehlo
250-london.ia.local Hello [192.168.0.20]
250-SIZE
250-DSN
250 AUTH NTLM

Here's what you should be seeing if you say EHLO to your default SMTP
receive connector:

250-SIZE
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250-XEXCH50
250 XRDST

So, is it your default receive connector you're connecting to? And if
it is, where did all the other keywords disappear to?

Do you have more than one receive connector for this machine? If you
do, is the one that works with your remoteiprange configured
correctly? Use "get-receiveconnector | fl" and check the values of
these properties:

AuthMechanism
BinaryMimeEnabled
ChunkingEnabled
EightBitMimeEnabled
EnhancedStatusCodesEnabled
PipeliningEnabled

Maybe someone's "secured" your reveive connector to the point it no
longer functions the way you expect it to?
---
Rich Matheisen
MCSE+I, Exchange MVP

I've done some testing here and here are my results so far.

I installed the telnet client on the server and locally connected to
port 25. I issued the ehlo command and got the following!

220 london.ia.local Microsoft ESMTP MAIL Service ready at Tue, 1 Sep
2009 11:04:
46 -0600
ehlo
250-london.ia.local Hello [::1]
250-SIZE
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250-XEXCH50
250 XRDST

This Exchange server is behind a firewall, but there is no smtp proxy
so I don't understand why clients on our network and clients outside
our network see different connections options.

Here is the output from get-receiveconnectors

[PS] C:\Windows\System32>get-receiveconnector

Identity              Bindings              Enabled
--------              --------              -------
LONDON\Default LONDON {:::25, 0.0.0.0:25}   True
LONDON\Client LONDON  {:::587, 0.0.0.0:587} True

Here is some output from get-receiveconnectors | fl

Identity                                : LONDON\Default LONDON
AuthMechanism                           : Tls, Integrated, BasicAuth,
BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges                          : {::-
ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Identity                                : LONDON\Client LONDON
AuthMechanism                           : Tls, Integrated, BasicAuth,
BasicAuthRequireTLS
RemoteIPRanges                          : {::-
ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}

Hopefully someone can identify a problem here cause I don't see one.
Are there supposed to be 2 receive connectors?

Thanks for the info so far.

Anyone else have an idea?

Figured out the cause. Our spam/virus/phishing scanner on our gateway
was dumping the ehlo down to helo.

I'll contact our vendor and get the answer from them.

Thanks everyone.
.

Relevant Pages

  • Re: SMTP TLS
    ... SMTP port to support POP and IMAP clients. ... receive connector: ... 250-AUTH NTLM ...
    (microsoft.public.exchange.admin)
  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the clients ... weight 100, port 389, target srv5.mydomain.local ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding machine to domain with NATed IPs
    ... sounds that the DCs are not reaching the clients ... Type: SRV (Service location) ... weight 100, port 389, target srv5.mydomain.local ...
    (microsoft.public.windows.server.active_directory)
  • Re: DDoS to microsoft sites
    ... The primary difference between the two clients is that the first port scan I ... > - netbios (brute force attack on Administrator account) ... I'm guessing that the SQL server is the infection vector in both these ...
    (Incidents)
  • RE: Kerberos Configured, but occasionally users login using NTLM
    ... The clients are set to integrated authentication. ... and then all of a sudden they will have a login that uses NTLM. ... Microsoft Online Community Support ...
    (microsoft.public.inetserver.iis.security)