Hi !!
but acl variables are stored that way in queued messages ?
See the "Format of spool files" chapter.
then maybe it will be better to split them in two lists ...
... which also introduces backwards compatibility problems. Yes, of
course it could be done. It just isn't totally straightforward. Which is
why I want there to be some discussion about the desirability of this
feature.
what about this:
format of -h files:
-acl <number> <length>: A line of this form is present for every ACL
variable that is not empty. The number identifies the variable; the
acl_c*x*$ variables are numbered 0–9 and the acl_m*x*$ variables are
numbered 10–19.
-acl_c <number> <length>: A line of this form is present for every ACL
variable that is not empty. The number identifies the acl_c*x*$ variable
-acl_m <number> <length>: A line of this form is present for every ACL
variable that is not empty. The number identifies the acl_m*x*$ variable
new versions of exim could only write acl_c and acl_m lines and read
acl, acl_m and acl_c , this will allow backwards compatibility without
adding extra problems.
--
Best regards ...
----------------------------------------------------------------
David Saez Padros http://www.ols.es
On-Line Services 2000 S.L. e-mail [EMAIL PROTECTED]
Pintor Vayreda 1 telf +34 902 50 29 75
08184 Palau-Solita i Plegamans movil +34 670 35 27 53
----------------------------------------------------------------
--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details
at http://www.exim.org/ ##
