Hello, Folks,
I have installed procmail-3.11pre7 on our Solaris5.5.1/Ultra-1 system
and I ocasionally got the following messages in /var/adm/messages:
May 20 13:52:58 testmail0 procmail[14069]: Renamed bogus
"/var/mail/sanders.lock" into "/var/mail/BOGUS.fDZ"
------
/etc/procmailrc is working fine and here is its contents:
VERBOSE=on
SHELL=/bin/ksh
PATH=/bin:/usr/bin:/usr/local/bin:/usr/local/bin
CACHEDIR=/var/spool/procmail
CACHE=/var/spool/procmail/$LOGNAME.cache
LOGFILE=/var/adm/procmail-log
SENDMAIL=/usr/lib/sendmail
DEFAULT=/var/mail/$LOGNAME
FORMAIL=/usr/local/bin/formail
LOCKFILE=/var/mail/$LOGNAME.lock
:0
* !^Subject:.*[*/*]
* !^Message-ID: *<MAPI(_dot_)*(_at_)MAPI(_dot_)to(_dot_)RFC822>
{
:0Wh : /var/mail/$LOGNAME.lock
* ? test -f $CACHE
| /usr/local/bin/formail -D 8192 $CACHEDIR/$LOGNAME.cache
}
------
The config.h did not uncomment any of the following lines:
Since we need to have procmail to have the same locking mechanism
as /bin/mail.
/*#define NO_fcntl_LOCK /* uncomment any of these three if you
*/
/*#define NO_lockf_LOCK /* definitely do not want procmail to make
*/
/*#define NO_flock_LOCK /* use of those kernel-locking methods
*/
----
Could someone shed a light on how to fix this BOGUS.xxx messages?
Thank you in advance.
Lchen(_at_)rational(_dot_)com
Lufan Chen
Sys Admin/Rational Software Copr
Cupertino, CA