|
List Info
Thread: Big Problem with GoDaddy
|
|
| Big Problem with GoDaddy |
|
2006-12-22 22:49:49 |
Better (though unpractical) have the users that are trying
to send to
friends at GoDaddy let then know how unreasonable GoDaddy is
in regards
to email handling. It sometimes works.
I know I have gotten at least 10 people to move their
websites away from
GoDaddy when I explained what they were doing and showed
them some of
the GoDaddy responses. I know I have also prevented a number
of people
from signing up with GoDaddy in the first place.
Stuart Chase wrote:
> I tried out the bit of having all mx's be
server.ephweb.com
>
> Godaddy unblocked me, and I got at least one email
through. I'll give it a
> few more days to see what happens. But if that's all
it takes, it's a minor
> fix. PITA but minor.
>
> I'll let the list know after the 1st.
>
> Thanks for your help Lyle, you kinda triggered the
thought process on it.
>
> -----Original Message-----
> From: Lyle Giese [mailto:lyle lcrcomputer.info]
> Sent: Friday, December 22, 2006 2:20 PM
> To: surgemail-listnetwinsite.com
> Subject: Re: [SurgeMail List] Big Problem with GoDaddy
>
> I am having a brain cramp here. The only piece left in
my opinion is to
> get Surge to answer as server.ephweb.com and all will
match. But I
> cann't find that setting in Surge right now.
>
> Lyle
>
> Stuart Chase wrote:
>
>> ok, so do you think that config I typed would solve
the problem? - at
>> least correctness.
>>
>> Lyle Giese wrote:
>>
>>> Actually the server is ephweb.com when it
answers on port 25, but that's
>>> configurable in Surge.
>>>
>>> Lyle
>>>
>>> Stuart Chase wrote:
>>>
>>>> That may be where it's going awry.
>>>>
>>>> The helo's saying server.ephweb.com
>>>> I had MX as mx.elpasohonda.com
>>>> There are A records going to both.
>>>>
>>>> So then, would this work ok.
>>>>
>>>> DNS in zone elpasohonda.com
>>>> A 209.30.134.202
>>>> MX 10 server.ephweb.com.
>>>> mail A 209.30.134.202
>>>>
>>>> But someones outlook still have incoming
and outgoing mail servers as
>>>> mail.elpasohonda.com
>>>>
>>>>
>>>>
>>>>
>>>> Lyle Giese wrote:
>>>>
>>>>> The standard is that the helo response
should match the host name
>>>>> in the
>>>>> MX record and that should point to an A
record and that ip address
>>>>> should be a ptr back to the host name
in the MX record. That's the
>>>>> standard and if GoDaddy tells you
anything else ask to talk to a 2nd
>>>>> level support person or a supervisor.
>>>>>
>>>>> Lyle
>>>>>
>>>>> Stuart Chase wrote:
>>>>>
>>>>>> Thanks Lyle,
>>>>>>
>>>>>> I added the PTR's at godaddy's
suggestion to do so, earlier I just
>>>>>> had
>>>>>> server.ephweb.com which they
wouldn't let through.
>>>>>>
>>>>>> They're wanting to see it, what
other choice is there - make all mx's
>>>>>> server.ephweb.com ? if that's the
case, can I still setup
>>>>>> elpasohonda.com to use
mail.elpasohonda.com as their outlook mail
>>>>>> server settings?
>>>>>>
>>>>>> Lyle Giese wrote:
>>>>>>
>>>>>>> Stuart Chase wrote:
>>>>>>>
>>>>>>>> GoDaddy's blocking me with
their error of bogus Helo.
>>>>>>>>
>>>>>>>> Spending some time with
them on the phone today they could offer
>>>>>>>> nothing except to say that
since my email address is
>>>>>>>> schaseelpasohonda.com - that IP Address resolves back to my
>>>>>>>> network
>>>>>>>> domain name.
>>>>>>>>
>>>>>>>> Obviously - like most of us
my web domains are different from my
>>>>>>>> network domain. I host
multiple company domains in fact. Yet
>>>>>>>> they're
>>>>>>>> refusing to unblock for as
long as elpasohonda.com's ip rDNS
>>>>>>>> doesn't
>>>>>>>> resolve to elpasohonda.com
>>>>>>>>
>>>>>>>> however, if you do a lookup
on elpasohonda.com - it will show the
>>>>>>>> same
>>>>>>>> ip address, rDNS will show
the network domain name.
>>>>>>>>
>>>>>>>> Anyone else run into this
garbage from godaddy's ?
>>>>>>>>
>>>>>>>>
>>>>>>> You setup your primary mx
record to be mail.elpasohonda.com. which
>>>>>>> resolves to 209.30.134.202.
The reverse lookup for that ip address
>>>>>>> is:
>>>>>>>
>>>>>>> ;; ANSWER SECTION:
>>>>>>> 202.134.30.209.in-addr.arpa.
6898 IN CNAME
>>>>>>>
202.200.134.30.209.in-addr.arpa.
>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
mail.ephweb.com.
>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>> mail.elpasohonda.com.
>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
server.ephweb.com.
>>>>>>>
>>>>>>> Actually the order of the three
ptr records varies each time I query
>>>>>>> it. Lose the other two ptr
records. It just confuses things.
>>>>>>> (and it
>>>>>>> answers as mail.elpasohonda.com
when connecting on port 25) Then
>>>>>>> you can
>>>>>>> tell them that the primary mx
record points to an A record and the
>>>>>>> reverse lookup on that ip
address matches the hostname for the
>>>>>>> primary
>>>>>>> mx record. That should be
exactly what they are looking for.
>>>>>>>
>>>>>>> Most likely they look at(or
see) the first ptr record only.
>>>>>>>
>>>>>>> Lyle
>>>>>>>
>>>
>>>
>
>
>
>
|
|
| Big Problem with GoDaddy |
|
2006-12-22 23:49:43 |
dale - feel free to send those hosting customers our way
we're more expensive than godaddy, but we give great
service, AND WE RUN SURGEMAIL!
david camm
advanced web systems
keller,tx
Dale wrote:
> Better (though unpractical) have the users that are
trying to send to
> friends at GoDaddy let then know how unreasonable
GoDaddy is in regards
> to email handling. It sometimes works.
>
> I know I have gotten at least 10 people to move their
websites away from
> GoDaddy when I explained what they were doing and
showed them some of
> the GoDaddy responses. I know I have also prevented a
number of people
> from signing up with GoDaddy in the first place.
>
>
>
> Stuart Chase wrote:
>
>> I tried out the bit of having all mx's be
server.ephweb.com
>>
>> Godaddy unblocked me, and I got at least one email
through. I'll give
>> it a
>> few more days to see what happens. But if that's
all it takes, it's a
>> minor
>> fix. PITA but minor.
>>
>> I'll let the list know after the 1st.
>>
>> Thanks for your help Lyle, you kinda triggered the
thought process on it.
>>
>> -----Original Message-----
>> From: Lyle Giese [mailto:lylelcrcomputer.info] Sent:
Friday, December
>> 22, 2006 2:20 PM
>> To: surgemail-listnetwinsite.com
>> Subject: Re: [SurgeMail List] Big Problem with
GoDaddy
>>
>> I am having a brain cramp here. The only piece
left in my opinion is to
>> get Surge to answer as server.ephweb.com and all
will match. But I
>> cann't find that setting in Surge right now.
>>
>> Lyle
>>
>> Stuart Chase wrote:
>>
>>
>>> ok, so do you think that config I typed would
solve the problem? - at
>>> least correctness.
>>>
>>> Lyle Giese wrote:
>>>
>>>
>>>> Actually the server is ephweb.com when it
answers on port 25, but
>>>> that's
>>>> configurable in Surge.
>>>>
>>>> Lyle
>>>>
>>>> Stuart Chase wrote:
>>>>
>>>>
>>>>> That may be where it's going awry.
>>>>>
>>>>> The helo's saying server.ephweb.com
>>>>> I had MX as mx.elpasohonda.com
>>>>> There are A records going to both.
>>>>>
>>>>> So then, would this work ok.
>>>>>
>>>>> DNS in zone elpasohonda.com
>>>>> A 209.30.134.202
>>>>> MX 10 server.ephweb.com.
>>>>> mail A 209.30.134.202
>>>>>
>>>>> But someones outlook still have
incoming and outgoing mail servers as
>>>>> mail.elpasohonda.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Lyle Giese wrote:
>>>>>
>>>>>
>>>>>> The standard is that the helo
response should match the host name
>>>>>> in the
>>>>>> MX record and that should point to
an A record and that ip address
>>>>>> should be a ptr back to the host
name in the MX record. That's the
>>>>>> standard and if GoDaddy tells you
anything else ask to talk to a 2nd
>>>>>> level support person or a
supervisor.
>>>>>>
>>>>>> Lyle
>>>>>>
>>>>>> Stuart Chase wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Lyle,
>>>>>>>
>>>>>>> I added the PTR's at godaddy's
suggestion to do so, earlier I just
>>>>>>> had
>>>>>>> server.ephweb.com which they
wouldn't let through.
>>>>>>>
>>>>>>> They're wanting to see it, what
other choice is there - make all
>>>>>>> mx's
>>>>>>> server.ephweb.com ? if that's
the case, can I still setup
>>>>>>> elpasohonda.com to use
mail.elpasohonda.com as their outlook mail
>>>>>>> server settings?
>>>>>>>
>>>>>>> Lyle Giese wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Stuart Chase wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> GoDaddy's blocking me
with their error of bogus Helo.
>>>>>>>>>
>>>>>>>>> Spending some time with
them on the phone today they could offer
>>>>>>>>> nothing except to say
that since my email address is
>>>>>>>>> schaseelpasohonda.com - that IP Address resolves back to my
>>>>>>>>> network
>>>>>>>>> domain name.
>>>>>>>>>
>>>>>>>>> Obviously - like most
of us my web domains are different from my
>>>>>>>>> network domain. I host
multiple company domains in fact. Yet
>>>>>>>>> they're
>>>>>>>>> refusing to unblock for
as long as elpasohonda.com's ip rDNS
>>>>>>>>> doesn't
>>>>>>>>> resolve to
elpasohonda.com
>>>>>>>>>
>>>>>>>>> however, if you do a
lookup on elpasohonda.com - it will show the
>>>>>>>>> same
>>>>>>>>> ip address, rDNS will
show the network domain name.
>>>>>>>>>
>>>>>>>>> Anyone else run into
this garbage from godaddy's ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> You setup your primary mx
record to be mail.elpasohonda.com. which
>>>>>>>> resolves to 209.30.134.202.
The reverse lookup for that ip address
>>>>>>>> is:
>>>>>>>>
>>>>>>>> ;; ANSWER SECTION:
>>>>>>>>
202.134.30.209.in-addr.arpa. 6898 IN CNAME
>>>>>>>>
202.200.134.30.209.in-addr.arpa.
>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
mail.ephweb.com.
>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>>> mail.elpasohonda.com.
>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
server.ephweb.com.
>>>>>>>>
>>>>>>>> Actually the order of the
three ptr records varies each time I
>>>>>>>> query
>>>>>>>> it. Lose the other two ptr
records. It just confuses things.
>>>>>>>> (and it
>>>>>>>> answers as
mail.elpasohonda.com when connecting on port 25) Then
>>>>>>>> you can
>>>>>>>> tell them that the primary
mx record points to an A record and the
>>>>>>>> reverse lookup on that ip
address matches the hostname for the
>>>>>>>> primary
>>>>>>>> mx record. That should be
exactly what they are looking for.
>>>>>>>>
>>>>>>>> Most likely they look at(or
see) the first ptr record only.
>>>>>>>>
>>>>>>>> Lyle
>>>>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>
>
>
>
|
|
| Big Problem with GoDaddy |
|
2006-12-23 00:40:39 |
Dale,
I've been a customer of David's since 1998, and he's right.
His service rocks!
For example, in those eight years, there have been two (2)
unplanned outages, and about that many planned ones. The
planned outages were on weekends, and involved things like
relocating servers to a new data center.
David didn't put me up to this; I wrote my response when I
saw his.
David Gray, MBA
WizardWrx, formerly P6 Consulting - Established 1985
V: +1 (817) 812-3041
TZ: USA Central, GMT -6
E: mailto:dagraywizardwrx.com
W: http://www.wizardwrx.com/
Tell me what you need, and I'll conjure it.
-----Original Message-----
From: David Camm [mailto:dcammadvwebsys.com]
Sent: Friday, December 22, 2006 17:50
To: surgemail-listnetwinsite.com
Subject: Re: [SurgeMail List] Big Problem with GoDaddy
dale - feel free to send those hosting customers our way
we're more expensive than godaddy, but we give great
service, AND WE RUN SURGEMAIL!
david camm
advanced web systems
keller,tx
Dale wrote:
> Better (though unpractical) have the users that are
trying
to send to
> friends at GoDaddy let then know how unreasonable
GoDaddy
is in regards
> to email handling. It sometimes works.
>
> I know I have gotten at least 10 people to move their
websites away from
> GoDaddy when I explained what they were doing and
showed
them some of
> the GoDaddy responses. I know I have also prevented a
number of people
> from signing up with GoDaddy in the first place.
>
>
>
> Stuart Chase wrote:
>
>> I tried out the bit of having all mx's be
server.ephweb.com
>>
>> Godaddy unblocked me, and I got at least one email
through. I'll give
>> it a
>> few more days to see what happens. But if that's
all it
takes, it's a
>> minor
>> fix. PITA but minor.
>>
>> I'll let the list know after the 1st.
>>
>> Thanks for your help Lyle, you kinda triggered the
thought process on it.
>>
>> -----Original Message-----
>> From: Lyle Giese [mailto:lylelcrcomputer.info] Sent:
Friday, December
>> 22, 2006 2:20 PM
>> To: surgemail-listnetwinsite.com
>> Subject: Re: [SurgeMail List] Big Problem with
GoDaddy
>>
>> I am having a brain cramp here. The only piece
left in
my opinion is to
>> get Surge to answer as server.ephweb.com and all
will
match. But I
>> cann't find that setting in Surge right now.
>>
>> Lyle
>>
>> Stuart Chase wrote:
>>
>>
>>> ok, so do you think that config I typed would
solve the
problem? - at
>>> least correctness.
>>>
>>> Lyle Giese wrote:
>>>
>>>
>>>> Actually the server is ephweb.com when it
answers on
port 25, but
>>>> that's
>>>> configurable in Surge.
>>>>
>>>> Lyle
>>>>
>>>> Stuart Chase wrote:
>>>>
>>>>
>>>>> That may be where it's going awry.
>>>>>
>>>>> The helo's saying server.ephweb.com
>>>>> I had MX as mx.elpasohonda.com
>>>>> There are A records going to both.
>>>>>
>>>>> So then, would this work ok.
>>>>>
>>>>> DNS in zone elpasohonda.com
>>>>> A 209.30.134.202
>>>>> MX 10 server.ephweb.com.
>>>>> mail A 209.30.134.202
>>>>>
>>>>> But someones outlook still have
incoming and outgoing
mail servers as
>>>>> mail.elpasohonda.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Lyle Giese wrote:
>>>>>
>>>>>
>>>>>> The standard is that the helo
response should match
the host name
>>>>>> in the
>>>>>> MX record and that should point to
an A record and
that ip address
>>>>>> should be a ptr back to the host
name in the MX
record. That's the
>>>>>> standard and if GoDaddy tells you
anything else ask
to talk to a 2nd
>>>>>> level support person or a
supervisor.
>>>>>>
>>>>>> Lyle
>>>>>>
>>>>>> Stuart Chase wrote:
>>>>>>
>>>>>>
>>>>>>> Thanks Lyle,
>>>>>>>
>>>>>>> I added the PTR's at godaddy's
suggestion to do so,
earlier I just
>>>>>>> had
>>>>>>> server.ephweb.com which they
wouldn't let through.
>>>>>>>
>>>>>>> They're wanting to see it, what
other choice is
there - make all
>>>>>>> mx's
>>>>>>> server.ephweb.com ? if that's
the case, can I still
setup
>>>>>>> elpasohonda.com to use
mail.elpasohonda.com as their
outlook mail
>>>>>>> server settings?
>>>>>>>
>>>>>>> Lyle Giese wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Stuart Chase wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> GoDaddy's blocking me
with their error of bogus
Helo.
>>>>>>>>>
>>>>>>>>> Spending some time with
them on the phone today
they could offer
>>>>>>>>> nothing except to say
that since my email address
is
>>>>>>>>> schaseelpasohonda.com - that IP Address resolves
back to my
>>>>>>>>> network
>>>>>>>>> domain name.
>>>>>>>>>
>>>>>>>>> Obviously - like most
of us my web domains are
different from my
>>>>>>>>> network domain. I host
multiple company domains
in fact. Yet
>>>>>>>>> they're
>>>>>>>>> refusing to unblock for
as long as
elpasohonda.com's ip rDNS
>>>>>>>>> doesn't
>>>>>>>>> resolve to
elpasohonda.com
>>>>>>>>>
>>>>>>>>> however, if you do a
lookup on elpasohonda.com -
it will show the
>>>>>>>>> same
>>>>>>>>> ip address, rDNS will
show the network domain
name.
>>>>>>>>>
>>>>>>>>> Anyone else run into
this garbage from godaddy's ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> You setup your primary mx
record to be
mail.elpasohonda.com. which
>>>>>>>> resolves to 209.30.134.202.
The reverse lookup for
that ip address
>>>>>>>> is:
>>>>>>>>
>>>>>>>> ;; ANSWER SECTION:
>>>>>>>>
202.134.30.209.in-addr.arpa. 6898 IN CNAME
>>>>>>>>
202.200.134.30.209.in-addr.arpa.
>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
mail.ephweb.com.
>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>>> mail.elpasohonda.com.
>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
server.ephweb.com.
>>>>>>>>
>>>>>>>> Actually the order of the
three ptr records varies
each time I
>>>>>>>> query
>>>>>>>> it. Lose the other two ptr
records. It just
confuses things.
>>>>>>>> (and it
>>>>>>>> answers as
mail.elpasohonda.com when connecting on
port 25) Then
>>>>>>>> you can
>>>>>>>> tell them that the primary
mx record points to an A
record and the
>>>>>>>> reverse lookup on that ip
address matches the
hostname for the
>>>>>>>> primary
>>>>>>>> mx record. That should be
exactly what they are
looking for.
>>>>>>>>
>>>>>>>> Most likely they look at(or
see) the first ptr
record only.
>>>>>>>>
>>>>>>>> Lyle
>>>>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>
>
>
>
|
|
| Big Problem with GoDaddy |
|
2006-12-23 04:00:05 |
Thanks for the offer David, but I think I would prefer to
refer them to
my own hosting service
Although I know they are better then they were in the past,
I couldn't
recommend any customer use a server hosted at The Planet.
Where I work, we had some servers there, one day one of the
boxes went
down, it took them 4 hours to figure out the problem, The
'cause' of the
problem (at least in their answer to us) someone tripped
over a power
cable and unplugged our server. And for that it took them 4
hours to
figure out.
I even had a couple of my own servers there for a while,
turned out they
gave me bad IPs that were blacklisted all over the place and
they
refused to help or give me new IPs.
Hopefully you been luckier than that.
Dale
David Camm wrote:
> dale - feel free to send those hosting customers our
way
>
> we're more expensive than godaddy, but we give great
service, AND WE
> RUN SURGEMAIL!
>
> david camm
> advanced web systems
> keller,tx
>
> Dale wrote:
>
>> Better (though unpractical) have the users that are
trying to send to
>> friends at GoDaddy let then know how unreasonable
GoDaddy is in
>> regards to email handling. It sometimes works.
>>
>> I know I have gotten at least 10 people to move
their websites away
>> from GoDaddy when I explained what they were doing
and showed them
>> some of the GoDaddy responses. I know I have also
prevented a number
>> of people from signing up with GoDaddy in the first
place.
>>
>>
>>
>> Stuart Chase wrote:
>>
>>> I tried out the bit of having all mx's be
server.ephweb.com
>>>
>>> Godaddy unblocked me, and I got at least one
email through. I'll
>>> give it a
>>> few more days to see what happens. But if
that's all it takes, it's
>>> a minor
>>> fix. PITA but minor.
>>>
>>> I'll let the list know after the 1st.
>>>
>>> Thanks for your help Lyle, you kinda triggered
the thought process
>>> on it.
>>>
>>> -----Original Message-----
>>> From: Lyle Giese [mailto:lylelcrcomputer.info] Sent: Friday,
>>> December 22, 2006 2:20 PM
>>> To: surgemail-listnetwinsite.com
>>> Subject: Re: [SurgeMail List] Big Problem with
GoDaddy
>>>
>>> I am having a brain cramp here. The only piece
left in my opinion
>>> is to
>>> get Surge to answer as server.ephweb.com and
all will match. But I
>>> cann't find that setting in Surge right now.
>>>
>>> Lyle
>>>
>>> Stuart Chase wrote:
>>>
>>>
>>>> ok, so do you think that config I typed
would solve the problem? - at
>>>> least correctness.
>>>>
>>>> Lyle Giese wrote:
>>>>
>>>>> Actually the server is ephweb.com when
it answers on port 25, but
>>>>> that's
>>>>> configurable in Surge.
>>>>>
>>>>> Lyle
>>>>>
>>>>> Stuart Chase wrote:
>>>>>
>>>>>> That may be where it's going awry.
>>>>>>
>>>>>> The helo's saying server.ephweb.com
>>>>>> I had MX as mx.elpasohonda.com
>>>>>> There are A records going to both.
>>>>>>
>>>>>> So then, would this work ok.
>>>>>>
>>>>>> DNS in zone elpasohonda.com
>>>>>> A 209.30.134.202
>>>>>> MX 10
server.ephweb.com.
>>>>>> mail A 209.30.134.202
>>>>>>
>>>>>> But someones outlook still have
incoming and outgoing mail
>>>>>> servers as
>>>>>> mail.elpasohonda.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Lyle Giese wrote:
>>>>>>
>>>>>>> The standard is that the helo
response should match the host name
>>>>>>> in the
>>>>>>> MX record and that should point
to an A record and that ip address
>>>>>>> should be a ptr back to the
host name in the MX record. That's the
>>>>>>> standard and if GoDaddy tells
you anything else ask to talk to a
>>>>>>> 2nd
>>>>>>> level support person or a
supervisor.
>>>>>>>
>>>>>>> Lyle
>>>>>>>
>>>>>>> Stuart Chase wrote:
>>>>>>>
>>>>>>>> Thanks Lyle,
>>>>>>>>
>>>>>>>> I added the PTR's at
godaddy's suggestion to do so, earlier I just
>>>>>>>> had
>>>>>>>> server.ephweb.com which
they wouldn't let through.
>>>>>>>>
>>>>>>>> They're wanting to see it,
what other choice is there - make
>>>>>>>> all mx's
>>>>>>>> server.ephweb.com ? if
that's the case, can I still setup
>>>>>>>> elpasohonda.com to use
mail.elpasohonda.com as their outlook mail
>>>>>>>> server settings?
>>>>>>>>
>>>>>>>> Lyle Giese wrote:
>>>>>>>>
>>>>>>>>> Stuart Chase wrote:
>>>>>>>>>
>>>>>>>>>> GoDaddy's blocking
me with their error of bogus Helo.
>>>>>>>>>>
>>>>>>>>>> Spending some time
with them on the phone today they could offer
>>>>>>>>>> nothing except to
say that since my email address is
>>>>>>>>>> schaseelpasohonda.com - that IP Address resolves back to my
>>>>>>>>>> network
>>>>>>>>>> domain name.
>>>>>>>>>>
>>>>>>>>>> Obviously - like
most of us my web domains are different from my
>>>>>>>>>> network domain. I
host multiple company domains in fact. Yet
>>>>>>>>>> they're
>>>>>>>>>> refusing to unblock
for as long as elpasohonda.com's ip rDNS
>>>>>>>>>> doesn't
>>>>>>>>>> resolve to
elpasohonda.com
>>>>>>>>>>
>>>>>>>>>> however, if you do
a lookup on elpasohonda.com - it will show
>>>>>>>>>> the
>>>>>>>>>> same
>>>>>>>>>> ip address, rDNS
will show the network domain name.
>>>>>>>>>>
>>>>>>>>>> Anyone else run
into this garbage from godaddy's ?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> You setup your primary
mx record to be mail.elpasohonda.com.
>>>>>>>>> which
>>>>>>>>> resolves to
209.30.134.202. The reverse lookup for that ip
>>>>>>>>> address
>>>>>>>>> is:
>>>>>>>>>
>>>>>>>>> ;; ANSWER SECTION:
>>>>>>>>>
202.134.30.209.in-addr.arpa. 6898 IN CNAME
>>>>>>>>>
202.200.134.30.209.in-addr.arpa.
>>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
mail.ephweb.com.
>>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>>>> mail.elpasohonda.com.
>>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>>>> server.ephweb.com.
>>>>>>>>>
>>>>>>>>> Actually the order of
the three ptr records varies each time I
>>>>>>>>> query
>>>>>>>>> it. Lose the other two
ptr records. It just confuses things.
>>>>>>>>> (and it
>>>>>>>>> answers as
mail.elpasohonda.com when connecting on port 25) Then
>>>>>>>>> you can
>>>>>>>>> tell them that the
primary mx record points to an A record and
>>>>>>>>> the
>>>>>>>>> reverse lookup on that
ip address matches the hostname for the
>>>>>>>>> primary
>>>>>>>>> mx record. That should
be exactly what they are looking for.
>>>>>>>>>
>>>>>>>>> Most likely they look
at(or see) the first ptr record only.
>>>>>>>>>
>>>>>>>>> Lyle
>>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
|
|
| Big Problem with GoDaddy |
|
2006-12-23 19:36:40 |
dale - nothing ventured, nothing gained 
we've been at theplanet for 3+ years - having moved there
after qwest closed its
datacenter in southlake (tx).
we have a full rack with 12 linux machines doing various
things - both dedicated
and shared webservers as well as a surgemail/dns server.
since we manage all our own stuff, customer service has
never been an issue for
us, although they do run our secondary dns, and their
response to adding or
deleting zones has been exemplary.
we've had one and only one incident that was theplanet's
fault - they had a
massive generator failure and it blew half the datacenter.
aside from the
outage time, our only other damage was one scarred hard
drive, so we were quite
lucky.
that said, you are certainly entitled to your opinion, and i
respect that.
david camm
Dale wrote:
> Thanks for the offer David, but I think I would prefer
to refer them to
> my own hosting service
>
> Although I know they are better then they were in the
past, I couldn't
> recommend any customer use a server hosted at The
Planet.
>
> Where I work, we had some servers there, one day one of
the boxes went
> down, it took them 4 hours to figure out the problem,
The 'cause' of the
> problem (at least in their answer to us) someone
tripped over a power
> cable and unplugged our server. And for that it took
them 4 hours to
> figure out.
>
> I even had a couple of my own servers there for a
while, turned out they
> gave me bad IPs that were blacklisted all over the
place and they
> refused to help or give me new IPs.
>
> Hopefully you been luckier than that.
>
> Dale
>
> David Camm wrote:
>
>> dale - feel free to send those hosting customers
our way
>>
>> we're more expensive than godaddy, but we give
great service, AND WE
>> RUN SURGEMAIL!
>>
>> david camm
>> advanced web systems
>> keller,tx
>>
>> Dale wrote:
>>
>>> Better (though unpractical) have the users that
are trying to send to
>>> friends at GoDaddy let then know how
unreasonable GoDaddy is in
>>> regards to email handling. It sometimes works.
>>>
>>> I know I have gotten at least 10 people to move
their websites away
>>> from GoDaddy when I explained what they were
doing and showed them
>>> some of the GoDaddy responses. I know I have
also prevented a number
>>> of people from signing up with GoDaddy in the
first place.
>>>
>>>
>>>
>>> Stuart Chase wrote:
>>>
>>>> I tried out the bit of having all mx's be
server.ephweb.com
>>>>
>>>> Godaddy unblocked me, and I got at least
one email through. I'll
>>>> give it a
>>>> few more days to see what happens. But if
that's all it takes, it's
>>>> a minor
>>>> fix. PITA but minor.
>>>>
>>>> I'll let the list know after the 1st.
>>>>
>>>> Thanks for your help Lyle, you kinda
triggered the thought process
>>>> on it.
>>>>
>>>> -----Original Message-----
>>>> From: Lyle Giese [mailto:lylelcrcomputer.info] Sent: Friday,
>>>> December 22, 2006 2:20 PM
>>>> To: surgemail-listnetwinsite.com
>>>> Subject: Re: [SurgeMail List] Big Problem
with GoDaddy
>>>>
>>>> I am having a brain cramp here. The only
piece left in my opinion
>>>> is to
>>>> get Surge to answer as server.ephweb.com
and all will match. But I
>>>> cann't find that setting in Surge right
now.
>>>>
>>>> Lyle
>>>>
>>>> Stuart Chase wrote:
>>>>
>>>>
>>>>> ok, so do you think that config I typed
would solve the problem? - at
>>>>> least correctness.
>>>>>
>>>>> Lyle Giese wrote:
>>>>>
>>>>>
>>>>>> Actually the server is ephweb.com
when it answers on port 25, but
>>>>>> that's
>>>>>> configurable in Surge.
>>>>>>
>>>>>> Lyle
>>>>>>
>>>>>> Stuart Chase wrote:
>>>>>>
>>>>>>
>>>>>>> That may be where it's going
awry.
>>>>>>>
>>>>>>> The helo's saying
server.ephweb.com
>>>>>>> I had MX as mx.elpasohonda.com
>>>>>>> There are A records going to
both.
>>>>>>>
>>>>>>> So then, would this work ok.
>>>>>>>
>>>>>>> DNS in zone elpasohonda.com
>>>>>>> A 209.30.134.202
>>>>>>> MX 10
server.ephweb.com.
>>>>>>> mail A 209.30.134.202
>>>>>>>
>>>>>>> But someones outlook still have
incoming and outgoing mail
>>>>>>> servers as
>>>>>>> mail.elpasohonda.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Lyle Giese wrote:
>>>>>>>
>>>>>>>
>>>>>>>> The standard is that the
helo response should match the host name
>>>>>>>> in the
>>>>>>>> MX record and that should
point to an A record and that ip address
>>>>>>>> should be a ptr back to the
host name in the MX record. That's the
>>>>>>>> standard and if GoDaddy
tells you anything else ask to talk to a
>>>>>>>> 2nd
>>>>>>>> level support person or a
supervisor.
>>>>>>>>
>>>>>>>> Lyle
>>>>>>>>
>>>>>>>> Stuart Chase wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks Lyle,
>>>>>>>>>
>>>>>>>>> I added the PTR's at
godaddy's suggestion to do so, earlier I just
>>>>>>>>> had
>>>>>>>>> server.ephweb.com which
they wouldn't let through.
>>>>>>>>>
>>>>>>>>> They're wanting to see
it, what other choice is there - make
>>>>>>>>> all mx's
>>>>>>>>> server.ephweb.com ? if
that's the case, can I still setup
>>>>>>>>> elpasohonda.com to use
mail.elpasohonda.com as their outlook mail
>>>>>>>>> server settings?
>>>>>>>>>
>>>>>>>>> Lyle Giese wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Stuart Chase wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> GoDaddy's
blocking me with their error of bogus Helo.
>>>>>>>>>>>
>>>>>>>>>>> Spending some
time with them on the phone today they could offer
>>>>>>>>>>> nothing except
to say that since my email address is
>>>>>>>>>>> schaseelpasohonda.com - that IP Address resolves back to my
>>>>>>>>>>> network
>>>>>>>>>>> domain name.
>>>>>>>>>>>
>>>>>>>>>>> Obviously -
like most of us my web domains are different from my
>>>>>>>>>>> network domain.
I host multiple company domains in fact. Yet
>>>>>>>>>>> they're
>>>>>>>>>>> refusing to
unblock for as long as elpasohonda.com's ip rDNS
>>>>>>>>>>> doesn't
>>>>>>>>>>> resolve to
elpasohonda.com
>>>>>>>>>>>
>>>>>>>>>>> however, if you
do a lookup on elpasohonda.com - it will show
>>>>>>>>>>> the
>>>>>>>>>>> same
>>>>>>>>>>> ip address,
rDNS will show the network domain name.
>>>>>>>>>>>
>>>>>>>>>>> Anyone else run
into this garbage from godaddy's ?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> You setup your
primary mx record to be mail.elpasohonda.com.
>>>>>>>>>> which
>>>>>>>>>> resolves to
209.30.134.202. The reverse lookup for that ip
>>>>>>>>>> address
>>>>>>>>>> is:
>>>>>>>>>>
>>>>>>>>>> ;; ANSWER SECTION:
>>>>>>>>>>
202.134.30.209.in-addr.arpa. 6898 IN CNAME
>>>>>>>>>>
202.200.134.30.209.in-addr.arpa.
>>>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
mail.ephweb.com.
>>>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>>>>>
mail.elpasohonda.com.
>>>>>>>>>>
202.200.134.30.209.in-addr.arpa. 3299 IN PTR
>>>>>>>>>> server.ephweb.com.
>>>>>>>>>>
>>>>>>>>>> Actually the order
of the three ptr records varies each time I
>>>>>>>>>> query
>>>>>>>>>> it. Lose the other
two ptr records. It just confuses things.
>>>>>>>>>> (and it
>>>>>>>>>> answers as
mail.elpasohonda.com when connecting on port 25) Then
>>>>>>>>>> you can
>>>>>>>>>> tell them that the
primary mx record points to an A record and
>>>>>>>>>> the
>>>>>>>>>> reverse lookup on
that ip address matches the hostname for the
>>>>>>>>>> primary
>>>>>>>>>> mx record. That
should be exactly what they are looking for.
>>>>>>>>>>
>>>>>>>>>> Most likely they
look at(or see) the first ptr record only.
>>>>>>>>>>
>>>>>>>>>> Lyle
>>>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>
>
|
|
[1-5]
|
|