My concern with an approach like that is that it multiplies
administration. If I have 3 front-end servers, I then have 3 places to go
to administer frozen mail, 3 efficiency reports to analyze, etc.
For me it's also not so simple, because I don't have one MX domain, I have
thousands. For this I'd rather let the Alteon load-balancer handle
failover instead of doing via MX.
And most importantly, if one of the front-ends goes down then any mail in
its spool will not get processed until that server is restored to
operation.
On Sat, 10 Aug 2002, Suresh Ramasubramanian wrote:
> (bazyar@???) [Saturday, August 10, 2002 1:06 PM]:
>
> > What I am trying to figure out is how to handle the mail spool.
> > Mailboxes are no problem, we are already using maildir for them. But
> > can the spool be stored on the NFS server and shared by the exim
> > daemons running on the front-end boxes?
>
> No. File locking over NFS is HELL.
>
> Have multiple mail spools (each with split spool directories) running on
> multiple MXs.
>
> Do something like
>
> $ dig hotmail.com MX
>
> for a hint.
>
> -srs
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>
--
Jawaid Bazyar | Affordable WWW & Internet Solutions
foreThought.net | for Small Business
jawaid.bazyar@??? | 910 16th Street, #1220 (303) 228-0070
--The Future is Now!-- | Denver, CO 80202 (303) 228-0077 fax
