Hi all,

At this point Turbine is pretty focussed on getting it's configuration from
a TR.props.  For instance, what mail host to use is dependent on what is set
as smtp.host.

I am finding this requires lots of funky build scripts, because my smtp.host
is different in development from production.  And, regular admin types can't
easily edit tr.props files.

Therefore we are switching to using JNDI for as many of our settings that
change as possible.  I would like to change the VelocityEmail to take in a
jndi javax.mail.session to use instead.  This would require a change to the
tr.props as well to specify mail.session=jndi/props or something of that
nature?

What do you all think?  Towards this end, I submitted a patch to
commons-email (
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16859) a couple weeks ago
to allow it to take a javax.mail.Session as well as a mailHost.  However
that patch hasn't been dealt with.

If this sounds like a good enhancement, then if someone who is also a
committer on commons could apply my patch, I'll make the changes to tr.props
to make the mail host a properties or jndi setting.

sincerely,
Eric Pugh

Reply via email to