From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.174.193 with SMTP id u1cs68676bkz; Sat, 1 May 2010 11:10:19 -0700 (PDT) Received: by 10.216.185.82 with SMTP id t60mr4824138wem.149.1272737418800; Sat, 01 May 2010 11:10:18 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id f24si9410730wbf.1.2010.05.01.11.10.18; Sat, 01 May 2010 11:10:18 -0700 (PDT) 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=@messagingengine.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 7ACFC18582FF; Sat, 1 May 2010 14:10:16 -0400 (EDT) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by rubyforge.org (Postfix) with ESMTP id 0C9201858309 for ; Sat, 1 May 2010 13:12:22 -0400 (EDT) Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id CA3E6EDFA7 for ; Sat, 1 May 2010 13:12:18 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 01 May 2010 13:12:18 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=date:from:to:subject:in-reply-to:message-id:references:mime-version:content-type; s=smtpout; bh=hd4dOoejR/deduNuCsP+6gmYSoA=; b=IRK0+WrmxcDihpinZ/baQ0Z7oKIRVwb/MQ1L9V7m6yn8S0NNqMzo/iw4sSTeeIeOR0XJr9h42cxFNjkTrGcofDBxn0yJNC1RZVLySfXtTBUgoilfW36wqDlAsar+K5cR1f83pYkwQ9xwBsco4uyI2G7QiSaLajgzF+hSnlI6sfA= X-Sasl-enc: JEQXX5bFuliDF1DE6nJsig0NXwf3l1DdlgA4d9i+I3W7 1272733938 Received: from sysopweg.local (c-24-3-244-168.hsd1.pa.comcast.net [24.3.244.168]) by mail.messagingengine.com (Postfix) with ESMTPSA id 744381AF97 for ; Sat, 1 May 2010 13:12:18 -0400 (EDT) Date: Sat, 1 May 2010 13:12:17 -0400 (EDT) From: Erik Quaeghebeur To: sup-talk In-Reply-To: <1272708559-sup-108@windir> Message-ID: References: <1272708559-sup-108@windir> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Subject: Re: [sup-talk] Multiple accounts handling 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Sat, 1 May 2010, Damien Leone wrote: > > My main issue is about selecting the proper account when I compose a > new mail, most informations I read was about filtering the "to:" field > in the "before-edit" hook to set up the "from:" field, but I use to > send mails to various recipients using different accounts. > > Is there a way to get an "Account" horizontal selector in the edit > screen just like the "Reply to" and "Crypto" ones? That would be > perfect to select our account regardless of the "to:" field. Other ways of looking at it: * create a 'personalities' feature that would override the To:-logic when activated and use the selected personality. * a way of specifying the From: as is currently done with the To: and Cc: headers, using nicks and tab-completion from addresses in the contact list, which would be useful as well in situations where one wants to send mail with a from that includes multiple addresses (yes, this is useful sometimes, best in combination with the non-self adresses added to Bcc). Best, Erik _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk