From: dtk <d.t.k@gmx.de>
To: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] multiple accounts
Date: Wed, 11 May 2011 02:16:03 +0200 [thread overview]
Message-ID: <1305072191-sup-3288@minibox> (raw)
In-Reply-To: <BANLkTin03XSrPG-Ck1ThNd8+1uAsVARL2g@mail.gmail.com>
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 ;)
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-05-11 0:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 20:17 dtk
2011-05-10 21:36 ` Wirt Wolff
2011-05-10 22:52 ` dtk
2011-05-10 23:23 ` Matthieu Rakotojaona
2011-05-11 0:16 ` dtk [this message]
2011-05-11 9:41 ` Patrick Totzke
2011-05-11 10:41 ` d.t.k
2011-05-11 15:08 ` dtk
2011-05-11 12:10 ` Ruthard Baudach
2011-05-11 13:20 ` Patrick Totzke
2011-05-11 13:50 ` dtk
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 6:52 [sup-talk] Multiple accounts Alexander Panek
2007-12-01 11:33 ` Magnus Therning
2007-12-08 22:03 ` William Morgan
2007-05-23 8:49 [sup-talk] multiple accounts Brian
2007-05-28 3:15 ` William Morgan
2007-06-08 23:43 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1305072191-sup-3288@minibox \
--to=d.t.k@gmx.de \
--cc=matthieu.rakotojaona@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox