if (resp instanceof SmbComTransactionResponse) {
                    ((SmbComTransactionResponse) resp).nextElement();
                }
            }

            /* Verification fails (w/ W2K3 server at least) if status is not 0. This
             * suggests MS doesn't compute the signature (correctly) for error responses
             * (perhaps for DOS reasons).
             */

        }
        if (configId.length() < 2) {
            throw new FessSystemException("Invalid configId length: " + configId + ". ConfigId must be at least 2 characters long.");
        }
        final CrawlingConfig config = crawlingConfigHelper.getCrawlingConfig(configId);
        if (config == null) {
            throw new FessSystemException("No crawlingConfig: " + configId);

        final InputStream in = new ByteArrayInputStream(xml.getBytes());
        final SitemapSet sitemapSet = sitemapsHelper.parse(in);
        final Sitemap[] sitemaps = sitemapSet.getSitemaps();

        // Should parse at least the 3 valid entries
        assertTrue(sitemaps.length >= 3);
        boolean foundPage1 = false;
        boolean foundPage2 = false;
        boolean foundPage3 = false;
        for (Sitemap sitemap : sitemaps) {

                     */
                    /* Technically we should also try to authenticate here but that means doing the session setup and tree connect separately. For now a simple connect will at least tell us if the host is alive. That should be sufficient for 99% of the cases. We can revisit this again for 2.0.
                     */
                    trans.connect();

      <match value="X-Notes-Item:" type="string" offset="0">
        <match value="Message-ID:" type="string" offset="0:8192"/>
      </match>
      <!-- match X- DKIM- ARC- at start of file and then require at least one
           of the usual: from, received, date...but look farther into the file
           because of the X|DKIM|ARC headers-->
      <match value="(X|DKIM|ARC)-" type="regex" offset="0">