[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

Walkthrough on receiving email with sendmail on Red Hat Enterprise Linux 4

My quest to receive email with sendmail started 14 months ago on RHEL3.  Now that I have a server with RHEL4 I am willing to give it another shot.  Keep in mind this is a plain RHEL4 without any control panel.

I have studied many articles and read/posted in many forums to no avail.  I'm not sure if anyone really understands sendmail.  (Can you tell I've had it up to my eyeballs in frustration. ;D)

I'll start from the very beginning of the process and allow you to walk me through it.

I type the following command to listen to port 25 for any activity:
[root@plain /]# tcpdump -i eth0 port 25
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

Then, I send an email to the domain name of the server from my gmail account and watch the putty window to see if there is activity.  I immediately get this kind of stuff, which shows me that email is successfully hitting the server:
18:54:13.994095 IP wr-out-0506.google.com.25806 > plain.ev1servers.net.smtp: S 2617874197:2617874197(0) win 5720 <mss 1430,sackOK,timestamp 4292017532 0,nop,wscale 0>
18:54:13.994178 IP plain.ev1servers.net.smtp > wr-out-0506.google.com.25806: R 0:0(0) ack 2617874198 win 0

From what I read, after setting things up right, the mail is supposed to end up in /var/spool/mail/.  I have high hopes for this working, but every time I try to apply the things that I read, it never works.  As far as I can tell, the problem ISN'T between screen and keyboard.  I have managed to accomplish a lot already by following directions.

If I could pay Experts Exchange $100 to give 10,000 points to whoever solves this for me, I would gladly give it.  I wish they had some kind of special option to pay for special operations.

Genuinely looking forward to this!

David
0
davidpesta
Asked:
davidpesta
1 Solution
 
m1tk4Commented:
I think you are digging too deep to begin with, you don't need to go to TCP level to see if SMTP protocol is working on your server.

What you do is from some other remote computer, telnet to port 25 like:

telnet myserver.com 25

If you see something like:

220 myservername.com ESMTP

after you telnet in, your transport protocol layer is fine and you should troubleshoot the delivery problems looking at sendmail logs (/var/log/maillog). If you don't get this, then either your firewall is blocking incoming port 25 or your sendmail is not listening to port 25 on external IP addresses (WHICH IS THE DEFAULT BY THE WAY!!! IT BINDS TO 127.0.0.1 ONLY!).
0
 
arvindCommented:
not able to understand your question... Do u wanna see the SMTP traffic on Linux box?

tcpdump is on packet level or /var/log/maillog sendmail logs is good idea to see
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Tackle projects and never again get stuck behind a technical roadblock.
Join Now