Configuring elink and Mercury Mailserver

From time to time, you need a test email server on a VM or on a test environment to configure the Content Server elink capabilities. Or maybe a Exchange is too powerful for you?

Then Mercury as an email server and Pegasus as email client may be a good choice for you. You can download this at .

But having a mail server up and running is only half of the price. You still have to configure elink and the mail server.

elink is a Content Server mechanism, which allows you to store documents via email or post replies to to discussions or send documents also via email.

Setting up elink is simple.

You have to imagine, that elink has to have a mailbox on the mail server, which is used to retrieve messages to the content server. This means, a mail to this mailbox is processed by the content server. The mail server must be configured that all mails from a domain will be stored in this mailbox.

for example the message

<123BeDessfdj> must be stored in the elink mailbox to be processed by the content server.

First, lets configure the Mercury Server. First, we need to setup a Content Server used. Lets call it elink.

User Administration on Mercury

Second, we need to setup the Domain for this mailbox. If we enter the DM=user with the username just defined and an Internet Name (here for our mails to the content server, we define that allĀ  mails from the Domain will be stored in the elink mailbox.

Domain Administration on Mercury

Next, we need to configure elink. This must be done on the Content Server admin pages.

elink on Admin pages
Configuration of elink on the admin pages

Virtual Hostname is the name of the Domain, from which we want to store all messages in the elink mailbox.

Username/Password is the name of out mailbox user (elink) and its password. You can test the connection by pressing the “Test Connection” button.

If everything runs, you’ll see mails like these in the Pegasus mail client.

If everything runs, Content Server can be used though Pegasus