• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2066
  • Last Modified:

Sendmail - DSN: service Unavaiable

Hi experts. I'm getting the following message when i tried to sent an email. The email is not sent.
Mar 30 16:22:39 ded1021-deb-162-21 sm-mta[3218]: starting daemon (8.14.3): SMTP+queueing@00:10:00
Mar 30 16:22:47 ded1021-deb-162-21 sendmail[3237]: o2ULMl9b003237: from=root, size=47, class=0, nrcpts=1, msgid=<201003302122.o2ULMl9b003237@ded1021-deb-162-21.netsonic.net>, relay=root@localhost
Mar 30 16:22:47 ded1021-deb-162-21 sm-mta[3238]: o2ULMlFp003238: from=<root@ded1021-deb-162-21.netsonic.net>, size=377, class=0, nrcpts=1, msgid=<201003302122.o2ULMl9b003237@ded1021-deb-162-21.netsonic.net>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1] (may be forged)
Mar 30 16:22:47 ded1021-deb-162-21 sendmail[3237]: o2ULMl9b003237: to=pthao@nuterrallc.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30047, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (o2ULMlFp003238 Message accepted for delivery)
Mar 30 16:22:47 ded1021-deb-162-21 sm-mta[3240]: STARTTLS=client, relay=mx1.emailsrvr.com., version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
Mar 30 16:22:47 ded1021-deb-162-21 sm-mta[3240]: o2ULMlFp003238: to=<pthao@nuterrallc.com>, ctladdr=<root@ded1021-deb-162-21.netsonic.net> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=120377, relay=mx1.emailsrvr.com. [98.129.184.3], dsn=5.7.1, stat=Service unavailable
Mar 30 16:22:47 ded1021-deb-162-21 sm-mta[3240]: o2ULMlFp003238: o2ULMlFp003240: DSN: Service unavailable
Mar 30 16:22:47 ded1021-deb-162-21 sm-mta[3240]: o2ULMlFp003240: to=netsonic, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30000, dsn=2.0.0, stat=Sent

Open in new window

0
infernothao
Asked:
infernothao
  • 8
  • 7
1 Solution
 
infernothaoAuthor Commented:
When I did a nslookup MyHostName, it says that it can't find MyHostName.
0
 
Jan SpringerCommented:
Please post your /etc/mail/sendmail.mc, /etc/hosts file, /etc/resolv.conf.

Also
  netstat -an | grep ":25"
  netstat -an | grep ":53
0
 
infernothaoAuthor Commented:
Thanks for answering Jesper. Here are the info.
# netstat -an | grep ".25"
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN
unix  2      [ ]         DGRAM                    2518     @/org/kernel/udev/udevd

# netstat -an | grep ".53"
tcp        0      0 66.180.162.21:22        67.53.79.202:51065      ESTABLISHED
tcp        0     52 66.180.162.21:22        67.53.79.202:53436      ESTABLISHED
tcp        0      0 66.180.162.21:22        67.53.79.202:50999      ESTABLISHED

Open in new window

