Hi Euler,
[quote]No. The Default Identity attribution is a by folder feature.[/quote]
Sorry - as I described - you're partly wrong.
You may set default identity by folder, but obviously Pegasus already has the functionality to set default identity for a whole IMAP-Mailbox by setting it on mailboxname. As desribed this works very good. Despite you have set default identities for some folders in the mailbox, this setting works on all other folders in the mailbox.
The only problem is, that Pegasus doesn't save the setting for the mailbox. I would call it a little bug [;)]
[quote] If you plan to use a certain Identity for the whole IMAP account it is better select that account and work on[/quote]
I know how to use it - but for commodity reasons (people including me miss changing the identity far to much) and because the functionality is already implemeted, I would prefer David adding the missing save of configuration. I want him to do that, because in our environment (like in most business) there is no POP anymore. And Pegasus is the only mail program where I can't set default identity persistent for a IMAP-mailbox. More and more this will be a KO-criteria.
Editing and repairing STATE.PMJ is no problem for me. [:)] I was hoping that there is exactly one missing entry for the default identity for the whole IMAP-mailbox. That's what I'm searching for.
[quote]I'm sure you have a very good reason to do so but I'm wondering why one would do that.[/quote]
I have 8 IMAP-mailboxes. 2 functional mailboxes (with multiple mailaliases) and 1 personal mailbox for job and 5 private mailboxes. All are accessed via IMAP (and most don't support POP). All of them have some form of webmailer too - and those are based on IMAP. It is necessary to have access to every mailbox despite of available mailclient or webmailer - or the computer where Pegasus (or any other mailclient) is running with a due to POP local mailbox on it's hardisk (mobile Pegasus is no choice). That's modern art using and handling mail - POP is antique and will not be the future - sorry.
[quote]There's also This server supports folders within folders (see help) IMAP option to consider[/quote]
The problem remains the same on any type of IMAP-Server and any type of folder support. The IMAP-Servers are Mercury (trays only), exchange (folders in folders), postfix and cyrrus (both configurable).
[quote]Of all little experience I have with IMAP usage (I keep it to a minimum) one I remember constantly is that "every one has your IMAP", and that means servers and clients[/quote]
In business it's very simple: my "boss" wants (in case I can't do it for some reasons) to have access to my business mails. This access may be essential for the company. The law on how this is possible in a legal manner defers from country to country - but at least it must be possible. So mails have to be at the servers of the company (in my case the university). It's the job of the company to limit access to my mailbox at IMAP-Server to me and authorized personal - and it's my job to ensure nobody unauthorized has access to any mailclient where mails may be cached local or due to saved password authorized connections to the IMAP-Server may be established automatically. So it's my job to delete any cache in local mailclient or webbrowsers if I use them for authorizing and reading mails.
In other words: there should be no mail local at any computer. Due to increasing use of mobile computers (means desktop, tablet, smartphone and so on) and increasing "loss" of those computers there is no way having mails, the answers on that mails and the folder structures only on that mobile computer.
[quote]IOW it is a poorly standardized protocol[/quote]
There is no need to discuss the quality of standardization of IMAP here - fact is, that it works nicely - with every IMAP-Server I know and have access and every mailclient.
Bye Olaf