 |  |
> > No, that's not quite what I'm saying. I don't want to allow
Re: Duplicate Logins and emails
From: john@relia.net
Date: Tuesday, December 10, 2002
Time: 12:40:08 pm
> the user
> > to have an email that matches their LOGIN, because all our scripts,
> > statements, etc "create" a mail account for the LOGIN already. So
> > OPTI should not allow "john" to be added to the services screen of
> > "john"'s account, that would be redundant.
>
> Well, I understand what you are saying, but from a purely
> design standpoint, don't you think it would be better to have
> a different server event for RADIUS and a different one for
> email instead of them being one and the same? Maybe I'm not
> understanding something (which very well could be the case),
> but since I'm a nerdy programmer guy, I tend to rationalize
> things in an object-oriented way.
>
> It sounds to me like you have it setup like this currently:
>
> 1 dialup in Optigold = 1 dialup + 1 email on your servers
> 1 email in Optigold = 1 email (maybe 1 dialup also?) on your servers
>
> Is there a reason that I don't under stand that it's not
> simplified to be:
>
> 1 dialup in Optigold = 1 dialup on your servers
> 1 email in Optigold = 1 email on your servers
>
> - Shawn
I've given this a lot of thought lately, and your question is really my best
answer.
Everything is entered into a CENTRALIZED mySQL database from Opti. One
account table stores all necessary information. When we create a new user,
it's given a certain account code (lets say = 10 for a standard account).
When a new emailbox gets added, it's account code = 20 (thus has no radius
priveleges, etc). Each type of radius account will have a different code
(i.e. ISDN Dual channel might = 30 for simultaneous logins, email only might
= 40, etc). Right now, when an email box is added into OPTI that matches an
already existing login, it replaces the account name that was a dialup to an
email account, so we don't want to allow a user to create an email box that
is identical to their login...it's not needed, redundant.
So on our system, we only want ADDITIONAL email's to be in the email
services screen, since all logins already have email with them. Otherwise,
if a user deletes his email box, he's really deleting his main account from
the table.
1 dialup in OPTI = 1 account in the table gets authorized for radius and
mail
1 email in OPTI = 1 account in the table gets authorized for email (no
radius)
You already have an option in OPTI to "create matching emails", why not have
an option that "does not allow matching emails" to be created, it shouldn't
be too difficult I hope.
Otherwise,
1 dialup in OPTI = 1 account in the table
1 email in OPTI = the same account in the table
1 email address removed in OPTI = 1 email and dialup account removed from
system = 1 unhappy customer
Hope that makes more sense.
John
---------------------------------------------------
To subscribe, unsubscribe or to search list archive
please visit http://www.optigold.com/lists/isp.html
---------------------------------------------------
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696