Exchange 2013 user cannot mail 2010 user

Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.

Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin

Similar Messages

Mailbox enabled user to mail enabled user

As part of a migration I have a requirement to change mailbox enable users to mail enable users on exchange 2003. This would be to be able to drop the mailbox but keep all the mail related attributes including the target address. This will allow us to start
decommissioning servers and storage as the migration proceeds.
Stephane
Stephane Favre

Hi,
Please refer to the following article:
Converting a Mailbox to a MailUser (and preserving your custom attributes)
What do you want the mail-user’s external email address to be?
The script takes the user’s mailbox alias and then appends @domain.com. You may wish to modify this with whatever their new external address has become.
hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Is exchange 2013 support thunderbird mail

Is exchange 2013 support thunderbird mail?
Akhilraj

Yes. add imap account for email.
Add the following addon (or the latest version of the same add-on) for calendar
http://www.1st-setup.nl/extensions/exchangecalendar-3.2.0-Beta77.xpi

Exchange 2013 not delivering mails to Exchange 2010

I am upgrading exchange 2010 to exchange 2013 and currently in coexistence. I cutover the mx to deliver mail to 2013 cas VIP last night and no mail was being received by the 2010 mailboxes, it was all being queued on the 2013 mailbox servers (mailbox
and cas servers are separate in this deployment.) There are only a few 2013 mailboxes as I have not yet started migrating them. These 2013 internal mailboxes can not send to exchange 2010 either, but 2010 can send to 2013. 2013 to 2013 mail works
fine. I have read somewhere about an issue with a receive connector having the same ip range that includes the mailbox servers, but I'm not clear on really which mailbox servers it is alluding to.
All the exchange 2010 servers are all on the 10.1.1.* network. Exchange 2013 CAS servers are all on the 10.1.1.* network and the 3 exchange mailbox servers are on 10.1.1.*, 10.1.2.* and 10.30.5.*. Only 1 AD site. On one of the 2010 receive
connectors there is a scope of 10.1.1.0/24 I'm wondering if this is the culprit and by removing it should fix the problem. Any other ideas would be appreciated.

Exchange 2013 users are unable to send emails to exchange 2010 users then check your connectors on Exchange 2013 Mailbox server. and yes if you have overlapping of scopes in different connectors then this can happen.
Kindly mark this as answer if found helpful. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

2013 CAS working for 2010 users, certificate error on 2013 users

Yesterday we decided to pull the trigger on migrating to exchange 2013 from 2010. We changed the autodiscover URI's to mail.domain.com and we also changed the DNS records to as follows:
mail.domain.com -> 2013 cas
mailhub1.domain.com -> 2010 cas
mailhub2.domain.com -> 2013 cas
Ive pushed every single URL I can find through mail.domain.com. We had a few odd issues but were able to work through them. Now we are about 10 hours into troubleshooting without making any headway. Here is where we currently stand:
Exchange 2010 User - Works on everything - Web, Mac Mail, Outlook (inside and outside), mobile clients
Migrated and New Exchange 2013 User - Works on Web, Mac Mail, Mobile. Does not work on outlook inside or out.
For outlook we receive the following error:
Microsoft Outlook
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 mail.domain.com.
Outlook is unable to connect to the proxy server. (Error Code 0)
OK
---------------------------The certificate is perfectly fine from what I can tell. The main domain on it is "mail.domain.com" with "autodiscover.", "mailhub1.", "mailhub2.", and "domain.com" in the Subject Alternate Name.What on earth could I be missing here? It works on exchange 2010 but not on 2013 which is the exact opposite of what I was expecting.

Oooh, Im getting an error now in testconnectivity that wasnt there before so one of the approx. 6000 changes I made must have triggered it!
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
So I looked at the regirestry of both the old mailhub1 and the new mailhub2. The new one only had 2 entries where as the old one had tons. I copied it over, added mailhub2:6001-6004;mailhub2.domain.com:6001-6004 and did an iisreset and restarted the services.
The port still isnt open. Do I have to run a command or reboot? I would rather not have to reboot but I understand if I do. Also, am I doing this right?
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl06_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details

Exchange 2013 OWA IM to federated users

