Hmmm. What would explain that I haven't been getting these messages,
then all of a sudden I am getting many of them? I haven't changed my
sendmail configuration and my sendmail server is not exposed to outside
users?
What ways can I track these things down?
Mike
On Tue, 2004-04-27 at 21:59, Rob Funk wrote:
mbox mbarsalou wrote:
I get status messages #65 and #64 quite frequently...I believe they are
in reference to bad dns names and non-existent users.
Check out /usr/include/sysexits.h:
#define EX_USAGE 64 /* command line usage error */
#define EX_DATAERR 65 /* data format error */
#define EX_NOINPUT 66 /* cannot open input */
#define EX_NOUSER 67 /* addressee unknown */
#define EX_NOHOST 68 /* host name unknown */
If you're getting 64 and 65, there's probably something you need to fix.
Either way, I
want to know how to have them not report from CRON. Would it be wrong
to use the antispam keyword to deal with this? I would turn bouncing
off.
Seems like a bad idea to me..... better to fix sendmail instead.
I don't care about messages that have bad dns entries or unknown users.
If you're really getting those errors rather than 64 & 65, and sendmail is
giving unique error codes for them, then antispam might help.