> So maybe try it without them
Well, I'll be darned! It worked!
I actually thought that both of the approaches
I used should have worked. From your message
it sounds like you were only surprised that
it didn't work when I had the entire in-line
ACL on a single physical line which was
enclosed within double quotes and any
newlines were represented by \n. IOW, I take
it that you were not surprised that my having
real newline characters within the in-line ACL
didn't work even though the entire in-line ACL
was enclosed within double quotes. I would have
thought the double quotes would have allowed me
to embed real newline characters. If you'd care
to pass along why that doesn't work, I'd love to
hear it.
In any event, thanks a batch for the input.
It's working now!
... doug
--- Fred Viles <fv+exim@???> wrote:
> On 9 Sep 2004 at 12:53, Doug Jolley wrote about
> "[exim] New lines in an in-line ACL":
>
> |...
> | My next thought was to keep the whole
> | in-line ACL within double quotes and also
> keep it
> | on a single physical line
>
> According to 6.12, "String Values", quoted
> strings can still use line
> continuation.
>
> | with the newline being
> | represented by a \n. That didn't work either.
>
> Not sure why, seems like it should have. But
> the acl option value is
> expanded, so you didn't need the enclosing
> quotes to get \n processed
> (per section 11.2, "Character escape sequences
> in expanded strings").
> So maybe try it without them, e.g.:
>
> acl_smtp_rcpt = verb condition1\n\tcondition2
>
> - Fred
>
>
>
>
>
> --
> ## List details at
> http://www.exim.org/mailman/listinfo/exim-users
> Exim details at http://www.exim.org/ ##
>
_______________________________
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.
http://shopping.yahoo.com/backtoschool
