From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.13.12 with SMTP id z12cs223531ebz; Fri, 8 Jan 2010 08:00:53 -0800 (PST) Received: by 10.224.28.14 with SMTP id k14mr279569qac.190.1262966452110; Fri, 08 Jan 2010 08:00:52 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si24316806qwb.32.2010.01.08.08.00.51; Fri, 08 Jan 2010 08:00:52 -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 6037F1779948; Fri, 8 Jan 2010 11:00:51 -0500 (EST) Received: from mail-yx0-f203.google.com (mail-yx0-f203.google.com [209.85.210.203]) by rubyforge.org (Postfix) with ESMTP id 3417C177993F for ; Fri, 8 Jan 2010 11:00:08 -0500 (EST) Received: by yxe41 with SMTP id 41so65807871yxe.30 for ; Fri, 08 Jan 2010 08:00:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=e5G2AQ426JDb1E6em5TUQmvLEWwY9+lRO9HLHrFOoGc=; b=kqKwawL5YcS6WvuVI3BG8NCmTdRS14fxkzBBnABvc++RtGIKY0iOks8pQzWmCPICxh tkrPKpBM1AC8FpQGy5tJOmZG0AlKi2DzlDpu1qyLyoJyY5RA92tul9gXB/cym5Sw0ikj zb7LUFR+907kPkLe8hXnSzviPlh5GHp5QFU9o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=fuCMWt54cgyhcio9/T7gPnORQ8uWK/IkzlnhsCH1aPP1fnWPc3xScsgfuKQj5ZSC2J E3TUtQyfGkMr30aDSvxWACZfLhxcac7N2qrvwaTNlZ/YegeuoPdiKV2psJijwqmF/ELy PJTYkcqNi3T+ZfYuaUUGa0rMQeARa/NrWgb74= MIME-Version: 1.0 Received: by 10.90.41.14 with SMTP id o14mr9201600ago.25.1262966407540; Fri, 08 Jan 2010 08:00:07 -0800 (PST) In-Reply-To: <1262879727-sup-9702@tilus.net> References: <1246542975-sup-7239@ntdws12.chass.utoronto.ca> <3f81a4241001041055t443931c6vbbe1e7a44599d4f1@mail.gmail.com> <1262728264-sup-3239@masanjin.net> <3f81a4241001061118k7fa0c9e6ub556c400a00b139b@mail.gmail.com> <1262805923-sup-3586@masanjin.net> <1262811731-sup-2447@tilus.net> <1262812952-sup-9357@masanjin.net> <1262879727-sup-9702@tilus.net> Date: Fri, 8 Jan 2010 09:00:07 -0700 Message-ID: <3f81a4241001080800ja97a0bbm9c9c39504ed88bec@mail.gmail.com> From: Bryan Richardson To: sup-talk Subject: Re: [sup-talk] sent_source - singular or per-account? 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org So... I take it I would still look at SentManager.write_sent_message for this? Are all the configuration options from config.yaml gobbled up into an object somewhere when Sup is started? I guess the first question I should really ask is if Tero is going to take a stab at this or if I should... :) On Thu, Jan 7, 2010 at 8:58 AM, Tero Tilus wrote: > William Morgan, 2010-01-06 23:23: >> Reformatted excerpts from Tero Tilus's message of 2010-01-06: >> > Does it really need to be a hook? =A0I haven't seen a single use case >> >> No, I don't care which it is. But you will be responsible for helping >> the first person who wants to automatically choose their sent source >> based on the body of the message. :) > > So be it it, if you (in the other scenario) are willing to help those > who simply want per-account sent_source and are afraid of Ruby. =A0:) > > -- > Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk