(RADIATOR) Re: your mail

[Enrique Vadillo]

Hi Rafael,

I don't know if this is what you are asking for (your question looked quite
cumbersome to me :) but here you are:

|o| What I need is a way to define a handler that would take the place of the
|o| domain-less Realm without using the Handler default (since I'd probably
|o| use it with gric).

if you wanna match "someuser" with no domain, you can use:

Handler User-Name=/^.*/

at the end of your config file, you can maybe use (i don't use it):

Handler default

but i'd rather not use that for gric, i'd rather use:

Handler User-Name=/^..*@..*/

that would match any "someuser@somedomain" format

Regards,

Enrique-

|o|  Rafael Ortega escribió 
|o| Hello, everyone
|o| 
|o| I'm not very proficient in Perl, but need has made me look into regular
|o| expressions to solve a configuration problem I have with Radiator (currently
|o| using 2.15, but about to upgrade to 2.16, as soon as the new servers
|o| arrive).
|o| 
|o| We recently merged with another ISP and inherited their database and
|o| domains.  We also support GRIC and IPASS romaing services.
|o| 
|o| My problem is, for roaming services, we are going to use prefixes and that
|o| means handlers (if I'm not mistaken).
|o| 
|o| Currently, I use realms for our local domains, defining Realm for our
|o| domain with the most users.  Realm default I use for Ipass.  No provisions
|o| have been made for Gric, yet.
|o| 
|o| I came up with the following handler definitions to replace my realms:
|o| 
|o| Handler User-Name=/domain.com$/i  would replace Realm domain.com
|o| 
|o| Handler User-Name=/^IPASS\//i  would do for the prefixes.
|o| 
|o| 
|o| What I need is a way to define a handler that would take the place of the
|o| domain-less Realm without using the Handler default (since I'd probably
|o| use it with gric).
|o| 
|o| Thanks for your help.
|o| 
|o| 
|o| 
|o| Rafael Ortega
|o| PSINetworks Panama
|o| [EMAIL PROTECTED]
|o| +507 206-3078
|o| 
|o| 
|o| 
|o| ===
|o| Archive at http://www.starport.net/~radiator/
|o| Announcements on [EMAIL PROTECTED]
|o| To unsubscribe, email '[EMAIL PROTECTED]' with
|o| 'unsubscribe radiator' in the body of the message.


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Re: (RADIATOR) Re: your mail

[Phil Freed]

 interesting.  Do you all feel its a good idea to "lowercase and chop" all
 usernames like this, and just let the user have "[EMAIL PROTECTED]" incorrectly
 in their dial up config, or do you think its better to correct for it?
 
 I think the RewriteUsername would cut down alot of tech support calls, and
 really its harmless so long as its only their dialup config that is
 braindead and not their mail config etc.
 
 I think it's not a good idea.
 Remeber that the password will not be touched, so if your customer forgot to
 turn off caps lock, the authentication will fail anyway, and support calls
 will happen.

FWIW, we like to automatically LC() the realm.  Enough of our 
users think that their e-mail address ought to be upper case - or 
lower case - or proper case - that we decided it was simpler to 
accept them all.  Especially since our name has odd capitalization 
anyway  (cyberTours. Yup - sure looks funny at the beginnig of a 
sentence.)
Phil Freed [EMAIL PROTECTED]

===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Re: (RADIATOR) Re: your mail

[Ricardo Freire]

interesting.  Do you all feel its a good idea to "lowercase and chop" all
usernames like this, and just let the user have "[EMAIL PROTECTED]" incorrectly
in their dial up config, or do you think its better to correct for it?

I think the RewriteUsername would cut down alot of tech support calls, and
really its harmless so long as its only their dialup config that is
braindead and not their mail config etc.

I think it's not a good idea.
Remeber that the password will not be touched, so if your customer forgot to
turn off caps lock, the authentication will fail anyway, and support calls
will happen.

Cheers,
Ricardo Freire


===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.