community/pipermail-archives/sup-talk/2008-09.txt (15787B) - raw
1 From manish@gslab.com Wed Sep 3 08:03:03 2008
2 From: manish@gslab.com (Manish Sapariya)
3 Date: Wed, 03 Sep 2008 17:33:03 +0530
4 Subject: [sup-talk] CCing to self mail id when composing mail
5 Message-ID: <48BE7CF7.1090103@gslab.com>
6
7 Hi All,
8
9 Two queries:
10
11 First:
12 ======
13 I have configured the ask for CC and I want to CC to
14 myself. I am using sendmail for sending mail. However
15 I am not receiving mail copy to myself. I tried bcc, and
16 specifying my mail id in to field as well.
17
18 Is it sup or sendmail which is removing the self id?
19 any ideas?
20
21 Second:
22 =======
23 Can I configure sup to always include self mail id in CC
24 when composing new mail or replying to any other mail.
25
26
27 Thanks for any help.
28 Regards,
29 Manish
30
31 From wmorgan-sup@masanjin.net Wed Sep 3 23:29:38 2008
32 From: wmorgan-sup@masanjin.net (William Morgan)
33 Date: Wed, 03 Sep 2008 20:29:38 -0700
34 Subject: [sup-talk] CCing to self mail id when composing mail
35 In-Reply-To: <48BE7CF7.1090103@gslab.com>
36 References: <48BE7CF7.1090103@gslab.com>
37 Message-ID: <1220498835-sup-9828@entry>
38
39 Reformatted excerpts from Manish Sapariya's message of 2008-09-03:
40 > I have configured the ask for CC and I want to CC to myself. I am
41 > using sendmail for sending mail. However I am not receiving mail copy
42 > to myself. I tried bcc, and specifying my mail id in to field as well.
43 >
44 > Is it sup or sendmail which is removing the self id? any ideas?
45
46 It's probably your sendmail setup. Sup is just passing that stuff
47 through unchanged. You can try enabling logging on sendmail's end
48 somehow...
49
50 > Can I configure sup to always include self mail id in CC when
51 > composing new mail or replying to any other mail.
52
53 I believe the before-edit hook can be used for this. Place something
54 like the following in ~/.sup/hooks/before-edit.rb:
55
56 header["Cc"] = my at email.address
57
58 (untested!)
59 --
60 William <wmorgan-sup at masanjin.net>
61
62 From daniel.wagner@gmail.com Thu Sep 4 01:53:27 2008
63 From: daniel.wagner@gmail.com (Daniel Wagner)
64 Date: Thu, 04 Sep 2008 01:53:27 -0400
65 Subject: [sup-talk] CCing to self mail id when composing mail
66 In-Reply-To: <48BE7CF7.1090103@gslab.com>
67 References: <48BE7CF7.1090103@gslab.com>
68 Message-ID: <1220507464-sup-1482@buckwheat>
69
70 Excerpts from Manish Sapariya's message of Wed Sep 03 08:03:03 -0400 2008:
71 > Is it sup or sendmail which is removing the self id?
72 > any ideas?
73
74 I don't know if this is related, but I have noticed that sup is a little
75 bit too smart for itself. I sometimes also CC myself. Though these
76 messages appear in my procmail.log, sup seems to recognize that they are
77 a duplicate of a message already in the index, and silently hides them.
78
79 So: check your procmail (or whatever) log to really see whether you are
80 getting a copy.
81 ~d
82
83 From gzjjgod@gmail.com Thu Sep 4 20:20:12 2008
84 From: gzjjgod@gmail.com (Jjgod Jiang)
85 Date: Fri, 5 Sep 2008 08:20:12 +0800
86 Subject: [sup-talk] Error trying to sup-sync a maildir
87 Message-ID: <ddd65cda0809041720x44047f6fmad865841fe0cbefb@mail.gmail.com>
88
89 Hi,
90 When I was trying to sync my maildir (which was synced from gmail with
91 isync)
92 using sup-sync, after it loaded 1328 messages, it crashed with the
93 following
94 backtrace:
95
96 /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/message.rb:376:in
97 `message_to_chunks': undefined method `multipart?' for
98 #<Redwood::Chunk::CryptoNotice:0x26b2fe0> (NoMethodError)
99 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/message.rb:371:in
100 `multipart_encrypted_to_chunks'
101 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/message.rb:382:in
102 `message_to_chunks'
103 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/message.rb:214:in
104 `load_from_source!'
105 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/message.rb:194:in `chunks'
106 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/message.rb:144:in `snippet'
107 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/index.rb:182:in
108 `sync_message'
109 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/util.rb:499:in `send'
110 from /Library/Ruby/Gems/1.8/gems/sup-0.6/lib/sup/util.rb:499:in
111 `method_missing'
112 ... 11 levels...
113 from /Library/Ruby/Gems/1.8/gems/sup-0.6/bin/sup-sync:131:in `each'
114 from /Library/Ruby/Gems/1.8/gems/sup-0.6/bin/sup-sync:131
115 from /usr/bin/sup-sync:19:in `load'
116 from /usr/bin/sup-sync:19
117 Rats, that failed. You may have to do it manually.
118
119 Is there anything I can do to solve this issue?
120
121 - Jiang
122 -------------- next part --------------
123 An HTML attachment was scrubbed...
124 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080905/808fb64c/attachment.html>
125
126 From wmorgan-sup@masanjin.net Mon Sep 8 14:47:43 2008
127 From: wmorgan-sup@masanjin.net (William Morgan)
128 Date: Mon, 08 Sep 2008 11:47:43 -0700
129 Subject: [sup-talk] CCing to self mail id when composing mail
130 In-Reply-To: <1220507464-sup-1482@buckwheat>
131 References: <48BE7CF7.1090103@gslab.com> <1220507464-sup-1482@buckwheat>
132 Message-ID: <1220899449-sup-112@entry>
133
134 Reformatted excerpts from Daniel Wagner's message of 2008-09-03:
135 > I don't know if this is related, but I have noticed that sup is a
136 > little bit too smart for itself. I sometimes also CC myself. Though
137 > these messages appear in my procmail.log, sup seems to recognize that
138 > they are a duplicate of a message already in the index, and silently
139 > hides them.
140
141 Oh yeah. Sup collapses dupes. That would do it.
142
143 That's another interesting lesson I've learned about email in the
144 process of writing Sup. Two messages with the same message id are more
145 likely than not to NOT be exactly the same message. For example, any
146 time you get a message both cc'ed and through a mailing list, they'll
147 have the same message id, but the mailing list one will probably have
148 extra content (ML signatures and taglines) and different headers.
149 --
150 William <wmorgan-sup at masanjin.net>
151
152 From nicolas.pouillard@gmail.com Mon Sep 8 15:29:20 2008
153 From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
154 Date: Mon, 08 Sep 2008 21:29:20 +0200
155 Subject: [sup-talk] CCing to self mail id when composing mail
156 In-Reply-To: <1220899449-sup-112@entry>
157 References: <48BE7CF7.1090103@gslab.com> <1220507464-sup-1482@buckwheat>
158 <1220899449-sup-112@entry>
159 Message-ID: <1220902090-sup-3097@ausone.local>
160
161 Excerpts from William Morgan's message of Mon Sep 08 20:47:43 +0200 2008:
162 > Reformatted excerpts from Daniel Wagner's message of 2008-09-03:
163 > > I don't know if this is related, but I have noticed that sup is a
164 > > little bit too smart for itself. I sometimes also CC myself. Though
165 > > these messages appear in my procmail.log, sup seems to recognize that
166 > > they are a duplicate of a message already in the index, and silently
167 > > hides them.
168 >
169 > Oh yeah. Sup collapses dupes. That would do it.
170 >
171 > That's another interesting lesson I've learned about email in the
172 > process of writing Sup. Two messages with the same message id are more
173 > likely than not to NOT be exactly the same message. For example, any
174 > time you get a message both cc'ed and through a mailing list, they'll
175 > have the same message id, but the mailing list one will probably have
176 > extra content (ML signatures and taglines) and different headers.
177
178 Do you get a conclusion, concerning email-tools design?
179
180 --
181 Nicolas Pouillard aka Ertai
182 -------------- next part --------------
183 A non-text attachment was scrubbed...
184 Name: signature.asc
185 Type: application/pgp-signature
186 Size: 194 bytes
187 Desc: not available
188 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080908/266c08d5/attachment.bin>
189
190 From israel.herraiz@gmail.com Tue Sep 9 06:45:27 2008
191 From: israel.herraiz@gmail.com (Israel Herraiz)
192 Date: Tue, 09 Sep 2008 12:45:27 +0200
193 Subject: [sup-talk] Inbox mode loads all the messages
194 Message-ID: <1220956744-sup-911@elly>
195
196 Hi all,
197
198 my inbox view is loading all the messages. It is quite strange,
199 because those messages do not have the "inbox" label. If I archive
200 them, save the changes, quit sup, and start sup, it will load all
201 the messages again.
202
203 If I search "label:inbox", it finds all the messages, even those that
204 do not have the "inbox" label.
205
206 I am using the Git version of sup, and I have not made any changes
207 neither a pull since the last time sup worked correctly. I have
208 updated ruby however (1.8.7 2008-06-20 patchlevel 22). But I updated
209 it some days ago, and it has been working correctly during some days.
210
211 I am probably have too many labels (108). I don't know if I have
212 reached some kind of limit :-).
213
214 Any hint about what is going on with my sup?
215
216 Cheers,
217 Israel
218
219 From wmorgan-sup@masanjin.net Wed Sep 10 16:29:44 2008
220 From: wmorgan-sup@masanjin.net (William Morgan)
221 Date: Wed, 10 Sep 2008 13:29:44 -0700
222 Subject: [sup-talk] Inbox mode loads all the messages
223 In-Reply-To: <1220956744-sup-911@elly>
224 References: <1220956744-sup-911@elly>
225 Message-ID: <1221078119-sup-1715@entry>
226
227 Reformatted excerpts from israel.herraiz's message of 2008-09-09:
228 > my inbox view is loading all the messages. It is quite strange,
229 > because those messages do not have the "inbox" label. If I archive
230 > them, save the changes, quit sup, and start sup, it will load all
231 > the messages again.
232
233 Very weird. Do searches for other labels work correctly? What about
234 searches for regular words?
235
236 > I am probably have too many labels (108). I don't know if I have
237 > reached some kind of limit :-).
238
239 There's no label limit. Ferret treats them as regular words so it should
240 be able to scale to, like, trillions.
241
242 You could try creating a small set of emails and starting a fresh Sup on
243 it (set the environment variable SUP_BASE to a new directory and Sup
244 will use that as its configuration dir instead of ~/.sup),and seeing if
245 Sup exhibits the same behavior on that. That would at least narrow it
246 down to something having happened to your system (new Ruby, new and
247 incompatible Ferret, etc.).
248 --
249 William <wmorgan-sup at masanjin.net>
250
251 From israel.herraiz@gmail.com Wed Sep 10 17:40:46 2008
252 From: israel.herraiz@gmail.com (Israel Herraiz)
253 Date: Wed, 10 Sep 2008 23:40:46 +0200
254 Subject: [sup-talk] Inbox mode loads all the messages
255 In-Reply-To: <1221078119-sup-1715@entry>
256 References: <1220956744-sup-911@elly> <1221078119-sup-1715@entry>
257 Message-ID: <1221082291-sup-9750@elly>
258
259 Excerpts from William's message on Sep 10, 2008 about 10 PM:
260 > Very weird. Do searches for other labels work correctly? What about
261 > searches for regular words?
262
263 Some searches work well, some others not. Those that do not work show
264 all the same messages incorrectly shown in the inbox. It seems like
265 those messages would be "persistent", and they are shown everywhere.
266
267 > There's no label limit. Ferret treats them as regular words so it should
268 > be able to scale to, like, trillions.
269
270 Ok. Good to know.
271
272 > You could try creating a small set of emails and starting a fresh Sup on
273 > it (set the environment variable SUP_BASE to a new directory and Sup
274 > will use that as its configuration dir instead of ~/.sup),and seeing if
275 > Sup exhibits the same behavior on that. That would at least narrow it
276 > down to something having happened to your system (new Ruby, new and
277 > incompatible Ferret, etc.).
278
279 I killed all those messages. That removed them from the inbox,
280 although they persisted in the searches.
281
282 I had all the messages in two mboxes file. One of about 500 MB (inbox), and
283 another one of 1 GB (mbox). I moved all the messages to one file (~1.5
284 GB), and after that I ran sup-sync with --all-sources and -as-is and
285 some other options I don't remember. However, the same behavior
286 persisted.
287
288 So I decided to access the index directly from ruby. I recovered all
289 the killed messages, added them the inbox label, saved the index,
290 removed the killed and inbox labels, saved again, and now it is
291 working.
292
293 Probably it is an issue with Ferret. Or maybe it is because my email
294 volume. Unfortunately, I did not keep the non-working index. If I find
295 the same issue again, I will try to make a copy of the index just in
296 case you want to try to reproduce the bug.
297
298 Thanks anyway for your comments.
299
300 Cheers,
301 Israel
302
303 From kapil.foss@gmail.com Thu Sep 11 13:43:20 2008
304 From: kapil.foss@gmail.com (Kapil Thangavelu)
305 Date: Thu, 11 Sep 2008 13:43:20 -0400
306 Subject: [sup-talk] problems downloading 0.6
307 Message-ID: <9c97bd2b0809111043k6d9f364tea895c80640b8b3a@mail.gmail.com>
308
309 hi folks,
310
311 i was trying to give sup, but ran into some installation issues. attempting
312 to download sup via gem
313 turns in an error where ruby forge has tagged the sup distribution file as a
314 virus.
315
316 ie. picking a random mirror for example link
317
318 http://rubyforge.rubyuser.de/sup/sup-0.6.tgz
319 leads to
320 """
321 File has been dropped.
322
323 ProxyAV Administrator: unknown
324
325 2008-09-11 13:40:56-04:00EDT
326 Hardware serial number: 1908081029
327 ProxyAV (Version 3.1.2.1(34850)) - http://www.BlueCoat.com/
328 Antivirus Vendor: Kaspersky Labs
329 Scan Engine Version: 5.0.0.38
330 Pattern File Version: 080911.160218.1213098 (Timestamp: 2008.09.11 16:02:18)
331
332 Machine name: ProxyAV2
333 Machine IP address: 140.147.236.197
334 Server: 80.237.222.133
335 Client: 140.147.174.68
336 Protocol: ICAP
337
338 Virus: "Exploit.HTML.Iframe.FileDownload" found!
339 URL: http://rubyforge.rubyuser.de/sup/sup-0.6.tgz
340 """
341
342 any ideas on a work around?
343
344 thanks,
345
346 kapil
347 -------------- next part --------------
348 An HTML attachment was scrubbed...
349 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080911/52f7a989/attachment.html>
350
351 From sup@davekap.com Thu Sep 18 11:21:55 2008
352 From: sup@davekap.com (Gladwright)
353 Date: Thu, 18 Sep 2008 08:21:55 -0700 (PDT)
354 Subject: [sup-talk] thunderbird import success
355 Message-ID: <19555367.post@talk.nabble.com>
356
357
358 'Sup?
359
360 I had large Thunderbird files to import. Similar to other reports here,
361 importing the files as mboxes didn't work for me.
362
363 I converted the mboxes to maildirs using mb2md, and then imported, and all
364 was well.
365
366 I'm pretty new to Linux and Ruby with aspirations to be proficient in both.
367 I was thrilled to find Sup. I had so been longing for a different email
368 experience, and so far Sup is giving me what I needed, plus it's written in
369 Ruby. Yahoo!
370
371 Cheers,
372 Dave
373 --
374 View this message in context: http://www.nabble.com/thunderbird-import-success-tp19555367p19555367.html
375 Sent from the SUP Talk mailing list archive at Nabble.com.
376
377
378 From wmorgan-sup@masanjin.net Thu Sep 18 15:41:17 2008
379 From: wmorgan-sup@masanjin.net (William Morgan)
380 Date: Thu, 18 Sep 2008 12:41:17 -0700
381 Subject: [sup-talk] thunderbird import success
382 In-Reply-To: <19555367.post@talk.nabble.com>
383 References: <19555367.post@talk.nabble.com>
384 Message-ID: <1221766839-sup-286@entry>
385
386 Reformatted excerpts from Gladwright's message of 2008-09-18:
387 > I had large Thunderbird files to import. Similar to other reports here,
388 > importing the files as mboxes didn't work for me.
389 >
390 > I converted the mboxes to maildirs using mb2md, and then imported, and all
391 > was well.
392
393 Great, very good to know.
394
395 > I'm pretty new to Linux and Ruby with aspirations to be proficient in
396 > both. I was thrilled to find Sup. I had so been longing for a
397 > different email experience, and so far Sup is giving me what I needed,
398 > plus it's written in Ruby.
399
400 Glad you like it!
401 --
402 William <wmorgan-sup at masanjin.net>
403
404 From sup@davekap.com Fri Sep 19 23:21:15 2008
405 From: sup@davekap.com (Gladwright)
406 Date: Fri, 19 Sep 2008 20:21:15 -0700 (PDT)
407 Subject: [sup-talk] thunderbird import success
408 In-Reply-To: <1221766839-sup-286@entry>
409 References: <19555367.post@talk.nabble.com> <1221766839-sup-286@entry>
410 Message-ID: <19582301.post@talk.nabble.com>
411
412
413
414 I added a guide for ThunderbirdImport to the wiki. As I'm just a newb, I
415 hope everyone will feel free to improve on its format, language, and
416 details. I included some ruby commands I used in irb to automate some of
417 the steps. I'm relatively a ruby newb too, so I would enjoy seeing
418 improvements there as well.
419
420 Cheers,
421 Dave
422 --
423 View this message in context: http://www.nabble.com/thunderbird-import-success-tp19555367p19582301.html
424 Sent from the SUP Talk mailing list archive at Nabble.com.
425
426