|
|
| Author |
Message |
jared
|
|
.forward file help
| 
Mar 30 04:59 UTC 1993 |
Okay... here's a good question.. I type login hangup to log out of the system
here. I would like to have mail that gets sent to me send to m-net, and
also to stay here. My .forward reads jared@m-net so that it gets sent
there, but that handles all my mail, and I would like to get the mail
while I'm on without having to mv .forward forward or something like that.
the reason for not moving it is because I don't execute a .logout file.
Any solutions?
|
| 27 responses total. |
mju
|
|
response 1 of 27:
|
Mar 30 06:18 UTC 1993 |
Just list both addresses in the .forward file, each on its own line.
For example, your .forward file could contain the two lines
jared
jared@m-net.ann-arbor.mi.us
Mail sent to you here would be delivered to your mailbox here, and
also forwarded to M-Net.
|
jared
|
|
response 2 of 27:
|
Mar 30 11:36 UTC 1993 |
okay... I thought that having the both listed would get the message to here
sent back through, and get in some endless loop constantly forking the message
|
jared
|
|
response 3 of 27:
|
Mar 31 00:37 UTC 1993 |
that didn't seem to work. wolvrine sent me mail for help, and it only
sent the mail to m-net. take a look at this .forward. but when I replied,
it got cc:ed to here, and stayed here, and I got a copy back on m-net.
Strange.
----.forward----cut-here-----
jared@m-net
jared
----.forward----cut-here-----
|
mju
|
|
response 4 of 27:
|
Mar 31 01:21 UTC 1993 |
It certainly appears like it should work. I just tested it out
by running "smail -N -v25 jared", and smail claimed to be doing
the right things. (-N turns off the actual delivery of the
mail, and is useful for debugging. -v25 turns on debugging
messages and sets the verbosity level to 25. This is a generally
useful level for figuring out what's going on, without getting
lots of meaningless garbage.)
|
tsty
|
|
response 5 of 27:
|
Mar 31 03:19 UTC 1993 |
One of the differences is that there is a "feature" in the m-net mailer
when it has to deal with forwarded email +and+ there is more than
one recipient. Eventhough it generates a failure, you will notice
that in the boxed area for (Ithink it's) "standard error follows" and
the "message contained below," there is *no* standard error listed,
the space thatis supposed to contain the "error" is null.
That's the clue which tells you that the email +was delivered+ anyway.
Another difference +might be+ the mechanism used to forward mail. I don't
know if the following will/can work here, but over there:
\\ name@address
is what's in a .forward address, well, maybe \ \name@address I don't
remember exactly at this moment. This sends you a copy on the local
machine and forwards a copy somewhere else.
Waht I do need to know is; isthere some "trap" for email that continuously
forwards in a round-robin sort of way?
|
popcorn
|
|
response 6 of 27:
|
Mar 31 03:35 UTC 1993 |
This response has been erased.
|
jared
|
|
response 7 of 27:
|
Mar 31 03:51 UTC 1993 |
Hmm.. I'm going to try several things here to work with any possible
changes, etc of the .forward
|
mju
|
|
response 8 of 27:
|
Mar 31 20:55 UTC 1993 |
The "\\" hack is a smail2.5-ism. We're running smail3, which just
takes a newline-separated list of addresses.
Well, I just tested it out. I created a .forward file for myself
that read
mju@m-net
mju
and then sent mail to myself. Sure enough, the mail was delivered to
my mailbox here, and queued up for m-net via netmeg.
|
tsty
|
|
response 9 of 27:
|
Apr 1 05:47 UTC 1993 |
Did it make any difference that the m-net address was incomplete?
|
mju
|
|
response 10 of 27:
|
Apr 1 23:01 UTC 1993 |
Nope.
|
jared
|
|
response 11 of 27:
|
Apr 2 04:51 UTC 1993 |
What is it with denise?
|
rcurl
|
|
response 12 of 27:
|
Apr 2 05:23 UTC 1993 |
YOU are denise! Haven't you noticed yet?
|
popcorn
|
|
response 13 of 27:
|
Apr 4 13:45 UTC 1993 |
This response has been erased.
|
jared
|
|
response 14 of 27:
|
Apr 5 05:22 UTC 1993 |
I saw that, and thought it was strange. Just a sed thing? call m-net,
and j knut, and see what they did with my name.
|
popcorn
|
|
response 15 of 27:
|
Apr 5 23:10 UTC 1993 |
This response has been erased.
|
jared
|
|
response 16 of 27:
|
Apr 6 01:47 UTC 1993 |
oh well.. I knew that something was up when I got on, and it said 'Happy
Thanksgiving'
|
aa8ij
|
|
response 17 of 27:
|
Apr 9 04:19 UTC 1993 |
you should have been here last year... Mary poppins... sheesh.
|
jared
|
|
response 18 of 27:
|
Apr 10 23:51 UTC 1993 |
I heard thet m-net last year was the best.
Grex is the breakfast food of champions
login:
|
nephi
|
|
response 19 of 27:
|
May 9 08:49 UTC 1995 |
<nephi laughs out loud at an ancient joke>
|
adbarr
|
|
response 20 of 27:
|
Aug 19 22:07 UTC 1995 |
This must be the black hole of conferences. I think
nephi must be n historian at heart. Or is it "a" historian?
|
orinoco
|
|
response 21 of 27:
|
Aug 20 14:04 UTC 1995 |
<orinoco is waiting for the punch line>
|
alb001
|
|
response 22 of 27:
|
Nov 30 10:51 UTC 1999 |
i am trying to forward to two addresses and reading this thread hasnt helped
+sorry+. if i put two addresses separated by newline in a .forward file, it
only forwards to the seconmd address. why is this?
|
davel
|
|
response 23 of 27:
|
Dec 2 02:34 UTC 1999 |
I'd have thought it would work. However, I've always used a .forward file
with just a comma-separated list on one line; it happens that this is how
the example I followed was done, & it worked. You might try a single line
of the form
user1@something.something, user2@somewhere.somewhere
If *that* doesn't work, I'd assume that something's wrong with the address
that's not going through - since I know that this format does forward
properly. (To test that with your current setup, you could try switching
the addresses in your .forward, I suppose.)
|
albaugh
|
|
response 24 of 27:
|
Dec 8 23:12 UTC 1999 |
1 address per line is *supposed* to work, and always has for me (though I
haven't used that on grex, but grex shouldn't be different). I tend to agree
that one of the addresses might be wrong or have a "problem" with grex, and
that it's not a .forward file problem.
|