!==
!== v3_proto.conf.txt for IServerd snapshot 23 Apr 2001
!==
Contributor:	Dmitry A. Panov <redfox@mail.khstu.ru>
Date:		04 November 2000
Updated:	23 April 2001 Alexandr V. Shutko <AVShutko@mail.khstu.ru>

Subject:	IServerd config file (for V3 proto module)
============================================================================

# This option disable or enable V3 proto module. If you disable 
# this proto, V3 clients will get a message box with "Proto V3 disabled"
V3 proto enabled	= 	Yes

# Maximum number of tries to retransmit packet if it lost.
# Server will try to retransmit packet specified times 
# and then delete it from confirm queue
V3 max retries		= 	3

# Timeout between retransmit packets. If packet is lost 
# server wait specified time and then resend expired packet 
V3 max timeout		=	2

# Time between keep-alive client packets. This (55) is
# standart value and you should remeber that if you decrease 
# this - clone clients will not work - they often don't extract
# ping time from login reply packet
V3 ping time		=	55

# Maximum records for search result. V3 protocol haven't 
# internal limit in search so user can request search by name 
# that doesn't contain 'sWERWW@#1' and he possibly receive 
# information about all server users. This search can easily 
# overload slow network (~300Kb/100 found users).
V3 max search		=	100

# Maximum message size (protocol top limit = 2025 bytes).
# After this limit every message will fragment. Groupware 
# win clients from Mirabilis don't like big packets and 
# immediately disconnecting from server, sending such packets
V3 max msgsize		=	2025

# Maximum fragment size (protocol top limit = 600 bytes). 
# Fragmented packets used when large messages or system packets are 
# transmited
V3 packet mtu		=	500

# Enable V3 clients registration. (ICQ->User(UIN)->Login with new uin)
# I plan to add Web registration option in main configuration file
# so you can disable this and enable only web registration with your
# own rules
V3 registration enabled =	Yes

# If enabled, user will receive his autogenerated UIN and password on
# request registration new account. Important: if you set this = yes
# you should also change V3 post-register info option, in another case 
# client will not see his new uin and password
V3 auto registration    =	No

# This text shows to client before registration new account.
# There are russian and english examples in etc/texts directory
V3 admin notes		=	etc/texts/adm_notes.txt

# This text shows to client after registration new account.
# If You have enabled [V3 auto registration], You MUST change this
# to [post_reg_auto.txt] (you should view this text to understand why). 
# In another case user can't get his new UIN and password after 
# registration. (See post_reg_auto.txt for information)
V3 post-register info	=	etc/texts/post_reg_man.txt