Please note that I am in the process of transferring my email agent from Mozilla Seamonkey (Thunderbird compatible) to Claws-mail. I'm just trying to echo the Seamonkey configuration to Claws (with mixed results). When I set up multiple POP accounts, I first defined my initial account using the wizard. Then I defined all the other local mailboxes. Then I defined all the associated email accounts. When I tested downloading my messages, (on the accounts that worked) everything was downloaded to the first email account defined. After investigation, I found that in the "accountrc" configuration file, the "inbox" variable was correct, but the "local_inbox" variable always pointed to the first account. After setting "local_inbox" to the value of "inbox", all the accounts are then downloaded to the correct mailbox. I think the correction should involve dedicating "inbox" to remote (i.e. IMAP) connexions, possibly renaming it to something like "remote_inbox" or "imap_inbox". Then for IMAP, remote connexions would use that variable. For all local mailboxes (POP and any local IMAP, etc), "local_inbox" would be used. Thus POP accounts would only have "local_inbox" defined. I assume that that should be a relatively simple correction, to anyone familiar with the code. BTW, I notice that the bogofilter plugin doesn't seem to accommodate multiple accounts if one doesn't want to use the default of "trash" of the mailbox in question, unless one wants to direct the spam for all mailboxes to the same folder. Although I prefer the default, it may matter to other users.
> Version: 2.9.0 Really in 2007 are you? Current is 3.9.3.
(In reply to comment #1) > > Version: 2.9.0 > > Really in 2007 are you? Current is 3.9.3. fixed ;)
'local_inbox' is used for Local accounts. 'inbox' is used for POP accounts. So I don't see how changing 'local_inbox' can have any affects on your POP accounts. If you were to use the GUI, changing the a POP account's 'Default inbox' on the Receive page changes the value of 'inbox'. Changing a Local account's 'Default inbox' on the Receive page changes the value of 'local_inbox'.
Reopening because the problem really exists, as explained below. (In reply to comment #3) > 'local_inbox' is used for Local accounts. > 'inbox' is used for POP accounts. Both were defined for all my POP accounts. The first POP account was defined by the wizard, the others directly through the GUI, as the wizard didn't seem to be available. As noted in the report, "local_inbox" was set equal to "inbox" of the first POP account (by the wizard). > So I don't see how changing 'local_inbox' can have any affects on your POP > accounts. Maybe you don't see it, but it is easy to test. 1) Configure a POP account to have "local_inbox" point to a different location than "local". (Necessarily using accountrc and not the GUI for "local_inbox".) 2) Then download an email. 3) It goes to the destination of "local_inbox" and not "inbox" > If you were to use the GUI, changing the a POP account's 'Default inbox' on > the Receive page changes the value of 'inbox'. Changing a Local account's > 'Default inbox' on the Receive page changes the value of 'local_inbox'. I didn't intend to define any "local" non-POP accounts, and used only the GUI. (Except for defining a location for archiving older email, which won't need an inbox.) Maybe this happened after defining the first account since defining an email address doesn't allow creating associated mailboxes at the same time, so I (probably) created the mailboxes first. But even the wizard created both variables. There is obviously some problem. There is no reason to define 2 inbox locations for each POP account, which is what happened. There could be some test to erase any "local_inbox" variables for POP accounts. Better yet, use the same variable for both POP (which necessarily stores emails locally) and "local" accounts. BTW, it seems to me a little bizarre to by default have every email account share the same mailboxes. One can give each account its' own set of mailboxes, but it is a little complex, particularly for non-programmers (unlike myself). It is as though Claws (and Sylpheed) was (and is still) designed for an internal corporate email system. Suggest : a) Initially ask the email base folder (which is "Mail" by default) b) then ask **Mailbox preferences : 1) one set of mailboxes for all accounts, directly in "Mail", or 2) a separate set of mailboxes for each account, as subfolders in "Mail"** (Of course "Mail" replaced by whatever is chosen in step a.) If option 2 is selected, then for each added email account, the wizard automatically adds the appropriate folders to a designated subfolder. This would greatly facilitate new users to claws, as well as helping existing users add new accounts. Right now it is a sort of chicken-and-egg situation. First, one adds a new mailbox, automatically classified as "local", even if one intends to add a new POP email account. Then one adds the new email account, selecting the newly added mailboxes. If one does it in reverse order, one has to associate the inbox to the account in a third step. Once I get set up with claws, I could help with such a transition, if wanted.
(In reply to comment #4) > Maybe you don't see it, but it is easy to test. > 1) Configure a POP account to have "local_inbox" point to a different > location than "local". (Necessarily using accountrc and not the GUI for > "local_inbox".) > 2) Then download an email. > 3) It goes to the destination of "local_inbox" and not "inbox" No, it doesn't go to the destination of "local_inbox", it goes to the destination of "inbox".
I believe that an easy way to have separate POP accounts, so users have independent files and sesions is to run claws-mail from command line with --alternate-config-dir option. This opens then install wizard as a brand new instalation and may select "mail" filename. Example: $ claws-mail --alternate-config-dir $HOME/mydirectory Of course you will need create a .desktop entry to run from desktop. It works fine for me Regards Dario