From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.218.138 with SMTP id hq10cs96284icb; Fri, 17 Dec 2010 06:25:41 -0800 (PST) Received: by 10.42.227.8 with SMTP id iy8mr872062icb.440.1292595941558; Fri, 17 Dec 2010 06:25:41 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e25si277276vbm.52.2010.12.17.06.25.37; Fri, 17 Dec 2010 06:25:41 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 061E71858390; Fri, 17 Dec 2010 09:25:37 -0500 (EST) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by rubyforge.org (Postfix) with ESMTP id ED9F21858370 for ; Fri, 17 Dec 2010 09:03:38 -0500 (EST) Received: by wwb31 with SMTP id 31so654786wwb.23 for ; Fri, 17 Dec 2010 06:03:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=pL88uzYfKKohCLagOqQsH9GEyDNnGcGK+jMVy0vvzpg=; b=Caq5++06G+KEJ8/kjG+suGW9jsHJ73ikjpydUpceksIooeNwD0OhmzSsTNHQebHkQR oTuGp6TZBNSCyPggTlf5RmqqO+XcXxv00R/7G2Fy8rRE/CJ0KVnWkHWDK0BEzVIYToh4 Vvccr/ofq7WiZKn29v83KNyo5CxecljIJt1Zg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lmWsG29L7L+1RRCUVdSMXt1g3nI6m7o+qzxW1lNJg/wF8WIfTnmt2hMrtsr2PPxB8W Qfwlejd3e18cyAAGse5lfbaUnVX34qbqXdhz6I8M95Cas9u2wnLyPrXnoAakqP7Shi4J wXrNcQkKEq9NYDK71C/YL3m4qWpn6KkHYv68I= MIME-Version: 1.0 Received: by 10.227.142.212 with SMTP id r20mr549704wbu.96.1292594618080; Fri, 17 Dec 2010 06:03:38 -0800 (PST) Received: by 10.227.151.73 with HTTP; Fri, 17 Dec 2010 06:03:38 -0800 (PST) Date: Fri, 17 Dec 2010 16:03:38 +0200 Message-ID: From: Matti Eiden To: sup-talk@rubyforge.org Subject: [sup-talk] Hook for in-reply-to 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hey folks, I gave up using sup a while ago (read half a year) when I began getting a lot of email from my university's Moodle. Moodle has/had a rather stupid bug (now fixed, but it's gonna take years to reach my university), which was that every email that wasn't based on a reply (For example a new forum thread notification at moodle), received a default In-Reply-To header of "moodlepost0@moodle.tamk.fi". You can probably imagine what happens: Every email coming from moodle gets threaded under non-existing email "moodlepost0". In fact, they wont appear in my inbox at all. So I'd need a hook to kill this moodlepost0 from every email I receive. I found this on pastebin, which looks like sup stuff: http://pastebin.com/vzuXu9gr In what file should I use it in? And is there a way to make the whole index go through the hook, so I can recover all my old moodle emails and get them threaded properly too? Thanks, Matti Eiden _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk