Jos Vos <jos(_at_)xos(_dot_)nl> writes:
- One mostly uses only one MUA. If you want to use more packages,
you might want to configure it differently.
...mainly because I want to treat WWW-data as more insecure
One uses mostly one MUA yes, but not exclusively one MUA. In
addition, there are other packages such as web browsers and news
readers which can also take advantage of a single mailcap file.
Security-wise, I wouldn't differentiate between any of these
packages. You're either secure on all fronts, or you're not secure
at all.
- The mhn_defaults file offers more than mailcap does (correct me if
I'm wrong). It manages also storing messages and more.
I'm more familiar with mhn_defaults, but from what I remember of
mailcap, it seems that they are fairly similar and I'd imagine that
the mhn extensions (to store messages) could be added to an existing
mailcap file without breaking other applications.
In the long run, current implementation details aside, having a
single configuration file to map content types to applications makes
sense. You also bring up a good point that personal configuration
files should also be available (currently, this is usually the case).
Bill Wohler <wohler(_at_)newt(_dot_)com> ph: +1-415-854-1857 fax:
+1-415-854-3195
Say it with MIME. Maintainer of comp.mail.mh and news.software.nn FAQs.
If you're passed on the right, you're in the wrong lane.