My telnet to GoDaddy's machine produced identical results as yours

 Telnet to Charter's machine gave me this...

-----------start-here---------------------------------


220 charter.net ESMTP server ready Fri, 21 Nov 2008 03:07:48 -0500
EHLO JOHN
250-charter.net
250-HELP
250-VRFY
250-XREMOTEQUEUE
250-ETRN
250-PIPELINING
250-DSN
250-8BITMIME
250 SIZE 15728640
QUIT
221 charter.net ESMTP server closing connection


Connection to host lost.

C:\SOMEDIR1\ETC>


-----------stop-here----------------------------------

I got a higher speed cable connection.

Now I can't send E-mail

I am repeatedly receiving this error; consistently...

"...553 sorry, relaying denied from your location..."

The pop3 address is set, (big question: correctly ?)

The smtp address is set, (again, correctly ?)

The lengths of the test E-mails are all small (generally, one line or so)

I have called their tech support repeatedly, and I have been given different stories about the names of the incoming and outgoing servers.

If I don't get the "553" message as listed above, then I get a completely different type of error, one in which a window pops up on my screen, telling me: "...8: Socket read timeout...."

Something I noticed was that Pegasus appears to be checking servers which are not listed in the internet mail options 

I am confused by this.

I tried searching the forums here for info, but didn't see this specific problem addressed. I may be missing something.

If this is already answered elsewhere, Then please point me to it. I couldn't find it.

Thanks for any clue.

-- Clarification --

Before today, I was using a dial-up connection. Parmaters were configured properly for the dialed-up host and all systems cooperated properly

Yesterday, I obtained a cable connection (speeds typically a 4+ MegaBits) which appears to be stable and solid; based on other internet applications.

We tested their web-based E-mail and it does work.

That is, of course, the problem; web-based E-mail.

My confusion is that I can't understand which part of which system is giving the various error messages to which part of which other system. 

When I see "8: Socket read timeout", who was trying to read what socket on what machine in what order for what time limit ?

Is there a way that I can see a trace of what signals go out of my machine, and what signals go back into my machine ?

e.g.,,,,

[[[ IF ]]]

If I try to connect to mail.TheirMachine.com, using ID ThisIsMe123 and password abcdefg

[[[ THEN ]]]

What commands actually went out of  my machine, and what response did I actually get back ?

[[[ ENDIF ]]]

If I knew the answer to those questions, I would have a better chance of understanding the problem which would increase the probability of properly guessing which parameter(s) to alter.

Go to Tools / Internet options and check the box on the first tab to create internet session logs.  They will be created in your home directory with names like TCP0001.WPM

Your provider may have changed the mail relay server you should send through from the new connection, which is why you get 553 errors and disconnects from the previous server.  Or you may now need to authenticate.

Vocabulary assistance request: "AUTHENTICATE"

I've heard that word before, but don't really know what it is, how it works, what it means, how it's used, what the implementation looks like, what the rules are, blah blah blah.

Is it explained here on pmail.com somewhere ?

Inquiring brain cells want to know !

Latest update from the Nth phone call with a tech support guy (which lasted 1 hour and 14 minutes)

A couple of months ago I asked several questions about arranging the headers so that the "From:" address would have different addresses that I could use for different accounts and different people

Seems that my crime against society is doing exactly that; setting the "From:" address to something different from what my (new improved higher-speed provider) ISP wants to issue me for E-mail.

When their system sees that I'm sending a message to someone with a "From:" address with my own domain name, I think it  immediately and automatically decides that I'm a spammer and won't let me do anything.

Thank you PaulW for the knowledge about the trace thing. Homework time here.

[quote user="A01"]Vocabulary assistance request: "AUTHENTICATE"[/quote]

Proving that you are who you say you are.

[quote]Is it explained here on pmail.com somewhere ?[/quote]

It's explained in the program in the help on the security tab of 'Settings for sending mail (SMTP)' in Internet mail options.

I now get the same error number, but a different message...

  553 Sorry, that domain isn't in my list of allowed rcpthosts.

Here's the full text...

Delivery has failed on the enclosed message for the following
reasons reported either by the mail delivery system on the mail
relay host or by the local TCP/IP transport module:

  553 Sorry, that domain isn't in my list of allowed rcpthosts.

Your original mail message follows:
--------------------------------------------------------

X-PM-Identity: <Default>
From: My.Desired.address@MyDesiredDomain.com
To: The.Test.Address@TheDesiredDomain.com
Date: Thu, 13 Nov 2008 03:57:44 -0500
MIME-Version: 1.0
Subject: Line Of Ws
Message-ID: <491BA5B8.23185.D97CDC5@My.Desired.address.MyDesiredDomain.com>
Priority: normal
X-mailer: Pegasus Mail for Windows (4.41)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

WWWWWWWWWWWWWWWW

Similar to the first 553 message you were getting - it's not allowing you to relay.

You haven't given any details of who your connection is with, what server you are using, or what changes you have made to your setup since the start, so it's a little difficult to diagnose this any further.  I suspect you need to authenticate before it will allow you to send mail.  Ask your provider for details.

[quote user="PaulW"]

"... details... connection... server... changes ..."

[/quote]

Ahhh, I was afraid I would clutter up the forum with obfuscating details. Sorry for being too vauge. Clueless Newbee strikes again

Here's a 90 word description.

(PREVIOUSLY WORKING SYSTEM)

• Me here, Pegasus v.4.41
• Connection provided by: www.LocalNet.com
• Connection: Dial-up (speed about 25K)
• Receiving mail server in-house at LocalNet
• SMTP server in-house at LocalNet

(FIRST FAILING ATTEMPT)

• Connection provided by: Charter Communications
• Connection: I think this is cable (speed about 4.5 Meg)
• Receiving mail server in-house at  Charter
• SMTP server in-house at Charter

(SECOND FAILING ATTEMPT)

• Connection provided by: Charter Communications
• Connection: Same 4.5 Meg Cable Modem
• Receiving mail server in-house at  GoDaddy
• SMTP server in-house at GoDaddy

(END OF DESCRIPTION)

My tech support conversations (more than 5 hours with 7 different calls) have yielded these results

LocalNet  made it polite and plain and firm: I can do what I want with their machine as long as I dial-in over the telephone. Can you blame them ? That's their business and that's what they sold me; and I might add, they do that job extremely well.

