01-11-2002
.forward file for mail redirection
I've set up a .forward file on a few identical servers that we have (all identical .forward file as well) but only one server is forwarding any of my unix mail (mail generated by cron) to my internet account.
Because these servers (5) are all identical in terms of aix versions, etc., I do not understand why only one works. The only difference that I can say is that these servers all run different cron jobs. Cron is the guy generating all these log messages and I'd like to see these emails in Outlook not unix.
Please advise as to what could be the issue. Is the use of the | tee command important in setting up the crontab to utilize the .forward file? Someone told me this is the case but I see no documentation in my unix admin book.
Thanks.
10 More Discussions You Might Find Interesting
1. Solaris
how can i forward roots mail, i want every mail fowarded (1 Reply)
Discussion started by: csaunders
1 Replies
2. UNIX for Dummies Questions & Answers
I am trying to configure sendmail to forward email to a PHP script. I don't know UNIX and am having trouble figuring out how to forward the mail. I think this is just a bunch of basic questions, but I have had little luck getting help elsewhere on my specific questions and it's driving me nuts. You... (3 Replies)
Discussion started by: bitt3n
3 Replies
3. Linux
Hai
can you help it out i am using send mail server in that some messages are teged with spam that messages has to forwaded to putecular Id and it has to removed from the user.
s.sheik (1 Reply)
Discussion started by: s_sheik
1 Replies
4. Solaris
Dear All,
Now I use solaris 10 and I try to forward mail from /var/mail/username to their external mail so what should I do?
thank u in advance (2 Replies)
Discussion started by: unitipon
2 Replies
5. Shell Programming and Scripting
I have forward dns zone file with A records and converting it to reverse zone file
ex.
subdomain1 A 10.20.30.40
subdomain2 A 10.20.31.41
subdomain3 A 10.20.35.43
subdomain4 A 10.20.30.41
subdomain5 ... (5 Replies)
Discussion started by: mosavani
5 Replies
6. UNIX for Dummies Questions & Answers
Hi there,
I receive job applications sent by a website daemon. The email subject contains the job offer description. The problem is that gmail tends to concatenate emails with the same subject and I don't really want all applications in the same email. Thus the from field contains the candidate... (0 Replies)
Discussion started by: chebarbudo
0 Replies
7. Debian
Hi There
Not sure if this is the correct place for this.
I'm running Sendmail on a Debian box and want to do the following.
e-mail comes in from userk@domain.co.za and is destined for usera@mydomain.co.za, but i want all mail from userk@domain.co.za to go to userb@mydomain.co.za. Sendmail... (3 Replies)
Discussion started by: linuxjunkie
3 Replies
8. UNIX for Advanced & Expert Users
Hi,
We are using mailx -s command to send mails from unix.
We need to ensure that this mail is not copied,forwarded etc.
Is there a command which can be used to achieve this using unix?
Thanks.
No double posting please, continue here. (0 Replies)
Discussion started by: dwarkeshr
0 Replies
9. UNIX for Dummies Questions & Answers
Hi,
We are using mailx -s command to send mails from unix.
We need to ensure that this mail is not copied,forwarded etc.
Is there a command which can be used to achieve this using unix?
Thanks. (1 Reply)
Discussion started by: dwarkeshr
1 Replies
10. Ubuntu
Hi,
I am new to linux stuff. I want to use linux iptables to configure rule so that all my incoming traffic with protocol "tcp" is forwarded to the "FORWARD CHAIN". The traffic i am dealing with has destination addresss of my machine but i want to block it from coming to input chain and somehow... (0 Replies)
Discussion started by: arsipk
0 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When
executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,
if such exists).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD