Mailbox Transfer

Hello,
I want to switch back to apple mail. I am currently using Microsoft outlook 2011 for mac. I would like to transfer all my mailboxes including the attachments present in them, my address book to vcard and also the contacts to ical. I have tried to import through the import option in apple mail but it doesn't show outlook 2011.
Your help will be greatly appreciated.
Thanks for help.

How to Import mailbox from Outlook 2011 into Mac Mail Lion
Export From Outlook 2011 Mac & Import .eml Files Into Apple Mail

Similar Messages

Any experience of BT mailbox transfer?

Hi, does anyone have experience of a BT mailbox transfer? We want to cancel a BT total broadband account in one property and "move" the 2 associated email addresses (and the 2 mailboxes on the BT server: each containing an inbox, various sub-folders and sent box) to align with an existing BT infinity broadband account in another property. Today 2 helpful people from an obscure corner of BT (the 'dial up technical help' people) said they would be able to do the mailbox transfer. But yesterday I spent nearly 4 hours on the phone with BT - received lots of confusing and conflicting advice from many different departments but no clear and good answer. Today I was finally recommended to speak to 'technical dial up' department who gave me the good news. Just want to be double sure that today's info isn't too good to be true! Would also be grateful for reassurance from anyone who has been through a 'mailbox transfer - did it work? Thanks

If things do not go to plan, then
If you would like to contact one of the UK based BT Care Team who moderate this forum, they should be able to help you.
They can be contacted using this link BT Care Team
They normally respond by phone or e-mail, within three working days, however you should get an immediate confirmation, with a tracking number.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Mailbox transfer from Apple mail to Windows Outlook 2010

There were thousands of emails in Apple mail email client. I sorted out and maild mailboxes for different types of emails. I separated work-related eails and other stuff related emails and made mailboxes for each. Now I want to move the work-related emails
to my windows laptop in Outlook 2010 email client.
I did try to sync the emails via Imap but the synchronization fails every time I try to sync the emails. I have double checked everything many times before synching but it always fails. Now I am sick of doing it as there are 10k plus mails and the sync is always
failing.
Is there any other way to transfer the mailbox from apple mail to outlook 2010. It would be very helpful of anyone can guide me to transfer only the work mailbox folder as syncing via Imap starts downloading all the emails including the others.
I just need to transfer the work folder.
Helpful solutions will be really appreciated.

Hi,
The easiest way to transfer data from Outlook for Mac to a Windows-based Outlook client is to upload to an exchange server. To do this, please refer:
http://support.microsoft.com/kb/2649169/en-us
However, if that option is not available use one of the methods listed in the link below:
http://www.office.mvps.org/cross_platform/mac_win.html
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee
the accuracy of this information.
Best Regards,
Steve Fan
TechNet Community Support

HT4889 Mailbox Transfer from OSX 10.2.8

Hi
Can anyone tell me how to transfer old mailboxes in Apple Mail 1.2.5 v533 created on an old iMac with OSX 10.2.8 to my new iMac? I do not need these to be active, merely to preserve old messages, so conversion to a documant format would work for me. I transferred one archive mailbox folder to my new iMac (OSX 10.8.5) but cannot open it to save its contents.
Thank you
cblauth

The easiest way is to make an IMAP account and copy to server mailboxes on the IMAP account.
Then that's portable with all e-mail programs.

IPhone mailbox transfer

Hi all,
How do I transfer the contents of the Sent Mail folder and Inbox from my 3G iPhone to my new 4s? I have some mesages there that exist nowhere else and I'd like to preserve them.
Ultimately I'd like just to copy the entire folder(s) over to the new phone. Having a really hard time getting any info on how to do this.
Any help is appreciated.
Thanks!

On your mac, there are different mailboxes listed in the left panel. One, "On my mac" are folders that are on your mac only, they are not part of the email account folders. Any folders "on my mac" will not sync with other devices.
Also, many email accounts are POP account (not Exchange or IMAP). Folders that you have on your mac in a POP account are local to your mac, not part of the account. So again, these folders cannot sync with other devices.

Unity/Mailbox Transfer

What I'd like to do is once an incoming reaches the voice mail prompt have the option for the caller to press a digit and be transfer outbound to a cell or home number. I'm not sure of the terminology that would be use for the title for this.

Hi Lyle,
This is call the "Alternate Contact Number"
Enabling Callers to Transfer From Subscriber Greetings to an Alternate Contact Number
As a convenience to callers, you can set up Cisco Unity so that callers can transfer to an alternate contact number by pressing a key during the greetings for a particular subscriber or a group of subscribers. An alternate contact number can be the extension for an operator or another subscriber (such as a supervisor or coworker), or any other number where the subscriber or another person can be reached.
You can use the Cisco Unity Administrator or the Bulk Edit utility to specify the key that callers press to transfer and the number that they transfer to. You can specify the same key and alternate contact number for multiple subscribers, or you can specify a different key and/or alternate contact number for each subscriber. Subscribers can specify the alternate contact number by using the Cisco Unity conversation or the Cisco Unity Assistant. (Note that the option to specify an alternate contact number appears in the Cisco Unity Assistant regardless of whether you have specified a key that callers can press to transfer from the subscriber greeting.) The alternate contact number is limited to the numbers allowed by the restriction table for transfers that is associated with the subscriber who specifies it.
When you enable the feature, you may want to specify the key(s) that can be used to make the transfer and leave the alternate contact number unspecified, so that subscribers can specify the number themselves. Until an alternate contact number is specified, Cisco Unity ignores the key set to transfer the call if callers happen to press it during a subscriber greeting. Because neither the Cisco Unity conversation nor the Cisco Unity Assistant indicate the key that you specified to allow callers to make the transfer, let subscribers know the key so that they can include the information in their greetings. When transferring a caller to an alternate contact number, by default Cisco Unity releases the call to the phone system. Alternatively, you can configure Cisco Unity to use the subscriber's active transfer rule settings, including call holding and call screening options.
To Enable Callers to Transfer From Subscriber Greetings to an Alternate Contact Number
Step 1 In the Cisco Unity Administrator, go to the applicable page:
â¢To modify the template that you will use to create subscriber accounts, go to any Subscribers > Subscriber Template page, and find the template that you want to modify. Then browse to the Caller Input page.
â¢To modify an existing subscriber account, go to any Subscribers > Subscribers page and find the applicable subscriber. Then browse to the Caller Input page.
Step 2 Select a key from the Caller Input Map or from the keypad.
Step 3 In the action section, click Send Caller To and then click Alternate Contact Number.
Step 4 In the Number to Dial field, enter digits 0 through 9 to specify an alternate contact number up to 30 digits in length. You can also enter:
â¢, (comma) to insert a one-second pause.
â¢# and * to correspond to the # and * keys on the phone.
Do not use spaces, dashes, or parentheses between digits. Begin with an access code, if needed to make an external call (for example, 9). For long-distance numbers, also include 1 and the area code.
Step 5 Indicate whether to lock the key to that action.
Step 6 Click the Save icon.
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/administration/guide/ex/5xcusag160e.html#wp1076028
Hope this helps!
Rob

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Apple Mail problems

