Chris V

Trying to setup a receive connector to relay mail that would have a more restricted RemoteIPRange.  According to Technet, you can have multiple recieve connectors on the same IP/Port combination as long as the RemoteIPRange overlap, the most restrictive will be used.

So I setup a receive connector restricted to 2 server IPs but on the same port (25) as the Default FrontEnd Connector (single server environment).   The 2 servers would work fine and connect to the new Send Connector.   However, the Default Frontend EXCH01 would stop recieving traffic, which has a IP range of 0.0.0.0   Any connections from other servers would get the following message on connecting:  421 4.3.2 Service not available.    So for the time being, I've moved the receive connector to  for relaying to port 26 and everything is working.    

Is there something in the configuration of a receive connector that I'm missing.  I know i've done this on Exchange 2010 without issue.

451 4.7.0 Temporary server error. Please try again later. PRX2

does anyone know exactly what causes this error? there are many references to it on the web, but nobody seems to know exactly what causes it. maybe it's something to do with DNS?

can someone please ask someone on the exchange team to help document this?

Hi,

I have below enviroment where I am not able to send email from Ex2013 box "Users" to Ex2007 box "users" or even Exchange 2013 "Users" are not able to send email themself.  all emails are going into queue

1 DC 2003 SP2

1 Exchange 2007 with all roles on single server

1 Exchange 2013 with all roles are on single server.

Hi ,

for email communication between Ex2003 ---> Ex2007 / 2010 is through  interop routing group connector .

My question is how email communicate between Ex2007 ----> 2010-- 2013 or vice versa

Hi,

Hoping someone can help me with a little issue I have please?

Our Exchange admin has left the firm and I have picked this up with very little experience of Exchange.

In short we have moved our internal SMTP relay from 2003 to 2010 and come up against some issues, all of which I have overcome bar one, our Finance team send various emails from their billing system to users and themselves in various ways, Anonymous, sending as an internal user to the same internal user but relaying with an admin account etc etc.

They also send emails to internal users as a completely different made up but relavant name to the actual firms domain, for example, our internal domain is company.com and all in internal users SMTP address is company.com, however they need their finance system to relay to users as an address from finance.com, this isn't a mailbox it's just a name their system uses and sends via our internal smtp relay/receive connectors.

I have setup a new internal receive connector that applies to only their finance subnet allowing anonymous, however I'm at a loss as to how to allow the finance.com domain to relay to our internal users, I'm assuming I need to create an authoritative domain or similar but do not just want to go playing around on a live environment.

Any help would be greatly received.

Many Thanks

Steve

Greetings,

We're trying to roll out TLS 1.2 in our test environment and can't seem to get Exchange to work with the protocol.

We've been using this method to enable TLS 1.2 (and disable the other protocols - TLS1.0, SSL2.0, SSL3.0, PCT1.0): http://www.adminhorror.com/2011/10/enable-tls-11-and-tls-12-on-windows_1853.html

We originally tried using Exchange 2010 on 2008 R2, but then I ran across this article saying that it is not supported: http://support.microsoft.com/kb/2709167/en-us

We've since tried to set it up with Exchange 2013 on Server 2012. Still no luck. The only time Exchange wants to work is when TLS1.0 is enabled.

I suspect that TLS1.1 and TLS 1.2 are also not supported on Exchange 2013, or that I'm changing the wrong registry keys, but I wanted to find confirmation. I've searched extensively and can't find any documentation leading me to believe one way or the other if it's supported.

Any help or insight would be greatly appreciated. Thanks!

--Aric

Silvio Tavares - Analista de Sistemas

Update

In my case the problem is about our ISP's network, they have some filtering device/software that work incorrectly, then it blocks our large mail to Yahoo.

Dear all

Recently I founded an Exchange Server problem that I cannot know why it happens. I'm working on Exchange Technology since 2000 and this is the first problem that I cannot find any resolution. Please help me if you can.

My new company use a newly implement Exchange Server 2013 (No previous version in this company).

Our sending IP is not listed in any RBL, I have reverse DNS record that matched the sending IP (also matched MX record), Sending IP is on SPF record.

Send connector is using MX's DNS name in HELO message (Force HELO is enabled).

