Sponsored Content
Full Discussion: Unable to telnet
Operating Systems Solaris Unable to telnet Post 302132415 by *Jess* on Thursday 16th of August 2007 11:38:17 PM
Old 08-17-2007
Problem is not solved yet. Still checking why it fails.
 

10 More Discussions You Might Find Interesting

1. IP Networking

Unable to telnet into the Sun server

I tried to telnet to my Sun server (E250) but I received the error message : "Network error: Connection reset by peer". I was able to ping my server. And, I had already commented off "CONSOLE=/dev/console" in /etc/default/login. But, if I rlogin from all other servers, it works. Is there... (2 Replies)
Discussion started by: dawn_lwf
2 Replies

2. UNIX for Dummies Questions & Answers

Unable to telnet from SunOS 5.6 Server

:cool: I need some assistance please. I'm setting up a SunOS 5.6 server and sofar I'm able to telnet into the unit but unable to telnet from it. Can anyone help me with this problem. When attempting to telnet from my SunOs to client terminal I'm receving the following error, "Unable to connect to... (3 Replies)
Discussion started by: sharris82
3 Replies

3. HP-UX

Unable to login at console and telnet

Hi friend, I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var? thanks. vestro (1 Reply)
Discussion started by: vestro
1 Replies

4. AIX

Unable to telnet to server

Hi, I encountered error when I telnet to my server. Error is as follows: telnetd: /bin/login: The file access permissions do not allow the specified action I am able to ssh into my server and I have checked/verified /etc/security and /etc/inetd.conf. I restarted the inetd subsystem via... (1 Reply)
Discussion started by: chongkls77
1 Replies

5. UNIX for Dummies Questions & Answers

Unable to Telnet

Dear All, I have Compaq Alpha server running UNIX OS. with Old Hardware specification. I had FTP conncetion using IP Switch ( FTP client ) to the Unix server in order to copy some files to my workstation. one day after closing the connection we noted that IT operations are not able to... (8 Replies)
Discussion started by: Arehan
8 Replies

6. SuSE

Unable to telnet (non-ssh) as root

Hi forum, I face a strange issue. I'm able to telnet as root with ssh. But I'm not able to telnet (non-ssh) as root to my Suse 10 machine. Can someone please point to significant files where I need to make changes for Suse 10 machine and resolve this issue. Thanks in advance. (2 Replies)
Discussion started by: anilgurwara
2 Replies

7. UNIX for Dummies Questions & Answers

Unable to telnet

Hi, I have two linux boxes and due to some reasons I have reinstalled OS in one of them. Now Iam unable to telnet one of them. I have included entries in /etc/hosts in both and Iam able to ping each other. Am I missing anything here or I we need to install/activate telnet server ? Thanks... (2 Replies)
Discussion started by: ssuhaib
2 Replies

8. Shell Programming and Scripting

Unable to close telnet session from script

Hello people, I am creating a script that will alert me in an ftp or telnet account on my system expires. FTP part is ok, but when I am entering the 3 script, it stucks. I can see that the script will not close the telnet seession. Can you please check and let me know what I am doing wrong? What if... (7 Replies)
Discussion started by: drbiloukos
7 Replies

9. Solaris

Unable to Telnet por 143 (IMAP)

Hello. I Need Some Help. I'm trying to telnet the IMAP port (to verify if is open). telnet myserver 143, but im getting this error: Connection closed by foreign host. The /var/log/syslog shows me following: imapd: error: cannot execute /usr/sbin/imapd: No such file or directory netstat... (3 Replies)
Discussion started by: rcruz
3 Replies

10. Shell Programming and Scripting

Unable to automate telnet login

i have to connect windows server from one of the unix box so i am using telnet and below is my following code #!/bin/sh host=hostname log=loginid port=23 pass=password cmd1=mkdir test1234 ( echo open ${host} ${port} sleep 1 echo ${log} sleep 3 echo "\r\n" sleep 3 echo ${pass}... (11 Replies)
Discussion started by: chandan.p
11 Replies
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)
All times are GMT -4. The time now is 07:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy