Alright, we really should get this resolved:
A few thoughts:
The easy solution (as has been suggested on the list now and then) is to unlink the spool file as soon as we open it. I didn't do this originally (and haven't done it still) for two reasons:
1) I want to understand why it is happening and make sure it doesn't happen anymore.
2) Keeping the filename allows for the method we just added to let plugins get at the file name and pass it to virus scanners etc. (I didn't add it earlier because I wanted to stick to being able to do 1) ).
Some time ago I think it happened some times because we had exits and dies left a few places. I think we took care of all those. (I see that some of the virus scanner plugins are having "exit" now -- they should use the disconnect return code).
I setup a spamtrap pointing to my development installation. When it starts getting some traffic I'll hopefully be able to reproduce it and figure out how it happens. :-)
- ask
-- http://www.askbjoernhansen.com/
