Introduce a NormalDomain newtype to ensure comparisons are made safely.

[list-remote-forwards.git] / list-remote-forwards.cabal

diff --git a/list-remote-forwards.cabal b/list-remote-forwards.cabal
index 4718b35534331b0a5bd58ca1f9d54a44a1126cc7..ba8ffa4ebba7f250517448acf281725e45299eab 100644 (file)
--- a/list-remote-forwards.cabal
+++ b/list-remote-forwards.cabal
@@ -79,11 +79,14 @@ description:
   The name of a mail exchanger, the forwards of whose domains we should
   ignore. For example, if one mail exchanger, mx1.example.com, has
   strict spam filtering, it may be acceptable to have remote forwarding
-  for domains that have mx1.example.com as their mail exchanger (MX
+  for domains that have mx1.example.com as their sole mail exchanger (MX
   record). In that case, you might want to exclude those domains from
   the report by naming mx1.example.com here.
   .
-  Can be repeated to exclude more than one mail exchanger.
+  A forward will be excluded from the report only if /all/ of its MX
+  records are contained in the given exclude list.
+  .
+  This option can be repeated to add mail exchangers to the exclude list.
   .
   Default: [] (empty)
   .
@@ -133,7 +136,7 @@ description:
   /Examples/:
   .
   @
-  $ list-remote-forwards --database=postfixadmin.sqlite3
+  $ list-remote-forwards --database=test/fixtures/postfixadmin.sqlite3
   user1@example.com -> user1@example.net
   user2@example.com -> user1@example.org
   user2@example.com -> user2@example.org
@@ -168,9 +171,11 @@ executable list-remote-forwards
     Configuration
     CommandLine
     DNS
+    Forward
     OptionalConfiguration
     MxList
     Report
+    String
 
   ghc-options:
     -Wall