William Hue writes: > "Bill Michell" wrote: >> >> You have only made a half-hearted attempt at a distributed system > here. >> There would appear to be two possible solutions: >> 1) Tell mail2 that it is merely a backup MX for the domain, not the > primary. >> Then it will automatically forward messages when the primary comes > back up - >> but users will not be able to connect to it to download messages >> 2) Go for a proper mail cluster. Essentially, you want to set up a > common >> mail store area, either by sharing the file system, or else by > replicating >> content between them. >> >> The first is much simpler. The second is more resilient, but will take > a >> significant effort. >> >> Which would you prefer? > > I want to do #1, mostly due to the traffic that #2 would generate (the > two > servers are geographically separated by about 1500 miles). I apologize > for > being unclear in my original post; what I'd like to be able to do is > have > store-and-forward, but also allow clients to connect for messages in > case the > primary server is down for a long time. > This is not trivial to set up - though I can think of several solutions. You probably want to fool your backup server into thinking that it is primary, and then have some automatic process (fetchmail?) periodically collect mail from the backup and deliver it to the primary. You need to be careful to avoid mail loops, particularly if the primary is down.
-- Bill Michell [EMAIL PROTECTED] (home) _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
