Re: [AOLSERVER] [ aolserver-Support Requests-429141 ] help w/data

2001-06-03 Thread Jim Wilcoxson

I have a suggestion: these Source Forge cc's to the mailing list are kinda
nice in that it connects the two forms of communication and helps keep the
community tied together.

But would it be possible to either:

a) only post the new responses to the non-digest mailing list, or
b) only post updated items on the digest mailing list, or
c) show the latest update at the beginning of the message

It gets old seeing the same thing come across the mailing list over and
over, to the point where I'm about ready to disable them.

Jim


 Support Requests item #429141, was updated on 2001-05-31 13:48
 You can respond by visiting:
 http://sourceforge.net/tracker/?func=detailatid=203152aid=429141group_id=3152

 Category: Configuration: Database
 Group: aolserver3_4
 Status: Open
 Priority: 5
 Submitted By: Tyge Cawthon (tyge)
 Assigned to: Dossy Shiobara (dossy)
 Summary: help w/data from AOL into Postgresql

 Initial Comment:
 I have done a lot of reading and I am stuck.
 I would appreciate any help.

...



Re: [AOLSERVER] [ aolserver-Support Requests-429141 ] help w/data

2001-06-03 Thread Tom Ivar Helbekkmo

Dossy [EMAIL PROTECTED] writes:

 d) Create seperate mailing lists for the different trackers.

Very good idea.

 In the meantime, I suggest that you may want to investigate how
 to create filtering rules within your email client (or mail
 transport agent) to put messages that match the expression
 [ aolserver-.*-[0-9]* ] in the Subject: header into a seperate
 mail folder, so you won't be bothered by them (and can check them
 when you feel like it).

Or, even better, filter on Sender: [EMAIL PROTECTED]
and From: [EMAIL PROTECTED] in combination, which uniquely
identifies the email item as machine generated at SourceForge for the
AOLserver project.  This means that you can dump the actual log
entries from SourceForge into a seldom viewed folder, but followup
discussion on the mailing list, triggered by the SourceForge posting,
will not be filtered away.

[On a related note, there's a popular misconception that it's only the
Subject: header that can be used for filtering.  Thus, you have lots
of mailing lists that uselessly add the name of the list to the front
of the subject, cluttering up the mail reader user interface with
unneeded meta-information.  Anything and everything can filter mail
these days (and if your email user agent or storage system can't, then
you can slip in something in front of them, like procmail), and they
can all filter on any header fields, not just the subject.  Of course,
the information about what list the item came from is available in
other header fields, so the Subject: mungeing is superfluous.]

-tih
--
The basic difference is this: hackers build things, crackers break them.