community/pipermail-archives/sup-talk/2012-09.txt (12821B) - raw
1 From naveen@lastninja.net Wed Sep 19 21:15:00 2012
2 From: naveen@lastninja.net (Naveen Nathan)
3 Date: Wed, 19 Sep 2012 14:15:00 -0700
4 Subject: [sup-talk] any testimonials from users who transitioned from mutt?
5 Message-ID: <20120919211500.GH48050@armakuni.lastninja.net>
6
7 Hi,
8
9 Mutt and mail savvy user here. It's my daily use client, I use a lot of
10 it's features such as threading, tagging, header caching (for imap).
11
12 What it truly lacks, even though slightly supported by IMAP, is full-body
13 search of email, indexing, etc.
14
15 I was wondering if any mutt users who use some of the above features
16 mentioned would mind sharing their experience after transitioning to Sup.
17 Although I wouldn't be surprised if people still continue to use both.
18
19 - Naveen
20
21
22 From masterkorp@masterkorp.net Wed Sep 19 21:47:19 2012
23 From: masterkorp@masterkorp.net (Alfredo Palhares)
24 Date: Wed, 19 Sep 2012 23:47:19 +0200
25 Subject: [sup-talk] any testimonials from users who transitioned from
26 mutt?
27 In-Reply-To: <20120919211500.GH48050@armakuni.lastninja.net>
28 References: <20120919211500.GH48050@armakuni.lastninja.net>
29 Message-ID: <1348090678-sup-2446@masterkorp.net>
30
31 Excerpts from Naveen Nathan's message of Wed Sep 19 23:15:00 +0200 2012:
32 > Hi,
33 >
34 > Mutt and mail savvy user here. It's my daily use client, I use a lot of
35 > it's features such as threading, tagging, header caching (for imap).
36 >
37 > What it truly lacks, even though slightly supported by IMAP, is full-body
38 > search of email, indexing, etc.
39 What i notice the most, is *speed*, mutt gets unbearable on big mailboxes.
40 Also the label is approach is much better, just because having more than one label
41 in an thread can be very usefull.
42 Also prefer the UI, tudier for tilling WMs and smarthphones (altough mutt can be
43 customized)
44
45 > I was wondering if any mutt users who use some of the above features
46 > mentioned would mind sharing their experience after transitioning to Sup.
47 > Although I wouldn't be surprised if people still continue to use both.
48 One thing about sup, is that you have to go cold turkey, sup does not sync
49 back to the mailbox. I solved that problem by placing it under tmux on a
50 24/7 avaliable server, so i just ssh to tmux, from the computer, cellphone,
51 public machine whatever.
52
53 I eventually want to migrate to heliotrope once a decent client shows up.
54
55 But if you're on mutt and dont bother about using only one client for email,
56 Sup is awesome
57
58 --
59 Regards,
60 Alfredo Palhares
61
62 From allan_wind@lifeintegrity.com Wed Sep 19 21:56:57 2012
63 From: allan_wind@lifeintegrity.com (Allan Wind)
64 Date: Wed, 19 Sep 2012 17:56:57 -0400
65 Subject: [sup-talk] any testimonials from users who transitioned from
66 mutt?
67 In-Reply-To: <20120919211500.GH48050@armakuni.lastninja.net>
68 References: <20120919211500.GH48050@armakuni.lastninja.net>
69 Message-ID: <20120919215657.GA17624@lifeintegrity.com>
70
71 On 2012-09-19 14:15:00, Naveen Nathan wrote:
72 > I was wondering if any mutt users who use some of the above features
73 > mentioned would mind sharing their experience after transitioning to Sup.
74 > Although I wouldn't be surprised if people still continue to use both.
75
76 sup, afaik, is dead <http://masanjin.net/>:
77
78 I leave behind me the wreckage of unmaintained or handed-off
79 projects:
80 ...
81 Sup, an email client for people with lots of mail.
82
83 You may, however, want to check out <http://notmuchmail.org/> and
84 <https://github.com/karelzak/mutt-kz>
85
86
87 /Allan
88 --
89 Allan Wind
90 Life Integrity, LLC
91 <http://lifeintegrity.com>
92
93 From jim@gonzul.net Thu Sep 20 00:12:54 2012
94 From: jim@gonzul.net (Jim Cheetham)
95 Date: Thu, 20 Sep 2012 12:12:54 +1200
96 Subject: [sup-talk] any testimonials from users who transitioned from
97 mutt?
98 In-Reply-To: <20120919215657.GA17624@lifeintegrity.com>
99 References: <20120919211500.GH48050@armakuni.lastninja.net>
100 <20120919215657.GA17624@lifeintegrity.com>
101 Message-ID: <CA+2knquXHSnK=uBoNCFDG6q58o4+S4k5AHNi86dVnH6PQmDsuA@mail.gmail.com>
102
103 On Thu, Sep 20, 2012 at 9:56 AM, Allan Wind
104 <allan_wind at lifeintegrity.com> wrote:
105 > On 2012-09-19 14:15:00, Naveen Nathan wrote:
106 > sup, afaik, is dead <http://masanjin.net/>:
107 >
108 > I leave behind me the wreckage of unmaintained or handed-off
109 > projects:
110 > ...
111 > Sup, an email client for people with lots of mail.
112 >
113 > You may, however, want to check out <http://notmuchmail.org/> and
114 > <https://github.com/karelzak/mutt-kz>
115
116 Well, I've moved on from sup because of the non-maintained status, and
117 problems with gpgme versions.
118 Now running heliotrope/turnsole, and in general it's fine, almost as
119 good as sup but with many more rough edges. Turnsole crashes a lot,
120 which isn't a big problem because state is in heliotrope & not the
121 client; but some features seem to be missing completely -- I haven't
122 figured out GPG signing yet. I expect that before_add hooks would need
123 in heliotrope and I haven't looked for them yet.
124
125 However, looking at the original post, perhaps notmuch with mutt
126 integration (i.e. it creates temporary folders based on searches)
127 would suit well?
128
129 -jim
130
131 From sup@zevv.nl Thu Sep 20 06:43:53 2012
132 From: sup@zevv.nl (Ico)
133 Date: Thu, 20 Sep 2012 08:43:53 +0200
134 Subject: [sup-talk] any testimonials from users who transitioned from
135 mutt?
136 In-Reply-To: <20120919211500.GH48050@armakuni.lastninja.net>
137 References: <20120919211500.GH48050@armakuni.lastninja.net>
138 Message-ID: <1348123080-sup-7217@pruts.nl>
139
140 > Mutt and mail savvy user here. It's my daily use client, I use a lot of
141 > it's features such as threading, tagging, header caching (for imap).
142 >
143 > What it truly lacks, even though slightly supported by IMAP, is full-body
144 > search of email, indexing, etc.
145
146 I've been a long time mutt user before switching to sup a few years ago. Mutt
147 indeed lacks proper searching and indexing, but for this I found mairix [1],
148 which with some scripting [2], .muttrc [3] configuration and a cronjob [4] can
149 be integrated into mutt pretty seamless.
150
151 I eventually switched to sup not mainly for of the indexing/searching, but
152 because of the unique way sup keeps track of threads.
153
154 Now that sup is pretty much dead I find myself poking around in the
155 source more and more often, but maybe it is about time to switch back to
156 mutt for more stability :(
157
158
159
160 1. http://www.rpcurnow.force9.co.uk/mairix/
161
162 2. ~/bin/searchmail
163
164 #!/bin/sh
165
166 echo -n "Search for: "
167 read expr
168
169 echo $expr
170
171 if [ "$expr" = "" ]; then
172 clear
173 mairix --help
174 read
175 exit
176 fi
177
178 mairix $expr
179
180 3. .muttrc
181
182 macro index <esc>s !searchmail\nc=searched\n
183 macro pager <esc>s !searchmail\nc=searched\n
184
185 4. crontab
186
187 */10 * * * * ~/bin/mairix
188
189 --
190 :wq
191 ^X^Cy^K^X^C^C^C^C
192
193 From sdothum@gmail.com Thu Sep 20 22:25:23 2012
194 From: sdothum@gmail.com (Steven Hum)
195 Date: Thu, 20 Sep 2012 18:25:23 -0400
196 Subject: [sup-talk] any testimonials from users who transitioned from
197 mutt?
198 In-Reply-To: <1348123080-sup-7217@pruts.nl>
199 References: <20120919211500.GH48050@armakuni.lastninja.net>
200 <1348123080-sup-7217@pruts.nl>
201 Message-ID: <1348177473-sup-7941@monad>
202
203 I have used mutt with notmuch for ages and thought I would never switch
204 until I came across sup recently. (notmuch, by the way is a very
205 competent search mechanism - I believe there is even a mutt fork afoot
206 to integrate it more seamlessly into mutt).
207
208 sup does not back sync to maildir which for me should be a deal breaker
209 as I like using offlineimap/imapfilter to maintain persistent mail on my
210 desktop and laptop which allows me to peruse and respond to emails even
211 when I am not connected to the Internet.
212
213 Alas, I find sup so compelling a mail client that I am, for now, willing
214 to put up with that serious lack. There are sup forks I have been
215 looking into that appear to address this issue - but I am not sure if
216 anyone is going to spearhead taking sup over officially to merge the
217 work done in this area.
218
219 The heliotrope/turnsole project is still not ready for prime time
220 - beyond installation for me at least, the turnsole client crashes
221 a lot. Even then, I am not sure if heliotrope will address the maildir
222 back sync issue (there is an imaptrope fork which may address this). If
223 it doesn't, it may not provide me with any benefit towards my offline
224 mail usage.
225
226 Like earlier posts, sup's tagging, smart conversation view (with only
227 unread messages expanded - I am not sure if even Google's web gmail
228 interface offers that) and facility to auto archive
229 threads/folders/whatever rules you wish, just makes the email process
230 more compelling and effective (for me) by eliminating inbox noise.
231
232 The big back sync issue, however, does mean sup is non-destructive, so
233 is worth a look if you are one of those people who is forever looking
234 for the perfect email client (that sucks less :-) mutt will stay on my
235 system if sup's maildir deficiency becomes intolerable - for now,
236 I foresee using it to periodically prune and manage my maildirs.
237
238 Steven
239 --
240 "Truth or die."
241
242 Steven Hum
243 5 - 28 Gilmour St
244 Ottawa, ON K2P 0N3
245 email sdothum at gmail.com
246 tel 613.237.9058
247
248 From matthieu.rakotojaona@gmail.com Thu Sep 20 23:58:34 2012
249 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
250 Date: Fri, 21 Sep 2012 01:58:34 +0200
251 Subject: [sup-talk] any testimonials from users who transitioned from
252 mutt?
253 In-Reply-To: <1348177473-sup-7941@monad>
254 References: <20120919211500.GH48050@armakuni.lastninja.net>
255 <1348123080-sup-7217@pruts.nl> <1348177473-sup-7941@monad>
256 Message-ID: <CAMiZLn3pLumCw2Zmm6i+5hV8y_FtgjDBtDjJH57qhVoRONWT5g@mail.gmail.com>
257
258 On Fri, Sep 21, 2012 at 12:25 AM, Steven Hum <sdothum at gmail.com> wrote:
259 > Even then, I am not sure if heliotrope will address the maildir
260 > back sync issue (there is an imaptrope fork which may address this). If
261 > it doesn't, it may not provide me with any benefit towards my offline
262 > mail usage.
263
264 I guess you're talking about https://github.com/rakoo/imaptrope. This
265 was actually the only reason why I didn't use heliotrope/turnsole (and
266 sup before it) full-time : I didn't want to do some gymnastics back
267 and forth for my mail, like everyone here. That's why I started
268 imaptrope. Unfortunately, I arrived to a point where using http
269 doesn't give me sufficient speed for the task. So I set out to
270 integrate it directly in heliotrope.
271
272 The result of my work is at
273 https://github.com/rakoo/heliotrope/tree/imap. You can now run an imap
274 server along the http one with the following command :
275
276 ruby -Ilib bin/heliotrope-server -d /path/to/data --with-imap
277
278 and connect to it on localhost:10142. As I explain in the README, the
279 goal is not to do a fully functional IMAP server, but just enough bits
280 to work with OfflineIMAP. This software does a great job, and will be
281 a very helpful tool for a smooth transition. This will be better than
282 reimplementing some 2-way-syncing-magic once again.
283
284 For the moment, heliotrope -> maildir works with a standard
285 offlineimap installation. Yay ! Don't do it on big mailboxes though,
286 because it will be horribly long (and by big I mean 100 messages. Yes,
287 that's not big, I'm working on it)
288
289 It is saddening to see that many people are interested in this great
290 project yet seems to be dying. I was thinking this may be due to
291 William abandoning sup in favor of heliotrope, and everyone still
292 following the former ? Anyway, I'll be happily hacking on heliotrope,
293 so everyone who is willing to continue is warmly invited to test
294 things out !
295
296
297 --
298 Matthieu RAKOTOJAONA
299
300 From matthieu.rakotojaona@gmail.com Mon Sep 24 22:13:57 2012
301 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
302 Date: Tue, 25 Sep 2012 00:13:57 +0200
303 Subject: [sup-talk] Update in heliotrope !
304 Message-ID: <CAMiZLn3ipaH=j+-hZBmnb-XhFc1QwQFG7J-Mqw2oHmvuuKRKzw@mail.gmail.com>
305
306 Hello everyone,
307
308 I have updated my version of heliotrope on my imap branch
309 (https://github.com/rakoo/heliotrope/tree/imap). You just have to
310 clone it and checkout the branch.
311 You may now synchronize your mails between heliotrope and a maildir
312 with offlineimap. I tested most of the situations that can happen
313 when using it (Adding/removing a label on heliotrope side,
314 adding/removing a mail on maildir side)
315
316 A few notes :
317
318 * It is not "multi-write-safe", in the sense that you should stop all
319 other activity with heliotrope while you sync with offlinimap.
320 Concurrent access will have unknown outcome.
321 * To continue on this point, use offlineimap with the `-1` flag, which
322 will turn off multithreading. It should work without it though,
323 because AFAIK offlineimap threads do not share mailboxes. But I'm not
324 sure.
325 * There are a few hardcoded labels/dir that you should find in your
326 maildir, such as INBOX/inbox and "All Mail", which has no equivalent
327 in heliotrope. Fear not, this one is taken care of.
328 * Syncing with another IMAP server should also work,because it is
329 transparent to offlineimap (at least from the outside)
330
331 Have fun !
332
333 --
334 Matthieu RAKOTOJAONA
335