The problem configuration did include 2 DNS servers, assigned by IP name
(the same two DNS servers that I have set-up in the IP configuration on my
local W2K machine), and the first thing that I tried was upping the MX
timeout from 30 to 90 seconds. So it sounds like all of your suggestions
were true when the problem was occurring.
I removed those two DNS servers and replaced them with 2 others, and that
seemed to clear up the problem, but I still don't understand what was
causing the problem in the first place. I don't understand why there was
only a problem with that one domain.
Any other ideas?
Thanks,
Bob
-----Original Message-----
From: Howie Hamlin [mailto:[EMAIL PROTECTED]]
Sent: June 18, 2001 12:22 PM
To: inFusion Support List
Subject: Re: [iMS] Error resolving MX
I would make sure that I had the following configured:
1) At least two DNS Servers assigned by IP rather than CNAME
2) MX timeout of 30-60 seconds
Please let me know if this fixes the problem.
Regards,
Howie
----- Original Message -----
From: "Bob Silverberg" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Monday, June 18, 2001 12:15 PM
Subject: [iMS] Error resolving MX
> We seem to be having problems sending email to a particular domain from
our
> development server. I'm no email expert, so I don't really have any idea
> what's going on. Emails to other domains seem to go out OK, but when we
> send to one particular domain we get errors. Sometimes the emails get
> through eventually, and other times I get a failure message.
>
> I am using the same DNS's that are used by my local machine (which is on
the
> same internal network), and I can send email to the problem domain without
> any errors.
>
> As a test, I changed the DNS's to ones used on one of our co-located
> servers, and this seemed to resolve the problem, but I'm confused as to
what
> was going on.
>
> Here is some info in the log file about one of the problem emails:
>
> 06/18/2001 10:35:01 AM Added 1 file to queue.
> 06/18/2001 10:35:01 AM [004] Send mail start for C0C31334AF43E64190D3.mbx
> (Priority 5)
> 06/18/2001 10:36:02 AM [004] WARNING: Error resolving MX from server
> 209.250.128.6 for ilogic.com: TIMEOUT: Socket Read Timeout
> 06/18/2001 10:37:02 AM [004] WARNING: Error resolving MX from server
> 209.250.128.8 for ilogic.com: TIMEOUT: Socket Read Timeout
> 06/18/2001 10:37:02 AM [004] Connect to ilogic.com
> 06/18/2001 10:37:22 AM [004] WARNING: SOCKET ERROR: (Sock Connect) [10060]
> Connection timed out [ilogic.com] (ilogic.com)
> 06/18/2001 10:37:23 AM [004] Rescheduling C0C31334AF43E64190D3.mbx
> 06/18/2001 10:37:23 AM [004] Completed Processing
> 06/18/2001 10:37:26 AM [004] resecheduling:
> 20010618104723/649E8171D3820D47AD94_C0C31334AF43E64190D3.mail
>
> Any light you can shed on this issue would be greatly appreciated.
>
> Thanks,
> Bob
>
========================================================================
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/
========================================================================
========================================================================
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/
========================================================================
