Hi,

I'm trying to come up with mechanisms to catch compromised accounts sending 
SPAM.  Since spammers don't necessarily have all good addresses a large number 
of their SPAM messages bounce with 550 errors (mailbox unavailable or doesn't 
even exist).  I would like to monitor men logs and catch that pattern.  The 
problem is that the log entry that includes the 550 error only shows where the 
message was intended to go and not where it came from.  That's found on another 
log entry line.  Is there anyway to tweak the logging mechanism so both bits of 
data appear on the same log line?

Thanks.


Rob Tanner
UNIX Services Manager
Linfield College, McMinnville Oregon

ITS will never ask you for your password.  Please don’t share yours with anyone!

Reply via email to