A. The latest version of the FAQ should be found at http://www.ikakura.com/faq.html.
A. Microsoft has recently released a hotfix for MAPI (CDO.DLL) which fixes a problem caused by Outlook 2003 which may affect Ikakura if someone accesses the Ikakura service account inbox with Outlook 2003.
See the following article for information and to download the hotfix from Microsoft: http://support.microsoft.com/default.aspx?kbid=823343
A. Most listserver events are listed as event 109. Check the text of the event to find the description for the event.
Q. Why do all the errors say "The description for Event ID ( 109 ) in Source ( ReddFish ListServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event:"?
A. On some machines, the above text is prepended to every listserver event - this part of the event description is basically meaningless - the actual error message begins after the colon.
A. Sometimes this problem has occurred due to "half-finished"
contacts created in the ReddFish ListServer Data container.
You should check the container for an existing contact for the
person you were trying to add.
This message is usually associated with an error event similar to:
ActiveDirectoryService.SubscribeNewCustomRecipient: -2147217 887: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done
Q. Does the first part of mail address for subscription have to be REDDFISHLISTSERVER?
A. Only the "alias" has to be ReddFishListServer - the e-mail address can be whatever you like.
Q. What is the problem with DAPI?
A. A common problem on Ikakura prior to Version 4, this is due to the presence of an old version of DAPI.DLL on the listserver's search path (DAPI.DLL is a component of Exchange Server 5.5 and is present on Exchange 2000 servers only for compatibility with legacy applications).
On Exchange 2000, you should have DAPI 6 installed, but many upgraded machines still have DAPI 5, which would normally indicate Exchange 5.5 was still installed. The ListServer will use Exchange 5.5 if it is installed. When the ListServer attempts to log in to Exchange 5.5 it fails - this causes an error in the application log every 5 minutes.
On Ikakura Version 4 - make sure you have set the correct Exchange Version on the Options tab of the Ikakura Service Manager.
On older versions of Ikakura, you can get rid of DAPI related error events by removing DAPI.DLL - We recommend renaming the DLL so it cannot be found by the ListServer. We have not heard of any problems due to removing DAPI.DLL - it is not normally needed by Exchange Server 2000.
Q. I've just installed on Windows 2000/2003 and I can't start the service?
A. It is necessary to give the full username and domain for the service user account. On a Windows 2000 domain the username needs to be in the format username@domain.com rather than the old DOMAIN\\USER format.
Sometimes, it helps to use the Control Panel "Services" applet to start the ReddFish ListServer service as it lets you browse for the username to use when starting the service.
Q. How do I fix MAPI_E_LOGON_FAILED?
A. The most common cause of this error is an incorrect alias name on the exchange mailbox which must be ReddFishListServer (all one word, case as shown).
The things to check are:
There is a remote possibility that Active Messaging is not properly registered. This component is installed as part of Exchange Server (and various other products), but the installation of this component in our experience is often broken. (For details of the library see http://support.microsoft.com/default.aspx?scid=kb;en-us;Q171440 ) It may help to unregister, and then re-register the library as follows:
Q. How do I debug logon problems?
A. Try following the instructions for "emulating ikakura" in the manual.
Q. When I send an email to the address of the distribution list, with various commands like Lists, Subscribe, etc. there is no response back from the listserver?
A. Command messages should be sent to the listserver e-mail not to the lists themselves.
Q. How do I fix "Object Variable or With Block not Set" errors?
A. These are probably a consequence of the logon failure.
Q. How do I move or rename the ReddFish ListServer Data container?
A. The default name of the container that used to hold the mailing lists
is ReddFish ListServer Data.
You can use a different name, or specify the name and location of the
container as follows:
1 Using regedit; go to the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReddFish ListServer\Parameters
2. add a String value called "Container Location".
The value should be the path to the OU where you want to store the
lists N.B.
Q. Can we install the ListServer on a second (Backup) Microsoft Exchange Server?
A. Yes, provided the 2 servers are not running simultaneously. Some system administrators configure a backup server so that if the live server is damaged, they can start the backup server quickly.
N.B. It is probably not safe to run two listserver simultaneously with the same listserver user account.
Q. What dependencies does Ikakura have when running on Exchange 2000?
A. The application has these dependencies:
Q. How do I create DEBUG logs?
A. Debug logs can be created as follows:
Q. Does Ikakura run on Windows 2000 SP3?
A. Yes, Ikakura does run on Windows 2000 SP3 with Exchange SP3.
There may be an issue with Widows 2000 SP3 installing an old version
of DAPI.DLL see FAQ for DAPI.DLL
Q. ActiveDirectoryService.SubscribeNewCustomRecipient: -2147463168: Unknown Error.
A. Error -2147463168 is "An invalid ADSI path name was passed". The most likely error is that the "ReddFish ListServer Data" container does not exist or has the wrong spelling - the name must appear with the case and spacing above (spaces between h and L and r and D).
Q. My ListServer reports "No lists were found". What is wrong?
A. (1) This can also be the result of a missing or mis-spelled "ReddFish ListServer Data" container.
A. (2) Sometimes, the Exchange server configuration leaves the lists with
invalid e-mail addresses. Some users have found that if they add
an X400 address for the list the listserver is then able to find the lists.
The debug message trace for this problem looks like:
Q. How do I fix ADODB problems?
A. ADODB is part of the Microsoft Data Access Components (MDAC) 2.5.
There is a known problem with ADODB, Microsoft's suggested fix
is to install Windows 2000 SP3. You could also try reinstalling MDAC
or installing one of the MDAC service packs on the MS site:
http://www.microsoft.com/data/download.htm
Q. What version of Ikakura am I running?
A. Check your listserver version against the version numbers on http://www.ikakura.com/version.html
The current version of the Ikakura list server is 3.1.1
The versions of key files are:
LISTSERVER.EXE
4.0.0.1
RFLSMAN.EXE
4.0.0.0
RFDAPI.DLL
3.1.0.1
RFABFIND.DLL
1.1.0.0
Q. How do I prevent spammers from mailing to my lists?
A. The key thing is to ensure that you set "Delivery Restrictions on
lists as described on p. 18 of the manual. This prevents non-members from
sending to a list.
Q. How do I add a large number of members to a list?
A. First take a look at: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q327620
which describes Microsoft's tool for importing and exporting CSV data
to Active Directory.
The other way is to generate a text document with a large number of subscribe commands.
Set yourself as list-owner, then paste batches of subscribe commands into an e-mail
and send them to the listserver.
e.g.
silent subscribe this-list abc@xyz.com
silent subscribe this-list def@xyz.com
...
silent subscribe this-list zzz@xyz.com
When the ListServer returns a welcome message to a new subscriber,
that subscriber must exist. If an NDR is received in response to the
welcome message, the ListServer deletes the new recipient it created.
This stops people using bogus e-mail addresses to join a list.
Q. How can I run the ListServer on a different server than the Exchange Server?
A. To run Ikakura on a separate server (not the Exchange 2000 Server), you will need to
Q. I get 15-20 informational events (108) everytime I send a subscribe note. How can I stop my event logs filling up like that?
A. Your listserver is probably running in debug mode. Check the debugging tab on the Ikakura service manager.
Q. One user receives a response e-mail every minute from the list server saying that they were added. How do I fix this?
A. The most likely cause of this would be a subscribe message "stuck"
in the ListServer's inbox - check the inbox and remove the stuck message
(we are looking into the reason why messages can get stuck in the inbox).
Q. How do I install Ikakura onto a separate Exchange Server