>David Grimberg <[EMAIL PROTECTED]> writes on tmda-user: > >> I read over that multiple action thread that you refered to below[1] >> and I was thinking that to avoid the "Is this an action or a >> delivery destination" conundrum that shows up in a rule like: >> >> To [EMAIL PROTECTED] deliver=~/Mailbox.bounces, |pager-program, bound > >(I assume you meant ``bounce'' instead of ``bound''?) > >How about just requiring that each action item must be explicitly >typed? The above line would become: > >to [EMAIL PROTECTED] deliver=~/Mailbox.bounces, >deliver=|pager-program, bounce
Yep I meant bounce instead of bound, and as far as explicitly typing each action, I don't have any problems with that. I was just trying to offer a solution to the question of how to determine weather or not everything after the equals sign were multiple destinations, or other commands. It seemed to be an issue in the thread and I hadn't seen my suggestion of bracketing the destinations (if more than one existed) offered as a way to disambiguate the intent. The bracketing option would definitely allow for less verbose and potentially easier to read rules, but it shouldn't preclude the explicitly typed option at all. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
