View Full Version : Is your ISP Blocking outgoing mail on your domain?
Just checking to see if anyone here is being affected by it... we have a solution we want to test...
Joe
Herbster
07-07-2003, 05:33 PM
Yes!
I thought I had this problem fixed once, but every time I send email I have to remember to change my email address to the ISP based account.
Herb, on your server, try port 2525 ... see if that works.
Herbster
07-07-2003, 07:34 PM
The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was 'hsmith@pacifier.com'. Subject 'Port: 2525', Account: 'NeonMovie', Server: 'mail.neonmovie.com', Protocol: SMTP, Server Response: '550 5.7.1 <hsmith@pacifier.com>... Relaying denied', Port: 2525, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79
Do you have SMTP Authentication enabled? Are you trying to check mail before sending?
Herbster
07-08-2003, 02:38 PM
Sez: "Outgoing Mail (SMTP): 2525".
Yeah, send and receive.
Just tried a straight send and got the same error.
Guess that trick didn't work :(
Anonymous
07-18-2003, 05:31 PM
Did you take down the SMTP listener on 2525?
baseline
07-06-2004, 01:59 AM
Hello,
I just signed up to HostPC and I have unfortunately bumped into this port25 blockage problem. Is it possible for us to pursue alternative port solutions again?
Sorry for digging up this old post.
My experience is that many ISP's have also taken to blocking port 2525 as well. An alternative is to use your ISP's SMTP for all your outgoing email. You may also call your ISP and express your displeasure about the blocking of port 25.
I'm sure Joe will chime in as well, but just things to try in the meantime.
baseline
07-07-2004, 02:37 AM
yup, thanks for your response
when I'm at home I can use my ISP's smtp server, but often times when I'm on the road and send email from my pda's wifi connection from a 'public' network it would be nice if I could access my hostpc's smtp server on some less blocked port :)
eugene
07-10-2004, 02:28 PM
I hate spam . . . argh, all the headaches caused in the attempt to block it.
Perhaps there is another way to get SMTP info. I suppose it could be proxied . . .
tonydi
08-18-2004, 03:36 PM
Joe....
Any more updates on ways to get around the outbound port 25 block?
I'm ok right now but my DSL provider (SBC) is blocking 25 in some other areas of the country and I'm afraid it won't be long before it hits the West Coast. One of the reasons I moved to HostPC was because you guys allowed me to send email through my domain. My previous web host did not and the SBC SMTP servers are awful, delaying outgoing mail by as much as 3 hrs during the day!
Thanks!
try port 2525...
let me know if that doesn't work
tonydi
08-18-2004, 04:28 PM
Nope, doesn't work, connection refused. I have smtp authentication enabled.
eelpot
08-19-2004, 08:25 AM
Joe,
As of yesterday Optonline.net began blocking port25 and I can no longer send mail via my eelpot.com site. The techs there were not very helful even to the point of initially denying that anything had changed, they then threw the ball back at me and "suggested" setting up a vpn or using some sort of "secure smtp".
So count me in on any possible workarounds or other potential solutions.
Thanks...
Paul
crabby at eelpot.com
pzm at amnh.org
Ok, I'll start moving this to the top of the priority list. I've GOT to finish these server moves before the end of the month, but we're getting pretty close - I should be able to clear the 2525 issue up soon.
Joe
Please add one more person to the list. My users would like the capabilty to check their e-mail with Outlook Express.
Joe, thanks for looking into a workaround to solve a problem you did not create!
Please add one more person to the list. My users would like the capabilty to check their e-mail with Outlook Express.
There should be no problem with doing that now. I use Outlook and Outlook Express every day. What change are you actually looking for? The other messages are talking about sending mail when your ISP blocks port 25.
The same workaround change as everyone else in this thread. To clarify my comments, my users connect to the internet using their personal ISP (PeoplePC, in one case) and want to check their e-mail on my domain (hgrm.org) using Outlook Express. PeoplePC started blocking Port 25, so they can't send e-mail now through hgrm.org.
I do have 2525 setup on a couple of servers... I'll try to get them all finished tonight. I've had two reports that the ISP's are blocking 2525 also :(
Dobos
09-06-2004, 02:01 PM
I'd also appreciate your enabling the 2525 port, on www20.hostpc.net. Sisna also blocks port 25.
Pauldow
09-07-2004, 11:03 AM
Hi Joe,
Cox blocks port 25 for me so I was checking if the port 2525 works for me. Is active on server 18?
From Outlook (Some day I'm going to get a real email program) It tells me when I use 2525 "Unable to connect to the outgoing mail server (SMTP). Please verify the port and SSL settings for the outgoing server.
So it looks like Cox may be blocking that too.
Thanks,
Paul
74gto
09-09-2004, 06:30 PM
We are on Optimum and as of this morning we are no longer able to use Outlook to send mail. I tried O/E and Eudora before I checked out the forum.
What is the work around? 2525 isn't helping.
2525 is enabled on all servers.. if it isn't working, your ISP has "caught on" and begun blocking that port as well. The only work around is to use your ISP for SMTP... you can set it up in your email program so that it LOOKS like it's coming from your domain, but it will actually be routed through your ISP.
Joe
74gto
09-09-2004, 07:19 PM
Joe,
I was coming back to reply that 2525 didn't work and I had to use my ISP for smtp.
Brian
Pauldow
09-10-2004, 11:20 AM
Originally posted by Joe@Sep 9 2004, 05:11 PM
2525 is enabled on all servers.. if it isn't working, your ISP has "caught on" and begun blocking that port as well.
To junk mailers, getting other servers to route their garbage is their full time job. It's tough to keep ahead of that.
tonydi
09-10-2004, 05:04 PM
Originally posted by Joe@Sep 9 2004, 05:11 PM
2525 is enabled on all servers.. if it isn't working, your ISP has "caught on" and begun blocking that port as well.
Joe....
I'm unable to send using 2525. As far as I know SBC isn't blocking either 25 or 2525 in my region....yet. Judging from what they've done in their other regions across the country I'm sure us here on the West Coast won't be far behind, at least for 25. I'm not aware of them blocking 2525 anywhere in the US right now.
If I telnet to my mail server address using 2525, it gets rejected, saying it can't open a connection to the host, giving a 525 error.
However, if I try and telnet to my mail server address here at HostPC, it works fine if I point it at port 25.
This is the only way I know to determine if my ISP is blocking a port but it seems really strange that SBC would block 2525 and not port 25. Is there something else I'm missing?
BTW, I'm on www18.
BodySnatcher
11-04-2005, 08:37 PM
Originally posted by Joe@Sep 9 2004, 05:11 PM
2525 is enabled on all servers.. if it isn't working, your ISP has "caught on" and begun blocking that port as well. The only work around is to use your ISP for SMTP... you can set it up in your email program so that it LOOKS like it's coming from your domain, but it will actually be routed through your ISP.
Joe
Quoted post
...this noob looks at that, scratches head, and wonders... How?
heck I am proud of myself for figuring out how to recieve... now this sending issue...
...scratch ...scratch.
Thanks for any further details on how to set this suggested workaround up.
tonydi
11-05-2005, 03:25 AM
You need to find out what the name is for the SMTP server your ISP provides for you. Then you set your email program to use that server name instead of the one here on HostPC. All of your outgoing emails will leave through your ISP's server and the incoming ones will come through the HostPC server.
Hope this helps! If not, post who your ISP is and I'll try and get you the name of the server.
Krishna
11-08-2005, 04:19 PM
hey guys,
recently some of my email has been coming back to me as
Your message did not reach some or all of the intended recipients.
Subject: RE:
Sent: 11/8/2005 10:30 AM
The following recipient(s) could not be reached:
'Danny Curnen' on 11/8/2005 10:30 AM
550 authentication required
I can't figure out the pattern as far as the recieving domains or the domain I am sending it through, it's not consistent. I am using my hostPC domains as SMTP, think this could this get resolved by using my ISP SMTP?
I suppose I could just try it and see what happens but thought I'd post anyways :)
Thanks
Krishna
vBulletin® v3.7.2, Copyright ©2000-2008, Jelsoft Enterprises Ltd.