On 1-Apr-2009, at 13:12, Linda Walsh wrote:
I found, BURIED, in the doc "Mail::SpamAssassin::Conf the broken,
primitive rules for white/black list patterns allowed:
Whitelist and blacklist addresses are now file-glob-style
patterns,
so "fri...@somewhere.com", "*...@isp.com", or "*.domain.net"
will all
work. Specifically, "*" and "?" are allowed, but all other
metacharacters are not. Regular expressions are not used
for
security reasons.
This text is pretty much in the default user_prefs file.
# Whitelist and blacklist addresses are now file-glob-style patterns, so
# "fri...@somewhere.com", "*...@isp.com", or "*.domain.net" will all work.
# whitelist_from some...@somewhere.com
"[0-9][0-9a-f]*.domain", "[0-9]*.domain", "[^0-9]*.domain"
[0-9] is a regex. So is [^0-9]. It's just that most shells support
most basic regex.
3) The documentation is ALSO unclear if the expression is a full or
partial
match, as "^ and "$" are also not included.
So unclear if "@domain" is same as "*...@domain".
Yes it is clear. Since @domain is not the same globbing as *...@domain*,
the matches ar enot the same. ^ and $ are part of 'all other
metacharacters' and not supported.
Granted, I think the lack of regex support in whitelist is a really
stupid mistake, but that's me and I'm probably wrong.
--
Advance and attack! Attack and destroy! Destroy and rejoice!
