AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080925170649.4c7321f5@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.rogers@onstor.com>,<larry.scheer@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 25 Sep 2008 17:08:23 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: John Rogers <john.rogers@onstor.com>, Larry Scheer
 <larry.scheer@onstor.com>
Subject: fyi: proper procedure for exim
Message-ID: <20080925170823.38336e30@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Howdy guys,

I saw this in the screen log files for the dogfood, and I said, huh, I
never said to do that, so I guess you were just doing what comes
natural after using BSD for so long.

Dogfood:/var/spool/exim4/msglog# rm -rf *

Please do not do this in the future, it is not the correct thing to do
with exim.  Generally the files in these directories should not be
mucked with by hand.  For the future, that's why I told Larry that all
that needed doing is to stop exim, do a "killall exim4" and then to
start exim.  If file deleting had been necessary, I would have
mentioned that.

If things are working as they should, exim will clean out the queue as
it sees fit.

I'm not sure where the right place is to document this sort of thing.
I think it's important to try and do so because I'm sure that there is
nastalgic information floating about the company about how to deal with
email queues and things filling up, and I would like to inform folks of
the new ways.

Cheers,

a

