Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
To be honest I don't know if I'm in the correct section for this subject but I think this is most relevant.
My question is about mailing with sendmail which won't work. I have seen some other topics about this subject but because I'm pretty new to Linux so I thought of opening a new threat because I'm not getting any further with the other topics.
I have a server where I try to send mails from but that won't work.
As I don't know exactly where to look for I shall try to be as clear as possible
From MAILER-DAEMON@aseg04 Mon Jan 23 14:49:07 2012
Date: Mon, 23 Jan 2012 14:49:07 +0100
From: Mail Delivery Subsystem <MAILER-DAEMON@aseg04>
To: <root@localhost.localdomain>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="q0NDn70f006835.1327326547/aseg04"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--q0NDn70f006835.1327326547/aseg04
The original message was received at Mon, 23 Jan 2012 14:49:07 +0100
from localhost.localdomain [127.0.0.1]
----- The following addresses had permanent fatal errors -----
<******@gmail.com>
(reason: 550 Host unknown)
----- Transcript of session follows -----
550 5.1.2 <******@gmail.com>... Host unknown (Name server: 172.30.2.13: host not found)
Return-Path: <root@localhost.localdomain>
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
by aseg04 (8.13.8/8.13.8) with ESMTP id q0NDn70f006833
for <******@gmail.com>; Mon, 23 Jan 2012 14:49:07 +0100
Received: (from root@localhost)
by localhost.localdomain (8.13.8/8.13.8/Submit) id q0NDn1fh006832
for ******@gmail.com; Mon, 23 Jan 2012 14:49:01 +0100
Date: Mon, 23 Jan 2012 14:49:01 +0100
From: root <root@localhost.localdomain>
Message-Id: <201201231349.q0NDn1fh006832@localhost.localdomain>
test mail again
I am aware that these 2 are pieces of data are not the same. That is because I'm not able to find the mail on the server anymore because the mailbox of user root contains over 70000 mails But they cover the same issue.
But anyway I hope this gives enough information to help me solve the problem.
Is there please somebody who can help me with this?
You need to check and get your DNS working before you think about sorting out your mails.
Try the following
Code:
nslookup www.google.com
and you'll probably get an error message.
Check your /etc/resolv.conf and check that it's pointing to valid name servers.
Check your firewall to ensure that outbound DNS queries aren't getting blocked.
Then when you can do that try
Code:
dig mx google.com
and ensure you get something like the following back:
Code:
# dig mx google.com
; <<>> DiG 9.5.0b2 <<>> mx google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61978
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 9
;; QUESTION SECTION:
;google.com. IN MX
;; ANSWER SECTION:
google.com. 600 IN MX 30 alt2.aspmx.l.google.com.
google.com. 600 IN MX 40 alt3.aspmx.l.google.com.
google.com. 600 IN MX 50 alt4.aspmx.l.google.com.
google.com. 600 IN MX 10 aspmx.l.google.com.
google.com. 600 IN MX 20 alt1.aspmx.l.google.com.
;; AUTHORITY SECTION:
google.com. 11045 IN NS ns3.google.com.
google.com. 11045 IN NS ns4.google.com.
google.com. 11045 IN NS ns1.google.com.
google.com. 11045 IN NS ns2.google.com.
;; ADDITIONAL SECTION:
aspmx.l.google.com. 293 IN A 209.85.229.27
alt1.aspmx.l.google.com. 293 IN A 173.194.69.27
alt2.aspmx.l.google.com. 293 IN A 209.85.137.27
alt3.aspmx.l.google.com. 293 IN A 74.125.127.27
alt4.aspmx.l.google.com. 293 IN A 74.125.81.27
ns1.google.com. 80317 IN A 216.239.32.10
ns2.google.com. 80317 IN A 216.239.34.10
ns3.google.com. 80317 IN A 216.239.36.10
ns4.google.com. 80317 IN A 216.239.38.10
;; Query time: 30 msec
;; SERVER: 172.29.143.19#53(172.29.143.19)
;; WHEN: Mon Jan 23 15:51:55 2012
;; MSG SIZE rcvd: 352
;; ANSWER SECTION:
google.com. 350 IN MX 50 alt4.aspmx.l.google.com.
google.com. 350 IN MX 20 alt1.aspmx.l.google.com.
google.com. 350 IN MX 10 aspmx.l.google.com.
google.com. 350 IN MX 30 alt2.aspmx.l.google.com.
google.com. 350 IN MX 40 alt3.aspmx.l.google.com.
;; ADDITIONAL SECTION:
alt4.aspmx.l.google.com. 43 IN A 74.125.81.27
alt1.aspmx.l.google.com. 43 IN A 173.194.69.27
aspmx.l.google.com. 43 IN A 173.194.67.27
alt2.aspmx.l.google.com. 43 IN A 209.85.137.27
alt3.aspmx.l.google.com. 43 IN A 74.125.127.27
Hmm, strange, is it ALL e-mails that are problematic or only certain domains? Are you attempting direct e-mail delivery or through an intermediate smarthost?
Hmm, only difference I can see is that your mailer looks like it's looking at 172.30.2.13 for DNS lookups and your other lookups were done at 172.30.2.40
Check that /etc/nsswitch.conf has a line that begins hosts: and has dns on the line, also check /etc/resolv.conf to ensure that 172.30.2.40 is listed as a nameserver, alternatively post those files here.
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
# nisplus or nis+ Use NIS+ (NIS version 3)
# nis or yp Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files
# compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far
#
# To use db, put the "db" in front of "files" for entries you want to be
# looked up first in the databases
#
# Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Host unknown
