*
     * @return local port to use for outgoing connections
     */
    int getLocalPort();

    /**
     *
     * Property {@code jcifs.smb.client.laddr} (string)
     *
     * @return local address to use for outgoing connections
     */
    InetAddress getLocalAddr();

    /**
     *
     * Property {@code jcifs.netbios.hostname} (string)
     *
     * @return local NETBIOS/short name to announce

          pingIntervalMillis = client.pingIntervalMillis,
          retryOnConnectionFailure = client.retryOnConnectionFailure,
          fastFallback = client.fastFallback,
          address = client.address(request.url),
          routeDatabase = client.routeDatabase,
          call = this,
          request = request,
        )
      this.exchangeFinder =
        when {

    <example>${fe:formatCode("L", "prettyprint", doc.mimetype, doc.content_description)}</example>
  </function>

  <function>
    <description>Mask e-mail address.</description>
    <name>maskEmail</name>
    <function-class>org.codelibs.fess.taglib.FessFunctions</function-class>
    <function-signature>java.lang.String maskEmail(java.lang.String)</function-signature>

        that it's for a use case that actually comes up in the real world. We want to hear the
        real-world use case so the community can discuss and debate whether this feature is actually
        the *best* way to address the real use case, or whether or not a different approach might be
        more appropriate.


        It's okay if you can't provide complete context on a use case. We understand if you are not

 *
 * There are trade-offs when selecting which options to include when negotiating a secure connection
 * to a remote host. Newer TLS options are quite useful:
 *
 *  * Server Name Indication (SNI) enables one IP address to negotiate secure connections for
 *    multiple domain names.
 *
 *  * Application Layer Protocol Negotiation (ALPN) enables the HTTPS port (443) to be used to
 *    negotiate HTTP/2.
 *

        that actually comes up in the real world. We want to hear the real-world use case so the
        community can discuss and debate whether this feature is actually the *best* way to address
        the real use case, or whether or not a different abstraction might be more appropriate.


        It's okay if you can't provide complete context on a use case. We understand if you are not

    /**
     * Test constructor with a valid token.
     *
     * @throws IOException if an I/O error occurs
     * @throws PACDecodingException if a PAC decoding error occurs
     * @throws UnknownHostException if the IP address is not found
     */
    @Test
    void testConstructor() throws IOException, PACDecodingException, UnknownHostException {
        // Build a sample Kerberos EncData structure

            assertTrue(mockConfig.getWitnessRegistrationTimeout() > 0);
            assertTrue(mockConfig.getWitnessReconnectDelay() >= 0);
        });

        // Test witness address validation
        assertNotNull(mockWitnessAddress);
        assertTrue(mockWitnessAddress.getHostAddress().matches("\\d+\\.\\d+\\.\\d+\\.\\d+"));

        // Test service endpoint formatting

#                                                     ------

# Name to display in the From field of emails.
mail.from.name = Administrator
# Email address to use in the From field.
mail.from.address = root@localhost
# Hostname for the mail server.
mail.hostname=

# ----------------------------------------------------------
#                                                  Scheduler

    }

    /**
     * Check if authentication attempt is allowed
     *
     * @param username the username attempting authentication
     * @param sourceIp the source IP address
     * @return true if attempt is allowed, false if rate limited
     * @throws SmbException if account is locked out
     */
    public boolean checkAttempt(String username, String sourceIp) throws SmbException {