Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » Import / use .MSG files
  •  
bengdell

Messages: 4
Karma: 0
Send a private message to this user
Hi,

I am looking to move from MDaemon to Kerio, but MDaemon stores all emails in the .MSG format. I have scoured the forums and google for a solution but can't seem to find one. Does anyone have any bright ideas?

As a test i installed a trial version of Kerio onto one of my windows machines. I set-up a test domain and user account. I then copied an email from one of my MDaemon accounts into the relevant 'store' folder for the test account i set-up and then loaded up Outlook. Obviously i was unable to view the message. So, i have learnt that Kerio cannot read .MSG files natively so can only assume that my only option is to find a way to convert or import legacy .MSG files into Kerio. Is there a way to do this?

Really hoping there are a few pieces of wonderful advice out there in the community as without a solution it is difficult to move over to Kerio.

Thanks in advance

Ben
  •  
talkinggoat

Messages: 49
Karma: 0
Send a private message to this user
Export the messages, addresses, and whatever else into .pst files, using outlook. Setup Kerio. Connect outlook to the Kerio server. Import the .pst files.
  •  
bengdell

Messages: 4
Karma: 0
Send a private message to this user
Thanks for the suggestion. I was hoping there would be a way to do this from the server end. I.e. so that i can convert and import all .MSG files into EML files in batch without having to involve the end-users.

Is there any known way to do this?
  •  
sedell

Messages: 1168
Karma: 1
Send a private message to this user
Probably not. It's not just the messages themselves that need to get moved to the new location, the whole database for each account needs to be created. You still need to have all of the indexes created, the properties files, search and sort information, etc. There's more to it than just the .eml files. It may look like just a collection of .eml files in a bunch of folders, but it's actually a database. Just dropping the mail files into the location bypassing the mail server won't make a working mailbox.

Scott
  •  
bengdell

Messages: 4
Karma: 0
Send a private message to this user
Ah interesting. OK looks like the original suggestion is probably the way to go then.
  •  
pkngan

Messages: 1
Karma: 0
Send a private message to this user
Very simple,

1. you just copy all .msg files into user\INBOX\#msg\.

2. Than, you need to rename all .msg files to 8 digits filename such as 00000001.msg 00000002.msg and so on. You may use Total Commander rename tool or another tool.

3. delete \INBOX\index.fld

Server will reindex when a new message arrived to the box or restart server to get luck.

I success convert email from Merak and MDaemon too.

Ngan

[Updated on: Wed, 06 August 2008 09:27]

  •  
bengdell

Messages: 4
Karma: 0
Send a private message to this user
Fantastic. That sounds nice and simple. I will give it a go.


  •  
supersheep

Messages: 7
Karma: 0
Send a private message to this user
I've used Emailchemy in the past to convert user mailboxes. It's pretty smart.

http://www.weirdkid.com/products.html

You could, for example, convert the mailbox at the client end to PST, then use Outlook with the Kerio account added as KOFF/IMAP and then copy it to the server.

That's how I'd go with it, assuming Emailchemy can handle that file format (never met a format it couldn't!)

You can also use the built-in IMAP server to move the mail around, but that's a bit more tech.

And no, I don't work for weirdkid, just like the product! Smile
  •  
i.kellywashington

Messages: 2
Karma: -2
Send a private message to this user
what is the file format of kerio?
  •  
Carsten Maas (Kerio)

Messages: 247
Karma: 27
Send a private message to this user
All files (mails, contacts, calendars etc.) are in eml format

Carsten Maas
Senior Technical Marketing Engineer
Kerio Technologies

Kerio Deutschland youtube Channel
http://www.youtube.com/KerioDeutschland
  •  
ksnyder (KERIO)

Messages: 526
Karma: 34
Send a private message to this user
*.eml for the email itself
*.env for the SMTP envelope

Ken Snyder
Director, Sales Engineering | Kerio
Stay Connected Anytime, Anywhere. Discover Kerio Cloud!
  •  
i.kellywashington

Messages: 2
Karma: -2
Send a private message to this user
can you mention steps to import eml files in kerio app
  •  
j.a.duke

Messages: 337
Karma: 10
Send a private message to this user
@supersheep mentioned EMailchemy.

That app has a built-in IMAP server, so it might be possible to use the Kerio IMAP migration tool (KIMT) to move messages from .msg directly into Kerio. No guarantee, nor have I tested EMailchemy or KIMT for this scenario.

The other option is, if you have a consistent directory structure for the EML files is to use a variety of python or perl modules & code to move from the structured data into Kerio server via IMAP; again not tested and only theoretical.

There's not a direct route into Kerio from raw eml files.

Cheers,
Jon
Previous Topic: Thunderbird/Lightning - CalDav URL not working after upgrade to 9.0.4
Next Topic: Kerio software maintenance
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Sun Dec 11 14:47:29 CET 2016

Total time taken to generate the page: 0.00950 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.