procmail
[Top] [All Lists]

Re: EXITCODE/HOST problem

1996-11-16 15:12:45
Tim <bodysurf(_at_)netcom(_dot_)com> writes:
...
Towards the middle it prints out all that information from my LOGFILE
(under "Transcipt of session follows").  I don't like that.  It lets these
idiots know what's in my PROCMAILRC file AND it tells them I am using
PROCMAIL to bounce their message.  I was under the impression using this
EXITCODE would "fool" these people into thinking the email address didn't
exist.  Maybe I'm asking for too much.  I could always go back to using the
manual bounce message.  Any more suggestions anyone?

sendmail includes in the bounce message anything that was sent to stdout or
stderr.  Procmail should only send the messages you saw to one of those
(stderr or stdout) if LOGFILE is not set.  Make sure the LOGFILE is always
set to some file, or if you don't want to save the output anywhere, set
it to /dev/null.

Here's some pertinent parts from my PROCMAILRC file.  I have been 
specifying my LOGFILE, so it should be set.  Any other advice :^)?

----- BEGIN:  PROCMAILRC -----
  #Set on when debugging
  VERBOSE=on

[...]

  #Directory for storing procmail log and rc files
  PMDIR=$HOME/.procmail

[...]

  LINEBUF=50000
  LOGFILE=$PMDIR/log

[...]
----- END: PROCMAILRC -----

BTW: I noticed that you set LOGFILE=50000.  Why do you set it to such a huge
value?

I think you mean 'LINEBUF=50000'.  I was having problems with NetCom's 
GREP being able to process long files (FGREP) so I increased the LINEBUF 
in hopes of correcting it.  That didn't end up working, but installing 
GNU Grep v2.0 *did*.  I should probably go back and reduce that LINEBUF 
to a more reasonable value.

Lates!
----------------------------------
Tim <bodysurf(_at_)netcom(_dot_)com>
"Finger" for PGP v2.6.2 Public Key

<Prev in Thread] Current Thread [Next in Thread>