"David U." <[EMAIL PROTECTED]> writes: > I'll take a look at it. I would guess there are two ways of > handling it. > > 1) exec'ing an outside program or script on the message before it > goes out
This method seems slightly less reliable. e.g, would the outside script be able to properly sign a MIME/Multipart message? > 2) building gpg support into tmda-inject with something like: > http://py-gnupg.sourceforge.net/ (GnuPGInterface Python module) I'd be more in favour of this, since it seems cleaner, and would be easy to add an `application/pgp-signature' (or whatever MIME content-type is appropriate for GnuPG sigs) part to the outgoing message. The tmda-inject in CVS has the machinery to do this fairly easily. > It looks like the python module is a pretty complete wrapper for > gpg. I wasn't aware of this module, but this will certainly make things easier. > I'll look at some python code this week and see if I can grok the > gpg module and then see where we are. Sounds good. BTW, further discussions on developmental issues of this sort should take place on tmda-workers. > Most likely though, this will be too difficult for me to tackle > without some more time with the language. Don't sweat it. Unless you urgently need this feature, I'll get around to it sooner or later. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
