Example of an X.400 address:

X.400 Recipient Addresses

Example of an X.400 address:
g=Bill;s=Lee;cn=Bill Lee;o=NAmericaW;p=fab;a= ;c=US;

Address attribute Contents Code
Given Name 0 through 16 characters g
Surname 0 through 40 characters s
Initials 0 through 5 characters i
Generation Qualifier 0 through 3 characters q
Common Name 1 through 64 characters cn
Organization 0 through 64 characters o
Organizational Unit (1-4) 0 through 32 characters ou1-ou4
Private Management 1 through 16 characters p (PRMD)
Administrative Mgmt 1 through 16 characters a (ADMD)
Country 2 characters or 3 digits c

Example of an X.400 address:

X.400 Recipient Addresses

Example of an X.400 address:
g=Bill;s=Lee;cn=Bill Lee;o=NAmericaW;p=fab;a= ;c=US;

Address attribute Contents Code
Given Name 0 through 16 characters g
Surname 0 through 40 characters s
Initials 0 through 5 characters i
Generation Qualifier 0 through 3 characters q
Common Name 1 through 64 characters cn
Organization 0 through 64 characters o
Organizational Unit (1-4) 0 through 32 characters ou1-ou4
Private Management 1 through 16 characters p (PRMD)
Administrative Mgmt 1 through 16 characters a (ADMD)
Country 2 characters or 3 digits c

X.400 TROUBLESHOOT

X.400 TROUBLESHOOT

1) Event Viewer: App & Sys Log on all the servers affected (local & remote).

2) Services must be started: SA, DS, IS, & MTA

3) Verify the configuration of the X.400 connector on both sites. Go through each tab! (169159)

4) Perform connectivity test: servers are online, Ping, tracert, Server Simulator, etc
NOTE: Verify if ICMP is disabled.

5) Send a one-off email to the remote site – determine what happens to this message (NDR, stuck, etc)

6) On the stack tab of the X.400 conn, verify that you can reach the Address listed (use srvsim)

7) Check networking settings: IPConfig, Binding order, Drivers, Network ID, Cabling, etc

8) Enable Diagnostic Logging on the MTA component on each server. Set to MAX.

9) Apply latest MTA build
(As of Sept 1 - 821698 Build: 5.5.2657.49)

10) Perform a Partial MTAWipe

TROUBLESHOOTING NNTP

TROUBLESHOOTING NNTP:

1) Telnet to port 119 and access the POST

2) Verify that the NNTP configuration is correct

3) Enable Diagnostic Logging where available

4) Ensure that 119 is listening (Netstat)

5) Get a Netmon capture of the communication

TROUBLESHOOTING IMAP4

TROUBLESHOOTING IMAP4:

1) Telnet to port 110. Perform manual test.

2) Verify that the POP3 configuration is correct

3) Enable Diagnostic Logging where available

4) Ensure that 110 is listening (Netstat)

5) Test other mailboxes

6) Get a Netmon capture of the communication

TROUBLESHOOTING POP3

TROUBLESHOOTING POP3:

1) Telnet to port 110. Perform manual test.

2) Verify that the POP3 configuration is correct

3) Enable Diagnostic Logging where available

4) Ensure that 110 is listening (Netstat)

5) Test other mailboxes

6) Get a Netmon capture of the communication

TROUBLESHOOTING CCMAIL

TROUBLESHOOTING CCMAIL

1. Verify the configuration of the connector (I.E. Post office name, password, and path) & Service

2. Log on using the Exchange Server service account & connect to the UNC path that is listed.

Make sure that you can write and read to that folder.

3. If Novell Netware is involved, verify access to the resources and permissions are correct on both side (NT & Netware). Set the username and password to match.

4. Check the cc:Mail P O version, and import and export programs. Make sure they are in the path.

5. CCMail admin uses Analyze or Reclaim to check the integrity of the cc:Mail P O

6. Run a manual dirsync using the command, "ccmc ccdir" (without the quotation marks).

NOTE: CTRL+BREAK stops the service.

7. No mail from cc:Mail to Exchange: check the Export folder (under Exchsrvr\Ccmcdata) on Exchange for orphaned files.

8. No mail from Exchange to cc:Mail: check the Submit or Import folders (under Exchsrvr\Ccmcdata) on Exchange for orphaned files.

NOTE: Stop the cc:Mail connector before moving these orphaned files.