I agree with you for the most part - and normally wouldn't route in a filter - except that in this case there are a few problems:
1. I need to attach the expansion of the $recipients variable to capture BCC's, and it is not available via routers - *only* ACL's and the system filter
2. It might be the case (but I doubt it) that the headers added by headers_add are allowed to be longer than those added by filters. But if they aren't (and I can get around problem #1) then I am right back to trying to add a too long header.
Now, if envelope_to_add will include the BCC information I might be able to get around this. I'll run a quick test now to see.
-David
> On Tue, 2003-06-03 at 15:34, David Powers wrote:
> > The system filter being used is:
> >
> > if first_delivery then
> > headers add "X-Foo-Mail-From: $sender_address\nX-Foo-Mail-To: $recipients"
> > unseen save "/home/willcap/mailusers/audit/"
> > endif
>
> Its obviously the week for this. Don't do routing in filters.
>
> How about this as the first router
>
> # NB This router is illegal in many situations
> # check your local legislation
> copy_router:
> driver = accept
> # accept absolutely anything - no domains/local_parts here
> no_expn
> transport = copy_transport
> unseen
> no_verify
>
> and then something like this transport:-
>
> copy_transport:
> # only save one message no matter how many recips
> # ?? is zero legal - if not put 1000000 there or something
> batch_max = 0
> driver = appendfile
> # save in dated directory
> directory = /some/file/path/$tod_logfile/
> create_directory
> # set perms and stuff
> user = fred
> # add extra audit data
> delivery_date_add
> envelope_to_add
> return_path_add
>
>
> All untested, but should do pretty much the right thing...
>
> Nigel.
> --
> [ Nigel Metheringham Nigel.Metheringham@??? ]
> [ - Comments in this message are my own and not ITO opinion/policy - ]
>
>
>
