Hello,
we released new product: XMail-SYNC. It's good when you want XMail to act as backup mail exchanger for other XMail server. XMail-SYNC does automatic synchronization - if you would create new domain on master server, the slave one will act as backup mx for it. If you delete it, will be deleted on slave server too.
More info you can read at http://www.altair2000.net/software/xmail-sync/. You may also download the program there. As usual, is free including source code, licensed under terms of GNU General Public License.
-- Michal Altair Valasek
| QUOTE |
The good thing on SMTP protocol is that allows to have multiple mail exchangers for single Internet domain. This can be used for load balancing or more often as backup. When primary mail exchanger is out of order, message is sent using the next server, with higher priority.
Backup (secondary etc.) mail exchanger is basically any server, which is available to accept mail for target domain, hold it for a while and then forward it to primary MX, when its going online.
In terms of XMail, backup MX is server having defined the target domain as custdomain with smtp command.
But if you have more than few domains and they are changing, itr maintenance of that server real pain in ass. So I wrote XMail-SYNC, which makes this maintenance fully automatic.
Furthermore, there is no need for master server to have real administrative access to slave server (ctrl account here) and no critical communications is between that server. It makes use of XMail-SYNC possible even between two servers of different companies, bound by some form of agreement.
This application is written under Microsoft .NET Framework and does not require any 3rd party components. All required components besides of operating system are free.
The software is built from two independent pieces. Master part (master.exe) is installed on master server (primary MX). When is run, creates at specified location XML file which lists all domains hosted on that server.
Then you must transfer that file to server. You can physivcally transfer the file to slave server (using Windows sharing or FTP, for example) and then point to it locally. Or you can publish the file on master server using WWW and then load it from slave using HTTP URL.
Second part (slave.exe) is running on slave (backup MX) server. This program takes the remote XML file and changes XMail configuration to accept all remote domains as custdomains and perform SMTP delivery on them. The slave server is maintaining its own domain database (is stored in database.xml in its program folder) to allow synchronization with multiple sources and do not modify domains added by anything else than XMail-SYNC. Therefore, all domains added other way than via XMail-SYNC would remain untouched.
|
|