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.

Hi Pegasisti,

a long existing problem for me (with a not that "cool" work around) ... but now have a new identity with new IMAP-Mailbox and the problem comes up again.

1. It is possible to define a standard identity on every IMAP-Mailbox by right-clicking on the mailboxname. Works fine for every folder in that mailbox. But Pegasus doesn't save that configuration! Every time I open Pegasus I have to define that standard identity for every IMAP-Mailbox. Any suggestions or does anyone know where Pegasus should save it (may be I could enter it by hand)?
   
2. You may define a standard identity for every single folder in that IMAP-Mailbox. That configuration is saved by Pegasus for every folder ... but doing that for hundreds of folders isn't "smart".
3. If I define standard identity via mailboxname, Pegasus uses it for the whole IMAP-Mailbox. If defining standard identity on a folder in that mailbox (have several mailaliases on same mailaccount), it works on exactly that folder ... not it's subfolders. In my opinion that is not logical - a set identity on a folder should effect the folder AND it's subfolders. Sorry - may be it's because nearly every filesystem passes access rights top down so that's what I would expect Pegasus to do on IMAP folderstructures.

[quote user="FJR"]

Hi Pegasisti,

a long existing problem for me (with a not that "cool" work around) ... but now have a new identity with new IMAP-Mailbox and the problem comes up again.

1. It is possible to define a standard identity on every IMAP-Mailbox by right-clicking on the mailboxname. Works fine for every folder in that mailbox. But Pegasus doesn't save that configuration! Every time I open Pegasus I have to define that standard identity for every IMAP-Mailbox. Any suggestions or does anyone know where Pegasus should save it (may be I could enter it by hand)?[/quote]
   No. The Default Identity attribution is a by folder feature. If you plan to use a certain Identity for the whole IMAP account it is better select that account and work on. I have Identities specifically to work with IMAP access of my accounts.
   [quote user="FJR"]
2. You may define a standard identity for every single folder in that IMAP-Mailbox. That configuration is saved by Pegasus for every folder ... but doing that for hundreds of folders isn't "smart".[/quote]
   I'm sure you have a very good reason to do so but I'm wondering why one would do that. Anyway, if you need to make that in big bunches you may try editing State.pmj file though I hope you do not. IMAP folders are referenced there by a quite long and cryptic name. Look after Folder_Identities section.
   [quote user="FJR"]
3. If I define standard identity via mailboxname, Pegasus uses it for the whole IMAP-Mailbox. If defining standard identity on a folder in that mailbox (have several mailaliases on same mailaccount), it works on exactly that folder ... not it's subfolders. In my opinion that is not logical - a set identity on a folder should effect the folder AND it's subfolders. Sorry - may be it's because nearly every filesystem passes access rights top down so that's what I would expect Pegasus to do on IMAP folderstructures.[/quote]
   Not sure if Folder status handling may play a role here. There's also This server supports folders within folders (see help) IMAP option to consider. I'm not completely sure as I have never come this far.
   

[/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. IOW it is a poorly standardized protocol, and so it is not uncommon to have IMAP accounts that works greatly and others that simply do not work at all. If at least all servers used the same common sense...

[quote user="Euler GERMAN"]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. IOW it is a poorly standardized protocol, and so it is not uncommon to have IMAP accounts that works greatly and others that simply do not work at all. If at least all servers used the same common sense...[/quote]

And this is, unfortunately, the reason for David Harris to not like working on anything that has to do with IMAP although this is, as far as I can tell from the incoming crash dumps, the most frequent cause left for crashes in Pegasus Mail :-/