Hi there!

On 5 Jan 00, at 14:14, Steve Lamb wrote
    about "Re: Pegasus vs. The Bat!":

> > Seems that the two things that you call "multiple accounts" and "multiple
> > instances" differ only when the folder structure is concerned.
> 
>     No, there is a lot more to it than that.

Having read this message of yours, I still don't see other differences...

> > At least, in the case of Pegasus. In PMail, two identities may happily have
> > absolutely different settings (*all* settings), *but* they always share the
> > same Inbox, same Outbox, same Trash and same Sent folders.
> 
>     This is "personalities" (Eudora/Lookout! term).  It is not a separate
> account since the mail does not come in separately.  It is all mixed in and
> jumbled together, requiring the user to build filters just to keep it
> separate.  This is a very undesirable position to be in.

For you, but not for me. I'm filtering all the input stream anyway, and BTW I 
*do* know that *no* message from my scientific supervisor should go to the 
"Personal" folders. But note, that my supervisor knows all 5 of my e-mail 
addresses and (probably, arbitrary:-)) selects between them. This means, that 
in the case of TB I would inevitably face the following situation:

5 accounts (one for each of my e-mail addresses, since its all different dial-
ups:-)), and into *each* of these 5 inboxes messages from my supervisor are 
likely to find their way. And now what? Now, obviously, I'll need to get the 
messages coming from [EMAIL PROTECTED] (the address has 
been altered) and from his another address into *one* place (logical, yeah?). 
This would in turn mean that I'll need even more a complicated filter structure 
(with multi-account filtering) then what I've got in Pegasus right now.

I've got a couple of another exampes that bring *me* to a conclusion that 
"identities" is more suitable for me then TB's "separate accounting".

Finally, now suppose that I *have* some need in separating one of accounts 
from the other ones (much the way you've described). It's not a problem in 
Pegasus, too. I'll then add another user (say, "Separate me":-)). Then, since 
this is a *user*, not identity, the corresponding tray structure will be absolutely 
separate from all the other accounts. After that, I'll log into Pegasus as always, 
_attach_ the mailbox of the user "Separate me" to the list of folders of the 
"Regular User" (which would give *absolutely the same situation* one has with 
TB!, and even the folder structure would look the same), and voila! From now 
on, whenever I check the mail, Pegasus will check the mail for *both* users, 
and the mail for "Separate me" will NOT be mixed with the rest of the input 
stream in any way. Note, that since the attached mailboxes in Pegasus are 
"sticky", the next time I log into the program that "Separate me" mailbox will still 
be attached;-)

>     Different "instances" means that I could get different structures but I'd
> have to, again, mangle it in one form or another just to get a sane
> configuration.

Not in the case described above.

[description of how you work snipped...]

>     They consider that "simple."  And notice how Pegasus, Eudora, Lookout! and
> virtually every other client out there except for TB! and PMMail do the same
> thing.  They retrieve mail from the difference sources, merge it all into a
> single stream and then force the user to filter it out from there.

Not the case with Pegasus, look above.

>     BTW, you are aware that you can have TB! function just like Pegasus in
> that regard if you chose?  Forward all your mail to a single account, use TB!
> filters to filter it out from there, have different templates and filters to
> change "personalities" for you and keep it separate.

It's not the thing that will work all right when dial-up connection is what one 
uses:-( Forwarding all my mail to one account isn't the thing I want to try, as 
you might guess:-)

So, as I see it, I've explained how in Pegasus TB's default behaviour can be 
completely mimicked, but the reverse involves forwarding and is hence 
inappropriate solution:-)

-- 
SY, Alex
(St.Petersburg, Russia)
http://mph.phys.spbu.ru/~akiselev
--- 
Thought for the day:
  Any system or problem, however complicated, if looked at
  in exactly the right way, will become even more complicated.

--- 
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]>
--------------------------------------------------------------

Reply via email to