|
Grex > Info > #125: Attaching file to be mailed to victim of mail deletion |   |
|
| Author |
Message |
vidar
|
|
Attaching file to be mailed to victim of mail deletion
| 
Mar 21 20:26 UTC 1994 |
How does one utilize the filter file to mail a file, before it deletes
the mail from the recipient? I have a file ".warning" in my ".elm"
directory, and I would like it to be sent to a certain person
who's loginid at emuvax I will enter in the 1st (hopefully) response.
Thank you for you help. Thanks in advance are always a good thing.
|
| 51 responses total. |
vidar
|
|
response 1 of 51:
|
Mar 21 20:28 UTC 1994 |
The loginid is "ENG_ST712528@emuvax.emich.edu"
Thanks again.
|
robh
|
|
response 2 of 51:
|
Mar 21 23:30 UTC 1994 |
If'n I remember correctly, you can tell the program to "execute"
a Unix program when receving mail from someone. How to combine
that with the deletion, I'm not sure. And since SOMEONE deleted
the on-line help files, I'll have to FTP them and look it up.
Hold on...
|
vidar
|
|
response 3 of 51:
|
Mar 22 01:38 UTC 1994 |
Don't worry. I'm not going anywhere until July.
|
robh
|
|
response 4 of 51:
|
Mar 22 03:20 UTC 1994 |
Okay, I tracked down the info, fooled around with my filter-rules
file, got some help from nestene, and here's what ya do:
if (to = "userid") then execute "elm userid < /u/vidar/.elm/.warning"
if (to = "userid") then delete
(Where, of course, you replace userid with the address of whoever.)
Upon receiving the mail, it first calls the elm program to send
a copy of your .warning file. The next filter rule zaps it.
Note that you can't combine the two functions into one filter
rule, but there's nothing wrong with two rules that use the same
conditional. Got all that? >8)
|
popcorn
|
|
response 5 of 51:
|
Mar 22 04:02 UTC 1994 |
Cool!
|
carson
|
|
response 6 of 51:
|
Mar 22 05:17 UTC 1994 |
Evil!
|
kentn
|
|
response 7 of 51:
|
Mar 22 05:26 UTC 1994 |
Okay, so (let me get this straight), this method sends a message
to a particular user, telling them their message is rejected or
somesuch, and then deletes the message?
Hmmm....
|
carson
|
|
response 8 of 51:
|
Mar 22 05:42 UTC 1994 |
(or as power might say: "Sexy!")
|
remmers
|
|
response 9 of 51:
|
Mar 22 05:47 UTC 1994 |
Re #4: Where do you put those lines? And where can I get
full documentation?
|
robh
|
|
response 10 of 51:
|
Mar 22 11:21 UTC 1994 |
Oops, sorry, I forgot that people besides vidar might be
reading this... >8)
These intructions go in your .elm directory, in a file named
filter-rules. There's a bunch of other stuff to do, too.
The Elm documentation (which USED to be online on Grex) can
be FTP'ed from ftp.mcs.com, in /mcsnet.users/dattier/elmguides
|
kentn
|
|
response 11 of 51:
|
Mar 22 15:09 UTC 1994 |
Okay, everyone...let's all put copies of the elm docs in our home
directories! NOT!
|
carl
|
|
response 12 of 51:
|
Mar 22 16:18 UTC 1994 |
Could one of the fw's download these files and let us know where they
end up? I'd like to read them when I get a chance.
|
popcorn
|
|
response 13 of 51:
|
Mar 22 19:37 UTC 1994 |
Hm. I'm the fair witnesses for this conference, but I'll defer to whoever
wants to download this thing and put it somewhere readable.
|
vidar
|
|
response 14 of 51:
|
Mar 22 21:17 UTC 1994 |
I'm not sure I have it exactly correct. Do both commands need be on
seperate lines, or is one continious sentence okay?
|
vidar
|
|
response 15 of 51:
|
Mar 22 21:30 UTC 1994 |
Never mind. I fixed it.
|
robh
|
|
response 16 of 51:
|
Mar 22 21:36 UTC 1994 |
Seperate lines. I checked your filter-rules and you've got
it right.
|
vidar
|
|
response 17 of 51:
|
Mar 22 22:13 UTC 1994 |
Good. I hope you didn't read ".warning", it's a real nasty file
directed towards the recipient.
|
robh
|
|
response 18 of 51:
|
Mar 23 02:09 UTC 1994 |
Ooh, you've scared me off! >8)
|
carl
|
|
response 19 of 51:
|
Mar 23 02:12 UTC 1994 |
The files are available in /u/carl/elm_help.
Now, can someone tell me how to read a .gz file?
|
vidar
|
|
response 20 of 51:
|
Mar 23 02:16 UTC 1994 |
Re#18: Do you mean that or are you being sarcastic? It's kinda hard to
tell in writing.
Re#19: Sorry, nope.
|
kaplan
|
|
response 21 of 51:
|
Mar 23 02:34 UTC 1994 |
This is from /usr/local/inet/README
To conserve disk space, many files in this area have been compressed with GNU
project's compress program, gzip. Detailed information is available. Type
man gzip
Briefly, if a filename ends with .gz, for example, ftp-faq.txt.gz, type:
zcat ftp-faq.txt -display file for text capture
zmore ftp-faq.txt -display file one screen full at a time; use the
space bar for the next screen full
|
davel
|
|
response 22 of 51:
|
Mar 23 11:10 UTC 1994 |
Good as far as it goes. A couple of added points: to uncompress it
permanently (if you need to), use gunzip. If it's something like a tar
file that's been gzip'd, you may want to gunzip and untar in one step with
something like
zcat something.tar.gz | tar tvf -
(or pipe it through some other program).
|
popcorn
|
|
response 23 of 51:
|
Mar 23 13:38 UTC 1994 |
Basically, .gz means that the file has been compressed by the Gnu Zip
utility. Grex is set up so you can say "uncompress foo" to uncompress
a file called foo.gz into a file called foo. You can also use Grex's
zcat program to look at the contents of a compressed file without having
to uncompress it. To compress a file named foo, use the command
"gzip -9v foo".
These utilities are based on the much more commonly found commands:
compress, uncompress, and zcat, which deal with files with .Z extensions.
Grex's uncompress and zcat programs have been replaced by Gnu utilities
that can handle several different formats. Grex's compress program is
the standard built-in version.
|
robh
|
|
response 24 of 51:
|
Mar 23 14:17 UTC 1994 |
Re 20 - If you see a >8), 100% chance I'm being sarcastic.
|