Sponsored Content
Operating Systems Linux Red Hat Sendmail saying "user unknown" after setting up MX Post 302664731 by Rohit Bhanot on Saturday 30th of June 2012 10:54:34 AM
Old 06-30-2012
Sendmail saying "user unknown" after setting up MX

Hi Friends,

I set up the sendmail in my perosnal home lab. I am using mutt to send the email in between the machines. Everything is working fine if i send email like <username>@<hostname>. Now i set up the MX record for my domain "home.com" and then i was trying to send the email to like root@home.com, but in this case as soon as i press "Y" to send the email in mutt; i get this error
Code:
Error sending message, child exited 67 (User unknown.)

Even in the sendmail logs it shows user known. I know that my sendmail was not configured to accept message from the domain home.com, so i added the home.com to /etc/mail/local-host-names file but still this error remains. It is weird and i assume i should get a delivery failure with something saying like "relaying rejected"

So can anyone please help me figuring out what is going on here ?>
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

unknown error message "sh: No: not found"

I am getting this error message (sh: No: not found) and I have no idea what line in my unix script its coming from or what it means. Can anyone help? thanks, Cindy (2 Replies)
Discussion started by: cindytucci
2 Replies

2. Shell Programming and Scripting

communicating wth another user aside from "wall" and "write"

Hi, Can anyone suggest a Unix command or c-shell algorithm to simulate to behavior of "wall" command minus the "all users"? What I'm trying to do is to send a notice to just one particular user but i dont want other remotely-logged-on users to receive the message (on the pseudo-terminals). I... (6 Replies)
Discussion started by: Deanne
6 Replies

3. Solaris

sendmail "root... User address required." error

I'm running sendmail (8.13.8+Sun/8.13.8/Submit) solaris 10. When I send mail to root at the command line (whether I use a full-qualified address or just root), I get the error message root... User address required. Sending mail to root (either at the command line or in a cron job),... (10 Replies)
Discussion started by: csgonan
10 Replies

4. Shell Programming and Scripting

awk command to replace ";" with "|" and ""|" at diferent places in line of file

Hi, I have line in input file as below: 3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL My expected output for line in the file must be : "1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL" Can someone... (7 Replies)
Discussion started by: shis100
7 Replies

5. UNIX for Advanced & Expert Users

Sendmail: how to restrict delivery based on "to" or "from"?

Hello, I manage a large sendmail server that handles more than 20,000 pieces of mail per day. It's a bit unusual in that all this mail is only being sent to and from 4 local accounts. (It's an automated transaction processing system, whereby users submit a transaction via email attachment). ... (2 Replies)
Discussion started by: lupin..the..3rd
2 Replies

6. Solaris

Unknown Disks "offline or reservation conflict"

Hi All, I am a RH Linux admin that recently started working at a company with a number of SUN Servers so it's been an interesting transition. Considering the last person left with very little documentation left behind so I have been picking up most issues half complete, or troubleshot. ... (7 Replies)
Discussion started by: MobileGSP
7 Replies

7. UNIX for Dummies Questions & Answers

What is the significance of sh -s in ssh -qtt ${user}@${host} "sh -s "${version}"" < test.sh?

Please can you help me understand the significance of providing arguments under sh -s in > ssh -qtt ${user}@${host} "sh -s "${version}"" < test.sh (4 Replies)
Discussion started by: Sree10
4 Replies

8. Shell Programming and Scripting

Bash script - Print an ascii file using specific font "Latin Modern Mono 12" "regular" "9"

Hello. System : opensuse leap 42.3 I have a bash script that build a text file. I would like the last command doing : print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt where : print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
NMUDIFF(1)                                                    General Commands Manual                                                   NMUDIFF(1)

NAME
nmudiff - email an NMU diff to the Debian BTS SYNOPSIS
nmudiff [options] DESCRIPTION
nmudiff should be run in the source tree of the package being NMUed, after the NMU is built. It assumes that the source packages (specifi- cally, the .dsc and any corresponding tar and diff files) for both the previous version of the package and the newly built NMU version are in the parent directory. It then uses debdiff to generate a diff between the previous version and the current NMU, and either runs mutt or an editor (using sensible-editor) so that the mail message (including the diff) can be examined and modified; once you exit the editor the diff will be mailed to the Debian BTS. The default behaviour is that if exactly one bug is closed by this NMU, then that bug will be mailed, otherwise a new bug will be submit- ted. This behaviour may be changed by command line options and configuration file options. OPTIONS
--new Instead of mailing the bug reports which are to be closed by this NMU, a new bug report is submitted directly to the BTS. --old Send the bug report to all of the bugs which are being closed by this NMU, rather than opening a new bug report. This option has no effect if no bugs are being closed by this NMU. --mutt Use mutt(1) for editing and sending the message to the BTS (default behaviour). This can be controlled using a configuration file option (see below). --no-mutt Use sensible-editor(1) to edit the message and then mail it directly using /usr/bin/sendmail. This can be controlled using a con- figuration file option (see below). --sendmail SENDMAILCMD Specify the sendmail command. The command will be split on white space and will be interpreted by the shell. Default is /usr/sbin/sendmail. The -t option will be automatically added if the command is /usr/sbin/sendmail or /usr/sbin/exim*. For other mailers, if they require a -t option, this must be included in the SENDMAILCMD, for example: --sendmail="/usr/sbin/mymailer -t". This can also be set using the devscripts configuration files; see below. --from EMAIL If using the sendmail (--no-mutt) option, then the email to the BTS will be sent using the name and address in the environment vari- ables DEBEMAIL and DEBFULLNAME. If these are not set, then the variables EMAIL and NAME will be used instead. These can be over- ridden using the --from option. The program will not work in this case if an email address cannot be determined. --delay DELAY Indicate in the generated mail that the NMU has been uploaded to the DELAYED queue, with a delay of DELAY days. The default value is XX which adds a placeholder to the e-mail. A value of 0 indicates that the upload has not been delayed. This can also be set using the devscripts configuration files; see below. --no-delay, --nodelay Equivalent to --delay 0. --no-conf, --noconf Do not read any configuration files. This can only be used as the first option given on the command-line. --help Display a help message and exit successfully. --version Display version and copyright information and exit successfully. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are: NMUDIFF_DELAY If this is set to a number, e-mails generated by nmudiff will by default mention an upload to the DELAYED queue, delayed for the specified number of days. The value 0 indicates that the DELAYED queue has not been used. NMUDIFF_MUTT Can be yes (default) or no, and specifies whether to use mutt to compose and send the message or not, as described above. NMUDIFF_NEWREPORT This option controls whether a new bug report is made, or whether the diff is sent to the bugs closed by this NMU. Can be maybe (default), which sends to the existing bug reports if exactly one bug is being closed; yes, which always creates a new report, or no, which always sends to the reports of the bugs being closed (unless no bugs are being closed, in which case a new report is always made). BTS_SENDMAIL_COMMAND If this is set, specifies a sendmail command to use instead of /usr/sbin/sendmail. Same as the --sendmail command line option. SEE ALSO
debdiff(1), sensible-editor(1) and devscripts.conf(5). AUTHOR
nmudiff was written and is copyright 2006 by Steinar H. Gunderson and modified by Julian Gilbey <jdg@debian.org>. The software may be freely redistributed under the terms and conditions of the GNU General Public License, version 2. DEBIAN Debian Utilities NMUDIFF(1)
All times are GMT -4. The time now is 01:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy