Hi!
I am facing the same issue. There is even respective entry in the
~/.mbsync, but no messages in the target mailbox.
On Tue, Aug 12, 2014 at 1:34 PM, Oswald Buddenhagen <
[email protected]> wrote:
> On Tue, Aug 12, 2014 at 10:07:24AM +0200, Bruno Gonzalez wrote:
> > On 14-08-11 15:42:54, Oswald Buddenhagen wrote:
> > > On Mon, Aug 11, 2014 at 02:18:13PM +0200, Bruno Gonzalez wrote:
> > > > >>> 2 NAMESPACE
> > > > * NAMESPACE (("INBOX." ".")) NIL NIL
> > > >
> > > whoops. that's a bit untypical.
> > >
> > > you can try overriding this by adding
> > > Path ""
> > > to the imap Store.
> >
> > You mean leaving the imap store section like this?
> >
> > =================
> > MaildirStore stenyakc-local
> > Path ~/mail/[email protected]/
> > Path ""
> > Inbox ~/mail/[email protected]/INBOX
> > =================
> >
> that's the maildir store.
> and obviously, you can't have two contradicting Paths in one store.
>
> On Tue, Aug 12, 2014 at 11:00:54AM +0200, Bruno Gonzalez wrote:
> > So it looks like any path ending in "/INBOX" is ignored, no matter where
> it is located?
> >
> that's not exactly what is supposed to happen.
> INBOX is magic in that it isn't rooted in the normal hierarchy, but is
> "free-flying" (that allows ~/mail/ as the namespace and
> /var/spool/mail/$USER as the INBOX on a traditional unix account).
> the consequence is that maildirs that are named INBOX but do not map
> back to the actual inbox (specified with Inbox) are ignored. you would
> also get a warning from mbsync that this is happening.
> fwiw, i just found a (somewhat minor bug): assuming a Path of ~/Maildir,
> a mailbox named foo.INBOX (path ~/Maildir/foo/.INBOX) will be ignored,
> but there is no reason to do that (because the unqualified name does not
> start with INBOX). but this is not what you are seeing, as then you'd
> also get no subfolders of this INBOX.
>
> in short, i have no clue what is happening. i'll have a look somewhen
> later, but that may take a few weeks.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> isync-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
