The easiest way I see to accomplish what you want is to avoid Majordomo
entirely (although it would be a lot easier if you just moved the whole
works to a Mj list and not worried about the issue), and just install
demime as a front-end filter *before* the other list-management
program. (Demime is an excellent program written by Nick Simicich, and
is available at http://scifi.squawk.com/demime.html and some
open-source repositories.)
Using the mail alias feature of the mail server on the site that hosts
the list (e.g., /etc/aliases or /etc/mail/aliases for sendmail & UNIX),
make the list posting address a pipe (or equivalent mechanism) to
demime, which then delivers the message to the list-management program.
For a Majordomo list it's something like:
mylist: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper
resend -p bulk -M 10000 -l mylist -f mylist-owner -h myhost.com -s
mylist-outgoing'"
For a non-Majordomo list, it might be something like:
mylist: "|/usr/local/bin/demime mylist-post"
where "mylist-post" maps to the input of your list-management program
for the list "mylist".
--
Michael C. Berch
mcb@postmodern.com / mcb@greatcircle.com
On Apr 29, 2004, at 10:35 AM, lee wrote:
> hello everyone,
>
> with apologies for the off topic nature of this;
>
> i have a situation where one of my non-majordomo mail list managers
> has a problem (for the foreseeable duration) where it has to allow
> people to write posts in html, but the digest cannot handle such
> posts, resulting in a html mess.
> Now, I currently have access to an unused majordomo list circuit which
> I know has the html stripper patch successfully working on it.
> I would like to feed all posts sent to my other list into the
> majordomo one, thereby stripping the html, then 'invisibly' /
> 'semi-invisibly' send the resulting output to the other lists'
> subscribers, whether they be 'normal' or 'digest' subscribers.
> Do you get what I mean? So far, this appears impossible without
> creating a mail loop. I've tried various forwarding / subscription
> 'tricks' but to no avail.
>
> In case you're wondering, there are 2 or 3 reasons why I need to stay
> 'centrally' with the faulty list, rather than just move everything
> (temporarily) over to the majordomo list.
>
> Any wisdom appreciated !
>
> (i also have access to Mailman, not that that seems to be of help in
> this scenario)
>
> lee
>
References:
|
|
