|
|
You're in the
iis smtp nntp
group:WebServer 2003 domain relay settings
iis smtp nntp:
Previously running with Win Server 2000 IIS SMTP as a domain controler default settings and all working great. Have now decommissioned the W2k Server box and set-up the WebServer 2003 in its place. The IP Address is on the same range, but is now part of a (WORK) Workgroup; The two differences are 1) the server is now in a workgroup and 2) is now using CDO in place of CDONTS. The asp scripts are working just fine Queing up the emails. but have an event for each to/cc that server has attempted to send to Events log :- Event ID: 4006 Message delivery to the host '72.14.205.83' failed while delivering to the remote domain 'googlemail.com' for the following reason: The remote server did not respond to a connection attempt. And an automatically generated Delivery Status Notification appears in the smtp queue. ' Unable to deliver message to the following recipients, due to being unable to connect successfully to the destination mail server. <username>@googlemail.com ' I believe this is a DNS setting as telnet is hit and miss connecting up to smtp servers or has my IP range been spam blocked? any help much appreciated.
[quoted text, click to view]
> Previously running with Win Server 2000 IIS SMTP as a domain > controler default settings and all working great. Have now > decommissioned the W2k Server box and set-up the WebServer 2003 in > its place. The IP Address is on the same range, but is now part of a > (WORK) Workgroup; The two differences are 1) the server is now in a > workgroup and 2) is now using CDO in place of CDONTS. And the server has a different IP address. Does this IP address have a PTR record? Is it allowed to make outbound connections to destination TCP port 25? [quoted text, click to view] > I believe this is a DNS setting as telnet is hit and miss connecting > up to smtp servers... Telnet doesn't use DNS unless you tell it to (by connecting to a hostname instead of an IP). If you run NSLOOKUPs against the mailserver's configured DNS server -- run from the mailserver itself -- can you get MX records back for a range of sample domains (google, msn, yahoo, et al.)? For each sample MX record, can you start an outbound telnet session, via IP, to TCP port 25? [quoted text, click to view] > ... or has my IP range been spam blocked? www.dnsstuff.com can help you find that out. If every single e-mail is failing, though, this will not be due to public blacklists (unless you coincidentally only send to a few domains). --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc.
Thanks Sandy,
The IP address is allowed to make outbound connections via port 25 through the firewalls. I can also ping googlemail.com which returns ip address of 66.249.91.83. so my isp DNS lookups are working. telnet connection fails up to 'googlemail.com' port '25' / '645'. But telnet connections up to 'smtp.gmail.com' port '645' works fine. (so DNS is looking up correctly) Which others should I try? searching on www.dnsstuff.com my ip address is not blocked on any lists. (Although the host I have registered my domain with has been.). So how do you alter the MX records in windows server 2003 web edition? Can not find any setting on the Web Edition? Thanks [quoted text, click to view] "Sanford Whiteman" wrote:
> > Previously running with Win Server 2000 IIS SMTP as a domain > > controler default settings and all working great. Have now > > decommissioned the W2k Server box and set-up the WebServer 2003 in > > its place. The IP Address is on the same range, but is now part of a > > (WORK) Workgroup; The two differences are 1) the server is now in a > > workgroup and 2) is now using CDO in place of CDONTS. > > And the server has a different IP address. Does this IP address have a > PTR record? Is it allowed to make outbound connections to destination > TCP port 25? > > > I believe this is a DNS setting as telnet is hit and miss connecting > > up to smtp servers... > > Telnet doesn't use DNS unless you tell it to (by connecting to a > hostname instead of an IP). If you run NSLOOKUPs against the > mailserver's configured DNS server -- run from the mailserver itself > -- can you get MX records back for a range of sample domains (google, > msn, yahoo, et al.)? > > For each sample MX record, can you start an outbound telnet session, > via IP, to TCP port 25? > > > ... or has my IP range been spam blocked? > > www.dnsstuff.com can help you find that out. If every single e-mail is > failing, though, this will not be due to public blacklists (unless you > coincidentally only send to a few domains). > > --Sandy > > > > ------------------------------------ > Sanford Whiteman, Chief Technologist > Broadleaf Systems, a division of > Cypress Integrated Systems, Inc. > ------------------------------------
[quoted text, click to view]
> so my isp DNS lookups are working. Actually, you haven't shown me a successful MX record lookup. But let us assume you can get the MX records for gmail.com (here is one sample set of records at this point in time from my location). gmail.com MX preference =3D 50, mail exchanger =3D gsmtp183.google= ..com gmail.com MX preference =3D 5, mail exchanger =3D = gmail-smtp-in.l.google.com gmail.com MX preference =3D 10, mail exchanger =3D = alt1.gmail-smtp-in.l.google ..com gmail.com MX preference =3D 10, mail exchanger =3D = alt2.gmail-smtp-in.l.google ..com gmail.com MX preference =3D 50, mail exchanger =3D gsmtp163.google= ..com [quoted text, click to view] > But telnet connections up to 'smtp.gmail.com' port '645' works fine. Based on these records, why would you be checking outbound connections to smtp.gmail.com? Why would you be checking, or caring about, connections to TCP 645, when your mailserver communicates on TCP 25 to remote domains? You have to stay focused on hand-replicating what your mailserver will do automatically, and not straying into other areas that don't actually bear on the problem. [quoted text, click to view] > So how do you alter the MX records in windows server 2003 web > edition? Alter the MX records? MX records are set by the hostmaster of a remote domain; they tell the outside world which hosts accept mail from the public Net for delivery to that domain. In kind, *your* MX records are used for incoming mail to your domain. You manage them wherever your DNS is served. The mailserver box would only be involved with the maintenance of your public DNS records if it *also* happens to be an authoritative nameserver for your domain. Can I ask you again whether your mailserver has a Reverse DNS entry for its public IP, and whether that hostname has a corresponding A record pointing back to the public IP? --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc.
Can we go over the set-up again.
The smtp server is now not part of a domain, it is sitting in a Workgroup. There is no local DNS server (as Web Edition does not include this) so I am using my ISP DNS servers. There has been no change to the external set-up. The only change was decommissioning the Windows 2000 Server (The PDC) and setting up the Server 2003 Web Edition onto a new IP Address and the firewalls nat redirecting to this server. The domain name DNS A record is pointing to my IP address, which the firewall is allowing and directing TCP/IP through on the smtp server. As for the Reverse DNS lookup, In the Advanced delivery the 'Perform Reverse DNS lookup' is Ticked. but in 'Relay' is by IP address list only and 127.0.0.1 is set (not by Domain). On using 'nslookup -type=MX gmail.com' am only receiving IP: '212.23.8.1' which I believe is the ISP dns server address. Also, when using .net 2 systems the emails are working correctly (using System.Web.Mail.SmtpMail.Send(msg); ). Also, the smtp log is hit and miss. Only records an entry when using the following asp code:- [code] on error resume next sch = "http://schemas.microsoft.com/cdo/configuration/" Set cdoConfig = CreateObject("CDO.Configuration") With cdoConfig.Fields .Item(sch & "sendusing") = 2 ' cdoSendUsingPort .Item(sch & "smtpserver") = "SERVER_IP_ADDRESS" .update End With Set cdoMessage = CreateObject("CDO.Message") With cdoMessage Set .Configuration = cdoConfig .From = "user" .To = "EMAIL-ADDRESS" .Subject = "CDO Message" .TextBody = "CDO.Message Body Text" .Send End With Set cdoMessage = Nothing Set cdoConfig = Nothing [/code] This fails to record a log entry [code] Set m = CreateObject("CDO.Message") m.From = "USERNAME" m.To = "EMAIL-ADDRESS" m.Cc = "EMAIL-ADDRESS" m.Bcc = "EMAIL-ADDRESS" m.Subject = "FeedBack Entered on web site" m.HtmlBody = sHTML On Error Resume Next m.send Set m = Nothing [/code] Thanks [quoted text, click to view] "Sanford Whiteman" wrote:
> > so my isp DNS lookups are working. > > Actually, you haven't shown me a successful MX record lookup. But let > us assume you can get the MX records for gmail.com (here is one sample > set of records at this point in time from my location). > > gmail.com MX preference = 50, mail exchanger = gsmtp183.google..com > gmail.com MX preference = 5, mail exchanger = > gmail-smtp-in.l.google.com > gmail.com MX preference = 10, mail exchanger = > alt1.gmail-smtp-in.l.google > ..com > gmail.com MX preference = 10, mail exchanger = > alt2.gmail-smtp-in.l.google > ..com > gmail.com MX preference = 50, mail exchanger = gsmtp163.google..com > > > But telnet connections up to 'smtp.gmail.com' port '645' works fine. > > Based on these records, why would you be checking outbound connections > to smtp.gmail.com? > > Why would you be checking, or caring about, connections to TCP 645, > when your mailserver communicates on TCP 25 to remote domains? > > You have to stay focused on hand-replicating what your mailserver will > do automatically, and not straying into other areas that don't > actually bear on the problem. > > > So how do you alter the MX records in windows server 2003 web > > edition? > > Alter the MX records? MX records are set by the hostmaster of a remote > domain; they tell the outside world which hosts accept mail from the > public Net for delivery to that domain. > > In kind, *your* MX records are used for incoming mail to your domain. > You manage them wherever your DNS is served. The mailserver box would > only be involved with the maintenance of your public DNS records if it > *also* happens to be an authoritative nameserver for your domain. > > Can I ask you again whether your mailserver has a Reverse DNS entry > for its public IP, and whether that hostname has a corresponding A > record pointing back to the public IP? > > --Sandy > > > > ------------------------------------ > Sanford Whiteman, Chief Technologist > Broadleaf Systems, a division of > Cypress Integrated Systems, Inc. > ------------------------------------
Results from cmd run :-
Server: dns.hq.svc.zen.net.uk Address: 212.23.3.100 Non-authoritative answer: gmail.com MX preference = 50, mail exchanger = gsmtp163.google.com gmail.com MX preference = 50, mail exchanger = gsmtp183.google.com gmail.com MX preference = 5, mail exchanger = gmail-smtp-in.l.google.com gmail.com MX preference = 10, mail exchanger = alt1.gmail-smtp-in.l.google ..com gmail.com MX preference = 10, mail exchanger = alt2.gmail-smtp-in.l.google ..com gmail.com nameserver = ns1.google.com gmail.com nameserver = ns2.google.com gmail.com nameserver = ns3.google.com gmail.com nameserver = ns4.google.com gmail-smtp-in.l.google.com internet address = 64.233.183.114 gmail-smtp-in.l.google.com internet address = 64.233.183.27 alt1.gmail-smtp-in.l.google.com internet address = 209.85.199.114 alt1.gmail-smtp-in.l.google.com internet address = 209.85.199.27 alt2.gmail-smtp-in.l.google.com internet address = 72.14.247.27 gsmtp163.google.com internet address = 64.233.163.27 gsmtp183.google.com internet address = 64.233.183.27 ns1.google.com internet address = 216.239.32.10 ns2.google.com internet address = 216.239.34.10 ns3.google.com internet address = 216.239.36.10 ns4.google.com internet address = 216.239.38.10' ' Thanks [quoted text, click to view] "Sanford Whiteman" wrote:
> > On using 'nslookup -type=MX gmail.com' am only receiving IP: '212.23..8.1' > > which I believe is the ISP dns server address. > > Run > > nslookup -q=mx gmail.com > > from the mailserver. Post the output. > > --Sandy > > > ------------------------------------ > Sanford Whiteman, Chief Technologist > Broadleaf Systems, a division of > Cypress Integrated Systems, Inc. > ------------------------------------
[quoted text, click to view]
> On using 'nslookup -type=3DMX gmail.com' am only receiving IP: '212.23= ..8.1' > which I believe is the ISP dns server address. Run nslookup -q=3Dmx gmail.com from the mailserver. Post the output. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc.
Hi Sandy,
It is now working.!! Coincidently, at the same time of the upgrade my ISP had changed its DNS server address (from '212.23.8.1' to 212.23.6.100. Without emailing me, as they have decided to post this on their web site and hope everyone uses it as a portal:-( All up and running now, thanks for your help. Kesmond [quoted text, click to view] "kesmond" wrote:
> Results from cmd run :- > > Server: dns.hq.svc.zen.net.uk > Address: 212.23.3.100 > > Non-authoritative answer: > gmail.com MX preference = 50, mail exchanger = gsmtp163.google.com > gmail.com MX preference = 50, mail exchanger = gsmtp183.google.com > gmail.com MX preference = 5, mail exchanger = gmail-smtp-in.l.google.com > gmail.com MX preference = 10, mail exchanger = > alt1.gmail-smtp-in.l.google > .com > gmail.com MX preference = 10, mail exchanger = > alt2.gmail-smtp-in.l.google > .com > > gmail.com nameserver = ns1.google.com > gmail.com nameserver = ns2.google.com > gmail.com nameserver = ns3.google.com > gmail.com nameserver = ns4.google.com > gmail-smtp-in.l.google.com internet address = 64.233.183.114 > gmail-smtp-in.l.google.com internet address = 64.233.183.27 > alt1.gmail-smtp-in.l.google.com internet address = 209.85.199.114 > alt1.gmail-smtp-in.l.google.com internet address = 209.85.199.27 > alt2.gmail-smtp-in.l.google.com internet address = 72.14.247.27 > gsmtp163.google.com internet address = 64.233.163.27 > gsmtp183.google.com internet address = 64.233.183.27 > ns1.google.com internet address = 216.239.32.10 > ns2.google.com internet address = 216.239.34.10 > ns3.google.com internet address = 216.239.36.10 > ns4.google.com internet address = 216.239.38.10' > ' > > Thanks > > > "Sanford Whiteman" wrote: > > > > On using 'nslookup -type=MX gmail.com' am only receiving IP: '212.23..8.1' > > > which I believe is the ISP dns server address. > > > > Run > > > > nslookup -q=mx gmail.com > > > > from the mailserver. Post the output. > > > > --Sandy > > > > > > ------------------------------------ > > Sanford Whiteman, Chief Technologist > > Broadleaf Systems, a division of > > Cypress Integrated Systems, Inc. > > ------------------------------------
[quoted text, click to view]
> Coincidently, at the same time of the upgrade my ISP had changed its > DNS server address (from '212.23.8.1' to 212.23.6.100. Without > emailing me, as they have decided to post this on their web site and > hope everyone uses it as a portal:-( That explains why I never saw proof of correct MX resolution. Glad you found out about the change. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |