SMTP Commands

1.                   Type open mail1.fabrikam.com 25 and then press ENTER.

2.                   Type EHLO contoso.com and then press ENTER.

3.                   Type MAIL FROM:chris@contoso.com and then press ENTER.

4.                   Type RCPT TO:kate@fabrikam.com NOTIFY=success,failure and then press ENTER. The optional NOTIFY command defines the particular delivery status notification (DSN) messages that the destination SMTP server must provide to the sender. DSN messages are defined in RFC 1891. In this case, you are requesting a DSN message for successful or failed message delivery.

5.                   Type DATA and then press ENTER. You will receive a response that resembles the following:

Copy Code

354 Start mail input; end with <CLRF>.<CLRF>

6.                   Type Subject: Test from Contoso and then press ENTER.

7.                   Press ENTER. RFC 2822 requires a blank line between the Subject: header field and the message body.

8.                   Type This is a test message and then press ENTER.

9.                   Press ENTER, type a period ( . ) and then press ENTER. You will receive a response that resembles the following:

Copy Code

250 2.6.0 <GUID> Queued mail for delivery

10.               To disconnect from the destination SMTP server, type QUIT and then press ENTER. You will receive a response that resembles the following:

Copy Code

221 2.0.0 Service closing transmission channel

11.               To close the Telnet session, type quit and then press ENTER.

Running NSD Manually - AIX

InBlrM107:[/applications]#cd lotus

InBlrM107:[/applications/lotus]#ls -l

total 8

drwxr-xr-x    3 root     system         4096 Jan 13 2009  bin

drwxr-xr-x    4 root     system          256 Jan 08 2009  domino

drwxr-xr-x    3 root     system          256 Jan 13 2009  notes

InBlrM107:[/applications/lotus]#cd bin

InBlrM107:[/applications/lotus/bin]#ls -l

total 0

lrwxrwxrwx    1 root     system           37 Jan 13 2009  beta3upd -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  catalog -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  cconsole -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  checkos -> /applications/lotus/bin/tools/execbin

lrwxrwxrwx    1 root     system           37 Jan 13 2009  compact -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  convert -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  design -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  faultmon -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  fixup -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  http -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  java -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  jconsole -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  ldapsearch -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  notesjre -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           41 Jan 13 2009  nsd -> /applications/lotus/bin/tools/diag/nsd.sh

lrwxrwxrwx    1 root     system           37 Jan 13 2009  nwar -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  object -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  replica -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  server -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  statlog -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  stats -> /applications/lotus/bin/tools/startup

drwxr-xr-x    3 root     system          256 Jan 13 2009  tools

lrwxrwxrwx    1 root     system           37 Jan 13 2009  updall -> /applications/lotus/bin/tools/startup

lrwxrwxrwx    1 root     system           37 Jan 13 2009  update -> /applications/lotus/bin/tools/startup

InBlrM107:[/applications/lotus/bin]#cd /applications/lotus/bin/tools/diag

This should run in Notes login only

then run this command ./nsd.sh.

InBlrM107:[/applications/lotus/bin/tools/diag]# ./nsd.sh.

Installing Domino

Installing Domino

To install Lotus Domino on aWindows platform, follow these steps.

1. Run the install program (setup.exe), which is on the Domino server installation CD.
2. Read the Welcome screen, and click Next. Then read the License Agreement and click Yes.
3. Enter the administrator's name and the company name. Do not elect to install Lotus Domino on partitioned servers.
4. Choose the program and data directory in which to copy the software, and then click Next.
5. Select "Domino Enterprise Server" as the server type.
6. Click Next to accept all components.
7. Specify the program folder or accept Lotus Applications as the program folder that will contain the software.
8. Click Finish to complete the install program.
9. Choose Start - Programs - Lotus Applications - Lotus Domino Server to start the Server Setup program.

Ports used by Lotus Notes

The Lotus Notes Domino web server uses port 80 to distribute and receive http requests.

The Lotus Notes Client uses port 1352 by default to communicate with the Lotus Notes Server.

Lotus Notes servers use port 1352 by default to replicate with each other.

The Lotus Notes server uses port 25 when using SMTP to receive and send email.

Ports 63148 and 63149 are used to process CORBA requests.

Lotus Notes Domino server uses port 443 for https or SSL requests.

Lotus Notes uses port 8080 as the default for http proxy requests.

Duplicate Calendar Entries

Case: In my calendar I don’t see any entries for Monday and Tuesday between 1 to 5 PM Eastern Time, but when my colleague tries to send me an invite during that time he says I am unavailable in the scheduler. Ie., in lotus notes when you click new meeting and you say check availability it is all red that means the recipient is unavailable, what you need to do at first.

Just follow what IBM says.

http://www-01.ibm.com/support/docview.wss?uid=swg21141060

http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21086471

Mostly this would resolve, but this time it did not. Now what I did?

Right click on where it says unavailable, you will definitely be shown the one calendar entry which is causing the problem. We had to delete that particular entry and re create that through lotus notes.

Root cause : Mostly this is because the entry created through a handheld which creates joint synchronization issue. But we cannot advice any one not to create a calendar entry through Hand held. But even if created and we have this issue, now we know what to do..

Cannot accept and Decline meetings with repeat instances

I thought it is good to write on the rock some thing which I have learned recently, hence this endeavor.

When I try to accept a repeat instances of meetings in lotus notes I get an error message. "An Error occurred  while saving : Error creating repeat instances".

Another issue for the same user is shown below : This occurs when I try to decline the meetings with comments but this does not happen if just decline. Really crazy. Error message - " Error occurred while saving : Notes error: The Database cannot be read due to invalid disk structure "

Solution :

I ran maintenance

l compact -c mail\mailfile.nsf

l fixup -f mail\mailfile.nsf

l updall -r mail\mailfile.nsf

Guess what. Issue is fixed. Let's celebrate now.