Red Hat

Hi,

That log excerpt indicates that the message was successfully accepted by Sendmail. So you'd have to check the mail logs for your own local server and for whichever server deals with the incoming e-mail for the recipient's domain to see what happened to it next. Presumably it's getting filtered out for some reason at some point, but that session log would certainly seem to show that Sendmail is doing its job successfully and putting the mail into the queue.

where I can check the logs??

Strictly speaking, the answer to that question is that they'll be wherever you've configured your system to store them. However by deafult on Linux, the Sendmail log would typically be /var/log/maillog on a RHEL-style system, or /var/log/mail.log on most Debian-derived distros (such as Ubuntu and others).

yes. I checked as I am not a root user I am unable to view the log. But i Checked in /var/log/spool/mail

And i find the below message:

Code:

... while talking to e2yxyxyx.eyx.ayx.gyx.com.:
<<< 554 CXYYXYX.eyx.ayx.gyx.com
554 5.0.0 Service unavailable

--v338nDQN011631.1491209353/vdyxyxyx.yxy.clyxyx.gyx.com
Content-Type: message/delivery-status

Reporting-MTA: dns; vdyxyxyx.yxy.clyxyx.gyx.com
Received-From-MTA: DNS; localhost
Arrival-Date: Mon, 3 Apr 2017 04:49:13 -0400

Final-Recipient: RFC822; devipriya.ch@gyx.com
Action: failed
Status: 5.5.0
Diagnostic-Code: SMTP; 554 CIYXYXYX.eyx.ayx.gyx.com
Last-Attempt-Date: Mon, 3 Apr 2017 04:49:13 -0400

something is wrong because its working fine for another server. This is only having some problem that too mail status showing working properly but unable to receive mails. please suggest.

This is the last time I clear your private data for you. Please be aware that publicly posting host names and / or e-mail addresses may result in undesired results.

And, SERIOUSLY, start using code tags for code and data!

Hi,

One thing before going any further - you might want to think about sanitising your log entries before you post them. Posting working e-mail addresses, public IPs and internal hostnames that might give away details about your infrastructure to random folk on the Internet could potentially be something of a security risk. For example, I'm hoping that from that hostname your mail gateway isn't really running Exchange 2000 in this day and age, for instance

In any case: you'll need to now check the mail logs on the upstream mail server (the one whose hostname begins with e2ksmtp01) to see why it returned a 554 error to your Linux box. From just the 554 error on its own it's hard to say exactly what's going on here, but my guess would be that e2ksmtp01 isn't configured to accept mail from your Linux box, and is rejecting it for some reason.

That's the name of the game with SMTP debugging really: keep following the mail trail until you find the server that actually rejected the message, and then you'll hopefully find out why and what to do about it.