Unable to find FEATURE(`msp',`[127.0.0.1]')dnl in submit.cf


 
Thread Tools Search this Thread
Operating Systems Solaris Unable to find FEATURE(`msp',`[127.0.0.1]')dnl in submit.cf
# 1  
Old 09-04-2007
Unable to find FEATURE(`msp',`[127.0.0.1]')dnl in submit.cf

Hi,

While trying to send mail using the mailx command i get the below mentioned error.

sdsddsd... Connecting to [127.0.0.1] via relay...
sdsddsd... Deferred: Connection refused by [127.0.0.1]

I went through some documents and it was mentioned that modifications needs to be done in submit.cf as given below.

define(`SMART_HOST', `your.smtp.server.')dnl
define(`MAIL_HUB',`your.smtp.server.')dnl
define(`LOCAL_RELAY',`your.smtp.server')dnl

prior to the line that says:
FEATURE(`msp',`[127.0.0.1]')dnl

But I am not able to see anything like FEATURE(`msp',`[127.0.0.1]')dnl . Please let me know from where is the localhost Ip taken and what should be done to send mail successfully. Kindly help.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Unable to find package

Hi there. I'm putting together a small cluster of Raspberry pis running Raspbian. They've all been setup identically from the same sd image. They all update and install perfectly except one node which refuses to install anything. It has exactly the same login, network, user details etc,... (3 Replies)
Discussion started by: MuntyScrunt
3 Replies

2. IP Networking

127.0.0.1 vs 0.0.0.0

Which one should I use in '/etc/hosts'? Please explain in details. Random quotes on the topic: (2 Replies)
Discussion started by: useretail
2 Replies

3. UNIX for Dummies Questions & Answers

Unable to find the history file

Hi friends, I am unable to find the .sh_history file on my PC. This files contains the log of all commands typed by the users. I searched it also , but no results. Please help me :(, where to find it . Or is there anything else to do to set the history file. (6 Replies)
Discussion started by: paras.oriental
6 Replies

4. UNIX for Advanced & Expert Users

wait - return code 127

Hi All, I am trying to create background processes and then check their status later. But I am getting return codes as 0,127 randomly On checking the return codes for wait, I found the below. Do I need to treat return code of 127 as successful as well?? as we know the process id passed is... (7 Replies)
Discussion started by: tostay2003
7 Replies

5. Solaris

multitude of packets from 127.0.0.1

I was checking routing table, and noticed that our server has a lot packets from localhost: Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- .. 127.0.0.1 127.0.0.1 ... (1 Reply)
Discussion started by: orange47
1 Replies

6. Solaris

Unable to find 8 gb of memory

I 've one box with 16gb of RAM and top, vmstat showing 8712M free , i 'm unable to find which process is eating up rest of the memory , the system is not running anything at the moment. (14 Replies)
Discussion started by: fugitive
14 Replies

7. AIX

Find the feature code of the installed processor card on my p550

Guys Does anyone know how to find the feature code of the installed processor card on my p550? Through AIX or HMC. Basically I need to find the processor card type. Thanks in advance Bala (2 Replies)
Discussion started by: balaji_prk
2 Replies

8. Solaris

Can't setup gateway other than 127.0.0.1?

I have just installed Solaris 10 X86 today, but I can't use internet at all on it. When I was installing it, it only asked me to create a hostname, without even asking me this computer is "networked" or "non-networked". After I finished installation, I use "netstat -rn" command, and only see... (3 Replies)
Discussion started by: Diamondust
3 Replies

9. Shell Programming and Scripting

rc=127 can't fork

I have a script to download a file using wget. It works if I execute it from the command line. But, if I run it in cron, it doesnt work and I am getting the following in the cron log: > CMD: /export/home/username/test > username 23159 c Tue Aug 1 14:40:00 2006 < username 23159 c Tue Aug ... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
Login or Register to Ask a Question
qmail-queue(8)						      System Manager's Manual						    qmail-queue(8)

NAME
qmail-queue - queue a mail message for delivery SYNOPSIS
qmail-queue DESCRIPTION
qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. It places the message into the outgoing queue for future delivery by qmail-send. The envelope information is an envelope sender address followed by a list of envelope recipient addresses. The sender address is preceded by the letter F and terminated by a 0 byte. Each recipient address is preceded by the letter T and terminated by a 0 byte. The list of recipient addresses is terminated by an extra 0 byte. If qmail-queue sees end-of-file before the extra 0 byte, it aborts without placing the message into the queue. Every envelope recipient address should contain a username, an @ sign, and a fully qualified domain name. qmail-queue always adds a Received line to the top of the message. Other than this, qmail-queue does not inspect the message and does not enforce any restrictions on its contents. However, the recipients probably expect to see a proper header, as described in qmail-header(5). Programs included with qmail which invoke qmail-queue will invoke the contents of $QMAILQUEUE instead, if that environment variable is set. FILESYSTEM RESTRICTIONS
qmail-queue imposes two constraints on the queue structure: each mess subdirectory must be in the same filesystem as the pid directory; and each todo subdirectory must be in the same filesystem as the intd directory. EXIT CODES
qmail-queue does not print diagnostics. It exits 0 if it has successfully queued the message. It exits between 1 and 99 if it has failed to queue the message. All qmail-queue error codes between 11 and 40 indicate permanent errors: 11 Address too long. 31 Mail server permanently refuses to send the message to any recipients. (Not used by qmail-queue, but can be used by programs offering the same interface.) All other qmail-queue error codes indicate temporary errors: 51 Out of memory. 52 Timeout. 53 Write error; e.g., disk full. 54 Unable to read the message or envelope. 55 Unable to read a configuration file. (Not used by qmail-queue.) 56 Problem making a network connection from this host. (Not used by qmail-queue.) 61 Problem with the qmail home directory. 62 Problem with the queue directory. 63 Problem with queue/pid. 64 Problem with queue/mess. 65 Problem with queue/intd. 66 Problem with queue/todo. 71 Mail server temporarily refuses to send the message to any recipients. (Not used by qmail-queue.) 72 Connection to mail server timed out. (Not used by qmail-queue.) 73 Connection to mail server rejected. (Not used by qmail-queue.) 74 Connection to mail server succeeded, but communication failed. (Not used by qmail-queue.) 81 Internal bug; e.g., segmentation fault. 91 Envelope format error. SEE ALSO
addresses(5), envelopes(5), qmail-header(5), qmail-inject(8), qmail-qmqpc(8), qmail-send(8), qmail-smtpd(8) qmail-queue(8)