From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sent_source - singular or per-account?
Date: Wed, 01 Jul 2009 23:17:57 -0400 [thread overview]
Message-ID: <1246502666-sup-1295@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <f4cc59760907011930x4678e623j33a777ef03b7da55@mail.gmail.com>
Excerpts from Jim Cheetham's message of Wed Jul 01 22:30:25 -0400 2009:
> On Thu, Jul 2, 2009 at 7:39 AM, Ben Walton<bwalton at artsci.utoronto.ca> wrote:
> > Excerpts from Jim Cheetham's message of Wed Jul 01 05:48:30 -0400 2009:
> >> I'd like to be able to save outgoing email into the mailstore for the
> >> matching account; can anyone suggest some way to do this? Hacking code
> >> is an option, although I'd appreciate some pointers ...
> >
> > This is an interesting idea. ?I think the best way to do it might be
> > to implement a sent_source hook that can override the global default.
>
> 'best' or 'simplest'?
Both?
> There already exists logic for determining which account a given
> outgoing message belongs to, because that's how the :sendmail:
> target is being used.
>
> If you are arguing that having a different sent_source per (outgoing)
> message is useful, then perhaps a hook makes sense; but the simpler
> case probably doesn't need it.
I'm not arguing anything, and perhaps using sent_source as the
(hypothetical) hook name was a bad choice...
If I'm understanding you correctly, you want to write to a different
source depending on which address is used in the From. You'd either
need to make a separate config entry in each account that gets setup
(similar to the sendmail that you note) or provide the ability for the
user to select the sent box in some other way.
In the 'simpler' case where the decision is made based on account
used, you've got a chunk of static code making the choice and
defaulting as it would now. The hook would simply take the place of
the static decision maker. The decision has to be made per message
regardless of how it's implemented, so doing it in a hook is a better
option, imo. The Hook route would be slightly slower, since there are
extra activation records on the stack for the function calls, but it
should be negligible.
The other advantage to a Hook is that the decision could be made based
on more than simply the From:. Maybe other users would prefer to
store mail based on who it was sent To...or a combo of From/To?
I'm interested in William's thoughts on this. It's not a feature I'd
use, but I do think it's a good feature to have.
I hope this explains my thinking more clearly.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090701/eb941c06/attachment.bin>
next prev parent reply other threads:[~2009-07-02 3:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 9:48 Jim Cheetham
2009-07-01 19:39 ` Ben Walton
2009-07-02 2:30 ` Jim Cheetham
2009-07-02 3:17 ` Ben Walton [this message]
2009-07-02 10:14 ` Jim Cheetham
2009-07-02 14:02 ` Ben Walton
2010-01-04 18:55 ` Bryan Richardson
2010-01-05 21:51 ` William Morgan
2010-01-06 19:18 ` Bryan Richardson
2010-01-06 19:29 ` William Morgan
2010-01-06 21:04 ` Tero Tilus
2010-01-06 21:23 ` William Morgan
2010-01-07 15:58 ` Tero Tilus
2010-01-08 16:00 ` Bryan Richardson
2010-01-09 22:47 ` Tero Tilus
2010-01-12 21:38 ` Bryan Richardson
2010-01-12 23:10 ` Tero Tilus
2010-01-04 20:50 ` Tero Tilus
2010-01-08 23:06 ` Kevin Riggle
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=1246502666-sup-1295@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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