X-MS-Exchange-Organization-AuthAs is configured as Internal other than Anonymous from internet mails

Hi Admin,
We want to restrict distribute group not to receive internet mails, but the internet mails are still going through even if the option"only senders inside my organize" is selected. The part of mail header is below,
X-MS-Exchange-Organization-AuthSource: myexchange.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 10
The value of X-MS-Exchange-Organization-AuthAs is configured as "Internal" other than "Anonymous" from internet mails. Maybe this is the root cause, but I don't know how to resolve it. Currently the internet mails are first checked by
our symantec mail gateway then transfer to our CAS server (myexchange.com) as above.
Could somebody instruct me on this?
Many thanks in advanced.
Leon
Leon

Did you check "Externally Secured" on the anonymous receive connector or add the ip address of the Symantec Gateway to the allowed IP anti-spam list in Exchange?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

System won't let me configure to anything other than stereo

my pavilion dv7-7020us no longer allows me configure the sound as 4.1 or anything other than stereo. this problem started within the last couple of days tho i'm not sure exactly when as i mostly use headphones. i've reinstalled all of the system drivers and ofc the audio drivers and it made no difference. i'd rather like to get my sound working the way it's supposedta again.

anybody else had this problem?

Calendar information other than iCloud is not showing in Notification center from Mails such as Gmail, Exchange, Yahoo

Hi,
After iOS 6 update on iPhone 4S I'm unable to see any information on Notification Center regarding any calendar information from mail boxes such as Gmail, Yahoo, Exchange server etc. But, calendar information is available only from iCloud mail box.
Please help me to get the calendar information in Notification center from mail boxes other than iCloud too.
Regards,
Srini

Read thier own support document on the subject then
http://support.apple.com/kb/TS1795
This document was written as an answer to all those who complained about it as paying MobileMe users
They ignored us then and when MobileMe became iCloud they ignored us again, and just carried on with a system that will not update the e-mail read status across all devices
That's how it works, and like you 1000's of loyal Apple users cant believe it either but there you go

Not receiving emails from internet to email ids of exchange 2013

hi
1) i installed exchange 2013 , mails going out well, coming well, but from internet mails r not receieving to email ids of exchange 2013, i added receive connnector also, but not working.
2) how to take backup of exchange 2013 & individual mailbox of mail id
pls

Hi
For your question
Make sure that the anonymous permission is enabled on the default receive connector
Make sure the port 25 is open for inbound and outbound in your firewall
Telnet to port 25 from external network to your domain and ensure port 25 is open
To take a back up it may not be easy to answer on this because it depends on the bckup software you are using.
If you are using Windows server backup then you have the below tech-net which you can refer
http://technet.microsoft.com/en-us/library/dd876854(v=exchg.150).aspx
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Missing the "Microsoft Exchange Server Auth Certificate"

