> I am a total newbie to mercury mail. I installed it on a server using
> Scenario 1: Permanent internet connection. I did not create any
> mailboxes - all emails sent to this server are to be forwarded.
You must create at least one mailbox, the local user that handles the postmaster cannot be forwarded for obvious reasons.
> Using the alias configuration, I set up an email forwarder which
> redirects email sent to firstname.lastname@example.org to
> email@example.com. Using the Send mail message capability
> from within the Mercury console, I sent an email to me and it wound up
> in my inbox.
Much better is to use one of the tools to do this via forwarding
These are NOT a true MX host function since it does not queue and wait for the receiving system to be online to send the mail. That said, WSMTPEx will keep retrying if the connection to the server and port cannot be made. I have not tested how long it will continue retrying.
1. First of all is the simplest, you simply re-write the domain in the mercury.ini [Rewrite] section.
I really was surprised when this one worked since it truly simple and has been there
all along. You learn something new every day. The brackets are required when using
an IP address. This forwards all mail for firstname.lastname@example.org to
email@example.com using the normal Mercury/32 send process via port 25.
Works quite well when using MercuryE, cannot work when using MercuryC unless the
IP address is a routable IP address. You must re-boot Mercury/32 for each change
since this is only read at startup.
2. The second one is the daemon MercFwd and it essentially does the same thing as
the rewrite but this can be done dynamically by changing the domains section. The
[Domains] entry of
does essentially the same thing as the rewrite above. Again it uses Mercury to deliver
the mail via port 25 and so you cannot use this with MercuryC when using non-
routable IP addresses.
3. The third one is the program WSMTPEx.exe (SMTPEX.NLM for Netware) and this a a
separate program that takes mail for a email account and forwards it to any port and
any hostname/IP address. I use this with my domains to forward the mail to a Linux
system (must use high ports as non-root) and to a second instance of Mercury/32
running on my system (can't share port 25) Here's a sample of the ini file I use for
forwarding all mail to Mercury/32 running on Ubuntu v8.10 and Wine.
# You can rename this tool, but name of following section must remain [WSMTPEx]
# TCP port, on which SMTP server listens
# Number of seconds to delay between searches for emails
# Folder, under which is most of user's mailboxes
# Users mail address domain part
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
This takes all the mail in the domain account "UBUNTO" and sends it to port 8025 on
192.168.1.4 to be received by MercuryS. The directory BADMAIL I have specified
must exist. You can run multiple instances of this tool and and it can be run as a
service. If run as a service and running multiple instances the name of the program
should be changed. I use WSE-UBUNTO to rename the program and ini file for this
Many thanks to Petr Jaklin for the development of these tools. You can get these
tools at the community download areas or directly from Petr Jaklin's site
> Next, I sent a message from my computer to firstname.lastname@example.org. Looking at
> the Mercury SMTP server console window, I see that the message did
> make it to the server. However, it reported 'user <email@example.com>
> not known'. I also received a bounce email which stated:
Looks like the alias was wrong. I do this all the time when receiving mail for non-local users. Could you provide exactly what was entered as the alias?