On Fri, Apr 21, 2006 at 04:16:53PM +0000, Mark Horn wrote: > First thing: I've done TMDA development before. If I create a patch > for the functionality that I want, who is accepting updates? Jason?
I'm not sure who has maintainer access these days. You could distribute the patch on tmda-workers, but I don't know who (if anyone) has commit access to the source anymore. > So, maybe the way to handle this is with a variable like > XTMDA_ENV_SENDER which works similarly to BOUNCE_ENV_SENDER. It may be > time to dust off my python skills. I think there are probably plenty of useful reasons to improve the flexibility of X-TMDA headers. I know a few other people have mentioned that they wish they could use X-TMDA to take different actions for different recipients through the X-TMDA interface, so this seems like a similar challenge. As for what you're doing, I'm not arguing with you, but I guess I still don't see the benefit of having the envelope sender and the from header be different. What does that buy you? -- Re-Interpreting Historic Miracles with SED #141: %s/water/wine/g _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
