Godaddy Mail Server/Telnet Session Not Working - Message Refused
nos...@notreal.com
mail through an email account at godaddy.com. Finally I tried a telnet
session, which I should have tried much, much earlier (duh), and the
results are as follows.
root@myserver:/etc/mail# telnet smtpout.secureserver.net 3535
Trying 72.167.82.80...
Connected to smtpout.secureserver.net.
Escape character is '^]'.
220 p3plsmtpa01-05.prod.phx3.secureserver.net ESMTP
auth login
334 VXNlcm5hbWU6
Z2FyYmFnZQ0KDQo=
334 UGFzc3dvcmQ6
bW9yZV9nYXJiYWdl
235 Authentication succeeded.
mail from: us...@mydomain.com
250 Sender accepted.
rcpt to: us...@someotherdomain.com
250 Recipient accepted.
data
354 End your message with a period.
Subject: Test
This is a test
.
554 Message refused.
quit
221 Good bye.
Connection closed by foreign host.
The server accepts my user name and password, both encoded to base64,
then accepts the sender address on my domain, the recipient's address,
and the email itself all without a whimper. When I end the email
however, I receive a "554 Message refused." Any idea what as to why
that would occur?
The only thing I could find doing a Google search was that their mail
servers in the past have refused a message if the server found "[]" on a
single line, but that is certainly not the case here.
Thanks.
Grant Taylor
> Any idea what as to why that would occur?
It is most likely some sort of policy / spam / virus filter that is
processing the message after the DATA portion is received, that is not
happy with the message.
I do see a couple sticking points that I've run in to over the years:
1) Your SMTP envelope addresses are not enclosed in angle brackets.
2) You do not have a date header. (Some filters require it.
Grant. . . .
nos...@notreal.com
gta...@riverviewtech.net says...
> nos...@notreal.com wrote:
> > Any idea what as to why that would occur?
>
> It is most likely some sort of policy / spam / virus filter that is
> processing the message after the DATA portion is received, that is not
> happy with the message.
I don't know what more I can do to make it plain vanilla. It has a one
word subject and a four word body. There certainly isn't any virus,
bad links, or other other things that might trigger a filter.
>
> I do see a couple sticking points that I've run in to over the years:
>
> 1) Your SMTP envelope addresses are not enclosed in angle brackets.
Based on this I gave that a try. Same result.
> 2) You do not have a date header. (Some filters require it.
>
I have never had to do that before, but I certainly have not seen it
all. I will see what I can find out on how to do that in a telnet
session and report back.
Thanks for responding.
>
>
> Grant. . . .
>
Grant Taylor
> I don't know what more I can do to make it plain vanilla. It has a one
> word subject and a four word body. There certainly isn't any virus,
> bad links, or other other things that might trigger a filter.
I don't believe your test message was in any way shape spam. I'm
thinking that the filter might have gotten unhappy at the fact that some
header (i.e. Date:) did not exist.
> Based on this I gave that a try. Same result.
*nod*
> I have never had to do that before, but I certainly have not seen it
> all. I will see what I can find out on how to do that in a telnet
> session and report back.
Very simply, copy the date header out of an email from today.
Another thing you can do is to look at the message source of a test
message you send your self from your MUA. Use that as a template.
> Thanks for responding.
You are welcome.
Grant. . . .
nos...@notreal.com
gta...@riverviewtech.net says...
> nos...@notreal.com wrote:
> > I don't know what more I can do to make it plain vanilla. It has a one
> > word subject and a four word body. There certainly isn't any virus,
> > bad links, or other other things that might trigger a filter.
>
> I don't believe your test message was in any way shape spam. I'm
> thinking that the filter might have gotten unhappy at the fact that some
> header (i.e. Date:) did not exist.
>
> > Based on this I gave that a try. Same result.
>
> *nod*
>
> > I have never had to do that before, but I certainly have not seen it
> > all. I will see what I can find out on how to do that in a telnet
> > session and report back.
>
> Very simply, copy the date header out of an email from today.
>
If understand you correctly you enter in the "data" section thusly.
data
354 End your message with a period.
Date: 23 Mar 2010 03:05:02 +0000
Subject: Test
This is a test.
.
554 Message refused.
> Another thing you can do is to look at the message source of a test
> message you send your self from your MUA. Use that as a template.
>
I also tried this.
data
354 End your message with a period.
Date: Mon, 22 Mar 2010 19:38:07 -0400
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCIIsw
Subject: Test
This is a test.
.
554 Message refused
I did fill out a ticket with Godaddy, but I am not hopeful. Their
responses seemed to be scripted and often do not answer the question
asked. Time will tell. Thanks again.
Grant Taylor
> If understand you correctly you enter in the "data" section thusly.
>
> data
> 354 End your message with a period.
> Date: 23 Mar 2010 03:05:02 +0000
> Subject: Test
> This is a test.
> .
> 554 Message refused.
Eh...
1) Your date is not RFC compliant. Use something like this:
Date: Tue, 23 Mar 2010 17:04:05 -0500
2) You don't have the required line between your headers and your
message body. I think your message should look more like this:
data
Date: Tue, 23 Mar 2010 17:04:05 -0500
Subject: Test
This is a test.
.
(Sorry, I did not notice the lack of the blank line to separate the
headers from the body before.)
> I also tried this.
>
> data
> 354 End your message with a period.
> Date: Mon, 22 Mar 2010 19:38:07 -0400
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCIIsw
> Subject: Test
> This is a test.
> .
> 554 Message refused
Well, there your date looks good. Though, there is the missing blank
line to separate the headers and body.
> I did fill out a ticket with Godaddy, but I am not hopeful. Their
> responses seemed to be scripted and often do not answer the question
> asked. Time will tell. Thanks again.
Good luck with that.
Grant. . . .
Paolo Bellutta
>....
> 554 Message refused.
> quit
> 221 Good bye.
> Connection closed by foreign host.
Is it possible that the mail server in question is configured to do a
reverse DNS lookup?
If so you need to make sure you have an entry for the host you are
sending the messages from.
Paolo
Grant Taylor
> Is it possible that the mail server in question is configured to do a
> reverse DNS lookup?
>
> If so you need to make sure you have an entry for the host you are
> sending the messages from.
Very true. More and more mail servers are requiring RevDNS for them to
be willing to accept email. (I personally don't subscribe to such, but
make sure that all my mail servers have RevDNS properly set up.)
Grant. . . .
nos...@notreal.com
>
> I did fill out a ticket with Godaddy, but I am not hopeful. Their
> responses seemed to be scripted and often do not answer the question
> asked. Time will tell. Thanks again.
>
>
FWIW, I did hear from Godaddy and they indicated that I was using the
wrong mail server and that I should be using relay-
hosting.secureserver.net and not smtpout.secureserver.net. They didn't
give a reason why and they didn't give me the port number to use. I
tried all the port numbers that were available for the
smtpout.secureserver.net server and few that other mail servers are
using but couldn't connect. I have followed up with another email
asking for the port number but I have a funny feeling they are going to
say they only offer port 25 on the server. Unfortunately my ISP blocks
25 outbound (sigh). Perhaps I will get lucky though. The fat lady has
not sung yet.
nos...@notreal.com
gta...@riverviewtech.net says...
the server change so I hadn't seen your suggestions. I will give those
suggestions a try now. Thanks.
Grant Taylor
> FWIW, I did hear from Godaddy and they indicated that I was using the
> wrong mail server and that I should be using
> to use. I tried all the port numbers that were available for the
> smtpout.secureserver.net server and few that other mail servers are
> using but couldn't connect. I have followed up with another email
> asking for the port number but I have a funny feeling they are going
> to say they only offer port 25 on the server. Unfortunately my ISP
> blocks 25 outbound (sigh). Perhaps I will get lucky though. The fat
> lady has not sung yet.
*nod*
For what it's worth, I was only able to connect to port 25 (out of 25,
465, and 587) on relay-hosting.secureserver.net.
Grant. . . .
nos...@notreal.com
> > If understand you correctly you enter in the "data" section thusly.
> >
> > data
> > 354 End your message with a period.
> > Date: 23 Mar 2010 03:05:02 +0000
> > Subject: Test
> > This is a test.
> > .
> > 554 Message refused.
>
> Eh...
>
> 1) Your date is not RFC compliant. Use something like this:
>
> Date: Tue, 23 Mar 2010 17:04:05 -0500
I just did a cut and paste from an existing email. It shows you how
much, or really how little, I know.
>
> 2) You don't have the required line between your headers and your
> message body. I think your message should look more like this:
>
> data
> Date: Tue, 23 Mar 2010 17:04:05 -0500
> Subject: Test
>
> This is a test.
> .
>
> (Sorry, I did not notice the lack of the blank line to separate the
> headers from the body before.)
Not a problem. I am just thankful you replied.
>
> > I also tried this.
> >
> > data
> > 354 End your message with a period.
> > Date: Mon, 22 Mar 2010 19:38:07 -0400
> > Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCIIsw
> > Subject: Test
> > This is a test.
> > .
> > 554 Message refused
>
> Well, there your date looks good. Though, there is the missing blank
> line to separate the headers and body.
This is my latest effort.
data
354 End your message with a period.
Date: Mon, 22 Mar 2010 19:38:07 -0400
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCIIsw
Subject: Test
This is a test.
.
554 Message refused.
I suspect you are hitting your head against the wall trying to solve a
problem that at least Godaddy feels is unsolvable if they switched me to
another server. On the other hand, I also suspect you know more about
email in general and sendmail in particular than 99.4% of their techs in
customer support so if you have any more ideas, I am game to try them.
>
> > I did fill out a ticket with Godaddy, but I am not hopeful. Their
> > responses seemed to be scripted and often do not answer the question
> > asked. Time will tell. Thanks again.
>
> Good luck with that.
Do I detect a sense of skepticism? :)
Thanks again for taking the time to help.
>
>
>
> Grant. . . .
>
Grant Taylor
> I just did a cut and paste from an existing email. It shows you how
> much, or really how little, I know.
n/p
> Not a problem. I am just thankful you replied.
You are welcome.
> This is my latest effort.
Try one more time including the To: and From: headers. (Same idea as
the requirement for the Date: header.)
To: Bob <b...@domain.tld>
From: Ed <e...@domain.tld>
> I suspect you are hitting your head against the wall trying to solve
> a problem that at least Godaddy feels is unsolvable if they switched
> me to another server. On the other hand, I also suspect you know
> more about email in general and sendmail in particular than 99.4% of
> their techs in customer support so if you have any more ideas, I am
> game to try them.
*chuckle*
> Do I detect a sense of skepticism? :)
Not in you. You are (or appear to be) actually trying. That is more
than I can say for most large companies that I've had to interface with.
> Thanks again for taking the time to help.
You are welcome.
Grant. . . .
Joe Zeff
> On the other hand, I also suspect you know more about
> email in general and sendmail in particular than 99.4% of their techs in
> customer support so if you have any more ideas, I am game to try them.
<mode="pedant">
That's 99.44%.
</mode>
--
Joe Zeff -- The Guy With The Sideburns:
http://www.zeff.us http://www.lasfs.info
Kill as many as you can; I have a morbid love of excess.
nos...@notreal.com
gta...@riverviewtech.net says...
>
> Try one more time including the To: and From: headers. (Same idea as
> the requirement for the Date: header.)
>
> To: Bob <b...@domain.tld>
> From: Ed <e...@domain.tld>
>
Good thought. I had reverted to just using an address with no angle
brackets.
Here are the results.
root@myserver:/etc/mail# telnet smtpout.secureserver.net 3535
Trying 72.167.82.80...
Connected to smtpout.secureserver.net.
Escape character is '^]'.
220 p3plsmtpa01-07.prod.phx3.secureserver.net ESMTP
auth login
334 VXNlcm5hbWU6
Z2FyYmFnZQ0KDQo=
334 UGFzc3dvcmQ6
bW9yZV9nYXJiYWdl
235 Authentication succeeded.
MAIL FROM: Test <us...@mydomain.com>
250 Sender accepted.
RCPT TO: Test2 <us...@another.com>
250 Recipient accepted.
data
354 End your message with a period.
Date: Mon, 22 Mar 2010 19:38:07 -0400
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCIIsw
Subject: Test
This a test.
.
554 Message refused.
Oh well.
>
> > Do I detect a sense of skepticism? :)
>
> Not in you. You are (or appear to be) actually trying. That is more
> than I can say for most large companies that I've had to interface with.
>
I guess I missed the mark on that one. The comment "Do I detect a sense
of skepticism? :)" was in reference your "Good luck with that."
statement after I told you that I was contacting Godaddy's support desk.
I guess you really meant "good luck" rather than "you really do not that
will ever happen, do you". Inflection and tone are hard to convey in
emails.
My apologies for the confusion.
I have a four drive tomorrow to arrive at my destination by 10:00 AM so
I wont be back this evening.
Claus Aßmann
> MAIL FROM: Test <us...@mydomain.com>
> 250 Sender accepted.
> RCPT TO: Test2 <us...@another.com>
Please see RFC 821/2821/...
The syntax is utterly wrong.
nos...@notreal.com
8859-1?Q?A=DFmann?= <ca+sendmail(-no-copies-please)@mine.informatik.uni-
kiel.de> says...
I use
MAIL FROM:<us...@mydomain.com>
and
RCPT TO:<us...@another.com>
and I will give those a try. If that is not what you were implying,
please give an example as I am obviously a slow learner.
The one thing I also found in the spec is "If accepted, the SMTP server
returns a 250 OK reply. If the mailbox specification is not acceptable
for some reason, the server MUST return a reply indicating whether the
failure is permanent...."
If my syntax was so wrong and unacceptable, why did the SMTP server
return a "250 Sender accepted"?
mikea
> If my syntax was so wrong and unacceptable, why did the SMTP server
> return a "250 Sender accepted"?
In my experience, not everyone follows every provision of each RFC, or
even the "MUST"s and "MUST NOT"s of the SMTP-related RFCs.
--
Mike Andrews, W5EGO
mi...@mikea.ath.cx
Tired old sysadmin
Grant Taylor
> In my experience, not everyone follows every provision of each RFC,
> or even the "MUST"s and "MUST NOT"s of the SMTP-related RFCs.
Correct.
RFCs are not a bible that everyone follows. (Much to my dismay.)
Rather think of RFCs as a suggested interoperability guide / common
standard that people can meet / agree on. It is up to each implementer
to decide if they want to honor any / all parts of the RFC.
Grant. . . .
nos...@notreal.com
nos...@notreal.com says...
I ran a telnet session the same as my last one with the Date etc. except
for the format of the "to" and "from" fields where I used the format I
think you were suggesting I use, as shown above, and I still receive a
"554 Message refused."
nos...@notreal.com
8859-1?Q?A=DFmann?= <ca+sendmail(-no-copies-please)@mine.informatik.uni-
kiel.de> says...
After reading some more I tried this - and it worked!!
Thanks for your help. Now to figure out what I doing wrong in send
mail.
At least I know now it can be made to to work. Thanks again.
root@myserver:/etc/mail# telnet smtpout.secureserver.net 3535
Trying 72.167.82.80...
Connected to smtpout.secureserver.net.
Escape character is '^]'.
220 smtpauth13.prod.mesa1.secureserver.net ESMTP
AUTH LOGIN
334 VXNlcm5hbWU6
Z2FyYmFnZQ0KDQo=
334 UGFzc3dvcmQ6
bW9yZV9nYXJiYWdl
235 Authentication succeeded.
MAIL FROM:<us...@mydomain.com>
250 Sender accepted.
RCPT TO:<us...@anotherdomian.com>
250 Recipient accepted.
DATA
354 End your message with a period.
Date: 25 Mar 10 09:42:30
From: user <us...@mydomain.com>
Subject: Test
To: user <us...@anotherdomian.com>
This is a test.
.
250 Accepted message qp 27771 bytes 259
Grant Taylor
> After reading some more I tried this - and it worked!!
Good.
> Thanks for your help. Now to figure out what I doing wrong in send
> mail.
;)
> At least I know now it can be made to to work. Thanks again.
Ayup.
So it looks like GoDaddy is requiring valid headers. Good to know.
Grant. . . .
Robert Bonomi
Joe Zeff <the.guy.with....@lasfs.info> wrote:
>On Tue, 23 Mar 2010 22:17:53 -0400, nospam wrote:
>
>> On the other hand, I also suspect you know more about
>> email in general and sendmail in particular than 99.4% of their techs in
>> customer support so if you have any more ideas, I am game to try them.
>
><mode="pedant">
>That's 99.44%.
></mode>
Are you suggesting that their techs are on the Ivory coast? *snigger*