Tim Legant <[EMAIL PROTECTED]> writes: > I seem to recall (and I could be completely in error) that we added > the various BOUNCE_TEXT_* variables as a "solution" to this problem, > but those don't address the full issue, as you are pointing out.
In retrospect, I think using variable interpolation for the text of the bounce message was a bad idea, even if it does save on the number of templates. For one, it makes things very hard to multi-lingualize, as you have to store both translations in a .tmda/config Python variable, and it isn't entirely clear that will even work with certain character sets. It's also proved to be very non-intuitive. This is something I'll be changing in TMDA post 1.0. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
