From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs235767vdc; Wed, 11 May 2011 08:18:12 -0700 (PDT) Received: by 10.52.180.72 with SMTP id dm8mr1255268vdc.118.1305127092135; Wed, 11 May 2011 08:18:12 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id m16si236006vcm.88.2011.05.11.08.18.12; Wed, 11 May 2011 08:18:12 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DCC6A18583A7; Wed, 11 May 2011 11:18:11 -0400 (EDT) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by rubyforge.org (Postfix) with SMTP id BB0631858372 for ; Wed, 11 May 2011 11:08:50 -0400 (EDT) Received: (qmail invoked by alias); 11 May 2011 15:08:48 -0000 Received: from hmbg-4d06d0fe.pool.mediaWays.net (EHLO localhost) [77.6.208.254] by mail.gmx.net (mp021) with SMTP; 11 May 2011 17:08:48 +0200 X-Authenticated: #67991182 X-Provags-ID: V01U2FsdGVkX18RjkRQX+ARxr4ieTBNf3kFf5YcqlzNE5F+WhBSMo K/7LrEqp7epIyG From: dtk To: Patrick Totzke In-reply-to: <1305109172-sup-2288@minibox> References: <1305058093-sup-1016@minibox> <1305063169-sup-9131@chigamba> <1305067227-sup-4227@minibox> <1305072191-sup-3288@minibox> <1305105912-sup-2960@brick> <1305109172-sup-2288@minibox> Date: Wed, 11 May 2011 17:08:48 +0200 Message-Id: <1305126047-sup-8239@minibox> User-Agent: Sup/git X-Y-GMX-Trusted: 0 Cc: sup-talk Subject: Re: [sup-talk] multiple accounts 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 d.t.k's message of Mi Mai 11 12:41:14 +0200 2011: > Excerpts from Patrick Totzke's message of Mi Mai 11 11:41:44 +0200 2011: > > I agree: a single send-sink seems totally unnatural. > > In fact, we have the same problem with drafts. > yeah, actually I can think of some more situations in which I would wish for > account specific sources: I'd love to add a :spam_source (e.g. 'Junk') and a :ham_source (e.g. INBOX) where mails > are moved when the 'spam' label is set/removed, so that operation is mapped onto > folders (I use a server side spamassassin to automagically learn from specified > folders) > > > I recently mentioned both shortcomings on sup-devel > > (http://rubyforge.org/pipermail/sup-devel/2011-May/001095.html). > > As you say: a quick glance at the code confirms that one can only > > specify one send-sink, as well as draft-sink. > > However, there is some sort of "DraftManager" object. I guess one can > > play with that.. > actually, as a dirty hack it shouldn't be too hard to do: message objects know > about their sources. Now we could reference the account a source belongs to in > every source in addition to fields like labels, usual, archived, etc. Et voila. > From the related account we could then get any required sink: draft, sent, spam, > ham, ... uah, what was I thinking? Actually, for the first two cases (draft, sent), it should be /way/ easier. There already /is/ a mechanism for correllating those messages to an account. I think it is acceptable to assume that sent mails as well as drafts have the from: header (which is most probably where the acct correllation hooks in) set (this may not be true for the spam/ham scenario). So since there is a mechanism to get the account to such a mail, all we would need to do is to provide account objects with a :sent_source and a :draft_source of type location. Case solved. Now that's gonna be easy ;) dtk PS depending on the direction this discussion is taking, I wonder whether I should subscribe to and include sup-devel :| _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk