LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Suse/Novell
User Name
Password
Suse/Novell This Forum is for the discussion of Suse Linux.

Notices

Reply
 
Search this Thread
Old 07-21-2005, 06:03 PM   #1
longtex
Member
 
Registered: Aug 2004
Location: Texhuahua
Distribution: RedHat 6,7,9,EL; SuSE 9.2 Pro, Knoppix 3.4/.7/.9, Fedora Core 4
Posts: 87

Rep: Reputation: 15
SuSE 9.2 Pro: can read but not send email


The system described in a previous message is able to read email (with both Thunderbird and Evolution) but can't send it. WHen I try, it simply puts up the "sending" box - I think it says it's contacting the host - and after a few minutes, announces that it timed out waiting for a reply. This is true of two different providers' hosts. The host names are correct and both pointed at port 25. I'm not seeing anything in logs, but I could be looking in the wrong place.
 
Old 07-22-2005, 02:00 PM   #2
fragos
Senior Member
 
Registered: May 2004
Location: Fresno CA USA
Distribution: Ubuntu 10.10
Posts: 1,466

Rep: Reputation: 51
This would be normal behavior if you were on a LAN at work.
 
Old 07-22-2005, 02:22 PM   #3
DrAxeman
Member
 
Registered: Jun 2004
Location: State of Confusion
Distribution: My other OS is your Solaris box.
Posts: 84

Rep: Reputation: 15
Sounds like either your ISP or work LAN has port 25 blocked. One way to test this is to telnet net the mail server:

"telnet <server> 25"

This will help you to determine if you can reach the mail server.
 
Old 07-23-2005, 11:34 AM   #4
longtex
Member
 
Registered: Aug 2004
Location: Texhuahua
Distribution: RedHat 6,7,9,EL; SuSE 9.2 Pro, Knoppix 3.4/.7/.9, Fedora Core 4
Posts: 87

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by fragos
This would be normal behavior if you were on a LAN at work.
Not on my planet.
 
Old 07-23-2005, 12:13 PM   #5
longtex
Member
 
Registered: Aug 2004
Location: Texhuahua
Distribution: RedHat 6,7,9,EL; SuSE 9.2 Pro, Knoppix 3.4/.7/.9, Fedora Core 4
Posts: 87

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by DrAxeman
Sounds like either your ISP or work LAN has port 25 blocked. One way to test this is to telnet net the mail server:

"telnet <server> 25"

This will help you to determine if you can reach the mail server.
I mail regularly from other computers, both Linux and Windoze, through the two mail servers in question. One of them is a server I rent at The Planet, and it does not allow telnet; however I ssh (and puTTY) to it several times a day, and as mentioned email it from other comnputers.

I'm thinking it's probably the router at home not letting traffic out on 25... but I know it lets traffic out on 22, because I ssh from home quite a bit. The more I think about it, the more I think it must be the router - this computer's been at home most of the time, and when I'm at the office I use other computers for email, and haven't tried it there... be easy to check, anyway...

Thanks!
 
Old 07-23-2005, 12:59 PM   #6
DrAxeman
Member
 
Registered: Jun 2004
Location: State of Confusion
Distribution: My other OS is your Solaris box.
Posts: 84

Rep: Reputation: 15
Mail receival happens on port tcp/110. SSH on 22, telnet on 23, and smtp (how you send email) on 25. The command

"telnet <server> 25"

Attempts to connect to your mail server on port 25, not the usual telnet port (23). If port 25 isn't blocked, you will get connected. If 25 is blocked it will eventually timeout.

Most ISP's these days block port 25. This stops spammers from setting up their own mailserver to send out spam on their networks.
 
Old 07-23-2005, 03:39 PM   #7
fragos
Senior Member
 
Registered: May 2004
Location: Fresno CA USA
Distribution: Ubuntu 10.10
Posts: 1,466

Rep: Reputation: 51
Quote:
Originally posted by longtex
Not on my planet.
Your planet must not be business or government agency with an IT department or perhaps you use web mail which normally operates through HTTP on port 80. Port 25 is customarily blocked so that spammers can't hijack it using basic SMTP. These entities mostly use some enterprise mail server, like MS Exchange or Novell Groupwise, for sending LAN user email.
 
Old 07-23-2005, 04:14 PM   #8
longtex
Member
 
Registered: Aug 2004
Location: Texhuahua
Distribution: RedHat 6,7,9,EL; SuSE 9.2 Pro, Knoppix 3.4/.7/.9, Fedora Core 4
Posts: 87

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by fragos
Your planet must not be business or government agency with an IT department or perhaps you use web mail which normally operates through HTTP on port 80. Port 25 is customarily blocked so that spammers can't hijack it using basic SMTP. These entities mostly use some enterprise mail server, like MS Exchange or Novell Groupwise, for sending LAN user email.
Must not. My planet uses SonicWall in office, home, and client offices; only services are ftp (no anonymous), ssh. Net services offered from offsite system in rack farm. See other message - #4 Son set up SonicWall at house, guessing he didn't allow outgoing 25. Personally I almost never use web mail (except on the aforementioned rack farm server) - can't stand the bloody shite. #4 Son uses web mail almost exclusively, so probably never noticed.

You live, and you learn... well, okay, you live...
 
Old 07-23-2005, 04:21 PM   #9
longtex
Member
 
Registered: Aug 2004
Location: Texhuahua
Distribution: RedHat 6,7,9,EL; SuSE 9.2 Pro, Knoppix 3.4/.7/.9, Fedora Core 4
Posts: 87

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by DrAxeman
Mail receival happens on port tcp/110. SSH on 22, telnet on 23, and smtp (how you send email) on 25. The command

"telnet <server> 25"

Attempts to connect to your mail server on port 25, not the usual telnet port (23). If port 25 isn't blocked, you will get connected. If 25 is blocked it will eventually timeout.

Most ISP's these days block port 25. This stops spammers from setting up their own mailserver to send out spam on their networks.
Yes, you're right, I wasn't thinking about telnet and 25 versus 2... but... as I said elsewhere, outgoing (smtp) mail works from other locations to the mail, so the blockage is on this end - either the new improved SuSE box, or the router... it looks like the router at this point. I'm at a client's site for a few days, so won't be able to check until I get back... but called #4 Son, who set up the router (actually, I think the problem is in the SonicWall, which he also set up) and told him to check it.

Thanks for the pointer!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Pine won't send email, can't read inbox, I'm a new Fedora user SharpyWarpy Fedora 1 06-29-2005 07:43 AM
email 'send' NO - email 'receive' YES..? captain skywave Linux - Wireless Networking 4 04-23-2005 03:35 AM
email 'send' YES - email 'receive' NO..? captain skywave Linux - Wireless Networking 1 04-22-2005 05:23 AM
I have problems to send emails out with Suse 9.1 Pro balki Linux - Software 0 09-24-2004 03:02 AM
Allowing an IP to send email using my email server... culprit Linux - Networking 7 09-09-2003 12:24 PM


All times are GMT -5. The time now is 10:20 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration