As mentioned earlier you can require email verification from as little or as many people depending on their ISP using the email verification system intergrated Dawns banning system.
The mud will send out an email with a random 6 hexidecimal digit verification code to the email address provided by the user when logging in/creating. At the end of creation/login they provide the verification code, after providing the correct code for their character they are allowed into the game. The mud records that they have correctly authenticated and no longer asks them for the verification code for each subsequent login.
To setup email verification create a permban of type email... see 'help permban'.
[prompt>help permban
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
edit[96 - wizicom.txt]ALLOW PERMBAN SHOWBAN
Syntax: allow <sitemask>
banedit <#>
permban <sitemask> <all|email|newbie|permit>
permban
showban <#>
PERMBAN <sitemask> prohibits players from that site from logging in. There
are various types of banning: all, email, newbie, permit. All will not
allow anyone from that sitemask to log on. Email will allow certain allowed
emails to create new characters (see help BANEDIT for more info). Newbie
will ban all newbie creation from the site. Permit will allow certain
characters with a permit flag set to log on from the site. Letgained
players automatically have the permit flag, but non-letgained characters
will have to have it manually entered into their pfile. See help SITEMASK
and help BAN-EXAMPLE for more information regarding setting up the permban.
PERMBAN with no arguments lists all of the banned sites. Each ban will have
a unique index numer next to it. Use this number for showban and banedit.
ALLOW <sitemask> removes a site from the ban list, but only if the level of
the ban is not above the level of the remover.
SHOWBAN will display the details of the ban without going into the edit
mode.
BANEDIT allows you to edit the details about the ban.
>>>SEE ALSO: BANEDIT, SITEMASK, BAN-EXAMPLE
[PREV][NEXT]-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
|
Once you have created a permban of type email edit it using banedit - e.g. banedit 0. You can change the sitemask (see help sitemask) in banedit if you didn't get it right when creating it with permban.
If you want to require email verification from everyone, you would just set the sitemask to '*' without the quotes.
Help checkban gives a good example of an email ban requiring verification from users of aol.com, msn.com and uunet.com. I have quoted it below:
[prompt>help checkban
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[command:immortal]edit[96 - immhelp.txt]CHECKBAN BAN-EMAIL-EXAMPLE EMAIL-VERIFICATION
Syntax: checkban <ip/host address of player as shown in sockets/laston>
The checkban command is used to show you which if any of the ban matching
rules will match for a particular host.
For example if you had a ban forcing email verification for all players
coming from aol.com. If you typed checkban AC9HCFA4.ipt.aol.com you would
expect to see something like the following:
-===========================================================================--
==- CHECK BAN ON: 'AC9HCFA4.ipt.aol.com'
- Newbies: allowed
- Permit/Letgained check: allowed
- Email check: denied
Ban #1
-========================== BANEDIT SHOW ==========================-
Sitemask: '*aol.com
*msn.com
*uunet.com
'
IntendedPeople: Email Verification System
Enabled: True
Permanent: True
Type: email
ban created on: Sat May 25 12:05:00 2002
by: Kalahn
Reason: To require email verification for users from particular ISPs.
Custom disconnect message: none
Expire date: none
always_allowed_email_masks:
exception1@hotmail.com
goodplayer@hotmail.com
anothergoodplayer@hotmail.com
friend@yahoomail.com
allowed_email_masks:
*@aol.com
*@msn.com
*@uunet.com
disallowed_email_masks:
badperson@aol.com
idiot@msn.com
note: disallowed_email_masks have a higher priority than allowed masks, if
a particular email addy matches the disallowed email mask, it will be denied
even if it matches the allowed mask also. The only exception to this is if
the email address is on the always_allowed_email_masks list for this ban...
note the always allowed only applies to this particular ban... if the host
and email match a disallowed on another ban, it will be declined.
disallowed_email_masks_message:
Access to this site has been denied! Please contact the MUD Administration
for inquiries on why access is denied.
- All: allowed
-===========================================================================--
>>>SEE ALSO: CHECKCOMMANDS
[PREV][NEXT]-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[prompt>
|
Feel free to ask further questions if things aren't clear after your testing.
- Kal