Hi Everyone,
I have a single Exchange box.
Was integrating my Lync and Exchange and noticed some issues after configuring my Lync pre-reqs: http://technet.microsoft.com/en-us/library/jj721919.aspx
Following the line of communication and event logs, I quickly saw that the error was not on my Lync Server, but on my Exchange. The "Microsoft Exchange Server Auth Certificate" that is created during Ex2013 install was missing.
It was not there to give out tokens for the Server to Server authentication required to integrate Lync, Exchange, and Sharepoint.
Running Get-AuthConfig: http://technet.microsoft.com/en-us/library/jj215766(v=exchg.150).aspx
pointed to a thumbprint that did not exist anymore.
I confirmed this by checking the local cert store (local computer>personal>certificates), looking in the ECP (servers>certificates), and also running Get-ExchangeCertificate
In my Exchange Server event log, I found the following errors:
Log Name: Application
Source: MSExchange Certificate Deployment
Date: 6/8/2014 4:00:50 AM
Event ID: 2005
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: server.domain.com
Description:
Federation or Auth certificate not found: ED2C3E86EBE821AAC2C0DEA85CAB5787E2CAC5F3. Unable to find the certificate in the local or neighboring sites. Confirm that the certificate is available in your topology and if necessary, reset the certificate on the Federation
Trust to a valid certificate using Set-FederationTrust or Set-AuthConfig. The certificate may take time to propagate to the local or neighboring sites.
Event Xml:
2005
3
1
0x80000000000000
2391484
Application
server.domain.com
ED2C3E86EBE821AAC2C0DEA85CAB5787E2CAC5F3
AND
Log Name: Application
Source: MSExchange OAuth
Date: 6/8/2014 1:25:41 PM
Event ID: 2004
Task Category: Configuration
Level: Warning
Keywords: Classic
User: N/A
Computer: server.domain.com
Description:
Unable to find the certificate with thumbprint ED2C3E86EBE821AAC2C0DEA85CAB5787E2CAC5F3 in the current computer or the certificate is missing private key. The certificate is needed to sign the outgoing token.
Event Xml:
2004
3
2
0x80000000000000
2397430
Application
server.domain.com
ED2C3E86EBE821AAC2C0DEA85CAB5787E2CAC5F3
Googling has only produced one article that is about another issue that I would have found further down the line if I wasn't testing within the pre-reqs. The solution is the same, but the article is somewhat poorly written and does not respond to all
the comments enough to leave one feeling it's 100% correct.
http://blogs.technet.com/b/jenstr/archive/2012/11/22/getting-internal-server-error-500-when-creating...
The broad strokes are clear:
The fix is to create a new "Microsoft Exchange Server Auth Certificate" by using the following sequence of cmdlets In EMS on the MBX server:
1. New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn= Microsoft Exchange Server Auth Certificate" -FriendlyName "Microsoft Exchange Server Auth Certificate" -Services smtp
Do not accept to replace the SMTP certificate when prompted
2. Note the thumbprint of the new certificate. Let us assume it is 7A39541F8DF58D4821967DD8F899B27410F7C081
3. $a=get-date
4. Set-AuthConfig -NewCertificateThumbprint 7A39541F8DF58D4821967DD8F899B27410F7C081 –NewCertificateEffectiveDate $a
Accept to continue despite the fact that the certificate effective date is not 48 hours into the future
5. Set-AuthConfig –PublishCertificate
6. Make sure to remove any potential reference to the previous certificate (which might not exist anymore) by doing Set-AuthConfig -ClearPreviousCertificate.
Remember to do iisreset on both CAS and MBX servers. Then finally, you can try to re-issue the New-CsPartnerApplication cmdlet.
65 Million Dollar question:
Is the syntax in part 1 correct? Two people says to add the domain? Jens responds, but it's vague. What would the correct command look like? I do not know where to add the -DomainName within the command and which name I
should add? The FQDN of the CAS?
New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn= Microsoft Exchange Server Auth Certificate" -FriendlyName "Microsoft Exchange Server Auth Certificate" -DomainName server.domain.com -Services
smtp
Thank you everyone

Hi,
Yes, we need to specify a valid FQDN for either the Subject or the DomainName parameter. Please run the following command:
New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn= Microsoft Exchange Server Auth Certificate" -FriendlyName "Microsoft Exchange Server Auth Certificate" -DomainName server.domain.com -Services
smtp
Then following the other steps in your posting to re-create the Microsoft Exchange Server Auth Certificate.
Regards,
Winnie Liang
TechNet Community Support

"Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run se

Team,
I am trying to Install Exchange on my Lab, getting below error
message.
The Schema Role is installed on Root Domain and trying to install
exchange on Child domain.
1 Root Domain - 1 Child domain. both are located on single site.
“Setup encountered a problem while validating
the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter and wait for
replication to complete.”
Followed below articles:
http://support.risualblogs.com/blog/2012/02/21/exchange-2010-sp2-upgrade-issue-exchange-organization-level-objects-have-not-been-created-and-setup-cannot-create-them-because-the-local-computer-is-not-in-the-same-domain-and-site-as-the-sche/
http://www.petenetlive.com/KB/Article/0000793.htm
transferred the schema roles to different server on root domain, still no luck.
can someone please help me.
regards
Srinivasa k
Srinivasa K

Hi Srinivasa,
I guess, you didn't completed the initial setup schemaprep and adprep before starting the installation. You can do it as follows:
1. Open command Prompt as administrator and browse to the root of installation cd and run Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
After finishing this,
2. Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms
3. To prepare all domains within the forest run Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms. If you want to prepare a specific domain run Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTerms
4. Once you complete all of the 3 steps, install the pre-requisities for Exchange 2013
5. Finally, run the setup program
Hope this will help you
Regards from Visit ExchangeOnline |
Visit WindowsAdmin

Microsoft Exchange Server Auth Certificate Error

I have new install the Exchange server 2013. I accidentally assigned the IIS service to the Microsoft Exchange Auth Certificate. now i'm facing problem to connect exchange server from outlook.
The Error shows
"There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site
name. Outlook is unable to connect to the proxy server. (Error Code 10)."
Certificate shows error
"This CA root Certificate is nit trusted because it is not in the Trusted Root Certificate Authorities store"
Please help me...
Thanks

HI Winnie,
if i use root CA from AD CA can solve this issue?
Please see the result:
[PS] C:\Windows\system32>Get-ExchangeCertificate | FL
AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {DBH-EX01, DBH-EX01.deltabrac.com}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=Microsoft Exchange Server Auth Certificate
NotAfter           : 12/19/2018 12:37:13 PM
NotBefore          : 12/19/2013 12:37:13 PM
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 30F29F3C289D448A4244C95D267B9976
Services           : IMAP, POP, SMTP
Status             : Valid
Subject            : CN=Microsoft Exchange Server Auth Certificate
Thumbprint         : 514DDBBDAB0878766B9D305A0D500CBEA334E109
AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=Microsoft Exchange Server Auth Certificate
NotAfter           : 12/18/2018 3:51:00 PM
NotBefore          : 12/18/2013 3:51:00 PM
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 2AAA1A565B385794473CE3AC8D3A85F4
Services           : IIS, SMTP
Status             : Valid
Subject            : CN=Microsoft Exchange Server Auth Certificate
Thumbprint         : 5E6026E8C9CC18BFE3684E58CD2876AC97A2514D
AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {DBH-EX01, DBH-EX01.deltabrac.com}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=DBH-EX01
NotAfter           : 12/11/2018 7:25:05 PM
NotBefore          : 12/11/2013 7:25:05 PM
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 1C611FA9102B64B3462A0100FEF74A12
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=DBH-EX01
Thumbprint         : 2FD1A8D2141DCA036F3DD5BE1191FD1FB6966EE9
AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule,
                     System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {WMSvc-DBH-EX01}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=WMSvc-DBH-EX01
NotAfter           : 12/9/2023 5:03:46 PM
NotBefore          : 12/11/2013 5:03:46 PM
PublicKeySize      : 2048
RootCAType         : Registry
SerialNumber       : 4013857FC4683FA940C6DCC87A83A05F
Services           : None
Status             : Valid
Subject            : CN=WMSvc-DBH-EX01
Thumbprint         : BAE5A99C48FDFDBDBDE1E158833F862BB977DC01

Exchange Server 2010 - Problem configuring my server 2008 so my clients can use Outlook to send/receive e-mails

Hi,
I am new to the servers and domains stuff. Therefore i have setup succesfully a Server 2008 R2 server with AD, DHCP, DNS roles installed. I configured the roles as i wanted and then i installed Exchange Server 2010 so the clients can use Outlook to send
receive mails in and out of the domain.
I can send/receive mails inside the domain (disalfa.com) but i cannot send/receive mails outside the domain. I configured the Exchange properly, i am sure of that. I am 99,9% i did something wrong with the DNS (A records, MX records, etc.).
Also is there something i must do from the control panel of the site i purchased the domain name and the mails?
Can someone guide me so i can manage to work this out?
Server 2008 - 192.168.1.250
Registered Domain - disalfa.com
Thank you in advance

Hi ,
I recommend you refer to the following article to configure your external mail flow:
Configure Internet Mail Flow Directly Through a Hub Transport Server
Prerequisites
Register MX resource records for all accepted domains in a public domain name system (DNS) server. Consult the documentation of your DNS provider for information about how to register MX records for your domain. Detailed procedures about how to complete
this step are outside the scope of this topic.
Configure network gateways to allow SMTP traffic to and from the Hub Transport server. Consult the documentation for your network routers and firewalls for information about how to route SMTP traffic to and from the Hub Transport server. Detailed procedures
about how to complete this step are outside the scope of this topic.
Best regards,
Niko Cheng
TechNet Community Support

Sharing free busy and GAL between exchange organization.

HI, we are looking to share free busy and GAL between 2 exchange organizations. Thus far using the Microsoft federation gateway appears to be the better option for us to achieve this. Although due to both exchange organizations using the same SMTP email
domain we may run into issues trying when both organizations attempt to create the federation trust using the same autodiscover.abcdomain.com
What is the recommended approach to work around this issue?

Change the e-mail domain in one of the organizations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 EAC Service Pack 1 New mailbox cannot see all OUs when selecting Browse with "Exchange Organization Management " permissions

Single forest 2 Domains. When I go to create a new mailbox in the Exchange Admin Centre and "Browse" the Organizational Unit. I can only see a few OU in the Parent Domain and most in the Child Domain. I have tried "expand All" and
cannot see anywhere in the EAC to set a "Recipient Scope". The account I am using has "Exchange Organization Management " rights and is a Domain Admin as well.
The Exchange servers are members of the Root Domain.
In the "Select an Organizational Unit" menu there is a message "There are more results available than are currently displayed". I have tried searching as well and cannot find OUs that I should be able to.
All the servers have had Exchange 2013 Service pack 1 installed.
Any suggestions?
Regards,
John

