[TriLUG] OT: DSL for SOHO in Chapel Hill

[Jon Carnes]

When you setup a mail server to act as a secondary you basically just
turn on relaying for that domain.  Mail for the domain then comes in to
the Secondary server and is accepted.  That server then continuously
tries to deliver the cached mail to the Primary (well every 4 hours).

Also, it is worth noting that mail is sent via SMTP and can end up
anywhere - in a cache, spool, NFS folder, database, etc.

Mail is downloaded via any number of protocols, including POP and IMAP. 
You can have multiple SMTP servers all feeding mail to a database server
or a centralized NFS server, then have multiple POP/IMAP servers that
front-end for that database or NFS server.  Some larger organizations do
mail this way.  There is no association between the smtp and the pop
servers - they are different servers.

Jon Carnes

On Tue, 2004-01-27 at 14:49, Carl Lindner wrote:
> Actually, if you guys don't mind me jumping into this thread.  I'm 
> curious that if you do have multiple MX records for email defined.... 
> how exactly do you go about synchronizing them without the user having 
> to pop/imap to multiple machines to retrieve their email from secondary 
> backup servers?
> 
> thanks
> carl
> 
> Magnus Hedemark wrote:
> > On 27 Jan 2004, Jon Carnes wrote:
> > 
> > 
> >>I knew that someone was going to post this, and I have to respectfully
> >>respond: [bleep]
> > 
> > 
> > Come on now, Jon, we have invited kids here.  Keep it clean.
> > 
> > 
> >>On a /29 network there is little if any need for a remote secondary
> >>DNS. 
> > 
> > 
> > So how do you expect mail to get sent to your backup MX?
> > 
> > --Magnus
> >