PDA

View Full Version : Verizon closing port 25




corbywan
Feb 6, 2010, 03:32 PM
I have a static IP with Verizon and SLS 10.6.2. They are closing port 25 for clients to send email and telling customers to change to port 587, even if their customers use a 3rd party mail server and a desktop client to access their email.

http://www22.verizon.com/ResidentialHelp/HighSpeed/General+Support/Top+Questions/QuestionsOne/124274.htm

What effect is this going to have on my server for sending/receiving email? What changes, if any, will I need to make? I can't seem to find any info for people running their own mail servers.



corbywan
Feb 6, 2010, 04:10 PM
This may not be an issue. Just re-read some info. You have to speak Verizon Marketing. It refers to residential "high speed" users, and Verizon typically differentiates between high-speed (DSL) and FiOS users. Still investigating. And we are a business, not a residential number.

Benjamindaines
Feb 6, 2010, 04:25 PM
Just change the port your server uses.

Consultant
Feb 6, 2010, 08:47 PM
Just change the port your server uses.

Yup. Can be done in your email client. Takes a minute to find it.

zaphon
Feb 6, 2010, 10:20 PM
Yup. Can be done in your email client. Takes a minute to find it.

Which doesn't help him one bit if this server is hosting e-mail for a domain, as the standard port is the one other mail servers will attempt to connect to him on, not some non-standard port.

Benjamindaines
Feb 6, 2010, 10:34 PM
Which doesn't help him one bit if this server is hosting e-mail for a domain, as the standard port is the one other mail servers will attempt to connect to him on, not some non-standard port.

Simple DNS redirect fix; have anything incoming to port 25 be redirected to 26 or whichever you so please.

Rodimus Prime
Feb 6, 2010, 10:38 PM
Surpised it took them that long. Honestly it is a fairly common practice for ISP to block port 25 for STMP email to all domains but theirs.

Reason being is it is to protect their network from spam being sent out and them getting their servers black listed for hosting it. Now days port 25 is no longer really used by any one.

belvdr
Feb 7, 2010, 04:45 PM
Simple DNS redirect fix; have anything incoming to port 25 be redirected to 26 or whichever you so please.

DNS doesn't hand out port numbers. It would simply pass out MX records for the (sub)domain.