Hiya! I agree: a single send-sink seems totally unnatural. In fact, we have the same problem with drafts. Has anyone of you managed to store drafts anywhere else than in ~/.sup/drafts ? let alone in different locations for different accounts? 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.. 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. cheers' /p Excerpts from dtk's message of Wed May 11 01:16:03 +0100 2011: > Excerpts from Matthieu Rakotojaona's message of Mi Mai 11 01:23:02 +0200 2011: > > I know that when you send an email from Google smtp, you don't have to save > > it anywhere. It will automagically be saved with a GMail/Send tag (most of > > the time 'Send' only'). You don't configure your GMail account to save > > anything in msmtp; it happens on Google side. > > Isn't there a way to do so with msmtp ? I know you can choose an account to > > send from, but after a quick looking you can't choose a folder where to save > > the sent email. Maybe you'd have to choose another MTA to save the sending > > mail ? Simple relays like msmtp or nbsmtp (in the example) can't save in a > > specific folder. > hmm, actually I don't think it's usually an smtp feature but rather an IMAP one? > > > sup is just like mutt, an MUA, and HAPPENS to be able to > > save your sent mail to a specific folder. But I think it's not the main > > purpose of it, or am I wrong ? > well, as an MUA I feel it is its task to manage mails, and that certainly > includes accessing my mailbox. Admittedly stressing the comparison, speaking > proper maildir e.g. means moving mails from new/ to cur/, so I feel like copying > sent mails into a destined directory sounds rather appropriate, as does deleting > mails, etc... > > Besides, sup /does/ it, so why not do it properly? Making the sent source > account dependent feels natural to me. And I don't see why I would need a more > complex MTA for that (which according to my understanding is responsible for > transferring mails between systems rather than shuffling around mails locally). > > ready to be educated > dtk ;)
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk