[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[sequence]
	22
	0
	0
	0
	19
	8
	Numbered list
	0
	Bullet
	0
	Indnt bullet
	0
	Indnt caution
	0
	Indnt tip
	0
	Indnt note
	0
	Caution
	0
	Tip
	0
	Note
	0
	Browse
	0
	Keyword
	0
	Context
	0
	Title
	0
	Macros
	0
	Alink
	0
	Window
	0
	Win95 macros
	0
	Win31 macros
	0
	Build tag
[prn]
	PostScript (QMS)
[port]
	LPT2:
[lang]
	1
[fldnames]
	Field1
	Field2
	Field3
	Field4
	Field5
	Field6
	Field7
	Field8
[desc]
	mail routing 
	
	
	
	
	801530499
	55
	769967163
	8300
	73
	0
	0
	0
	0
	
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
	
	
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Ahead
	3
	[fnt]
		Arial
		220
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		240
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		2160
		3
		0
		1
		1
		1
		65
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		79
		0
		3
		100
	[brk]
		80
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Bhead
	6
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		180
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	7
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		300
		300
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		<*:>.
		0
		3
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	1st lev para
	9
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Bullet
	11
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		120
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Bullet
	2
	1
	160
	1
	400
	0
[tag]
	Indnt bullet
	12
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		420
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		16
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	2nd lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		600
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	See also prnt
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Book art
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Book art
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Callout text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Callout text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Figure title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		60
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Arial
		280
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		300
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Chapter title
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Right pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Right pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Left pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Left pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Table title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		60
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		4
	[line]
		10
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table Text
	0
	0
[tag]
	See also hlp
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		40
		4
		180
		0
		3
		100
	[brk]
		96
	[line]
		9
		0
		3
		0
		1
		1
		1
		70
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	0
	120
[tag]
	See also btn
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		240
	[spc]
		24
		200
		4
		0
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Crossref
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		513
		3
		0
		300
		600
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Indnt caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		324
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt tip
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Indnt note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		300
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Dhead
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Parameter
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Parameter
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Formula
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		+
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Browse
	0
	0
[tag]
	Keyword
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		K
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Keyword
	0
	0
[tag]
	Context
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		#
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Context
	0
	0
[tag]
	Title
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		$
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Title
	0
	0
[tag]
	Macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		!
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Macros
	0
	0
[tag]
	Footnote
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		244
		0
	[spc]
		40
		2400
		3
		0
		0
		1
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		256
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[tag]
	Alink
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		A
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Alink
	0
	0
[tag]
	Butnbar
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		0
		0
		3
		100
	[brk]
		48
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Butnbar
	0
	0
[tag]
	Window
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		>
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Window
	0
	0
[tag]
	Win95 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		W
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win95 macros
	0
	0
[tag]
	Win31 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		X
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win31 macros
	0
	0
[tag]
	Build tag
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		*
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Build tag
	0
	0
[frm]
	22
	1572932
	957
	2614
	9428
	6585
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	26
	0
	16
	12779 53771
	[frmlay]
		4350
		8471
		3
		0
		0
		3
		2614
		0
		0
		2
		0
		49
		13
		2314
		1
		1497
		9625
		0
	[tbl]
		 13 2 200 86 4133 86 1 43 43
		[h]
			 0 210 86 2 0 2 0
			 1 200 86 2 0 2 0
			 2 200 86 2 0 2 0
			 3 400 86 2 0 2 0
			 4 200 86 2 0 2 0
			 5 200 86 2 0 2 0
			 6 200 86 2 0 2 0
			 7 200 86 2 0 2 0
			 8 200 86 2 0 2 0
			 9 200 86 2 0 2 0
			 10 200 86 2 0 2 0
			 11 200 86 2 0 2 0
			 12 200 86 2 0 2 0
		[e]
		[w]
			 0 1961 86 2 0
			 1 6295 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
@Table col hd@Server commands

>
			 0 1 0 0 0 0 0 1 0 0 0 0
@Table col hd@Description or purpose

>
			 1 0 0 0 0 0 0 1 0 0 0 0
HELP 

>
			 1 1 0 0 0 0 0 1 0 0 0 0
Provides additional online information on commands. 

>
			 2 0 0 0 0 0 0 1 0 0 0 0
ROUTE servername

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Sends all mail messages to the specified server, regardless of priority. 

>
			 3 0 0 0 0 0 0 1 0 0 0 0
SET CONFIG "DOMAIN = domainname"

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Sets the domain for users on new servers that cannot receive mail from other servers.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
SHOW CONFIG DOMAIN

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Shows the domain, if specified.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
LINK

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Links users' mail databases with the MAILOBJ.NSF.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
UNLINK

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Unlinks users' mail databases with the MAILOBJ.NSF.

>
			 7 0 0 0 0 0 0 1 0 0 0 0
COLLECT

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Checks if the non-summary data in the object store is linked to summary data. 

>
			 8 0 0 0 0 0 0 1 0 0 0 0
SET

>
			 8 1 0 0 0 0 0 1 0 0 0 0
Specifies per-database options.

>
			 9 0 0 0 0 0 0 1 0 0 0 0
RESET

>
			 9 1 0 0 0 0 0 1 0 0 0 0
Can undo any SET command.

>
			 10 0 0 0 0 0 0 1 0 0 0 0
INFO

>
			 10 1 0 0 0 0 0 1 0 0 0 0
Displays statistics and information on database usage and object stores.

>
			 11 0 0 0 0 0 0 1 0 0 0 0
SHOW PORTS

>
			 11 1 0 0 0 0 0 1 0 0 0 0
Shows the status of LAN and COM ports

>
			 12 0 0 0 0 0 0 1 0 0 0 0
SHOW TASKS

>
			 12 1 0 0 0 0 0 1 0 0 0 0
Dead letters and pending mail are shown. 

>
		[e]
	[tble]
[frm]
	21
	1572932
	957
	2433
	9428
	4774
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	27
	1
	0
	9220 15361
	[frmlay]
		3314
		8471
		3
		0
		0
		3
		2433
		0
		0
		2
		0
		108
		102
		23924
		1
		1497
		9625
		0
	[tbl]
		 8 2 200 86 4133 86 1 43 43
		[h]
			 0 210 86 2 0 2 0
			 1 200 86 2 0 2 0
			 2 200 86 2 0 2 0
			 3 200 86 2 0 2 0
			 4 200 86 2 0 2 0
			 5 200 86 2 0 2 0
			 6 200 86 2 0 2 0
			 7 200 86 2 0 2 0
		[e]
		[w]
			 0 2208 86 2 0
			 1 6048 86 2 0
		[e]
		[data]
			 0 0 0 0 0 0 0 1 0 0 0 0
@Table col hd@NOTES.INI variable 

>
			 0 1 0 0 0 0 0 1 0 0 0 0
@Table col hd@Description

>
			 1 0 0 0 0 0 0 1 0 0 0 0
MailEncryptIncoming

>
			 1 1 0 0 0 0 0 1 0 0 0 0
On the server, encrypts all incoming mail messages.  

>
			 2 0 0 0 0 0 0 1 0 0 0 0
SecureMail=1

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Indicates the time allowed to route a mail message. The default is 24 hours.  

>
			 3 0 0 0 0 0 0 1 0 0 0 0
MailTimeoutMinutes=n

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Indicates the time allowed to route a mail message. 

>
			 4 0 0 0 0 0 0 1 0 0 0 0
MailMaxThreads

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Provides the number of threads needed to route mail.

>
			 5 0 0 0 0 0 0 1 0 0 0 0
MinNewMailPoll

>
			 5 1 0 0 0 0 0 1 0 0 0 0
Provides the minimum number of times that you can poll for mail.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
NoMailMenu

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Disables and suppresses the mail menu. 

>
			 7 0 0 0 0 0 0 1 0 0 0 0
MailLow Priority 

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Routes low priority mail during specified time.

>
		[e]
	[tble]
[frm]
	45
	1572868
	957
	1435
	9433
	10938
	0
	3
	1
	1 0 0 0 0 0 0
	0
	16777215
	24
	2
	0
	20224 14080
	[frmlay]
		3340
		8476
		3
		0
		0
		3
		1435
		0
		0
		2
		0
		0
		0
		65280
		1
		1380
		9626
		0
	[tbl]
		 14 4 200 86 2026 86 1 43 43
		[h]
			 0 610 20 6 0 1 0
			 1 800 0 6 0 1 0
			 2 400 86 2 0 1 0
			 3 800 86 2 0 1 0
			 4 1400 86 34 0 1 0
			 5 1000 86 2 0 1 0
			 6 2200 86 2 0 1 0
			 7 800 86 2 0 2 0
			 8 600 86 2 0 1 0
			 9 600 86 2 0 2 0
			 10 600 86 2 0 1 0
			 11 400 86 2 0 1 0
			 12 600 86 2 0 1 0
			 13 400 86 2 0 1 0
		[e]
		[w]
			 0 1390 0 6 0
			 1 3099 0 6 0
			 2 1390 0 6 0
			 3 2554 0 6 0
		[e]
		[data]
			 0 0 0 0 0 0 512 1 0 0 0 0
@Table col hd@<:I0,0,0,0>Notes mail command

>
			 0 1 0 0 0 0 512 1 0 0 0 0
@Table col hd@Notes action

>
			 0 2 0 0 0 0 512 1 0 0 0 0
@Table col hd@cc:Mail or VIM</m>compliant mail command

>
			 0 3 0 0 0 0 512 1 0 0 0 0
@Table col hd@Action

>
			 1 0 0 0 0 0 512 1 0 0 0 0
Double-click mail icon

>
			 1 1 0 0 0 0 512 1 0 0 0 0
Opens mail file on server. Can also use File - Open.

>
			 1 2 0 0 0 0 512 1 0 0 0 0
Open - Open

>
			 1 3 0 0 0 0 512 1 0 0 0 0
Activates the other mail application, using the path and file name specified in Mail Setup.

>
			 2 0 0 0 0 0 0 1 0 0 0 0
Create - Memo

>
			 2 1 0 0 0 0 0 1 0 0 0 0
Displays a list of forms from which to compose a new mail message

>
			 2 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 3 0 0 0 0 0 0 1 0 0 0 0
Address (on mail form)

>
			 3 1 0 0 0 0 0 1 0 0 0 0
Allows user to select recipient names from a Notes Address Book

>
			 3 2 0 0 0 0 0 1 0 0 0 0
Not available - Compose

>
			 3 3 0 0 0 0 0 1 0 0 0 0
Recipient names can be added/edited through the application's Simple Messaging Interface dialog box.

>
			 4 0 0 0 0 0 0 1 0 0 0 0
Forward (on mail form)

>
			 4 1 0 0 0 0 0 1 0 0 0 0
Copies Notes document into a mail memo for mailing

>
			 4 2 0 0 0 0 0 1 0 0 0 0
Forward - Address

>
			 4 3 0 0 0 0 0 1 0 0 0 0
Puts the current or selected Notes documents into the body of a mail memo and displays the mail application's SMI dialog box; use to mail documents that don't have Send to:, cc:, and bcc: entries.

>
			 5 2 0 0 0 0 0 1 0 0 0 0
Forward as attachment

>
			 5 3 0 0 0 0 0 1 0 0 0 0
Attaches the document to a mail message. The user has the choice of providing additional information in the addressing area.

>
			 6 0 0 0 0 0 0 1 0 0 0 0
Send (on mail form)

>
			 6 1 0 0 0 0 0 1 0 0 0 0
Sends mail message to recipient(s)

>
			 6 2 0 0 0 0 0 1 0 0 0 0
Send - Not available

>
			 6 3 0 0 0 0 0 1 0 0 0 0
Converts the current or selected Notes documents to text or attaches them as a Notes database. Recipient and subject names come from the To:, cc:, bcc:, and Subject: entries in the Notes document. Recipients must have Notes to read the attachment. Use to ma
il documents that have Send to:, cc:, and bcc: entries.

>
			 7 0 0 0 0 0 0 1 0 0 0 0
Send User ID

>
			 7 1 0 0 0 0 0 1 0 0 0 0
Displays options related to security that can be done through Notes mail, such as requesting a certificate or sending encryption keys

>
			 7 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 7 3 0 0 0 0 0 1 0 0 0 0
To send encryption keys, users can use the Import/Export functions (see Notes Help for details).

>
			 8 0 0 0 0 0 0 1 0 0 0 0
Create - Memo

>
			 8 1 0 0 0 0 0 1 0 0 0 0
Opens a memo form for a mail message. Can also use Create - Mail - Memo. 

>
			 8 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 8 3 0 0 0 0 0 1 0 0 0 0
Not available

>
			 9 0 0 0 0 0 0 1 0 0 0 0
Create - Other - Memo to Manager

>
			 9 1 0 0 0 0 0 1 0 0 0 0
Opens a memo to manager form for a mail message. Can also use Create - Mail - Memo to Manager. 

>
			 9 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 9 3 0 0 0 0 0 1 0 0 0 0
Not available

>
			 10 0 0 0 0 0 0 1 0 0 0 0
Create - Mail - Phone Message 

>
			 10 1 0 0 0 0 0 1 0 0 0 0
Opens a phone message form for mail message. Can also use Create - Phone Message. 

>
			 10 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 10 3 0 0 0 0 0 1 0 0 0 0
Not available

>
			 11 0 0 0 0 0 0 1 0 0 0 0
File - Mail - Reply

>
			 11 1 0 0 0 0 0 1 0 0 0 0
Opens a memo form for mail message. Can also use Create - Reply.

>
			 11 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 11 3 0 0 0 0 0 1 0 0 0 0
Not available

>
			 12 0 0 0 0 0 0 1 0 0 0 0
Create Reply with history

>
			 12 1 0 0 0 0 0 1 0 0 0 0
Opens a memo form for mail message. Can also use Create - Mail - Reply with history. 

>
			 12 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 12 3 0 0 0 0 0 1 0 0 0 0
Not available

>
			 13 0 0 0 0 0 0 1 0 0 0 0
Create - Mail - Custom Forms 

>
			 13 1 0 0 0 0 0 1 0 0 0 0
Opens a custom form you created.

>
			 13 2 0 0 0 0 0 1 0 0 0 0
Not available

>
			 13 3 0 0 0 0 0 1 0 0 0 0
Not available

>
		[e]
	[tble]
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		0
		1
		0
		1
		0
		2
		1
		960
		9446
		1
		1
		3120
	[lft]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		0
		1
		0
		1
		0
		2
		1
		720
		9206
		1
		1
		3120
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		2
		4674
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		2
		4674
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		3
		9900
	[txt]
>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		12960
		10166
		1
		960
		480
		3
		11940
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		3
		9900
	[txt]
>
[elay]
[lay]
	1
	7
	[rght]
		12971
		10181
		1
		957
		957
		3
		1435
		736
		0
		1
		1
		1
		0
		2
		1
		957
		9445
		0
	[lft]
		12971
		10181
		1
		957
		957
		3
		1435
		736
		0
		1
		1
		1
		0
		2
		1
		957
		9445
		0
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10181
		1435
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		21
	[frmlay]
		1435
		10181
		1
		957
		180
		3
		0
		736
		0
		1
		0
		1
		1
		0
		1
		957
		9445
		0
	[txt]
Setting Up and Managing Mail

>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10181
		1435
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		18
	[frmlay]
		1435
		10181
		1
		957
		180
		3
		0
		736
		0
		1
		0
		1
		1
		0
		1
		957
		9445
		0
	[txt]
<:S+194>

>
	[flft]
	[lyfrm]
		1
		5056
		0
		12014
		10181
		12971
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		22
	[frmlay]
		12971
		10181
		1
		957
		480
		3
		12014
		736
		0
		1
		0
		1
		1
		0
		1
		957
		9445
		0
	[txt]
@Left pg foot@<:R1,1,3,8069,><:P19999,0,4->  Administrator's Guide 	Lotus Confidential

>
	[frght]
	[lyfrm]
		1
		13248
		0
		12014
		10181
		12971
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		20
	[frmlay]
		12971
		10181
		1
		900
		480
		3
		12014
		793
		0
		1
		0
		1
		1
		0
		1
		900
		9388
		0
	[txt]
@Right pg foot@<:R1,1,3,8488,>Lotus Confidential	Administrator's Guide  <:P19999,0,4->

>
[elay]
[l1]
	1
[pg]
	73
	7 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	18 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	27 0 5 516 1 0 0 220 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	49 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	56 0 5 516 1 0 0 240 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	74 0 5 516 1 0 0 240 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	83 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	95 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	101 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	106 0 67 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	114 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	122 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	127 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	134 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	145 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	151 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	159 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	164 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	170 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	178 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	184 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	189 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	191 330 69 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	201 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	204 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	208 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	223 0 7 516 1 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	230 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	244 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	259 99 19 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	275 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	282 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	294 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	301 101 37 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	307 0 5 516 1 0 0 240 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	329 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	348 0 87 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	373 0 5 516 1 0 0 220 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	379 0 5 516 1 0 0 220 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	389 90 107 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	395 0 43 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	403 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	412 0 10 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	420 0 101 516 0 0 0 40 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	429 0 5 516 1 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	436 97 11 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	444 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	450 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	455 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	463 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	473 0 7 516 1 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	487 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	501 423 37 4 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	510 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	516 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	533 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	538 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	548 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	556 0 7 516 0 0 0 40 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	574 0 6 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	583 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	588 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 4 0 0
	589 318 100 4 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	595 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	601 0 14 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	615 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	630 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	642 102 47 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	646 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	660 0 5 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	685 0 24 516 0 0 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	723 0 27 4 0 1 0 200 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
	738 0 2 1029 1 0 0 220 65535 1	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 0 0 0 0 0
[edoc]
@Chapter title@<:s>Chapter 4 Setting Up and Managing Mail 

<:s>This chapter explains how to set up mail for Notes users, connect servers, and schedule mail delivery.  It also discusses mail routing between Notes and non-Notes mail servers, mail routing costs, and mail encryption.   

@See also prnt@<:s>

@See also hlp@<:s>

xref Chapter 3 / chapter 10, 


<:p<* >>

@Ahead@<:s>About Notes mail

<:s>Notes uses electronic mail to share information between Notes users. Mail messages are stored in Notes mail databases and provide a way to store incoming and outgoing mail messages for each user.  

<:s>Notes mail is comprised of four components: a mailer, a router, a names service, and gateways. The Mailer handles the Notes menu commands, the Router checks and delivers new messages as well as transfers or routes mail to their destinations, the Names servi
ce provides the address and location of mail files in the Public Name & Address book, and gateways provide a way to communicate with non-Notes mail systems. 

<:s>Notes mail, for all its complexity, is simple to use and to administer. As an administrator, your tasks are creating and maintaining mail databases for users in each Notes domain and setting up connections between the servers, domains, and gateways that wan
t to communicate with each other. 

You can set up mail storage as a separate mail database, or use a combination of a separate mail database and a shared, common database. The shared database uses the single copy object store (SCOS) feature. 

<:s>

@See also prnt@<:s>See the Deployment Guide for additional information.    

@See also hlp@<:s>

<:s>About Notes mail databases, About single copy object store


<:p<* >>

@Bhead title@<:s>About Notes mail databases

<:s>When you register Notes users, you assign a home server and a mail file location for your mail database. A home server is where a user's mail file is stored. Then, user ID files and mail databases are created for every user. Mail databases typically contain
 copies of your memos and drafts as well as other memos you saved and categorized. 

Mail databases are usually located in the mail subdirectory on the server. Typically, user mail databases use the first initial of your first name and your entire last name. For example, Salvador Diaz can find his mail file in the mail subdirectory: \MAIL\S
DIAZ. 

<:s>For example, if Salvador sent a memo to 15 other Notes users, you may find 15 copies of the same memo stored in 15 different mail database files on the same or multiple servers. To avoid this waste of system resources, you can now combine individual mail da
tabases with single copy object store (SCOS) features. 

<:s>

@See also hlp@<:s>

<:s>xref Deployment Guide for size, server types


@Bhead title@<:p<* >>Setting up individual mail databases on a server

@Numbered list@<:s><:R1,4,1,0,1,720,1,1440,1,2160,>Double-click the Notes workstation icon on the Notes desktop. 

@Numbered list@<:s><:R>Select File - Tools - Notes Administration.

@Numbered list@<:s>Select the server you want.

@Numbered list@<:s>Click Users - Users View.

@Numbered list@<:s>Be sure that there are user documents for all the users you want to register. 

@Numbered list@<:s>Click Window - Administration.

@Numbered list@<:s>Click Users - Register User.

@Numbered list@<:s>Click Yes if you possess the necessary user licenses.

@Numbered list@<:s>Enter the administrator password and click OK.

@Numbered list@<:s>Click Continue if the registration server is correct, otherwise, select the appropriate server and ID.

@Numbered list@<:s>Enter the user name, password, and other appropriate data, 

@Numbered list@<:s>Click Mail to make sure that you indicate the home server for each user. 

@Numbered list@<:s>Click Other to select the location of the ID file, assign the delegation authority, and add organization unit, location, and comments.  

@Numbered list@<:s>Click Next to register more users and repeat steps 10 through 13. 

@Numbered list@<:s>Click Register when you're finished. 

@Numbered list@<:s>Enter the administrator password and click OK. 

@Numbered list@<:s>Click OK after Notes creates each user ID file and mail file.

@Bhead title@<:s>

@See also hlp@<:s>

route mail; About schedules for mail routing, scheduling server-to-server routing, setting up immediate routing


<:p<* >>

@Bhead title@About shared mail  

Shared mail allows users to store common messages in a single location. The Single copy object store (SCOS) technology is used to store these mail messages in a central database. Users can then open the shared copy of the message. Each user can edit, save, 
and resend the original message, although the edited message is stored as a separate message. 

Typically, most mail messages have more than one recipient and each recipient receives and stores the same message in their mail database. With shared mail, a single mail message is stored once in the object store, which frees system resources. 

When you use separate mail databases for each user, the same message can be stored in many mail databases and system memory resources are used at much greater cost/rate. Since shared mail allows multiple users to access the same message at the same time, us
ers are not adversely affected by this storage method. Users can delete, reply, change the view or folder, and perform all the same tasks with a mail message stored in an object store as the same message stored in an individual mail database.  

The default object store database is referred to on each server as MAILOBJ.NSF. Administrators usually rename this database when they make back up copies as well as when they replicate it. This database may get grow quickly so you must create new linked ver
sion of this database so users can continue to access their shared messages. Users can add this database to their Notes desktop along with their individual mail database, but they cannot open it.    

<:s>

@Ahead@<:s><:p<* >>

@Bhead title@<:s>Setting up and enabling object store on a server

@Numbered list@<:s>Be sure that individual mail databases are created for each user.

@Numbered list@<:s>Double-click the Notes workstation icon on your desktop.

@Numbered list@<:s>Click File - Tools - Notes Administration.

@Numbered list@<:s>Select the server you want.

@Numbered list@<:s>Click Servers - Configure Servers.  

@Numbered list@<:s>Click Set new parameter. 

@Numbered list@Select R<++>outerUsesObjectStore<-+>. 

@Numbered list@<:s>Enter 1 as the value and click OK. 

@Numbered list@<:s>Double-click Console. 

@Numbered list@Enter LOAD OBJECT LINK <<mail\usermail.nsf<;>  MAILOBJ.NSF

@Numbered list@<:s>Enter LOAD OBJECT COLLECT.

@Numbered list@<:s>Click Done.

@Numbered list@<:s>Close Notes Administration window.

<:s>

@See also hlp@<:s>

<:s>route mail; About schedules for mail routing, scheduling server-to-server routing, setting up immediate routing

@Ahead@<:p<* >>

@Ahead@About using single copy object store (SCOS)

Single copy object store (SCOS) is a space-saving feature that lets you store single copies of mail messages in a special-purpose object store database (MAILOBJ.NSF) where all recipients share them. After you enable SCOS on a server, when the router on the 
server receives a mail message addressed to two or more people, it separates the message header text from the content and sends the header text to each recipients mail database and the content to MAILOBJ.NSF. Thus, the part of a shared message consuming the
 most space (the content) is not duplicated but instead stored as a single copy in MAILOBJ.NSF.

Links created between the message content and the header text let users read shared memos stored in the object store database as though it were in their local mail databases.

If a user edits the content of a shared memo, Notes copies the edited content to the user's mail databases and removes its pointer to MAILOBJ.NSF. 

If a user deletes a shared memo, Notes deletes only the header text in the user mail database; the content remains in MAILOBJ.NSF. If all users delete header text for a shared memo, the Collect server program, which runs daily at 2:00 AM, deletes the obsole
te memo content from MAILOBJ.NSF.

You enable SCOS by creating a server configuration document in the Name & Address Book or by editing NOTES.INI.<-"> When you enable SCOS, Notes automatically creates the object store database MAILOBJ.NSF. If MAILOBJ.NSF becomes large, you can rename it and 
create a new one; users continue to have access to the original object store as well as the new MAILOBJ.NSF.

All mail messages can be shared in an object store except messages received by users who choose the "Encrypt saved mail" option.<-!><-">


<:p<* >>

@Bhead title@Enabling shared mail 

@Numbered list@Choose File - Tools - Notes Administration.

@Numbered list@Type the name of the server on which to enable SCOS.

@Numbered list@Click the Servers icon and choose Configure Servers.

@Numbered list@Click Set new parameter. <-!><-">

@Numbered list@Select ROUTERUSESOBJECTSTORE.

@Numbered list@Enter 1 as the value and click OK.

You can now link to MAILOBJ.NSF any mail databases that were in place before you enabled SCOS.

@See also prnt@For information, see "Linking and unlinking mail databases."

@See also prnt@You can also enable SCOS by using the SET CONFIG command or by editing NOTES.INI directly.

@See also prnt@
@See also prnt@<:p<* >>

@Bhead title@<+@><:I0,0,0,0>About deleting obsolete documents from an object store or linked mail databases

<+@><:I0,0,0,0>When users delete header documents from their mail databases, the links to the corresponding content documents in object store databases are broken. To keep the size of object store databases to a minimum, the server program Collect deletes any content docu
ments in them that no longer have associated header documents (because all users have deleted the header documents from their mail databases).

<+@><:I0,0,0,0>The Collect server program runs by default each morning at 2:00 A.M on all object store databases on a server.

<+@><:I0,0,0,0>You can also run the Collect server program manually at the server console. The Collect server program run manually provides additional options. For example, if there are multiple object store databases on a server, you can run Collect on one rather than al
l of them. <-!>Or, you can purge any header documents in a mail database that link to a corrupted object store. You can then restore the header documents from backup or from a replica of the mail database, if one exists. 

<+@><:I0,0,0,0>

<+@><:I0,0,0,0><:p<* >>

@Bhead title@<-!>Running the Collect server program

It's important that the Collect server program runs each day so that the size of MAILOBJ.NSF is kept to a minimum. By default, Collect runs on MAILOBJ.NSF each morning at 2:00 AM. 
<-!><-"><+!><+"> <-"><-!>Notes administrators can change this default time by editing NOTES.INI and adding "ObjectCollect" 
<+!><+">CORRECT NAME?<-"><-!> to the desired "ServerTasksAt" time.<-!><-">

<-!>You can also run Collect manually from the server console as follows:

@Mono@LOAD OBJECT COLLECT -FORCE <<DATABASE<;>

Using the -FORCE switch or typing a database name is optional.<:p<* >>

<-!><+!>Details: Running the Collect server program <-!><+!><<DATABASE<;>

You can specify one database or a directory of databases. The specified database(s) can be a mail database or an object store database. If the database is an object store, content documents that do not link to header text in mail databases are purged to sav
e disk space.  

If the database is a mail database, header documents that do not link to content documents are purged. A header document may not link to a content document if the content document becomes corrupted and is then purged by FIXUP or if the links become corruopt
ed.

If you omit a database name, Collect runs on all object store databases on a server.<-!><-"><-!><-">

<+!>-FORCE

With this switch Collect purges all documents that link to inaccessible databases as well as all documents that link to inaccessible documents. This switch is primarily useful for purging documents from an object store database that link to deleted mail dat
abases. Without -FORCE, Collect does not purge documents linked to inaccessible databases. 

Use this switch carefully since it purges all documents with links to inaccessible databases, even databases that are only temporarily inaccessible due to a hardware problem. As an alternative to using the -FORCE switch, you can keep empty replicas of obsol
ete mail databases rather than deleting them. By doing this, content documents in the object store database associated with these obsolete databases can be deleted while content documents associated with other mail databases that are only temporarily inacce
ssible remain intact.<-!><-">

<:p<* >>

<+@><:I0,0,0,0><+!>Examples: Running the Collect server program<-!>

@Mono@LOAD OBJECT COLLECT

Runs on all object store databases on the server <-!><-">and purges content documents that link to inaccessible header documents in user mail databases. Does not purge documents linked to inaccessible mail databases.

@Mono@LOAD OBJECT COLLECT <<JBROWN.NSF<;>

Purges any header documents in JBROWN.NSF that link to inaccessible content documents in an object store. A content document may be inaccessible if it is corrupted. 

@Mono@LOAD OBJECT COLLECT -FORCE MAILOBJ.NSF<-!><-">

Purges any documents in MAILOBJ.NSF linked to inaccessible mail databases and any document linked to inaccessible header documents in mail databases. 

<:p<* >>

@Bhead title@<+!>About creating a new copy of <-!><+!>MAILOBJ.NSF<-!>

Occasionally you should check the size of MAILOBJ.NSF and if it is large consider<-!><-"><-"> creating a new copy. You may never or only rarely have to do this since the Collect server program limits its growth. When you create a new MAILOBJ.NSF, you must r
etain the original copy so that users continue to have access to content documents in it. 

Creating a new MAILOBJ.NSF allows you to generate "virtual" mail databases, allowing users to access more information than a single database allows. Since many users share mail in MAILOBJ.NSF, by preventing the database from becoming too large you also mini
mize mail disruption in the event the database becomes corrupted. 

Creating a new copy of MAILOBJ.NSF involves temporarily disabling object store, renaming MAILOBJ.NSF, and then enabling object store again to automatically create a new MAILOBJ.NSF. This change is transparent to users; once a new MAILOBJ.NSF is in place, us
ers with mail databases on the server can access new messages in MAILOBJ.NSF while retaining access to older messages in the original, renamed object store database. All object store databases must be located in or be linked to the Notes server data directo
ry for links to header documents in mail databases on the server to remain intact.

<:p<* >>

@Bhead title@Creating a new copy of MAILOBJ.NSF

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,>Disable SCOS. 

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,>Make sure MAILOBJ.NSF is closed. To ensure that it is closed, execute the DROP ALL server command. This command drops all active server sessions and closes all databases.

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,>Rename MAILOBJ.NSF.

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,>Enable SCOS again to create a new MAILOBJ.NSF.<-!><-">

@Numbered list@<:R1,4,1,0,1,720,1,1440,1,2160,>Link mail databases again to account for mail messages routed when SCOS was disabled.

<:R1,4,1,0,1,720,1,1440,1,2160,><:p<* >>

@Ahead@<+@><:I0,0,0,0><:R>About linking and unlinking mail databases<-!><-">

<+@><:I0,0,0,0>The LINK command lets you link mail databases to object store databases.<-!><-">

<+@><:I0,0,0,0>Use the LINK command in the following situations:

@Chead@To link messages received prior to using SCOS

Notes automatically creates links for messages received after you enable SCOS. You must create these links manually for mail received before SCOS was enabled.<-!><-">

@Chead@To link mail databases added since SCOS was enabled

If you add a new mail database to a server that uses SCOS, you must use the LINK command to link it to the object store.

@Chead@To link mail received when SCOS is temporarily disabled

If you temporarily disable SCOS, for example to recreate MAILOBJ.NSF,<-!><-"><+!><+"> 
<-!><-">mail messages routed to the server while SCOS is disabled are not linked to an object store database. After you enable SCOS again, you should link mail databases again. 

The UNLINK command lets you unlink mail databases currently linked to an object store or unlink an object store currently linked to mail databases.

<:p<* >>

@Bhead@<+@><:I0,0,0,0><+!>Example<-!><+!>s: linking<-!><+!> mail databases<-!>

@Mono@<+@><:I0,0,0,0>LOAD OBJECT LINK JBROWN.NSF MAILOBJ.NSF

<+@><:I0,0,0,0>Links any unlinked documents in JBROWN.NSF to MAILOBJ.NSF.

@Mono@<+@><:I0,0,0,0>LOAD OBJECT LINK -RELINK \SALES OBJECT1.NSF

<+@><:I0,0,0,0>Links all documents in the directory SALES, both linked and unlinked, to OBJECT1.NSF.<-!><-">

<+@><:I0,0,0,0><:p<* >>

@Bhead title@Linking mail databases

<-!><-">To link a mail database to an object store database, execute the following server command:

@Mono@<+@><:I0,0,0,0>LOAD OBJECT LINK -RELINK -NOCOMPACT <<DB.NSF<;> <<OBJECT.NSF<;><-!><-">

<<DB.NSF<;>(Required) The name of a mail database you want to link.<+!><+"> 
<-"><-!>To link all the databases in a directory, type the directory path. You can link the contents of only one directory at a time.

<<OBJECT.NSF<;>(Required) The name of the object store to link to, usually MAILOBJ.NSF.

-RELINK (Optional) Links all documents in the mail database(s), even those with existing links. Useful if multiple object stores exist and you want to link all documents to one of them.

- NOCOMPACT (Optional) If more than five mail messages are linked in a database, by default Notes compacts the database. Use -NOCOMPACT to prevent this.

<:p<* >>

@Bhead title@Unlinking mail databases

To unlink all documents in one or more mail databases, type the following server command:

@Mono@LOAD OBJECT UNLINK <<DB.NSF<;><-!><-">

<<DB.NSF<;><+!> <-!>(Required) The name of a mail database you want to unlink.<-!><-"><+!><+"> 
<-"><-!>To unlink all the databases in a directory, type the directory path. You can unlink the contents of only one directory at a time.

<:p<* >>

@Bhead title@Unlinking an object store

<:I0,0,0,0><:R1,1,1,720,><-!><-">If you have disabled SCOS and want to unlink all documents linked to a specific object store database, type the following server command:

@Mono@<:I0,0,0,0><:R1,1,1,720,>LOAD OBJECT UNLINK <<OBJECT.NSF<;>

<:I0,0,0,0><:R1,1,1,720,>If you unlink an object store, Notes moves all the contents document previously stored in the object store to individual mail databases.<-!><-">

<+@><:I0,0,0,0><:R1,1,1,720,><<OBJECT.NSF<;> (Required). <-"><-!>The name of the object store you want to unlink, for example, MAILOBJ.NSF.

<+@><:I0,0,0,0><:R1,1,1,720,><:p<* >>

@Bhead title@<:I0,0,0,0><:R1,1,1,720,>Excluding and including a mail database from object store

<:I0,0,0,0><:R1,1,1,720,><-!><-">You can exclude specific mail databases from using object store by typing the following command:

@Mono@<:I0,0,0,0><:R1,1,1,720,>LOAD OBJECT SET -NEVER <<DB.NSF<;><-!><-">

<:I0,0,0,0><:R1,1,1,720,><<DB.NSF<;><+!> <-!>(Required) The name of a mail database you want to exclude from object store.<+!><+"> 
<-"><-!>To exclude all the databases in a directory, type the directory path. You can exclude the contents of only one directory at a time.<-!><-">

<+@><:I0,0,0,0><:R>If you previously excluded a mail database from the object store, type the following command to include the mail database again:

@Mono@<+@><:I0,0,0,0>LOAD OBJECT RESET -NEVER <<DB.NSF<;><-!><-">

<:I0,0,0,0><:R1,1,1,720,><<DB.NSF<;> The name of a mail database you want to enable again for object store. To enable all the databases in a directory, type the directory path. You can enable the contents of only one directory at a time.<-!><-">

<:I0,0,0,0><:R1,1,1,720,><:p<* >>

@Ahead@<+@><:I0,0,0,0><:R1,1,1,720,><+!>Determining if a database uses SCOS<-!>

<+@><:I0,0,0,0><:R1,1,1,720,>To determine if a database uses SCOS: 

@Mono@<+@><:I0,0,0,0><:R1,1,1,720,>LOAD OBJECT INFO <<DB.NSF<;>

<:R1,1,1,720,>Console output indicates whether a database is an object store, is linked to an object store, or neither.

<+@><:I0,0,0,0><:R1,1,1,720,><<DB.NSF<;> (Required) The name of a database or a directory of databases. You can specify only one directory at a time

<+@><:I0,0,0,0><:R1,1,1,720,><:p<* >>

@Bhead title@<+@><:I0,0,0,0><:R1,1,1,720,><+!>Displaying statistics <-!><+!>about an object store database<-!>

<+@><:I0,0,0,0><:R1,1,1,720,>You can display statistics about the extent of file sharing in MAILOBJ.NSF. The statistics appear in the Object Store Statistics view of Stats & Events Report (STATREP.NSF) if the Report server program is running on the server. To do this, type the followin
g command at the server console:

@Mono@<+@><:I0,0,0,0><:R1,1,1,720,>LOAD OBJECT INFO -FULL MAILOBJ.NSF

@See also prnt@<+@><:I0,0,0,0><:R1,1,1,720,>For more information, see Chapter 9.<-!><-"><-">

@See also prnt@<+@><:I0,0,0,0><:R1,1,1,720,><:p<* >>

@Ahead@<:R1,1,1,720,>About disabling SCOS

<:R1,1,1,720,>You can disable SCOS if you no longer want to use this feature. After doing this, you may want to unlink mail files previously linked to an object store. If you unlink mail files, you may also want to delete the object store to reclaim disk space. Prior to 
deleting the object store, however, run the Collect server program on it to make sure there are no longer links to its content documents.<:p<* >>

@Bhead title@<:R1,1,1,720,>Disabling shared mail 

@Numbered list@<:R1,1,1,720,>Choose File - Tools - Notes Administration.

@Numbered list@<:R>Type the name of the server on which to enable SCOS.

@Numbered list@Click the Servers icon and choose Configure Servers.

@Numbered list@Click Set new parameter. <-!><-">

@Numbered list@Select ROUTERUSESOBJECTSTORE.

@Numbered list@Enter 0 as the value and click OK.

@See also prnt@You can also disable SCOS by using the SET CONFIG command or by editing NOTES.INI directly.

@See also prnt@
@See also prnt@<:p<* >>

@Ahead@About backing up databases that use SCOS

If you've enabled SCOS to link mail databases to an object store, make sure to regularly backup the object store as well as the mail databases. If there is no backup of an object store, then any corrupted content documents in it are not recoverable and can'
t be accessed by users.

<:p<* >>

@Ahead@About copying, moving, or replicating linked mail databases

If you want to move, copy, or make a replica of a mail database that is linked to an object store, make sure to do so through Notes rather than through the operating system. Moving, copying, or replicating through Notes rebuilds each document so that it con
tains both header and content information; this doesn't occur when you copy through the operating system, resulting in copies that contain only header text and not the content information.


<:p<* >>

@Ahead@<:s>About mail routing basics

<:s>When your Notes system contains a number of servers, you must understand how Notes routes mail between users. Notes uses the Mail Router program to transfer mail from one user to another. The Mail Router runs on all Notes servers. The Mail Router gets its i
nformation from two databases located on the server. The Mailbox database (MAIL.BOX) receives incoming mail from workstations and from another server's Mail Router. The Public Name & Address Book (PNAB) contains server, connection, and domain documents that
 provide information about the structure of the Notes networks and domains at your company.

<:s>Since you route mail based on this Notes network and domain map, you must understand the difference between a Notes network and a Notes domain. Although, a Notes network can be a single network or multiple networks, connected by routers and bridges, they al
l share the same Network name, which is located in the server documents in the PNAB. Notes assumes that servers with the same network name can communicate directly with each other. Notes domains are a collection of Notes servers and users that share the sam
e PNAB.

<:s>The home server, which contains the user's mail database, is the final destination of mail messages. Routing mail passes a document from hop to hop along a series of servers until the Mail Router finds one whose PNAB contains an entry for the recipient.

@Bhead@<:s>Routing mail in the same domain

<:s>To understand the basics of mail routing, consider what happens in the case of mail routing between two users in the same domain. When a user mails a document, the Notes workstation looks for the recipient's mail address in the PNAB. The workstation program
 appends the address to the document. Then the Mail Router examines the document to find the location of the recipient's mail file, which is located on the recipient's home server. Based on the location of the recipient's home address, the Mail Router does 
one of the following:

@Bullet@<:s>If the recipient's mail file is on the same server as the sender's mail file, the Mail Router moves the document into the recipient's mail file.

@Bullet@<:s>If the recipient's mail file is on another server that is connected via a network connection document in the PNAB to the sender's server, the Mail Router establishes a connection with the destination server based on connection schedules, and transfers the d
ocument to the Mail Router mailbox on that server. 

@Bullet@<:s>If there is more than one possible route to the destination server, the Mail Router computes the least-cost route from the source server to the destination server. 

@Bhead@<:s>How mail routing occurs automatically

<:s>Mail routing occurs automatically during scheduled replication. If you establish pairs of connection documents for all of the pairs of servers in your Notes system, you do not need to schedule mail routing separately. All you need to do is identify mail rou
ting as a task on each connection document, and let the replication schedule handle the rest of the work. For example, if you want to route mail between servers A and B, make sure that you have a connection document that has server A call server B for repli
cation and another connection document that has server B call server A for replication. You can then minimize the number of connection documents and prevent unnecessary traffic between servers.

<:s>You do need to specify mail routing via a connection document when you want to route mail outside the current domain whether to another Notes or a non-Notes mail system. 

@See also hlp@<:s><+!>

<:s><+!>

<:s><+!><:p<* >>

@Bhead title@<:s><+!>About mail routing and server documents

<:s>Since server documents define the information about a Notes server, you must create a server document for every server in a Notes domain. The server document contains information on server and domain names, server and pass-through restrictions, server tasks
, and enabled port names and addresses. 

<:s>You can specify users and groups that can or cannot access this server or create databases in this server to provide additional control of servers. 

@Note@<:s>Do not create server documents for non-Notes servers or Notes servers in other domains.  

To enable mail routing, you must specify Mail Routing in the Tasks field. The information in the server document is used by the Router to create the network map and routing tables. Then the Router can determine the least cost route as well as how to bypass 
unavailable servers when it routes messages. 

<:s>

<:s><:p<* >>

@Chead title@<:s>Completing a server document for routing

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Select the server that contains the Name & Address you want to edit.

@Numbered list@<:s>Click the Servers - View Servers. 

@Numbered list@<:s>Double-click the Server document you want to edit.

@Numbered list@<:s>Be sure the names in the Server and the Domain fields are correct.  

@Numbered list@<:s>Specify Mail Routing in the Routing Tasks field.

@Numbered list@<:s>Locate and expand the Server Restrictions section. 

@Numbered list@<:s>Specify the users and servers in the Access server, Not access server, Create new databases, and Create replica databases fields. 

@Numbered list@<:s>Expand the Pass-through Restrictions section, if needed. 

@Numbered list@Specify the users and servers in the Access server, Route through, Cause calling, and destination allowed fields.

@Numbered list@<:s>Save and close the server document. 

<:s><:p<* >>

@Bhead title@<:s>About mail routing and connection documents

<:s>Since connection documents define the connections to servers, whether they are in the same or different domains, or Notes or non-Notes servers, you must create connection documents to route mail between servers. 

@Tip@<:s>The only exception are servers in the same Notes network; they can communicate directly without a Connection document. Notes immediately routes mail that is addressed to a user in the same network. 

<:s>You must be familiar with the network and server configuration of any server you want to connect with. You must specify the correct connection type for each server to communicate. You can specify the type of connection that exists between the servers, such 
as local network, modem, pass-through, or Remote LAN Service. 

<:s>Connection documents contain fields that you use to schedule mail routing<:X8,-32768;Index "mail routing" # "connection documents">. To set up mail routing, you create pairs of connection documents that allow each server in the connection to call the other 
server. 

<:s>To establish mail routing between domains, you need two connection documents for each connection. For example, to set up mail routing between servers A and B, you need one connection document that describes how A calls B and you need another connection docu
ment that describes how B calls A.

<:s>You must complete the Scheduling Calling section for each Connection document to enable mail routing.

@Note@<:s>See the appropriate documentation on X.400, SMTP, and X.25 to configure these connections. 

@Chead@<:s>Mail routing without a schedule

<:s>Mail routing occurs automatically during scheduled replication. If you establish replication schedules for all of the pairs of servers in your Notes system, you do not need to schedule mail routing separately. All you need to do is identify mail routing as 
a task on each connection document, and let the replication schedule handle the rest of the work. This is a smart way to minimize the number of connection documents and prevent unnecessary traffic between servers.

@Chead@<:s>The "route at once" limit

<:s>The connection document contains a field that allows you to automatically force a connection when a specified number of mail messages to a single destination server are pending delivery in the MAIL.BOX. To do this, you enter a value in the Route at once fie
ld of the connection document. For example, if you enter 5 in the field, the fifth mail message to the same server forces a mail connection. If fewer than five messages are waiting, mail is transferred according to the schedule. 

<:s>This setting applies only to normal-priority mail because high-priority mail forces an immediate call and low-priority mail is handled according to different criteria.

@See also hlp@<:s>

<:s><+!><[><-!><+!>About connection documents, About replication and connection documents, 
<-!><+!>Setting up mail routing<-!><+!>]<-!><:p<* >>

@Chead title@<:s>Completing a connection document for routing

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Select the server that contains the Name & Address you want to edit.

@Numbered list@<:s>Double-click Address book and select View - Connections.

@Numbered list@<:s>Double-click the Connection document you want to edit.

@Numbered list@<:s>Be sure the connection type is correct and locate the Scheduling Calling section. 

@Numbered list@<:s>Select Schedule Enabled in the Enabled/Disabled field.

@Numbered list@<:s>Specify the times or range of times in the Call at times field.

@Numbered list@<:s>Specify the number of minutes in the Repeat interval field.

@Numbered list@<:s>Select which days you want to route mail in the Days of week field.

@Numbered list@<:s>Specify Mail Routing in the Tasks field.

@Numbered list@<:s>Specify the number of messages in the Route at once if field.

@Numbered list@<:s>Do not change the routing cost field. 

@Numbered list@<:s>Save and close the connection document. 

<:s><:p<* >>

@Bhead title@<:s>About mail routing and domain documents

<:s>Domain documents define the location of Notes and non-Notes domains that are not in the local Notes domain. For each domain that communicates with the local domain, you must create a domain document. The domain documents contain information on the type of d
omain and its location as well as fields that allow or deny mail routing. 

<:s>Since you can specify users, groups, and servers that can or cannot send to or receive mail from this domain, this document provides additional control of mail routing. 

@Note@<:s>Do not create domain documents for Notes servers in the local domain.  

<:s>You can create adjacent, non-adjacent, foreign, SMTP, Global, and X.400 domains. 

<:s>You must complete the Mail Routing restrictions section for each domain document. 

<:s><:p<* >>

@Chead title@<:s>Completing a domain document for routing

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Select the server that contains the Name & Address you want to edit.

@Numbered list@<:s>Double-click Address book and select View - Domains.

@Numbered list@<:s>Double-click the Domain document you want to edit

@Numbered list@<:s>Locate the Mail Routing restrictions section. 

@Numbered list@<:s>Specify the domains that can send mail to this domain in the Allow mail only from domains field.

@Numbered list@<:s>Specify the domains that cannot send mail to this domain in the Deny mail from domains field.  

@Numbered list@<:s>Save and close the domain document. 

@Chead title@<:s>

<:s><:p<* >>

@Ahead@<:s>About mail routing to other Notes domains

<:s>In a large organization, there may be Notes domains that are directly connected and others that are not.  When Notes servers in one domain are directly connected to a second domain, they are considered adjacent Notes domains. When Notes servers in two diffe
rent domains are not directly connected and there are no connection documents to link the servers, they are considered non-adjacent Notes domains.

@Bhead@<:s>Adjacent domains

<:s>To route mail between two domains that are connected, you must create an Adjacent Domain document in the Public Name & Address Book (PNAB). In the Adjacent Domain document, you specify the second domain. Notes can then send all mail directly to the adjacent
 domain where it is distributed. 

@Bhead@<:s>Non-Adjacent domains

<:s>To route mail between two domains that are not connected, you must find a third domain that is adjacent to both of the other two. Then you create a Non-adjacent Domain document in the Public Name & Address Book (PNAB). In the Non-adjacent Domain document, y
ou specify a domain that is connected to both of the non-adjacent domains. This middle domain serves as a path between the two non-adjacent domains. When mail is routed to the non-adjacent domain, Notes first sends the mail to the adjacent domain. From ther
e, the adjacent domain forwards the mail on to the next domain.

<:s>To route mail successfully between two non-adjacent domains, you must create two Non-adjacent Domain documents, one for each domain. 
<:p<* >>

@Chead title@<:s>Example: Non-adjacent domains

<:s>For example, suppose that Domain X and Domain Z are non-adjacent, but Domain Y contains Connection documents that link it to both Domain X and Z. T route mail from Domain X to Domain Z, you create a Non-adjacent Domain document in Domain X's PNAB, specifyin
g that mail destined for Domain Z be routed through Domain Y. Then in Domain Z's PNAB, you create a Non-adjacent Domain document, specifying that mail destined for Domain X be routed through Domain Y.

<:s>When the Mail Router has mail addressed from Domain X to Domain Z, it routes the mail through Domain Y. Similarly, when the Mail Router has mail addressed from Domain Z to Domain X, it routes the mail through Domain Y. Domain Y serves only as a hop on the w
ay to the final destination of the mail.

@See also hlp@<:s>

<:s>

@Ahead@<:s><:p<* >>

@Bhead title@<:s>Scheduling server-to-server routing

<:s>You edit each server's Connection document to set up routing between servers in different domains. 

@Numbered list@<:s>Double-click the Notes workstation icon on your Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Choose the name of the calling server from the Servers list. 

@Numbered list@<:s>Double-click the Address Book.

@Numbered list@<:s>Choose View - Connections.

@Numbered list@<:s>Select and open the server's Connection document.

@Numbered list@<:s>Choose Actions - Edit Document.

@Numbered list@<:s>Be sure this switch is set to Schedule Enabled in the Enabled/Disabled field. 

@Numbered list@<:s>Enter the time you want this server to contact the other server in the "Call at times" field. You can enter specific times, ranges (such as 8:00 AM - 10:00 PM), or both. Use a comma to separate times. 

@Numbered list@<:s>Enter the interval you want in the "Repeat interval of" field. The default is 360 minutes. 

@Numbered list@<:s>When you use a range of time in the "Call at times" field, enter the number of minutes between one call and the next. The server tries to replicate and route mail at the specified interval. If it can't complete its tasks, it keeps trying until it succeeds. 
After successful replication or mail routing, the server calls again at the repeat interval that you set. 

@Numbered list@<:s>Specifies the days of the week that you want the server to call in the "Days of week" field. By default, the server calls every day of the week. To use a different schedule for the weekend, create two Connection documents: one that specifies a schedule for 
calling Monday to Friday and another for calling on Saturday and Sunday.

@Numbered list@<+@><:s>Specify Routing in the Tasks field. Both Mail Routing and Replication are enabled initially (separated by a comma). You can create separate documents for Routing and Replication to set up different schedules and priorities. Notes routes mail at the times yo
u scheduled and also when replication is scheduled.

@Numbered list@<:s>Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@Numbered list@<:s>Repeat these steps for the destination server. 

@See also hlp@<:s>

<:s>Scheduling server-to-server replication, ... routing, setting up immediate server-to-server routing,... replication

<:s>

<:s><-!><-">

<:s><:p<* >>

@Bhead title@<:s>Setting up immediate server-to-server routing 

<:s>You edit each server's Connection document to set up immediate routing between two servers in different domains. 

@Numbered list@<:s>Double-click the Notes workstation icon on your Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Choose the name of the calling server from the Servers list. 

@Numbered list@<:s>Click the Address book.

@Numbered list@<:s>Choose View - Connections.

@Numbered list@<:s>Select and open the server's Connection document.

@Numbered list@<:s>Choose Actions - Edit Document.

@Numbered list@<:s>Be sure this switch is set to Schedule Enabled in the Enabled/Disabled field. 

@Numbered list@<+@><:s>Specify Routing in the Tasks field. Both Mail Routing and Replication are enabled initially (separated by a comma). You can create separate documents for Routing and Replication to set up different schedules and priorities. Notes routes mail at the times yo
u scheduled and also when replication is scheduled.

@Numbered list@<:s>Specify 1 in the Route at once if field. Mail is routed immediately. Notes forces the Router to send the pending mail messages. High-priority mail is routed immediately. The default is 5 messages. 

@Numbered list@<:s>Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@Numbered list@<:s>Double-click Console and select a server from the list  to set up immediate routing on the destination server. 

@Numbered list@<:s>Enter ROUTE "server name"

@Numbered list@<:s>Click Done to exit from the Console.

@Bhead title@<:s>

@See also hlp@<:s>

<:s>Scheduling server-to-server routing, setting up immediate server-to-server routing<:p<* >>

@Bhead title@<:s>About disabling mail routing

<:s>Users who have mail files on the same Notes server or share the same Notes network automatically get mail routed to them. You can disable routing to these users by deleting their server documents. Otherwise, you can disable servers in a domain by editing th
eir server document, servers in other Notes domains by editing or deleting their connection documents, and servers in Notes and non-Notes domains by editing or deleting their domain documents. 

<:s>

<:s>

@Bhead title@<:s>Disabling mail routing

@Numbered list@<:s>Double-click the Notes workstation icon on your Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Choose the name of the calling server from the Servers list. 

@Numbered list@<:s>Click Servers - View Servers.

@Numbered list@<:s>Select and open the server document.

@Numbered list@<:s>Choose Actions - Edit Document.

@Numbered list@<:s>Remove Mail Routing, X.400 Mail Routing, or SMTP Mail Routing in the Tasks field.

@Numbered list@<:s>Expand the Server restrictions section.

@Numbered list@<:s>Disable server access in the Can access server field.  

@Numbered list@<:s>Press ESC to exit and save the server document.

@Numbered list@<:s>Select and open the server's connection document.

@Indnt tip@<:s>You can also delete the connection and domain documents to disable routing.

@Numbered list@<:s>Choose Actions - Edit Document.

@Numbered list@<:s>Check the Scheduled Calling section and set Schedule Disabled in the Enabled/Disabled field. 

@Numbered list@<:s>Press ESC to exit and save the connection document.

@Numbered list@<:s>Select and open the server's domain document.

@Numbered list@<:s>Choose Actions - Edit Document.

@Numbered list@<:s>Check the Mail Routing restrictions section and add the domain to the Deny mail from domains field. 

@Numbered list@<:s>Press ESC to exit and save the domain document.

@Bhead title@<:s><:p<* >>

@Bhead title@<:s>About mail routing<:X8,-32768;Index "mail routing" # "foreign domains"> to non-Notes domains

<:s>Depending on the Notes server platform that you choose, Notes can exchange mail with other VIM-compliant electronic mail systems and mail-handling systems. In addition, Notes can deliver incoming and outgoing faxes.

<:s>To accomplish this, you install a <:X8,-32768;Index "message transfer agent (MTA)" #>message transfer agent (MTA) on the Notes server and then compose a foreign domain document to define the foreign mail system. An MTA<:X8,-32768;Index "MTA" #> translates m
essages between the Notes mail format and the mail format of the foreign system. MTAs are add-in products that are not included in the standard Lotus Notes server software.

@See also hlp@<:s>

<:s><+!><[>Creating a foreign domain document]<-!>

@Bhead title@<:s><:p<* >>

@Bhead title@<:s>Schedule guidelines

@Bullet@<:s>When scheduling mail routing, keep in mind the existing replication schedule, because mail routing normally accompanies replication. In other words, do not overschedule traffic between servers.

@Bullet@<:s>You can schedule two calls a day for both replication and mail routing: one in the morning, one in the afternoon. 

@Bullet@<:s>When scheduling mail routing between two servers, you may want to schedule one of the servers to do most of the calling, for billing purposes. (But each server must have at least one Remote Connection document scheduling mail routing to the other server.)

@Bullet@<:s>Schedule calls for times when there is less activity on the network. For example, have the servers call before or after work hours, or at lunchtime.

@Bullet@<:s>For peer</m>to</m>peer connections, limit the number of servers that one server calls to 10 to avoid overloading the server with too many tasks. This isn't necessary with a hub</m>and</m>spoke configuration (see "Hub</m>and</m>Spoke Connections" later in th
is chapter for more information).

@Bullet@<:s>Server performance degrades if the server makes too many calls. When the server becomes overloaded, calls start backing up, mail does not get through, and users may receive poor service from the server.

@Bullet@<:s>With multiple servers' schedules, staggered schedules work well. For example, you could schedule the first server to route mail from 8:00 A.M. to 10:00 A.M., the second server from 8:05 A.M. to 10:05 A.M., and so on. 

@Bullet@For greater efficiency and economy, schedule replications of different priority databases. You can schedule a call between midnight and 6:00 A.M., for example, to replicate low</m>priority databases and (if a Remote connection) to route low</m>priority mail
.

@Bullet@<:s>Connection documents should not have overlapping schedules for the same task, in the same direction, at the same time. Overlapping task schedules give the server conflicting instructions.<:X8,-32768;Index "Conflict" # "in Connection document schedules"><:p<* >>

@Ahead@<:s>Table of <:X8,-32768;Index "cc:Mail" # "mail menu when using with Notes">mail-related NOTES.INI variables

<:s>You can edit the NOTES.INI file to set the mail variables for this server or you can use the Server Configuration documents in the Name & Address book to set these variables.  

<:s>The following NOTES.INI variables can be used to configure mail. 

<:s><:t1>

<:s>

XREF server config doc, edit NOTES.INI<:p<* >>

@Ahead@<:s>Table of mail-related server commands 

<:s>Although, mail routing is set up using Notes menu commands, you can also check or force mail routing using the server console commands. You can enter the commands in the server console or edit the NOTES.INI file.   

@Table title@<:s>Table of mail-related server commands 

<:s><:t0>

<:s>

@See also hlp@<:s>

<:s>Table of server commands for replication, Issuing server commands

<:s><:p<* >>

@Ahead@<:s>About mail routing and Notes system topology

<:s>How Notes routes mail from one server to another depends entirely on the Notes system topology. In some cases, routing is fairly simple and quick. In other cases, routing requires that a document make multiple hops from server-to-server as it finds its way 
to the destination. How many hops a message makes depends on the locations of the sender's and the recipient's home server.

<:s>The following are possible Notes topologies for mail routing:

@Bullet@<:s>The sender and recipient are in the same Notes network and in the same domain. For more information, see 
<+!><[>jump to About mail routing within the same Notes network and domain]<-!>

@Bullet@<:s>The sender and recipient are in different Notes networks . For more information, see 
<+!><[>jump to About mail routing between<-!><+!> different Notes networks]<-!><+!> 
<-!>

@Bullet@<:s>The sender and recipient are in different domains. For more information, see 
<+!><[>jump to About mail routing between different domains<-!><+!>]<-!>

@Bullet@<:s>The sender and recipient are different domains that are connected by a common domain. For more information, see 
<+!><[>About mail routing to a non-adjacent domain]<-!>

@See also hlp@See also <+!><[> About editing connection docs for mail routing

<:s><+!>]<-!><:p<* >>

@Bhead title@<:s>About mail routing within the same Notes network and domain

Mail routing between servers who are in the same Notes network and domain is the fastest, since it's virtually automatic. When a user mails a document, the Notes workstation examines the Public Name & Address Book (PNAB) for the recipient's address. If the 
document is addressed to a named group, Notes examines the PNAB for the group document and then translates the group into a list of individual users. Then, the workstation program appends the correct addresses to the document.

<:s>Next the Mail Router examines the address for the location of the recipient's mail file, which is located on the recipient's home server. Then the Mail Router does one of two things:

@Bullet@<:s>If the recipient's mail file is on the same server as the sender's mail file, the Mail Router moves the document into the recipient's mail file. 

@Bullet@<:s>If the recipient's mail file is on a different server and the PNAB contains a connection document that allows the two servers to communicate, the Mail Router establishes a connection with the destination server, based on the connection document schedule, an
d transfers the document to the destination server's mailbox (MAIL.BOX). 

@1st lev para@<:s>If there are a number of servers between the sender's server and the recipient's server, the Mail Router temporarily stores the document in each server's mailbox until a connection, scheduled via a connection document, routes the document to the next stop o
n its way.

<:s>If there is more than one possible route to the destination server, the Mail Router computes a least-cost route from the source server to the destination server. The Mail Router uses the server, connection, and domain documents in the PNAB to compute the ro
ute.

@See also hlp@<:s>See also <+!><[>About mail routing cost, About alternate routes--these topics are not yet written]<-!><:p<* >>

@Chead title@<:s>Example: Routing mail in the same network and domain 

"Network" in these examples refers to the Notes network(s) you defined when you set up each server and is the name used in each Server document in the Name & Address Book.

@Dhead@<:s><+!>When users have the same home server <-!>

<:s>Jon, whose home server is A, sends mail to Ed, whose home server is also A. The document goes from Jon's workstation to the Router mailbox on Server A. The Router looks up the location of Ed's mail file in the public Name & Address Book. Ed's mail file is o
n the same server, so the Router simply moves the document to Ed's mail file. 

@Dhead@<:s><+!>When u<-!><+!>sers have a different home servers

Jon sends mail to Peggy, whose home server is C. The document goes from Jon's workstation to the Router mailbox on Jon's home server, A. The Router on A examines the Name & Address Book for the location of Peggy's mail file. It sees that Peggy's mail file i
s on Server C, and it transfers the document over the network to Server C's mailbox. The Router on Server C checks the Name & Address Book, sees that Peggy's mail file is on Server C, and transfers the document to her mail file. 

@Dhead@<:s>When users have a different network but are in the same domain

Peggy, whose home server is C, sends mail to Bud. The document goes from Peggy's workstation to Server C's mailbox. The Router on Server C checks the Name & Address Book and finds that Bud's home server, H, is on another network. The Router then checks Conn
ection documents, finds that Server A has a remote connection to Server J on Bud's network, and transfers the mail from C's mailbox to A's. When the mail routing schedule permits, Server A transfers the document to Server J's mailbox. Server J's Router chec
ks the Name & Address Book and sends the document to Bud's home server, H. Server H's Router delivers the document from the mailbox to Bud's mail file. 

@Chead@<:s><:p<* >>

@Bhead title@<:s>About mail routing to different Notes domains

Domains are connected to each other by remote connection documents that you create in the Public Name & Address Book (PNAB) and that connect a server in one domain with a server in the other domain. When a user in one domain mails a document to a user in an
other domain, the Mail Router looks at connection documents in the PNAB to determine how to route the mail. The Mail Router on the sender's mail server looks in the PNAB for a server in the local domain that has a connection to a server in the remote domain
. The Mail Router than transfers the mail document to the server that has a connection. The next time this server connects to the server in the other domain, it transfers the mail. When the mail reaches the server in the other domain, the Mail Router there 
determines where the recipient's mail server is, and then transfers the mail to it.

<:s>If the sender's mail server doesn't have a replica copy of the other domain's PNAB and the correct Names = variable in NOTES.INI, Notes won't be able to translate the group names or check the spelling of recipient's names in the other domain. 

<:s>Servers located in different network domains but the same Notes domain are connected to each other by network connection documents that you create in the Public Name & Address Book (PNAB). Servers located in different network domains and different Notes dom
ains are connected to each other by remote connection documents that you create in the PNAB. When a user mails a document to another user in different Notes domain, the Mail Router looks at connection documents in the PNAB to determine how to route the mail
. Each server's Mail Router along the route computes the least-cost route to the destination server and sends the document to the next hop along the route.

<:s>For mail routing between Notes domains to work properly, be sure that all remote connection documents between domains are replicated in the domain's PNAB, so the servers are visible to all servers.<+!> 
<-!>If the remote connection documents do not define a complete route from the sender's network to the recipient's network, the Mail Router returns the mail to the sender.

@See also hlp@<:s>

<[>Creating connection documents; Managing the Public Name & Address Book; Specifying multiple N&A Books]<:p<* >>

@Chead title@<:s>Example: Routing mail to different domains and different networks

"Network" in these examples refers to the Notes network(s) you defined when you set up each server and is the name used in each Server document in the Name & Address Book.

@Dhead@<:s>Different network, different domain

Peggy, in Domain X, sends mail to Sue, in Domain Y. A Remote Connection document in the Name & Address Book shows that Server K in Peggy's domain can reach Server Q in Sue's domain. The message goes from Peggy's workstation to Server C's mailbox, to Server 
A's mailbox, over the remote connection to J's mailbox, and on to K's mailbox via the network. Server K transfers the document to Server Q's mailbox. The Router on Q finds, in the Name & Address Book in Sue's domain, that Sue's home server is R. It sends th
e document to R's mailbox, where the Router on R places the document in Sue's mail file. 

@Dhead@<:s>Same network, different domain

<:s>Sue, in Domain Y, sends mail to Bob, in Domain Z. The Router examines Domain Y's Name & Address Book and finds a Remote Connection document showing that Server S can reach Server T in Bob's domain. The message goes from Sue's workstation to Server R's mailb
ox, to Server S's mailbox, and on to T's mailbox via the network. Server T transfers the document to the mailbox on Bob's home server, U, where the Router places the document in Bob's mail file. 

<:s>

<:s><:p<* >>

@Bhead title@<:s>About mail routing between non-adjacent Notes domains

<:s>In a large organization, there may be two Notes domains that are not directly connected via a connection document, bridge, or router. These domains are not connected because they do not contain networks that run compatible protocols. To route mail between t
hese domains, you identify a third, "middle" domain that runs multiple protocols and can communicate directly with the two non-adjacent domains. Then you route mail through the "middle" domain to the non-adjacent domain.

<:s>To set up mail routing between non-adjacent domains, you create a non-adjacent domain document in the Public Name & Address Book (PNAB). This document specifies a domain that is connected to the source domain and that can route mail to the non-adjacent, des
tination domain. The adjacent domain is then a hop on the route to the non-adjacent destination domain.

@See also hlp@<:s>

<:s><[>About non-adjacent domain documents; Creating a non-adjacent domain document]

@See also btn@<:s><:p<* >>

@Chead title@<:s>Example: Routing mail to a non</m>adjacent domain

<:s>In a very large organization, there may be two Notes domains that are not directly connected; the servers in one domain have no connections to servers in the other domain. 

<:s>For example, Domain Y is connected to both Domains X and Z, but Domains X and Z are not connected to each other. To route mail from X to Z, you need a Non</m>adjacent Domain document in Domain X's Name & Address Book, which specifies that mail destined for 
Z be routed through Y. When the Router has mail for Z, it then transfers the mail to a server in Y. The server in Y forwards the mail to a server in Z. 

<:s>

<:s><:p<* >>

@Ahead@<:s>About mail priority levels and routing

<:s>When users compose mail messages, they can specify the priority level of the messages. The priority level--high, normal, or low--determines how quickly the mail will be delivered to its recipient. 

@Bullet@<:s>High-priority mail is routed immediately, regardless of the routing schedule. 

@Bullet@<:s>Normal-priority mail is routed at the next scheduled time or as soon as the number of pending messages reaches the route-at-once limit, as specified in the connection document. Normal is the default value for delivery priority.

@Bullet@Low-priority mail is, by default, routed only between midnight and 6:00AM. Notes does not route a low-priority message at any other time.

@See also hlp@<:s>

<[>Changing db priority Changing mail priority Table of mail-related NOTES.INI variables

<:s><:p<* >>

@Bhead title@<:s><+!>Changing routing priority for databases 

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select the database whose priority you want to change.

@Numbered list@<:s>Select File - Replication - Replication Settings.

@Numbered list@<:s>Click Other.

@Numbered list@<:s>Click to choose Low, Medium, or High priority in the Scheduled replication priority section.  

@Numbered list@<:s>Click OK. 

<:s><+!>

@See also hlp@<:s>See also About mail priority levels and routing

<:s><+!><:p<* >>

@Bhead title@<:s><+!>Changing routing priority for mail <-!> 

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select your mail database.

@Numbered list@<:s>Select Create - Mail memo.

@Numbered list@<:s>Specify the user's address in the To field.

@Numbered list@<:s>Enter the message in the body of the memo.

@Numbered list@<:s>Expand the Delivery options section.

@Numbered list@<:s>Click Priority to select High, Normal, and Low. 

@Numbered list@<:s>Select Send and File. 

@See also hlp@<:s>

<:s>About mail priority levels and routing

<:s>

<:s>

<:s><:p<* >>

@Ahead@<:s><+!>About mail routing costs and alternate routes

<:s>When users send mail to other users, Notes uses routing tables to determine the path to send the message. Routing tables are created from the documents in the Name & Address book and are used to find the fastest and least expensive way to send messages betw
een known servers and domains. The routing table uses a combination of the server documents, the domain documents, and the connection documents to designate the path and the cost of sending mail messages. 

@Bhead@<:s>Determining routing costs 

<:s>Typically, after the routing path is determined, the cost is set according to the type of connection and the number of hops it takes to reach its destination. This algorithm is preset so the routing cost is set by the Router and updated according to the rou
ter algorithm automatically. Since Notes routes messages based on the fastest and least expensive route, you can now trace the hops by using Mail Trace. A connection cost of 1 is lowest; 20 is highest???  Values are preset (WHAT ARE THEY??).

<:s>After checking the routes, you can explicitly define a route that the most direct or the most indirect route (using more hops) and the routing cost would change accordingly. 

@Bhead@<:s>Using alternate routes to send mail 

When there is a network failure, Notes can send mail via alternate routes. The Notes Mail Router selects alternate routes by keeping a short-term history of connection failures. The Router uses this history to "weigh" its routing choices. It can then rerout
e messages around network failures. Be aware of the following details:

@Bullet@<:s>The failure history (the cost biases) are kept in the routing tables. The routing tables are memory</m>resident and are reinitialized when the server is restarted, or when the Name & Address Book is modified. The failure history is lost when either event oc
curs; the Router then chooses the original routes until it learns to use the alternate routes again.

@Bullet@<:s>For the Router to use the original route again as soon as possible after a server comes online, the Router deletes a connection's failure history when it receives a successful connection (for example, an incoming phone call). This avoids the problem of an i
nactive server coming online and calling the original server. To handle an inactive server or connection coming online but never calling the original server, all the failure histories are deleted hourly.

@Bullet@<:s>The Router only uses alternate paths of equal<+!> <-!>cost. This means that if alternate, more expensive paths exist, the Router doesn't choose them. This solves problems such as multiple dial</m>up servers between networks and domains or multiple servers w
ithin a network (for example, bridges).

@Bhead@<:s>Preventing routing loops

<:s>When you send a mail message, the message can hop from server to server until it reaches its destination. Without setting the maximum number of hops per message, some messages could 
<:X8,-32768;Index "Hop count" # "illustrated"><:X8,-32768;Index "Mail routing" # "maximum hop count">loop endlessly. To prevent routing loops, Notes sets a default maximum hop count of 25 for each message. So, when Notes routes a mail message, it can make u
p to 25 server stops before the Router returns or discards the message. Each time the message transits a server, the count decrements, until the count reaches zero. The hop count maximum prevents endless message looping between servers.

@Bhead@<:s>Specifying an explicit path

<:s>When a mail address includes an explicit path, each Router along the path routes the mail to the last (rightmost) domain specified in the address. When the mail reaches a server within that domain, the Router strips off the last domain name in the address. 
If there is another domain name remaining, the Router sends the mail to that domain. This process continues until there are no more domain names left in the address, and the mail reaches its destination.

@Bhead title@<:s>Routing mail by specifying an explicit path

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select your mail database.

@Numbered list@<:s>Select Create - Mail memo.

@Numbered list@<:s>Specify the user's address including any servers and domains that you want to route this message through in the To field.

@Numbered list@<:s>Enter the message in the body of the memo.

@Numbered list@<:s>Click Send and File. 

<:s>

<:s><:p<* >>

@Chead title@<:s>Examples: Routing mail using an explicit path 

@Dhead@<:s>Domains

When a route to a domain is not defined in the Name & Address Book with Non</m>adjacent Domain documents, users can address mail using an explicit path that includes all domain names en route to the recipient. For example, you can route mail from domain X t
o Salvador Diaz in domain Z via the adjacent domain Y. Although, the adjacent domain Y is known to both domains X and Z, neither X nor Z are known to the other. The explicit address for this mail message is Salvador Diaz@Z@Y.

@Dhead@<:s>Servers

<:s>You can also specify servers in an explicit path, which is useful when hub servers are unavailable. If the servers that route mail within domains or between domains are not available, you can bypass these servers to make sure mail reaches its destination. 

<:s><:p<* >>

@Bhead title@<:s>Changing mail routing cost

<:s><:X8,-32768;Index "Routing cost" # "overriding"><:X8,-32768;Index "Mail routing" # "overriding standard connection cost">You can change or override the connection cost in the Routing cost field in Connection documents. 

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Choose File - Tools - Notes Administration.  

@Numbered list@<:s>Choose the name of the server from the Servers list. 

@Numbered list@<:s>Double-click the Address book.

@Numbered list@<:s>Select View - Connections.

@Numbered list@<:s>Select Connection document you want to edit.

@Numbered list@<:s>Select Actions - Edit Document.

@Numbered list@<:s>Specify a different connection type. This may change the Routing cost field. 

@Numbered list@<:s>Specify a higher number (increments of 5) in the Routing cost field. 

@Caution@<:s>Changing costs can disable Alternate Route Selection or create routing loops. Use this feature only if you are an experienced Notes administrator. You can assess your changes by examining the Notes Log, checking how often your server calls another or choose
s one over the other.

@Numbered list@<:s>Press ESC when you finish editing and then click Yes (or Save on the Macintosh) to save the document.

@Numbered list@<:s>Repeat these steps for the destination server, if possible.

@See also hlp@<:s>

<:s>

@art:cap@<:s><:p<* >>

@Chead title@<:s>Example: Rerouting mail and cost

<:s>In the example in Figure 4</m>34, the cost for transferring a message from Server A to Server C through Server B is 1, since they are on the same network. The cost for using Server J as the intermediary is 5. If Server A doesn't have a direct connection to 
Server C, Server A chooses Server B as the mail routing connection since the cost is less than routing the mail through Server J. If the cost were the same, Notes would choose the server whose name is first alphabetically.

If the least</m>cost route fails (for example, if there is no answer, or the network times out), the Router adds a cost bias to the connection (or server) entry in the routing table. The next time the Router tries to transfer mail, the cost of that connecti
on is higher than before. If there is an alternate route to the destination that was equal to the original route's cost, the alternate route now costs less than the original route. The Router thus chooses the alternate route. (On a different domain and WAN,
 the alternate route must exist - a Remote Connection document must exist that routes to the alternate server.)

Using the example in Figure 4</m>34, Server A tries to route mail through Server B, but Server B doesn't respond. Server A's routing table now changes to reflect a higher cost for a connection to Server B to discourage mail transfers through that route. The
 next time Server A needs to transfer mail, it finds a lower</m>cost way to route than through Server B.

<:s><:p<* >>

@Ahead@<:s>About mail routing and security

<:s>Notes provides several opportunities for users and administrators to encrypt mail messages. Users are allowed to encrypt or decrypt their mail messages if their public keys reside in the User documents in the Name & Address book. Also, the license type (Nor
th American or International) determines the encryption scheme for users. Users with North American licenses cannot send encrypted messages to International users; although International users can send encrypted mail to users with North American licenses. 

<:s>Encryption does not affect the speed that the message is routed to its destination. It does affect the amount of time it takes to send and open a message since it encrypts and decrypts at that time. The amount of time it takes to encrypt and decrypt depends
 on the message size, graphic images, objects, and attachments that the message contains.  

<:s>Note the following encryption rules: 

@Bullet@<:s>If the mail is encrypted by the sender, the mail isn't encrypted again upon receipt.

@Bullet@<:s>If the user loses his or her User ID, he or she can no longer read encrypted mail documents.

@Bullet@<:s>Notes does not encrypt mail from foreign mail gateways.<:X8,-32768;Index "ACL" #><:X8,-32768;Index "Port" #><:X8,-32768;Index "Port" #><:X8,-32768;Index "LAN" #><:X8,-32768;Index "COM" #><:X8,-32768;Index "Mail" # "router">

<:s>

@See also hlp@<:s>  Ways to encrypt mail

<:s><:p<* >>

@Bhead title@<:s>Ways to en<:X8,-32768;Index "Mail" # "encrypting incoming">crypt mail messages<+!> 
<-!>

<:s>When you encrypt Notes mail, you ensure that only the intended user can read a document. 
<:X8,-32768;Index "Encryption" # "incoming mail, specified by server">You can automatically encrypt the mail received by all mail files on a server by setting a NOTES.INI variable. Encrypting mail on a server provides an additional level of security for use
rs assigned to the server, such as high-level executives or users who handle company-confidential information. Before you encrypt the server, you must check that user documents contain a Public Key. The Public Key enables each user to decrypt encrypted mess
ages.

@Bullet@<:s>Encrypting outgoing mail (workstation) XREF help.nsf

@Bullet@<:s>Encrypting saved mail (workstation) XREF help.nsf

@Bullet@<:s>Encrypting incoming mail (workstation) XREF help.nsf

@Bullet@<+)>Encrypting all incoming mail (server)<-)><+*>H_ENCRYPTING_ALL_INCOMING_MAIL_SERVER<-*>

<:s>

@See also hlp@<:s>  <:p<* >>

@Chead title@<:s>Encrypting all incoming mail on a<:X8,-32768;Index "Encryption" # "incoming mail, specified by user"> server

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Choose File - Tools - Notes Administration and then select the server.  

@Numbered list@<:s>Click Users - View Users to display all of the users. 

@Numbered list@<:s>Double-click any User document to open it and select Actions - Edit Document.

@Numbered list@<:s>Check if the user document contains a Public Key for that user and close the document.

@Numbered list@<:s>Repeat steps 5 and 6 to make sure the Public Key is available for several other users.

@Indnt note@<:s>After checking several User documents for Public Keys, you can assume that Public Keys are available for all users on the server since 
<:X8,-32768;Index "Key" # "public"><:X8,-32768;Index "Public key" # "needed for encryption">Notes automatically adds the public key when it creates the User ID. 

@Numbered list@<:s>Close the Name & Address Book for the specified server. 

@Numbered list@<:s>Double-click Servers - Configure Server.

@Numbered list@<:s>Click Set new parameter.  Enter the following to 

@Indnt mono@SET CONFIG MailEncryptIncoming=1 

@1st lev para@<:s>Notes automatically encrypts the mail received by all mail files. After the NOTES.INI file is read by the server, Notes stores all of the mail, in encrypted form, in the users' mail files on the server's disk. Only the recipient can read the encrypted field
 (the body) of the mail.

@See also hlp@<:s>

<:s>XREF help.nsf topics

<:s>

<:s>

<:s> <:p<* >>

@Ahead@About <+,>USING <-,><++>Notes<-+><+,> WITH O<-,>t<+,>her Mail S<-,>ystems 

When users want to <+,>COMMUNICATE WITH<-,> a mail system other than Notes, you must configure the servers and workstations to allow the exchange of mail. Notes can communicate with cc:Mail and other Vendor Independent Messaging (VIM)-compliant mail program
s. Notes and the other mail system must be connected via a mail gateway or MTA servers. Since these servers are not Notes servers, you must create a Foreign Domain document in the PNAB.  

@Bullet@<:s>Setting up OS/2 servers for cc:Mail users 

@Bullet@<:s>Setting up servers for Notes and cc:Mail users 

@Bullet@<:s>Setting up cc:Mail users in a Notes foreign domain

@Bullet@<:s>Setting up another mail program (Windows or OS/2)

@See also prnt@<:s>For more information about using Notes with cc:Mail, see the Lotus Mail Exchange Facility<+"> Administrator's Guide<-">. For more information about cc:Mail, see the cc:Mail<+"> Administrator's Manual<-">.

@See also hlp@<:s>

<:s><:p<* >>

@Bhead title@<:s>Table comparing Notes, cc:Mail, and other VIM-compliant mail programs

If you want to use <:X8,-32768;Index "User" # "enabling cc:Mail"><:X8,-32768;Index "cc:Mail" # "setting up"><:X8,-32768;Index "VIM" # "VIM</m>compliant mail"><:X8,-32768;Index "Mail" # "cc:Mail with Notes"><:X8,-32768;Index "Mail" # "VIM</m>compliant mail">
cc:Mail or another VIM (Vendor Independent Messaging</m>compliant mail program rather than Notes, the differences are identified to allow users to move easily between Notes and the VIM mail programs. 
<:X8,-32768;Index "Mail" # "using Notes mail with other mail programs">If users choose cc:Mail or another VIM</m>compliant mail program, some Notes functions work somewhat differently or are not available. When the user selects a VIM</m>compliant mail packa
ge, the Mail menu changes to display the appropriate mail commands. In the following table, the Notes mail commands are compared to the cc:Mail and other VIM-compliant mail commands.

<:s>To open a Notes document from a Notes user, a cc:Mail user double</m>clicks the attachment icon to have cc:Mail copy the attachment and launch Notes. A user of another VIM</m>compliant mail program can do the same if the product supports direct launching of
 attachments.

@Table title@<:s>Comparison of Notes mail and VIM</m>compliant mail menus

<:s><:t2>

<:s>In addition to the Mail menu features mentioned in the previous table, users and administrators may want to know what other features are different if they use another mail application. In general, if the feature needs the Notes Router or Mailer to complete 
the action, the feature is unavailable when using other mail applications. The following Notes features are unavailable in cc:Mail or VIM-compliant mail systems:

@Bullet@Dial</m>up mail - A user cannot use Notes to transfer outgoing mail or receive incoming mail. However, cc:Mail users can use cc:Mail Remote] to work from a remote location.

@Bullet@Mail</m>in databases - Notes mail users can send mail directly to a mail</m>in database. cc:Mail users must address mail through the Mail Exchange facility. 

@Bullet@<:s>Server events and database notices mailed to administrator or database manager - The Event Reporter and Database Monitor use Notes mail to deliver reports. The recipient must use Notes mail unless the mail is addressed to cc:Mail through the Mail Exchange f
acility.

@Bullet@<:s>Signing a message - With other mail applications, there is a difference between signing a document and signing a mail message. When the user sends a Notes document (as an attachment), the document can be signed if the mail program supports it. 

@Bullet@Rich text - When sending rich text to cc:Mail users, Notes rich text format is maintained as much as possible. cc:Mail background colors are used to translate certain style conventions. Tables, checkboxes, and radio buttons are converted into ASCII text. Em
bedded graphics and OLE/DDE links are converted to file attachments (where possible). The associated OLE/DDE link graphic is also a file attachment. When sending to users of other VIM</m>compliant mail programs, Notes rich text is converted to text format

<:s><:p<* >>

@Bhead title@<:s>Setting up OS/2 servers for cc:Mail users 

<:s>You can allow cc:Mail users to mail Notes documents to Notes mail users by installing the LMEF software.

@Numbered list@<:s>Install LMEF on a Notes server.

@Numbered list@<:s>Make sure that the Notes program directory is on the same server that contains the Mail Exchange component ($MAILEX.EXE) of the Lotus Mail Exchange Facility. 
<:X8,-32768;Index "Lotus Mail Exchange Facility" #><:X8,-32768;Index "Mail Exchange Facility" #>

@See also hlp@<:s>

LMEF doc <:p<* >>

@Bhead title@<:s>Setting up servers for Notes and cc:Mail users 

<:s>You can allow users with Notes mail and other mail applications to mail memos and documents to each other. 

@Numbered list@<:s>Be sure to install and set up an MTA or a gateway server with the appropriate software. 

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop. 

@Numbered list@<:s>Select File - Tools - Notes Administration and then select a server.

@Numbered list@<:s>Double-click the Address Book. 

@Numbered list@<:s>Select Create - Server Administration - Domains. 

@Numbered list@<:s>Click to display choices and select Foreign Domain.

@Numbered list@<:s>Enter information into the fields in the Foreign Domain document. 

@Numbered list@<:s>Press ESC to exit and save the document.

<:s>

@See also hlp@<:s>

<:s>Setting up OS/2 servers for cc:Mail users, Setting up another mail application (Windows or OS/2), 

<:s><:p<* >>

@Bhead title@<:s>Setting up cc:Mail users in a Notes foreign domain

<:s>To ensure that users in a foreign domain receive their mail, specify a forwarding address in their User document so Notes can direct mail to the proper location.

@Numbered list@<:s>Be sure to install and set up an MTA or a gateway server with the appropriate software. 

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop. 

@Numbered list@<:s>Select File - Tools - Administration, select a server.

@Numbered list@<:s>Double-click the Address book. 

@Numbered list@<:s>Choose View - Users

@Numbered list@<:s>Open the user documents for any users in a foreign domain. 

@Numbered list@<:s>Choose Actions - Edit Document.

@Numbered list@<:s>Enter information in the Forwarding address field in each User document(s). 

@Numbered list@<:s>Press ESC to exit and save the document.

@See also hlp@<:s>

<:s>Setting up servers for Notes and cc:Mail users,, Setting up OS/2 servers for cc:Mail users, Setting up another mail application (Windows or OS/2 )

<:s>

<:s><:p<* >>

@Bhead title@<:s>Setting up another mail application (Windows or OS/2) 

<:s>Users can keep their existing VIM</m>compliant mail program (such as cc:Mail) instead of using Notes mail. You can specify the mail program that users want to use when you register them. To use this feature with cc:Mail, you need a Windows workstation. cc:M
ail 2.0 is recommended over earlier versions to achieve the best Notes</m>to</m>cc:Mail conversion. The alternate mail feature is not supported in Notes for UNIX.

@Numbered list@<:s>Be sure the user installs the other mail program or sets up his or her system to use the mail program from a file server. 

@1st lev para@<:s>The mail program must support the <:X8,-32768;Index "Mail" # "VIM</m>based mail applications"><:X8,-32768;Index "VIM" # "VIM</m>based mail applications">VIM and SMI (Simple Mail Interface) API. In addition, Notes requires that the program has implemented th
e SMIAddressAndSend function, which is a Lotus SMI implementation extension.

@Numbered list@<:s>Be sure the user installs the Notes workstation software and selects a mail system during registration. 

@Numbered list@<:s>If you choose cc:Mail or Other VIM Mail, specify a Forwarding address. This information is added to the user's Person document in the public Name & Address Book. This ensures that Notes mail is directed to the correct mail system.

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop. 

@Numbered list@<:s>Select File - Tools </m> Notes Preferences and click Mail to change the current mail program. 

@1st lev para@<:s>When a user instructs Notes to use cc:Mail or another VIM</m>compliant mail program, Notes renames its VIM.DLL and SMI.DLL files and uses the other application's VIM.DLL and SMI.DLL files instead. The files must be in a directory found on the workstation's 
search path. Only one mail application can be used at a time on a workstation. 

@Numbered list@<:s>Click OK to exit the dialog box. 

@See also hlp@<:s>

<:s>Setting up servers for Notes and cc:Mail users, Setting up OS/2 servers for cc:Mail users, Setting up another mail application (Windows or OS/2)<:p<* >>

@Ahead@<:s>About testing mail routing

<:s>You must test mail routing to ensure that the messages are delivered to the specified recipients. You can test to find the last hop of the delivery route or all the hops in the entire route. Use Mail trace to determine the path that mail messages take when 
they deliver mail. 

<:s>After you create user documents for each user and register each user in the domain, you can test routing by sending mail messages to selected users. You can check if users that are assigned different home servers in the same or different Notes networks or d
omains, receive mail.   

<:s><:p<* >>

@Bhead title@<:s>Tracing the path of a mail message

@Numbered list@<:s>Double-click the Notes workstation icon on the Notes desktop.

@Numbered list@<:s>Select File - Tools - Notes Administration.

@Numbered list@<:s>Click Mail - Send Mail trace. 

@Numbered list@<:s>Enter the name of the user in the To field. 

@Numbered list@<:s>Click either Each Router on Path or Last Router only.  

@Numbered list@<:s>Click Send. 

@Numbered list@<:s>Click Databases - Open Log.

@Numbered list@<:s>Select View - Mail Routing Events - Miscellaneous Events.

@Numbered list@<:s><+!>Can't get this to work... <-!>

@Numbered list@<:s>Close the log file. 

@Numbered list@<:s>Close Notes Administration.

<:s>

<:s><:p<* >>

@Ahead@<:s>About troubleshooting mail routing

<:s>After Notes is configured and set up for mail routing, most users encounter few problems. Some common situations are described and resolved.

@Dhead@<:s>Problem

<:s>When servers are unavailable for any reason, the Router tracks this information. Administrators find that the mail router quickly reroutes mail messages to bypass the unavailable servers.

Notes also prevents routing loops by allowing a total of 25 hops per message. Also, mail messages that are not delivered within 24 hours are categorized as dead mail and the administrators are notified. Users often receive notification that their mail messa
ge cannot be delivered, and can choose to resend it. 

@Dhead@<:s>Solution

<:s>You can open the server's MAIL.BOX to check the Pending Mail and the Dead Letters views. The Pending Mail view indicates when mail is not being routed promptly to servers on the same network or servers connected via a modem. You can also check the Dead Lett
ers view daily or issue the SHOW TASKS command at the server console to determine which documents are not delivered and why. 

XREF ch10?

@Dhead@<:s>Problem

<:s>When users cannot send or receive mail from users in other domains, but can receive mail from users assigned the same home server.  

@Dhead@<:s>Solution

<:s>Check the Server, Connection, and the Domains documents in the Name & Address books for both domains to make sure that the domains know about each other and mail routing is enabled between the two domains. 

<:s>Check the User documents in both Name & Address books to be sure your users are set up and registered. 

Check the NOTES.INI file for DOMAIN= statement, and set it if you cannot find the statement. 

@Dhead@<:s>Problem

<:s>When mail cannot be routed through a modem or using a script, and the physical connections are properly installed.  

@Dhead@<:s>Solution

<:s>Check the User, Server, Connection, and the Domains documents and views in the Name & Address books for both domains to make sure that mail routing is enabled, the ports are set up, and the phone numbers are correct.  

<:s>Check if the servers possess common certificates so they can communicate. 

@Dhead@<:s>Problem

<:s>When user's mail database is configured for single copy object store (SCOS) and users cannot access the shared messages.  

@Dhead@<:s>Solution

Be sure that you linked the user's mail database (username.nsf) to the SCOS mail database (MAILOBJ.NSF) using the new LINK server command.  

@See also hlp@<:s>

Ch 10, <-!><-"><-+><-!><-"><-!><:p<* >>

@Bhead title@<:s><+!>Chapter 4 -- Setting up and Managing Mail

<:s><-!>About Notes mail

<:s>About Notes mail databases

<:s>	Setting up individual mail databases on a server

<:s>About single copy object store (SCOS) 

<:s>	Setting up and enabling object store on a server

<:s>About mail routing basics 

<:s>About mail routing and server documents

<:s>	Completing a server document for routing

<:s>About mail routing and connection documents

<:s>	Completing a connection document for routing

<:s>About mail routing and domain documents

<:s>	Completing a domain document for routing

<:s>About mail routing to other Notes domains

<:s><-!>		Example: Non-adjacent domains

<:s><-!>About mail routing and scheduling

	Scheduling server-to-server routing

<:s>	Setting up immediate server-to-server routing

<:s>About disabling mail routing

<:s>	Disabling mail routing 

<:s>About mail routing to a non-Notes domain

<:s>	Schedule guidelines

<:s>	Table of mail-related NOTES.INI variables

<:s>	Table of mail-related server commands

<:s>About mail routing and Notes system topology

<:s>About mail routing within the same Notes network and domain

<:s><-!>		Example: Mail routing within the same Notes network and domain

<:s>About mail routing to different Notes domains

<:s>		Example: Mail routing to different domains

<:s>About mail routing between non-adjacent domains

<:s>		Example: Mail routing between non-adjacent Notes domains

<:s>About mail priority levels and routing

<:s>	Changing routing priority for databases

<:s>	Changing routing priority for mail

<:s>About mail routing costs and alternate routes  

<:s>	Routing mail by specifying an explicit path

<:s>		Example: Routing mail using an explicit path

<:s>	Changing mail routing cost

<:s>		Example: Re-routing mail and cost

<:s><-!><-!><-!><-!><-!><-!>About mail routing and security

<:s>	Ways to encrypt mail messages

<:s>		Encrypting all incoming mail on a server

<:s>About using Notes with other mail systems

<:s>	Table comparing Notes and VIM-compliant mail programs

<:s>	Setting up OS/2 servers for cc:Mail users

<:s>	Setting up servers for Notes and cc:Mail users

<:s>	Setting up cc:Mail users in a Notes foreign domain

<:s>	Setting up another mail application (Windows)

<:s><-!><-!><-!>About testing mail routing

<:s>	Tracing the path  of a mail message 

<:s>About troubleshooting mail routing<+!>   - <-!>prevent routing loops

<:s>

@Bhead title@<+!>

>

[Embedded]
00125757
