You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Ken Keller <kk...@ign.com> on 2002/06/17 23:03:44 UTC

www.boldfish.com mailer

We use www.boldfish.com because it can run directly off your site's
membership schema. When it detects a bounce, it calls a DB trigger which you
can program to mark the user's email address as suspect. When the user
visits your site, you can nag him to provide a valid email addr.

Note that you still need to operate your own SMTP relays unless you have the
$ to pay Boldfish to use its Boldfish Express Network (BEN). We use pizza
boxes running postfix.

Boldfish is not a high-end mailer. Marketers can't use it to define segments
& multi-step mailings.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


how to use template/screen class pairing in a parse situation?

Posted by Bruce Altner <ba...@hq.nasa.gov>.
Greetings:

I've been using the template/screen class pairing method quite extensively 
to populate the context used by a template. However, I've run into a 
situation wherein a master template (Index.vm) #parses many other templates 
and screen class for the parsed templates is not invoked. I could make a 
screen class Index.java but this would result in name collisions among the 
parsed templates. What is the best practice for using screen classes in 
this scenario...fully qualified variables in the context, pull tools, etc?

Thanks,
Bruce


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org