From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs221387vdc; Wed, 11 May 2011 03:47:59 -0700 (PDT) Received: by 10.52.74.234 with SMTP id x10mr2401305vdv.140.1305110879432; Wed, 11 May 2011 03:47:59 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id cj13si17871vdb.115.2011.05.11.03.47.58; Wed, 11 May 2011 03:47:58 -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 20F901858376; Wed, 11 May 2011 06:47:58 -0400 (EDT) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by rubyforge.org (Postfix) with SMTP id EE07F185836B for ; Wed, 11 May 2011 06:41:17 -0400 (EDT) Received: (qmail invoked by alias); 11 May 2011 10:41:16 -0000 Received: from hmbg-4d06d0fe.pool.mediaWays.net (EHLO localhost) [77.6.208.254] by mail.gmx.net (mp061) with SMTP; 11 May 2011 12:41:16 +0200 X-Authenticated: #67991182 X-Provags-ID: V01U2FsdGVkX1/1pWVpG1v1+dX2Ap1s35oFduPVf9jTHgK7Gk/g5o iY9vdnF3eclKeX From: d.t.k To: Patrick Totzke In-reply-to: <1305105912-sup-2960@brick> References: <1305058093-sup-1016@minibox> <1305063169-sup-9131@chigamba> <1305067227-sup-4227@minibox> <1305072191-sup-3288@minibox> <1305105912-sup-2960@brick> Date: Wed, 11 May 2011 12:41:14 +0200 Message-Id: <1305109172-sup-2288@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 Hi, 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, ... I don't think it's too beautiful if sources know what account they belong to. I feel like it should rather be the other way around (an acct knows its srcs). Specifying the sources of an account in the config.yaml might seriously clutter that file up, though, especially for users with many imap folder. So we could either reference a file containing the sources for an account in config.yaml (per account) or name the file by some convention (sources_.yaml) and have it parsed automagically (convention over configuration?). Thinking about it, if we could correlate mails and accounts (via the source) we might just store the belonging account in a message field. > Anyhow, my current solution is to use a local mbox as send-sink > and use a bcc to myself. Then I use server-side filters to > mark incoming mails from myself as read and move it to sent. > offlineimap then syncs the sent folder, which is then included in > sources.yaml with archived:true and autoadd label:sent. > > The problem with this is, that despite different sup's on different > hosts both can read the send mails wich are stored on the correct > servers, the sup-instance that was used to compose the mail actually > displays its local version and somehow skips the one from the server. > BUT: I cannot prevent my mailhost from adding another signature to the > mail and therefore, the mail sup stores is different from the one I > sent! To conclude: different send-sinks for different accounts are > the sensible solution in my view. I agree. Your solution may provide a work around for now, but it feels rather hacky. I'd prefer having account specific sources handled properly (as I have other applications in mind, see above) as much as I imagine you would. dtk _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk