Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: richfiddler on January 04, 2006, 02:41:12 PM

Title: outgoing port 25 blocked by SME? Outgoing email problem
Post by: richfiddler on January 04, 2006, 02:41:12 PM

I'm using SME server 6.01 for a home firewall/router and am running into an outgoing email problem.

All I want is for the SME box to forward outgoing SMTP transactions from clients on the LAN. This works with my DLINK router, so I know there is not an ISP problem.

Does SME server block port 25 outgoing by default? Something is!

From a root shell on my SME box, I can do the port 25 test:

telnet outgoing.verizon.net 25 and it connects just fine.

But from a shell on a client machine on the LAN, the same test fails.

I've also looked at the iptables -L output and I can't see where port 25 is blocked. What am I missing here?

Thanks in advance!

Rich

Title: outgoing port 25 blocked by SME? Outgoing email problem
Post by: byte on January 04, 2006, 03:18:44 PM

SME does not block port 25 at all...

Could it be your ISP blocking 25 ?? try searching there's alot on port 25

Title: outgoing port 25 blocked by SME? Outgoing email problem
Post by: byte on January 04, 2006, 03:39:36 PM

Or maybe your ISP requires Auth...

See here

http://www.pagefault.org/howto/securemail.shtml

Title: HOWTO disable SMTP proxy - SMTP from LAN caught by server
Post by: gordonr on January 05, 2006, 02:19:06 AM

Quote from: "byte"

SME does not block port 25 at all...

No, but it transparently redirects outbound SMTP from the LAN via the local SMTP server, so that it can be scanned for viruses, etc.:

http://no.longer.valid/phpwiki/index.php/SME%20Server%20Announce%20v6.0

Title: outgoing port 25 blocked by SME? Outgoing email problem
Post by: richfiddler on January 05, 2006, 02:32:18 AM

Thanks for the response, I appreciate the effort to help figure out what is going on here.

Just to restate: I made two tests and was in fact able to connect to port 25 from the server, but not from a client on the LAN so I have a hard time seeing how my ISP could be blocking me:

From the SME server:
- ssh as root into my SME server
- telnet mysmtpserver.com 25
- it works -- I'm connected, here's the (scrubbed) message

telnet mysmtpserver.com 25
Trying ww.xx.yy.zz...
Connected to mysmtpserver.com.
Escape character is '^]'.

From my windows machine:
- open dos box
- telnet mysmtpserver.com 25
- no joy, connection failed, here's message

telnet mysmtpserver.com 25
Connecting To mysmtpserver.com...Could not open connection to the host, on port 25: Connect failed


OK, so if my ISP was blocking port 25, then I wouldn't be able to connect from the SME server, right?

Any suggestions on how I can monitor what is happening on the server?

Nothing is logged in /var/log/messages, is there some way to turn on verbose logging for ipchains?

Thanks,

Rich

Title: outgoing port 25 blocked by SME? Outgoing email problem
Post by: gordonr on January 05, 2006, 02:37:44 AM

Quote from: "richfiddler"

Just to restate: I made two tests and was in fact able to connect to port 25 from the server, but not from a client on the LAN so I have a hard time seeing how my ISP could be blocking me:

My post provided a link with details of how to disable the proxy.

Title: Woo-hoo! Thanks Gordon!!! :-D :-D :-D
Post by: richfiddler on January 05, 2006, 02:56:14 AM

That was it!! Thanks so much!!!  :-D :-D :-D

I disabled the proxy with

/sbin/e-smith/db configuration setprop smtpfront-qmail Proxy disabled  
/sbin/e-smith/signal-event remoteaccess-update

and it worked!!!

My wife is very happy and my 3 year old wants me to check my email

 :-)

Thanks again