Hi there!
On 30 Nov 99, at 16:09, Douglas Hinds wrote
about "Re[2]: Activating only certain filt":
> Monday, November 29, 1999, 9:05:57 AM, Alexander wrote in response to
> my saying:
>
> AVK> 1. Managing the Inbox. What essentially is done to my Inbox in
> AVK> Pegasus? On every _opening_, the messages get filtered from
> AVK> it to the \Unread\... hierarchy.
>
> Is this the inbox itself for each account? Hierarchy here represents a
> folder? Reading below, perhaps you mean a color.
In Pegasus, all the new mail arrives to *one* Inbox (Pegasus
calls it "New mail folder"), provided that you install the program
as single-user and use identities under this single user (this is
how I run Pegasus).
As for "hierarchy", here it represents the set of folders, like:
\Unread\TBUDL;
\Unread\TBBeta;
\unread\Work\Similarity problem;
etc., etc.
The major part of my everyday traffic is moved from Inbox to
these folders automatically, so that I never see it in Inbox. The
rest of the messages (i.e. the messages that remain in the
Inbox) are coloured into various colours of the rainbow:-)
Delivery confirmations are made pale gray; the messages from
my ISP are made bright green, etc., etc:-)
> AVK> This can be implemented with TB all right. But then, on _closing_
> AVK> of Inbox, *some* messages get filtered to the other folders as
> AVK> well (such as delivery confirmations, messages from my ISP, etc.
>
> AVK> The crux of the matter here is that I usually just need to *see*
> AVK> them, but don't need to read these, at least on the regular
> AVK> basis).
>
> I assume you just need to see the information given on your columns
> bar. In that case, your needs seem similar to mine.
Yes, but this applies only to a special fraction of my traffic (the
"technical" messages mostly, i.e. the messages that I just want
to know they exist:-) but needn't read...)
> AVK> In TB this part cannot be implemented, therefore one would need
> AVK> to implement this part as "Read" type filters. But then I would
> AVK> *have* to open *each* of the delivery confirmations to get them
> AVK> filtered where I want them to go to, which isn't the thing I
> AVK> would like to do...
>
> Once again, our reactions are similar. Doing that would be excessively
> burdensome and time consuming, inefficient and impractical.
That's it.
> AVK> In many cases, it's quite enough to *look* at the delivery conf
> AVK> in the folder listing to say, where it came from and what does
> AVK> this all mean.
>
> Particularly if it came in on a list.
Yes, but then all the delivery confirmations can be separated
from the "valuable" traffic. I usually filter on "daemon" and "mail
delivery" strings in the sender... That does the trick.
> AVK> Following this idea, in Pegasus I have set up a filter that
> AVK> *automatically* marks all the delivery-type messages with pale
> AVK> gray colour in the Inbox, so that I could just skip these
> AVK> messages... TB's filtering won't allow me this, too.
>
> I would think that Pegasus is *the* email client with which TB must
> compete (not an easy task, given Pegasus' price),
:-)))
> since the Pegasus user base is probably the group most like
> TB's own.
Wrong here. Pegasus is much a Netware-oriented package,
offering *real lot* of extra functionality under Netware. Then, it
has excellent network support (can be installed on the server
side, users logging in from the client machines, and this type of
functionality is refined all the time). All this results in the
situation when Pegasus is used on *large* LANs (AFAIK, on
Pegasus mailing list we have 30+ postmasters of 1500+ user
LANs), whilst TB with its current functionality is mainly a single-
user or family application (remember the addressbooks wisible
for ALL the users:-))
>From what I heard I assume that RIT labs are mainly aimed at
competing with Eudora (and here luck can and must be on TB's
side:-)) given the Eudora's quality...)
> In my case, Pegasus has performed erratically on my system
Just curious, how?
> have poor customer service), but TB needs some polishing, to
> go along w some very solid basic and advanced functions.
That's my point, too.
> TB, the bloated Netscape (and a number of others I've removed) just
> open and run w/o problems, but I was discussing last night the absence
> of *any* way to flag messages in TB
Well, in Pegasus one's got "quick folders" feature:-) That is, a
single key-combo moves the current message to a pre-defined
(by the user) folder. Up to 9 quick folders supported.
<snipped the rest, since we're apparently thinking similarly...>
> Thank you for the detailed explanation. While I can see and
> appreciate your point, I feel committed to TB and enjoy using it
> in many ways that Pegasus never achieved for me. (In fact,
> Pegasus has never run problem free for me). TB is excellent for
> composition it and it's also very stable.
Actually, TB currently:
1. Doesn't support the features I use every now and then (for
example, advanced MIME functionality like attaching *multiple*
messages to a message, creating/reading MIME digests, etc.);
2. Has nontheless numerous bugs in its very basic functionality.
That's IMHO, of course:-)
SY, Alex
(St.Petersburg, Russia)
--
Thought for the day:
Backup not found: (A)bort (R)etry (P)anic
---
PGP public keys on keyservers:
0xA2194BF9 (RSA); 0x214135A2 (DH/DSS)
fingerprints:
F222 4AEF EC9F 5FA6 7515 910A 2429 9CB1 (RSA)
A677 81C9 48CF 16D1 B589 9D33 E7D5 675F 2141 35A2 (DH/DSS)
---
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
