> This should be nearly the first router (for me it comes after system
> aliases, and an "eximfilter" router I use to sort out mailing
> lists before they reach tmda)
>
> # This router catches all local deliveries *before* forward and local mail
> # routers and sends to TMDA. Once messages is released by TMDA it is
> # added to users maildir directory by TMDA/Exim.
>
> tmdaprocess:
> driver = accept
> check_local_user
> no_verify
> no_expn
> local_part_suffix = -*
> local_part_suffix_optional
> transport = tmda_pipe
> condition = ${if exists{$home/.tmda/config} {yes} {no} }
>
>
> and later in the file in the transports section.
>
>
> # This is the command pipe transport for TMDA used instead of address pipe
> # transport
>
> tmda_pipe:
> driver = pipe
> command = /usr/local/bin/python /usr/local/bin/tmda-filter
> return_path_add
> delivery_date_add
> envelope_to_add
> user = $local_part
> group = mail
> environment = EXTENSION=${substr_1:$local_part_suffix}:\
> [EMAIL PROTECTED]
If this all worked I guess it should go in the FAQ. But I can't
see how it can work. We want tmda DELIVERY to just return as in
qmail and have exim look at other exim routers below tmdaprocess
when tmda doesn't want to impede the progress of the message.
However for this to work tmdaprocess's driver (accept) would
have to return PASS based on the status of the tmda-filter.
I don't think it ever does that. The proposal is OK if tmda
does its own final delivery. However that means messages to users
with a ~/.tmda/config are never subject to .forward or aliases.
Of course we can put tmdaprocess last, but then you lose tmda when
you forward your mail elsewhere. Can we improve the condition to
see whether the mail has already been through tmda?
Or maybe I missing something?
Bob
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
