Unblocking SMTP

Posted on 2004-04-21
Last Modified: 2010-04-08
Our ISP currently has port 25 blocked. They say we cannot open it because the local port is a random one. How can we allow outgoing emails on our servers, while not requiring the opening of a large number of ports? This is a Cisco PIX515
Question by:dcman99
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
  • +4
LVL 23

Accepted Solution

Tim Holman earned 250 total points
ID: 10883402
Sounds like complete and utter bull to me !
Instructions how to setup an internal mail server so that it can send and receive mail via the PIX are here:

Local server port is NOT random - it will always be port 25 talking to port 25 on another mail server, followed by renegotiations on higher ports that are covered by the state table.  
I would advise 'no fixup smtp' on this PIX, as this is well known to cause issues with Exchange.
LVL 13

Assisted Solution

td_miles earned 250 total points
ID: 10884252
I need to correct tim on one thing, the source port on the sending server will NOT be port 25. It will be a random high port. The destination port on the receiving server will always be port 25.

Other than that, everything else is correct and his advice on what to do is good.

"fixup smtp" doesn't just break Exchange, it causes problems with Lotus Domino as well. I just turn it off all the time now to save any problems. Does anyone have a situation where they are using it and find it helpful ?

The ISP sounds like the don't know what they are talking about...

Expert Comment

ID: 10888963
I'm not an e-mail expert by far, but correct me if I am wrong....doesn't mail go out on a pop3 port 110? I know incoming mail comes in on port 25, but I allways thought that outgoing was port 110....guess i need to read up on my exchange....

FYI, The pix uses the fixup protocol to "Inspect" traffic coming in on port 25 to see if it is actual e-mail, if it is not it shuts down the connection. Since, exchange uses ESMTP instead of SMTP the pix has a hard time distinquishing traffic. That is why we turn off the smtp fixup protocol if we are using EXCHANGE, etc. If the server on the inside is runing regular SMTP....keep the fixup protocol turned will prevent e-mail specific attacks.....
Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

LVL 79

Expert Comment

ID: 10889074
Agree with td that your ISP is blowing smoke up your a...
Why would an ISP purposely block SMTP for a business-class service? If it is not a business service but rather a consumer priced service, then they have every right to block outbound email as well as inbound email to servers. What's in your service agreement?
I would definately fire that ISP and get service elsewhere.
LVL 23

Expert Comment

by:Tim Holman
ID: 10890179
Hawpig - from a mail server perspective incoming mail hits SMTP port 25.  Outgoing mail talks to SMTP port 25 on mail servers out in the wild.
From a client perspective, users can retrieve POP3 email by talking to a server running POP3 on port 110.

Author Comment

ID: 10893146
I just wanted to make a clarification on my original question.  The reason our host says they can not open the mail ports is because they have filters set up to prevent the ongoing DoS attacks that hit our servers.  These filters I guess block the mail ports that we need to use to use the PHP mail function.  Here is the email from our web host:

If we go ahead and unblock ports, the DOS will resume.  They are still
attacking your servers.

If you would like us to remove the filters so you can mail and use your
PHP functions, please let me know.  That being said, once the filters are
removed, your servers will have to handle the DOS attack.

My question is... Is there a way to unblock these mail ports, without leaving them venerable to the DoS attacks?  Is there any way to just unblock the outgoing traffic through these mail ports, but keep the incoming DoS traffic blocked?  It just doesn't sound right that our mail functions have to be rendered useless to block the DoS attacks.  Any suggestions?


Expert Comment

ID: 10894671
Just block the IP addresses doing the attack....Why would they filter port 25 and not block the attacking IPs???? Is your server updated?? is exchange updated??? are all critical updates complete?? Man that makes no sense. Is there hundreds of IP addresses attacking your mail server....if it is only 10 or 20 block those addresses at your boarder router and reopen port 25.....
What type of DoS attack was you getting???

Author Comment

ID: 10901746
The DoS attack is from many random spoofed IPs.
LVL 11

Expert Comment

ID: 10933354
Many ISPs block outbound port 25 to force their customers to use the ISP's SMTP server.  This makes it very hard for clients to send out spam and email viruses, and is a Good Thing -- for residential-class service.  If you have business-class service, your email server should be an exception to this rule; failing that, set your email server to relay all outbound traffic (except for your own domain) via the ISP's server, and move on.

LVL 20

Expert Comment

ID: 11004448

Who's the ISP?
Over in the Exchange forums a number of folks have been told they're on a "business" network, usually  xDSL and have found out that port 25 traffic is block unless they used the ISP as a smart relay. They get very upset if you try to find away around them and may even terminate your connection, as breack of contract.

Basically these are not business class ISP's, they are home user ISP's and suffer from script kiddies and poor user knowledge which floods their networks.

As already mentioned, if this is the case, swap to another ISP.

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Wikipedia defines 'Script Kiddies' in this informal way: "In hacker culture, a script kiddie, occasionally script bunny, skiddie, script kitty, script-running juvenile (SRJ), or similar, is a derogatory term used to describe those who use scripts or…
If you are like regular user of computer nowadays, a good bet that your home computer is on right now, all exposed to world of Internet to be exploited by somebody you do not know and you never will. Internet security issues has been getting worse d…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question