Can we set up Mercury as a secondary MX Server?

Rolf Lindby

posted Sep 19 '12 at 9:21 pm

For SMTP forwarding of messages in a domain mailbox you can use WSMTPEx.exe, as mentioned in the link I posted before:

Thomas R. Stephenson:

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]
[WSMTPEx]
Version=0.10
# TCP port, on which SMTP server listens
Port=8025
# Number of seconds to delay between searches for emails
LoopDelay=30
# Folder, under which is most of user's mailboxes
UserFolder=
Domains=1
# Users mail address domain part
Domain1=linux-tstephenson.com
LogName=c:\Mercury\WSMTPEx.log
SMTPServer=192.168.1.4
MailBoxes=1
Badmails=c:\pmail\mail\BadMail

[linux-tstephenson.com]
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mb1addr=dm:ubunto
Mb1dir=c:\pmail\mail\ubunto

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 one.

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 http://www.3net.cz/software/softe.htm

/Rolf

For SMTP forwarding of messages in a domain mailbox you can use WSMTPEx.exe, as mentioned in the link I posted before:Thomas R. Stephenson: <blockquote>The third one is the program WSMTPEx.exe (SMTPEX.NLM for Netware)&nbsp; and this a a separate program that takes mail for a email account and forwards it to any port and any hostname/IP address.&nbsp; 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)&nbsp; Here's a sample of the ini file I use for forwarding all mail to Mercury/32 running on Ubuntu v8.10 and Wine. &nbsp; &nbsp;#&nbsp; You can rename this tool, but name of following section must remain [WSMTPEx] [WSMTPEx] Version=0.10 #&nbsp; TCP port, on which SMTP server listens Port=8025 #&nbsp; Number of seconds to delay between searches for emails LoopDelay=30 #&nbsp; Folder, under which is most of user's mailboxes UserFolder= Domains=1 # Users mail address domain part Domain1=linux-tstephenson.com LogName=c:\Mercury\WSMTPEx.log SMTPServer=192.168.1.4 MailBoxes=1 Badmails=c:\pmail\mail\BadMail [linux-tstephenson.com] # When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file Mb1addr=dm:ubunto Mb1dir=c:\pmail\mail\ubunto This takes all the mail in the domain account "UBUNTO"&nbsp; and sends it to port 8025 on 192.168.1.4 to be received by MercuryS.&nbsp; The directory BADMAIL I have specified must exist.&nbsp; You can run multiple instances of this tool and and it can be run as a service.&nbsp; If run as a service and running multiple instances the name of the program should be changed.&nbsp; I use WSE-UBUNTO to rename the program and ini file for this one. &nbsp; Many thanks to Petr Jaklin for the development of these tools.&nbsp; You can get these tools at the community download areas or directly from Petr Jaklin's site <a href="http://www.3net.cz/software/softe.htm" title="http://www.3net.cz/software/softe.htm" style="color: rgb(0, 0, 0); text-decoration: none; font-family: Tahoma,Arial,Helvetica; font-size: 12px;" mce_href="http://www.3net.cz/software/softe.htm">http://www.3net.cz/software/softe.htm</a>&nbsp;&nbsp;</blockquote>/Rolf&nbsp;

ChrisGWarp

posted Aug 3 '12 at 2:49 pm

If so how?

-Chris

If so how?&nbsp;-Chris&nbsp;

Rolf Lindby

posted Aug 3 '12 at 9:07 pm

There is an example on how to configure a secondary mail server in this thread:

http://community.pmail.com/forums/thread/4772.aspx

/Rolf

There is an example on how to configure a secondary mail server in this thread:<a href="http://community.pmail.com/forums/thread/4772.aspx">http://community.pmail.com/forums/thread/4772.aspx</a><a href="http://community.pmail.com/forums/thread/4772.aspx"></a>/Rolf&nbsp;

ChrisGWarp

posted Sep 10 '12 at 11:55 am

Hi Rolf.

Perhaps I'm missing something, but that's not quite what I had in mind.

This is my DNS setup:

C:\MERCURY>nslookup

Default Server: gateway.warpspeed.com.au
Address: 203.27.78.133

> set q=mx
> warpspeed.com.au
Server: gateway.warpspeed.com.au
Address: 203.27.78.133

Non-authoritative answer:
warpspeed.com.au        MX preference = 20, mail exchanger = main.warpspeed.com.au
warpspeed.com.au        MX preference = 5, mail exchanger = vhost.warpspeed.com.au
warpspeed.com.au        MX preference = 10, mail exchanger = inet.warpspeed.com.au

warpspeed.com.au        nameserver = wendy.virtual.net.au
warpspeed.com.au        nameserver = ns.virtual.net.au
warpspeed.com.au        nameserver = inet.warpspeed.com.au
warpspeed.com.au        nameserver = main.warpspeed.com.au
vhost.warpspeed.com.au internet address = 203.27.78.1
inet.warpspeed.com.au   internet address = 203.27.78.4
main.warpspeed.com.au   internet address = 203.27.78.129
>

Mercury is running on vhost.

Ideally, I'd like all mail to go to vhost first, hence the lowest MX weight, and then forwarded to inet, the real primary server. Main, which is not running mercury, is still a further secondary.

The other thread is talking about using MercuryD, the pop server to achieve this, which is not what I had in mind.

I'm at a loss as how to configure a "Domain User".

Or have I just missed something really, really simple and obvious?

-Chris

Hi Rolf.&nbsp;Perhaps I'm missing something, but that's not quite what I had in mind.This is my DNS setup:C:\MERCURY&gt;nslookup <blockquote>Default Server:&nbsp; gateway.warpspeed.com.au Address:&nbsp; 203.27.78.133 &gt; set q=mx &gt; warpspeed.com.au Server:&nbsp; gateway.warpspeed.com.au Address:&nbsp; 203.27.78.133 Non-authoritative answer: warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MX preference = 20, mail exchanger = main.warpspeed.com.au warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MX preference = 5, mail exchanger = vhost.warpspeed.com.au warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MX preference = 10, mail exchanger = inet.warpspeed.com.au warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nameserver = wendy.virtual.net.au warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nameserver = ns.virtual.net.au warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nameserver = inet.warpspeed.com.au warpspeed.com.au&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nameserver = main.warpspeed.com.au vhost.warpspeed.com.au&nbsp; internet address = 203.27.78.1 inet.warpspeed.com.au&nbsp;&nbsp; internet address = 203.27.78.4 main.warpspeed.com.au&nbsp;&nbsp; internet address = 203.27.78.129 &gt; </blockquote>Mercury is running on vhost.Ideally, I'd like all mail to go to vhost first, hence the lowest MX weight, and then forwarded to inet, the real primary server. Main, which is not running mercury, is still a further secondary.The other thread is talking about using MercuryD, the pop server to achieve this, which is not what I had in mind.I'm at a loss as how to configure a "Domain User".Or have I just missed something really, really simple and obvious?-Chris

Rolf Lindby

posted Sep 10 '12 at 9:38 pm

Here is what Mercury help says about setting up a domain mailbox:

Mercury supports the idea of a domain mailbox, or a mailbox that accepts mail addressed to any user at a given domain. To create a domain mailbox, first create the user account that is to receive all mail addressed to the domain, then place an entry in the Domains recognized as local by this server section in the following format:

DM=username domain address

username can be any valid reference to a single local user on your system. So, to create a domain mailbox where user mailserver receives all mail addressed to any user in the domain fish.net, you would create this entry:

DM=mailserver fish.net

With this entry in place, mail sent to [any address]@fish.net will be delivered into user mailserver's mailbox.

This setup normally works well for a secondary mail server. Some more direct SMTP approaches can be found in this thread:

http://community.pmail.com/forums/post/22615.aspx

/Rolf

Here is what Mercury help says about setting up a domain mailbox:<blockquote>Mercury supports the idea of a domain mailbox, or a mailbox that accepts mail addressed to any user at a given domain. To create a domain mailbox, first create the user account that is to receive all mail addressed to the domain, then place an entry in the Domains recognized as local by this server section in the following format: &nbsp;&nbsp;&nbsp; DM=username&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; domain address username can be any valid reference to a single local user on your system. So, to create a domain mailbox where user mailserver receives all mail addressed to any user in the domain fish.net, you would create this entry: DM=mailserver&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; fish.net With this entry in place, mail sent to [any address]@fish.net will be delivered into user mailserver's mailbox. </blockquote>This setup normally works well for a secondary mail server. Some more direct SMTP approaches can be found in this thread: <a href="http://community.pmail.com/forums/post/22615.aspx">http://community.pmail.com/forums/post/22615.aspx</a>&nbsp;/Rolf

ChrisGWarp

posted Sep 11 '12 at 3:30 am

Part of the issue in creating a Domain Mailbox, is that I've not been able to find it. Certainly, I've not seen anything where I can set the "Domains recognized as local by this server section", as specified in the help.

Or am I missing something?

I'll have a look at the other link, thanks!

-Chris

Part of the issue in creating a Domain Mailbox, is that I've not been able to find it. Certainly, I've not seen anything where I can set the "Domains recognized as local by this server section", as specified in the help.Or am I missing something?I'll have a look at the other link, thanks!-Chris

ChrisGWarp

posted Sep 11 '12 at 3:35 am

Is the statement from that thread:

"You are talking about Mercury/32 as a MX host. Mercury/32 currently does

not provide MX services. David's looking into this for a future

enhancement but until that happens here's 3 possible work arounds."

Still true?

Yes, that is exactly what I am trying to do, set up Mercury as a secondary MX to feed into my primary MX. So it needs to receive all mail, and forward it. Ideally, after having been checked for spam etc (which is what is driving all of this).

-Chris

Is the statement from that thread:"You are talking about Mercury/32 as a MX host. Mercury/32 currently does not provide MX services.&nbsp; David's looking into this for a future enhancement but until that happens here's 3 possible work arounds."Still true?Yes, that is exactly what I am trying to do, set up Mercury as a secondary MX to feed into my primary MX. So it needs to receive all mail, and forward it. Ideally, after having been checked for spam etc (which is what is driving all of this).-Chris

Rolf Lindby

posted Sep 11 '12 at 4:11 am

You will find it in the "Local domains" tab in Core configuration.

/Rolf

You will find it in the "Local domains" tab in Core configuration./Rolf&nbsp;

Rolf Lindby

posted Sep 11 '12 at 4:27 am

Personally I prefer using domain mailboxes for forwarding mail from a secondary mail server to the primary, but the SMTP solutions described in the other thread

will work as well. As you might guess I wouldn't have linked it if it was obsolete. Until Mercury v5 is out these are the available options.

/Rolf

Personally I prefer using domain mailboxes for forwarding mail from a secondary mail server to the primary, but the SMTP solutions described in the other thread will work as well. As you might guess I wouldn't have linked it if it was obsolete. Until Mercury v5 is out these are the available options./Rolf&nbsp;

ChrisGWarp

posted Sep 11 '12 at 6:33 am

Oh, fair enough.

So back to one of my original questions:

How does one set up a domain mailbox?

-Chris

Oh, fair enough.So back to one of my original questions:&nbsp;How does one set up a domain mailbox?&nbsp;-Chris

ChrisGWarp

posted Sep 11 '12 at 9:18 am

Oops. Sorry. I missed your response above.

I've created the three variants of the domain (host, FQDN and IP).

However, I have been able to work out where to set the "Domains recognized as local by this server section" bit.

Is this to be set via the GUI or via editing the INI file directly?

The help is unclear (to me at least).

-Chris

Oops. Sorry. I missed your response above.I've created the three variants of the domain (host, FQDN and IP).However, I have been able to work out where to set the "Domains recognized as local by this server section" bit.Is this to be set via the GUI or via editing the INI file directly?The help is unclear (to me at least).-Chris

PaulW

posted Sep 11 '12 at 8:15 pm

[quote user="ChrisGWarp"]However, I have been able to work out where to set the "Domains recognized as local by this server section" bit.

Is this to be set via the GUI or via editing the INI file directly?

The help is unclear (to me at least).[/quote]

Go to the menu bar: Configuration / Mercury core module, then click on the Local domains tab.

There are many configuration items to set up but most can be left on their default setting. Local domains is not one of those - you must fill it in or no mail will be accepted.

[quote user="ChrisGWarp"]However, I have been able to work out where to set the "Domains recognized as local by this server section" bit. Is this to be set via the GUI or via editing the INI file directly? The help is unclear (to me at least).[/quote] Go to the menu bar: Configuration / Mercury core module, then click on the Local domains tab. There are many configuration items to set up but most can be left on their default setting.&nbsp; Local domains is not one of those - you must fill it in or no mail will be accepted.

ChrisGWarp

posted Sep 15 '12 at 8:04 am

Ok, I'd already done that. I'd set up the local machine as it's own domain, with the three variants of the domain (host, FQDN and IP).

However, I have been able to work out where to set the "Domains recognized as local by this server section" bit.

Is this to be set via the GUI or via editing the INI file directly?

The help is unclear (to me at least).

-Chris

Ok, I'd already done that. I'd set up the local machine as it's own domain, with the three variants of the domain (host, FQDN and IP).However, I have been able to work out where to set the "Domains recognized as local by this server section" bit.Is this to be set via the GUI or via editing the INI file directly?The help is unclear (to me at least). &nbsp;-Chris

Rolf Lindby

posted Sep 15 '12 at 4:19 pm

Most settings can be made either via the GUI or by editing the ini file. If you want to create an entry for a domain mailbox via the GUI you go to the "Local domains" tab in Core configuration and click "Add new domain". A new dialog window with two empty text boxes will open. In "Local host or server" you should enter "DM=" followed by the name of the mailbox you have created for the domain, for instance "DM=mydomainmailbox". In "Internet name" you should enter the name of the domain, for instance "mydomain.com". Then click OK, verify that the new entry has appeared in the Local domains tab, and click OK again. Restart Mercury to make the new rule active.

/Rolf

Most settings can be made either via the GUI or by editing the ini file. If you want to create an entry for a domain mailbox via the GUI you go to the "Local domains" tab in Core configuration and click "Add new domain". A new dialog window with two empty text boxes will open. In "Local host or server" you should enter "DM=" followed by the name of the mailbox you have created for the domain, for instance "DM=mydomainmailbox". In "Internet name" you should enter the name of the domain, for instance "mydomain.com". Then click OK, verify that the new entry has appeared in the Local domains tab, and click OK again. Restart Mercury to make the new rule active./Rolf&nbsp;&nbsp;

ChrisGWarp

posted Sep 19 '12 at 11:46 am

Ok, I appear to have done that. Thank for very much for the detailed instructions.

The next step, and this is one that I have not seen covered elsewhere (the other thread is pick up via POP, whereas I need a SMTP push), is how do we now tell Mercury to forward all of the mail that it receives for that domain mail box.

-Chris

Ok, I appear to have done that. Thank for very much for the detailed instructions.The next step, and this is one that I have not seen covered elsewhere (the other thread is pick up via POP, whereas I need a SMTP push), is how do we now tell Mercury to forward all of the mail that it receives for that domain mail box.-Chris&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history