Re: Exchange 2007 does not resolve the second SMTP address

No restarts required.

--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------




"Berger" <Berger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:03742294-B47E-44DC-B1A5-AA1AF47BA2C1@xxxxxxxxxxxxxxxx
You were right, my second accepted domain didn't had the -AddressBookEnabled
parameter set to $true. I made the change on the server, do I need to restart
the Transport service to make this happen?



"Bharat Suneja [MSFT]" wrote:

- So you want to make sure mail for non-existent recipients is dropped? For
this to happen, Recipient Filtering has to be enabled, and the option to
drop mail for non-existent recipients (aka "Recipient Validation) needs to
be selected.
- Is Recipient Validation enabled for that Accepted Domain? This is done by
setting the Accepted Domain's -AddressBookEnabled parameter to $true. Note,
this generally shouldn't be done for External Relay domain because none of
the recipients exist in your Organization.

Get-AcceptedDomain | fl

Take a look at the Accepted Domain - is AddressBookEnabled set to true? If
not:
Set-AcceptedDomain "Accepted Domain Name" -AddressBookEnabled $true

--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------




"Berger" <Berger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C1B319DB-EB28-4649-9DA9-21323752FD43@xxxxxxxxxxxxxxxx
> So far I'm getting this only from a Telnet session, not from a mail
> client.
> We were looking at how secure our Exchange server was, and discovered > this
> behavior. I cant get my hand on any document on the Web relating to > this
> behavior, this is the reason I'm posting here.
>
>
>
> "Bharat Suneja [MSFT]" wrote:
>
>> >> The problem is that whenever
>> > someone send an email to an invalid address to the cde.com domain,
>> > Exchange
>> > will accept the message, until it hits the server, and then return a
>> > NDR.
>>
>> - Which clients and what are they using to submit messages? >> Outlook/MAPI,
>> OWA, EAS, or POP3/IMAP4 clients using SMTP?
>> - By default, the proxyAddresses attribute is set for ANR (Ambiguous >> Name
>> Resolution)
>> -- >> Bharat Suneja
>> Microsoft Corporation
>> blog: exchangepedia.com/blog
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>> ----------------------------
>>
>>
>>
>>
>> "Berger" <Berger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:F0CE7FEF-82F1-4014-B56E-6BBF484EF337@xxxxxxxxxxxxxxxx
>> > Our Exchange 2007 server is set to accept abc.com and cde.com SMTP
>> > address.
>> > Any client authenticating to our Exchange server are able to resolve
>> > name
>> > for
>> > any SMTP address in the abc.com domain, but not able to do so for >> > the
>> > cde.com. Both of my accepted domain are set to authorative, and we >> > are
>> > receiving emails for both domains just fine. The problem is that
>> > whenever
>> > someone send an email to an invalid address to the cde.com domain,
>> > Exchange
>> > will accept the message, until it hits the server, and then return a
>> > NDR.
>> >
>> > Further more, if I'm using a Telnet session and connect from outside >> > on
>> > port
>> > 25, I'm able to put nonvalid@xxxxxxx in the rcpt to: feild, and I'm
>> > able
>> > to
>> > send the message to the Exchange, and then it will send a NDR back.
>> >
>> > Does anyone out there experience the same behavior, and how can I >> > fix
>> > that.
>>
>>



.

Relevant Pages

  • Re: Exchange not receiving email from Internet
    ... Recieved email for that domain from internet. ... I understand that your exchange unable to ... permission to send to this recipient". ... The Exchange server Directory Access tab error may not related to ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Name
    ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... Configure the SMTP virtual server in Exchange to send mail with unresolved ... recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... of their e-mail server). ... This is the same for POP3 and SMTP, ... the "Microsoft Exchange MTA Stacks" service is not ... Configure the Default Policy in the Exchange recipient policy to use the ...
    (microsoft.public.windows.server.sbs)
  • Re: Send E-Mails to 2 SMTP Server
    ... You can configure the exchange server to host multiple SMTP mail domains on ... Click to expand the Recipients container and then click Recipient ...
    (microsoft.public.windows.server.sbs)
  • Re: e-mail messages stop in categorizer problem
    ... Based on my experience, since this is a SBS server, you can simply run ... In the right pane, click "Connect to the Internet", and then click ... Open the Exchange System Manager, go to Recipients -> Recipient ...
    (microsoft.public.windows.server.sbs)
Loading