------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1062 Phil Pennock <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|Exim 4.74 |Exim 4.75 Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #7 from Phil Pennock <[email protected]> 2011-02-06 09:25:51 --- I objected in #1. So far, the only use case proposed is an actively dangerous one for which a safe viable alternative was proposed but never implemented by the administrator in question, who instead just repeatedly pushed for us to make a dangerous change. Unless and until I see a use-case clearly presented for raising the limit where the use-case is not dangerous and there is no alternative, we should not implement this raise. If a real use-case is found, then it's a deficiency in the existing facilities. We should then look at what's needed. It is possible that what is needed is an "acl" expansion condition which can be used in a ${forall...} loop. To prove this, someone who thinks they need the limit raised should explain their scenario on exim-users and ask for help finding a configuration, in the normal way. If a solution is proposed which works, we go with that. If not, we look into acl-as-expansion-condition. Since Exim's not a general-purpose scripting language, we don't need to provide multiple ways to achieve the same thing. As it is, the count stands at: * one maintainer strongly opposed * one maintainer tentatively supporting, if no other maintainer opposes Closing this bug wontfix. -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
