hmz. the actual artv export behaviour is definetely bad. if you have a wideley distributed set of users, and business related mail load on it, you need to have some way of propagating 'down for service'
i've experienced the resulting difficulties right now.
citadel needs to accept all kinds of inbound messages during artv import/export, and answer them with an according message.
this message could allso be static, but there needs to be one.
even if it's accept all imap / smtp etc connects, and say, "sorry we're down for maintainance". via imap this could be allso using the paging mechanism. poping a window into the users face is just right the thing that needs to be done in such a situation.
plus, if one wants to do an artv export, and take a binary copy in advance, the system needs to enter that state with a command before.
ah, and while i'm writing: adding the tip that you should wrap nohup or screen arround the artv export would be a good point for the documentation.
