排插（插排）的归类问题，即准确的HS CODE~ PS:归类依据可以提供的可以多给分的。。_百度知道
排插（插排）的归类问题，即准确的HS CODE~ PS:归类依据可以提供的可以多给分的。。
目前告知排插功能电力配功能所认归<img class="word-replace" src="/api/getdecpic?picenc=0a007a.37;找文献认排插插座集放起形孔插座认应该归<img class="word-replace" src="/api/getdecpic?picenc=0a007a.36.纠结...预归类或者归类指导意见加哦~~~
提问者采纳
都知道讲东东说清楚点啦
你知道海关编码吗？如果知道的话才可能给出我准确的答案的，这是很专业的归类问题，谢谢~
你看一下，这些是不
这些资料我在海关总署的网站上有看到，但是这也是企业的人归类的资料，并非权威机构的资料。我现在就是纠结于85.36和85.37的归类依据，或者说是证据更合适... ...
权威我就不权威咯
提问者评价
虽然你也不懂，但是还是谢谢啦
其他类似问题
为您推荐：
插排的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁项目语言:JAVA
权限:read-only(如需更高权限请先加入项目)
Index: package.html
===================================================================
--- package.html (revision 0)
+++ package.html (revision 2)
@@ -0,0 +1,738 @@
+&!DOCTYPE HTML PUBLIC &-//W3C//DTD HTML 3.2 Final//EN&&
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright (c)
Oracle and/or its affiliates. All rights reserved.
The contents of this file are subject to the terms of either the GNU
General Public License Version 2 only (&GPL&) or the Common Development
and Distribution License(&CDDL&) (collectively, the &License&).
may not use this file except in compliance with the License.
obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html
or packager/legal/LICENSE.txt.
See the License for the specific
language governing permissions and limitations under the License.
When distributing the software, include this License Header Notice in each
file and include the License file at packager/legal/LICENSE.txt.
GPL Classpath Exception:
Oracle designates this particular file as subject to the &Classpath&
exception as provided by Oracle in the GPL Version 2 section of the License
file that accompanied this code.
Modifications:
If applicable, add the following below the License Header, with the fields
enclosed by brackets [] replaced by your own identifying information:
&Portions Copyright [year] [name of copyright owner]&
Contributor(s):
If you wish your version of this file to be governed by only the CDDL or
only the GPL Version 2, indicate your decision by adding &[Contributor]
elects to include this software in this distribution under the [CDDL or GPL
Version 2] license.&
If you don&#39;t indicate a single choice of license, a
recipient has the option to distribute your version of this file under
either the CDDL, the GPL Version 2 or to extend the choice of license to
its licensees as provided above.
However, if you add GPL Version 2 code
and therefore, elected the GPL Version 2 license, then the option applies
only if the new code is made subject to such option by the copyright
+&BODY BGCOLOR=&white&&
+An IMAP protocol provider for the JavaMail API
+that provides access to an IMAP message store.
+Both the IMAP4 and IMAP4rev1 protocols are supported.
+Refer to &A HREF=&http://www.ietf.org/rfc/rfc3501.txt& TARGET=&_top&&
+RFC 3501&/A&
+for more information.
+The IMAP protocol provider also supports many IMAP extensions (described below).
+Note that the server needs to support these extensions (and not all servers do)
+in order to use the support in the IMAP provider.
+You can query the server for support of these extensions using the
+{@link com.sun.mail.imap.IMAPStore#hasCapability IMAPStore hasCapability}
+method using the capability name defined by the extension
+(see the appropriate RFC) after connecting to the server.
+&H4&SASL Support&/H4&
+The IMAP protocol provider can use SASL
+(&A HREF=&http://www.ietf.org/rfc/rfc2222.txt& TARGET=&_top&&RFC 2222&/A&)
+authentication mechanisms on systems that support the
+&CODE&javax.security.sasl&/CODE& APIs.
+In addition to the SASL mechanisms that are built into
+the SASL implementation, users can also provide additional
+SASL mechanisms of their own design to support custom authentication
+&A HREF=&/javase/6/docs/technotes/guides/security/sasl/sasl-refguide.html& TARGET=&_top&&
+Java SASL API Programming and Deployment Guide&/A& for details.
+Note that the current implementation doesn&#39;t support SASL mechanisms
+that provide their own integrity or confidentiality layer.
+&H4&Connection Pool&/H4&
+A connected IMAPStore maintains a pool of IMAP protocol objects for
+use in communicating with the IMAP server. The IMAPStore will create
+the initial AUTHENTICATED connection and seed the pool with this
+connection. As folders are opened and new IMAP protocol objects are
+needed, the IMAPStore will provide them from the connection pool,
+or create them if none are available. When a folder is closed,
+its IMAP protocol object is returned to the connection pool if the
+pool is not over capacity.
+A mechanism is provided for timing out idle connection pool IMAP
+protocol objects. Timed out connections are closed and removed (pruned)
+from the connection pool.
+The connected IMAPStore object may or may not maintain a separate IMAP
+protocol object that provides the store a dedicated connection to the
+IMAP server. This is provided mainly for compatibility with previous
+implementations of the IMAP protocol provider.
+&H4&QUOTA Support&/H4&
+The IMAP QUOTA extension
+(&A HREF=&http://www.ietf.org/rfc/rfc2087.txt&&RFC 2087&/A&)
+is supported via the
+{@link javax.mail.QuotaAwareStore QuotaAwareStore} interface implemented by
+{@link com.sun.mail.imap.IMAPStore IMAPStore}, and the
+{@link com.sun.mail.imap.IMAPFolder#getQuota IMAPFolder getQuota} and
+{@link com.sun.mail.imap.IMAPFolder#setQuota IMAPFolder setQuota} methods.
+&H4&ACL Support&/H4&
+The IMAP ACL extension
+(&A HREF=&http://www.ietf.org/rfc/rfc2086.txt&&RFC 2086&/A&)
+is supported via the
+{@link com.sun.mail.imap.Rights Rights} class and the IMAPFolder methods
+{@link com.sun.mail.imap.IMAPFolder#getACL getACL},
+{@link com.sun.mail.imap.IMAPFolder#addACL addACL},
+{@link com.sun.mail.imap.IMAPFolder#removeACL removeACL},
+{@link com.sun.mail.imap.IMAPFolder#addRights addRights},
+{@link com.sun.mail.imap.IMAPFolder#removeRights removeRights},
+{@link com.sun.mail.imap.IMAPFolder#listRights listRights}, and
+{@link com.sun.mail.imap.IMAPFolder#myRights myRights}.
+&H4&SORT Support&/H4&
+The IMAP SORT extension
+(&A HREF=&http://www.ietf.org/rfc/rfc5256.txt&&RFC 5256&/A&)
+is supported via the
+{@link com.sun.mail.imap.SortTerm SortTerm} class and the IMAPFolder
+{@link com.sun.mail.imap.IMAPFolder#getSortedMessages getSortedMessages}
+&H4&CONDSTORE and QRESYNC Support&/H4&
+Basic support is provided for the IMAP CONDSTORE
+(&A HREF=&http://www.ietf.org/rfc/rfc4551.txt& TARGET=&_top&&RFC 4551&/A&)
+and QRESYNC
+(&A HREF=&http://www.ietf.org/rfc/rfc5162.txt& TARGET=&_top&&RFC 5162&/A&)
+extensions for the purpose of resynchronizing a folder after offline operation.
+Of course, the server must support these extensions.
+Use of these extensions is enabled by using the new
+{@link com.sun.mail.imap.IMAPFolder#open(int,com.sun.mail.imap.ResyncData)
+IMAPFolder open} method and supplying an appropriate
+{@link com.sun.mail.imap.ResyncData ResyncData} instance.
+{@link com.sun.mail.imap.ResyncData#CONDSTORE ResyncData.CONDSTORE}
+enables the CONDSTORE extension, which allows you to discover the
+modification sequence number (modseq) of messages using the
+{@link com.sun.mail.imap.IMAPMessage#getModSeq IMAPMessage getModSeq}
+method and the
+{@link com.sun.mail.imap.IMAPFolder#getHighestModSeq
+IMAPFolder getHighestModSeq} method.
+{@link com.sun.mail.imap.ResyncData ResyncData} instance with appropriate
+values also allows the server to report any changes in messages since the last
+resynchronization.
+The changes are reported as a list of
+{@link javax.mail.event.MailEvent MailEvent} instances.
+The special
+{@link com.sun.mail.imap.MessageVanishedEvent MessageVanishedEvent} reports on
+UIDs of messages that have been removed since the last resynchronization.
+{@link javax.mail.event.MessageChangedEvent MessageChangedEvent} reports on
+changes to flags of messages.
+For example:
+ Folder folder = store.getFolder(&whatever&);
+ IMAPFolder ifolder = (IMAPFolder)
+ List&MailEvent& events = ifolder.open(Folder.READ_WRITE,
new ResyncData(prevUidValidity, prevModSeq));
+ for (MailEvent ev : events) {
if (ev instanceOf MessageChangedEvent) {
// process flag changes
} else if (ev instanceof MessageVanishedEvent) {
// process messages that were removed
+See the referenced RFCs for more details on these IMAP extensions.
+&H4&WITHIN Search Support&/H4&
+The IMAP WITHIN search extension
+(&A HREF=&http://www.ietf.org/rfc/rfc5032.txt& TARGET=&_top&&RFC 5032&/A&)
+is supported via the
+{@link com.sun.mail.imap.YoungerTerm YoungerTerm} and
+{@link com.sun.mail.imap.OlderTerm OlderTerm}
+{@link javax.mail.search.SearchTerm SearchTerms}, which can be used as follows:
+ // search for messages delivered in the last day
+ Message[] msgs = folder.search(new YoungerTerm(24 * 60 * 60));
+&H4&Properties&/H4&
+The IMAP protocol provider supports the following properties,
+which may be set in the JavaMail &code&Session&/code& object.
+The properties are a the Type column describes
+how the string is interpreted.
For example, use
+ props.put(&mail.imap.port&, &888&);
+to set the &CODE&mail.imap.port&/CODE& property, which is of type int.
+Note that if you&#39;re using the &imaps& protocol to access IMAP over SSL,
+all the properties would be named &mail.imaps.*&.
+&TABLE BORDER&
+&TH&Name&/TH&
+&TH&Type&/TH&
+&TH&Description&/TH&
+&TD&mail.imap.user&/TD&
+&TD&String&/TD&
+&TD&Default user name for IMAP.&/TD&
+&TD&mail.imap.host&/TD&
+&TD&String&/TD&
+&TD&The IMAP server to connect to.&/TD&
+&TD&mail.imap.port&/TD&
+&TD&int&/TD&
+&TD&The IMAP server port to connect to, if the connect() method doesn&#39;t
+explicitly specify one. Defaults to 143.&/TD&
+&TD&mail.imap.partialfetch&/TD&
+&TD&boolean&/TD&
+&TD&Controls whether the IMAP partial-fetch capability should be used.
+Defaults to true.&/TD&
+&TD&mail.imap.fetchsize&/TD&
+&TD&int&/TD&
+&TD&Partial fetch size in bytes. Defaults to 16K.&/TD&
+&TD&mail.imap.ignorebodystructuresize&/TD&
+&TD&boolean&/TD&
+&TD&The IMAP BODYSTRUCTURE response includes the exact size of each body part.
+Normally, this size is used to determine how much data to fetch for each
+body part.
+Some servers report this size incor this property can
+be set to work around such server bugs.
+If this property is set to true, this size is ignored and data is fetched
+until the server reports the end of data.
+This will result in an extra fetch if the data size is a multiple of the
+block size.
+Defaults to false.&/TD&
+&TD&mail.imap.connectiontimeout&/TD&
+&TD&int&/TD&
+&TD&Socket connection timeout value in milliseconds.
+This timeout is implemented by java.net.Socket.
+Default is infinite timeout.&/TD&
+&TD&mail.imap.timeout&/TD&
+&TD&int&/TD&
+&TD&Socket read timeout value in milliseconds.
+This timeout is implemented by java.net.Socket.
+Default is infinite timeout.&/TD&
+&TD&mail.imap.writetimeout&/TD&
+&TD&int&/TD&
+&TD&Socket write timeout value in milliseconds.
+This timeout is implemented by using a
+java.util.concurrent.ScheduledExecutorService per connection
+that schedules a thread to close the socket if the timeout expires.
+Thus, the overhead of using this timeout is one thread per connection.
+Default is infinite timeout.&/TD&
+&TD&mail.imap.statuscachetimeout&/TD&
+&TD&int&/TD&
+&TD&Timeout value in milliseconds for cache of STATUS command response.
+Default is 1000 (1 second).
Zero disables cache.&/TD&
+&TD&mail.imap.appendbuffersize&/TD&
+&TD&int&/TD&
+Maximum size of a message to buffer in memory when appending to an IMAP
If not set, or set to -1, there is no maximum and all messages
+are buffered.
If set to 0, no messages are buffered.
If set to (e.g.)
+8192, messages of 8K bytes or less are buffered, larger messages are
+not buffered.
Buffering saves cpu time at the expense of short term
+memory usage.
If you commonly append very large messages to IMAP
+mailboxes you might want to set this to a moderate value (1M or less).
+&TD&mail.imap.connectionpoolsize&/TD&
+&TD&int&/TD&
+&TD&Maximum number of available connections in the connection pool.
+Default is 1.&/TD&
+&TD&mail.imap.connectionpooltimeout&/TD&
+&TD&int&/TD&
+&TD&Timeout value in milliseconds for connection pool connections.
+is 45000 (45 seconds).&/TD&
+&TD&mail.imap.separatestoreconnection&/TD&
+&TD&boolean&/TD&
+&TD&Flag to indicate whether to use a dedicated store connection for store
+commands.
Default is false.&/TD&
+&TD&mail.imap.allowreadonlyselect&/TD&
+&TD&boolean&/TD&
+&TD&If false, attempts to open a folder read/write will fail
+if the SELECT command succeeds but indicates that the folder is READ-ONLY.
+This sometimes indicates that the folder contents can&#39;tbe changed, but
+the flags are per-user and can be changed, such as might be the case for
+public shared folders.
If true, such open attempts will succeed, allowing
+the flags to be changed.
The &code&getMode&/code& method on the
+&code&Folder&/code& object will return &code&Folder.READ_ONLY&/code&
+in this case even though the &code&open&/code& method specified
+&code&Folder.READ_WRITE&/code&.
Default is false.&/TD&
+&TD&mail.imap.auth.login.disable&/TD&
+&TD&boolean&/TD&
+&TD&If true, prevents use of the non-standard &code&AUTHENTICATE LOGIN&/code&
+command, instead using the plain &code&LOGIN&/code& command.
+Default is false.&/TD&
+&TD&mail.imap.auth.plain.disable&/TD&
+&TD&boolean&/TD&
+&TD&If true, prevents use of the &code&AUTHENTICATE PLAIN&/code& command.
+Default is false.&/TD&
+&TD&mail.imap.auth.ntlm.disable&/TD&
+&TD&boolean&/TD&
+&TD&If true, prevents use of the &code&AUTHENTICATE NTLM&/code& command.
+Default is false.&/TD&
+&TD&mail.imap.proxyauth.user&/TD&
+&TD&String&/TD&
+&TD&If the server supports the PROXYAUTH extension, this property
+specifies the name of the user to act as.
Authenticate to the
+server using the administrator&#39;s credentials.
After authentication,
+the IMAP provider will issue the &code&PROXYAUTH&/code& command with
+the user name specified in this property.
+&TD&mail.imap.localaddress&/TD&
+&TD&String&/TD&
+Local address (host name) to bind to when creating the IMAP socket.
+Defaults to the address picked by the Socket class.
+Should not normally need to be set, but useful with multi-homed hosts
+where it&#39;s important to pick a particular local address to bind to.
+&TD&mail.imap.localport&/TD&
+&TD&int&/TD&
+Local port number to bind to when creating the IMAP socket.
+Defaults to the port number picked by the Socket class.
+&TD&mail.imap.sasl.enable&/TD&
+&TD&boolean&/TD&
+If set to true, attempt to use the javax.security.sasl package to
+choose an authentication mechanism for login.
+Defaults to false.
+&TD&mail.imap.sasl.mechanisms&/TD&
+&TD&String&/TD&
+A space or comma separated list of SASL mechanism names to try
+&TD&mail.imap.sasl.authorizationid&/TD&
+&TD&String&/TD&
+The authorization ID to use in the SASL authentication.
+If not set, the authentication ID (user name) is used.
+&TD&mail.imap.sasl.realm&/TD&
+&TD&String&/TD&
+&TD&The realm to use with SASL authentication mechanisms that
+require a realm, such as DIGEST-MD5.&/TD&
+&TD&mail.imap.sasl. xgwtrustedapphack.enable&/TD&
+&TD&boolean&/TD&
+If set to true, enables a workaround for a bug in the Novell Groupwise
+XGWTRUSTEDAPP SASL mechanism, when that mechanism is being used.
+Defaults to true.
+&TD&mail.imap.auth.ntlm.domain&/TD&
+&TD&String&/TD&
+The NTLM authentication domain.
+&TD&mail.imap.auth.ntlm.flags&/TD&
+&TD&int&/TD&
+NTLM protocol-specific flags.
+See &A HREF=&http://curl.haxx.se/rfc/ntlm.html#theNtlmFlags& TARGET=&_top&&
+http://curl.haxx.se/rfc/ntlm.html#theNtlmFlags&/A& for details.
+&TD&mail.imap.socketFactory&/TD&
+&TD&SocketFactory&/TD&
+If set to a class that implements the
+&code&javax.net.SocketFactory&/code& interface, this class
+will be used to create IMAP sockets.
Note that this is an
+instance of a class, not a name, and must be set using the
+&code&put&/code& method, not the &code&setProperty&/code& method.
+&TD&mail.imap.socketFactory.class&/TD&
+&TD&String&/TD&
+If set, specifies the name of a class that implements the
+&code&javax.net.SocketFactory&/code& interface.
This class
+will be used to create IMAP sockets.
+&TD&mail.imap.socketFactory.fallback&/TD&
+&TD&boolean&/TD&
+If set to true, failure to create a socket using the specified
+socket factory class will cause the socket to be created using
+the &code&java.net.Socket&/code& class.
+Defaults to true.
+&TD&mail.imap.socketFactory.port&/TD&
+&TD&int&/TD&
+Specifies the port to connect to when using the specified socket
+If not set, the default port will be used.
+&TD&mail.imap.ssl.enable&/TD&
+&TD&boolean&/TD&
+If set to true, use SSL to connect and use the SSL port by default.
+Defaults to false for the &imap& protocol and true for the &imaps& protocol.
+&TD&mail.imap.ssl.checkserveridentity&/TD&
+&TD&boolean&/TD&
+If set to true, check the server identity as specified by
+&A HREF=&http://www.ietf.org/rfc/rfc2595.txt& TARGET=&_top&&RFC 2595&/A&.
+These additional checks based on the content of the server&#39;s certificate
+are intended to prevent man-in-the-middle attacks.
+Defaults to false.
+&TD&mail.imap.ssl.trust&/TD&
+&TD&String&/TD&
+If set, and a socket factory hasn&#39;t been specified, enables use of a
+{@link com.sun.mail.util.MailSSLSocketFactory MailSSLSocketFactory}.
+If set to &*&, all hosts are trusted.
+If set to a whitespace separated list of hosts, those hosts are trusted.
+Otherwise, trust depends on the certificate the server presents.
+&TD&mail.imap.ssl.socketFactory&/TD&
+&TD&SSLSocketFactory&/TD&
+If set to a class that extends the
+&code&javax.net.ssl.SSLSocketFactory&/code& class, this class
+will be used to create IMAP SSL sockets.
Note that this is an
+instance of a class, not a name, and must be set using the
+&code&put&/code& method, not the &code&setProperty&/code& method.
+&TD&mail.imap.ssl.socketFactory.class&/TD&
+&TD&String&/TD&
+If set, specifies the name of a class that extends the
+&code&javax.net.ssl.SSLSocketFactory&/code& class.
This class
+will be used to create IMAP SSL sockets.
+&TD&mail.imap.ssl.socketFactory.port&/TD&
+&TD&int&/TD&
+Specifies the port to connect to when using the specified socket
+If not set, the default port will be used.
+&TD&mail.imap.ssl.protocols&/TD&
+&TD&string&/TD&
+Specifies the SSL protocols that will be enabled for SSL connections.
+The property value is a whitespace separated list of tokens acceptable
+to the &code&javax.net.ssl.SSLSocket.setEnabledProtocols&/code& method.
+&TD&mail.imap.ssl.ciphersuites&/TD&
+&TD&string&/TD&
+Specifies the SSL cipher suites that will be enabled for SSL connections.
+The property value is a whitespace separated list of tokens acceptable
+to the &code&javax.net.ssl.SSLSocket.setEnabledCipherSuites&/code& method.
+&TD&mail.imap.starttls.enable&/TD&
+&TD&boolean&/TD&
+&TD&If true, enables the use of the &code&STARTTLS&/code& command (if
+supported by the server) to switch the connection to a TLS-protected
+connection before issuing any login commands.
Note that an appropriate
+trust store must configured so that the client will trust the server&#39;s
+certificate.
This feature only works on J2SE 1.4 and newer systems.
+Default is false.&/TD&
+&TD&mail.imap.starttls.required&/TD&
+&TD&boolean&/TD&
+If true, requires the use of the &code&STARTTLS&/code& command.
+If the server doesn&#39;t support the STARTTLS command, or the command
+fails, the connect method will fail.
+Defaults to false.
+&TD&mail.imap.socks.host&/TD&
+&TD&string&/TD&
+Specifies the host name of a SOCKS5 proxy server that will be used for
+connections to the mail server.
+(Note that this only works on JDK 1.5 or newer.)
+&TD&mail.imap.socks.port&/TD&
+&TD&string&/TD&
+Specifies the port number for the SOCKS5 proxy server.
+This should only need to be used if the proxy server is not using
+the standard port number of 1080.
+&TD&mail.imap.minidletime&/TD&
+&TD&int&/TD&
+Applications typically call the idle method in a loop.
If another
+thread termiantes the IDLE command, it needs a chance to do its
+work before another IDLE command is issued.
The idle method enforces
+a delay to prevent thrashing between the IDLE command and regular
+commands.
This property sets the delay in milliseconds.
+set, the default is 10 milliseconds.
+&TD&mail.imap.enableimapevents&/TD&
+&TD&boolean&/TD&
+Enable special IMAP-specific events to be delivered to the Store&#39;s
+&code&ConnectionListener&/code&.
If true, unsolicited responses
+received during the Store&#39;s &code&idle&/code& method will be sent
+as &code&ConnectionEvent&/code&s with a type of
+&code&IMAPStore.RESPONSE&/code&.
The event&#39;s message will be the
+raw IMAP response string.
+By default, these events are not sent.
+NOTE: This capability is highly experimental and likely will change
+in future releases.
+&TD&mail.imap.folder.class&/TD&
+&TD&String&/TD&
+Class name of a subclass of &code&com.sun.mail.imap.IMAPFolder&/code&.
+The subclass can be used to provide support for additional IMAP commands.
+The subclass must have public constructors of the form
+&code&public MyIMAPFolder(String fullName, char separator, IMAPStore store,
+Boolean isNamespace)&/code& and
+&code&public MyIMAPFolder(ListInfo li, IMAPStore store)&/code&
+In general, applications should not need to use the classes in this
+package directly.
Instead, they should use the APIs defined by
+&code&javax.mail&/code& package (and subpackages).
Applications should
+never construct instances of &code&IMAPStore&/code& or
+&code&IMAPFolder&/code& directly.
Instead, they should use the
+&code&Session&/code& method &code&getStore&/code& to acquire an
+appropriate &code&Store&/code& object, and from that acquire
+&code&Folder&/code& objects.
+&H4&Loggers&/H4&
+In addition to printing debugging output as controlled by the
+{@link javax.mail.Session Session} configuration,
+the com.sun.mail.imap provider logs the same information using
+{@link java.util.logging.Logger} as described in the following table:
+&TABLE BORDER&
+&TH&Logger Name&/TH&
+&TH&Logging Level&/TH&
+&TH&Purpose&/TH&
+&TD&com.sun.mail.imap&/TD&
+&TD&CONFIG&/TD&
+&TD&Configuration of the IMAPStore&/TD&
+&TD&com.sun.mail.imap&/TD&
+&TD&FINE&/TD&
+&TD&General debugging output&/TD&
+&TD&com.sun.mail.imap.connectionpool&/TD&
+&TD&CONFIG&/TD&
+&TD&Configuration of the IMAP connection pool&/TD&
+&TD&com.sun.mail.imap.connectionpool&/TD&
+&TD&FINE&/TD&
+&TD&Debugging output related to the IMAP connection pool&/TD&
+&TD&com.sun.mail.imap.messagecache&/TD&
+&TD&CONFIG&/TD&
+&TD&Configuration of the IMAP message cache&/TD&
+&TD&com.sun.mail.imap.messagecache&/TD&
+&TD&FINE&/TD&
+&TD&Debugging output related to the IMAP message cache&/TD&
+&TD&com.sun.mail.imap.protocol&/TD&
+&TD&FINEST&/TD&
+&TD&Complete protocol trace&/TD&
+&H4&WARNING&/H4&
+&strong&WARNING:&/strong& The APIs unique to this package should be
+considered &strong&EXPERIMENTAL&/strong&.
They may be changed in the
+future in ways that are incompatible with applications using the
+current APIs.
(C)&&2013&&Alibaba&&Inc.&&All&&rights&&resvered.
Powered by}