-d69 Queue scheduling.
-d70 Queue quarantining.
-d71 Milter quarantine on errors.
-d72 Unused.
-d73 Queue shared memory updates.
-d74 Unused.
-d75 Unused.
-d76 Unused.
-d77 Unused.
-d78 Unused.
-d79 Unused.
-d80 Trace Content-Length: header (Sun version).
-d81 Trace > option for remote mode (Sun version).
-d82 Unused.
-d83 Collection timeout.
-d84 Delivery timeout.
-d85 The internal dprintf database map.
-d86 Unused.
-d87 Unused.
-d88 Unused.
-d89 Unused.
Table 15-3. Debugging switches by category (continued)
Category Description
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
15.6 Pitfalls | 539
15.6 Pitfalls
??? It is best to debug sendmail in a window environment, within script(1), with
emacs(1), or something similar. Debugging output can run to many screens.
??? Sometimes debugging output seems not to be printed:
% /usr/sbin/sendmail -d11.1 you < /dev/null
%
When this happens, add the -v command-line switchto keep the output
attached to your screen:
% /usr/sbin/sendmail -v -d11.1 you < /dev/null
?†? many lines of output here
%
??? There must be no space between the -d and its numeric arguments. If you put
space there, the numeric arguments might be interpreted as recipient addresses.
??? There is no way to isolate a single category and level.
Pages:
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957