From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.172.101 with SMTP id bb5csp147497vdc; Thu, 2 Aug 2012 03:55:06 -0700 (PDT) Received: by 10.60.1.69 with SMTP id 5mr35319032oek.66.1343904906239; Thu, 02 Aug 2012 03:55:06 -0700 (PDT) Return-Path: Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com. [50.56.192.79]) by mx.google.com with ESMTP id kq10si6906297obb.30.2012.08.02.03.55.05; Thu, 02 Aug 2012 03:55:06 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 1B46E2E06F; Thu, 2 Aug 2012 10:55:05 +0000 (UTC) X-Greylist: delayed 454 seconds by postgrey-1.31 at rubyforge; Thu, 02 Aug 2012 10:54:50 UTC Received: from satan.local (212.140.broadband10.iol.cz [90.177.140.212]) by rubyforge.org (Postfix) with ESMTP id C35092E05D for ; Thu, 2 Aug 2012 10:54:50 +0000 (UTC) Received: from localhost (x220.local [10.0.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: asch) by satan.local (Postfix) with ESMTPSA id 5FEFB79E5C for ; Thu, 2 Aug 2012 12:47:13 +0200 (CEST) From: Vojtech Aschenbrenner To: sup-talk Date: Thu, 02 Aug 2012 12:47:12 +0200 Message-Id: <1343904276-sup-842@x220> User-Agent: Sup/0.12.1 Subject: [sup-talk] Detection of messages with Fake Sender X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hello folks. Is there any convenient way to detect, which messages has sender marked as "Sup Auto-generated Fake Sender" so I can delete them manually from filesystem? I think, that it could be some old encrypted messages for which I don't have a key anymore or some corrupted messages. When I display detailed header there is a exception: /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:803:in `index_text' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:684:in `index_message_static' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:645:in `sync_message' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:169:in `block in poll_from' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:106:in `block (2 levels) in poll' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `each_with_index' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:105:in `block in poll' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:90:in `each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/maildir.rb:90:in `poll' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/poll.rb:155:in `poll_from' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/util.rb:609:in `method_missing' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup-sync:123:in `block in ' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup-sync:118:in `each' /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup-sync:118:in `' /usr/bin/sup-sync:19:in `load' /usr/bin/sup-sync:19:in `
' I can't identify these messages, any suggestions? Regards, Vojtech. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk