From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.172.101 with SMTP id bb5csp183212vdc; Fri, 3 Aug 2012 04:49:27 -0700 (PDT) Received: by 10.182.174.70 with SMTP id bq6mr3833368obc.78.1343994566566; Fri, 03 Aug 2012 04:49:26 -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 qd10si13600855obc.116.2012.08.03.04.49.26; Fri, 03 Aug 2012 04:49:26 -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 088E32E073; Fri, 3 Aug 2012 11:49:25 +0000 (UTC) Received: from satan.local (212.140.broadband10.iol.cz [90.177.140.212]) by rubyforge.org (Postfix) with ESMTP id ABF962E06B for ; Fri, 3 Aug 2012 11:49:05 +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 F3FEC7A527 for ; Fri, 3 Aug 2012 13:49:02 +0200 (CEST) From: Vojtech Aschenbrenner To: sup-talk In-reply-to: <1343904276-sup-842@x220> References: <1343904276-sup-842@x220> Date: Fri, 03 Aug 2012 13:49:02 +0200 Message-Id: <1343994446-sup-8999@x220> User-Agent: Sup/0.12.1 Subject: Re: [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 Excerpts from Vojtech Aschenbrenner's message of 2012-08-02 12:47:12 +0200: > 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: Already solved. I didn't find a solution with sup-sync to report a bad message so I wrote a script to detect corrupted raw message. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk