Thanks so much for the help, I can now confirm I have a working system supporting multiple domains. Just got to get squirrel mail or similar inplace and tie up the loose ends with security and access. Then its apache, php and mysql.
Hi there, I'm new to Mercury Mail and web hosting in general so please excuse my lack of knowledge. I currently run a re-seller account using a linux backend. I am wanting to move all the services I provide onto a home box as I now have a long awaited static IP. I have the MX record setup and have a single instance of Mercury Mail setup and accepting mail. I have done some digging on the forum and found that I need to setup multiple instances of MMail and one of the options is to use WSMTPEx to port mail between the instances. I was wondering if there are any step by step guides on how to do this or if somebody could help guide me through this. Thanks in advance for any help. I would also like to add something like squirrel mail to allow users to access email over the web, again was wondering if anybody had done this.
Thanks Rob
There is some information on how to set up WSMTPX with multiple instances of Mercury in this thread:
http://community.pmail.com/forums/thread/14135.aspx
There is plenty of information about how to set up SquirrelMail on their website, http://squirrelmail.org/. On the Mercury end you will of course have to have the IMAP module installed.
/Rolf
> Hi there, I'm new to Mercury Mail and web hosting in general so please
> excuse my lack of knowledge. I currently run a re-seller account using
> a Linux backend. I am wanting to move all the services I provide onto
> a home box as I now have a long awaited static IP. I have the MX
> record setup and have a single instance of Mercury Mail setup and
> accepting mail. I have done some digging on the forum and found that I
> need to setup multiple instances of MMail and one of the options is to
> use WSMTPEx to port mail between the instances.
I have setup the to forward my mail to the internal mail servers from my gateway Mercury system. The domains merwin-tstephenson.com, ubunto-tstephenson.com, linux-tstephenson.com, merwin.dyndns.org, novell-tstephenson.com, xampp.from-ca.com are set to the same IP address in the DNS. Some of the domains I use WSMTPEx, some of the domains I use a daemon mercfwd. If the Mercury system can receive on port 25 I use the daemon; if I use a separate port I use WSMTPEx. Here's is the domains section of the gateway server.
[Domains]
stephens: stephens
stephens: [209.128.94.2]
stephens: mail.tstephenson.com
stephens: tstephenson.com
stephens: [192.168.1.2]
dm=merwin: merwin-tstephenson.com
dm=ubunto: ubunto-tstephenson.com
dm=ubunto: linux-tstephenson.com
dm=dyndns: dyndns-tstephenson.dyndns.org
dm=merwin: merwin.dyndns.org
daemon:c:\mercury\mercfwd.dll;[192.168.1.3]: novell-tstephenson.com
daemon:c:\mercury\mercfwd.dll;[192.168.1.153]: xampp.from-ca.com
The forwarding with the daemon is simple, you just tell the daemon to use the correct internal IP address and all mail is forwarded to that IP address.
For the WSMTPEx I use the following INI file.
# Configuration file for WSMTPEx
# At the beginning, it is recommended to use program menu Option for configuration.
# When you change this file, WSMTPEx will automatically update its
# config in next cycle time.
# You can rename this tool, but name of following section must remain [WSMTPEx]
[WSMTPEx]
Version=0.21
# Number of seconds to delay between searches for emails
LoopDelay=30
# Folder, under which is most of user's mailboxes
UserFolder=c:\pmail\mail\
Domains=3
LogName=c:\wsmtp\WSMTPEx.log
MailBoxes=3
Badmails=c:\pmail\mail\BadMail\
# Domains must be numbered from 1 to Domains
[Domains]
# Users email address domain part
Domain1=linux-tstephenson.com
# where to send all mail for domain (if port is not specified, default 25 is used)
SMTPServer1=192.168.1.4:8025
Domain2=merwin.dyndns.org
SMTPServer2=192.168.1.5:8025
Domain3=dyndns-tstephenson.dyndns.org
SMTPServer3=192.168.1.5:8025
# Users must be numbered from 1 to MailBoxes
# User parameters are: "name";"folder";"domain"
[Mailboxes]
mailbox1=dm:merwin;merwin;2
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mailbox2=dm:ubunto;ubunto;1
Mailbox3=dm:dyndns;dyndns;3
> I was wondering if there are any step by step guides on how to do this
> or if somebody could help guide me through this. Thanks in advance for
> any help. I would also like to add something like squirrel mail to
> allow users to access email over the web, again was wondering if anybody
> had done this.
SquirrelMail just talks to Mercury/32 via IMAP4 and I installed SquirrelMail using the instructions of the Apache web server package I was using. A bit tricky but not rocket science.
Thanks for the advice, much appreciated. Just a thought, if I'm serving remote users with the above setup do I need to change ports for SMTP, POP3 and IMAP so that none of the instances clash? Just to run the process past the experts:
1. I have a single host running behind a NAT router, I need to setup port forwarding on router for external ip to internal host for all services e.g. pop3, smtp, http
2. Setup a gateway instance of Mercury Mail, adding following modules MercuryE, MercuryP, MercuryD, MercuryI, MercuryX using default ports, add domains and mailboxs
3. Setup domain mail instances with MercuryE, MercuryP, MercuryI, MercuryX, change ports for the services so no conflicts with other instances
That's right, you will need to use different ports for email services if running several instances of Mercury on the same machine. What modules to use in each instance will of course depend on the role. MercuryX should be used if you plan to switch Mercury on and off using a time schedule.
/Rolf
[quote user="Rolf Lindby"]
That's right, you will need to use different ports for email services if running several instances of Mercury on the same machine. What modules to use in each instance will of course depend on the role. MercuryX should be used if you plan to switch Mercury on and off using a time schedule.
/Rolf
[/quote]
or instead of multiple ports, use multiple IPs on the same adapter.
