8.19.2 Trace collection points on JavaMail receipt and the trace information that you can collect

Organization of this subsection

(1) Trace collection points and PRF trace collection levels
(2) Trace information that you can collect

(1) Trace collection points and PRF trace collection levels

The following table describes the information such as Event ID, trace collection points, and PRF trace collection level.

Table 8‒119: Details of trace collection points on JavaMail receipt
Event ID	Numbers used in the figures^#1	Trace collection points	Level
0xAD80	1	Entry point of the `connect(String host, int port, String user, String password)` method of the `javax.mail.Store` class	A
0xAD81	14	Exit point of the `connect(String host, int port, String user, String password)` method of the `javax.mail.Store` class	A
0xAD82	2	Immediately before starting the process to fetch the connection	A
0xAD83	3	Immediately after ending the process to fetch the connection	A
0xAD84	15	Entry point of the `open(int)` method of the `javax.mail.Folder` class	A
0xAD85	18	Exit point of the `open(int)` method of the `javax.mail.Folder` class	A
0xAD86	25	Entry point of the `close(boolean)` method of the `javax.mail.Folder` class	A
0xAD87	36	Exit point of the `close(boolean)` method of the `javax.mail.Folder` class	A
0xAD88	34	Immediately before starting the process to terminate the connection	B
0xAD88	6	Immediately before starting the process to terminate the connection	B
0xAD89	35	Immediately after ending the process to terminate the connection	B
0xAD89	7	Immediately after ending the process to terminate the connection	B
0xAD8A	19^#2	Immediately before starting the process to fetch the entire message information	A
0xAD8B	22^#2	Immediately after ending the process to fetch the entire message information.	A
0xAD8C	28^#2	Immediately before issuing the `DELE` command for all the messages to be deleted	A
0xAD8D	31^#2	Immediately after receiving the response to the `DELE` command for all the messages to be deleted	A
0xAD8E	10	Immediately before starting to issue the `USER` command	A
	23^#3	Immediately before starting to issue the `LIST`, `UIDL`, `RETR`, or `TOP` commands	A
	26	Immediately before starting to issue the RSET command	A
	8	Immediately before starting to issue the `CAPA` command	A
0xAD8F	11	Immediately after receiving the response to the `USER` command	A
	24^#3	Immediately after receiving the response to the `LIST`, UIDL, RETR, or TOP command	A
	27	Immediately after receiving the response to the `RSET` command	A
	9	Immediately after receiving the response to the `CAPA` command	A
