On Thursday, May 23, 2002, at 02:04 , lz wrote:
[..]
> Here is what in my perl file. .forward is the same:
>
> #!/usr/bin/perl
> open LOG, ">/home/lz/perl/logfile" or die "Can't
> create logfile: $!";
>
> print LOG "test";
>
> When the mail is sent, the file is not generared...
> When I execute the code from the command prompt, file
> is generated...
[..]
>>> in my .forward file
>>> |/home/lz/perl/checkRelation.pl
>> phase one good - the .forward file seems correct
[..]
hum... you did set the permissions to that correctly, eh no?
hence if you are at the keyboard that you can type
/home/lz/perl/checkRelation.pl
and your code runs????
not the
perl checkRelation.pl
form of running it.....
and that .forward file is in
~/.forward
"
Automatic Forwarding
When an alias (or address) is resolved to the name of a user
on the local host, sendmail(1M) checks for a ~/.forward
file, owned by the intended recipient, in that user's home
directory, and with universal read access. This file can
contain one or more addresses or aliases as described above,
each of which is sent a copy of the user's mail.
Care must be taken to avoid creating addressing loops in the
~/.forward file. When forwarding mail between machines, be
sure that the destination machine does not return the mail
to the sender through the operation of any NIS aliases.
Otherwise, copies of the message may "bounce." Usually, the
solution is to change the NIS alias to direct mail to the
proper destination.
A backslash before a username inhibits further aliasing.
For instance, to invoke the vacation program, user js
creates a ~/.forward file that contains the line:
\js, "|/usr/ucb/vacation js"
so that one copy of the message is sent to the user, and
"
thank god I still have the old Solaris versions to remind me where
all of this Skank Resides....
ciao
drieux
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