Here's the situation:
One PBG4 w/broken screen, running an external (duh) Samsung monitor. This is my shop PB, it's currently masquerading as an immobile desktop.
Another PBG4, which I mostly keep at home, but also use on the road.
LaCie 320GB external Firewire drive. backup at shop (used Migration Assistant to copy the shop PB's system (10.4.7), apps, and docs to the FireWire drive)
Two mail accounts both of which dump into Mail 2.1, on both PBs.
Problem one:
Is there a way -- besides signing up with .Mac -- that I can synchronize the mail on both machines? Failing that, is there a way -- besides doing it message-by-message -- to save the text and attachments from new mail messages?
Problem two:
As far as I can tell, both PBs are set up exactly the same way and certainly the mail prefs are the same, and both PBs are set up with Firefox as the default browser. when I click on a hypertext link in a message on my PB at home, it opens Firefox to the correct page, just like it ought to do, but if I click on an HTML link in a message on my PB at the shop, the mail window flashes once, but nothing opens. This is especially problematic when the clickable link is one of those "click here" links, rather than the actual URL.
What in the ding-dong am I doing wrong?
Thanks!
Bart Brown
PBG4 Mac OS X (10.4.9)
PBG4 Mac OS X (10.4.9)

Locally stored mailboxes and POP accounts cannot be synchronized. The only way to synchronize mail between users or computers is storing it on the server, i.e. using an IMAP account (it doesn’t have to be a .Mac account, any IMAP account would do).
Mail stores most preferences and all account settings in ~/Library/Preferences/com.apple.mail.plist (except the passwords, which are stored in the keychain). Everything else, including all your messages and mailboxes, is stored within the ~/Library/Mail/ folder.
If both computers are running the same major version of Mac OS X, copying these (the preferences file and the entire Mail folder) from one computer to the other is all you need to do in order to have an exact copy of all your messages, mailboxes and Mail settings on both computers.
Locally stored mailboxes can be copied to the Desktop or anywhere else by just dragging them there from Mail itself (for IMAP server-stored mailboxes, transfer the messages to locally stored “On My Mac” mailboxes in Mail first). These, however, are *.mbox folders (not standard mbox files), where messages are stored in individual *.emlx files that other mail clients don’t know or care about. They can be imported back into Mail doing File > Import Mailboxes and choosing Mail for Mac OS X as the data format.
Selected messages can be exported in standard mbox format doing File > Save As and choosing Raw Message Source from the Format popup menu. Standard mbox files can be imported into most mail clients. In particular, they can be imported back into Mail doing File > Import Mailboxes and choosing Other as the data format. Using this format, however, would cause some status flags to be lost (e.g. whether a message has been replied to).
Andreas Amann’s Mail Scripts has an Archive Messages script that you may also find useful.
Finally, there are several backup/archiving solutions for Mail available out there:
http://www.hawkwings.net/plugins.htm#archive
if I click on an HTML link in a message on my PB at the shop,
the mail window flashes once, but nothing opens.
1. Open /Applications/Utilities/Console.
2. From the File menu, choose either Open Console Log, or Open System Log, or both, so that Console displays the contents of both system.log and console.log.
3. Try to reproduce the problem and look at the bottom of the Console windows for messages that might be written there as a result. They may provide some clues.
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder, i.e. ~/Library is the Library folder within the user’s home folder.

How can I transfer mailboxes from one computer to another?

How can transfer all mailboxes(and their contents from one MBP to another? Migration assistant was no help.

Select all your mailboxes, and then select
Mailbox ▹ Export Mailbox...
from the Mail menu bar. Export the mailboxes to the Desktop folder. Transfer them to the new machine.
On the new machine, import the mailboxes:
File ▹ Import Mailbox...

I need to transfer the Smart Mailboxes I have set up on one computer to another computer. Both are running 10.8.4 and Mail 6.3. None of the old solutions are viable since there is no longer a 'Mail' folder in the User account.

I acquired a new iMac, and need to transfer the Smart Mialboxes I have set up on my Mac Pro to the iMac. Mail is already set up to sync thorough iCloud, but the Smart mailboxes are - apparently - set up for individual machines. The only solutions I have been able to locate involve moving Preference files from one machine to the other; the problem is that there is no longer a 'Mail' folder set up for individual Users (actually there is no Mail folder at ALL under 10.8.4), and I am unable to locate any .plist files for Mail at all. Any idea how to make this haoppen?

Create a new smart mailbox. Does it sync? If not, do as below.
Back up all data.
1. Triple-click the line below on this page to select it:
~/Library/Mail/Bundles
Right-click or control-click the highlighted line and select
Services ▹ Open
from the contextual menu. A folder may open, or you may get an error message that the item can't be found. Either result is normal. If the folder does open and has contents, move the contents to the Desktop. Relaunch Mail and test. If there's no change, put the contents of the folder back and quit Mail again.
2. Repeat with this line:
/Library/Mail/Bundles
This time you may be prompted for your login password when you remove the items. Make sure they're removed from the folder and not just copied to the Desktop. If necessary, copy them first and then move the originals to the Trash.

How can I transfer entire contents of Mail mailbox from one Mac to another?

I've long wondered how to do this:
I have two Macs - an iMac and a MacBook Pro.
I have categorized several hundred emails on the MacBook into a separate "mailbox" by itself. Let's just call it "Project XYZ emails" for the sake of discussion.
I need to transfer ALL of those emails +en masse+, hopefully still categorized together into a separate "Project XYZ emails" mailbox file, from the MacBook to the iMac. How is this done?
In the old days, when I used to use Eudora, this was quite simple -- one could physically locate the separate desired "mailbox" file in the Finder and just copy it from one hard drive to the other, and then place the mailbox into the appropriate place of Eudora's file structure on the second computer. Relaunch Eudora and voila, the new mailbox is there for viewing, etc.
But in Mail, I can't find any tangible "file" on my hard drive that represents a "mailbox" in the Mail program. And that includes control-clicking the application file itself and choosing "Show Package Contents." When I do that, I can see, after burrowing into the folders, a single large file called "Mail" which I think contains ALL mailboxes lumped together. But I can't see a way to separate them for individual manipulation.
Any suggestions or ideas on how to copy entire mailboxes in Mail from one Mac to another?

Thanks! Seems to have worked.
Once I imported tham, I had to fiddle around renaming mailboxes and "moving" the emails to the desired locations, but that only took a minute. So overall, seems like that's the solution! I only wish that the steps to do this were made clearer by Apple in the Mail "help" menu -- where I couldn't find any mention of how to do this.
A happy ending, in any event.
In case anyone reads this in the future, let me add in the missing steps, to make it perfectly clear:
In Mail, choose 'archive mailbox' from the mailbox menu.
+Copy the newly created archived mailbox file, which will probably be a file with the suffix ".mbox," from the original machine to the second machine.+
On the second machine: In Mail choose 'import mailbox' from the file menu.
+The emails will now appear in a new mailbox in Mail listed under the name "imported" or "import." If desired, either rename the mailbox, or create a new mailbox with the correct name, and "move" all the emails into it.+
Done!

How can I transfer a local mailbox to another user account on the same computer?

I have two user accounts on the same computer. I actually never really wanted two accounts, but a second one was generated when I chose to use the Migration Assistant to transfer my account from a previous computer to my current one, and I never did anything to delete the second one. Anyway, I have been using Mac Mail to view my work email messages from a Microsoft Exchange server. Awhile back, I was running out of space on my mail server, and decided to download a bunch of my email messages to local mailboxes in order to free up space.
Recently (for reasons that are not terribly relevant) I have decided to switch between the two user accounts on the computer. I have transfered all of my documents, apps, etc. to the new account. However, I haven't been able to find a way to transfer all the email that is in those local mailboxes, so that they are viewable/usable in the new account. Could somebody suggest the best way for me to do this? I am no longer going to use the old account, so the two do not have to be synced. I just want the mailboxes to be available for the new user account (with the same organizational structure).
I am currently running Mavericks (just upgraded last week).
Thanks,
JEG

A quick update....
I copied the folder in ~Library/Mail/V2/Mailboxes that contains all of my local mailboxes over to the same location in the new account. When I go into mail, the entire file structure is there, however it does not let me view (or search) any of the messages. The messages can be accessed through the Finder, though.
I tried to "Rebuild" the local mailboxes, but it didn't seem to do anything. Any advice would be appreciated.
JEG

Can't Transfer user created mailboxes from G4 iMac to new Intel iMac 24"

I recently purchased a new intel based 24" iMac and began setting it up. I ran the Migration Assistant to trnsafer user settings, applications and files. about 80% successful so far after two runs. However, I cannot transfer the various email boxes I set up onthe prior mac to store older emails by subject area. I have a .Mac account, but only the Smart mailboxes seem to be backed up.
Any easy ways to do this so i do not lose my history
iMac G4 17"" to new iMac 24" Mac OS X (10.4.6) Both systems have been updated to latest OS

Steve,
Are these two Macs on the same network? If so, then on the old Mac, in System Preferences/Sharing have you selected to allow Personal File Sharing under the Services Tab. If you do, then in the Finder window of the new Mac click on the Network Icon at the left, and you should see all computers available on the network, that have permitted file sharing. Once you sign onto the old Mac, from the new Mac, use the Import command in Mail to navigate to the old Mac's home folder (that is a choice of what to first connect to), and then the Library in that computer's Home folder (you can't use the Home Icon at the left -- that's your new Mac Home folder), where you will find the Mail folder. Open the Mail folder, and then navigate to one Account folder, select to import all mailboxes in this one Account folder. Once those mailboxes (INBOX.mbox, etc) are imported they will be found below all standard mailboxes, just like any other On My Mac mailbox. Rename them to something descriptive, rather than the standard names. Then do any other Account folders the same way. Next open the Mailboxes folder, within the Mail folder on the old Mac, and proceed to Import. Any mailboxes you created as On My Mac on the old computer can be imported. However, you should check whether you have already named some on the new Mac to what you used on the old Mac.
Hope this is clear, and do not hesitate to ask further questions.
Ernie

Transfer Mailboxes to new IMac

I just bought new iMac. I am transferring data from the old one. I have linked the two with a Firewire. I transferred the iPhoto Library, the iTunes Library and all documents. But I cannot transfer the contents of the old Mailboxes. I found the mailboxes on the old computer OS X > Users > username > Library > Mail > Mailboxes > Messages
However, when trying to copy to the new computer, I am stopped after >username. "Library" has a minus sign on it. So do Desktop, Documents, Movies, Music and Pictures. If I click on "Library" I get the message "could not be opened because you do not have sufficient access privileges." I am the administrator and sole user of this computer. When I bought it this morning, I entered just one password.

You can use the Migration Assistant.
http://docs.info.apple.com/article.html?artnum=25773
Or if the old Mac is running Tiger, quit the Mail.app on the old Mac and using the Finder, go to Home > Library > Mail.
Copy the Mail folder and with the Mail.app quit on the new Mac, place the copy of the Mail folder at Home > Library on your new Mac. If there is an existing Mail folder, this will replace it.
On the old Mac, go to Home > Library > Preferences > com.apple.mail.plist. The com.apple.mail.plist file stores all account information and general Mail.app preferences. Copy the com.apple.mail.plist file and place the copy at Home > Library > Preferences on your new Mac. If there is an existing com.apple.mail.plist file on your new Mac, this will replace it.
Launch Mail on your new Mac and it should be identical to the Mail.app on your old Mac.

Transfer of smart mailbox to a new mac

hi... how do i transfer my SmartMailbox to a new Mac?

If you use Migration or Setup Assistant when you get your new computer the smart mailboxes will be recreated. If not you can easily create them yourself.

Mailbox Transfer

Similar Messages

Maybe you are looking for