By default only the Inbox and sent items are redirected in Blakcberry devices.
For Redirection folder on Blakberry deivece , it is required to select the folders on Blackberry device.
On blackberry user profile under state database it should show 1 , under folder redirection colum, that means folder redirection =Yes.
How to select the option from device:
Messages -- Options--Email settings ---Select 'Send Email To Handheld' and click on that ---> select 'Folder Redirection' -- Click and Expand and select the folder you want to redirect .
Wait for some time and all the mails coming to selected folder should be delivered to Device.
Sunday, July 27, 2008
Monday, May 5, 2008
Disabling IM / sametime access:
Sametime Connect & Instant Messaging, a user required only an entry in the Domino Directory and Internet / HTTP password to get authorized with the server.
No Access Server field does not work in this case.
Recommended solution:
1. Open Notes Address book.
2. Find the user to be blocked.
3. Go to Sametime server field of user’s person document.
4. Put a nonexistent server name (eg: VirtualIM etc.) in that field
No Access Server field does not work in this case.
Recommended solution:
1. Open Notes Address book.
2. Find the user to be blocked.
3. Go to Sametime server field of user’s person document.
4. Put a nonexistent server name (eg: VirtualIM etc.) in that field
How to rebuild Directory Catalog database:
1.Open Directory catalog database from your server and then configuration, open the
Directory catalog document and then go to advanced tab and clear the history; this will rebuild the directory catalog database.
2. On the command prompt apply this command to fully rebuild the Directory Catalog database:
Load Dircat databasename.nsf -r
Directory catalog document and then go to advanced tab and clear the history; this will rebuild the directory catalog database.
2. On the command prompt apply this command to fully rebuild the Directory Catalog database:
Load Dircat databasename.nsf -r
Setting up a private LAN for a cluster
Setting up a private LAN for your cluster separates the server probes and cluster replication from the rest of your network traffic. This prevents the cluster traffic from slowing down your primary network.
Assign a second IP address to each server. In a cluster using two servers, for example, addresses 192.168.64.1 and 192.168.64.2.
Assign host names for the new IP addresses, and place entries in the HOSTS file or the DNS. In a cluster using two servers
192.168.64.1 server1.xyz.com
192.168.64.2 server2.xyz.com
Verify that the private LAN is operational by making sure that each cluster server can ping both the IP address and the host name of the other cluster servers. Also, be sure that other servers can still ping the cluster servers at their regular LAN addresses.
On each server in the cluster, add new port for the private LAN (Cluster_Net), and edit the Server document to enable the port.
Assign each port an IP address from the corresponding subnets, and place this information in the NOTES.INI file in the following form:
TCPIP_TcpIPAddress=0,10.105.0.11:1352
Net_CLUSTER_TcpIPAddress=0, 192.168.64.1:1352
Server_Cluster_Default_Port= Cluster_Net (port name)
Server_Cluster_Probe_Port= Cluster_Net (port name)
Use show cluster. Command to check that domino is using private LAN.
To check Cluster replication is using the private LAN : From the Domino Administrator click the Server - Statistics tab and check the cluster port statistics
Assign a second IP address to each server. In a cluster using two servers, for example, addresses 192.168.64.1 and 192.168.64.2.
Assign host names for the new IP addresses, and place entries in the HOSTS file or the DNS. In a cluster using two servers
192.168.64.1 server1.xyz.com
192.168.64.2 server2.xyz.com
Verify that the private LAN is operational by making sure that each cluster server can ping both the IP address and the host name of the other cluster servers. Also, be sure that other servers can still ping the cluster servers at their regular LAN addresses.
On each server in the cluster, add new port for the private LAN (Cluster_Net), and edit the Server document to enable the port.
Assign each port an IP address from the corresponding subnets, and place this information in the NOTES.INI file in the following form:
TCPIP_TcpIPAddress=0,10.105.0.11:1352
Net_CLUSTER_TcpIPAddress=0, 192.168.64.1:1352
Server_Cluster_Default_Port= Cluster_Net (port name)
Server_Cluster_Probe_Port= Cluster_Net (port name)
Use show cluster. Command to check that domino is using private LAN.
To check Cluster replication is using the private LAN : From the Domino Administrator click the Server - Statistics tab and check the cluster port statistics
Guidelines for setting server access to databases
Guidelines for setting server access to databases
For replication to occur properly, you must assign servers the
appropriate access in the database ACL. Follow these guidelines when
you set server access to databases.
Assign an access level that is at least as high as the highest user
access level
For example, design changes made to the replica on Server A replicate to
Server B only if the replica on Server B gives Server A at least Designer
access.
Include servers in read access lists for database design elements
If a database design element has a read access list associated with it that
allows access only to certain users with Reader access, include the names
of replicating servers in the read access list in addition to the server
names with Reader access in the database ACL. For example, if a replica
on Server A includes a form access list that limits who can read
documents created with the form, include Server B in the read access list
and give Server B at least Reader access in the ACL to allow Server B to
pull new documents and changes to documents created with the form.
Assign appropriate access to intermediate servers
If replication occurs through an intermediate server, the intermediate
server acts first as a destination server, then as a source server and must
have the access level necessary to pass along the changes. For example, if
you want ACL changes on Server A’s replica to replicate to Server C by
way of Server B, Server B’s replica must give Manager access to Server A,
and Server C’s replica must give Manager access to Server B.
Assign Reader access for one-way replication
Give a server Reader access to a replica when you want to allow the
server to receive information from the replica but not to send changes
back. For example, to allow Server B to receive changes from a replica on
Server A but not to send changes to Server A, give Server B Reader
access to the replica on Server A.
Assign Editor access to allow author changes to replicate
If a replica includes an Authors field that allows authors to modify their
own documents, a server must have at least Editor access, not Author
access, to replicate these modifications. For example, changes made to
Server A’s replica by someone with Author access only replicate to
Server B if Server B’s replica gives Server A at least Editor
Setting up a database ACL for server-to-server replication
You add the names of servers to a database ACL in the same way that
you add the names of people. The access level given to a server in an
ACL determines what, if any, changes that server can replicate to the
replica.
For more information on setting up a database ACL, see the chapter
“Controlling User Access to Domino Databases.”
Default server groups in an ACL
By default, every database ACL includes the server groups
LocalDomainServers and OtherDomainServers.
LocalDomainServers
This group represents servers that are in the same Domino domain as the
server that stores the replica. Typically you assign this group a higher
access level in the database ACL than the OtherDomainServers group.
OtherDomainServers
This group represents servers that are not included in the Domino
domain of the server that stores the replica. Typically you assign this
group a lower access level in the database ACL than
LocalDomainServers. For example, assigning this group Reader access in
the ACL ensures that the local Domino domain retains control over the
database.
Access level privileges
For each access level, you can select or deselect these privileges:
• Create documents
• Delete documents
• Create personal agents
• Create personal folders/views
• Create shared folders/views
• Create LotusScript/Java agents
• Read public documents
• Write public documents
In general, for servers, enable all the privileges that the selected access
level allows. This ensures that the server has access that is as high as
users might have and can replicate all user changes. However, to prevent
certain changes from replicating without deselecting privileges for each
user, you can deselect a particular privilege for a server entry in the ACL.
For example, to prevent all document deletions made in a database on a
particular server from replicating, deselect “Delete documents” in the
ACL entry for the server. Then when users who have “Delete
documents” access in the ACL delete documents, the deletions don’t
replicate.
For replication to occur properly, you must assign servers the
appropriate access in the database ACL. Follow these guidelines when
you set server access to databases.
Assign an access level that is at least as high as the highest user
access level
For example, design changes made to the replica on Server A replicate to
Server B only if the replica on Server B gives Server A at least Designer
access.
Include servers in read access lists for database design elements
If a database design element has a read access list associated with it that
allows access only to certain users with Reader access, include the names
of replicating servers in the read access list in addition to the server
names with Reader access in the database ACL. For example, if a replica
on Server A includes a form access list that limits who can read
documents created with the form, include Server B in the read access list
and give Server B at least Reader access in the ACL to allow Server B to
pull new documents and changes to documents created with the form.
Assign appropriate access to intermediate servers
If replication occurs through an intermediate server, the intermediate
server acts first as a destination server, then as a source server and must
have the access level necessary to pass along the changes. For example, if
you want ACL changes on Server A’s replica to replicate to Server C by
way of Server B, Server B’s replica must give Manager access to Server A,
and Server C’s replica must give Manager access to Server B.
Assign Reader access for one-way replication
Give a server Reader access to a replica when you want to allow the
server to receive information from the replica but not to send changes
back. For example, to allow Server B to receive changes from a replica on
Server A but not to send changes to Server A, give Server B Reader
access to the replica on Server A.
Assign Editor access to allow author changes to replicate
If a replica includes an Authors field that allows authors to modify their
own documents, a server must have at least Editor access, not Author
access, to replicate these modifications. For example, changes made to
Server A’s replica by someone with Author access only replicate to
Server B if Server B’s replica gives Server A at least Editor
Setting up a database ACL for server-to-server replication
You add the names of servers to a database ACL in the same way that
you add the names of people. The access level given to a server in an
ACL determines what, if any, changes that server can replicate to the
replica.
For more information on setting up a database ACL, see the chapter
“Controlling User Access to Domino Databases.”
Default server groups in an ACL
By default, every database ACL includes the server groups
LocalDomainServers and OtherDomainServers.
LocalDomainServers
This group represents servers that are in the same Domino domain as the
server that stores the replica. Typically you assign this group a higher
access level in the database ACL than the OtherDomainServers group.
OtherDomainServers
This group represents servers that are not included in the Domino
domain of the server that stores the replica. Typically you assign this
group a lower access level in the database ACL than
LocalDomainServers. For example, assigning this group Reader access in
the ACL ensures that the local Domino domain retains control over the
database.
Access level privileges
For each access level, you can select or deselect these privileges:
• Create documents
• Delete documents
• Create personal agents
• Create personal folders/views
• Create shared folders/views
• Create LotusScript/Java agents
• Read public documents
• Write public documents
In general, for servers, enable all the privileges that the selected access
level allows. This ensures that the server has access that is as high as
users might have and can replicate all user changes. However, to prevent
certain changes from replicating without deselecting privileges for each
user, you can deselect a particular privilege for a server entry in the ACL.
For example, to prevent all document deletions made in a database on a
particular server from replicating, deselect “Delete documents” in the
ACL entry for the server. Then when users who have “Delete
documents” access in the ACL delete documents, the deletions don’t
replicate.
Sunday, May 4, 2008
Localy encrypted Notes Database
If user has localy encrypte his database with his id file . It is only possible to open the file with same id file or with a id file in ID recovery databse with same encryption key.
There is no other way to open the nsf database or mail file.
How the configured size method effects over-quota enforcement
Unless you configure the Router to withhold mail from or send warnings to users whose mail files exceed their quotas or warning thresholds, you won't notice any differences between the various methods for calculating file size. However, the method you select for calculating file size becomes significant if you enable quota enforcement or warning notifications on the server.
When servers are set to use file size to determine whether a user is over quota, a user who is over quota might not be able to receive mail immediately after deleting messages. This is because white space remains in the mail file until the Compact task removes it(you can write a program document for scheduling the comapct task on every night , use compact -B option to get the size of the mail box down after compaction). As a result, a user whose mail is withheld due to a quota error typically experiences some delay between removing messages and achieving the reduced mail file size required to reinstate mail delivery.
You can configure the Router to notify a user whose mail file exceeds a warning threshold or quota
On servers where quota enforcement is set to "Hold mail and retry," you choose whether the Router attempts delivery to mail files that exceed quota.
You can also customize the quota notification process by writing a script and and notifing user how to reduce the space in their mail file and procedure for house keeping etc.
When servers are set to use file size to determine whether a user is over quota, a user who is over quota might not be able to receive mail immediately after deleting messages. This is because white space remains in the mail file until the Compact task removes it(you can write a program document for scheduling the comapct task on every night , use compact -B option to get the size of the mail box down after compaction). As a result, a user whose mail is withheld due to a quota error typically experiences some delay between removing messages and achieving the reduced mail file size required to reinstate mail delivery.
You can configure the Router to notify a user whose mail file exceeds a warning threshold or quota
On servers where quota enforcement is set to "Hold mail and retry," you choose whether the Router attempts delivery to mail files that exceed quota.
You can also customize the quota notification process by writing a script and and notifing user how to reduce the space in their mail file and procedure for house keeping etc.
Subscribe to:
Comments (Atom)