Koozali.org: home of the SME Server

Master / Slave servers

Offline dehacked

  • *
  • 10
  • +0/-0
Master / Slave servers
« on: November 23, 2012, 02:03:46 PM »
I have a number of geographically disperse offices that get emails from my server. Due to intermittent connectivity issues I'm playing with the idea of putting a slave server in each of these locations so that users will at least perceive the mails to be working all the time. There is resilience in the network but limited automation so the idea is for the servers to catch up as soon as connectivity is manually restored. Not ideal, but this is Africa... I recall I saw SME having this ability some time back but I'm not able to find the documents. Am I mistaken or can someone please point me in the right direction?

Offline nicolatiana

  • *
  • 724
  • +0/-0
Re: Master / Slave servers
« Reply #1 on: November 23, 2012, 04:15:27 PM »
The first and simple idea is local Sme servers with fetchmail downloading mail from the main server (every 15', for example) and local clients getting mail from local servers via IMAP. Valid for both xDSL or dialup (dialup needs a server&gateway configuration and a RS232-not-pci modem).

http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter5#Configuring_the_Server_for_Server_and_Gateway_Mode_-_Dialup_Access

Nicola
« Last Edit: November 23, 2012, 04:22:24 PM by nicolatiana »
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia.

Offline janet

  • *****
  • 4,812
  • +0/-0
Re: Master / Slave servers
« Reply #2 on: November 24, 2012, 05:49:28 AM »
dehacked

I am not aware of any Master/Slave setups. You may be referring to the high availability howto from years ago, or perhaps the current LDAP implementation in sme8.

You can create standalone mail servers (based on sme) at each location.
Configure them with their own domain eg office1domain.com, office2domain.com, or a subset of your main domain eg office1.mydomain.com, office2.mydomain.com etc, or use free domains from dyndns etc.
On the main server you could have forwarding setup to deliver the main domain email to the subdomain mail servers eg user1@mydomain forwards to user1@mydomain (local), user2@mydomain forwards to user2@office2mydomain.com (remote) & so on. That way users can retain their original user@mydomain addresses, but of course all messages will be routed through the main server. Alternatively send direct to the subdomains, and rely on mail servers (external) to queue the messages for a few days.

Then just allow qmail to deliver the messages when the servers come on line. Qmail will keep trying for 7 days, before sending an undeliverable message to the sender.
Avoid fetchmail as much as possible.
« Last Edit: November 24, 2012, 06:06:43 AM by mary »
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.