Peter Galbraith <GalbraithP(_at_)dfo-mpo(_dot_)gc(_dot_)ca> writes:
Jon Steinhart <jon(_at_)fourwinds(_dot_)com> wrote:
If you decide to make these additions, keep in mind that they have to
be done in the send code, not in the whatnow code. This is because
the design of the attachment code was such that it would work
independent of the user interface. In particular, I know people who
have hacked mh-e to add attachment headers.
I'm sure Bill will chime-in here... MH-E now can use either mhn
attachment directives, or gnus directives. The Content-Type is (for the
most part) filled-in automatically using `file -i'.
Don't need to when the other MH-E developers do so for me ;-).
Note that MH-E calls mhbuild/mhn to expand the directives before
calling send. I haven't been following this discussion close enough to
know how that impacts the design.
p.s. We've started calling MH-E as such with all uppercase since
version 7.
--
Bill Wohler <wohler(_at_)newt(_dot_)com> http://www.newt.com/wohler/ GnuPG
ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
http://lists.nongnu.org/mailman/listinfo/nmh-workers