From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/16704 Path: news.gmane.org!not-for-mail From: regcl Newsgroups: gmane.emacs.gnus.user Subject: Re: emac gnus-centric gmail-phobic multi-host mail management Date: Wed, 19 Feb 2014 20:05:32 -0500 Message-ID: <87mwhm7fvn.fsf@channing.harvard.edu> References: <87r470tkr3.fsf@channing.harvard.edu> <87ppmjqxzn.fsf@motoko.kusanagi> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1392909693 12858 80.91.229.3 (20 Feb 2014 15:21:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Feb 2014 15:21:33 +0000 (UTC) Cc: public-info-gnus-english-mXXj517/zsQ@plane.gmane.org To: W. Greenhouse Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Thu Feb 20 16:21:38 2014 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WGVRR-0002qe-AH for gegu-info-gnus-english@m.gmane.org; Thu, 20 Feb 2014 16:21:37 +0100 Original-Received: from localhost ([::1]:39198 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGVRQ-0000bg-TU for gegu-info-gnus-english@m.gmane.org; Thu, 20 Feb 2014 10:21:36 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGVQU-0007hl-HS for info-gnus-english@gnu.org; Thu, 20 Feb 2014 10:20:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGVQN-0008Vs-Gv for info-gnus-english@gnu.org; Thu, 20 Feb 2014 10:20:38 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:38147) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGVQN-0008Ve-4r for info-gnus-english@gnu.org; Thu, 20 Feb 2014 10:20:31 -0500 Original-Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WGVQL-00013P-2s for info-gnus-english@gnu.org; Thu, 20 Feb 2014 16:20:29 +0100 Original-Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WGVQA-0000iT-L5 for public-info-gnus-english-mXXj517/zsQ@plane.gmane.org; Thu, 20 Feb 2014 16:20:18 +0100 Original-Received: from mail-qc0-f171.google.com ([209.85.216.171]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WGI6E-0004vy-Jv for public-info-gnus-english-mXXj517/zsQ@plane.gmane.org; Thu, 20 Feb 2014 02:06:50 +0100 Original-Received: by mail-qc0-f171.google.com with SMTP id x3so2156950qcv.2 for ; Wed, 19 Feb 2014 17:06:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=sJRDNz2Yl05M8lJJKgcg8xo9tCqpMmlMTKuzKawOIAA=; b=JzW3K43elZ5i8XjhHgYjzuffj61+gb71k1ARJUCkXbwIl27i2meQaJyRNuMVY4A7oC tSmw3nDPaQyjRv85nfFM5uxfh1/uso+4ZfFXkBHvNw/jKjr3KNJ9fqAcPBazDDbd+dJG VZqH/cCesVT2A0N88MgS23TypMvxIUl6K4b/NsLduz9lYytqduxHvXqixEuk14/6WDeY NvW87sPzKKeh7C9XfE9VBbHf2H5mMR+IHnQZ8+3B9bsY6QgGX9V/fXMtayNYTdavnRIY rPJ0dK4o99lC4q++PQ5FJTmAkMYOFbSg+a0rkWxMqk/KFviv+YRywHNS+6yUwcgwUIvV zQZQ== X-Gm-Message-State: ALoCoQnff/AK5f94EU0OJQOv++XfbGqt3hFxcpeFC13n+A21j/WiEeqUsNwar4AeXg9bqaFJ6nTW X-Received: by 10.140.25.142 with SMTP id 14mr6095174qgt.83.1392858409411; Wed, 19 Feb 2014 17:06:49 -0800 (PST) Original-Received: from e3.local (pool-71-184-176-2.bstnma.east.verizon.net. [71.184.176.2]) by mx.google.com with ESMTPSA id k95sm4555545qgd.22.2014.02.19.17.06.47 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 19 Feb 2014 17:06:48 -0800 (PST) In-Reply-To: <87ppmjqxzn.fsf@motoko.kusanagi> (W. Greenhouse's message of "Wed, 19 Feb 2014 08:59:24 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-TMDA-Confirmed: Thu, 20 Feb 2014 16:20:18 +0100 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: info-gnus-english@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:16704 Archived-At: W. Greenhouse writes: > Taking your last two questions: > > regcl writes: > > [...] > >> C) Compatible mail repo/backup scheme >> >> I need to park the mail I am sweeping somewhere, once again with the >> compartmentalization issues. While I use emacs as my primary email >> client, it would probably be wise not to lock myself in to emacs, so >> maybe I want the mail in a form compatible with other clients on my mac >> os x desktops, most likely mac mail.app. What is the lightest weight >> approach here? Is it maildir with dovecot/localhost? >> >> >> D) Replication of the mail repos. >> >> I don't think I want to put up a pop or imap server on the net, at least >> not now. So I am thinking the problem here is primarily one of >> replication of my mail directories across machines. Am I right? >> >> Based on my limited reading about mail, it seems like this could be done >> with IMAP, but I know zilch about IMAP and I don't have a place to park >> a personal IMAP server on the net. >> >> On the other hand I use git for all of the other replication/syncing >> that I ever do. So here is the question: Can I park my mail in maildir >> with sub-repos for work and play, and use git for replication between >> machines? What would be the pros and cons of this approach vs learning >> using IMAP? > > Git would be sub-optimal for syncing Maildirs around, as would a > standard file-moving tool like rsync, because a fundamental idea of > Maildir is that mail states are expressed by renaming/moving the file. > Whenever Gnus flags something or marks it read, therefore, git or rsync > would treat this like a whole new file, leading to inefficiencies. > Fortunately, there are tools to parse the Maildir format and figure out > which messages are in fact the same on both ends, so we can quickly > rename them to express a change in "flaggedness", instead of resending > the whole thing and deleting the file on the other end (yuck). > Actually, if the contents of a file don't change, git does not create another object, since it recognizes it as the same file because the file's SHA-1 does not change when you move it or rename it. The only overhead of moving or renaming a file is to store its new name and directory, which has to happen anyway for each commit. Since we don't edit incoming mail messages, each mail message will create at most one git storage object. This is why I was thinking git might work well for Maildir. > Here are the two implementations I know of to efficiently sync maildirs > over SSH, without exposing a new network service such as IMAP. (They > also bypass the system MTAs on both ends, as they operate on the end > user's maildirs directly): > > 1. Maildirsync : > Single perl script. Requires you to write your own short shell script > or cron job to handle synchronization. > > 2. http://syncmaildir.sourceforge.net/: a complete rewrite of > maildirsync. Evidently meant to "just work" without writing own shell > hax; I had trouble getting it to install on Slackware, however, so I've > been happily using maildirsync. Syncmaildir seems to be packaged for > Debian-like distros, so that's a consideration. > Thank you. I will compare the features of these to git to try to understand what the relative merits might be. > My configuration looks something like this: > > 1. My almost-always-on homebox slurps various mail sites via fetchmail > using POP3. On landing at the system MTA, the mail gets delivered > (along with any local/daemon-generated mail) to various Maildirs > according to rules in my ~/.procmailrc. > > 2. I read some mail on Gnus at the homebox. When fetchmail->procmail > delivers some new mail to my priority inbox, `display-time-mode' > notifies me by putting a little picture of an envelope on my mode > line. :) Otherwise I don't get prodded about new mail until I poll > Gnus again myself. > > 3. I go on the road with my netbook. On the netbook, I run my maildirsync > script when I have reliable net, and then M-x gnus to read the mail. > > 4. Gnus nnmaildir is pretty self-contained (flags/unread state is all > inside the maildir itself), so if you are only using maildir, > maildirsync will be enough to share state between the two machines. > Since I also read NNTP news with Gnus, however, and also use niceties > like adaptive scoring, I also sync my emacs configuration dir (which > contains the gnus score files and newsrc* files) using Bzr. > Thank you for laying out these details. > TODO: be able to sync just one thing, instead of the sync > mailidr-then-sync-bzr-repo dance. Maybe > http://lars.ingebrigtsen.no/2014/02/01/emacs-cloud/ will help with this > someday. Also, cronify the maildirsync end on the netbook. If we can do both of these functions with git, this issues may be resolved. > > Hope this helps. Please don't hesitate to ask for clarification; I'd be > happy to share any of the configuration files (fetchmail, procmail, > gnus/message/smtpmail/bbdb, maildirsync) that might be interesting. Yes, this is all very helpful, thank you. Once I select an approach I may well want more details. Best, regcl