Linda A. Walsh wrote:
> Matt Kettler wrote:
> Actually, I know sed/[e]grep/bash{2,3} et al. RE's, just need to know
> which syntax is supported, i.e. old "sh", bash2 compatible, bash3
> (w/iterators),
> sed compat RE's, grep (w/POSIX support), egrep (w/alternation)...etc.
FWIW, perl regexes are based on, and compatible with posix extended regular
expressions.
However, perl regexes are only used when creating rules in spamassassin. They
are not used in whitelists.
You
> say "fileglob" format, is that as in "sh" or "ash", or "bash3.x"? I'm
> still not real clear from the docs (sorry) ...?
file globbing is the format that sh/bash and MS dos use for file name
expansions.
ie: *.txt matches joe.txt, whatever.txt but not bluetxt.
To quote the Mail::SpamAssassin::Conf manpage:
-----------------------------
Whitelist and blacklist addresses are now file-glob-style patterns, so
[EMAIL PROTECTED], [EMAIL PROTECTED], or *.domain.net will all work.
Specifically, *
and ? are allowed, but all other metacharacters are not. Regular expressions are
not used for security reasons.
Multiple addresses per line, separated by spaces, is OK. Multiple
whitelist_allows_relays lines is also OK.
The specified email address does not have to match exactly the address
previously used in a whitelist_from_rcvd line as it is compared to the address
in the header.
e.g.
whitelist_allows_relays [EMAIL PROTECTED] [EMAIL PROTECTED]
whitelist_allows_relays [EMAIL PROTECTED]
