[TriLUG] seeking advice for a bullet-proof mail server

[Tanner Lovelace]

Re-reading my message, I think perhaps I spoke a bit too strongly. 
The issue I was trying to raise is that of using the right tool for the job.
If you really want real-time communication, then you should use
a tool that will do that for you, rather than try to shoehorn something
in that isn't designed for that.  (i.e. don't use a screwdriver to pound in
a nail).  

Now, that granted, I understand that sometimes you must make do
with what you've been given.  But, just make sure your management
knows that e-mail was never designed to work this way and while it
may work ok the majority of the time, there could be instances where
it falls flat on it's face, and that's not your fault.

Good luck!

Cheers,
Tanner


On Fri, 05 Nov 2004 05:58:09 -0500, Brandon L. Newport
<bnewport at appws.com> wrote:
> Tanner is absolutely correct...the RFC for email talks about 48 hours if
> I remember correctly.
> 
> 
> 
> -brandon
> 
> On Fri, 2004-11-05 at 10:40 -0500, Tanner Lovelace wrote:
> > On Fri, 5 Nov 2004 10:34:18 -0500, Ryan Leathers
> > <ryan.leathers at globalknowledge.com> wrote:
> > >  Some number of the mail messages arriving will be the type that must
> > > be delivered in near real time.
> >
> > Then you shouldn't be using SMTP. Period.  SMTP was never meant to be a
> > real-time protocol.  If these are your requirements, you should look into using
> > something like Jabber instead, which is a real-time protocol (in the
> > sense you're
> > talking about).
> >
> > Cheers,
> > Tanner
> 
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>