As some of you may have heard and noticed, the MHonArc mailing list is
now being run at NCSA. Over the past few years Achim Bohnet has done
a tremendous job in providing this invaluable resource to the MHonArc
community; I only hope that I can continue his high standards and
dedication.
The list
In response to the recent influx of spam on the list, I've gone ahead and
wrapped the installation on our servers with a set of procmail recipes
that should catch most known spam and/or spam patterns.
This shouldn't affect list performance in any way (other than receiving
less spam through it), a
After talking to Earl about the growing spam problem we have decided that
it is better to leave the list closed to subscribers. Non-subscribers
will still be able to post, but their messages will need to be approved
by the listowner.
Unfortunately, this change won't take place until Aug. 17th, a
Well, we've been moderately successful in our anti-spam tactics
for the MHonArc mailing list. Believe it or not, we've been
trapping about 50% of the junk that comes in.
Unfortunately, it's still not good enough though. I know that you've
all been getting sick and tired of this type of mail pro
Does MHonArc do any kind of testing for directory permissions before
doing anything?
I'm asking because I recently set up some archives using v2.2.0
in AFS. AFS totally ignores the 'og' settings for files and
directories when it comes to permissions because it uses its
own authentication scheme
> So before I put it on top of my TODO list ...
>
> Has anybody tried to patch mhonarc to use the msgid for the name of
> file instead of the sequential numbering? So files
>
> Earl, does it make sense to make this bigger extention for mhonarc v2?
> Or should one better wait and hack an alpha o
> But wait I just realized that I jumpedto fast into an implementation
> issue. What I would really like to have is
>
> o ARI (Archive Msg Identifier)
> o extention to mhonarc to use the $w3archive/$ARI instead of
> $w3archive/my-substruct/{msg*.html,ext*.ext}
> o ARI -> filename tran
> MHonArc adding IDs will not help duplicate message checking. It helps in
> other ways.
Yes, I don't know what I was thinking... One of those days where everything
that I post doesn't quite make sense... :)
> Something like FROMFIELDS can be done. However, I will need more
> information on
>Now, I've gone through the archives (still wading through them, so
> I may have missed something, of course), and I see references to wilma and
> how it will provide an 'index.html' front end that divides things up by
> month. Great for the end-users looking at it, but, and unless I'm missin
> Not knowing Glimpse yet, I'm not sure how it works. However, if a search
> index (not the mhonarc index) only has to be added to rather than
> re-created, the process would seem more efficient. Mhonarc can add on the
> fly, why not a search tool? Just a thought.
Glimpse has this functionality,
> We'd like to hide any e-mail addresses to avoid robots to collect them.
> Using the resource does not exactly what we want, because it
> generates no link to e-mails, but you will still find them in the html
> source. I have tried to replace all @ symbols with something else like #
> in the inb
> Now sometimes that results in what was msg00587.html to turn into
> msg00560.html. Not a big deal, except that it might leave a dozen
> major internet search engines (and my little minor search engine) with
> a bad idea of what is where, at least until the pages can be
> re-indexed.
>
> So, one
> However, I wonder about the MD5 method. Without knowing anything
> about MD5, could it work with 8.3 filenames? I buid my archives on a
> DOS box, so am constrained to that format.
Hi Claire,
I'm embarassed to admit that it doesn't fall into 8.3 filename
scheme. It's probably one of
> I'm running Majordomo and qmail together and I'm looking for a nice way to
> publish my list archives on the web.
>
> I can get MHonarc to add them to an archive as they arrive, but as far as
> I can see this will put all mail for the list into one huge archive.
> Alternatively I could run MHon
> > If using v2.3 (in beta), you can use -nolock if you are using a
> > pre-filter like Procmail. I.e. You can use Procmail's locking
> > capabilities to insure single process access to the archive. I would
> > guess that Procmail's locking mechanism is more robust than MHonArc's.
>
> Have you
> Solutions can vary depending on what kind of access you have to your
> newserver. If you are the administrator, you can probably have MHonArc
> process the directories the news server stores articles in directly.
> Many servers store articles in a directoy structure that mirrors
> newsgroup nam
> Subscribers who don't want their messages to be archived
> could add a "no archive" flag within their mail.
The most common way to do this is by checking for the existence
of an 'X-no-archive: yes' or 'Restrict: no-external-archive' header.
> As I'm invoking MHonArc through a procmail recipe I
> Looking at the source of the 1.32 version I have here, I do not see any
> support for such field...
No. You can preprocess with procmail though:
# If people don't want to be archived, then remove their
# message
:0
* ^(X-no-archive: yes|Restrict: no-external-archive)
/dev
This message is just a reminder to all of you about the member-only
posting restriction on this list. We were getting so much spam
through to the list that this was the only viable solution to keep
everyone on track.
Unfortunately, it also means that posts from non-members may not
be received in
>Is there a certain way to have the X-sender-Ip show up
> when changing the mail to HTML format ? Right now it seems to
> be stripping that header.
You need to change the EXCS resource. Right now the default is
to strip out all X- headers. Instead change your resource to
something like
> > And your Glimpse version is? Versions after 3.6 have serious problems with
> > incremental indexing, which is why we tell you not to use them. I use 3.0
> > myself.
> >
>
> Glimpse 4.1; I thought I'd read somewhere that that version was OK.
> I'll try to find version 3.0 and revert to it
> Help!
>
> Files attached to email notes are overwriting each other. I tried Earl's
> suggestion in:
> http://www.xray.mpe.mpg.de/mailing-lists/mhonarc/1998-12/msg5.html
> but it's not working.
>
> I'm using MHonArc version 2.2.0. Enclosed is my resource file below, and
> here is the c
> Someone could help me debugging this problem ?
>
> Mar 9 16:37:51 armstrong sendmail[11796]: QAA11794:
> to="|/usr/majordomo/wrapper mhonarc -idxfname
> index.html -add -outdir /home/httpd/html/my-rep/", delay=00:00:00,
> xdelay=00:00:00,
> mailer=prog, stat=Operating system error: Error 0
>
> "Here is a template for archiving messages as they arrive for a
> Majordomo list to include in sendmail's aliases file:
>
> :"|/usr/lib/majordomo/wrapper resend -l
> -outgoing"
> -outgoing: :include:/var/lib/majordomo/lists/,
> -mhonarc
> -req
> I am using Mhonarc to archive a mail list. The current archive is now 5000
> messages.
>
> First, I was wondering if there is a practical limit to the size
> of an archive mhonarc can handle (for performance reasons mainly).
It all depends on how long your users are willing to wait when they
> > Anyone got a good way of dealing with Netscape generated mail that has
> > text/x-vcard attachments (Virtual Card).
There's a snippet of perl code that you can run to strip vcard attachments.
It was discussed on the procmail mailing list (no, procmail is not
necessary to use it), so you ca
> is there a way to have messages end in .shtml so that they can be processed
> as a ssi? also is it possible to change the default (maillist.html) to
> index.shtml?
Hi Mark,
Check out the HTMLEXT resource. i.e,
shtml
And from the documentation:
"WARNING! The
> I'm still getting an error in my procmail.log:
>
> ERROR: Unable to create =
> /home/www/rcairplanes/archives/nsrca//.mhonarc.lck after 10 tries
> procmail: Error while writing to "mhonarc"
> procmail: Program failure (75) of "mhonarc"
>
> There isn't a retained .lck file in that directory.
> PD: I use X-Mailing-List header in the recipe, but that´s
> something I would like people comment on. Maybe Resent-From ?
I'm going to turn this into another procmail mailing list... :)
I've found that X-Mailing-List: doesn't always exist; sometimes
it's From_, Sender:, or Delivered-To: that I
> What's wrong with doing a a little post processing of the archive?
>
> E.g., put a comment like:
>
>
>
> in the resource section you want it to be. Then do a scan and replace
> script to insert the file. Probably about 20-50 line of perl (with
> comments). You might want to think abo
> The Content-Disposition setting takes precedence over what arguments
> are specified for the filter. The "inline" option tells the filter
> how to treat the graphic if no Content-Disposition is specified.
> In sum, if the Content-Disposition states the data as an "attachment",
> then only a lin
> I'm trying to improve the speed at which Wilma indexes. Right now the real
> bottleneck is that we pass every MHonArc-generated page through the
> striphtml program, which is written in Perl. The time to load the Perl
> interpreter tens or hundred of thousands of times is pretty harsh, and
> o
> How would you highlight new mail in the index files for the archive (with
> little GIFs, say, or differently coloured text)? (When I say "new", I mean
> mail that's arrived in the last 24 hours, for example.)
You'd have to write a CGI script that "wraps" the HTML indexes produced by
MHonArc, un
> I am not sure if MHonArc has this functionality, but a nice little shell
> script command to get around this is "touch". If you run MHonArc from a
> shell script(or at or cron, whatever) you could throwin two(one) line
> beforehand saying touch /maillist.html
> /threads.html
Some browsers will
> I tried to invoke mhonarc through .procmailrc as soon as a new
> message comes from a mailing list in but I can not get it done. Below
> is my .procmailrc. Only the last four paragraps refer to the invoke
> command. I tried various possibilities but not one to them worked.
> Below I copied m
> :0: microempresa.lock
> * ^[EMAIL PROTECTED]
> | /usr/www/users/galileo/cgi-local/mha/mhonarc -add -nolock -nodoc \
> -rcfile /usr/www/users/galileo/cgi-local/mha/rcfile4 \
> -outdir /usr/www/users/galileo/intercam/listas-html/microempresa
>
> But in the above example, where does mhonarc the
> I want to restrict MhOnarc mailing list archive to list subscribers.
> Is any one of you did it ?
MHonArc doesn't have any builtin support for access control, but your
web server probably does. It all depends on what kind of access control
lists your server users. If using Apache, you can
> I am running Mhonarc 2.1.2 on a Sparc 20 running Solaris 2.5.1.
> I have an archive that currently has 3416 messages. I went to add some
> more messages and I eventually recieved an Out of Memory error.
>
> Any suggesttions?
Have you tried the -savemem option?
-savemem
> It seems that mhonarc will try lines start with "From " as a new
> message, is it possible to make mhonarc to identify which "From "
> is start of new message and which is not?
I think this is in the FAQ. Take a look at the MsgSep
resource (i.e
^From \S+\s+\S+\s+\S+\s+\d+\s+\d+:\d+:\d
> MHonArc, I'm discovering, is a rich and fabulous tool for generating and
> making archives, but it apparently lacks this additional component of
> selectivity. I'd like to help fill that gap, and to that end, I'd like to
> know if I need to start from scratch, or if I'd be well-served to build
> with UMASK 0 -> rw- instead of rwx
> 1 -> rw- ok
> 2 -> r-- instead of r-x
> 3 -> r-- ok
> 4 -> -w- instead of -wx
> 5 -> -w- ok
> 6 -> --- instead of --x
> 7 -> --- ok
>
> am i wrong about what UMASK does ?
Yes. In most Unices UMASK(2) wi
> Anyone successfully have mailman and mhonarc setup?
> Any info about doing it would be appreciated.
Yup, but it's a hack. The longterm goal is to patch mailman
to allow *any* outside archival program to be executed instead
of pipermail, but for now I just subscribe an archiving
account to the
> >Are *.alt.perl plain files? If so, I would guess that the default MSGSEP
> >resource does not work for them. What does a *.alt.perl file look like?
>
> they are plain files gotten by "suck" here is one of the files, though not
> *.alt.perl (as MHonArc did get done processing them finally) I
> Does anyone have a fix to a problem which has long plagued me, namely,
> that when one searches one's mail archives with marc-search.cgi, using the
> "find all of these words" (boolean AND) option, one is only returned
> messages which match all the words ON A SINGLE LINE. This is extremely
> m
> I don't know much about march-search, but the default in glimpse is to
> do exactly what you say. However, glimpse 4.0 (don't know about 3.6)
> allows the entire body to be searched by adding the -W flag. From
> GLIMPSE(l):
>
> So if you can find the glimpse commandline arguments, adding -W
>
> So, the mailer inserted a '>' before the 'From' in the body of the message;
> just thought to explain this, otherwise my previous message doesn't make
> much sense. Cheers,
Well, I was going to say that you should take a look at the
resource which sets a regular expression that must be matche
> This will not matter either, unless mhonarc is being invoked incorrectly.
> If piping stdin and using -add in a alias, mhonarc treats the data
> as a single message, so MSGSEP is not used. However, if you put
> " -- - " as mhonarc arguments, then you may have problems.
OK, you learn something
> > However, one can add a Content-Length: header with everyone's favorite
> > tool, procmail. :) Here's a recipe borrowed from David Tamkin about
> > 9 moons ago:
> >
> > :0fhw # B won't help; size conditions ignore H and B flags on the :0 line
> > * ! ^Content-Length:.*[0-9]
> > * 1^1 B
> Sadly not -
>
> >From MAILER-DAEMON Mon Jul 19 13:22:20 1999
> Date: Mon, 19 Jul 1999 13:22:20 +0100 (BST)
> From: Mail System Internal Data <[EMAIL PROTECTED]>
> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
> X-IMAP: 0932386940 00
> Status: RO
>
> This text is part of t
> Would it be possible to notify a subscriber everytime he/she sends a
> message to a mailinglist, indicating where his/her message was
> published by Mhonarc on the web?
>
> Any ideas would be highly appreciated!
The only method that I can think of is to extract the Message-Id: header
from th
I've had a couple of requests over the past few months to prepend a
list identifier to the Subject: header on messages sent through
the list to aid in filtering and identification.
Consequently, some time after 5:00pm on Thursday, August 12th (those
times are US/Central) all messages will have [M
I've received a lot of messages from people against the planned Subject:
line tagging for the MHonArc mailing list. Consequently, I haven't
enabled this feature for the list yet.
I would like to hear from those who are in favor of this change,
accompanied by an explanation or description of nee
> I am looking for any input to the matter of running MHonArc and Frontpage
> Extensions on the same server. Has anyone had problems doing this ?
What OS for the server -- Unix or NT? And what server is being used?
I'm using Apache 1.3.9 (the pre-release) with FrontPage extensions under
Linux a
> For those who set up their archives to mask out addresses, you
> should also make sure that the .mhonarc.db file cannot be
> accessed since it will contain address information. If you are
> using Apache, add the following to your httpd.conf:
>
>
> Order allow,deny
> Deny from all
>
> >Can anyone enlighten me as to why I am getting this error?. I use a
> >template for my archives, so that all I change is the name of the list
> >and plug it in to the template. All permissions seem to be correct. The
> >message is being delivered to the list, but not to the archive.
>
> He
Recently people have been reporting breakages in various software packages
when the 'From ' line contains a quoted address with spaces. By
default MHonArc is OK, but the suggested extended MSGSEP declaration
in the documentation will break in this type of situation.
This should work in that type
> When MHonArc encounters a message w/o an ID, it internally creates its
> own ID. ... Including the body as part
> of the MD5 sum would provide better chance of uniqeness, but would
> require code restructuring (and a performance penalty) for questionable
> gain.
Cool. So if you're having probl
> You can just grep it out, or if you're worried about snagging one
> in the message body for whatever reason, this procmail recipe will
> remove a Message-Id: header (formail auto-generates one):
>
>:0 fhw
>| formail -I "Message-Id:"
Gack. formail only auto-generates one if you do
Just a little buglet...
mx1 329% mhonarc -afs -outdir ./oct99 .mbox/oct99
ERROR: "oct99" is not readable
mx1 330% ls -ld oct99
drwx-- 2 80 202 2048 Oct 21 15:22 oct99
mx1 331% touch oct99/hi ; rm oct99/hi
mx1 332% chmod a+rwx oct99
mx1 333% mhonarc -afs -
> Your script, as written, will dutifully extract the date header, parse
> it, and spool to the wrong directory, because you relied on bad data.
>
> In virtually all cases, it's easier, safer, and more accurate to store
> messages based on the time they arrive, not when they say they were
> sen
> We recently set up several email archives using mhonarc 2.4.4.
>
> The result looks fine, except that it is displayed in
> chronological order (oldest mail appears on the top) and has no
>
> date stamp. Is it possible to have the latest first with a date stamp?
> (two separate items). Thank
> I've gotten wilma/glimpse/mhonarc running on my home web server, and I
> ran into a problem with glimpse noted in the wilma documentation:
>
> "Version 3.6 is recommended because version 4 of glimpse is broken
> in that it corrupts the index when doing incremental additions."
>
> For now I'm d
> It appears that Excite is the problem. So, are there any good suggestions
> about what index/search software to use for a Solaris 2.7 platform? I am
> using Majordomo and I understand that Wilma is available to interface
> Majordomo with Glimpse. However, I also understood that the newer version
> While all is clear with using Mhonarc itself, there is the quesion how
> to convert news data into mail data. The only package I could find was
> a pretty old Mail2News script written by Rich Salz (The creator of
> the INN).
>
> We want to make the archives directly on the server, by accessing
> We have INN 2.x - that should work.
Sorry about the delayed response... Playing catch-up today.
> > We lost our feed and our ISP won't let us do anything through
> >inn -- we need to use suck or something (which I don't want to
>
> Hm, I think we have at least some of that bu
> This looks alot like something I've wanted to do, and tinkered with
> for a while.
>
> Sorry for being dense here but it isn't clear to my inexperienced eye
> how the news messages are coming in to be redirected to procmail.
Unfortunately, this is only a server-based (INN) approach.
I'll wo
> Somewhere I got the idea that the hallmark 'From ' line and space at
> the end that are the earmarks of unix-message format, were required
> for procmail to work. Is this not the case? Still haven't had a
> chance to experiment to find out for sure.
You really only need the "From " line if yo
I have a bunch of archives that get updated via this command:
mhonarc -nolock -nomodtime -add -umask -rcfile rc -outdir [outputdirectory]
This is piped into the archive with each incoming message via procmail
(which does global locking of its own).
Sometimes on unusally high traffic lists t
> >mhonarc -nolock -nomodtime -add -umask -rcfile rc -outdir [outputdirectory
> > ]
> I'm guessing the problem has to do with the index pages getting
> corrupted and important comment declarations are getting lost.
> Unlike thread index pages, main index pages are edited and not
> overwritten
> >From the cases before, the problem was that the comment declarations
> were not present in the pages, so mhonarc ends up "preserving" the
> entire previous index page instead of just HEADER. From looking
> at the code, I fail to see where the error is. Maybe there is
> some querky file flushi
> > Uh? So what exactly can you do with your MHonArc message files with
> > these tools that you couldn't do with a simple update query in SQL
> > server?
>
> Full text search indexing. Many indexing tools work best with regular
> files on not with data in a database, especially the free ones.
> > I'm having problems with the main index page of new archives that I
> > create. The index just keeps adding another full page to itself after
> > each message is received.
>
> > I have tried rebuilding the archive with:
> >
> > /usr/local/bin/mhonarc -rcfile
> > /export/home2/www/wwwdev/mhon
72 matches
Mail list logo
