2 /****** BEGIN USER CONFIGURATION SECTION *****/
5 * IMPORTANT: You should no longer need to edit this file to handle
6 * your operating system. That should be handled and set correctly by
9 * These are slowly being phased out, but currently
10 * not everyone is auto-configured. Then decide if you
11 * wish to change the features that are compiled into nmh.
15 * If you have defined DOT_LOCKING, then the default is to
16 * place the lock files in the same directory as the file that
17 * is to be locked. Alternately, if you define LOCKDIR, you
18 * can specify that all lock files go in a specific directory.
19 * Don't define this unless you know you need it.
21 /* #define LOCKDIR "/usr/spool/locks" */
24 * Define this if your passwords are stored in some type of
25 * distributed name service, such as NIS, or NIS+.
30 * Directs nmh not to try and rewrite addresses
31 * to their official form. You probably don't
32 * want to change this without good reason.
37 * Define this if you do not want nmh to attach the local hostname
38 * to local addresses. You must also define DUMB. You probably
39 * don't need this unless you are behind a firewall.
41 /* #define REALLYDUMB 1 */
44 * Starting on January 1, 2000, some MUAs like ELM and Ultrix's DXmail started
45 * generated bad dates ("00" or "100" for the year). If this #define is active,
46 * we use windowing to correct those dates to what we presume to be the intended
47 * values. About the only time this could get us into trouble would be if a MUA
48 * was generating a year of "00" in 2001 or later, due to an unrelated bug. In
49 * this case we would "correct" the year to 2000, which could result in
50 * inaccurate bug reports against the offending MUA. A much more esoteric case
51 * in which you might not want to #define this would be if you were OCR'ing in
52 * old written correspondence and saving it in email format, and you had dates
55 #define FIX_NON_Y2K_COMPLIANT_MUA_DATES 1
58 * Directs inc/slocal to extract the envelope sender from "From "
59 * line. If inc/slocal is saving message to folder, then this
60 * sender information is then used to create a Return-Path
61 * header which is then added to the message.
66 * If defined, slocal will use `mbox' format when saving to
67 * your standard mail spool. If not defined, it will use
73 * Compile simple ftp client into mhshow/mhstore. This will be used by
74 * mhshow/mhstore for ftp access unless you have specified another access
75 * method in your .mh_profile or mhn.defaults. Use the "nmh-access-ftp"
76 * profile entry to override this. Check mhshow(1)/mhstore(1) man page
82 * Define to 1 if your vi has ATT bug, such that it returns
83 * non-zero exit codes on `pseudo-errors'.
88 /***** END USER CONFIGURATION SECTION *****/