Hi I configured Exchange 2013 OWA IM for Lync server and everything is working fine except that I can't IM federated Lync users when the conversation is initiated from OWA. When I start an IM conversation from the federated user to my OWA, everything is
working fine. Also the replies arrive then! So it must be something with initiating the session. I don't have issues with federated users form normal Lync desktop clients or mobile clients.
In the lync logs I notice the following when starting the conversation from OWA:
1027;reason="Cannot route this type of SIP request to or from federated partners";
I also notice there's a KB2977259 (http://support.microsoft.com/kb/2977259) that discusses similar things but I'm not working with contacts like that and I guess they don't mean that you have to do this for every federated contact a Lync user has.
Does somebody else also experience this issue?
Update: following this KB I tried to add a new outlook contact in owa and add my sip address as "sip:[email protected]". When doing this it actually work to IM this federated user. But this is actually a workaround you can't expect your users
to implement. I can't believe nobody else has issues with this.

Hi DS_Kevin,
Please post a little more log information. It seems that IM from OWA can’t locate the federated user’s SIP address without the sip prefix.
Best Regards,
Lisa Zheng
Lisa Zheng
TechNet Community Support

Exchange 2013 - moving an email from user inbox to Shared Mailbox removes images

Good afternoon,
Employees that are setup with Shared Mailboxes are experiencing a weird issue today. They embed an image into an email and send it to a co-worker. The co-worker sends it back and when they drag and drop it from their user mailbox into the Shared
Mailbox, the image is gone. The Outlook client settings are correct and the format of the emails are HTML. Trying to change the format does not resolve the issue.
One comment I did want to make is that we are currently transitioning from Exchange 2007 and 2010 to Exchange 2013. We moved all of our Shared Mailboxes over to 2013 and we have a majority of users moved over already. Could this be an issue with
using a mixed environment? Thanks!

I confirmed that both the employees and Shared Mailbox are both on Exchange 2013.

Can't install Exchange 2013 after previous uninstall (insufficient user privileges with the same user)

I have installed Exchange 2013 on Windows Server 2012, which ist a member of a Windows Server 2012 R2 Domain. All prerequisites and AD modifications were successfully completed and I could install Exchange 2013. Unfortunately I made a mistake with
the target directory and had to uninstal Exchange 2013. If I start the Setup again, it fails in prerequisite check - the current user should not be a member of Enterprise and Schema admin Group, but it's the same user, which comleted the previous Installation
of Exchange 2013! Do you have any idea how to solve this Problem - I'm running out of ideas.

Inhave tried to run setup /PrepareSchema again and get the following error in exchange setup log:
[03.07.2014 19:25:53.0305] [0] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
[03.07.2014 19:25:53.0337] [0] Validating options for the 0 requested roles
[03.07.2014 19:25:53.0383] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
[03.07.2014 19:25:53.0399] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
After removing all Exchange Parts by ADUC (advanced View) and ADSI Edit (Services) I'm able to install Exchnge 2013 again - the uninstall procedure seems not to work in a clean manner.

In Exchange 2013 i cannot open mails with attachments greater than 19.6 MB in EWS or OWA

Hello,
i have in Exchange 2013 CU3 on Windows 2012 the following problem :
When backup mails using EWS i get the message " EWS Error Code : ErrorMessageSizeExceeded." in mails with attachments greater than 20.137 KB ( 19.6 MB).
Then I checked all the settings of the EWS , but the defaults are already significantly higher than these 19.6 MB (Base64 approximately 26.5 MB)
web.config ( maxAllowedContentLength = " 85000000 ").
Settings of the MaxSendSize and ReceiveSize are 300MB .
All requestfiltering settings in IIS are set to 85MB.
When i access via EMS or OWA , file attachments over 19.6 MB can not be opened .
However, the preview shows in OWA the correct mail including attachment and it can be saved from the preview up to the set maximum size.
By double clicking on an email in OWA bigger than 19.6 MB i get the following error message:
"Error : Your request can not be completed right now Please try again later . . "
Send and receive mail can also be up to maxsize .
When accessing via Outlook , this problem does not occur.
i hope anyone here can help me
Thanks in advance

Hi,
To change the maximum message size for Outlook Web App clients, you need to change the value of
maxAllowedContentLength, maxRequestLength and both instances of
maxReceivedMessageSize by editing %ExchangeInstallPath%ClientAccess\Owa\web.config in notepad.
To change the maximum message size for Exchange Web Services clients, you need to change the value of
maxAllowedContentLength and all instances of maxReceivedMessageSize="67108864" in %ExchangeInstallPath%ClientAccess\exchweb\ews\web.config.
When you are finished, save and close the Web.config file. Also need to restart IIS by running the following command:
IISReset /noforce
For more information about Configure Client-Specific Message Size Limits on Client Access Servers, please refer to:
http://technet.microsoft.com/en-us/library/hh529949(v=exchg.150).aspx
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 in coexistence with 2010, Outlook keep looking for Exchange 2010 server slow connection

