Hi!
I think that it would be better, if Earl could set in
Mhonarc by default that it would divide messages by months, and years (into
separate folders/pages).
At present I don't know how to do it, and surveying the documentation I haven't
found a simple answer, yet.
Could you help me,
I have successfully built an index sorted by author using the Otherindex
feature, when running from the command line. But when I make the same call
from within a Perl script invoked by procmail, the index gets screwed up.
Names are not sorted correctly, as indicated in:
It seems like every so often somebody asks a question like this.
Unfortunately the examples given on the Mhonarc web page are exceedingly
obscure. They seem to be pitched to people who have an advanced
understanding of Unix and inter-process communications. I have only been
working with Unix (Aix
At 01:37 PM 11/4/99 +0100, Andrzej Kasperowicz wrote:
Mails from the file which I saved from the pegasus mail folder do not want
to
be processed by mhonarc like separate mails, but as a one mail. Why? What
to do about that?
You can have a look at that there:
On 11/4/99 at 1:39 PM, [EMAIL PROTECTED] (Andrzej Kasperowicz)
wrote:
I think that it would be better, if Earl could set in Mhonarc by
default that it would divide messages by months, and years (into
separate folders/pages).
One reason I wouldn't want this to happen is that people seem to
On 11/4/99 at 1:37 PM, [EMAIL PROTECTED] (Andrzej Kasperowicz)
wrote:
Mails from the file which I saved from the pegasus mail folder do not
want to be processed by mhonarc like separate mails, but as a one
mail. Why? What to do about that?
Check the MSGSEP resource as Al suggests, but I've
On 11/4/99 at 9:50 AM, [EMAIL PROTECTED] (Louis Proyect) wrote:
Furthermore, the script does not address itself to date anomalies
which are crucial for proper archiving. My mailing list has some
messages that, for example, are dated Oct 31, but are filtered into
the November archive--only
Check the MSGSEP resource as Al suggests, but I've never used Pegasus
mail -- does it store files in mbox format, like Pine or Eudora? if
MSGSEP doesn't help you, try posting two consecutive raw messages from
your datastore to the list.
You can have a look at this messages saved from
Check the MSGSEP resource as Al suggests, but I've never used Pegasus
mail -- does it store files in mbox format, like Pine or Eudora? if
MSGSEP doesn't help you, try posting two consecutive raw messages from
your datastore to the list.
The latest versions of Pegasus *can* store
On 11/4/99 at 1:02 PM, [EMAIL PROTECTED] (Louis Proyect) wrote:
As I just a moment ago mentioned to Andrzej, if you want to get
clever about interpreting date headers in your mailbox-assignment
scripts, you're inheriting the responsibility to reject those date
headers which are wildly wrong.
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
sent.
On November 4, 1999 at 12:34, Nathaniel Irons wrote:
I tend to think that the most current information should load first, and
be at the top of the page.
I have no problem with that. The main link you provide to the
archive can always point to last page of the index initially.
Some uses a
On November 4, 1999 at 16:04, Nathaniel Irons wrote:
So Joe User turns the clock back a year on his PC, to get around an
expiration date on some software package he wants to use, and forgets to
reset the clock when he's done. Then he sends your mailing list a
message, timestamped as it
13 matches
Mail list logo
