On Thu, Nov 29, 2012 at 09:16:48AM +, Ben Brown wrote:
Looking at the master branch in git, this file has been replaced by a
directory with several files (proxy.d). The example of filter_username
in proxy.d/filter uses /@.*@/ which as we've discovered on the list is
fine for the purpose
On 28 Nov 2012, at 15:08, alan buxey a.l.m.bu...@lboro.ac.uk wrote:
Hi,
That's not quite the same, as it would match more than the original
regex. OK the parenthesis aren't needed, however consider the following
username:
bob@@realm
that would be a wrong and illegal
hi,
..theres also an error in v2.2 policy.conf
#
# Realm begins with a dot
# e.g. u...@.site.com
#
if (User-Name !~ /@\\./) {
update reply {
Reply-Message+ =
hi,
if(User-Name =~ /@(.+)?@/i ) {
=
Would this not be simpler just by using '/@.*@/' ?
its good to get feedback.
yes, theres no need for case insensitive for this oneand also, we dont care
about feeding the results to a following processso no need
On Wed, Nov 28, 2012 at 01:09:44PM +, John Horne wrote:
#
if(User-Name =~ /@(.+)?@/i ) {
=
Would this not be simpler just by using '/@.*@/' ?
That's not quite the same, as it would match more than the original
regex. OK the parenthesis aren't needed,
Hi,
That's not quite the same, as it would match more than the original
regex. OK the parenthesis aren't needed, however consider the following
username:
bob@@realm
that would be a wrong and illegal entry...so needs to be rejected too.
alan
-
List info/subscribe/unsubscribe? See
On 28 Nov 2012, at 15:08, alan buxey a.l.m.bu...@lboro.ac.uk wrote:
Hi,
That's not quite the same, as it would match more than the original
regex. OK the parenthesis aren't needed, however consider the following
username:
bob@@realm
that would be a wrong and illegal entry...so needs
7 matches
Mail list logo
