From owner-svn-doc-all@freebsd.org Wed Nov 20 05:54:36 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7ED321A9718; Wed, 20 Nov 2019 05:54:36 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47HsMw2b9Sz4N4g; Wed, 20 Nov 2019 05:54:36 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 37AB51E4BA; Wed, 20 Nov 2019 05:54:36 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id xAK5saO0002608; Wed, 20 Nov 2019 05:54:36 GMT (envelope-from linimon@FreeBSD.org) Received: (from linimon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id xAK5saYR002607; Wed, 20 Nov 2019 05:54:36 GMT (envelope-from linimon@FreeBSD.org) Message-Id: <201911200554.xAK5saYR002607@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: linimon set sender to linimon@FreeBSD.org using -f From: Mark Linimon Date: Wed, 20 Nov 2019 05:54:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53612 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head X-SVN-Commit-Author: linimon X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/faq X-SVN-Commit-Revision: 53612 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2019 05:54:36 -0000 Author: linimon Date: Wed Nov 20 05:54:35 2019 New Revision: 53612 URL: https://svnweb.freebsd.org/changeset/doc/53612 Log: Remove stale questions about bind and sendmail. Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Wed Nov 20 05:50:20 2019 (r53611) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed Nov 20 05:54:35 2019 (r53612) @@ -5349,57 +5349,6 @@ nodevice gre - - BIND9 - (named) is listening on some - high-numbered ports. What is going on? - - - - BIND uses a random high-numbered port for outgoing - queries. Recent versions of it choose a new, random UDP - port for each query. This may cause problems for some - network configurations, especially if a firewall blocks - incoming UDP packets on particular ports. To - get past that firewall, try the - avoid-v4-udp-ports and - avoid-v6-udp-ports options to avoid - selecting random port numbers within a blocked - range. - - - If a port number (like 53) is specified via the - query-source or - query-source-v6 options in - /usr/local/etc/namedb/named.conf, - randomized - port selection will not be used. It is strongly - recommended that these options not be used to specify - fixed port numbers. - - - Congratulations, by the way. It is good practice to - read &man.sockstat.1; output and notice odd - things! - - - - - - The Sendmail daemon is - listening on port 587 as well as the standard port 25! - What is going on? - - - - Recent versions of Sendmail - support a mail submission feature that runs over port 587. - This is not yet widely supported, but is growing in - popularity. - - - - What is this UID 0 toor account? Have I been