I use the Gmail web interface (if at work). At home, I download it into
Outlook into its own folder (via a rule) and group by conversation. I also
keep the archive on Gmail (only been doing that since April, 2007). I have
Gmail taging this group as 'Midrange'.

On Jan 16, 2008 2:19 PM, Urbanek, Marty <Marty_Urbanek@xxxxxxxxxxxx> wrote:

Just curious how other members of this community read midrange-l, i.e.
by what mechanism do you read and post?

I have always used digest mode + plain text because I don't want to be
interrupted with email every two seconds and this combination lets me
quickly scroll to the posts I want to read. But lately, even digest mode
is becoming tough to keep up with.

Some people post [seems like] the entire history of the thread to which
they are replying, so today, for example, I am receiving a digest mode
email every 8 - 15 minutes and they only contain a few new messages
because some of the posts include so much history. I usually just post
one previous message (the one I am immediately replying to), but I can
see the logic in doing it the other way.

This isn't meant to be a criticism of anybody. I'm just wondering what
other people do to manage these messages so they can monitor the
discussions without making a full-time job of it.

Thanks,
-Marty
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].