NOTE: for users of the online version of this book: This section has a lot of examples followed by long explanations. To avoid jumping between the example and its explanation, it's a good idea to open a new browser window to show an example. (Check your browser's menu for a command like New Web Browser or Open in New Window). Then, use the original browser to read the explanation while you view the example in the second browser window.
In most cases, your computer's MTA (see the Section How UNIX Email Works) has to be told to read your .maildelivery file. The list below explains what to do for common transfer agents. If you aren't sure what MTA is running on your system, ask your postmaster -- or read your system's online mhook(1) manual page; it should have been customized automatically for your configuration when MH was installed.
"| /x/y/lib/mh/slocal -user username"where /x/y is the start of the path to the MH library directory where slocal is stored on your computer and username is your username. This command sends all your incoming mail through the slocal program.
Your .forward file should be owned and writable only by you. (Use the command chmod 644 or chmod 600.)
% ln /x/y/lib/slocal rcvmailIf slocal and your bin directory are on different filsystems, a standard hard link won't work. You'll need to make a symbolic link (the ln -s option).
Here's one more note. At least some MH systems won't run your .maildelivery file unless the mode is 644 -- other users can't edit the file. Even if that isn't required, it's a good idea.
[Table of Contents] [Index] [Previous: The .maildelivery File in Detail] [Next: Experimenting? Make Backups!]
This file is from the third edition of the book MH & xmh: Email for Users & Programmers, ISBN 1-56592-093-7, by Jerry Peek. Copyright © 1991, 1992, 1995 by O'Reilly & Associates, Inc. This file is freely-available; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation. For more information, see the file copying.htm.
Suggestions are welcome: Jerry Peek <email@example.com>