----- Original Message -----
From: "Max Paperno" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 2:48 PM
Subject: Re: [iMS] iMS2.1 & smart delivery
<<<<<
Howie,
Thanks for the response. How can I tell why the Smart Delivery is failing? It says
it fails and keeps re-sending the mail even
thought it is being delivered on each attempt. There are no errors anywhere that I
can see. ???
>>>>
You mentioned that you turned on debug logging, I think. Could you send me that
portion of the log file privately?
<<<<
>I think that Smart Delivery always looked for result=accept but I may be wrong. At
>any rate, best practice is to include
>result=accept (or reject, etc.) in any iMS template.
Smart delivery never cared about a result string, in fact you had to guard against
non-delivery within the SD template because POST
would just hand off the transaction w/out checking that it succeeded. But in any
case, I can see the result=accept in my output
string, so that's not it.
>>>>
I just looked at the code and the POST Server should be looking for the result=accept.
Could you send me the entire error ("Error
sending locally to ...")?
<<<<
As for the DNS, here's why I think so. I'm testing using a domain name I made up
(private.wdg), and I run a local DNS server on my
LAN so that private.wdg domains can be resolved. The system DNS settings on the test
server point to 1) a real DNS server on the
'net and 2) my local DNS server that serves private.wdg. The DNS setting in iMS was
always pointed to the local DNS. This used to
work fine pre v2.1. When I tried 2.1, POST at first reported no DNS entry for
"private.wdg". In fact I sniffed some traffic on the
WAN and I see iMS is asking my remote DNS server to resolve the host name, even though
that one is not specified in iMS settings.
The remote server cannot resolve "private.wdg" so POST reported an error (it did not
go on to check the local DNS at all). Then I
switched the order in which the DNS servers are specified in the system settings (so
my local one comes first). iMS then could look
up the private.wdg domain w/out problem. The only explanation I can see for that is
that iMS is (somewhat) using the system
settings, but perhaps there's something else going on?
>>>>
Weird. When iMS POST starts it gives a list of DNS servers in order of
preference...does this look right?
Regards,
Howie
<<<<
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/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/
Note: You are subscribed as [email protected]
==^=======================================================
