----- Original Message -----
From: "Max Paperno" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Saturday, December 09, 2000 11:08 AM
Subject: [iMS] What makes POST so "smart"?
>
> Hi,
>
> Now that the docs are out I still have a question on the POST "smart
delivery" feature. How exactly does POST know that the mail is local before
it sends it to the DATA (or whichever) template instead of the outgoing
queue? Also, second question I guess, what happens if the mail is rejected
after it's been "handed off" to the DATA template?
>
Here is the way it works:
Now, usually you don't really want local mail in the POST Server queue.
However, it is sometimes convenient to dump a bunch of addresses into the
POST Queue (a mailing list, for example). Now, assume that you have two
servers for your local mail: Server A and Server B (in order of MX priority
for your domain). You send a mail to a local account to the POST Server on
Server A.
- Server A picks up the mail
- Server A does an MX lookup and finds that the MX resolves to
ServerA.yourdomain.com and ServerB.yourdomain.com
- Server A now tries to send the mail to Server A and discovers that Server
A resolves to an IP adress on itself.
- Server A now uses the POST Smart Delivery feature instead of sending mail
via SMTP to itself.
If the delivery to that template fails then the POST Server will send the
mail to Server B via SMTP.
Now, remember, mail will not get into the POST Queue unless the SMTP Server
accepted it for external delivery or you have some process using CFX_iMSMail
or some other method to put the mail into the POST Queue. So, the only time
that Smart Delivery is needed is the second case.
HTH,
Howie
> Much thanks,
> -Max
>
========================================================================
This list server is Powered by iMS
'The Swiss Army Knife of Mail Servers'
--------------------------------------
To leave this list please complete the form at
http://www.CoolFusion.com/iMS.htm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================