Charter and GoDaddy both gave me long phone conversations and investigations, with repeated subtle suggestions and hints that Pegasus was causing the problem (since it's one'o'them 3rd party E-mail clients, which are all bad). Both companies' reps dropped some not-too-specific (but clear, just the same) hints that OutLook express is the solution to all problems.

When I asked them if they could tell me what bytes I was sending, and the specific string~byte~command~format~whatever that was causing them to reject the request, I got the big uhm, no we don't have that capability here  type of conversation. When I asked if there was another human further up the line who might be more experienced or knowledgeable in the matter, the answer was uniformly no.

That's my question: Who sends what byte(s) to whom, in what order, to cause what action to occur on what part of what system ?

I'm getting the distinct impression, from experiments and minor comments from these tech support people, that the entire problem is the "From:" field in the headers. That is exactly why I want to use Pegasus in the first place. It allows that. Evidently, both Charter and GoDaddy only allow SMTP access when your "From:" field matches the user-name (which is the E-mail address they assign you). Again, these are all guesses. No human on any phone from any company is capable of telling me what bytes went which way in response to what expectations between what systems.

So, I'm guessing further that this means that if you have a small company and you want your E-mail to display your own company's domain name in the "From:" address of your messages, you'll need to find another place. [[update: the following sentence is now false]] Charter and GoDaddy won't allow that.

[[correct version now is]] GoDaddy does allow this, thanks to PaulW and a guy at GoDaddy

According to their websites the outgoing servers are:

Charter: smtp.charter.net  (no authentication)

GoDaddy: smtpout.secureserver.net (authentication with same details as incoming)

Is that what you have been trying?

I have no idea whether either limit the 'From:' address - if that is a problem you will have to find another relay.

[quote user="PaulW"]

Charter: smtp.charter.net (no authentication)

[/quote]

Absolutely not what I was told on the phone.

Again, not what I was told.

I will find out in an hour or so

Everybody !

Vote PaulW for president of the USA

Thanks Paul. I was REALLY getting scared I had made a collossal error.

The GoDaddy SMTP machines do work as you stated.

Also, the latest Tech support guy with whom I spoke agreed with you.

Hey, steady down there.

Glad you got it working,

Identical behaviors appeared, starting yesterday

To my knowledge, I changed nothing

I'm getting a timeout error.

I did get a log, and saw one successful connection, followed by a timeout. The host machine asked for a message, ending with a ".", then timed out.

Great big "duh" in my brain.

I deleted the GoDaddy definitions

Pegasus appears to be contacting the Charter machine, and retrieving messages (if they're there) from the charter machine.

Pegasus appears to be refusing to attempt a connection to the SMTP machine.

This was the result of this afternoon's attempt...

--- Wed, 19 Nov 2008 16:42:46 ---
Connect to 'pop.charter.net' port 110, timeout 30.
16:42:46.390 [*] Connection established to 209.225.8.224
16:42:46.421 >> 0034 +OK InterMail POP3 server ready.\0D\0A
16:42:46.421 << 0027 USER MyUserID@Charter.Net\0D\0A
16:42:46.453 >> 0030 +OK please send PASS command\0D\0A
16:42:46.453 << 0015 PASS TellTheWorldYourPasswordHere\0D\0A
16:42:46.500 >> 0042 +OK MyUserID@Charter.Net is welcome here\0D\0A
16:42:46.500 << 0006 STAT\0D\0A
16:42:46.531 >> 0009 +OK 0 0\0D\0A
16:42:46.531 << 0006 QUIT\0D\0A
16:42:46.562 >> 0061 +OK MyUserID@Charter.Net InterMail POP3 server signing off.\0D\0A
16:42:46.562 --- Connection closed normally at Wed, 19 Nov 2008 16:42:46. ---\0A\0A

That's a POP collection log.  What settings are you now using for sending (SMTP)?  What is the log output?

[quote user="PaulW"]What settings are you now using for sending (SMTP)?[/quote]

Settings for sending (SMTP) are...

Server Host name: smtp.charter.net

Server TCP/IP Port: 25

Timeout: 30

[quote user="PaulW"]What is the log output?
[/quote]

There is none ! That's the entire log session for [ALT][F][H] (Menu, "File", "Check and send mail")

For some reason, two or three days ago, either...

-- Both machines (i.e., GoDaddy and Charter) just stopped responding to anything, or else
-- Pegasus just stopped sending messages

Everything was fine, and I didn't change a thing. Just a few days ago, the systems quit cooperating with each other.

Major DUH in the brain here

By the way, thanks (to you or anyone reading) if you can help me solve this. I'm totally stuck

This just doesn't make any sense at all. The behavior is inconsistent; turbo inconsistent

-- Both machines (i.e., GoDaddy and Charter) just stopped responding to anything, or else
-- Pegasus just stopped sending messages

Any time you are using port 25 for sending it's quite possible you will be blocked by your ISP unless you are using the SMTP host they have provided.  Even there you will normally be required to use authentication when sending to someone off the local system.  You can generally use other ports though especially is using direct SSL   That's why may people are not sending via GMail servers via direct SSL.

I also tried port 80. 

Same results.

So,,,

How do I know when it's my problem with the way I've set the options here; and when it's one of the other two parties ?

i.e., what part of this problem am I contributing ? What is Charter doing ? What is GoDaddy doing.

For that matter, what byte(s) [is|are] going from whom to whom ?

How can I see such bytes ?

So far, all such questions remain unanswered.