Search results for query: *

Announced this month... http://windowsitpro.com/blog/why-exchange-2016-will-be-coming-you-soon

I have a vague recollection I looked at this for something like GFi Mail Essentials around Exchange 2000 days. If memory serves (not 100% likely) it was that a spammer doing spoofing of a domain should be blocked based on IP rather than white listed based on domain name.

Agreed - great to get confirmation back from you that all is good.

Haven't got access to my lab at the moment to test but I think block takes precedence over whitelist.

Not sure what sort of tunnel you have but you will need to allow the ewes end points to talk to each other. A federation trust and org relationship would be the most common way to achieve it. Check out http://blogs.technet.com/b/exchange/archive/2011/03/04/3412075.aspx which should help you.

I would expect resetting the index did it as there isn't anything in ru9 about search. You may find something in the app logs about an issue but either way you got it resolved.

Did you do a cross forest move and is there a trust in place?

Office filter pack - http://blogs.technet.com/b/exchange/archive/2011/08/02/exchange-server-and-sp1-for-microsoft-office-filter-pack-2010.aspx Reset-SearchIndex yes, it deletes and recreates. I'd still suggest the updating the database copies afterwards with catalogonly using example 4 in...

I'd say that you need to update the search. Update Exchange to the current service pack and rollup. Update the search filter packs to the current version. Then for each database delete and recreate the search catalog on the active copy of the database then update the passive with a -catalogonly...

check the internalURL or externalURL on the 2013 server for the get-owavirtualdirectory. One of those is likely to be wrong and causing the Proxying. Hence why the IP works. Run through http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx...

yes, that's right. Exchange 2013 mailboxes cannot access legacy public folders.

Sounds like you have a damaged virtual directory. A remove-owavirtualdirectory and a new-owavirtualdirectory might get you up and running. Oh - have you restarted the server??? ;-)

And install SP3 RU4 - SP1 is REALLY old and out of support...

Can they see them all using OWA? If so, check the application event log on the CAS and look for matching 9646 events in which case you're hitting a bottleneck on the CAS.

From each side: telnet IP 25 then do a helo domain.com mail from: x.com rcpt to: realuser@domain.com DATA Subject: Test Data . during which time take a netmon. Also do a pathping. You say you've only upgraded the domain functional level....what devices are between the 2 orgs?

Yup, that should help.

get-sendconnector | fl might show you that you have a connector to there. Or a duff DNS entry on that server. The server has been told to deliver emails for those domains to itself hence the 550.

Not out of the box no. Third party only.

there isn't one. You can only parse the logon stats. If a user is in cached mode to a load balancer, there is no activity so you could class them as not logged on, but Outlook is running.

Look at the get-sendconnector | fl and get-receiveconnector | fl output to see if the transport mechanisms are aligned.