Hi, I have a wishlist item. Is there an appropriate place for me to post it? Basically, I would like to know that my email isn't recoverable from the local disk on the mail server after I delete it. So instead of just deleting the file from my Maildir, I'd like the option to exist for Dovecot to shred it.. Ie, overwrite the file with random data and/or null bytes before deletion. In the same way that GNU shred behaves: https://www.gnu.org/software/coreutils/manual/html_node/shred-invocation.html -- Mike Cardwell https://grepular.com/ https://twitter.com/mickeyc Professional http://cardwellit.com/ http://linkedin.com/in/mikecardwell PGP.mit.edu 0018461F/35BC AF1D 3AA2 1F84 3DC3 B0CF 70A5 F512 0018 461F -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20110914/6da6904b/attachment-0004.bin>
On 14.9.2011, at 16.46, Mike Cardwell wrote:> I have a wishlist item. Is there an appropriate place for me to post it? > Basically, I would like to know that my email isn't recoverable from the > local disk on the mail server after I delete it. So instead of just > deleting the file from my Maildir, I'd like the option to exist for > Dovecot to shred it.. Ie, overwrite the file with random data and/or > null bytes before deletion. In the same way that GNU shred behaves:Well, the choices are: a) Patch Dovecot sources b) Use a LD_PRELOAD library to override unlink() c) Use a FUSE filesystem that replaces unlinks with shredding d) Wait until I've finished making dbox code use lib-fs, and write a lib-fs wrapper plugin that replaces unlink() I'm not anyway planning on distributing any of these solutions with Dovecot. It won't even work with newer copy-on-write filesystems (ZFS, BTRFS, etc.)