mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
parent
9fd72b030c
commit
0572e0ccc4
|
@ -270,7 +270,7 @@ Outlook-to-Unix-Mailbox</ULink>, <CiteTitle>
|
|||
MS Outlook to Unix Mailbox Conversion mini HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>
|
||||
Updated: Dec 2003</CiteTitle>.
|
||||
Updated: Jan 2004</CiteTitle>.
|
||||
Covers conversion of old email in Microsoft Outlook
|
||||
(not Outlook Express!) to typical Unix file formats. </Para>
|
||||
</ListItem>
|
||||
|
@ -695,7 +695,7 @@ Outlook-to-Unix-Mailbox</ULink>, <CiteTitle>
|
|||
MS Outlook to Unix Mailbox Conversion mini HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>
|
||||
Updated: Dec 2003</CiteTitle>.
|
||||
Updated: Jan 2004</CiteTitle>.
|
||||
Covers conversion of old email in Microsoft Outlook
|
||||
(not Outlook Express!) to typical Unix file formats. </Para>
|
||||
</ListItem>
|
||||
|
|
|
@ -3314,7 +3314,7 @@ installation under RedHat Linux 8.x and 9.x. </Para>
|
|||
Outlook-to-Unix-Mailbox</ULink>,
|
||||
<CiteTitle>MS Outlook to Unix Mailbox Conversion mini HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>Updated: Dec 2003</CiteTitle>.
|
||||
<CiteTitle>Updated: Jan 2004</CiteTitle>.
|
||||
Covers conversion of old email in Microsoft Outlook
|
||||
(not Outlook Express!) to typical Unix file formats. </Para>
|
||||
</ListItem>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
<author>Greg Lindahl, <tt/lindahl@pbm.com/
|
||||
|
||||
<date>v1.3, 2003-12-29
|
||||
<date>v1.4, 2004-01-08
|
||||
|
||||
<abstract>
|
||||
This MiniHowto covers conversion of old email in Microsoft
|
||||
|
@ -38,7 +38,7 @@ documented at:
|
|||
<sect1>Copyright
|
||||
<p>
|
||||
|
||||
Copyright (c) 2001-2003 by Greg Lindahl
|
||||
Copyright (c) 2001-2004 by Greg Lindahl
|
||||
|
||||
<p>
|
||||
|
||||
|
@ -91,6 +91,8 @@ Outlook to talk to IMAP servers if it's in Exchange mode.
|
|||
|
||||
1.3: Yet more minor fixes.
|
||||
|
||||
1.4: Information about TNEF stuff from Scott Phelps (thanks!)
|
||||
|
||||
<sect1>Other ways of doing this
|
||||
<p>
|
||||
A list of conversion utilities, many commercial, may be found at:
|
||||
|
@ -112,9 +114,9 @@ mailboxes -- but the only solid report I've gotten was that
|
|||
attachments were not converted, so if they matter to you, don't use
|
||||
this method.
|
||||
|
||||
I found some documentation on the Ximian Evolution
|
||||
website. I haven't tried this since I don't have a Windows machine
|
||||
anymore. But, here's what they say to do:
|
||||
There is some documentation on the Ximian Evolution website. I haven't
|
||||
tried this since I don't have a Windows machine anymore. But, here's
|
||||
what they say to do:
|
||||
|
||||
Run Mozilla Mail
|
||||
|
||||
|
@ -278,16 +280,18 @@ right-click on the folder name and select the "Copy" option. For the
|
|||
destination, pick your Linux server at the bottom of the list.
|
||||
|
||||
<p>
|
||||
|
||||
However, life isn't quite that simple. Outlook supports folders
|
||||
containing folders which also contain messages. The Linux IMAP server
|
||||
does not support that; a folder is either a regular file containing
|
||||
messages, or a directory containing subdirectories and files. So if
|
||||
you have folders in Outlook with both messages and subfolders, you
|
||||
can't copy the entire tree over to the Linux IMAP server. Another
|
||||
incompatibility of the Linux IMAP server is that you have to tell it
|
||||
in advance if a new folder will contain subfolders or messages. You do
|
||||
this by appending a slash (<tt>/</tt>) to the folder name when you create
|
||||
it. This slash will disappear when the folder is created.
|
||||
containing folders which also contain messages. Linux IMAP servers do
|
||||
not support that (at least those using Mailbox format); a folder is
|
||||
either a regular file containing messages, or a directory containing
|
||||
subdirectories and files. So if you have folders in Outlook with both
|
||||
messages and subfolders, you can't copy the entire tree over to the
|
||||
Linux IMAP server. Another incompatibility of the Linux IMAP server is
|
||||
that you have to tell it in advance if a new folder will contain
|
||||
subfolders or messages. You do this by appending a slash (<tt>/</tt>)
|
||||
to the folder name when you create it. This slash will disappear when
|
||||
the folder is created.
|
||||
|
||||
<p>
|
||||
So, in order to copy a tree of folders to the Linux IMAP server, first
|
||||
|
@ -315,6 +319,24 @@ also one extra message per folder which is a (useless) header.
|
|||
line, which contains the envelope address of the email. Fortunately
|
||||
you don't actually need that information.)
|
||||
|
||||
<p>
|
||||
|
||||
An additional wrinkle applies regarding attachments. Microsoft
|
||||
sometimes bundles together several attachments into a ms-tnef
|
||||
attachment; TNEF stands for Transport Neutral Encapsulation
|
||||
Format. This attachment contains several mime-encoded attachments. I
|
||||
was lucky that my mail folders didn't contain any of these -- they
|
||||
seem to be created when people send you "Rich Text Format" email -- it
|
||||
contains two alternatives, one in plain text and the other a
|
||||
TNEF-encapsulated version of the message in rich text plus any
|
||||
attachments.
|
||||
|
||||
<p>
|
||||
|
||||
Fortunately, there are some ways to unpack TNEF attachments.
|
||||
One is the tnef project hosted on sourceforge, the other is
|
||||
ktnef, which is a part of KDE.
|
||||
|
||||
<sect1>Deinstall IMAP from your Linux box
|
||||
<p>
|
||||
Once you've transferred all of your email, you will want to deinstall
|
||||
|
@ -336,3 +358,4 @@ Voila! You have taken another step towards a Microsoft-free lifestyle.
|
|||
|
||||
</article>
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue