ex3

ex3

#Smtp config and VS:
Default relies on 1 smtp vs. this server can also support users of internet mail clients for sending messages. Communication unsecured. No authentication; anonymous(allowed).

Additional vs. 1 settings separately manage ability. 2 each must use unique tcp sockets.
Note, adding additional vs doesn抰 increase server抯 scalability or performance.
Check surrent session number for dos attacks.
还有记住了跟SMTP服务之间的关系。

#Mailroot:
each vs has a separate mailroot dir. \exchsrvr\mailroot. Each contains 3-4 subs. 1 badmail: undelivered messages. Pickup: outgoing messages in text files. Queue: awaiting messages. Filter: not present by default, auto created when messge filtering is enabled.

To change mailroot dir location, use metaedit utility which changes the settings directly in the IIS metabase. Note, ex sys manager only allows the change of badmail dir.

#Traffic: smtp domain name must be reg with dns mail exchanger or mx records. Timeout in general tab default 10 min.

#inbound:
default, only the main smtp domain name of your ex org is configured as an inbound smtp domain. Additional, through recipients policies.

# relaying:
the process of accepting a message from a remote smtp host and forwarding this host to another smtp host for delivery. By default?ex allows only authenticated computers to relay smtp messages.?*anonymous not recommended.

#filter rules:
use wild cards to filter entire domain.
Filter messages with blank sender information.

#reverse dns lookup: verfy domain information submitted bu remote smtp host in ehlo/helo command. Through reverse lookup. (delivery tab)

#message delivery:
size limits. Default inbound recipients per message 5000 receiptents, this locatin apply only to users with mailbox in the org. anonymous, 64,000 recipents, because settings of the smtp vs apply instead of the global delivery settings.

#forwarding:
messages with unresolved recipients to host text box.--- migrated ex milaboxes will receive internet meeage. Nonmigrated users will be forwarded to legacy system(mapi clients). Adivse not to use this feature for long term coexistence.
Note.?Avoid messge loops, do not forward messages for unresolved recipients to another vs?that is configured also for forwarding of unresolved messages. Message tab.

#outgoing:
failur occurs, queues for a later time delivery, first 3 tries within 10 min. after every 15min, for 12 hours, inform sender, 2 days message expires nondelivery report is generated.
Connection limits: default per domain is 100 concurrent. Multi domain 1,000 concurrent. For mulit domain esnding, smtp groups then in memory by destination and batch them in single connection, limit of message per connection is 20 default. For centreal bridgehead, avoid additional handshakes for further connection establishment.
Delivery tab for tcp port.

#smart host:
1 enter tcp port value, 2 specify smart host in advanced delivery dialog box.
Smart host is a server that is able to receive message from relaying systems and send them to the proper destination on behave of the relayers.?Note, default is through dns, if external dns isn抰 intergradted internal.add reference to external to smtp vs configs. (delivery tab)

#richtext:
entire message is encapsulated using the transport neutral encapsulation tnef sent as attachment called winmail in smtp message.
Apply content settings to non mapi clients. Cause server to convert messages from internet mail clients to mapi format.

#logging format:
sometimes it is more sufficient to log in ACSII text file instead of an open database connectivity ODBC ocmpliant database.?Acsii in selected in iis log gile format. Odbc in ex sys man general protocol logging feature.
Access filter based on sender address and sender informaiotn.

#transport event:
transport evens are an extension mechanism for intercepting messages agter the smtp service has received them, before they are delivered to exchange mailboxes or relayed to other smtp hosts.?Event sinks rely on collaboration data objects 2.0. intercept only one type of smtp service event the onarrival event that occurs when a message has been successfully received by the smtp service. Note pretect scripts with ntfs file permissions.?
Virus protection, mail worms, retrives the full set of address information from all available address lists or from messages in the inbox, and a new message address to all recipients is generated

#protocol event:
inbound and outbound.

#event binding:
for event sink to work, reg it with smtp service in iis metabase. A guid id each binding. Use server extension objects seos implemented in a dll called seo.dll to manage event sink bindings. (metaedit, smtpsvc, eventmanager node, event type container.)

#routing groups:
typically share a permanent, reliable high bandwidth network connection, in a routing group all server communivate directly using smtp.?Between routing groups, transfer relies on messaging connectors, connector parameters determines how messages are transferred.
The most important reason to engage in routing group planning is minimizing transmission costs by maximizing the eddiciency of network communication.
Note, all smtp vs of a particular ex 2000 server must belong to the same routing group.
Single routing ?lan.
Server running smtp connector is called a bridgehead, all inout bound traffic must be transferred to the bridge hear server before delivered.

#Routing group org:
Routing groups define the boundaries of direct public folder access. Within a routing group all local public folders are available.
Single advantage:
Easiest message routing administration, connectors installed on bridgehead servers and the routing group are available to all users in the routing group.
Efficient routing of messages, message delivery from server to server is direct and immediate without a need of bridgehead servers single hop routing.
Smtp based.

Multi reasons: wan
Minimize the consumption of network bandwidth. As control access to public folders, replicate public folders instances.
Messaging connectors between routing groups can help minimize transmission costs. Send in batches as specified connection times.
Data is compressed y an average ratio of 5:1

#routing arrangement:
hierarchical arrangement, central group of hub servers controls the entire message transfer between subordinated groups, known as spokes. (large and very large environments). This arrangement share workload and provide redundancy of well defined message paths bwtween all locations, prevents uncontrolled rerouting of message, which was difficult in earilier versions.

Full mesh:?avoid, configure shortcuts between spokes.