On Tue, 31 Jan 2006, John Peacock wrote:
The tricky part is how to handle an error condition when we would want to keep a copy of the file.
What conditions might they be?
I want to get a much better handle on why we aren't cleaning up right now (though it may just be a byproduct of using 'svc -t' to restart the server).
Which in turn could only be inappropriate response to a TERM signal - there's nothing magical about 'svc -t'.
Only then can I make any sort of rational guess at what point in the transaction should failure retain a copy of the message: ~ post-data up to queue? ~ new hook available for plugin authors? ~ global parameter? ~ others I haven't thought of yet?
I'm struggling to think of any case where qpsmtpd needs to preserve content. The content is always available elsewhere - either in the backend, which has acknowledged receiving it, or in the sender's system, which will keep it for resending until it receives a permanent status code. Or both, if the backend has provided a response which hasn't yet been relayed to the sender.
--- Charlie
