From: Etienne Pretorius (etiennepkingsley.co.za)
Date: Tue Mar 07 2006 - 04:43:32 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello Neil,

I have tried to go through SAIX about this issue and they are very
closed mouth about it. They say since people have been using dyndns
servers to resolve the dynamic ip issue that their mail queue has been
fludded with idoits who could not set it up propperly. So what they did
is block CRON messages for all of us. I have used header-checks to
remove all of the following:

X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>

But sadly I could not figure out a way to change the Subject that will
read with the word cron in it. So the only way I solved it for myself at
least was to make a transport and deliver the mail directly to a machine
that I use to collect the cron daemon messages and then monitor the
other servers. Best of luck, and please post your findings and answers
to this mailing list as I am very interisted to see a propper solution
to this problem.

Kind Regards
Etienne

Ralf Hildebrandt wrote:

>* Neil Wilson <neilwdcdata.co.za>:
>
>
>
>>Yea, thanks, I saw this post, but his drive crashed before he had a
>>chance to track it down, so I'm assuming that he didn't bother trying to
>>figure out what the cause of it was.
>>
>>
>
>
>
>I wonder how these people can run a service WITHOUT a backup. And: It
>seems that these *_checks came from someplace else, so it should be
>possible to find the common source!
>
>
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]