Sponsored Content
Full Discussion: FTP problem. please help
Top Forums UNIX for Dummies Questions & Answers FTP problem. please help Post 34199 by TRUEST on Saturday 8th of February 2003 03:48:53 PM
Old 02-08-2003
why wouldn't root be allowed to ftp? isn't root the god of unix??
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

ftp problem

I use FTP in a shell script to transfer the files to a remote server. Sometimes the program hangs without returning any errors after the command ftp server_name How do you detect from within the shell that something is wrong? How do you trap the errors returned by ftp command? Any help... (3 Replies)
Discussion started by: marusia
3 Replies

2. Shell Programming and Scripting

Ftp problem

hi i have written a shell to automate the ftp process for the particular file.iam getting errors when try to ftp it.And i am cant get why the lcd is not being taken properly as it is taking during runtime.can anyone give me a solution here its my code DATE=`date '+%d_%m_%Y'`... (1 Reply)
Discussion started by: cskumar
1 Replies

3. Solaris

FTP problem

Hi Guys, Got problem when I tried to get files from Solaris server to my PC. The connection transfer was using FTP and the connection was made from the solaris server to my PC. Here's what happened when the file transfer being made: # ftp 10.192.23.230 Connected to 10.192.23.230. 220... (9 Replies)
Discussion started by: raskita
9 Replies

4. HP-UX

FTP problem

We recently moved offices and checked our network ID. I have configured all the files that I am familiar with and am able to telnet and ping from my pc but I am unable to ftp. Any suggestions...Thanks (5 Replies)
Discussion started by: andrewd
5 Replies

5. Shell Programming and Scripting

problem with ftp:

i have got 2 servers in unix(IBM AIX 5.3) namely below. test1 production1 i m trying to do ftp from test1 to production1. ------------------------------------------------------------ below the script called naveed1.sh which lies in test1,also it have two files called ... (2 Replies)
Discussion started by: ali560045
2 Replies

6. Shell Programming and Scripting

problem in FTP

i m able to login to Unix box from window's cmd can anyone tell me how to run a script from window cmd using ftp ? the script is in unix box and i need to run from windows CMD using ftp (2 Replies)
Discussion started by: ali560045
2 Replies

7. Shell Programming and Scripting

FTP Problem

Hello experts, I've got the following script that is supposed to FTP a file to another box. #!/usr/bin/ksh while read line do HOST=`echo "$line" | cut -d" " -f1` USER=`echo "$line" | cut -d" " -f2` PASSWD=`echo "$line" | cut -d" " -f3` PATH=`echo "$line" | cut -d" " -f4` done <... (5 Replies)
Discussion started by: King Nothing
5 Replies

8. Shell Programming and Scripting

ftp problem

Hello, I have a very simple script that put a file in server ftp #!/bin/bash var="ITW-trail-templiers-samedi" cd /Users/$USER/Desktop ftp -n >&1 << EOF open server quote user "user" cd oberon binary put "$var" bye EOF I have error : 200 Type set to IMAGE. remote:... (2 Replies)
Discussion started by: protocomm
2 Replies

9. Red Hat

ftp problem?

Dear All I cannot ftp to my RedHat server from MS Windows machine ,but ping and telnet are ok. I checked as the following : #chkconfig tftp on #setup After enabling tftp service, still the ftp is not ok but ping & telnet are ok. Can you please help me? Thank you (8 Replies)
Discussion started by: hadimotamedi
8 Replies

10. Shell Programming and Scripting

Ftp problem

Hi, I have a problem when i want to get a filename from an ftp server when a space is before his name. example: "spacetestFile" The ftp server return an error "no asset or no permission" though the file exist ? Why it behave in this way ? (8 Replies)
Discussion started by: protocomm
8 Replies
envelopes(5)							File Formats Manual						      envelopes(5)

NAME
envelopes - sender/recipient lists attached to messages INTRODUCTION
Electronic mail messages are delivered in envelopes. An envelope lists a sender and one or more recipients. Usually these envelope addresses are the same as the addresses listed in the mes- sage header: (envelope) from djb to root From: djb To: root In more complicated situations, though, the envelope addresses may differ from the header addresses. ENVELOPE EXAMPLES
When a message is delivered to several people at different locations, it is first photocopied and placed into several envelopes: (envelope) from djb to root From: djb Copy #1 of message To: root, god@brl.mil (envelope) from djb to god@brl.mil From: djb Copy #2 of message To: root, god@brl.mil When a message is delivered to several people at the same location, the sender doesn't have to photocopy it. He can instead stuff it into one envelope with several addresses; the recipients will make the photocopy: (envelope) from djb to god@brl.mil, angel@brl.mil From: djb To: god@brl.mil, angel@brl.mil, joe, frde Bounced mail is sent back to the envelope sender address. The bounced mail doesn't list an envelope sender, so bounce loops are impossi- ble: (envelope) from <> to djb From: MAILER-DAEMON To: djb Subject: unknown user frde The recipient of a message may make another copy and forward it in a new envelope: (envelope) from djb to joe From: djb Original message To: joe (envelope) from joe to fred From: djb Forwarded message To: joe A mailing list works almost the same way: (envelope) from djb to sos-list From: djb Original message To: sos-list (envelope) from sos-owner to god@brl.mil From: djb Forwarded message To: sos-list to recipient #1 (envelope) from sos-owner to frde From: djb Forwarded message To: sos-list to recipient #2 Notice that the mailing list is set up to replace the envelope sender with something new, sos-owner. So bounces will come back to sos- owner: (envelope) from <> to sos-owner From: MAILER-DAEMON To: sos-owner Subject: unknown user frde It's a good idea to set up an extra address, sos-owner, like this: the original envelope sender (djb) has no way to fix bad sos-list addresses, and of course bounces must not be sent to sos-list itself. HOW ENVELOPE ADDRESSES ARE STORED
Envelope sender and envelope recipient addresses are transmitted and recorded in several ways. When a user injects mail through qmail-inject, he can supply a Return-Path line or a -f option for the envelope sender; by default the envelope sender is his login name. The envelope recipient addresses can be taken from the command line or from various header fields, depending on the options to qmail-inject. Similar comments apply to sendmail. When a message is transferred from one machine to another through SMTP, the envelope sender is given in a MAIL FROM command, the envelope recipients are given in RCPT TO commands, and the message is supplied separately by a DATA command. When a message is delivered by qmail to a single local recipient, qmail-local records the recipient in Delivered-To and the envelope sender in Return-Path. It uses Delivered-To to detect mail forwarding loops. sendmail normally records the envelope sender in Return-Path. It does not record envelope recipient addresses, on the theory that they are redundant: you received the mail, so you must have been one of the envelope recipients. Note that, if the header doesn't have any recipient addresses, sendmail will move envelope recipient addresses back into the header. This situation occurs if all addresses were originally listed as Bcc, since Bcc is automatically removed. When sendmail sees this, it creates a new Apparently-To header field with the envelope recipient addresses. This has the strange effect that each blind-carbon-copy recipient will see a list of all recipients on the same machine. When a message is stored in mbox format, the envelope sender is recorded at the top of the message as a UUCP-style From (no colon) line. Note that this line is less reliable than the Return-Path line added by qmail-local or sendmail. SEE ALSO
qmail-header(5), qmail-local(8), qmail-inject(8) envelopes(5)
All times are GMT -4. The time now is 05:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy