Re: [iMS] Continued: PermFaileds that really are'nt fails

[Howie Hamlin]

OK - in the first instance your DNS server was not available so iMS used the "MX From Address" feature to send the mail.  It found an SMTP Server that way but that server would not accept the mail.  Later on, the MX lookup succeeded and the mail was delivered.  What I would do is ether add additional DNS Servers to the iMS configuration or turn off the MX From Address feature.   HTH,   Howie ----- Original Message ----- From: Lionel Richthofen To: inFusion Support List Sent: Tuesday, May 22, 2001 4:49 PM Subject: Re: [iMS] Continued: PermFaileds that really are'nt fails I understand what you need now!   Here are all transactions in the log related to one instance ([EMAIL PROTECTED]) :   Failed Delivery 05/21/2001 04:45:59 PM [031] Send mail start for CD9849EED04AD5118745.mbx (Priority 5) 05/21/2001 04:46:00 PM [031] WARNING: Error resolving MX from server 12.104.36.7 for wt.net: SOCKET ERROR: (Sock Close) [10038] Socket operation on non-socket 05/21/2001 04:46:00 PM [031] Connect to wt.net 05/21/2001 04:46:27 PM [031] Sending mail to wt.net 05/21/2001 04:46:28 PM [031] WARNING: RCPT failed (<[EMAIL PROTECTED]>: 550 <[EMAIL PROTECTED]>... 5.7.1 Relaying denied 05/21/2001 04:46:28 PM [031] Returning undeliverable mail to <[EMAIL PROTECTED]> 05/21/2001 04:46:28 PM [031] WARNING: Application server response: 05/21/2001 04:46:28 PM [031] WARNING: Template=C:\iMS\Domains\REPORTPOSTSTATUS.cfm 05/21/2001 04:46:28 PM [031] WARNING: Content-type: text/html 05/21/2001 04:46:28 PM [031] WARNING: Page-Completion-Status: Normal 05/21/2001 04:46:28 PM [031] Completed Processing   Successful Delivery 05/22/2001 02:20:35 PM [004] Send mail start for 339D49EED04AD5118745.mbx (Priority 5) 05/22/2001 02:20:35 PM [004] Connect to mp.hou.wt.net 05/22/2001 02:20:35 PM [004] Sending mail to mp.hou.wt.net 05/22/2001 02:20:36 PM [004] 339D49EED04AD5118745.mbx sent successfully to [EMAIL PROTECTED] from <[EMAIL PROTECTED]> 5024