From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] search by message size (incl. attachments)
Date: Thu, 16 Dec 2010 00:03:11 +0200 [thread overview]
Message-ID: <1292450230-sup-1708@tilus.net> (raw)
In-Reply-To: <1292428060-sup-9071@pk-desktop>
Piotr Kempa, 2010-12-15 17:59:
> I need to backup my maildir regularly, have it zipped, encrypted and
> sent away, and it's taking more and more time.
I'd go with incremental backups in that scenario. Daily backup size
is gonna be a tiny fraction of the whole mail archive.
Repeatedly sending stuff that has not changed (as most of your mail in
current backup were in the previous too) is plain waste of resources.
No matter if the zip is a gig or five.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-12-15 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 15:59 Piotr Kempa
2010-12-15 21:15 ` Marc Hartstein
2010-12-16 9:22 ` Piotr Kempa
2010-12-16 12:49 ` Moritz Wilhelmy
2010-12-16 13:19 ` Piotr Kempa
2010-12-16 13:21 ` Iain
2010-12-15 22:03 ` Tero Tilus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1292450230-sup-1708@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox