community/pipermail-archives/sup-talk/2012-08.txt (2843B) - raw
1 From v@asch.cz Thu Aug 2 10:47:12 2012
2 From: v@asch.cz (Vojtech Aschenbrenner)
3 Date: Thu, 02 Aug 2012 12:47:12 +0200
4 Subject: [sup-talk] Detection of messages with Fake Sender
5 Message-ID: <1343904276-sup-842@x220>
6
7 Hello folks.
8
9 Is there any convenient way to detect, which messages has sender marked
10 as "Sup Auto-generated Fake Sender" so I can delete them manually from
11 filesystem? I think, that it could be some old encrypted messages for
12 which I don't have a key anymore or some corrupted messages. When I
13 display detailed header there is a exception:
14
15 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:803:in `index_text'
16 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:684:in `index_message_static'
17 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:645:in `sync_message'
18 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing'
19 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:169:in `block in poll_from'
20 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:106:in `block (2 levels) in poll'
21 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `each'
22 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `each_with_index'
23 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `block in poll'
24 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:90:in `each'
25 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:90:in `poll'
26 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:155:in `poll_from'
27 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing'
28 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup-sync:123:in `block in <top (required)>'
29 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup-sync:118:in `each'
30 /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup-sync:118:in `<top (required)>'
31 /usr/bin/sup-sync:19:in `load'
32 /usr/bin/sup-sync:19:in `<main>'
33
34 I can't identify these messages, any suggestions?
35
36 Regards,
37 Vojtech.
38
39 From v@asch.cz Fri Aug 3 11:49:02 2012
40 From: v@asch.cz (Vojtech Aschenbrenner)
41 Date: Fri, 03 Aug 2012 13:49:02 +0200
42 Subject: [sup-talk] Detection of messages with Fake Sender
43 In-Reply-To: <1343904276-sup-842@x220>
44 References: <1343904276-sup-842@x220>
45 Message-ID: <1343994446-sup-8999@x220>
46
47 Excerpts from Vojtech Aschenbrenner's message of 2012-08-02 12:47:12 +0200:
48 > Hello folks.
49 >
50 > Is there any convenient way to detect, which messages has sender marked
51 > as "Sup Auto-generated Fake Sender" so I can delete them manually from
52 > filesystem? I think, that it could be some old encrypted messages for
53 > which I don't have a key anymore or some corrupted messages. When I
54 > display detailed header there is a exception:
55 Already solved. I didn't find a solution with sup-sync to report a bad
56 message so I wrote a script to detect corrupted raw message.
57