|
Grex > Info > #28: Sending files via email ?? | |
|
| Author |
Message |
matthew
|
|
Sending files via email ??
| 
Mar 25 05:35 UTC 1993 |
I've figured out how to get a text file into my directory in GREX, now
how do I go about sending it out via email to someone else ? Help please!
|
| 26 responses total. |
srw
|
|
response 1 of 26:
|
Mar 25 05:45 UTC 1993 |
I use mail rather than elm, and I say:
mail -s "subject goes here" person@domain <file
This send file to person@domain and gives you a chance to put a subject in.
|
davel
|
|
response 2 of 26:
|
Mar 25 11:08 UTC 1993 |
You can also use the mail program's editor and just read in the file. This
depends on what editor you have set up for whatever mail program you're
using. For either bbsed or vi, the command is
:r filename
In bbsed this must be issued as the entire contents of a line; in vi, you
should not be actually entering text (be in command mode, in other words).
This allows you to modify the file's contents if you wish, or to change
any of the header information you normally can. Otherwise, Steve's advice
is good; note that the same conventions will work for elm as well as for
mail.
|
robh
|
|
response 3 of 26:
|
Mar 25 11:41 UTC 1993 |
Yet another technique to use when in vi is position the cursor and
enter:
!!cat filename
Yes, that's two exclamation points. Using !! instead of :! to execute
a command puts the output of that command in the current file. I think.
|
remmers
|
|
response 4 of 26:
|
Mar 25 14:13 UTC 1993 |
That's correct.
Steve's method in #1 is probably the simplest.
|
tsty
|
|
response 5 of 26:
|
Mar 25 15:20 UTC 1993 |
Steve's is the simplest if you ONLY want the file sent. I believe that
after his command sequeence is effected, the cc: prompt comess up
next. There is no opportunity to put anything in the email +except+ the
contents of file . If you want to have some introductory
or finishing text in addition to file use davel's #2 or robh's #3
method.
Notice that there is no space in #1 for the redirection
<file not < file .
As noted in davel's #2 "depends on what editor you have set" you can
tell if it worked becasue you'll see reading "file" xx/yy as
a response from the editor. the xx=number of lines, yy=number of
characters.
If you don't see that respnse, it didn't work and you should use ~r fyle
instead, in which case the reading "fyle" xx/yy will appear proving
that the command worked. Deciding which command to use depends
on the editor. If there is a > prompt while you're entering
email text, use the >:r fyle style on a new line, if there
is no > prompt, use theh ~r fyle style on a new line.
|
mju
|
|
response 6 of 26:
|
Mar 25 17:04 UTC 1993 |
(Actually, "< file" will work just as well as "<file".)
|
matthew
|
|
response 7 of 26:
|
Mar 25 23:01 UTC 1993 |
Thank you all very much ! :)
|
power
|
|
response 8 of 26:
|
Mar 26 02:41 UTC 1993 |
Also, if you just want to put file on your hard drive into a mail message,
you mail someone, write a couple lines of explanation, and do a send ascii
on your end - this will 'type' it in for you...
|
tsty
|
|
response 9 of 26:
|
Mar 28 17:34 UTC 1993 |
Taht's cool too. re #6, re #5 and earlier ... thankxx mju, I thought
the lack of a space in <fyle for redirection was intentional. Ssometimes
the spaces are necessary, it seems, and sometimes they are optional,
it seems - isthere any way to "know" for +sure+ when spaces "count?"
|
davel
|
|
response 10 of 26:
|
Mar 29 11:32 UTC 1993 |
I think maybe I know where you got confused on that one, TS. If you want
to redirect a stream (stdout or stderr) by its descriptor (at least in sh)
you must not have a space between the descriptor and the > - as in
find / -name 'sometemplate' -print 2>/dev/null
The reason for this is presumably that you might have a command line that
ends in a number such as 2, and want to redirect its output somewhere. So
if you put a blank after the 2, it's part of the command line; if not, it's
a descriptor.
Some programs ("commands") require blanks in their options in various ways,
but I believe this is not according to current standards, for the most
part. The only way to tell that for sure is the man page or other doc,
and trial & error of course.
|
tsty
|
|
response 11 of 26:
|
Mar 31 03:08 UTC 1993 |
Hmmmmmm, guess tthat's the extent of the options, including, naturally,
the good old smoke-test, trial and error ........ thankxx.
|
matthew
|
|
response 12 of 26:
|
Apr 2 06:34 UTC 1993 |
Wow, thanks for all the input. I finally got it figured out.
Thanks yet again for everyones assistance
|
sweets
|
|
response 13 of 26:
|
May 6 20:23 UTC 1994 |
I want to know how to send a file from a floppy disk at you computerand also
what are the dial numbers for this services ,
|
rcurl
|
|
response 14 of 26:
|
May 6 20:55 UTC 1994 |
Where would you like to send it, and what comm program are you using?
|
scg
|
|
response 15 of 26:
|
May 7 04:11 UTC 1994 |
The dialin number for Grex is +1 313 761-3000. It's in Ann Arbor, MI., so
if you're calling from Boise, Idaho, the long distance might be kind of
expensive (especially if you use Grex as much as I do). The dialin lines
are also often busy, since we only have six of them. I have somehow
managed to get one right now, though.
|
davel
|
|
response 16 of 26:
|
May 7 12:30 UTC 1994 |
They're actually a lot less busy since the net connection opened up.
|
scg
|
|
response 17 of 26:
|
May 7 20:14 UTC 1994 |
Yeah, since attack dialing is no longer required to get in. The last
couple of times I have gotten fed up with net lag it has only taken me a
minute or two to get an open line, compared to waits of more than half an
hour before.
|
coyote
|
|
response 18 of 26:
|
Apr 9 23:15 UTC 1996 |
Does anybody know how to attach a file to an email when using elm? I've
already tried:
elm -s <subject> <receiver> < <filename>
as written in the elm manual page, but it doesn't work. It thinks that the
"<" and the filename are people who I want the letter to be sent to. I really
don't feel like switching mailers and having to re-configure right now, so
help would be greatly appreciated. Thanks!
|
popcorn
|
|
response 19 of 26:
|
Apr 10 08:39 UTC 1996 |
This response has been erased.
|
davel
|
|
response 20 of 26:
|
Apr 10 10:17 UTC 1996 |
That last is a likely cause of the problem, I'd say. You'd need to enter
the command from a shell prompt; from a Picospan Ok: or Respond-or-pass:
prompt, or from a menu or lynx prompt, you'd need an exclamation mark at the
beginning.
Another possible problem would be if you put quotes around the "<" or
something like that; but it doesn't sound like that's what you're doing.
Finally, one other possible source of problems: if your subject includes
blanks or tabs, be sure to enclose the entire subject in quotes. To spin off
Valerie's example:
elm -s "This is a test" popcorn < .login
(If you omit the quotes, it would think the subject was just "This", and that
"is", "a", and "test" were intended recipients. Depending on your message,
you might not want it to go to any user who happened to be named "test", for
example ...)
|
coyote
|
|
response 21 of 26:
|
Apr 10 13:13 UTC 1996 |
I tried it again, and it still didn't work. It seemed to at first, because
it didn't put the filename and the "<" in the To: menu. It also put my full
name instead of "coyote@cyberspace.org" in the To: list. The only thing I
did differently that time was just typing "coyote" instead of my full address
as the receiver of the letter. But it still didn't work, and I got a "User
Unknown" letter from the mail robot about the filename and the "<". If anyone
can figure out what's going on, I'd appreciate it. Thanks!
|
srw
|
|
response 22 of 26:
|
Apr 11 07:02 UTC 1996 |
Could you type the exact command you typed that failed. You can change the
name of the recipients, but we want to see how many words were typed and where
(if any) the quotes were, precisely.
|
davel
|
|
response 23 of 26:
|
Apr 11 11:10 UTC 1996 |
Also, exactly what prompt you're issuing it from.
Thanks.
|
popcorn
|
|
response 24 of 26:
|
Apr 11 14:03 UTC 1996 |
This response has been erased.
|