From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs114629ebc; Mon, 25 Jan 2010 13:31:55 -0800 (PST) Received: by 10.91.19.35 with SMTP id w35mr6227658agi.76.1264455114579; Mon, 25 Jan 2010 13:31:54 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 2si12160145gxk.47.2010.01.25.13.31.54; Mon, 25 Jan 2010 13:31:54 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E9AA13C8046; Mon, 25 Jan 2010 16:31:53 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 58E7618582CE for ; Mon, 25 Jan 2010 16:27:37 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NZWTB-0005o9-6l for sup-talk@rubyforge.org; Mon, 25 Jan 2010 16:27:37 -0500 From: William Morgan To: sup-talk In-reply-to: <8b854d6b1001250111i3bf7c27fjc2c91449413cf4e7@mail.gmail.com> References: <8b854d6b1001250111i3bf7c27fjc2c91449413cf4e7@mail.gmail.com> Date: Mon, 25 Jan 2010 16:27:37 -0500 Message-Id: <1264454639-sup-985@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] Signature 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 Reformatted excerpts from Shreyank Gupta's message of 2010-01-25: > Ideally it should identify the last block of text preceded with a '--' > as the signature block. Instead it takes a random block of email body > and condenses it as signature. Sup does detect "-- " (note the space) as the beginning of a "standard" signature block. It also detects several other variants seen in practice. Email being what it is, this detection code is necessarily heuristic and will sometimes generate both false positives and false negatives. > Is there any way around this problem? Provide a patch, or at the least, file a bug report with the specific behavior you are seeing. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk