| Groups | Blog | Home |
iis smtp nntp : Problem in sending mail from local SMTP service
I am using IIS/SMTP Service on Windows 2000 professional for sending email, it was working fine on Windows XP Professional and on this it is not giving any error message but In Event Viewer its giving follwing warning. 'Message delivery to the remote domain 'yahoo.com' failed for the following reason: An internal DNS error caused a failure to find the remote server.' I have allowed relay on this system. and also checked basic authentication. And message remains in queue. Please help me out. TIA
Hi
What do you mean dump question!!! In this newsgroup there are many topics posted askin the same question but no one has given proper solution. And about DNS name resolution, I am connected to interent thru DHCP. And when i specify DNS Server then its giving following exception: "System.Runtime.InteropServices.COMException: The transport failed to connect to the server" Please help TIA Pradeep [quoted text, click to view] >-----Original Message-----
>On Tue, 1 Mar 2005 04:07:03 -0800, "Pradeep" <s.pradeep79@gmail.com> >wrote: > >>I am using IIS/SMTP Service on Windows 2000 professional >>for sending email, it was working fine on Windows XP >>Professional and on this it is not giving any error >>message but In Event Viewer its giving follwing warning. >> >>'Message delivery to the remote domain 'yahoo.com' failed >>for the following reason: >>An internal DNS error caused a failure to find the remote >>server.' >> >>I have allowed relay on this system. and also checked basic >>authentication. >> >>And message remains in queue. >> >>Please help me out. > >Dumb question probably, but did you actually check DNS name resolution >to make sure you can get to the destination server? > >Jeff >.
On Tue, 1 Mar 2005 04:07:03 -0800, "Pradeep" <s.pradeep79@gmail.com>
[quoted text, click to view] wrote: >I am using IIS/SMTP Service on Windows 2000 professional >for sending email, it was working fine on Windows XP >Professional and on this it is not giving any error >message but In Event Viewer its giving follwing warning. > >'Message delivery to the remote domain 'yahoo.com' failed >for the following reason: >An internal DNS error caused a failure to find the remote >server.' > >I have allowed relay on this system. and also checked basic >authentication. > >And message remains in queue. > >Please help me out. Dumb question probably, but did you actually check DNS name resolution to make sure you can get to the destination server?
On Tue, 1 Mar 2005 20:58:56 -0800, "Pradeep" <s.pradeep79@gmail.com>
[quoted text, click to view] wrote: >Hi > >What do you mean dump question!!! In this newsgroup there >are many topics posted askin the same question but no one >has given proper solution. Sorry for the confusion. I didn't mean *your* question was dumb, I meant that *mine* might be. Checking name resolution in DNS when you recieve an error stating that a DNS error caused the problem would be an obvious first step, but you didn't say you had done that. So my asking may seem "dumb" because it's so obvious. [quoted text, click to view] >And about DNS name resolution, I am connected to interent >thru DHCP. And when i specify DNS Server then its giving >following exception: > >"System.Runtime.InteropServices.COMException: The >transport failed to connect to the server" I'm not sure what you mean when you say you "specify DNS server". Every system should have a DNS server specified, either a manually entered on or one assigned by DHCP. The key is whether or not that DNS server is resolving addresses correctly for the message to be sent to the destination. Tools such as NSLookup can help determine if your system can find the destination SMTP server as a valid MX record. But the above error is less a DNS one than a connectivity one I suspect. Does your ISP block port 25? Can you post the full event log error with the event ID and source? Is there a record in the SMTP log that might indicate what's happening? My guess in your original error is that the system didn't get a valid resolution of a destination MX record. Then when the SMTP server retried, the record was properly retrieved and the message got through. Not unusual unless it happens routinely, but it may indicate a network connectivity issue or intermittent connectivity. Jeff [quoted text, click to view] >Please help
> >TIA > >Pradeep > >>-----Original Message----- >>On Tue, 1 Mar 2005 04:07:03 -0800, "Pradeep" ><s.pradeep79@gmail.com> >>wrote: >> >>>I am using IIS/SMTP Service on Windows 2000 professional >>>for sending email, it was working fine on Windows XP >>>Professional and on this it is not giving any error >>>message but In Event Viewer its giving follwing warning. >>> >>>'Message delivery to the remote domain 'yahoo.com' >failed >>>for the following reason: >>>An internal DNS error caused a failure to find the >remote >>>server.' >>> >>>I have allowed relay on this system. and also checked >basic >>>authentication. >>> >>>And message remains in queue. >>> >>>Please help me out. >> >>Dumb question probably, but did you actually check DNS >name resolution >>to make sure you can get to the destination server? >> >>Jeff >>. >>
Hi,
Thanks for ur help, that problem is solved but now I am able to send mails on gmail.com but on Yahoo.com & mail.com its giving following error.... "Message delivery to the remote domain 'yahoo.com' failed for the following reason: An SMTP protocol error occurred." Please help me out. TIA Pradeep [quoted text, click to view] >-----Original Message-----
>On Tue, 1 Mar 2005 20:58:56 -0800, "Pradeep" <s.pradeep79@gmail.com> >wrote: > >>Hi >> >>What do you mean dump question!!! In this newsgroup there >>are many topics posted askin the same question but no one >>has given proper solution. > >Sorry for the confusion. I didn't mean *your* question was dumb, I >meant that *mine* might be. Checking name resolution in DNS when you >recieve an error stating that a DNS error caused the problem would be >an obvious first step, but you didn't say you had done that. So my >asking may seem "dumb" because it's so obvious. > >>And about DNS name resolution, I am connected to interent >>thru DHCP. And when i specify DNS Server then its giving >>following exception: >> >>"System.Runtime.InteropServices.COMException: The >>transport failed to connect to the server" > >I'm not sure what you mean when you say you "specify DNS server". >Every system should have a DNS server specified, either a manually >entered on or one assigned by DHCP. The key is whether or not that >DNS server is resolving addresses correctly for the message to be sent >to the destination. Tools such as NSLookup can help determine if your >system can find the destination SMTP server as a valid MX record. > >But the above error is less a DNS one than a connectivity one I >suspect. Does your ISP block port 25? Can you post the full event >log error with the event ID and source? Is there a record in the SMTP >log that might indicate what's happening? > >My guess in your original error is that the system didn't get a valid >resolution of a destination MX record. Then when the SMTP server >retried, the record was properly retrieved and the message got >through. Not unusual unless it happens routinely, but it may indicate >a network connectivity issue or intermittent connectivity. > >Jeff > > > >>Please help >> >>TIA >> >>Pradeep >> >>>-----Original Message----- >>>On Tue, 1 Mar 2005 04:07:03 -0800, "Pradeep" >><s.pradeep79@gmail.com> >>>wrote: >>> >>>>I am using IIS/SMTP Service on Windows 2000 professional >>>>for sending email, it was working fine on Windows XP >>>>Professional and on this it is not giving any error >>>>message but In Event Viewer its giving follwing warning. >>>> >>>>'Message delivery to the remote domain 'yahoo.com' >>failed >>>>for the following reason: >>>>An internal DNS error caused a failure to find the >>remote >>>>server.' >>>> >>>>I have allowed relay on this system. and also checked >>basic >>>>authentication. >>>> >>>>And message remains in queue. >>>> >>>>Please help me out. >>> >>>Dumb question probably, but did you actually check DNS >>name resolution >>>to make sure you can get to the destination server? >>> >>>Jeff >>>. >>> > >.
Pradeep,
Try the following. 1. Open up a DOS window on your Win2k machine 2. Type the following command nslookup -querytype=mx yahoo.com This is what I get on my machine when I do this Server: home8-qwest.bellatlantic.net Address: 151.204.0.84 Non-authoritative answer: yahoo.com MX preference = 1, mail exchanger = mx1.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = mx2.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = mx3.mail.yahoo.com yahoo.com MX preference = 5, mail exchanger = mx4.mail.yahoo.com yahoo.com nameserver = ns2.yahoo.com yahoo.com nameserver = ns3.yahoo.com yahoo.com nameserver = ns4.yahoo.com yahoo.com nameserver = ns5.yahoo.com yahoo.com nameserver = ns1.yahoo.com mx1.mail.yahoo.com internet address = 67.28.113.10 mx1.mail.yahoo.com internet address = 67.28.113.11 mx1.mail.yahoo.com internet address = 64.157.4.78 If you don't get a similar result, try changing your DNS server on the machine. [quoted text, click to view] Pradeep wrote:
> Hi, > > Thanks for ur help, that problem is solved but now I am > able to send mails on gmail.com but on Yahoo.com & > mail.com its giving following error.... > > "Message delivery to the remote domain 'yahoo.com' failed > for the following reason: An SMTP protocol error occurred." > > Please help me out. > > TIA > > Pradeep > > >>-----Original Message----- >>On Tue, 1 Mar 2005 20:58:56 -0800, "Pradeep" > > <s.pradeep79@gmail.com> > >>wrote: >> >> >>>Hi >>> >>>What do you mean dump question!!! In this newsgroup there >>>are many topics posted askin the same question but no > > one > >>>has given proper solution. >> >>Sorry for the confusion. I didn't mean *your* question > > was dumb, I > >>meant that *mine* might be. Checking name resolution in > > DNS when you > >>recieve an error stating that a DNS error caused the > > problem would be > >>an obvious first step, but you didn't say you had done > > that. So my > >>asking may seem "dumb" because it's so obvious. >> >> >>>And about DNS name resolution, I am connected to > > interent > >>>thru DHCP. And when i specify DNS Server then its giving >>>following exception: >>> >>>"System.Runtime.InteropServices.COMException: The >>>transport failed to connect to the server" >> >>I'm not sure what you mean when you say you "specify DNS > > server". > >>Every system should have a DNS server specified, either a > > manually > >>entered on or one assigned by DHCP. The key is whether > > or not that > >>DNS server is resolving addresses correctly for the > > message to be sent > >>to the destination. Tools such as NSLookup can help > > determine if your > >>system can find the destination SMTP server as a valid MX > > record. > >>But the above error is less a DNS one than a connectivity > > one I > >>suspect. Does your ISP block port 25? Can you post the > > full event > >>log error with the event ID and source? Is there a > > record in the SMTP > >>log that might indicate what's happening? >> >>My guess in your original error is that the system didn't > > get a valid > >>resolution of a destination MX record. Then when the > > SMTP server > >>retried, the record was properly retrieved and the > > message got > >>through. Not unusual unless it happens routinely, but it > > may indicate > >>a network connectivity issue or intermittent connectivity. >> >>Jeff >> >> >> >> >>>Please help >>> >>>TIA >>> >>>Pradeep >>> >>> >>>>-----Original Message----- >>>>On Tue, 1 Mar 2005 04:07:03 -0800, "Pradeep" >>> >>><s.pradeep79@gmail.com> >>> >>>>wrote: >>>> >>>> >>>>>I am using IIS/SMTP Service on Windows 2000 > > professional > >>>>>for sending email, it was working fine on Windows XP >>>>>Professional and on this it is not giving any error >>>>>message but In Event Viewer its giving follwing > > warning. > >>>>>'Message delivery to the remote domain 'yahoo.com' >>> >>>failed >>> >>>>>for the following reason: >>>>>An internal DNS error caused a failure to find the >>> >>>remote >>> >>>>>server.' >>>>> >>>>>I have allowed relay on this system. and also checked >>> >>>basic >>> >>>>>authentication. >>>>> >>>>>And message remains in queue. >>>>> >>>>>Please help me out. >>>> >>>>Dumb question probably, but did you actually check DNS >>> >>>name resolution >>> >>>>to make sure you can get to the destination server? >>>> >>>>Jeff >>>>. >>>> >> >>.
Hi
Thanks for reply but I am getting this output from this command.... and i think it is correct..... Server: aaadel.mantraonline.com Address: 202.56.230.6 Non-authoritative answer: yahoo.com MX preference = 1, mail exchanger = mx1.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = mx2.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = mx3.mail.yahoo.com yahoo.com MX preference = 5, mail exchanger = mx4.mail.yahoo.com yahoo.com nameserver = ns1.yahoo.com yahoo.com nameserver = ns2.yahoo.com yahoo.com nameserver = ns3.yahoo.com yahoo.com nameserver = ns4.yahoo.com yahoo.com nameserver = ns5.yahoo.com mx1.mail.yahoo.com internet address = 64.157.4.78 mx1.mail.yahoo.com internet address = 67.28.113.10 mx1.mail.yahoo.com internet address = 67.28.113.11 mx2.mail.yahoo.com internet address = 67.28.114.35 mx2.mail.yahoo.com internet address = 67.28.114.36 mx2.mail.yahoo.com internet address = 64.156.215.8 mx3.mail.yahoo.com internet address = 64.156.215.18 mx3.mail.yahoo.com internet address = 64.156.215.5 mx3.mail.yahoo.com internet address = 64.156.215.6 mx3.mail.yahoo.com internet address = 64.156.215.7 mx4.mail.yahoo.com internet address = 68.142.202.112 mx4.mail.yahoo.com internet address = 68.142.202.113 I don't know whats the problem here even I sent on hotmail and it is working.... but for yahoo its still not working Please help TIA Pradeep [quoted text, click to view] >-----Original Message-----
>Pradeep, > >Try the following. > >1. Open up a DOS window on your Win2k machine >2. Type the following command > > nslookup -querytype=mx yahoo.com > >This is what I get on my machine when I do this > > >Server: home8-qwest.bellatlantic.net >Address: 151.204.0.84 > >Non-authoritative answer: >yahoo.com MX preference = 1, mail exchanger = mx1.mail.yahoo.com >yahoo.com MX preference = 1, mail exchanger = mx2.mail.yahoo.com >yahoo.com MX preference = 1, mail exchanger = mx3.mail.yahoo.com >yahoo.com MX preference = 5, mail exchanger = mx4.mail.yahoo.com > >yahoo.com nameserver = ns2.yahoo.com >yahoo.com nameserver = ns3.yahoo.com >yahoo.com nameserver = ns4.yahoo.com >yahoo.com nameserver = ns5.yahoo.com >yahoo.com nameserver = ns1.yahoo.com >mx1.mail.yahoo.com internet address = 67.28.113.10 >mx1.mail.yahoo.com internet address = 67.28.113.11 >mx1.mail.yahoo.com internet address = 64.157.4.78 > > > >If you don't get a similar result, try changing your DNS server on the >machine. > > > > > > >Pradeep wrote: >> Hi, >> >> Thanks for ur help, that problem is solved but now I am >> able to send mails on gmail.com but on Yahoo.com & >> mail.com its giving following error.... >> >> "Message delivery to the remote domain 'yahoo.com' failed >> for the following reason: An SMTP protocol error occurred." >> >> Please help me out. >> >> TIA >> >> Pradeep >> >> >>>-----Original Message----- >>>On Tue, 1 Mar 2005 20:58:56 -0800, "Pradeep" >> >> <s.pradeep79@gmail.com> >> >>>wrote: >>> >>> >>>>Hi >>>> >>>>What do you mean dump question!!! In this newsgroup there >>>>are many topics posted askin the same question but no >> >> one >> >>>>has given proper solution. >>> >>>Sorry for the confusion. I didn't mean *your* question >> >> was dumb, I >> >>>meant that *mine* might be. Checking name resolution in >> >> DNS when you >> >>>recieve an error stating that a DNS error caused the >> >> problem would be >> >>>an obvious first step, but you didn't say you had done >> >> that. So my >> >>>asking may seem "dumb" because it's so obvious. >>> >>> >>>>And about DNS name resolution, I am connected to >> >> interent >> >>>>thru DHCP. And when i specify DNS Server then its giving >>>>following exception: >>>> >>>>"System.Runtime.InteropServices.COMException: The >>>>transport failed to connect to the server" >>> >>>I'm not sure what you mean when you say you "specify DNS >> >> server". >> >>>Every system should have a DNS server specified, either a >> >> manually >> >>>entered on or one assigned by DHCP. The key is whether >> >> or not that >> >>>DNS server is resolving addresses correctly for the >> >> message to be sent >> >>>to the destination. Tools such as NSLookup can help >> >> determine if your >> >>>system can find the destination SMTP server as a valid MX >> >> record. >> >>>But the above error is less a DNS one than a connectivity >> >> one I >> >>>suspect. Does your ISP block port 25? Can you post the >> >> full event >> >>>log error with the event ID and source? Is there a >> >> record in the SMTP >> >>>log that might indicate what's happening? >>> >>>My guess in your original error is that the system didn't >> >> get a valid >> >>>resolution of a destination MX record. Then when the >> >> SMTP server >> >>>retried, the record was properly retrieved and the >> >> message got >> >>>through. Not unusual unless it happens routinely, but it >> >> may indicate >> >>>a network connectivity issue or intermittent connectivity. >>> >>>Jeff >>> >>> >>> >>> >>>>Please help >>>> >>>>TIA >>>> >>>>Pradeep >>>> >>>> >>>>>-----Original Message----- >>>>>On Tue, 1 Mar 2005 04:07:03 -0800, "Pradeep" >>>> >>>><s.pradeep79@gmail.com> >>>> >>>>>wrote: >>>>> >>>>> >>>>>>I am using IIS/SMTP Service on Windows 2000 >> >> professional >> >>>>>>for sending email, it was working fine on Windows XP >>>>>>Professional and on this it is not giving any error >>>>>>message but In Event Viewer its giving follwing >> >> warning. >> >>>>>>'Message delivery to the remote domain 'yahoo.com' >>>> >>>>failed >>>> >>>>>>for the following reason: >>>>>>An internal DNS error caused a failure to find the >>>> >>>>remote >>>> >>>>>>server.' >>>>>> >>>>>>I have allowed relay on this system. and also checked >>>> >>>>basic >>>> >>>>>>authentication. >>>>>> >>>>>>And message remains in queue. >>>>>> >>>>>>Please help me out. >>>>> >>>>>Dumb question probably, but did you actually check DNS >>>> >>>>name resolution >>>> >>>>>to make sure you can get to the destination server? >>>>> >>>>>Jeff >>>>>. >>>>> >>> >>>. >>> >.
Hmm. Every thing does looks fine.
Try the following: Go to http://aboutmydns.com and run the DevNull SMTP server on your machine in the browser window. This will make your browser an SMTP server. Let's assume your IP is 192.168.1.5 Then, modify the "hosts" file (%WINDIR%\System32\drivers\etc) on your Exchange server and add the following entries 192.168.1.5 mx1.mail.yahoo.com 192.168.1.5 mx2.mail.yahoo.com 192.168.1.5 mx3.mail.yahoo.com 192.168.1.5 mx4.mail.yahoo.com REPLACE 192.168.1.5 with the IP Address of YOUR machine. Now, send a message to Yahoo. Rather than resolving Yahoo's MX to their server, your Exchange will send Yahoo's email to your machine and you will be able to see the server communication in DevNull. If you see messages in DevNull, that means that your server is fine and for some reason Yahoo does not like getting emails from your IP. (Perhaps it got black listed in their DB) If you DO NOT see any messages in DevNull, that means something is wrong with Exchange. [quoted text, click to view] Pradeep wrote:
> Hi > > Thanks for reply but I am getting this output from this > command.... and i think it is correct..... > > Server: aaadel.mantraonline.com > Address: 202.56.230.6 > > Non-authoritative answer: > yahoo.com MX preference = 1, mail exchanger = > mx1.mail.yahoo.com > yahoo.com MX preference = 1, mail exchanger = > mx2.mail.yahoo.com > yahoo.com MX preference = 1, mail exchanger = > mx3.mail.yahoo.com > yahoo.com MX preference = 5, mail exchanger = > mx4.mail.yahoo.com > > yahoo.com nameserver = ns1.yahoo.com > yahoo.com nameserver = ns2.yahoo.com > yahoo.com nameserver = ns3.yahoo.com > yahoo.com nameserver = ns4.yahoo.com > yahoo.com nameserver = ns5.yahoo.com > mx1.mail.yahoo.com internet address = 64.157.4.78 > mx1.mail.yahoo.com internet address = 67.28.113.10 > mx1.mail.yahoo.com internet address = 67.28.113.11 > mx2.mail.yahoo.com internet address = 67.28.114.35 > mx2.mail.yahoo.com internet address = 67.28.114.36 > mx2.mail.yahoo.com internet address = 64.156.215.8 > mx3.mail.yahoo.com internet address = 64.156.215.18 > mx3.mail.yahoo.com internet address = 64.156.215.5 > mx3.mail.yahoo.com internet address = 64.156.215.6 > mx3.mail.yahoo.com internet address = 64.156.215.7 > mx4.mail.yahoo.com internet address = 68.142.202.112 > mx4.mail.yahoo.com internet address = 68.142.202.113 > > I don't know whats the problem here even I sent on hotmail > and it is working.... but for yahoo its still not working > > Please help > > TIA > > Pradeep > >>-----Original Message----- >>Pradeep, >> >>Try the following. >> >>1. Open up a DOS window on your Win2k machine >>2. Type the following command >> >> nslookup -querytype=mx yahoo.com >> >>This is what I get on my machine when I do this >> >> >>Server: home8-qwest.bellatlantic.net >>Address: 151.204.0.84 >> >>Non-authoritative answer: >>yahoo.com MX preference = 1, mail exchanger = > > mx1.mail.yahoo.com > >>yahoo.com MX preference = 1, mail exchanger = > > mx2.mail.yahoo.com > >>yahoo.com MX preference = 1, mail exchanger = > > mx3.mail.yahoo.com > >>yahoo.com MX preference = 5, mail exchanger = > > mx4.mail.yahoo.com > >>yahoo.com nameserver = ns2.yahoo.com >>yahoo.com nameserver = ns3.yahoo.com >>yahoo.com nameserver = ns4.yahoo.com >>yahoo.com nameserver = ns5.yahoo.com >>yahoo.com nameserver = ns1.yahoo.com >>mx1.mail.yahoo.com internet address = 67.28.113.10 >>mx1.mail.yahoo.com internet address = 67.28.113.11 >>mx1.mail.yahoo.com internet address = 64.157.4.78 >> >> >> >>If you don't get a similar result, try changing your DNS > > server on the > >>machine. >> >> >> >> >> >> >>Pradeep wrote: >> >>>Hi, >>> >>>Thanks for ur help, that problem is solved but now I am >>>able to send mails on gmail.com but on Yahoo.com & >>>mail.com its giving following error.... >>> >>>"Message delivery to the remote domain 'yahoo.com' > > failed > >>>for the following reason: An SMTP protocol error > > occurred." > >>>Please help me out. >>> >>>TIA >>> >>>Pradeep >>> >>> >>> >>>>-----Original Message----- >>>>On Tue, 1 Mar 2005 20:58:56 -0800, "Pradeep" >>> >>><s.pradeep79@gmail.com> >>> >>>>wrote: >>>> >>>> >>>> >>>>>Hi >>>>> >>>>>What do you mean dump question!!! In this newsgroup > > there > >>>>>are many topics posted askin the same question but no >>> >>>one >>> >>> >>>>>has given proper solution. >>>> >>>>Sorry for the confusion. I didn't mean *your* question >>> >>>was dumb, I >>> >>> >>>>meant that *mine* might be. Checking name resolution > > in > >>>DNS when you >>> >>> >>>>recieve an error stating that a DNS error caused the >>> >>>problem would be >>> >>> >>>>an obvious first step, but you didn't say you had done >>> >>>that. So my >>> >>> >>>>asking may seem "dumb" because it's so obvious. >>>> >>>> >>>> >>>>>And about DNS name resolution, I am connected to >>> >>>interent >>> >>> >>>>>thru DHCP. And when i specify DNS Server then its > > giving > >>>>>following exception: >>>>> >>>>>"System.Runtime.InteropServices.COMException: The >>>>>transport failed to connect to the server" >>>> >>>>I'm not sure what you mean when you say you "specify > > DNS > >>>server". >>> >>> >>>>Every system should have a DNS server specified, either > > a > >>>manually >>> >>> >>>>entered on or one assigned by DHCP. The key is whether >>> >>>or not that >>> >>> >>>>DNS server is resolving addresses correctly for the >>> >>>message to be sent >>> >>> >>>>to the destination. Tools such as NSLookup can help >>> >>>determine if your >>> >>> >>>>system can find the destination SMTP server as a valid > > MX > >>>record. >>> >>> >>>>But the above error is less a DNS one than a > > connectivity > >>>one I >>> >>> >>>>suspect. Does your ISP block port 25? Can you post > > the > >>>full event >>> >>> >>>>log error with the event ID and source? Is there a >>> >>>record in the SMTP >>> >>> >>>>log that might indicate what's happening? >>>> >>>>My guess in your original error is that the system > > didn't > >>>get a valid >>> >>> >>>>resolution of a destination MX record. Then when the >>> >>>SMTP server >>> >>> >>>>retried, the record was properly retrieved and the >>> >>>message got >>> >>> >>>>through. Not unusual unless it happens routinely, but > > it > >>>may indicate >>> >>> >>>>a network connectivity issue or intermittent > > connectivity. > >>>>Jeff >>>> >>>> >>>> >>>> >>>> >>>>>Please help >>>>> >>>>>TIA >>>>> >>>>>Pradeep >>>>>
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 |