POP and SMTP don't work with DASP

folks,

this is a general question about POP and SMTP email service with DASP.
how many of you successfully or unsuccessfully get POP and SMTP to work or not work with DASP?
and who's your ISP?

i use Cox Communications as the main ISP.
Cox blocks port 25 and 110.
Tmobile, Sprint and Tmobile also block 25 and 110.

thus, if you setup a POP account on DASP and try to use email client such as Outlook, you're out of luck since the ISP blocked 25 and 110.
25/110 will work with the POP email of the ISP but not outside of their network.

i have to reroute all my mails from DASP to GMAIL since GMAIL uses 465 and 995 which not blocked by the ISP.
and then, i can use Outlook.

i have contacted DASP support.
seems like nothing much will be done regarding changing the port to something that the ISP doesn't block.

as a long time customer of DASP (more than 7 years) and before i look for new hosting company, i just want to know how many of you here actually get your POP email to work with DASP and who's your ISP?


TIA.

 

hi,

the 3 mobile ISP are Tmobile, Sprint and Verizon.
i mentioned Tmobile twice in the original post.

anyhow, i tried IMAP per KB instruction here:
http://support.discountasp.net/KB/a277/general-discountaspnet-mail-server-information.aspx


no luck.

i did TELNET from CMD.
it showed 3 connections but all failed.

the only thing works 100% is the webmail.


so, the next question for DASP is....
if i host a client website on DASP, what's the workaround?
tell the client to use webmail?
a lot of them want to archive their correspondence for legal reasons.
webmail has small storage and just plain inconvenient for customers.
especially, most of them now use smartphone.
thus, they want either the POP or IMAP and have the email pushes to their device instead of having to log-on to webmail and check every so often.

 

yep, i am/was surprised as well.
Cox has different service plan.
for home users, 25/100 are blocked outside their network.

i have talked to Cox technician about this.
and yes, they said those ports are blocked.
for a "business plan" which is about $130 per month for internet service, those ports are opened and you can even run your own FTP server (port 21 also will open).

today, i did a remote link to a customer in California who uses Comcast.
25/100 also blocked!!

did a remote link to another customer in Boston who uses Comcast.
25/110 also blocked!!

also checked with Warners broadband ISP in Texas.
25/110 also blocked!

checked with RoadRunner broadband ISP.
blocked too.

checked with AT&T mobile internet, blocked too.

checked with FIOS (which is Verizon fiber optic high speed internet), also blocked 25/110.


i understand 25/110 are the standard port for POP and SMTP.
but, this is a major problem for those who want to use DASP POP3 or IMAP emails.
and i can understand the ISP point of view.
they do it probably to prevent SPAM.


GMAIL uses 465/995 for POP3.
obviously, GMAIL knew about the blockage of ISP and Google made a wise choice.
samething with YAHOO or HOTMAIL Premium POP3 service.
none of them operate on 25/110.
considering YAHOO and HOTMAIL has been around for over a decade and they decided NOT to use 25/110 for their POP3, i think DASP should seriously consider an alternative as well.

 

you can read all about it here in GOOGLE HELP SECTION regarding POP3:

http://mail.google.com/support/bin/answer.py?answer=86373

i've been using port 465/995 for POP3 with GMAIL since 2006.
Outlook Express was my client email with XP and now i use Windows Live Mail with Windows 7.

wouldn't you agree that anyone that hosted a website today would use an email?
and if anyone use it for business, most likely, they want to be able to check their email with their smartphone or PC without having to log-on to webmail.
and preferrably, client wants to use their own domain not GMAIL or Yahoo or any of the free email service.

i understand 25/110 is blocked by ISP is not DASP fault.
however, knowing those ports are blocked by ALMOST all the major ISP in the USA and not having an alternative port to use, that's a different story.

like i said, i've been a long time DASP customer....almost 10 years.
the email thing never bother me since i don't use POP3 with DASP.
now that i got a client who wanted to host their website and use POP3 email and i found out this limitation with DASP, it forces me to look somewhere else for hosting service.

 

Again, that is for a secure POP, it isn't an alternate for regular POP. In any event, what Google or Hotmail do is irrelevant.

Yes. And we service almost 50,000 customers with 300,000 email accounts, and so far, you're the only one who is reporting this issue.

If your ISP is blocking an incoming POP port in order to squeeze more money out of you, maybe it's time to get a new ISP rather than asking us to change our platform.

No one that I know of in the hosting industry offers an alternate POP port. Maybe you can find one, but I can assure you it is not typical. You seem to be suggesting in your posts that we're somehow lacking or a decade behind the times because we don't, but that's simply not the case.

 

read the previous post regarding the ISP that block 25/110.
thus, it's not only my ISP.

i also tested with mobile internet provider such as AT&T, Verizon, Sprint, Tmobile, and a smaller ISP Cricket. all block 25/110.

the landline ISP (as mentioned above) also block 25/110.

and i'm curious as to non of the DASP members responded to this post.

can you provide the ISP in the USA that DASP client able to use POP3?

 

Yes, all of them, as far as I know.

If they didn't, we would have thousands of people telling us it didn't work, not just you. I'm not trying to be a dick, but you're trying to make this our problem and it is not. Nor is there anything we can do to help you with it.

Find me an official non-SSL alternate POP3 port on this list and I'll open it for you.

 

or, they didn't bother using DASP POP3.
like i said, i use DASP for almost 10 yrs and i don't use DASP POP3 either.
so, i never wrote to ask you guys or found out about this problem....until now.

i understand your position completely.
keep in mind, if all the major ISP block 25/110 which made DASP POP3 useless, it's a problem for the client who wanted to use Outlook with DASP.
i have personally tested with all the major ISP in the USA (as mentioned in previous post), none works on 25/110 outside of the ISP network.

and like i mentioned before.
i found out about this port problem when my client asked to host their website with the POP3 email requirement.
this is when i tested POP3 with my own DASP account and this is when i found out the problem.
i'm not trying to be a pain.
in fact, i'm trying to bring more customers to host on DASP.
unfortunately, if my client cannot receive their POP3 email with DASP and i can't tell the client to use webmail, so, DASP is off the list.

tomorrow, i'll test POP3 on my other hosting service on Linux.
we'll report back if it's a problem there too or not.

 

update -- problem solved!!

i tested on my Linux server with another hosting company which i'm with them for over 15 years.
POP3 works on port 110.
SMTP works on SSL 465....doesn't work on 587.
however, during Windows Live Mail authentication process, a pop-up confirms for "certificate". once i click to approve it. voila!
i restarted the PC and launch WLM again.
the pop-up about certificate never came up again.
so, i assume it's just a one time deal.

my next goal?
find a Windows hosting service that will work like my Linux server.

i hate to leave DASP for this POP3 limitation.
great service, prompt response.
always answer my question promptly.

last note....i spent probably a total about 5-6 hours regarding this DASP POP3 saga.
it took me about 2 minutes to setup POP3 on Linux server and test it on Windows Live Mail client.
works on the first try using the exact same ISP that didn't work on DASP!!

 

Right. Just like it does here.