From: Charlie Tame on
Okay, if I am in the right thread (One of those days) I think you can reply
to email but not create new right?

If this is the case try typing my email address into the "To" field (
charlie @ tames.net ) with no spaces and see if that will send.I left out
the spaces to avoid making a link out of it.

If that goes okay then try charlie(a)tames.net and see if that works.


If both of these work it seems to me that the problem may be corruption in
your address book so that the name is appearing right to you but the address
book is actually sending a bunch of grabage to the SMTP server, which
naturally is reluctant to send it.

Just my 2c and I hope I remembered the problem from last night - like I said
it is being one of those days :)

Charlie

"Heirloom" <roland58XX(a)XXcox.net> wrote in message
news:%23RKvYNpxFHA.2924(a)TK2MSFTNGP15.phx.gbl...
> Norman and Bruce,
> I did that out of convenience, a cut and paste operation. The SMTP entry
> is actually: smtp.central.cox.net. Sorry about the misleading entries,
> but, those were all verified, removed and re-entered to no avail. I have
> removed the account and set it up again.....may try that again today.
> Is it beyon the realm of possibility that the modem could be at fault? I
> don't see how, since it will connect, surf, dl'd email, obtain updates,
> etc. The only thing failing is the Send Mail To People. I will be sure
> to post the resolution.....if I ever come up with one. Thanks again to
> everyone who has contributed suggestions.
> Heirloom, old and out of ideas
>
> "N. Miller" <anonymous(a)discussions.microsoft.com> wrote in message
> news:k53qd8525gvh$.dlg(a)discussions.microsoft.com...
>> On Fri, 30 Sep 2005 19:34:50 -0500, Heirloom wrote:
>>
>>> I have set up a new Identity, switched to it from the main Identity
>>> and got the same results. I have also tried the <sfc /scannow> from
>>> a command prompt.
>>
>>> The error message is not unlike the following:
>>
>>> Error: The connection to the server has failed.
>>> Account: 'youraccount',
>>> Server: 'www.yourdomain.com',
>>> Protocol: SMTP,
>>> Port: 25,
>>> Secure(SSL): No,
>>> Socket Error: 10060,
>>> Error Number: 0x800CCC0E
>>
>>> Inbox and all other folders are emptied daily....to include the Deleted
>>> items. Email scanning is and has been disabled.
>>
>> I would check your server name againg; "www.yourdomain.com" is an unusual
>> name for an SMTP server. Some variation of "mail.example.com", or
>> "smtp.example.com" is more common.
>>
>> Some that I use include:
>>
>> smtpauth.sbcglobal.net
>> smtp.pacbell.yahoo.com
>> smtp.mail.yahoo.co.jp
>> mail.gmx.net
>> mail.pacbell.net
>>
>> Also, hiding the actual mail server name is pointless. If the ISP is
>> known,
>> then the mail server name can be discovered. OTOH, it is often helpful in
>> troubleshooting to know the actual server name in the error message.
>> Leave
>> the account name obfuscated, but not the server name.
>>
>> --
>> Norman
>> ~Win dain a lotica, En vai tu ri, Si lo ta
>> ~Fin dein a loluca, En dragu a sei lain
>> ~Vi fa-ru les shutai am, En riga-lint
>
>


From: Heirloom on
Okay gang, thanks to all for the ideas and suggestions. I did get the
problem remedied.....finally, after three days of fighting.
This morning, I had a friend, with a similar cpu, set up my mother's account
on his machine. He, too, was unable to send email and got the identical
socket error. I set up his acccount on my mother's machine and everything
worked fine. (any lights going off yet??)
I called my ISP and told them they had a server problem.....probably
blocking my port 25 (SMTP). Once again, I got the same B.S. about my
firewall, AV, OE, etc. etc., so I asked for a supv. He got on the
defensive and repeated what the techs had told me. Long story short, I
changed my smtp server to "east" instead of "central" and everything started
working fine. I then got hold of the RDA (Remote Dial Access) engineering
dept. (took a while to dig that number up). I finally proved to them that
they have a bad server and that it was, in fact, dropping my requests from
port 25.
Like my ol' Dad always used to tell me, "Son, don't talk to the
puppets.....talk to the guy that is pulling the strings."
Heirloom, old and elated


"Charlie Tame" <charlie(a)tames.net> wrote in message
news:uedOpJqxFHA.3860(a)TK2MSFTNGP09.phx.gbl...
> Okay, if I am in the right thread (One of those days) I think you can
> reply to email but not create new right?
>
> If this is the case try typing my email address into the "To" field (
> charlie @ tames.net ) with no spaces and see if that will send.I left out
> the spaces to avoid making a link out of it.
>
> If that goes okay then try charlie(a)tames.net and see if that works.
>
>
> If both of these work it seems to me that the problem may be corruption in
> your address book so that the name is appearing right to you but the
> address book is actually sending a bunch of grabage to the SMTP server,
> which naturally is reluctant to send it.
>
> Just my 2c and I hope I remembered the problem from last night - like I
> said it is being one of those days :)
>
> Charlie
>
> "Heirloom" <roland58XX(a)XXcox.net> wrote in message
> news:%23RKvYNpxFHA.2924(a)TK2MSFTNGP15.phx.gbl...
>> Norman and Bruce,
>> I did that out of convenience, a cut and paste operation. The SMTP
>> entry is actually: smtp.central.cox.net. Sorry about the misleading
>> entries, but, those were all verified, removed and re-entered to no
>> avail. I have removed the account and set it up again.....may try that
>> again today.
>> Is it beyon the realm of possibility that the modem could be at fault?
>> I don't see how, since it will connect, surf, dl'd email, obtain updates,
>> etc. The only thing failing is the Send Mail To People. I will be sure
>> to post the resolution.....if I ever come up with one. Thanks again to
>> everyone who has contributed suggestions.
>> Heirloom, old and out of ideas
>>
>> "N. Miller" <anonymous(a)discussions.microsoft.com> wrote in message
>> news:k53qd8525gvh$.dlg(a)discussions.microsoft.com...
>>> On Fri, 30 Sep 2005 19:34:50 -0500, Heirloom wrote:
>>>
>>>> I have set up a new Identity, switched to it from the main Identity
>>>> and got the same results. I have also tried the <sfc /scannow> from
>>>> a command prompt.
>>>
>>>> The error message is not unlike the following:
>>>
>>>> Error: The connection to the server has failed.
>>>> Account: 'youraccount',
>>>> Server: 'www.yourdomain.com',
>>>> Protocol: SMTP,
>>>> Port: 25,
>>>> Secure(SSL): No,
>>>> Socket Error: 10060,
>>>> Error Number: 0x800CCC0E
>>>
>>>> Inbox and all other folders are emptied daily....to include the Deleted
>>>> items. Email scanning is and has been disabled.
>>>
>>> I would check your server name againg; "www.yourdomain.com" is an
>>> unusual
>>> name for an SMTP server. Some variation of "mail.example.com", or
>>> "smtp.example.com" is more common.
>>>
>>> Some that I use include:
>>>
>>> smtpauth.sbcglobal.net
>>> smtp.pacbell.yahoo.com
>>> smtp.mail.yahoo.co.jp
>>> mail.gmx.net
>>> mail.pacbell.net
>>>
>>> Also, hiding the actual mail server name is pointless. If the ISP is
>>> known,
>>> then the mail server name can be discovered. OTOH, it is often helpful
>>> in
>>> troubleshooting to know the actual server name in the error message.
>>> Leave
>>> the account name obfuscated, but not the server name.
>>>
>>> --
>>> Norman
>>> ~Win dain a lotica, En vai tu ri, Si lo ta
>>> ~Fin dein a loluca, En dragu a sei lain
>>> ~Vi fa-ru les shutai am, En riga-lint
>>
>>
>
>


From: Charlie Tame on
FWIW when USWest changed to QWest they forgot to tell the tech support team
the server names had been changed... Well done by the way.

Charlie