I can send mail to all major mail provider (Gmail, Outlook.com and others) except the Yahoo.

In many testing I founded most of smaller mail (0-3 MB) can send to Yahoo without any problems, but bigger mail (In the test I use 10MB attachment) can't.

I check all my firewall/content filtering gateway, no filtering settings or something like that is founded. For Exchange Server, no message size restriction is configured and no special configuration for Yahoo.

I also test my configuration with Exchange Remote Connectivity Analyzer (Outbound SMTP) and no problem founded.

I check the SMTP log and found this error

HandleError has encountered a suspicious connection reset from a remote, non-mailbox transport server (will retry in 00:10:00)

The full log is (I change the real domain and some privacy data)

2013-07-22T16:30:04.335Z,Mail Connector,08D053603E76D1D8,0,,98.136.216.26:25,*,,attempting to connect
2013-07-22T16:30:04.351Z,Mail Connector,08D053603E76D1D8,1,192.168.1.13:32418,98.136.216.26:25,+,,
2013-07-22T16:30:04.834Z,Mail Connector,08D053603E76D1D8,2,192.168.1.13:32418,98.136.216.26:25,<,220 mta1075.mail.gq1.yahoo.com ESMTP YSmtpProxy service ready,
2013-07-22T16:30:04.834Z,Mail Connector,08D053603E76D1D8,3,192.168.1.13:32418,98.136.216.26:25,>,HELO mymail.com,
2013-07-22T16:30:05.255Z,Mail Connector,08D053603E76D1D8,4,192.168.1.13:32418,98.136.216.26:25,<,250 mta1075.mail.gq1.yahoo.com,
2013-07-22T16:30:05.255Z,Mail Connector,08D053603E76D1D8,5,192.168.1.13:32418,98.136.216.26:25,*,,sending message with RecordId 12309376270368 and InternetMessageId <f6ca2855b4e549969e9d71d7dc7302da@srv1.mymail.com>
2013-07-22T16:30:05.255Z,Mail Connector,08D053603E76D1D8,6,192.168.1.13:32418,98.136.216.26:25,>,MAIL FROM:<usr1@mymail.com>,
2013-07-22T16:30:05.521Z,Mail Connector,08D053603E76D1D8,7,192.168.1.13:32418,98.136.216.26:25,<,250 sender <usr1@mymail.com> ok,
2013-07-22T16:30:05.521Z,Mail Connector,08D053603E76D1D8,8,192.168.1.13:32418,98.136.216.26:25,>,RCPT TO:<yahoousr@yahoo.com>,
2013-07-22T16:30:05.770Z,Mail Connector,08D053603E76D1D8,9,192.168.1.13:32418,98.136.216.26:25,<,250 recipient <yahoousr@yahoo.com> ok,
2013-07-22T16:30:06.051Z,Mail Connector,08D053603E76D1D8,10,192.168.1.13:32418,98.136.216.26:25,>,DATA,
2013-07-22T16:30:06.067Z,Mail Connector,08D053603E76D1D8,11,192.168.1.13:32418,98.136.216.26:25,<,354 end data with <CR><LF>.<CR><LF>,
2013-07-22T16:30:10.793Z,Mail Connector,08D053603E76D1D8,12,192.168.1.13:32418,98.136.216.26:25,*,,"HandleError has encountered a suspicious connection reset from a remote, non-mailbox transport server (will retry in 00:10:00)."
2013-07-22T16:30:10.793Z,Mail Connector,08D053603E76D1D8,13,192.168.1.13:32418,98.136.216.26:25,-,,Remote

At present, because we cannot send mail directly to Yahoo, then we send mail to Yahoo via our ISP's relay (we add ISP's relay IP to our SPF record) and it works fine. But for me, this solution is not a good solution because our ISP's relay has some restriction and I'm not sure they will block us or not in the future if their policy changed. 

Please help me if you can.

Regards

Jun.

New 2013 implementation... Two Servers (Front End and Back End) both running Exchange 2013.

I am having trouble sending a local AD Exchange mailbox mail to external SMTP address.  I have tried several options.. I have created an "contact" as was required in previous versions.  I have created new AD accounts with external SMTP addresses, I have also attempted to use the scriptlet:

Set-Mailbox -Identity "%AD-USER%" -DeliverToMailboxAndForward $true -ForwardingSMTPAddressexternaluser@mail.com  (%AD-USER% was actual AD Username/mailbox) andexternaluser@mail.com was actual receipient SMTP address (username@gmail.com)

Local AD Mailbox receives the mail appropriately however I have enabled forwarding everyway I know how and nothing seems to work.  If I send mail straight from my account to the destination SMTP address, they get it; just not if it is sent to the local AD account then forwarded via -DeliverToMailboxAndForward command...

Please help.. I have several users that I need to have their mail CC'd to an external SMTP address.. Previous versions of Exchange required a "Contact" to be created and then the mailbox forwarded to that contact, which had a SMPT mail address...

Im not adverse to implementing via powershell if I can just get it to work... Any suggestions are greatly appreciated and needed.

We moved to another location and got a new ip from ISP and our exchange server is not able to send emails to some recipients getting .mail.protection.outlook.com error.

user@domain.com
BN1AFFO11FD036.mail.protection.outlook.com #550 5.7.1 Service unavailable; Client host [72.76.xxx.xx] blocked using Blocklist 1; To request removal from this list please forward this message todelist@messaging.microsoft.com ##

This is the error I am getting and I did email to delist@messaging.microsoft.com and I am wondering when will my IP get unblocked as this is causing a lot of communication issues. I checked my ip for blacklist but its not in any database. Hope I'll be able to find some solution soon on this.

I have Exchange 2013 CU2. Recently, one of our users received an e-mail message with sender's addressuser_a.b.@domain.com. It was impossible to reply to that address because Exchange refused to accept it:

----- The following addresses had permanent fatal errors ----- <ADDRESS> (reason: 501 5.1.3 Invalid address)

It was possible to send the message if the second dot was removed (i.e. no more ".@" combination). Of course, it could not be delivered anyways (no such mailbox).

I've conducted some experiments and found that both my mail server running Sendmail and Google mail system accept that address and deliver messages to it.

Why does Exchange behave in such a way?

Hi all

Its me again.

I am trying to update the inbuilt malware definitions according to the instructions in article.

http://technet.microsoft.com/en-us/library/jj657471.aspx

& $env:ExchangeInstallPath\Scripts\Update-MalwareFilteringServer.ps1 -Identity <FQDN of server>

I am getting the following two events  see below on all the mailbox servers. I obviously cannot go into production Exchange 2013 RTM on Windows 2012 Servers and Domaincontrollers.

Log Name:      Application
Source:        Microsoft-Filtering-FIPFS
Date:          1/29/2013 2:50:45 PM
Event ID:      6027
Task Category: None
Level:         Error
Keywords:     
User:          NETWORK SERVICE
Computer:    Removed To Protect The Innocent 
Description:
MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path:http://forefrontdl.microsoft.com/server/scanengineupdate
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Filtering-FIPFS" Guid="{1BE3A000-EA09-4AB8-B0A0-30BBB6793D80}" />
    <EventID>6027</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-01-29T12:50:45.262896300Z" />
    <EventRecordID>120660</EventRecordID>
    <Correlation />
    <Execution ProcessID="2584" ThreadID="3752" />
    <Channel>Application</Channel>
    <Computer>Removed To Protect The Innocent
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="UpdatePath">http://forefrontdl.microsoft.com/server/scanengineupdate</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-Filtering-FIPFS
Date:          1/29/2013 2:53:25 PM
Event ID:      6024
Task Category: None
Level:         Information
Keywords:     
User:          NETWORK SERVICE
Computer:     Removed To Protect The Innocent
Description:
MS Filtering Engine Update process is checking for new engine updates.
 Scan Engine: Microsoft
 Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Filtering-FIPFS" Guid="{1BE3A000-EA09-4AB8-B0A0-30BBB6793D80}" />
    <EventID>6024</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-01-29T12:53:25.654390000Z" />
    <EventRecordID>120667</EventRecordID>
    <Correlation />
    <Execution ProcessID="2584" ThreadID="3752" />
    <Channel>Application</Channel>
    <Computer> Removed To Protect The Innocent
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="EngineName">Microsoft</Data>
    <Data Name="UpdatePath">http://forefrontdl.microsoft.com/server/scanengineupdate</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-Filtering-FIPFS
Date:          1/29/2013 2:56:07 PM
Event ID:      6030
Task Category: None
Level:         Information
Keywords:     
User:          NETWORK SERVICE
Computer:   Removed To Protect The Innocent  
Description:
MS Filtering Engine Update process is attempting to download a scan engine update.
 Scan Engine: Microsoft
 Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Filtering-FIPFS" Guid="{1BE3A000-EA09-4AB8-B0A0-30BBB6793D80}" />
    <EventID>6030</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-01-29T12:56:07.715314800Z" />
    <EventRecordID>120668</EventRecordID>
    <Correlation />
    <Execution ProcessID="2584" ThreadID="3748" />
    <Channel>Application</Channel>
    <Computer> Removed To Protect The Innocent
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="EngineName">Microsoft</Data>
    <Data Name="UpdatePath">http://forefrontdl.microsoft.com/server/scanengineupdate</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-Filtering-FIPFS
Date:          1/29/2013 3:48:03 PM
Event ID:      7003
Task Category: None
Level:         Information
Keywords:     
User:          NETWORK SERVICE
Computer:    Removed To Protect The Innocent 
Description:
MS Filtering Engine Update process has successfully scheduled all update jobs.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Filtering-FIPFS" Guid="{1BE3A000-EA09-4AB8-B0A0-30BBB6793D80}" />
    <EventID>7003</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2013-01-29T13:48:03.321784200Z" />
    <EventRecordID>120776</EventRecordID>
    <Correlation />
    <Execution ProcessID="2584" ThreadID="21120" />
    <Channel>Application</Channel>
    <Computer>Removed To Protect The Innocent</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
  </EventData>
</Event>

Regards

Bright

We have a few groups (HR and Legal) that provide services for a few different companies.  I would like the groups to be able to send/receive messages from multiple email domains, but I would like to avoid each user having multiple Mailboxes on the system (each with multiple calendars, contact lists, GAL entries, etc)

It is so easy to add additional inbound alias, but I for the life of me cannot find a good solution for sending Outbound via an alias. 

Does anyone have any suggestions for how they've done something similar in their own org?

We're running Exchange 2010 and Outlook 2013.

I received an email in my mailbox today which has given me some concern.  The email has the following header -

Received: from EXCHANGE2.local.xxxxxxxxxx.co.uk (192.168.0.72) by
 EXCHANGE2.local.xxxxxxxxx.co.uk (192.168.0.72) with Microsoft SMTP Server
 (TLS) id 15.0.712.22 via Mailbox Transport; Wed, 21 Aug 2013 14:42:09 +0100
Received: from EXCHANGE2.local.xxxxxxxx.co.uk (192.168.0.72) by
 EXCHANGE2.local.xxxxxxxxxx.co.uk (192.168.0.72) with Microsoft SMTP Server
 (TLS) id 15.0.712.22; Wed, 21 Aug 2013 14:41:33 +0100
Received: from 10ibl21ser04.datacenter.cha.cantv.net (200.11.173.10) by
 EXCHANGE2.local.xxxxxxxxxx.co.uk (192.168.0.72) with Microsoft SMTP Server
 id 15.0.712.22 via Frontend Transport; Wed, 21 Aug 2013 14:41:32 +0100
X-Virus-Scanned: amavisd-new at cantv.net
Received: from webmail-06.datacenter.cha.cantv.net
 (webmail-06.datacenter.cha.cantv.net [200.11.153.89]) (authenticated bits=0)
 by 10ibl21ser04.datacenter.cha.cantv.net (8.14.3/8.14.3/3.0) with ESMTP id
 r7LDenkD016671; Wed, 21 Aug 2013 09:10:49 -0430
X-Matched-Lists: []
Received: from 81.91.229.189 ([81.91.229.189]) by
 webmail-06.datacenter.cha.cantv.net (Cantv Webmail) with HTTP; Wed, 21 Aug
 2013 09:10:49 -0430 (VET)
Date: Wed, 21 Aug 2013 09:10:49 -0430
From: okakaoffice <okakaoffice@cantv.net>
Reply-To: <dhl-expressdeliverycourier56788cmpny@56788.com>
To: <family@mpdeegan.wanadoo.co.u>
Message-ID: <2099142773.5215096.1377092449211.JavaMail.gess@webmail-06.datacenter.cha.cantv.net>
Subject: CONTACT MR. HARRY MORRIS FOR YOUR ATM CARD OF 2.5USD
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Cantv Webmail
X-Originating-IP: [81.91.229.189]
Return-Path: okakaoffice@cantv.net
X-MS-Exchange-Organization-PRD: cantv.net
X-MS-Exchange-Organization-SenderIdResult: Pass
Received-SPF: Pass (EXCHANGE2.local.xxxxxxxxxxx.co.uk: domain of
 okakaoffice@cantv.net designates 200.11.173.10 as permitted sender)
 receiver=EXCHANGE2.local.xxxxxxxxx.co.uk; client-ip=200.11.173.10;
 helo=10ibl21ser04.datacenter.cha.cantv.net;
X-MS-Exchange-Organization-Network-Message-Id: 095595f4-456c-4202-8988-08d06c8b48c8
X-MS-Exchange-Organization-SCL: 6
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.5705.600;SID:SenderIDStatus Pass;OrigIP:200.11.173.10
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: EXCHANGE2.local.xxxxxxxxxxx.co.uk
X-MS-Exchange-Organization-AuthAs: Anonymous

The message tracking log does indicate that my mail box was the one the message was targeted at.  However how does the header say otherwise?

