Karl Vogel wrote about my suggestion to Brock Rozen,
| Dunno if this would be of interest to the list, but if your mailbox is
| big and you're doing this for every message, should you keep the backup.$$
| file on the same filesystem?
|
| cat - backup > backup.$$ && mv backup.$$ backup
|
| You'll get some savings from mv not having to copy the file...
Very good point, Karl. My reasoning in suggesting /tmp/backup.$$ is that
one might be so near one's storage quota that $MAILDIR/backup.$$ couldn't be
written out in full (or even to the point of saving the incoming message plus
999 more as Brock wants). Besides, when I posted I was deprecating the idea
of adding gyrations for every incoming message instead of adding them just
once a day in Brock's cron job.
I had no idea that Brock would go for it after all. If he actually checks
the backup folder to reread old mail, then having newer messages at the
beginning is a bonus and it's worth the extra cycles to put them at the top
as they arrive.