0xAD90	12	Immediately before starting to issue the `PASS` command	B
	16	Immediately before starting to issue the `STAT` command	B
	20^{#4, #5}	Immediately before starting to issue the `TOP` or `LIST` command	B
	29^#5	Immediately before starting to issue the `DELE` command	B
	32	Immediately before starting to issue the `QUIT` command	B
	37^#6	Immediately before starting to issue the `NOOP` command	B
0xAD91	13	Immediately after receiving the response to the `PASS` command	B
	17	Immediately after receiving the response to the `STAT` command	B
	21^{#4, #5}	Immediately after receiving the response to the `TOP` command	B
	30^#5	Immediately after receiving the response to the `DELE` command	B
	33	Immediately after receiving the response to the `QUIT` command	B
	38^#6	Immediately after receiving the response to the `NOOP` command	B
0xAD92	4	Immediately before receiving the server response on connection	B
0xAD93	5	Immediately after receiving the server response on connection	B

Legend:

A: Standard

B: Advanced

#1

Corresponds to the numbers used in Figure 8-82 or Figure 8-83.

#2

Fetched at the start and end of receiving the entire mail information.

#3

If not called by specifying ENVELOPE in the 2^nd argument of the fetch method of the javax.mail.Folder class.

#4

Only if called by specifying ENVELOPE in the 2^nd argument of the fetch method of the javax.mail.Folder class.

#5

Fetched at the start and end of receiving the individual mail information.

#6

Collected only when connected to the server.

The following figure shows the trace collection points on JavaMail receipt.

Figure 8‒82: Trace collection points on JavaMail receipt

Figure 8‒83: Trace collection point on confirming the JavaMail connection

To Page Top

(2) Trace information that you can collect

The following table describes the trace information that you can collect on JavaMail receipt.

Table 8‒120: Trace information that you can collect on JavaMail receipt
Numbers used in the figures^#1	Event ID	Level	Interface name	Operation name	Option
1	0xAD80	A	--	--	--
2	0xAD82	A	--	--	#2
3	0xAD83	A	--	--	Exception class name in the event of an abnormality
4	0xAD92	B	String that shows communication^#3	--	--
5	0xAD93	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
6	0xAD88	B	--	--	--
7	0xAD89	B	--	--	Exception class name in the event of an abnormality
8	0xAD8E	A	String that shows communication^#3	--	--
9	0xAD8F	A	String that shows communication^#3	Response code from the mail server^#4	Name of the exception class if an error occurs
10	0xAD8E	A	String that shows communication^#3	--	--
11	0xAD8F	A	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
12	0xAD90	B	String that shows communication^#3	--	--
13	0xAD91	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
14	0xAD81	A	--	--	Exception class name in the event of an abnormality
15	0xAD84	A	--	--	--
16	0xAD90	B	String that shows communication^#3	--	--
17	0xAD91	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
18	0xAD85	A	--	--	Exception class name in the event of an abnormality
19^#5	0xAD8A	A	--	--	--
20	0xAD90	B	String that shows communication^#3	--	--
21^#6	0xAD91	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
22^#5	0xAD8B	A	--	--	Exception class name in the event of an abnormality
23	0xAD8E	A	String that shows communication^#3	--	--
24^#6	0xAD8F	A	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
25	0xAD86	A	--	--	--
26	0xAD8E	A	String that shows communication^#3	--	--
27	0xAD8F	A	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
28	0xAD8C	A	--	--	--
29	0xAD90	B	String that shows communication^#3	--	--
30	0xAD91	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
31	0xAD8D	A	--	--	Exception class name in the event of an abnormality
32	0xAD90	B	String that shows communication^#3	--	--
33	0xAD91	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality
34	0xAD88	B	--	--	--
35	0xAD89	B	--	--	Exception class name in the event of an abnormality
36	0xAD87	A	--	--	Exception class name in the event of an abnormality
37	0xAD90	B	String that shows communication^#3	--	--
38	0xAD91	B	String that shows communication^#3	Response code from the mail server^#4	Exception class name in the event of an abnormality

Legend:

A: Standard

B: Advanced

--: Not applicable

#1

Corresponds to the numbers used in Figure 8-82 or Figure 8-83.

#2

Outputs the following items:

host-name port-number timeout-value-when-fetching-connection communication-timeout-value

Each of the items should be output by separating them with a space.

0 is output if the timeout is set to infinite. -1 is output, if the user omits the timeout setting.

(Example) localhost 25 10000 10000

#3

The following table describes the output contents of the strings that show communication:

Sr. No.	String that shows communication	Communication process
1	-- (Not applicable)	Fetch connection
2	connect-mail-server	Fetch server response on connection
3	USER	Issue `USER` command
4	PASS	Issue `PASS` command
5	QUIT	Issue `QUIT` command
6	STAT	Issue `STAT` command
7	`LIST` command arguments	Issue `LIST` command
8	`UIDL` command arguments	Issue `UIDL` command
9	`RETR` command arguments	Issue `RETR` command
10	`TOP` command arguments	Issue `TOP` command
11	`DELE` command arguments	Issue `DELE` command
12	`NOOP`	Issue `NOOP` command
13	`RSET`	Issue `RSET` command
14	`CAPA`	Issuing the `CAPA` command

#4: Response code is output only if the 1^st line of the response is received. Response code is not output, if the response is not received due to the abnormal conditions such as occurrence of IOException in communication.
#5: The following table describes the output contents of responses:

Response	Output contents
Response code is correct (satisfies the RFC specifications)	Response code
Response code is incorrect (does not satisfy the RFC specifications)	Header 4 letters of the 1^st line of the response (See KDJE59112-E message for details) If the 1^st line is less than 4 letters Output all the letters present in the 1^st line No response Output empty string

Response

Output contents

Response code is correct (satisfies the RFC specifications)

Response code

Response code is incorrect (does not satisfy the RFC specifications)

Header 4 letters of the 1^st line of the response (See KDJE59112-E message for details)

If the 1^st line is less than 4 letters

Output all the letters present in the 1^st line
No response

Output empty string

#6: For the commands (RETR command, TOP command, and UIDL command) that receive multiple-line response, return code 0 is output on fetching the 1^st line of the response.

To Page Top