Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Where does Eudora store email files?

Eudora supports both POP and IMAP mail accounts.  Using POP, messages are stored on a local drive.  Using IMAP, messages are stored on a server until the user views them, at which point Eudora downloads and makes a local copy.  Typically, mailboxes and directories defined for an IMAP mail account will be stored in a top level directory called “Dominant”.

The path to POP mailboxes is usually something like:
   c:\Documents and Settings\[username]\Application Data\Qualcomm\Eudora
   c:\Users\[username]\AppData\Roaming\Qualcomm\Eudora

The path to IMAP mailboxes is usually something like:
   c:\Program Files\Qualcomm\Eudora\Imap\Dominant\
   c:\Users\[username]\AppData\Roaming\Qualcomm\Eudora\Imap\Dominant

If you are not sure where Eudora data files are located, you can search for the "eudora.ini" file.  The directory containing this file should be the Eudora data directory.

How does Eudora store email files?

Eudora stores each mailbox in a separate MBOX (.mbx) file.  Attachments are stored separately from messages in a separate "attach" directory.  Embedded images (meant to display within a message) are also stored separately in a separate "embedded" directory.  There are also mailbox directories and additional file types to look out for. 

Below is a list of data types found in Eudora email content that you should include in your EAS submission:

  • Mailboxes:  Includes files with the .mbx extension accompanied by similarly-named files but different extensions (.toc, .inf, etc.).  Standard in and out mailboxes will be located in the top level Eudora directory for POP accounts.  IMAP accounts support local mailboxes in the top level Eudora directory and IMAP mailboxes a few levels down in the eudora\imap\dominant\ directory.
     
  • Directories:  Eudora supports creation of nested mail directories to organize mailboxes.  In POP accounts, these directories are identified on the file system with the ".fol" extension (e.g., projects.fol).  One or more mailboxes will be nested inside this type of directory. For IMAP accounts, mailbox directories lack the .fol extension.
     
  • Nicknames:  Any files with the name "nndbase" in the top Eudora directory or in a “Nickname” subdirectory are nickname files.  These are part of the Eudora address book.  This file stores email addresses and associated nicknames. In some scenarios where the address book is used, outbox messages may contain nicknames without the corresponding email addresses in the “To:” field.  (Note: this is only an issue for messages in the outbox.)  If your Eudora email content includes an outbox (out.mbx), it is important to include any nickname files as part of your EAS packet submission.
     
  • Attachments:   All attachments are stored separately from their associated messages in a separate "attach" directory.  In POP accounts, there is one “attach” directory in the top level Eudora directory.  In IMAP accounts, there will also be separate “attach” directories nested inside each specific mailbox directory. 
    Note that Eudora marks the associated message with a relative path to the attachment file's location.  When you transfer Eudora content to you staging directory, be sure to maintain the attach directory's location relative to the mailboxes.  Maintaining relative locations helps EAS re-associate messages with their attachments during the conversion process.
  • Embedded files:  Includes files such as images that are meant to display within a message.  These files are stored in a single "embedded" directory under the top level Eudora directory.  For embedded files, follow the attachments guideline about maintaining relative location of this file in your EAS submission.

There may be other file types present in your Eudora content -- these may not play a direct role in the EAS conversion of messages and attachments, but for purposes of digital preservation should be included when possible. 

Below is a sample of the Eudora data directory structure in a POP account.

c:\Users\MJJ\AppData\Roaming\Qualcomm\Eudora

               descmap.pce

               Eudora.ini

               Gardening.mbox

               Gardening.toc

               In.mbx

               In.toc

               Junk.mbx

               Junk.toc

               Out.mbx

               Out.toc

               Trash.mbx

               Trash.toc

               >attach

               >embedded

               >Nickname

               >AdministrativeNews.fol

                              Jan.mbx

                              Jan.toc

                              Feb.mbx

                              Feb.toc

               >Projects.fol

                              APAA.mbx

                              APAA.toc

                              descmap.pce

                              Scholarship.mbx

                              Scholarship.toc

Below is a sample of the Eudora data directory structure in an IMAP account.

c:\Users\MJJ\AppData\Roaming\Qualcomm\Eudora

               descmap.pce

               Eudora.ini

               Gardening.mbox

               Gardening.toc

               In.mbx

               In.toc

               Junk.mbx

               Junk.toc

               Out.mbx

               Out.toc

               Trash.mbx

               Trash.toc

               >embedded

               >Imap

                              >Dominant

                                             mboxlist.lst

                                             >AdministrativeNews

                                                            Jan.act

                                                            Jan.inf

                                                            Jan.mbx

                                                            Jan.opt

                                                            Jan.toc

                                                            >attach

                                             >INBOX

                                                            INBOX.act

                                                            INBOX.inf

                                                            INBOX.mbx

                                                            INBOX.opt

                                                            INBOX.toc

                                                            >attach

                                             >Projects

                                                            APAA.act

                                                            APAA.inf

                                                            APAA.mbx

                                                            APAA.opt

                                                            APAA.toc

                                                            >attach