Hi,

A few months ago, Peter P. described a "missing INBOX issue" after upgrading 
isync to 1.2.2:

  https://sourceforge.net/p/isync/mailman/message/35525334/

Peter appears to have resolved this issue by removing the following line from 
his mbrsyncrc:
  Path INBOX

and adding the following instead:
  UseNamespace no


I recently seem to have run into the same issue as Peter, but resolved it (I 
think?) differently, i.e., by renaming
  Path INBOX

to
  Path Inbox


After running into Peter's solution by accident - and before testing my own 
solution more thoroughly on the ground - I am wondering:

=> Does the second solution (Path Inbox) seem reasonable at all, or am I 
heading towards trouble without knowing it?
=> Would one of the two described solutions be preferable to the other (for 
whatever reason)?


For the record, both solutions seem to result in "INBOX." being prefixed to 
local folder names, i.e., with the
  Flatten .

option, I seem to be getting the following local folder structure in either 
case:

INBOX/
INBOX.Sent/
INBOX.Trash/
[...]


Thanks to Oswald for this amazing piece of software!

best,
flo.H



On 12/03/2016, peterpar...@fastmail.com> wrote:
> Hi Oswald,
> 
> * Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2016-12-02 10:30]:
>> On Thu, Dec 01, 2016 at 12:14:21PM +0100, Peter P. wrote:
>>> I assume that the way the config options have changed,
>>>
>> yes, there is this item in the NEWS file:
>>
>>>> An IMAP Path/NAMESPACE rooted in INBOX won't be handled specially
>>>> any more.  This means that some Patterns may need adjustment.
> Thank you! I should have had checked that in /usr/share/doc please
> excuse me.
>  
>> from the first look it seems that this is exactly what is hitting you.
>>
>>>     IMAPStore box-remote
>>>     Account box

>>>     Path INBOX
>>>
>> an entirely wild guess is that you just need to remove this. running
>> with -l will tell you.
>> if it doesn't help, try adding 'UseNamespace no' as well.
> both, removing "Path INBOX" and setting "UseNamespace no" were required
> to fix my problem. As well as getting me the correct output from -l as
> described in my other email with subject "empty line in output of -l".

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Reply via email to