EventId  Source   Sender                            Recipients                        MessageSubject
-------  ------   ------                            ----------                        --------------
HARED... SMTP     okakaoffice@cantv.net            {me@xxxxxxxxxx... CONTACT MR. HARRY MORRIS FOR Y...
RECEIVE  SMTP     okakaoffice@cantv.net            {me@xxxxxxxxxx... CONTACT MR. HARRY MORRIS FOR Y...
AGENT... AGENT    okakaoffice@cantv.net            {me@xxxxxxxxxx... CONTACT MR. HARRY MORRIS FOR Y...
SEND     SMTP     okakaoffice@cantv.net            {me@xxxxxxxxxx... CONTACT MR. HARRY MORRIS FOR Y...
DELIVER  STORE... okakaoffice@cantv.net            {me@xxxxxxxxx... CONTACT MR. HARRY MORRIS FOR Y...

Exchange has been configured to reject email if the receiving mailbox does not exist.  In this instanceme@xxxxxxxxxx does exist but how come the header indicates otherwise.  family@mpdeegan.wanadoo.co.u does not exist on my server!

Further concerned because the SPF got a pass.  How did the spammer do this and have I got something to worry about?

Many thanks in anticipation of your replies.

I have a fresh install of 2 2013 servers  Front CAS and Back MBX role coexistent with 2007.

It was working fine until this weekend when we moved the DNS names to 2013. Meaning we moved owa/ol etc site names in DNS  and adjusted the virtual directories on both 2007 to legacy.xxx.com and mail.xx.com to the new 2013.

What now is happening is the 2 services "microsoft Exchange mailbox transport submission and microsoft exchange mailbox transport delivery services are not starting.. The only error i get is the standard "the service did not respond to the start or control request in a timely fashion."e

Its preventing any 2013 mialbox from send/recieve.  

I have checked and IPv6 is ON, the connectors are scoped ONLY to the IPv4 address. The MBX server is configured with internal/external DNS and the send connector is using external DNS.  I found that here http://social.technet.microsoft.com/Forums/exchange/en-US/26cc797d-6a40-4e18-bdb9-0e0387a12da1/the-microsoft-exchange-mailbox-transport-submission-service-terminated-unexpectedly 

Need help resolving this as its preventing moving anymailboxes to it.. All other services are working OWA proxy to 2007 etc and mail flow to and from 2007 are all working..

Thanks, Grady Vogt

Hi all,

I've got an issue with Exchange 2007 and an Exchange Online mail service (Office365). I was pointed here for additional assistance. The issue is Exchange 2007 users cannot mail Office365 users. I have verified it's not on the Office365 end as I can send and receive emails from other services such as Google Mail.

Background:

We have 3 domains, I'll name them as colors to distinguish them and for privacy reasons. Here's the list with their purpose:

• white.local.lan - internal domain
  
• red.com - Faculty Email Domain (Exchange 2007) and Website Domain
  
• blue.com - Students Email Domain (Exchange Online via Office365)

We have created a UPN suffix of blue.com in order to match them with the Office365 domain. All students are assigned this suffix. We have created records in the proxyAddresses attribute of Active Directory for the purpose of DirSync via Forefront Identity Manager. This is working well.

Every time we send an email to an address in the proxyAddresses attribute we get bounce messages as follows:

Delivery has failed to these recipients or distribution lists:
John Smith
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.

_____
Sent by Microsoft Exchange Server 2007 

Diagnostic information for administrators:

Generating server: EXCHANGE.white.local.lan
IMCEAEX-_O=NT5_ou=3865e760e8c9484fafde58fe9e1f40cf_cn=9e9257a09938de4ca69181ebb94aff38@red.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:
Received: from EXCHANGE.white.local.lan 
([...]) by EXCHANGE.white.local.lan 
([...]) with mapi; Thu, 22 Aug 2013 16:11:09 +1000
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: James Elliott <James.Elliott@red.com>
To: John Smith    <IMCEAEX-_O=NT5_ou=3865e760e8c9484fafde58fe9e1f40cf_cn=9e9257a09938de4ca69181ebb94aff38@red.com>
Date: Thu, 22 Aug 2013 16:10:51 +1000
Subject: Outbound Test
Thread-Topic: Outbound Test
Thread-Index: Ac6e/lgzDPoWcQUgSC6bvsDNW0O2dg==
Message-ID: <ADBD636EDF962E4AB0F6B86D7399B14301D1274D4B@EXCHANGE.white.local.lan>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <ADBD636EDF962E4AB0F6B86D7399B14301D1274D4B@EXCHANGE.white.local.lan>
MIME-Version: 1.0

Destination User Attributes (UPN: smithj@blue.com):

proxyAddresses:

SMTP:John.Smith@blue.com;smtp:smithj@blue.com;SIP:John.Smith@blue.com

mail:

John.Smith@blue.com

mailNickname

<not set>

We have set up the following in Exchange 2007:

[Organization Configuration] -> [Accepted Domains]

Accepted Domain: blue.com
Default: False
After MSEXCH Accepts: External Relay Domain

[Organization Configuration] -> [Send Connectors]

GENERAL
Protocol Logging Level: None
Specify the FQDN this connector will provide in response to HELO or EHLO:<blank>
Max Message Size (KB): 10240

ADDRESS SPACE
Type: SMTP
Address: blue.com
Cost: 1
Scoped Send Connector: unchecked / no

NETWORK
Select how to send mail with this connector: Use domain name system (DNS) "MX" records to route mail automatically
Enable Domain Security (Mutual Auth TLS): unchecked / no
Use the External DNS Lookup Settings on the transport server: checked / yes

SOURCE SERVER
Name:<Exchange Hostname>
Site: <Site Name>
Role: Mailbox, Client Access, Hub Transport

Hello guys

Exchange 2010 SP1/ 

Here is my requirement. 

We have 3 Databases. VIP, Normal Users, accounts. I have created User Group Call "Help Desk" . They Should be able to modify the User Attributes ( such as Display Name ) only  user inside the Normal Users. 

They should not be able to do any changes for users inside VIP . 

how can we do this ?

regards 

Hi there,

I am struggling with understanding security implication of the anonymous permission on the default receive connector. I am looking for a steer in the right direction:)

I have exchange 2010 SP3 stand alone server with hub transport behind a firewall (no edge). We do have a 3rd party service (spam filter) that relays clean emails to our exchange server.

Currently i have a default setup receive connector that is configured to receive emails for any IP and a rule in the firewall to relay traffic on port 25 to the exchange server.

Recently i came to realization that all of my internal devices such as multi functional printers, UPS, NAS, etc are able to send notification emails to me without any authentication involved. That would mean, if say a virus hit any of my client computers, it would have a green light to spam everyone internally or externally without much effort!

Is this correct?

Obviously, if i uncheck anonymous permission in default receive connector, my server won't be able to receive anything at all.

Are there any best practices to secure this flaw? limit which anonymous INTERNAL devices can use my exchange as a relay? how about External anonymous clients, is it a concern?