All,
not sure if this topic has already answered, but can't find anything around.
Here's the scenario. Migrating from a single Exchange 2010 to a cluster of 2 + 1 Exchange 2013. Two in a site, One in the other site (DC).
I have migrated successfully a firsat batch of users. Mail flow works perfectly. The only thing is that often the migrated users are experiencing a long time (about 30 minutes) to get their Outlook syncronized. Both OL 2010 and 2013 doesn't make any difference.
They're using OL Anywhere, and I've already tried to rebuild the profile.
From a check on the OL connection status, looks like they're still looking for something on EX2010, but no idea what could be. If I disable the cache mode it works smooth and quick.
My best guess is that is something in cache they're trying to keep updated... but still this doesn't explain the huge delay.
Any help would be highly appreciated!
Thanks!

Hi Alessandro,
What happens in OWA? I guess it should be good.
Did you have public folders with Exchange 2010? Were they moved over to Exch 2013? Technically you should move the PF to the latest version from the legacy version before moving over the users?
- Moved the PF to OL2013. same behaviour
May be the outlook clients are looking for th OAB? Did you move the OAB to Exchange 2013?
- Did this too.
Try running outlook on safe mode and see what happens? may be one of the outlook add-in's are looking for something on Exchange 2010?
- Will try that....
Can you do a Test Email Auto Configuration in outlook (Hold CNTRL key and right click on outlook icon on status bar) and see if the exchange url's are pointed to Exch 2013?
- Will try that....
Is this happening to all migrated users or specific? Are they BlackBerry users?
- All users and there are no BB users
Do you have any archived emails on those migrated users? May be outlook is looking for some archived stuff on the Exch 2010 side?
- I instructed Exchange to migrate also the archiving database, however There are no archived mailbox on 2010
Could this be because of any calendar entries? May be migrated user mailboxes are having issues with working with non-migrated mailbox calendars?
- This maybe a possibility. I have only 10 users actively using Exchange, while all others have the mailboxes only because they've Lync. I've completed all migrations today, so there shouldn't be anything left on 2010
Let me know how it went - all the best!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. Regards, Siva

Exchange 2013 OWA: Cannot set auto reply in shared mailbox

We use Exchange 2013 and Outlook 2010. We have 3 users tha connect to a shared mailbox. We would like to have an auto-reply on this mailbox but cannot set it with the OWA. We get the following error:
Client Information
User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; InfoPath.3)
CPU Class: x86
Platform: Win32
System Language: nl-NL
User Language: nl-NL
CookieEnabled: true
Exception Details
Date: Fri Jul 11 11:31:40 UTC+0200 2014
Message: Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
Url:
https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
Line: 5
Call Stack
Dump Event
errorMessage = Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
errorUrl =
https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
errorLine = 5
errorCharacter = 57312
errorCode = 0
actionURL =
altKey = false
altLeft = false
behaviorCookie = 0
behaviorPart = 0
bookmarks = null
boundElements = [object HTMLCollection]
button = 0
buttonID = 0
cancelBubble = false
clientX = 1187
clientY = 72
contentOverflow = false
ctrlKey = false
ctrlLeft = false
data =
dataFld =
dataTransfer = null
fromElement = null
keyCode = 0
nextPage =
offsetX = 0
offsetY = 0
origin =
propertyName =
qualifier =
reason = 0
recordset = null
repeat = false
returnValue = true
screenX = 2373
screenY = 343
shiftKey = false
shiftLeft = false
source = null
srcElement = null
srcFilter = null
srcUrn =
toElement = null
type = error
url =
wheelDelta = 0
x = 0
y = 0
getAttribute =
function getAttribute() {
    [native code]
removeAttribute =
function removeAttribute() {
    [native code]
setAttribute =
function setAttribute() {
    [native code]
Detailed Call Stack

Hi,
Error information is quite important. In order to solve your issue effectively, please take your time to describe the error in English for my research.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 ECP redirects to 2010 OWA still

I have a new Exchange 2013 SP1 server on a 2012 R2 OS where I've installed both Mailbox and Client Access roles in an existing Exchange 2010 environment. Initially ran into some DNS issues that caused errors installing the Client Access server, but
I fixed those, removed Exchange 2013 and reinstalled with no errors. In every scenario so far, trying to access the ECP redirects you to the 2010 OWA. I have been scouring threads for hours and tried everything I've seen, but to no avail. I
have tried:
1) Using the https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15 URL, which still
redirects to the 2010 OWA
2) Creating a new user account with all of the same rights as the domain admin but has no mailbox, which redirects to the 2010 OWA and throws an error that there is no mailbox.
3) Setting the domain in IIS authentication settings for the ECP on both the 2013 and 2010 server.
Does anyone have any ideas here on what to try next?

Try creating a mailbox for the administrative account on the Exchange 2013 server or moving the existing mailbox.
I've seen issues like you're experiencing in various forms before myself, though not exactly as you've reported.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

How do i connect manually to Exchange 2013 from Outlook 2007/2010 in another forest?

Hello All,
I have a source organization: Windows 2003 domain + Exchange 2010 SP3 + smtp domain acme.com
Target organization: Winows 2012 R2 domain + Exchange 2013 CU3 + smtp domain acme.com
We are migrating to target organization.
I want to connect Outlook 2007/2010 to their target mailbox (Exchange 2013) from a machine which is joined to Source DOmain.
I couldn't use autodiscover, because as the machine is joined to source domain, autodiscover it's mapping to Exchange 2010.
It only works when I machine is joined to target domain.
Any idea how to connect manually to eXCHANGE 2013 mailbox from a machine which is joined to source domain?
Regards
José Osorio

Hi,
Firstly, I’d like to explain, Autodiscover service can be used cross forest:
1. the two forests must be trusted.
2. configure a mail contact in the original forest.
For more information, please refer to the partition named how to configure the Autodiscover service for cross-forest moves in the following article:
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx#BKMK_ConfigureForCrossForestMoves
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 - outlook cannot connect server

Hi,
I have installed exchange server 2013 to testing it in my home lab. DC - domain.local and exchange - sub.domain.com. Internet connection is with dynamic IP from ISP - router (PPPoE). My ISP provide DDNS and I got sub.domain.com for dynamic
IP. Also ISP is blocking port 25. I've asked ISP to unblock port 25 and i don't know if they unblock it. For exchange server i use smart host for relay.
Problem: If i use port forwarding (25) mail flow is normal intern - extern. This was tested with OWA, but outlook cannot connect to exchange server: logging on mail server failed.
If i don't use port forwarding (25) outlook connect to exchange server, but i cannot receive email from external.
Please give me a hand on this.
Thank you.

Hi Radu,
how do you connect Outlook with Exchange? Usually you're using MAPI/RPC/HTTPS so there is no dependency with SMTP. How did you configure your Outlook? How did you configure your CAS Settings?
Please verify your CAS is configured correctly and you are using Outlook AnyWhere, see
http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx
Regards,
Martin

Exchange 2013, scan-to-Mail, Attachments broken down to mime tipes

Good day
I recently installed Exchange 2013 to our domain.
The problem i'm facing is that any scan to email document gets delivered as the following :
This is a multi-part message in MIME format.
--DC_BOUND_PRE_<1361347488.00267327e1cb>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
--DC_BOUND_PRE_<1361347488.00267327e1cb>
Content-Type: application/pdf; name="20130220090448407.pdf"
Content-Transfer-Encoding: base64
Content-Dis;
filename="20130220090448407.pdf"
JVBERi0xLjQKJeLjz9MKNCAwIG9iago8PC9UeXBlL1hPYmplY3QKL1N1YnR5cGUvSW1hZ2UK
L1dpZHRoIDE2NTYKL0hlaWdodCAyMzM5Ci9CaXRzUGVyQ29tcG9uZW50IDEKL0NvbG9yU3Bh
Y2UvRGV2aWNlR3JheQovRGVjb2RlWzEgMF0KL0xlbmd0aCA0ODQxNzMKPj4Kc3RyZWFtCgAA
AAAAAAAAAAAAAEAl+3vv///+gAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF9
gAAAbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFZK26AAAAAAAAAAAAAAA
And it goes on for this for a couple hundred more lines.
I have tested the following
Scanning to any email address outside my domain, work 100%
Any scanner sending mail-to-pdf from outside my organization it get delivered as above
I have changed smtp servers to our ISP and that also delivered as abve
I change the sending address of scan-to-mail machine to gmail account, also delivered as above, but to my non domain email address it works perfectly
Please help

one of our clients had the same problem before, he have Richo printer with scanner witch is scanning to pdf file attached to email , this printer is working fine by using Exchange 2010 but has that problem after the migration to exchange 2013, this
problem is totally fixed after installing Exchange SP1 (CU4). I found others say this problem is fixed by just installing CU1.
for more information about content conversion
http://technet.microsoft.com/en-us/library/bb232174.aspx#External

Exchange 2013 user cannot mail 2010 user

Similar Messages

Maybe you are looking for