I just checked and ces.globalc.org does not have an MX record.

Regards,

Howie

----- Original Message ----- 
From: <"Fournier>; <Don <[EMAIL PROTECTED]>>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Friday, November 16, 2001 5:29 PM
Subject: [iMS] MX errors.


> Howie,
> can you shed some light on this.....   
> when I send an email from the IMS server to an external server the external
> server gets the message just fine.
> 
> When I send a message to one of the domains on the IMS server it doesn't go
> through.
> 
> the following is an excerpt of the post log for the message.  
> 11/16/2001 03:07:10 PM [001] WARNING: Error resolving MX from server
> 199.104.212.131 for ces.globalc.org: TIMEOUT: Socket Read Timeout
> 11/16/2001 03:07:10 PM [001] WARNING: No MX found from server
> 199.104.212.130 for ces.globalc.org: 
> 11/16/2001 03:07:10 PM [001] WARNING: MX Lookup Error (no MX for
> ces.globalc.org). Aborting delivery.
> 11/16/2001 03:07:10 PM [001] POSTSTATUS:
> [EMAIL PROTECTED]
> 11/16/2001 03:07:10 PM [001] POSTSTATUS:
> [EMAIL PROTECTED]
> 11/16/2001 03:07:10 PM [001] Returning undeliverable mail to
> [EMAIL PROTECTED]
> 11/16/2001 03:07:10 PM [001] Completed Processing
> 
> it say's there's no MX for ces.globalc.org. I checked 199.104.212.130 with
> nslookup and it's showing a MX record for that server (it looks ok).
> 
> any ideas??????????? 
> 
> 
> Donald Fournier
> Webmaster -  Global Connections
> Email: [EMAIL PROTECTED]
> PH: 602 - 764-1015
> 4502 N. Central Avenue
> Phoenix, Arizona 85012
> 
==^=======================================================
     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]
==^=======================================================


Reply via email to