10-08-2004
Thanks, Hassan2...
Problem resolved!
9 More Discussions You Might Find Interesting
1. SCO
I installed Openserver 5.0.7 and I cannot telnet to the localhost and I can't telnet from my old SCO 3.2.42 to the new SCO machine but I can ping the new machine and it will telnet to the old machine. (2 Replies)
Discussion started by: printrick
2 Replies
2. Shell Programming and Scripting
Hi everyone,
I am having a problem in the following area:
I want to arrange list of Ip Addresses selected from a multiple files and make it look like this:
"IP=192.168.0.1, hostname=snake.cooliris.com"
Now i have already written the code to select the ip address from various files but... (4 Replies)
Discussion started by: snake450
4 Replies
3. UNIX for Advanced & Expert Users
Originally I had the server at home and on Comcast so I used dyndns.org for DNS.
Once the server got a bit more popular, I leased a server at a colo facility. They set up the server name in their DNS so I didn't really have any reason to manage my own DNS. DynDNS was managing the domains and I... (7 Replies)
Discussion started by: BOFH
7 Replies
4. UNIX for Advanced & Expert Users
Folks...have just stumbled on an issue where DNSstuff says there is no reverse dns in place when there is...as evidenced by a reverse check from 3 diff networks.
Any advice why this would be happening (DNSstuff-wise) would be appreciated.
Jordan:
jsd@standby:~$ host 12.177.133.70... (3 Replies)
Discussion started by: jsd
3 Replies
5. IP Networking
Hello, I'm trying to get reverse dns to point to my domain on network but I'm failing. I am using bind dns with port 53 enabled and my ISP is mediacom. Currently my reverse dns is *.client.mchsi.com and I would like to make it example.com basically.
My bind configuration
I have 2 records, one... (4 Replies)
Discussion started by: GRMrGecko
4 Replies
6. AIX
Hi,
After a crash of our older AIX server it happend as it is in the title:
ping is ok, but telnet:
What it can be this strange thing?
Franci (2 Replies)
Discussion started by: frajer
2 Replies
7. Linux
Hi all,
i got stuck with telnet issue, I am not able to telnet on 4001 port it show connection refused.
with default port it will open
# telnet 127.0.0.1
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Fedora release 14 (Laughlin)
Kernel 2.6.35.6-45.fc14.i686 on... (1 Reply)
Discussion started by: muzaffar.k
1 Replies
8. Shell Programming and Scripting
Hi All,
I am using the below script to get some files from the remote location
HOST='Test03'
USER='root'
PASSWD='*****'
FILE='/home/user/d.txt'
ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
get $FILE
quit
END_SCRIPT
exit 0
But ist is giving me the... (3 Replies)
Discussion started by: sharsour
3 Replies
9. Red Hat
Hi guys. Ok so let me lay out my configs. I can do a NSlookup from client to server BUT NOT a reverse lookup.
DNS server: Optimus.jaydomain.com
IP : 192.168.1.50
DNS Client: Megatron.jaydomain.com
IP : 192.168.1.60
On Sever:
# cat /etc/named.conf
//
// named.conf
//
// Provided... (4 Replies)
Discussion started by: Junaid Subhani
4 Replies
LEARN ABOUT HPUX
qmail-queue
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)