"Heirloom" <roland58XX(a)XXcox.net> wrote in message
news:%237wy%239rxFHA.3188(a)TK2MSFTNGP14.phx.gbl...
> Okay gang, thanks to all for the ideas and suggestions. I did get the
> problem remedied.....finally, after three days of fighting.
> This morning, I had a friend, with a similar cpu, set up my mother's
> account on his machine. He, too, was unable to send email and got the
> identical socket error. I set up his acccount on my mother's machine and
> everything worked fine. (any lights going off yet??)
> I called my ISP and told them they had a server problem.....probably
> blocking my port 25 (SMTP). Once again, I got the same B.S. about my
> firewall, AV, OE, etc. etc., so I asked for a supv. He got on the
> defensive and repeated what the techs had told me. Long story short, I
> changed my smtp server to "east" instead of "central" and everything
> started working fine. I then got hold of the RDA (Remote Dial Access)
> engineering dept. (took a while to dig that number up). I finally proved
> to them that they have a bad server and that it was, in fact, dropping my
> requests from port 25.
> Like my ol' Dad always used to tell me, "Son, don't talk to the
> puppets.....talk to the guy that is pulling the strings."
> Heirloom, old and elated
>
>
> "Charlie Tame" <charlie(a)tames.net> wrote in message
> news:uedOpJqxFHA.3860(a)TK2MSFTNGP09.phx.gbl...
>> Okay, if I am in the right thread (One of those days) I think you can
>> reply to email but not create new right?
>>
>> If this is the case try typing my email address into the "To" field (
>> charlie @ tames.net ) with no spaces and see if that will send.I left out
>> the spaces to avoid making a link out of it.
>>
>> If that goes okay then try charlie(a)tames.net and see if that works.
>>
>>
>> If both of these work it seems to me that the problem may be corruption
>> in your address book so that the name is appearing right to you but the
>> address book is actually sending a bunch of grabage to the SMTP server,
>> which naturally is reluctant to send it.
>>
>> Just my 2c and I hope I remembered the problem from last night - like I
>> said it is being one of those days :)
>>
>> Charlie
>>
>> "Heirloom" <roland58XX(a)XXcox.net> wrote in message
>> news:%23RKvYNpxFHA.2924(a)TK2MSFTNGP15.phx.gbl...
>>> Norman and Bruce,
>>> I did that out of convenience, a cut and paste operation. The SMTP
>>> entry is actually: smtp.central.cox.net. Sorry about the misleading
>>> entries, but, those were all verified, removed and re-entered to no
>>> avail. I have removed the account and set it up again.....may try that
>>> again today.
>>> Is it beyon the realm of possibility that the modem could be at fault? I
>>> don't see how, since it will connect, surf, dl'd email, obtain updates,
>>> etc. The only thing failing is the Send Mail To People. I will be sure
>>> to post the resolution.....if I ever come up with one. Thanks again to
>>> everyone who has contributed suggestions.
>>> Heirloom, old and out of ideas
>>>
>>> "N. Miller" <anonymous(a)discussions.microsoft.com> wrote in message
>>> news:k53qd8525gvh$.dlg(a)discussions.microsoft.com...
>>>> On Fri, 30 Sep 2005 19:34:50 -0500, Heirloom wrote:
>>>>
>>>>> I have set up a new Identity, switched to it from the main Identity
>>>>> and got the same results. I have also tried the <sfc /scannow> from
>>>>> a command prompt.
>>>>
>>>>> The error message is not unlike the following:
>>>>
>>>>> Error: The connection to the server has failed.
>>>>> Account: 'youraccount',
>>>>> Server: 'www.yourdomain.com',
>>>>> Protocol: SMTP,
>>>>> Port: 25,
>>>>> Secure(SSL): No,
>>>>> Socket Error: 10060,
>>>>> Error Number: 0x800CCC0E
>>>>
>>>>> Inbox and all other folders are emptied daily....to include the
>>>>> Deleted
>>>>> items. Email scanning is and has been disabled.
>>>>
>>>> I would check your server name againg; "www.yourdomain.com" is an
>>>> unusual
>>>> name for an SMTP server. Some variation of "mail.example.com", or
>>>> "smtp.example.com" is more common.
>>>>
>>>> Some that I use include:
>>>>
>>>> smtpauth.sbcglobal.net
>>>> smtp.pacbell.yahoo.com
>>>> smtp.mail.yahoo.co.jp
>>>> mail.gmx.net
>>>> mail.pacbell.net
>>>>
>>>> Also, hiding the actual mail server name is pointless. If the ISP is
>>>> known,
>>>> then the mail server name can be discovered. OTOH, it is often helpful
>>>> in
>>>> troubleshooting to know the actual server name in the error message.
>>>> Leave
>>>> the account name obfuscated, but not the server name.
>>>>
>>>> --
>>>> Norman
>>>> ~Win dain a lotica, En vai tu ri, Si lo ta
>>>> ~Fin dein a loluca, En dragu a sei lain
>>>> ~Vi fa-ru les shutai am, En riga-lint
>>>
>>>
>>
>>
>
>


From: PA Bear on
Good sleuthing & thanks to Bruce & Charlie for picking up the ball while
many of us were attending the 2005 MS MVP Summit in Redmond (cf. MVP Steve
Friedl's posts at http://www.dslreports.com/forum/remark,14458312 et al.).
--
~PA Bear

Heirloom wrote:
> Okay gang, thanks to all for the ideas and suggestions. I did get the
> problem remedied.....finally, after three days of fighting.
> This morning, I had a friend, with a similar cpu, set up my mother's
> account
> on his machine. He, too, was unable to send email and got the identical
> socket error. I set up his acccount on my mother's machine and
> everything
> worked fine. (any lights going off yet??)
> I called my ISP and told them they had a server problem.....probably
> blocking my port 25 (SMTP). Once again, I got the same B.S. about my
> firewall, AV, OE, etc. etc., so I asked for a supv. He got on the
> defensive and repeated what the techs had told me. Long story short, I
> changed my smtp server to "east" instead of "central" and everything
> started
> working fine. I then got hold of the RDA (Remote Dial Access) engineering
> dept. (took a while to dig that number up). I finally proved to them that
> they have a bad server and that it was, in fact, dropping my requests from
> port 25.
> Like my ol' Dad always used to tell me, "Son, don't talk to the
> puppets.....talk to the guy that is pulling the strings."
<snip>

From: Heirloom on
Thanks for the kudos.....
In this case they didn't change the server name.....just had a bad server
(or servers). What I am doing, using the "east" server, is rather
unorthodox, but, a valid workaround until they get their act together. It
just irritates me, to no end, when some self-proclaimed tech, bounded by the
results that pop up on his monitor, tells me I need to "format and reinstall
Windows" or "your firewall is causing the problem" or "your AV...." or any
number of things, none of which point THEIR direction. It's just a shame
you have to prove your own innocence. Oh well, 'tis they that dine on
humble pie tonight......of course, it cost me three days of frustration, so,
they deserve every slice.
Heirloom, old and it's rare, but, I love it when I'm
right


"Charlie Tame" <charlie(a)tames.net> wrote in message
news:eNCeDcuxFHA.464(a)TK2MSFTNGP15.phx.gbl...
> FWIW when USWest changed to QWest they forgot to tell the tech support
> team the server names had been changed... Well done by the way.
>
> Charlie
>
>
> "Heirloom" <roland58XX(a)XXcox.net> wrote in message
> news:%237wy%239rxFHA.3188(a)TK2MSFTNGP14.phx.gbl...
>> Okay gang, thanks to all for the ideas and suggestions. I did get the
>> problem remedied.....finally, after three days of fighting.
>> This morning, I had a friend, with a similar cpu, set up my mother's
>> account on his machine. He, too, was unable to send email and got the
>> identical socket error. I set up his acccount on my mother's machine
>> and everything worked fine. (any lights going off yet??)
>> I called my ISP and told them they had a server problem.....probably
>> blocking my port 25 (SMTP). Once again, I got the same B.S. about my
>> firewall, AV, OE, etc. etc., so I asked for a supv. He got on the
>> defensive and repeated what the techs had told me. Long story short, I
>> changed my smtp server to "east" instead of "central" and everything
>> started working fine. I then got hold of the RDA (Remote Dial Access)
>> engineering dept. (took a while to dig that number up). I finally proved
>> to them that they have a bad server and that it was, in fact, dropping my
>> requests from port 25.
>> Like my ol' Dad always used to tell me, "Son, don't talk to the
>> puppets.....talk to the guy that is pulling the strings."
>> Heirloom, old and elated
>>
>>
>> "Charlie Tame" <charlie(a)tames.net> wrote in message
>> news:uedOpJqxFHA.3860(a)TK2MSFTNGP09.phx.gbl...
>>> Okay, if I am in the right thread (One of those days) I think you can
>>> reply to email but not create new right?
>>>
>>> If this is the case try typing my email address into the "To" field (
>>> charlie @ tames.net ) with no spaces and see if that will send.I left
>>> out the spaces to avoid making a link out of it.
>>>
>>> If that goes okay then try charlie(a)tames.net and see if that works.
>>>
>>>
>>> If both of these work it seems to me that the problem may be corruption
>>> in your address book so that the name is appearing right to you but the
>>> address book is actually sending a bunch of grabage to the SMTP server,
>>> which naturally is reluctant to send it.
>>>
>>> Just my 2c and I hope I remembered the problem from last night - like I
>>> said it is being one of those days :)
>>>
>>> Charlie
>>>
>>> "Heirloom" <roland58XX(a)XXcox.net> wrote in message
>>> news:%23RKvYNpxFHA.2924(a)TK2MSFTNGP15.phx.gbl...
>>>> Norman and Bruce,
>>>> I did that out of convenience, a cut and paste operation. The SMTP
>>>> entry is actually: smtp.central.cox.net. Sorry about the misleading
>>>> entries, but, those were all verified, removed and re-entered to no
>>>> avail. I have removed the account and set it up again.....may try
>>>> that again today.
>>>> Is it beyon the realm of possibility that the modem could be at fault?
>>>> I don't see how, since it will connect, surf, dl'd email, obtain
>>>> updates, etc. The only thing failing is the Send Mail To People. I
>>>> will be sure to post the resolution.....if I ever come up with one.
>>>> Thanks again to everyone who has contributed suggestions.
>>>> Heirloom, old and out of ideas
>>>>
>>>> "N. Miller" <anonymous(a)discussions.microsoft.com> wrote in message
>>>> news:k53qd8525gvh$.dlg(a)discussions.microsoft.com...
>>>>> On Fri, 30 Sep 2005 19:34:50 -0500, Heirloom wrote:
>>>>>
>>>>>> I have set up a new Identity, switched to it from the main Identity
>>>>>> and got the same results. I have also tried the <sfc /scannow> from
>>>>>> a command prompt.
>>>>>
>>>>>> The error message is not unlike the following:
>>>>>
>>>>>> Error: The connection to the server has failed.
>>>>>> Account: 'youraccount',
>>>>>> Server: 'www.yourdomain.com',
>>>>>> Protocol: SMTP,
>>>>>> Port: 25,
>>>>>> Secure(SSL): No,
>>>>>> Socket Error: 10060,
>>>>>> Error Number: 0x800CCC0E
>>>>>
>>>>>> Inbox and all other folders are emptied daily....to include the
>>>>>> Deleted
>>>>>> items. Email scanning is and has been disabled.
>>>>>
>>>>> I would check your server name againg; "www.yourdomain.com" is an
>>>>> unusual
>>>>> name for an SMTP server. Some variation of "mail.example.com", or
>>>>> "smtp.example.com" is more common.
>>>>>
>>>>> Some that I use include:
>>>>>
>>>>> smtpauth.sbcglobal.net
>>>>> smtp.pacbell.yahoo.com
>>>>> smtp.mail.yahoo.co.jp
>>>>> mail.gmx.net
>>>>> mail.pacbell.net
>>>>>
>>>>> Also, hiding the actual mail server name is pointless. If the ISP is
>>>>> known,
>>>>> then the mail server name can be discovered. OTOH, it is often helpful
>>>>> in
>>>>> troubleshooting to know the actual server name in the error message.
>>>>> Leave
>>>>> the account name obfuscated, but not the server name.
>>>>>
>>>>> --
>>>>> Norman
>>>>> ~Win dain a lotica, En vai tu ri, Si lo ta
>>>>> ~Fin dein a loluca, En dragu a sei lain
>>>>> ~Vi fa-ru les shutai am, En riga-lint
>>>>
>>>>
>>>
>>>
>>
>>
>
>