Usually the directories will exist somewhere in /var or /usr, my linux is rusty, but try this command line in a new terminal window

inotifywait -rme modify,attrib,move,close_write,create,delete,delete_self /dname


change dname to appropriate directory. inotify is part of iotify-tools on Centos, im sure you can find/install it easily enough. try different directory roots perhaps , start mail server in another window, see what is being accessed.

its early here too ;-)



On 05/04/2017 01:39, Jim McLachlan wrote:
Hi ap-ml,

This sounds interesting. Could you let me know where I should look for the temporary files you mentioned?

    I'm on the edges of my knowledge of e-mail and networking here :-)

    Kind regards.

    Jim.

On 05/04/17 01:11, ap-ml wrote:
Its almost as though there is a build-up of messages that are being continually scanned through, I had a similar issue once where due to incorrect permissions, temp files were not being deleted. Perhaps check temp & working directories for such a logjam of emails. Have you also checked for the message IDs in the logfiles in email headers to see if the files are in user emaildirs or some
other folder?


On 05/04/2017 01:06, Dave Wreski wrote:
Hi,


    I've posted the spamfilter.sh file to http://pasted.co/7b794ccd

    I don't see anything in there about verbose logging, but there are
two lines in there with a resemblance to your suggestion:

logger -f $SALOG -p mail.notice -t spamfilter <<<"Spam filter piping to
SpamAssassin: $SPAMASSASSIN -x -E -s $MAX_MESSAGE_SIZE"

    and

logger -s -p mail.notice -t spamfilter <<<"OK. Piping to sendmail:
$SENDMAIL $@"

The second one seems to be after-the-fact, so I think I could modify
the first one.  Should this be cut down to:

$SPAMASSASSIN -x -E -s $MAX_MESSAGE_SIZE

    to avoid the logging process?

Yes, you can comment out this line:

logger -f $SALOG -p mail.notice -t spamfilter <<<"Spam filter piping ...

and this one:

logger -s -p mail.notice -t spamfilter <<<"OK. Piping to sendmail: ...

Basically, the first and last "logger" lines. That's a good start.

Regards,
Dave


Reply via email to