Space Monkey, Both approaches are common place. In the even of an unavailable MTA, the email engine will log the failed connect attempt in the email error logs form and will retry on the next interval; the messages queue up if they are not handed off to the MTA. As for defining an alternate MTA, this would require something outside of Remedy, like a clustered MTA. Not knowledgeable enough on SMTP auth to answer that part of your question.
Axton Grams On Mon, Sep 22, 2008 at 3:21 PM, spacegoose <[EMAIL PROTECTED]> wrote: > Is it recommended to use a localhost or alternate MTA to the built in > Remedy engine for handling mail? > > I'm wondering how the Remedy mail engine handles failed connections to > the outgoing mail server? Does it retry? > > Can the remedy mail handler/engine be configured to do SMTP AUTH? > > I am faced with the problem of mail building up in the queue which is > affecting the ticketing work flow and communication to clients. > > I believe this can be helped by telling remedy to use an alternate MTA > - like a localhost listening Sendmail. > > Is this common practice? > > Thanks, > SG > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
