These fields are ignored by legacy mailers and Note: when CommuniGate Pro stores a message in a BSD-type mailbox, it adds additionalįields to the separator ( From) line. Have external INBOXes (see above), and the old mailbox files will be used "in place". Places in the CommuniGate Pro account directories, or you can specify that some accounts You should either copy the old mailbox files into the proper Since most legacy mail systems use this format, the existing mailbox files can be used when The default format for CommuniGate Pro mailboxes is the BSD-type text mailbox format:Ī mailbox is a text file with messages separated with an empty line and a line starting It can only guarantee (using file locks) that legacy mailers do not destroy a mailbox while CommuniGate Pro is working with it.įor more details, see the Sharing section. CommuniGate Pro cannot fix this, since these mailers bypass the server,
TheyĬan destroy data in your mailbox if you open two legacy mailer sessions with the same mailboxĪnd delete messages in one of the sessions. Note: legacy mailers were not designed to support simultaneous access to mailboxes. Mechanism to synchronize its activity with legacy mailers. When the Server accesses these external mailboxes, it uses the OS file-locking Location where legacy mailers expect to see user mailboxes. Usually, you specify /var/mail/* or /var/spool/mail/* - the "standard" Instead, the mailbox location will be taken from the In this case, the account INBOX will not be created inside the CommuniGate Proīase directory. Mail access via legacy mailers, select the External INBOX When you create a CommuniGate Pro account for a local user who needs On a properly configured system direct user access to the baseĭirectory is prohibited to ensure that account mailboxes and other Server files stay intact. The CommuniGate Pro Server keeps all user accounts and mailboxes inside its Protocols, the CommuniGate Pro server has no control over those mailers. Mailer applications that read mailbox files directly. Some users registered with the server OS may access their mail accounts using legacy Not only the published mail access protocols standards, but most of unofficial protocol extensions, too. Users that access their mail accounts using any standard Internet Protocol (POP, IMAP)ĭo not have to switch their mailer applications or change mailer settings - CommuniGate Pro supports provide services for "local users" - the users of "local" (Unix) mail programs thatĭirectly access their mailbox files, bypassing E-mail protocols (such as the POP or IMAP protocols).to migrate all user E-mail from the old server to the new CommuniGate Pro Server.Specified account settings, especially - account passwords to create all existing mail accounts on your new CommuniGate Pro Server, using already.Integrate your existing E-mail environment into the CommuniGate Pro messaging system. If your system was already running some type of mail server, you may want to Migrating from an Arbitrary Server ("on-the-fly" migration).Copying All Mailboxes from Other Servers.Copying Mailboxes from Other IMAP Servers.Copying Mailboxes from Other POP Servers.Migrating from Microsoft® Exchange Servers.Migrating from CommuniGate/MacOS and SIMS.Migrating from Netscape®/iPlanet Messaging Servers.CommuniGate Pro Server: Migrating to CommuniGate Pro