How to setup a remote mail spool?

[Walter Marchuk]

Here's our sendmail.mc file for our queue server, change it around to suit 
your needs:
<snip>
divert(0)dnl
OSTYPE(linux)dnl
DOMAIN(generic)dnl

# Access Features
FEATURE(access_db)dnl
FEATURE(relay_entire_domain)dnl
FEATURE(`relay_based_on_MX')dnl

# Misc Features
FEATURE(use_cw_file)dnl
FEATURE(nocanonify)dnl
FEATURE(no_default_msa)dnl

# Gateway
undefine(`ALIAS_FILE')dnl
define(`confFORWARD_PATH', `')dnl
define(`MAIL_HUB', `spoolserver')dnl
define(`LOCAL_RELAY', `spoolserver')dnl
define(`SMART_HOST', `spoolserver')dnl
define(`LOCAL_USER', `root')dnl

# System
DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl
MAILER(local)dnl
MAILER(smtp)dnl

# Settings
define(`confMIN_QUEUE_AGE', `10m')dnl
define(`confQUEUE_LA', `999')dnl
define(`confREFUSE_LA', `999')dnl
define(`confMAX_DAEMON_CHILDREN', `24')dnl
define(`confSMTP_LOGIN_MSG', `Mail Gateway')dnl
define(`confPRIVACY_FLAGS', `goaway restrictmailq restrictqrun')dnl

# SSL
define(`CERT_DIR', `MAIL_SETTINGS_DIR`'certs')dnl
define(`confCACERT_PATH', `CERT_DIR')dnl
define(`confCACERT', `CERT_DIR/ca-bundle.crt')dnl
define(`confSERVER_CERT', `CERT_DIR/cert.pem')dnl
define(`confSERVER_KEY', `CERT_DIR/key.pem')dnl
</snip>

Walter.

On Wed, 22 Jan 2003, Richard Lotz wrote:

> 
> On Wednesday, Jan 22, 2003, at 16:12 US/Pacific, Walter Marchuk wrote:
> 
> > Having multiple mail spool servers is not very recommended unless 
> > there's
> > a very urgent need.  The main issue is with file locking.  If you do a
> > search for "file locking sendmail" on google, you'll see why.  We at EE
> > department have 2 mail spool servers connected together through a SCSI
> > interface with the spool disks in the middle.  The 2 mail servers
> > communicate with each other through heartbeat and if the primary mail
> > server goes down, the backup server takes over.  The heartbeat 
> > solution is
> > for redundancy, if you are looking for load balancing then you should
> > consider having mail gateway servers that queue mail.
> 
> Ahh, no, see I'm looking to setup a remote system to queue incoming 
> mail while the primary server is down.  Then, once the primary server 
> comes back up the queued mail will be delivered back to the primary.  
> The second server shouldn't need to look at an alias file or deliver 
> mail to any local user (that it is being a backup queue for).
> 
> In reality it's not important since most mail will be queued for 
> several hours if the remote mailserver is down.  I'm just looking to 
> add a bit of redundancy to my setup...
> 
> thanks,
> 
> -richard
> 
> --
> Richard Lotz
> GPG Key:     http://students.washington.edu/rlotz/key.txt
> Fingerprint: 6BD7 C584 7DDC 43FD F0D4  87AB 5A8F 89D5 B3CC 9517
>