Menu
▾
▴
isync-devel
|
From: Bruno G. <st...@st...> - 2014-06-16 21:13:13
Attachments:
signature.asc
|
Hello,
I'm running isync 1.1.0 (1.1.0-2 in a 32bit debian unstable)
With my old gmail account, and with my work gapps account, it's working perfectly.
However, my personal email, running on a shared hosting server, is not getting fully synchronized. The failing account has the following IMAP directory tree:
INBOX
INBOX/Trash
INBOX/Drafts
INBOX/Archive
(etc.)
All the INBOX/* directories are synced without problems.
But the INBOX directory is always empty in my slave directory.
I've noticed that, during the very first sync (when starting from scratch), mbsync -V will output a line that says: "Maildir warning: ignoring INBOX"
Not sure if that's normal behaviour. All later runs of mbsync -V will never mention INBOX itself again (but as I say, they do mention, and properly synchronize, INBOX/* dirs).
The relevant part of my .mbsyncrc file is this:
--------------------
IMAPAccount stenyakc
Host imap.bar.com
User fo...@ba...
Pass baz-qux
UseIMAPS no
RequireSSL no
UseTLSv1 no
IMAPStore stenyakc-remote
Account stenyakc
MaildirStore stenyakc-local
Path ~/mail/fo...@ba.../
Inbox ~/mail/fo...@ba.../INBOX
Channel stenyakc
Master :stenyakc-remote:
Slave :stenyakc-local:
Patterns *
Create Slave
SyncState *
Sync All
--------------------
Is anything wrong with my mbsync configuration, or my imap server?
If you need any other information, please let me know. Thanks in advance!
--
Regards/Saludos,
Bruno Gonzalez
|
|
From: Oswald B. <osw...@gm...> - 2014-06-17 07:44:22
|
On Mon, Jun 16, 2014 at 10:46:16PM +0200, Bruno Gonzalez wrote: > However, my personal email, running on a shared hosting server, is not getting fully synchronized. The failing account has the following IMAP directory tree: > INBOX > INBOX/Trash > INBOX/Drafts > INBOX/Archive > (etc.) > > All the INBOX/* directories are synced without problems. > that's actually weird. i'd have expected this to be broken as well. > But the INBOX directory is always empty in my slave directory. > > I've noticed that, during the very first sync (when starting from scratch), mbsync -V will output a line that says: "Maildir warning: ignoring INBOX" > this is the cause of your problem. ignoring INBOX is a measure to avoid that the mailbox name is misinterpreted after stripping off the path. obviously, that's counterproductive in the case when INBOX is explicitly mapped into the maildir, so i'll need to fix that. > The relevant part of my .mbsyncrc file is this: > -------------------- > IMAPAccount stenyakc > Host imap.bar.com > User fo...@ba... > Pass baz-qux > UseIMAPS no > RequireSSL no > UseTLSv1 no > > IMAPStore stenyakc-remote > Account stenyakc > > MaildirStore stenyakc-local > Path ~/mail/fo...@ba.../ > Inbox ~/mail/fo...@ba.../INBOX > > Channel stenyakc > Master :stenyakc-remote: > Slave :stenyakc-local: > Patterns * > try simply appending INBOX to the list. > Create Slave > SyncState * > Sync All > -------------------- |
|
From: Bruno G. <st...@st...> - 2014-06-17 10:21:31
Attachments:
signature.asc
|
On 14-06-17 09:44:12, Oswald Buddenhagen wrote:
> On Mon, Jun 16, 2014 at 10:46:16PM +0200, Bruno Gonzalez wrote:
> > All the INBOX/* directories are synced without problems.
> >
> that's actually weird. i'd have expected this to be broken as well.
FYI, all of INBOX and INBOX/* have the usual cur,tmp,new subdirs in them: INBOX/{cur,new,tmp}/ are empty, while INBOX/*/{cur,new,tmp}/ seem to have the correct contents (they are synced).
> this is the cause of your problem.
> ignoring INBOX is a measure to avoid that the mailbox name is
> misinterpreted after stripping off the path. obviously, that's
> counterproductive in the case when INBOX is explicitly mapped into the
> maildir, so i'll need to fix that.
Okay, let me know if you need any help testing or whatever.
Do you suggest I stop using mbsync for this specific imap account meanwhile?
> > Channel stenyakc
> > Master :stenyakc-remote:
> > Slave :stenyakc-local:
> > Patterns *
> >
> try simply appending INBOX to the list.
I've tried all of the following lines (some were just random tests), unfortunately none of them worked:
Patterns *
Patterns INBOX
Patterns INBOX.
Patterns INBOX/
Patterns INBOX/*
Patterns INBOX/INBOX
Patterns INBOX.INBOX
Patterns INBOX/.INBOX
Patterns *INBOX
Patterns ./INBOX
Patterns ./.INBOX
Patterns ./*INBOX
Thanks for the help
--
Regards/Saludos,
Bruno Gonzalez
|
|
From: Oswald B. <osw...@gm...> - 2014-06-17 15:40:23
|
On Tue, Jun 17, 2014 at 11:54:33AM +0200, Bruno Gonzalez wrote: > On 14-06-17 09:44:12, Oswald Buddenhagen wrote: > > > Channel stenyakc > > > Master :stenyakc-remote: > > > Slave :stenyakc-local: > > > Patterns * > > > > > try simply appending INBOX to the list. > > I've tried all of the following lines (some were just random tests), unfortunately none of them worked: > Patterns * > Patterns INBOX > Patterns INBOX. > Patterns INBOX/ > Patterns INBOX/* > Patterns INBOX/INBOX > Patterns INBOX.INBOX > Patterns INBOX/.INBOX > Patterns *INBOX > Patterns ./INBOX > Patterns ./.INBOX > Patterns ./*INBOX > i meant Patterns * INBOX |
|
From: Bruno G. <st...@st...> - 2014-06-17 16:22:14
|
On 14-06-17 17:40:14, Oswald Buddenhagen wrote:
> i meant
> Patterns * INBOX
Not working either.
--
Regards/Saludos,
Bruno Gonzalez
|
|
From: Oswald B. <osw...@gm...> - 2014-06-28 12:32:02
|
On Tue, Jun 17, 2014 at 05:55:18PM +0200, Bruno Gonzalez wrote: > On 14-06-17 17:40:14, Oswald Buddenhagen wrote: > > i meant > > Patterns * INBOX > > Not working either. > actually, Patterns INBOX* would be the correct config for you. but i don't think that would change anything. maybe you ran into the same problem that armands discovered. please pull isync_1_1_branch and see whether it works. if not, let's start with the output of "mbsync -a -l". |
|
From: Bruno G. <st...@st...> - 2014-08-11 12:45:10
Attachments:
signature.asc
|
On 14-06-28 14:31:53, Oswald Buddenhagen wrote:
> On Tue, Jun 17, 2014 at 05:55:18PM +0200, Bruno Gonzalez wrote:
> actually,
>
> Patterns INBOX*
>
> would be the correct config for you.
> but i don't think that would change anything.
>
> maybe you ran into the same problem that armands discovered. please pull
> isync_1_1_branch and see whether it works.
> if not, let's start with the output of "mbsync -a -l".
I just tried commit 313c9193f890aaabd64f9ca97ccdfae8a29d02f1. The problem seems to persist. These are the logs, please let me know if I can do anything else. Thanks!
#######################################################################
$ mbsync -v
isync 1.1.2
#######################################################################
$ cat .mbsyncrc # (personal details edited)
IMAPAccount stenyakc
Host imap.xxxxxxx.com
User xxxxxxxxxxxx
Pass xxxxxxxxxxxx
UseIMAPS no
RequireSSL no
UseTLSv1 no
IMAPStore stenyakc-remote
Account stenyakc
MaildirStore stenyakc-local
Path ~/mail/xx...@xx.../
Inbox ~/mail/xx...@xx.../INBOX
Channel stenyakc
Master :stenyakc-remote:
Slave :stenyakc-local:
Patterns INBOX*
Create Slave
SyncState *
Sync All
#######################################################################
$ mbsync -a -l -V
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
*** IMAP Warning *** Password is being sent in the clear
>>> 1 LOGIN <user> <pass>
1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA] Logged in
>>> 2 NAMESPACE
* NAMESPACE (("INBOX." ".")) NIL NIL
2 OK Namespace completed.
>>> 3 LIST "" "INBOX.*"
* LIST (\HasNoChildren) "." "INBOX.WhatsApp"
* LIST (\HasNoChildren) "." "INBOX.Drafts"
* LIST (\HasChildren) "." "INBOX.Trash"
* LIST (\HasNoChildren) "." "INBOX.Trash.2014"
* LIST (\HasNoChildren) "." "INBOX.spam"
* LIST (\HasNoChildren) "." "INBOX.Sent"
* LIST (\HasNoChildren) "." "INBOX.INBOX.Trash"
* LIST (\HasNoChildren) "." "INBOX.phone"
* LIST (\HasNoChildren) "." "INBOX.Archive"
3 OK List completed.
INBOX/Archive
INBOX/phone
INBOX/INBOX/Trash
INBOX/Sent
INBOX/spam
INBOX/Trash/2014
INBOX/Trash
INBOX/Drafts
INBOX/WhatsApp
>>> 4 LOGOUT
* BYE Logging out
4 OK Logout completed.
#######################################################################
$ mbsync -a -V |grep -vw FETCH
*** IMAP Warning *** Password is being sent in the clear
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
>>> 1 LOGIN <user> <pass>
1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA] Logged in
>>> 2 NAMESPACE
* NAMESPACE (("INBOX." ".")) NIL NIL
2 OK Namespace completed.
>>> 3 LIST "" "INBOX.*"
* LIST (\HasNoChildren) "." "INBOX.WhatsApp"
* LIST (\HasNoChildren) "." "INBOX.Drafts"
* LIST (\HasChildren) "." "INBOX.Trash"
* LIST (\HasNoChildren) "." "INBOX.Trash.2014"
* LIST (\HasNoChildren) "." "INBOX.spam"
* LIST (\HasNoChildren) "." "INBOX.Sent"
* LIST (\HasNoChildren) "." "INBOX.INBOX.Trash"
* LIST (\HasNoChildren) "." "INBOX.phone"
* LIST (\HasNoChildren) "." "INBOX.Archive"
3 OK List completed.
>>> 4 SELECT "INBOX.Archive"
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $ulabels_5252832f52c37 $labels_5252832f52c37 $Forwarded $MDNSent $has_cal Junk $ulabels_52556be96cc9f Old)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $ulabels_5252832f52c37 $labels_5252832f52c37 $Forwarded $MDNSent $has_cal Junk $ulabels_52556be96cc9f Old \*)] Flags permitted.
* 76374 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1380747160] UIDs valid
* OK [UIDNEXT 155088] Predicted next UID
* OK [HIGHESTMODSEQ 12029] Highest
4 OK [READ-WRITE] Select completed.
5 OK Fetch completed.
>>> 6 SELECT "INBOX.phone"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.
* 679 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1380747161] UIDs valid
* OK [UIDNEXT 680] Predicted next UID
* OK [HIGHESTMODSEQ 678] Highest
6 OK [READ-WRITE] Select completed.
7 OK Fetch completed.
>>> 8 SELECT "INBOX.INBOX.Trash"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1401470391] UIDs valid
* OK [UIDNEXT 1] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
8 OK [READ-WRITE] Select completed.
>>> 9 SELECT "INBOX.Sent"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $Forwarded)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $Forwarded \*)] Flags permitted.
* 10011 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1380747156] UIDs valid
* OK [UIDNEXT 10013] Predicted next UID
* OK [HIGHESTMODSEQ 340] Highest
9 OK [READ-WRITE] Select completed.
10 OK Fetch completed.
>>> 11 SELECT "INBOX.spam"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk NonJunk Old)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk NonJunk Old \*)] Flags permitted.
* 698 EXISTS
* 0 RECENT
* OK [UNSEEN 698] First unseen.
* OK [UIDVALIDITY 1380747159] UIDs valid
* OK [UIDNEXT 10836] Predicted next UID
* OK [HIGHESTMODSEQ 10763] Highest
11 OK [READ-WRITE] Select completed.
12 OK Fetch completed.
>>> 13 SELECT "INBOX.Trash.2014"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1401470390] UIDs valid
* OK [UIDNEXT 1] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
13 OK [READ-WRITE] Select completed.
>>> 14 SELECT "INBOX.Trash"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $MDNSent Junk)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk $MDNSent Junk \*)] Flags permitted.
* 63 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1380747158] UIDs valid
* OK [UIDNEXT 94872] Predicted next UID
* OK [HIGHESTMODSEQ 897] Highest
14 OK [READ-WRITE] Select completed.
15 OK Fetch completed.
>>> 16 SELECT "INBOX.Drafts"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1380747155] UIDs valid
* OK [UIDNEXT 862] Predicted next UID
* OK [HIGHESTMODSEQ 2138] Highest
16 OK [READ-WRITE] Select completed.
>>> 17 SELECT "INBOX.WhatsApp"
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.
* 823 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1380747162] UIDs valid
* OK [UIDNEXT 825] Predicted next UID
* OK [HIGHESTMODSEQ 809] Highest
17 OK [READ-WRITE] Select completed.
18 OK Fetch completed.
>>> 19 LOGOUT
* BYE Logging out
19 OK Logout completed.
--
Regards/Saludos,
Bruno Gonzalez
|
|
From: Oswald B. <osw...@gm...> - 2014-08-11 13:43:01
|
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.
alternatively, you could use
Patterns INBOX *
which would put the inbox and its subfolders on the same level in the
maildir.
however, what i find worrisome is that despite the namespace (which is a
prefix that should be stripped), the final mailbox list contains the
INBOX/ prefix. something seems wrong with mbsync.
> * LIST (\HasNoChildren) "." "INBOX.INBOX.Trash"
>
this doesn't look too sensible ... i suppose it's a leftover from a
previous attempt?
|
|
From: Bruno G. <st...@st...> - 2014-08-12 08:34:21
Attachments:
signature.asc
|
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/xx...@xx.../
Path ""
Inbox ~/mail/xx...@xx.../INBOX
=================
>
> alternatively, you could use
> Patterns INBOX *
> which would put the inbox and its subfolders on the same level in the
> maildir.
I've tried "Patterns INBOX *" in the past with no luck.
With the new version, it also doesn't seem to make a difference:
==================
$ mbsync -l -V stenyakc
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
*** IMAP Warning *** Password is being sent in the clear
>>> 1 LOGIN <user> <pass>
1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA] Logged in
>>> 2 NAMESPACE
* NAMESPACE (("INBOX." ".")) NIL NIL
2 OK Namespace completed.
>>> 3 LIST "" "INBOX.*"
* LIST (\HasNoChildren) "." "INBOX.WhatsApp"
* LIST (\HasNoChildren) "." "INBOX.Drafts"
* LIST (\HasChildren) "." "INBOX.Trash"
* LIST (\HasNoChildren) "." "INBOX.Trash.2014"
* LIST (\HasNoChildren) "." "INBOX.spam"
* LIST (\HasNoChildren) "." "INBOX.Sent"
* LIST (\HasNoChildren) "." "INBOX.INBOX.Trash"
* LIST (\HasNoChildren) "." "INBOX.phone"
* LIST (\HasNoChildren) "." "INBOX.Archive"
3 OK List completed.
INBOX/Archive
INBOX/phone
INBOX/INBOX/Trash
INBOX/Sent
INBOX/spam
INBOX/Trash/2014
INBOX/Trash
INBOX/Drafts
INBOX/WhatsApp
>>> 4 LOGOUT
* BYE Logging out
4 OK Logout completed
==================
>
> however, what i find worrisome is that despite the namespace (which is a
> prefix that should be stripped), the final mailbox list contains the
> INBOX/ prefix. something seems wrong with mbsync.
>
> > * LIST (\HasNoChildren) "." "INBOX.INBOX.Trash"
> >
> this doesn't look too sensible ... i suppose it's a leftover from a
> previous attempt?
Most probably, don't worry about it (I've to review all my IMAP clients configs, one must be reuploading old cruft, such as that and the 2014 folder).
--
Regards/Saludos,
Bruno Gonzalez
|
|
From: Bruno G. <st...@st...> - 2014-08-12 09:27:51
Attachments:
signature.asc
|
Hmmm... I just noticed this:
On 14-08-12 10:07:24, Bruno Gonzalez wrote:
> ==================
> $ mbsync -l -V stenyakc
[...]
> >>> 3 LIST "" "INBOX.*"
> * LIST (\HasNoChildren) "." "INBOX.WhatsApp"
> * LIST (\HasNoChildren) "." "INBOX.Drafts"
> * LIST (\HasChildren) "." "INBOX.Trash"
> * LIST (\HasNoChildren) "." "INBOX.Trash.2014"
> * LIST (\HasNoChildren) "." "INBOX.spam"
> * LIST (\HasNoChildren) "." "INBOX.Sent"
> * LIST (\HasNoChildren) "." "INBOX.INBOX.Trash"
> * LIST (\HasNoChildren) "." "INBOX.phone"
> * LIST (\HasNoChildren) "." "INBOX.Archive"
> 3 OK List completed.
> INBOX/Archive
> INBOX/phone
> INBOX/INBOX/Trash
> INBOX/Sent
> INBOX/spam
> INBOX/Trash/2014
> INBOX/Trash
> INBOX/Drafts
> INBOX/WhatsApp
> >>> 4 LOGOUT
> * BYE Logging out
> 4 OK Logout completed
> ==================
The folder tree seems to be the following (written with full paths):
/
/INBOX
/INBOX/WhatsApp
/INBOX/Drafts
/INBOX/Trash
/INBOX/Trash/2014
/INBOX/spam
/INBOX/Sent
/INBOX/INBOX
/INBOX/INBOX/Trash
/INBOX/phone
/INBOX/Archive
Note that neither /INBOX nor /INBOX/INBOX are mentioned anywhere, while the rest of folders are.
So it looks like any path ending in "/INBOX" is ignored, no matter where it is located?
--
Regards/Saludos,
Bruno Gonzalez
|
|
From: Oswald B. <osw...@gm...> - 2014-08-12 10:34:43
|
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/xx...@xx.../
> Path ""
> Inbox ~/mail/xx...@xx.../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.
|
|
From: Armands L. <arm...@gm...> - 2014-10-01 08:54:02
|
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 <
osw...@gm...> 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/xx...@xx.../
> > Path ""
> > Inbox ~/mail/xx...@xx.../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
> isy...@li...
> https://lists.sourceforge.net/lists/listinfo/isync-devel
>
|
|
From: Armands L. <arm...@gm...> - 2014-10-01 09:43:27
|
On Wed, Oct 1, 2014 at 11:53 AM, Armands Liepins <arm...@gm...> wrote: > Hi! > > I am facing the same issue. There is even respective entry in the > ~/.mbsync, but no messages in the target mailbox. > > Oops, sorry, found what was wrong. Missing "Inbox" entry in the ~/mbsyncrc, so by default INBOX messages go to ~/Maildir. But anyway question is why INBOX subfolders go to "Path". |
|
From: Oswald B. <osw...@gm...> - 2014-10-02 06:41:23
|
On Wed, Oct 01, 2014 at 12:43:20PM +0300, Armands Liepins wrote: > On Wed, Oct 1, 2014 at 11:53 AM, Armands Liepins <arm...@gm...> wrote: > > > Hi! > > > > I am facing the same issue. There is even respective entry in the > > ~/.mbsync, but no messages in the target mailbox. > > > > > Oops, sorry, found what was wrong. Missing "Inbox" entry in the > ~/mbsyncrc, so by default INBOX messages go to ~/Maildir. But anyway > question is why INBOX subfolders go to "Path". > please paste the .mbsyncrc |
|
From: Armands L. <arm...@gm...> - 2014-10-02 09:43:57
|
On Thu, Oct 2, 2014 at 9:41 AM, Oswald Buddenhagen < osw...@gm...> wrote: please paste the .mbsyncrc > IMAPStore test-imap Host imaphost.com Port 993 User "user" Pass "password" RequireSSL yes UseIMAPS yes MaildirStore test-local Path /var/lib/imap/us...@so.../. Flatten . Channel test Master :test-imap: Slave :test-local: Patterns * Sync Pull Create slave Expunge none CopyArrivaldate yes |
|
From: Oswald B. <osw...@gm...> - 2014-10-03 09:49:15
|
On Thu, Oct 02, 2014 at 12:43:50PM +0300, Armands Liepins wrote: > MaildirStore test-local > Path /var/lib/imap/us...@so.../. > Flatten . > that. it's explicitly documented that subfolders of INBOX will be flattened into the Path hierarchy. there is little alternative to that: if your INBOX is ~/Maildir, what is INBOX.foo supposed to be? ~/Maildir.foo? do you really want that in your home dir? now, if you place INBOX inside Path (by using the Inbox option) and actually name it INBOX, the flattened INBOX subfolders will naturally align name-wise, as the INBOX mapping is a null transformation. the problems start if you map INBOX to a different name (say, Inb0x) - the flattened INBOX.foo is not seen as a subfolder of INBOX (it's just a string with no hierarchy), so you'd get ~/maildir/Inb0x and ~/maildir/INBOX.foo as folders. i don't think it makes sense to spend time on making this work differently - the semantics would be arbitrary. it's basically asking the question "what does an imap server that does not understand hierarchical mailboxes do with hierarchical mailboxes?" - "something". |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X