Configuring user mailboxes or user accounts in Mercury

[Jim Hurley]

Hello,

I'm just getting familiar with Mercury. I'm using it for a project at a
Hospital I consult for. I've purchased a support package, but,
unfortunately, the Pmail people are having hardware problems. I want to
push forward, so I hope someone can help me with my probably basic
question.

What I want to do is have Mercury running on a Windows server, as an
SMTP server, to receive email addressed to ***@epage.hospital.org .
I've picked Mercury as the server program for this task because of its
support for "domain mailboxes". I want to configure things so that any
email addressed to the "epage.hospital.org" domain will come to my
server. I have the server set up now, and I am running MercuryS to do
the SMTP receiving part of this, and it appears to be working.

The next step is to create the user account or email box. The manuals
don't cover this at all, at least not that I can find. Can anyone tell
me what to do?

My goal is to have all email for this domain come into one email box
that can be accessed by a POP3 client. I want to use Thunderbird to
access this mailbox, but only as a tester. My real goal is to write a
program that can access this mailbox to read and process these emails
as my application demands.

Thanks in advance.

[Guy]

Post by Jim Hurley
"domain mailboxes".
The next step is to create the user account or email box. The
manuals don't cover this at all, at least not that I can find. Can
anyone tell me what to do?

User:

Configuration | Manage local users > Add


Domain Mailbox:

Configuration | Mercury core module> Local domains > Add new domain

Press Help when necessary.

[Jim Hurley]

Post by Guy

Post by Jim Hurley
"domain mailboxes".
The next step is to create the user account or email box. The
manuals don't cover this at all, at least not that I can find. Can
anyone tell me what to do?

Configuration | Manage local users > Add
Configuration | Mercury core module> Local domains > Add new domain
Press Help when necessary.

Guy,

Thanks for your help - I was able to get the local user account
working. I didn't see that option initially. Maybe it appeared when I
turned something else off?

I can now send mail to an account called
***@epage.hospital.org, and I can read this mail with my
thunderbird client.

Next step is to get the Domain mailbox working. I have the
epage.hospital.org domain set up correctly, I think. I went to
Configuration/MercuryCoreModue and clicked on the local domains tab.
There I added a local host or server called epage, and said that it's
Internet name is epage.christianacare.org . Note that this domain is
NOT on the Internet, just the hospital Intranet.

I editted the mercury.ini file directly, since I don't see how to add
this text through the dialog box. Here is the contents of the domains
section:

[Domains]
ds27766: ds27766.christianacare.org
epage: epage.christianacare.org
DM=hci_postmaster epage.christianacare.org

That is all that is in this section, and it looks okay to me, but email
addressed to ***@epage.christianacare.org does not get delivered
to the hci_postmaster mailbox.

I probably have missed something stupid here. Any help is appreciated.

[Guy]

Post by Jim Hurley

Post by Guy

Post by Jim Hurley
"domain mailboxes".
The next step is to create the user account or email box. The
manuals don't cover this at all, at least not that I can find.
Can anyone tell me what to do?

Configuration | Manage local users > Add
Configuration | Mercury core module> Local domains > Add new
domain
Press Help when necessary.

I editted the mercury.ini file directly, since I don't see how to
add this text through the dialog box. Here is the contents of the
[Domains]
ds27766: ds27766.christianacare.org
epage: epage.christianacare.org
DM=hci_postmaster epage.christianacare.org

If ALL mail to the epage.christianacare.org domain is to go to the user
hci_postmaster and no other domain is to used all you need:

[Domains]
DM=hci_postmaster: epage.christianacare.org

(At least I'm pretty sure that is all you need to have)

Manual edit of the INI missed the delimiter :(colon).

In the user interface on the top enter:
DM=hci_postmaster

and on the bottom enter:
epage.christianacare.org

[Jim Hurley]

Post by Guy

Post by Jim Hurley

Post by Guy

Post by Jim Hurley
"domain mailboxes".
The next step is to create the user account or email box. The
manuals don't cover this at all, at least not that I can find.
Can anyone tell me what to do?

Configuration | Manage local users > Add
Configuration | Mercury core module> Local domains > Add new domain
Press Help when necessary.

I editted the mercury.ini file directly, since I don't see how to
add this text through the dialog box. Here is the contents of the
[Domains]
ds27766: ds27766.christianacare.org
epage: epage.christianacare.org
DM=hci_postmaster epage.christianacare.org

If ALL mail to the epage.christianacare.org domain is to go to the
[Domains]
DM=hci_postmaster: epage.christianacare.org
(At least I'm pretty sure that is all you need to have)
Manual edit of the INI missed the delimiter :(colon).
DM=hci_postmaster
epage.christianacare.org

Guy,

Your suggestion worked just like I wanted. Thank you very much for your
time and your patience.

Jim Hurley

[Jay T. Blocksom]

On Tue, 22 Mar 2005 16:05:31 +0000 (UTC), in <comp.mail.pegasus-mail.misc>,
"Jim Hurley" <***@world.std.com> wrote:
[snip]

Post by Jim Hurley
What I want to do is have Mercury running on a Windows server, as an
I've picked Mercury as the server program for this task because of its
support for "domain mailboxes". I want to configure things so that any
email addressed to the "epage.hospital.org" domain will come to my
server.

[snip]

That is not determined by your mail server. It is a matter having the
appropriate MX record(s) in DNS for your domain.

Post by Jim Hurley
I have the server set up now, and I am running MercuryS to do
the SMTP receiving part of this, and it appears to be working.

[snip]

OK.

Post by Jim Hurley
The next step is to create the user account or email box. The manuals
don't cover this at all, at least not that I can find. Can anyone tell
me what to do?

[snip]

First, be sure that you *also* have at least the MercuryP POP3 Server Module
loaded, or you will most likely crash Merc as soon as you take the next step.
With that in mind, go to the pull-down menus...

[Configuration | Manage Local Users]
then
[Add] button

and fill in the fields as desired for your "catch-all" account. You can name
that account anything you want (within reason); but for purposes of this
illustration, I'm going to presume that the username for this account will be
"catchall".

So next, back to the pull-down menus...

[Configuration | Mercury core module]
then
[Local Domains] tab
then
[Add new domain] button

and fill in the fields as follows:

Local host or server: DM=catchall
Internet name: epage.hospital.org

Post by Jim Hurley
My goal is to have all email for this domain come into one email box
that can be accessed by a POP3 client.

[snip]

Presuming you've followed the instructions above, that's exactly what you'll
have.

Post by Jim Hurley
I want to use Thunderbird to
access this mailbox, but only as a tester.

[snip]

That certainly would not be my first choice, but it ought to work.

Post by Jim Hurley
My real goal is to write a
program that can access this mailbox to read and process these emails
as my application demands.

[snip]

Depending on just what you really mean by this, you *might* be barking up the
wrong tree. I suggest you read up on "Policies" (starting with the info in
MERCURY.HLP, if your manuals have not yet been delivered). Odds are you do
*not* really need to force everything through a catch-all mailbox; and
avoiding the catch-all mailbox will also let you avoid a ton of spam spewed
via dictionary attacks.
--
Jay T. Blocksom
--------------------------------
Appropriate Technology, Inc.
usenet02[at]appropriate-tech.net

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Unsolicited advertising sent to this domain is expressly prohibited under
47 USC S227 and State Law. Violators are subject to prosecution.