Remove a domain from Exchange 2003, now other domains cannot send to the old domain error 5.1.1

We have a single Exchange 2003 server. We have multiple mail domains on the server, but are slowly moving to a hosted email solution. I moved the first domain, I will call it
domainABC, to our hosted solution. I have removed all exchange mailboxes from the users, and deselected the domain from Recipient Policies. I then ran the policy.
Whenever I send an email to anyone on Domain ABC from any other domain on the Exchange server, I get the 5.1.1 message. I am not sure what to do next - any help would be appreciated...
Brian

Hi Brian,
Could you post the detail information for the NDR message?
When you migrate all the users to the host email server, did you change mx record point to the new server?
You also can use this tool to help you check for the inbound email test (for Domain ABC).
Exchange Remote Connectivity Analyzer
https://www.testexchangeconnectivity.com/
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Similar Messages

Unable to manage Distribution list membership since moving from Exchange 2003 to Exchange 2010

Hi,
We have recently started migrating from Exchange 2003 to Exchange 2010. One of our customers used to be able to manage a security group through the outlook address book. This is a mail enabled security group where the customer is on
the "Managed by" entry and the "Manager can update membership list" is ticked.
Now that the users mailbox has been migrated to Exchange 2010, if they try and modify the membership using outlook by finding the group in the address book they get the error "changes to the distribution list membership cannot be saved. you do not have
sufficient permission to perform this operation on this object".
I have now added a test account to the managed by entry on the security group to test the problem.
I have followed the article
http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx that explains how to use the EMS to give users the right to amend groups that users own. I did not run the script but entered the following commands:
New-ManagementRole -name “MyDistributionGroupsManagement_Test” -parent MyDistributionGroups
Remove-ManagementRoleEntry “MyDistributionGroupsManagement_Test\New-DistributionGroup” -confirm:$false
Remove-ManagementRoleEntry “MyDistributionGroupsManagement_Test\Remove-DistributionGroup” -confirm:$false
New-ManagementRoleAssignment -name “MyDistributionGroupsManagement_Test-Default Role Assignment Pol” -role “MyDistributionGroupsManagement_Test” -policy “Default Role Assignment Policy”
All appears to have worked ok and I have seen no errors while doing this
If I use OWA and then use the ECP, I can now see the "Public groups I own" but no groups are listed.
I have created some new distribution groups in Exchange 2010 (One dist list and one security group) to test and added the test account as an owner of both and a member of both. I still cannot amend the membership using outlook address book and the
ECP still shows no groups under "Public Groups I own"
I have seen a number of articles on how to do this and it looks like I am doing everything right and it has worked for plenty of other people. I just don't know what's going wrong.
I would be very grateful if anyone can help.
Matt

Hi Rajith,
I deleted the outlook profile and recreated it but this did not work.
I have now created a brand new mailbox on Exchange 2010 added this to the "managed by" section of the Exchange 2010 dist lists and I still get the error. I also do not see the groups listed when logging in as that user to OWA ECP and clicking on the
Groups link.
I had a look at the link you sent me and I could see that from the Exchange server when I opened the User roles to get to the ECP, clicked on Roles and Auditing and then User Roles the only policy applied is "Default role assignment". When I select
the details for this, under Distribution groups, "My Distribution Groups" is not ticked but my new one that I created "My DistributionGroupsManagement_Test" is. So this looks ok.
Any other ideas?
Matt

Exchange 2007 setup, transitioning from Exchange 2003

Hello Exchange Experts,
I just setup a Exchange 2007 within our domain, transistioning from Exchange 2003, question: When I added the mailbox role on the setup of Exchange 2007, the mailboxes appeared instantly from our Exchange 2003..the connector I'm assuming automatically connected
during the 07 setup. Is this normal? I was under the assumption to migrate mailboxes from 03 to 07 Exchange, the wizard must be ran. All active mailboxes from 03 appear. I attempted to migrate one mailbox using the wizard, error after the wizard completed,
mailbox exists. Makes sense, just not understanding how the mailboxes flowed/migrated automatically without running the migration steps. Would someone explain? You could say, this migration is very new to me.
Thanks in advance!
James

Ronny, our company had an existing license for 2007. Of courser 2010 or 2013 would have been a better transition, but 2007 is it. The server 2007 has met all the criteria for the transition, spent last moth prepping everything on 2003 and 2007. I'm just
not understanding why the mailboxes appeared upon 2007 immediately after adding the mailbox role. The management console on 07 shows the mailboxes reside on 03 exchange server. I did not go through the process/wizard to move to 07. Perhaps because
during the installation of Exchange 07 created the connector from 2003? Maybe that's my question.
Mail flow is very responsive now, just wondering for the reasons of decommissioning exchange 2003 at a later date. Exchange 2003 is functioning now as a bridgehead, working perfectly now.
Thanks for your input.
James
Thanks Ronnie for your input! Issue resolved

Moving public folders from exchange 2003 to exchange 2010 error while moving replicas

Dear All,
i am in the process of migrating from Microsoft Exchange 2003 to Exchange 2010,
i am done with moving all the mailboxes 300 mailbox almost with a 1.5 TB DB with no issues
when i tried all the processes, procedures, instructions and forums to move the public folder or
to use move all replicas from Exchange 2003 to Exchange 2010 i always get errors , now when i try
to open PF Management console from the exchange 2010 server i get it but it is disconnected
then i can choose to coneect to the new server name EXCHANGE2010 with no issues
when i try to expand the default folder and system folder i get the following error.
OAB is set on the new server as default.
when i try to add replica using power shell i get this error:
WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an inst
of an object.
Object reference not set to an instance of an object.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
following error when trying to expand PF on EXCHANGE 2010
Microsoft Corporation
Microsoft® Windows® Operating System
6.0.6000.16386
Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''.
Microsoft.Exchange.Configuration.MonadDataProvider.CommandExecutionException: Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''. ---> System.NullReferenceException: Object
reference not set to an instance of an object.
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.GetMapiPublicFolderDatabasesIdentities(ADSystemConfigurationSession configurationSession, ADObjectId serverId, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ValidateServerContainsPFDatabase(Server server, ADSystemConfigurationSession scSession, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ResolvePublicFolderServerAndUserLegacyDNs(ADSystemConfigurationSession scSession, ServerIdParameter serverIdParameter, String& serverLegacyDN, String& userLegacyDN, Fqdn& serverFQDN,
TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.GetMapiObjectTask`2.CreateSession()
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalStateReset()
at Microsoft.Exchange.Management.MapiTasks.GetPublicFolder.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Close()
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Dispose(Boolean disposing)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.Fill(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.OnDoRefreshWork(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.RefreshableComponent.worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UmDiagnostics.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Collaboration, Version=3.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Media, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Microsoft.Exchange.Data.Directory.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
i will be thankful for any assistant.
PF DB is arounf 90 GB with alot of public folders and sub-folders. around 60 mail PF and too many subfolders.

First and the most important thing you need to do is, upgrade exchange 2010 to SP2 and RU5.
Exchange 2010 RTM support is long gone.
http://www.microsoft.com/en-us/download/details.aspx?id=36768
http://www.microsoft.com/en-us/download/details.aspx?id=41480
Your exchange 2010 is still in stogeage ;)
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SPAM rules on Inbox after migration from Exchange 2003 - GFI Mail Essentials

Hello,
Few times ago, we had an Exchange 2003 server with mailboxes which were configured with "rulemgmt.exe" tool (from Microsoft ?) to manage users mailboxes and SPAM redirection in these mailboxes.
GFI MailEssentials (antispam) was installed on a mail relay and once a SPAM was detected, it was redirected in Inbox/SPAM folder on user mailbox thanks to the rule defined by "rulemgmt.exe".
Recently, we did a migration from Exchange 2003 to 2010. Unfortunately, "rulemgmt.exe" doesn't work anymore on Exchange 2010 and it's replaced by a "Transport Rule" which works fine but only to redirect SPAMs in Junk e-mail folder. However,
if I don't set up this transport rule, SPAM redirection still works from mailboxes which were created on Exchange 2003 and e-mails go to Inbox/SPAM as before... For new mailboxes on Exchange 2010, it doesn't work which is normal.
My question is: for old mailboxes from Exchange 2003, where are the SPAM redirection (Inbox/SPAM) information stored? I don't understand how SPAM can be redirected if the information is not stored in Exchange...
The aim is to use Junk E-mail folder with the Transport Rule at the end everywhere and to clean old rules used for Inbox/SPAM.
I contact GFI support but they couldn't help me.
Any idea?
Regards,
DeltaSM

Those old mailboxes probably have old rules still set. You can use the Outlook.exe /cleanrules switch to purge those old rules. This would require that you create an outlook profile for each of those impacted mailboxes.
You can also look at using MFCMapi -
http://support.microsoft.com/kb/2860406/en-us
When that is done, you might want to perform a Clean-MailboxDatabase and then look at the mailbox rules (get-inboxrule). If that does not work for you, could be something else within the mailbox and as such, I would recommend working with MS to get
more info.
DaDougInc

Need detail information, steps would be nicer, to upgrade from Exchange 2003 to Exchange 2010 to setup in test system first then try on production, since not much room for downtime, thanks bekir

Need detail information, steps would be nicer, to upgrade from Exchange 2003 to Exchange 2010 to setup in test system first then try on production, since not much room for downtime, thanks bekir

Hi,
Overview of the upgrade progress from Exchange 2003 to Exchange 2010 including the following steps:
Installing Exchange 2010 within your organization on new hardware.
Configuring Exchange 2010 Client Access.
Creating a set of legacy host names and associating those host names with your Exchange 2003 infrastructure.
Obtaining a digital certificate with the names you'll be using during the coexistence period and installing it on your Exchange 2010 Client Access server.
Associating the host name you currently use for your Exchange 2003 infrastructure with your newly installed Exchange 2010 infrastructure.
Moving mailboxes from Exchange 2003 to Exchange 2010.
Decommissioning your Exchange 2003 infrastructure.
For more details, please refer to this following document.
http://technet.microsoft.com/en-us/library/ff805040(v=exchg.141).aspx
Best Regards.

Shared mailbox access from exchange 2003 to 2010 users

We'd successfully migrated from exchange 2003 to 2010. still some of the users are yet to be migrate.
The issue is only in MAC (Apple) Migrated users was unable to access the shared folder residing in 2003 environment.
but the migrated 2010 users are able to access the shared folders in the windows environment.
Any one can assist or suggest this issue.
Awaiting for ur reply.
Regards
kart26

Hi Kart26,
Please install certificate in your MAC App Client.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Migration from Exchange 2003

Hi,
We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
Can Office 2011 connect to Mac mail services? If so, what protocols?
Many thanks,
Ciaran.

We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
What features of Exchange are you using? Push notifications? Calendaring. Sharepoint? Figure out what you want and what you need (and which are two separate lists) and then map that over to what Mac OS X Server, or to what a Mac box with the Kerio Connect package loaded, might provide you.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
That's rather open-ended. It's possible, but there's no single definition of small business mail requirements. Some small businesses can and have, and some might find themselves missing critical features.
Can Office 2011 connect to Mac mail services? If so, what protocols?
iWork does well enough to read and write Office files locally, so I don't have experience with Microsoft Office. The Windows mail clients can certainly access Unix mail servers. As for what connectivity is present within Office, I'm way too rusty with Windows to comment. What used to be the Outlook Express client worked just fine with Unix mail servers. The full-on Office Outlook client was pretty flaky with stuff other than Exchange, but that was some years ago.
Biggest issues with SBS migrations tend to be with shared Address Book, with shared Calendars and with Sharepoint services; if you're heavy users of those features, you might find the Mac OS X Server implementations lacking. Kerio can potentially help here.
Look around the forums for some other folks. This particular SBS migration has been fairly common fodder for discussions.

Calendar Free/Busy permissions being ignored for users migrated from Exchange 2003, fine for new users created on Exchange 2010

I have uncovered a situation where it seems the free/busy permissions are being ignored for users that were migrated from Exchange 2003 to Exchange 2010.
I have the default permissions set to only show Free/Busy Time, not Details. However if I look at the calendar for a users who was migrated from the old Exchange 2003 server, I can see details. If I look
at a newer user who was added directly to the Exchange 2010 server, I (correctly) only see the times and "Free" or "Busy", not the specific details.
I verified the permissions on the migrated mailboxes many different ways (Exfolders, cmdlets, etc) and all signs point to only allow showing Free/Busy Times, but alas, I can still see the Details as well.
My users are using Outlook 2010.

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2003 users are unable to send attachments larger then 8 MB to Exchange 2010 users on the same LAN

I am migrating from Exchange 2003 to Exchange 2010.
Users who are still on Exchange 2003 cannot send attachments any larger than around 8MB to Exchange 2010 users on the same LAN.
Users on Exchange 2010 can send large attachments to fellow Exchange 2010 users without issue.
I do not have any quota restrictions on Exchange 2010.
Had a look at the Exchange 2003 Connector but could not see any reference to attachement restrictions.
Has anyone come across this?

Here is a note of the NDR:-
Your message did not reach some or all of the intended recipients.
Subject:
The following recipient(s) cannot be reached:
Tracey xxxxxx on 01/12/2014 13:27
This message is larger than the current system limit or the recipient's mailbox is full.
Create a shorter message body or remove attachments and try sending it again.
<mail.xxxxxxxxx.com #5.2.3 smtp;450 5.2.3 Msg Size greater than allowed by Remote Host>

I am trying to email pictures from my ipad to my email address on my computer and I have been going along nice but now I get a message that says "cannot send mail the message was rejected by the server" can't see to figure out why it stopped sending now.

I have been emailing pictures from my ipad to my computer and have been going along nicely and now when I went to send 5 pictures to my computer from my ipad I am getting a message that says " cannot send mail The message was rejected by the server" cannot understand why this is happening and have not been able to fix. Now when I try to send pictues even to another email address I am getting the same message.
Help.

Email may not be the best way to move pictures.
There are lots of ways of moving files.
A simple and popular way to copy files and share files among your devices.
https://www.dropbox.com/
"Box lets you store all of your content online, so you can access, manage and share it from anywhere. Integrate Box with Google Apps and Salesforce and access Box on mobile devices" Rated the most secure cloud storage by SkyHigh Networks.
https://www.box.com/
Using iTunes to transfer files:
http://support.apple.com/kb/HT4094?viewlocale=en_US&locale=en_US
Files Connect -- "Cloud Storage services like Dropbox, MobileMe iDisk, Google Docs/Picasa, Facebook photos, FTP, SFTP, WebDAV ... AFS (Apple File Shares) SMB (Windows shares) protocols"
https://itunes.apple.com/us/app/files-connect/id404324302?mt=8
Windows File server
http://itunes.apple.com/us/app/filebrowser-access-files-on/id364738545?mt=8
"The kiteworks mobile file sharing solution provides secure creation, viewing, and sharing of enterprise content on smartphones and tablets while providing IT and security teams the administrative controls to manage user privileges and access rights necessary to ensure enterprise security and compliance." " Includes choice of private cloud on-premise."
http://www.accellion.com/solutions/mobile-enablement/mobile-file-sharing
"Dukto is a simple application that allows you to share files between devices connected to the same (wireless) LAN network."
http://www.tidal.it/?page_id=309&lang=en
http://www.msec.it/blog/?page_id=11

When e mail a photo from my mac in i photo and receiving on the i pad the photo appears the same as the other ones i send but the jpg file numbers are the same

when using e mail from my i photos on the mac and attach a photo and receiving on the i pad the photo appears the same as the other ones i send but the jpg file numbers are the same

I have one album named "iPad". I don't recall how it got there, where it is there by default or if I created it. Nothing in this album shows a trash can in either full or thumbnail view - I can only edit or share or add to.
In full view mode, when I click on "edit" the upper left shows "cancel". The other greyed out options next to "cancel" are "undo" and "revert to original". The bottom shows the usual photo editing tools, but no "edit". Most of the other pictures show the trash can, which is located on the bottom right corner in camera roll in full view mode. In thumbnail mode when I click "select" on the upper right corner and choose a photo the trash can appears on the upper left corner". This all seems normal. However, the "iPad" album behaves different.

I bought a iPhone and I was able to log into my iCloud with no problem and when I tried to update it it kicked me out and now it's asking me for the old apple user please help what can I do...?

I bought a iPhone and I was able to log into my iCloud with no problem and when I tried to update it it kicked me out and now it's asking me for the old apple user please help what can I do...?

Contact the original owner, and ask them to remove the device from their icloud.
http://support.apple.com/kb/PH13695
HTH

Since upgrade to iOS 7 Email error on over 100KB emails "Cannot Send Mail The message was rejected by the server because it is too large." Connecting to Exchange via Activesync

Hi,
Following the upgrade to iOS 7.0.3 on all our iPhone and iPad devices, it has been identified that when sending emails around 100KB in size and over an error message appears on the device stating “Cannot Send Mail The message was rejected by the server because it is too large.” See error message below. The send/receive limit is over 10MB so this is not the issue.
We are in an Exchange Environment using Microsoft Activesync. This issue is not evident in iOS 6. This has been tested on an iPhone 3GS running version iOS 6.1.3. We have been unable to repeat the issues seen on iOS 7 on the older OS. It is not possible to roll back to the older operating system as Apple are no longer signing the software.
We use Microsoft Active Sync to connect to our Exchange servers through a TMG. The issue is very inconsistent, some identical emails go through, some fail. This is not an issue with the send/receive limit as this is over 10MB. The error message when it fails on the TMG is Status: 413 Request Entity Too Large, which we believe is from IIS on the CAS server.
Does anyone have any suggest course of actions to take?
Many Thanks

This resolution have to attend at the server not with the ios device. My employer's mail administrator reject me to correct it from the server. As his concern is, if ither ios devices works why don't mine? So I am helpless than changing my iphone. It works fine for early versions of ios and with androids. And also one of my friends iphone4 with ios 7 (similar as mine) works too. So I guess it's something wrong with my iPhones settings. But basic question I cannot understand is it works in my phone before this ios7 upgrading. And currently working with my yahoo account too. Favourable reply expected.

Yahoo is my homepage, when I downloaded Firefox 4 my email was on the right in place of page options and I liked it better, but now it has gone back to the old way on the left, why is this

Yahoo is my homepage, I have been using Firefox for years but when I downloaded Firefox 4 my yahoo email was on the right in place of page options and I liked it better, it was there for a while but now it has gone back to the old way on the left, why is this

Firefox 4 requires at least OS X 10.5 and an Intel Mac. There is a third party version of Firefox 4 that runs on OS X 10.4/10.5 and PPC Macs, for details see http://www.floodgap.com/software/tenfourfox
If you prefer, you can get the latest version of Firefox 3.6 from http://www.mozilla.com/en-US/firefox/all-older.html

Remove a domain from Exchange 2003, now other domains cannot send to the old domain error 5.1.1

Similar Messages

Maybe you are looking for