On Wed, 28 May 2003 22:37:28 GMT, Tim Legant <[EMAIL PROTECTED]> wrote:
> It does somewhat more than that, including processing the X-TMDA > header and X-TMDA in the Subject field, if that feature is turned on > in config. > > It uses both the sender address and the recipient addresses to search > the outgoing filter. It searches once per recipient and sends the > email separately for each recipient, after tagging the sender address > and possibly the address in the Mail-Followup-To field appropriately. > > It adds Date and Message-ID header fields, if they don't exist. If so > configured, it can add the X-TMDA-Fingerprint header field. It adds > any custom headers from ADDED_HEADERS_CLIENT and removes any listed in > PURGED_HEADERS_CLIENT. It adds any custom headers from the matched > rule in the outgoing filter. Dear Tim & Jason Thanks for detailed info. Tim just one clarification - in your comments above are you referring to tmda-sendmail or tmda-inject? If I want to ensure *full* functionality of tmda for users outgoing mail which should I use? What would you both recommend / like to see. I am considering similar scheme to that which I use for incoming mail - an Exim "router" which routes mail to a specifically designed transport. The new router would be first to process mail before Exim's usual outgoing DNS lookup and incoming user delivery routers. As it needs to be the first router (routers are processed in order) it must be quick. Then next question is what conditions I use to determine that the email must be processed by tmda, options are: 1. IP address range (coming from inside network) 2. User (I think this is the most 'precise' as perhaps the user is injecting mail from some outside host to then go out again. Also covers situation where one system may have tmda and non-tmda users. Matching user to local part of sending address should be no problem) 3. Some criteria which can show whether it has *already* been processed by tmda-sendmail/inject and now can go out The router and transport are below - the transport should work as written, for the flag checked in the router to show whether tmda-inject/sendmail has already processed the email what would you recommend/prefer I use. I was thinking the X-Delivery-Agent header? Regards PS ==================================== Router ====== outgoing_tmda: driver = redirect Check sender address local part against some lookup - list/file/etc. Check some tmda flag in email transport = outgoing_tmda_pipe no_more Transport ========= outgoing_tmda_pipe: driver = pipe command = /usr/bin/python2 /usr/bin/tmda-inject **OR** tmda-sendmail user = $sender_address_local_part group = tmda _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
