Maintenance for Infusion Post Server SEWhen a mail server sends mail to
another server/domain there are several things that can happen
1) Remote server accepts the mail and delivers it to the recipient
2) Remote server cannot be contacted
3) Remote server temporarily rejects the mail (mailbox is full, for example)
4) Remote server rejects recipient as unknown
5) No MX for domain (invalid email address)
6) Remote server accepts mail but sends a deferred rejection notification
For the first situation we're done and nothing else needs to happen (normal
mail delivery). In the second case, the iMS server will requeue the mail
and try again later. For numbers 3-6 we need to create special processing
templates to handle these. Items 3-5 can be handled with a ReportPostStatus
template (you may want to ignore the third one since iMS will automatically
resend the mail later on). First, you need a ReportPostStatus template (you
can download one from
ftp://ftp.coolfusion.com/pub/ods/ims/reportpoststatus.zip). You will also
need to enable the permanent and/or temporary failure notifications in the
iMS POST settings.
The last situation is the most difficult to deal with. The remote server
has accepted the mail from the iMS server based simply on the domain of the
recipient - whether the actual email account exists or not. The remote
server will then defer failure notification to the sender of the mail. The
remote server will usually send the rejection notification in an email to
the sender of the mail (although most mail servers will send the
notification to an address that you specify in an "Errors-to" header in the
mail). At any rate, you have two choices as to where to send these error
notifications - to an account monitored by a person or to an automated
process. If you want to send the mail to an automated process then you need
the iMS SMTP Server (which is not included in the POST-SE or the iMS-SE
product). You cannot add the SMTP Server to the POST-SE 1.x server but you
can add the iMS SMTP Server to any iMS 2.0 server).
If you send the mail to an automated processor then it helps to have a
unique address for each recipient. Something like:
[EMAIL PROTECTED]
Then, whenever you receive a mail to any address that starts with "bounce"
you can parse the address for the intended recipient (replace the "=" or
whatever character you decide on with an "@").
HTH,
Howie
----- Original Message -----
From: Joe Pitera
To: inFusion Support List
Sent: Friday, April 20, 2001 9:49 AM
Subject: [iMS] Maintenance for Infusion Post Server SE
Hello,
I was looking for a way to monitor my emails being sent out. Right now I am
sending out around 12,000 emails daily, and am having problems monitoring
which ones are successful and which are not reaching their intended
destination. I can search through the log files, but this is a tedious
task. And I have about 4 users who state that they are not receiving their
mail. Is there something out there that will help me with this task?
Anything is appreciated.
Thanks,
<<...OLE_Obj...>>
Joseph Pitera
E-Mail: [EMAIL PROTECTED]
========================================================================
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/iMSSupport.cfm
Need an iMS Developer license? Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================