Changing that setting resulted in the ECP site being inaccessible. So I changed it back
I have copied the user accounts to test with.
Originals:
User1: can see OU's when making a new user through the ECP (access: domain, exchange recipient admin)
User2: cannot. (Enterprise, domain, exchange, schema admin)
Test users:
test user1: copied from user 1, cannot see any OU's when creating a new user.
test user2: copied from user 2, can see all OU's when creating a new user.

Exchange Report - Top 10 internet Domains Sending Emails to exchange organization

Hi guys
I've been getting alot of reports out of my exchange organization lately. mostly using powershell. A report im interested in is Top 10 internet Domains Sending Emails to exchange organization.
Anyone got a script getting that or willing to give me some pointers to write one ?
Thanks in Advance
Farhad

Hi
Thank you for your question.
You can refer to the following link :
http://exchangeserverpro.com/exchange-2010-message-tracking-log-search-powershell/
If you want the detailed script, you can ask the question on Exchange Development forum.
If there are any questions , please let me know.
Best Regard,
Jim

Txt record for exchange organization

Hi,
I am searching on how to get information and how to correctly create txt record in the external DNS to prevent mail spoofing for my accepted domains
currently I have one exchange organization and I have 4 accepted domains which I want to create txt records for them.all I found is related to office 365 not related to hosted Exchange 2013.
I need to et this information to provide it to public dns provider
Mashhour Faraj

Hi,
You can create a TXT record by using DNS Manager on a server running Windows Server 2008 that has the DNS server role installed. Also, you can use the DNSCmd command to create a TXT record.
For more information, here is an article for your reference:
https://technet.microsoft.com/en-us/library/ee423548%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Is it possible that Exchange UM could be configure with two call managers over the same sip?

Hi,
I have Cisco call manager 8.2 integrated with Microsoft Exchange Server 2010 Unified Messaging.
Call manager has primary and secondary server. I created a sip trunk and linked primary CUCM with Exchange. Users can leave and get voice mails.
Problem: In case that primary server is down (WAN is down) the users registered on secondary server but they cannot contact to Exchange Unified Messaging.
I added new UM Dial Plan with the same pilot and associated it to the secondary CUCM server. UM answered but do not recognize the extension number "is not a valid mailbox extension".
Is it possible that Exchange UM could be configure with two call managers over the same sip, the same pilot number, different associated UM servers and get access to the same voice mail boxes?
If not:
Does exist a way to configure Exchange UM that will work if one CUCM server is down?
Thank you,
Peter

Hi,
I have Cisco call manager 8.2 integrated with Microsoft Exchange Server 2010 Unified Messaging.
Call manager has primary and secondary server. I created a sip trunk and linked primary CUCM with Exchange. Users can leave and get voice mails.
Problem: In case that primary server is down (WAN is down) the users registered on secondary server but they cannot contact to Exchange Unified Messaging.
I added new UM Dial Plan with the same pilot and associated it to the secondary CUCM server. UM answered but do not recognize the extension number "is not a valid mailbox extension".
Is it possible that Exchange UM could be configure with two call managers over the same sip, the same pilot number, different associated UM servers and get access to the same voice mail boxes?
If not:
Does exist a way to configure Exchange UM that will work if one CUCM server is down?
Thank you,
Peter

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

First Exchange 2013 server in 2010 Deployment - 2010 edge is routing SOME inbound mail to new server where it fails.

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ). I have one 2010 edge server and one 2010 ht,cas,mailbox server. I have added a 2013 server and started working
on configuring virtual directories. This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.
My issue is the edge server is already passing inbound internet mail to the new 2013 server. I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox
users never receive.
Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?
And why is it delivering to a server with now mailboxes on it yet?
Thank you for any help
dean

Hello Dean,
I understand that the message tracking log indicates the email delivered to Exchange 2013 server. Please check the message tracking log on both Exchange 2013 server and Exchange 2010 server.
How about the result? Have you created new 2013 mailbox and tested if it works?
As for the send connector, actually an intra-org send connector will be involved for internal mail flow within an organization. So there is no need to create another send connector.
In addition, I’d like to share you an article about Edge Subscriptions:
Title:
Understanding Edge Subscriptions
Link:
http://technet.microsoft.com/en-us/library/aa997438(v=exchg.141).aspx
Regards,

X-MS-Exchange-Organization-AuthAs is configured as Internal other than Anonymous from internet mails

Similar Messages

Maybe you are looking for