sendmail
hosts
resolv
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
Jan SpringerCommented:
sendmail.mc l ine 57:

      DAEMON_OPTIONS(`Family=inet,  Name=MTA-v4, Port=smtp, Addr=127.0.0.1')dnl

Either get rid of the Addr=127.0.0.1 or change 127.0.0.1 to 66.180.162.21

Then:
   make -C /etc/mail
   restart sendmail
0
 
infernothaoAuthor Commented:
I removed "Addr=127.0.0.1" from sendmail.mc, make -C /etc/mail, /etc/init.d reload. But I still get the same error.
0
 
Jan SpringerCommented:
telnet mx1.emailsrvr.com 25
<wait for banner>
ehlo netsonic.net
<wait for response>
mail from: <root@ded1021-deb-162-21.netsonic.net>
<wait for ok>
rcpt to: <pthao@nuterrallc.com>
<wait for ok>
data
this is a test
.
quit

Somewhere in that dialog, you should see the error perhaps with more clarification.
0
 
infernothaoAuthor Commented:
Hi Jesper, here is what I get.
/# telnet mx1.emailsrvr.com 25
Trying 98.129.184.3...
Connected to mx1.emailsrvr.com.
Escape character is '^]'.
220 mx1.emailsrvr.com ESMTP - (gate36.gate.dfw.mlsrvr.com) VA Code Section 18.2-152.3:1 forbids sending spam through this system
421 4.4.2 gate36.gate.dfw.mlsrvr.com Error: timeout exceeded
Connection closed by foreign host.


/# ehlo netsonic.net
-bash: ehlo: command not found
Daedalus:/# echo netsonic.net
netsonic.net


# mail from: <root@ded1021-deb-162-21.netsonic.net>
-bash: syntax error near unexpected token `newline'

Open in new window

0
 
Jan SpringerCommented:
When you see this:

    220 mx1.emailsrvr.com ESMTP - (gate36.gate.dfw.mlsrvr.com) VA Code Section 18.2-152.3:1 forbids sending spam through this system

You need to type this:

    ehlo netsonic.net


The commands listed above (excluding those inside the <>) are mail commands and need to be typed in while you are engaged in a conversation with the mail server.  They are not bash commands.  This mail server has a short timeout period so you need to be ready to type once you get a response.
0
 
infernothaoAuthor Commented:
Sorry, I'm new to this kind of stuff. Below is what I get.
# telnet mx1.emailsrvr.com 25
Trying 98.129.184.3...
Connected to mx1.emailsrvr.com.
Escape character is '^]'.
220 mx1.emailsrvr.com ESMTP - (gate36.gate.dfw.mlsrvr.com) VA Code Section 18.2-152.3:1 forbids sending spam through this system
ehlo netsonic.net
250-gate36.gate.dfw.mlsrvr.com
250-PIPELINING
250-SIZE 75000000
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250 8BITMIME
mail from: <root@ded1021-deb-162-21.netsonic.net>
250 2.1.0 Ok
rcpt to: <pthao@nuterrallc.com>
554 5.7.1 ACL dns_rbl; Client host [66.180.162.21] blocked using pf-ip4tset.blagr.emailsrvr.com=127.26.0.2
data
554 5.5.1 Error: no valid recipients
421 4.7.0 gate36.gate.dfw.mlsrvr.com Error: too many errors
Connection closed by foreign host.

Open in new window

0
 
infernothaoAuthor Commented:
I tried with a different rcpt email and this is what I get.
# telnet mx1.emailsrvr.com 25
Trying 98.129.185.3...
Connected to mx1.emailsrvr.com.
Escape character is '^]'.
220 mx1.emailsrvr.com ESMTP - (gate14.gate.dfw.mlsrvr.com) VA Code Section 18.2-152.3:1 forbids sending spam through this system
ehlo netsonic.net
250-gate14.gate.dfw.mlsrvr.com
250-PIPELINING
250-SIZE 75000000
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250 8BITMIME
mail from: <root@ded1021-deb-162-21.netsonic.net>
250 2.1.0 Ok
rcpt to: <thaopeter25@gmail.com>
550 5.7.1 <thaopeter25@gmail.com>: Relay access denied
data
554 5.5.1 Error: no valid recipients
421 4.7.0 gate14.gate.dfw.mlsrvr.com Error: too many errors
Connection closed by foreign host.

Open in new window

0
 
Jan SpringerCommented:
Your IP is blacklisted from sending to pthao:


554 5.7.1 ACL dns_rbl; Client host [66.180.162.21] blocked using pf-ip4tset.blagr.emailsrvr.com=127.26.0.2


And which is odd since I did not find your IP address on any public blacklists.  Contact emailsrvr.com to see if you can get delisted.
0
 
Jan SpringerCommented:
This message:

550 5.7.1 <thaopeter25@gmail.com>: Relay access denied

means that you cannot use emailsrvr.com to send email to someone that is not local to that mail server.

To send email to a gmail account, you would need to test by telneting to gmail's mx server port 25.
0
 
infernothaoAuthor Commented:
I'm not really sure what is wrong. Our current server, which uses sendmail also, seems to be working fine. I send an email on our current server and it works fine. I'm trying to install sendmail on our new server which it is giving me error and it just doesn't make sense.
0
 
Jan SpringerCommented:
The new server is using 66.180.162.21?  That is the message from the server that says blacklisted:

554 5.7.1 ACL dns_rbl; Client host [66.180.162.21] blocked using pf-ip4tset.blagr.emailsrvr.com=127.26.0.2

And paying attention, it appears to be a local blacklist.  First contact emailsrvr.com and ask them to remove that IP from its blacklist and test again.
0
 
infernothaoAuthor Commented:
You' are right Jesper. Actually it's not Emailsrvr.com but our other email provider. Anyway, we whitelist it and it seems to work. Thanks a lot Jesper.
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

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