First post of the year!
Domino 7 and 8 releases do not currently support authentication using credentials included within the SOAP packet.
See this TN about an work around
mySphere Posts
Notes does not have the feature to deny Return Receipt. If you don’t like it you can disable it on the server
In the Configuration Settings > MIME tab > Conversion Options tab > General tab, set “Return receipts” as Enabled or Disabled to affect how return receipts go to and from the Internet. For more information, refer to the Domino Administrator Information Center topic “Enabling Domino to process return receipts for SMTP messages.”
If you want to send but control Return Receipt on the Notes Client put the code on the QueryOpen event of the memo form:
Dim answer As Integer
If( Not Source.Document Is Nothing ) Then
If( Source.Document.HasItem( “ReturnReceipt” ) ) Then
If( Source.Document.ReturnReceipt(0) = “1” ) Then
answer% = Messagebox(“Deseja enviar aviso de recebimento solicitado por”& Chr$(10) & Chr$(13) & Chr$(13)_
&Source.Document.GetItemValue(“From”)(0), 36, _
“Aviso de Recebimento”)
If (answer%=7) Then
Source.Document.ReturnReceipt = “0”
Source.Document.Save True, False
End If
End If
End If
End If
We are migrating an installation of Portal 6.0.1.3 to 6.1.0.1. After several errors and corrections applied is time to finalize and put the last piece of IBM HTTP Server. But the Bug described in this TN seems to be the last headache. Beware of remote HTTP Server and Portal 6.1.x
Estamos migrando uma instalação do Portal 6.0.1.3 para 6.1.0.1. Após vários erros e correções aplicadas é hora de finalizar e colocar a última peça IBM HTTP Server.
Mas o Bug descrito no TN nos parece a última dor de cabeça. Cuidado com HTTP Remoto
This link contains useful information about Sametime 8.5 . It is a question and answer document.
Sametime 8.5 is available for download. The infocenter is working and for instant messagin you need this:
Deploying instant messaging and presence only
To provide instant messaging and presence only, use a Sametime® Community Server or cluster of servers running on Domino®.
The following components are deployed in a Sametime environment that contains instant messaging and presence only:
- Lotus® Sametime System Console (used for managing and administering servers from a central location)
- DB2®
- LDAP directory
- Lotus Sametime Community Server
- Lotus Sametime Proxy Server
- Sametime Connect client, Sametime client embedded in Notes®, or Sametime browser client
To extend instant messaging to external communities, also deploy Lotus Sametime Gateway. To provide audio-visual features in the Sametime client, also deploy Lotus Sametime Media Manager.
This funcionality is good and some Administrators do not implement it. From the Domnino Administrator Help
License Tracking allows you to monitor the number of active Notes users within an IBM® Lotus® Domino™ domain. You can use License Tracking to determine how many client licenses you have, whether you need to purchase additional licenses, and when you need to purchase them.
Note License Tracking is not supported in a hosted environment.
When License Tracking is turned on, client usage is tracked on each server and the data is temporarily stored in the file LICENSE.NCF. When a user authenticates with a server using the IBM® Lotus® Notes® client, HTTP, IMAP, POP3, SMTP, or the LDAP protocol, the user’s full canonical name, protocol, and time and date of access are collected. Once each day (at midnight) , an administration request sends to the administration process, information regarding new users and information regarding users who have not accessed the server within the last 30 days. The administration process running on the administration server processes the request.
The Domino User License Tracking database is created and resides on the administration server, not on all servers. The database is not created as soon as the License Tracking feature is enabled; instead, it is created when the administration process processes the first administration request to update the database. The administration process creates a new User License document in the Domino User License Tracking database (USERLICENSES.NSF) for each new user reported in the administration request. Documents are updated with the new time and date for those users who already have a document in the Domino User License Tracking database. If a user does not access any servers in the Domino domain for one full year, the corresponding User License document is deleted from the Domino User License Tracking database. Daily updates to the database enable you to review this information at any time to obtain an up-to-date report on the number of client licenses that you have available for use.
Note If a user is deleted from the Domino Directory, the corresponding document in the Domino User License Tracking database is deleted. If a user is renamed, the corresponding document is also renamed accordingly. Existing administration requests are used to maintain this user information.
By default, administrators have Manager access to the Domino User License Tracking database and users have no access.
Note The Miscellaneous/Licenses view that displayed in Domino R5 is not part of the License Tracking feature.
Enabling or disabling license tracking
Use this procedure to either enable or disable License Tracking.
1. From the Domino administrator, click the Configuration tab.
2. Choose Server – Configurations.
3. Select the server and click Edit Configuration.
4. On the Basics tab, in the License Tracking field, click Disabled or Enabled according to what you want to do.
5. Click Save and Close.
Calculating the number of licenses in use
Use this procedure to recalculate the number of IBM® Lotus® Notes® and/or IBM® Lotus® Domino™ Web Access users in your domain. A document is created for each server in your domain, listing the number of Notes and Domino Web Access users on each server.
1. From the Domino administrator, click the Files tab.
2. Open the Domino User License Tracking database.
3. Choose Active Users – By Server, or choose All Users – By Server, and then click Recalculate Licenses.
O Sametime 8.5 estará dispnÃvel em 22 de Dezembro segundo a IBM. A carta de anúncio está neste link
Sametime version 8.5 will be launched on 22 December.
I was “synchronizing” two clustered Domino Servers. I opened a PMR about the trash folder is different on two replicas. The answer:
When you create a new replica with soft deletions enabled, the soft deletions are not being carried over to the new replica.
Notes and Domino are working as designed. An enhancement request to include this functionality has been submitted to Quality Engineering; however, there are no current plans to implement this functionality.
Workaround used in one case to synchronize the trash folder.
Once that the new replica is being created, if new documents are deleted and sent to the trash folder, these new document do correctly replicate between the replicas and you can see them on the trash folder to the two replicas.
In one occasion this steps helped to synchronize the trash folder of the two replicas:
– Restored the document/s that are present on the trash folder on one of the replicas, therefore you can see the document/s on the Inbox of the database
– Replicate the two databases, the document/s are now present on the Inbox of the 2 replicas.
– Delete the document/s again from one of the replicas.
– Replicate again and now you can see the Trash folder synchronized in the two replicas containing the same number of documents
* If you only do the following, restore the document /s on the database where you have the documents in the trash folder ( you can see the document in the Inbox or this database) and delete them again, so the documents come back to the trash folder, and then you replicate, the trash folder does not get synchronized.
Today i have a issue with thow clustered mail servers. Some databases are different and one server goes down. Some users complain about deletion documents still on their mail databases. I found the cause. I don’t know why yet, but replica setings was not the default settings (like the figure bellow) and deletions doesn’t replicate.
Hoje eu tive um problema com dois servidores clusterizados de correio. Algumas bases estavam diferentes e um dos servidores caiu. Alguns usuários reclamaram que emails antigos ainda estavam nas suas bases. Achei a causa mas não sei porquê estava assim. As definições de replcia estavam marcadas para não replicar deleções.
I have a lot of mail databases and then i use the agent bellow to make sure all databases has the same configuration as the screen above.
Como eu tenho muitas bases eu usei o agente abaixo para verificar as configurações.
Sub Initialize
Dim db As NotesDatabase
Dim ses As New NotesSession
Dim doc As NotesDocument
Dim dbdir As NotesDbDirectory
Dim maildb As NotesDatabase
Dim server As String
Dim subdir As String
Dim rep As NotesReplication
Dim i As integer
server = InputBox (“Nome do Servidor) (Enter para Local)”)
subdir = InputBox (“Em qual subdiretório o agente deve procurar as bases? ( Enter para todos os diretórios) “)
If subdir <> “” Then subdir=subdir & “”
Set db = ses.CurrentDatabase
Set dbdir = ses.GetDbDirectory(server)
Set maildb = dbdir.GetFirstDatabase(DATABASE)
i = 0
While Not (maildb Is Nothing)
If InStr(1,maildb.FilePath,subdir,5)<>0 Then
Call maildb.Open(“”,“”)
If maildb.IsOpen Then
Set rep = maildb.ReplicationInfo
If rep.IgnoreDeletes Then
rep.IgnoreDeletes = False
i = i + 1
End If
Call rep.Save()
End If
End If
Set maildb = dbdir.getnextdatabase
Wend
MsgBox (“Foi (ram) modificado (s) “+ CStr(i) +” banco(s) de dados!” )
End Sub
Acesso ao correio particular usando o Notes não é muito comum mas pode ser necessário. A configuração é simples, basta criar uma conta POP3 e SMTP e pronto. Mas e se você desejar que o correio recebido do seu email particular seja colocado em uma pasta? Regras?
Regras não funcionam em replicas locais. A solução encontrada foi até simples: Faça um encaminhamento da mensagem no seu email particular para seu endereço no Domino e crie uma regra para mover as mensagens do email particular para a pasta desejada
Access to private mail using Notes is not very common but may be necessary. Setup is simple, just create a POP3 and SMTP and ready. But what if you want the incoming mail from your private email is placed in a folder? Rules? Rules do not work on local replicas. The solution was to simple: Make a forwarding of the message on your private email address to the Domino and create a rule to move email messages to a desired folder
If you forget your WebSphere Application Server administrator’s password and/or your WebSphere Portal administrator’s password, and your administrative users are stored in the file registry, how can you reset the forgotten password in the file registry? You can use this TN and solve the problem.
Se você esquecer a senha no WebSphere Portal 6.1 o procedimento neste TN resolve o problema. Válido apenas para o Portal 6.1