On Mon, Jun 29, 2015 at 01:00:25PM +0200, Daniel Trstenjak wrote:
> I'm not quite sure which misconfiguration of
> mbsync could have done this.
I think I know how it happened. I started off with mbsync
with the local MAILDIR folders created/synced by offlineimap
and my first mbsync co
Ok, the problem seems to be, that a syncing of mbsync
created the folders '[Google Mail].Sent Mail' and
'[Google Mail].Spam' on the IMAP server.
I'm not quite sure which misconfiguration of
mbsync could have done this.
After removing these folders from the IMAP server
everything works.
Thanks!
On Mon, Jun 29, 2015 at 12:13:15PM +0200, Oswald Buddenhagen wrote:
> ok, everything clear. you introduced this with a previous
> misconfiguration. clean up your folder structure, and all will be fine.
If you mean the local one, seems to be fine:
$> ll Mail/gmail/
total 9,5M
drwx-- 5 dan dan
On Mon, Jun 29, 2015 at 10:05:40AM +0200, Oswald Buddenhagen wrote:
> hmpf, this looks entirely ok.
> please add -l -Dn to the mbsync command line and send me the output.
Greetings,
Daniel
Reading configuration file /home/dan/.mbsyncrc
Channel gmail
Opening master store gmail-remote...
Resolving i
On Sun, Jun 28, 2015 at 09:29:25AM +0200, Oswald Buddenhagen wrote:
> your master store's config is presumably botched.
Here's my complete gmail config:
IMAPAccount gmail
Host imap.gmail.com
User daniel.trsten...@gmail.com
Pass ***
SSLType IMAPS
AuthMechs LOGIN
CertificateFile /etc/ssl/certs/ca-c
On Sun, Jun 21, 2015 at 03:04:04PM +0200, Daniel Trstenjak wrote:
> when syncing with gmail I'm now getting:
> >>> 17 APPEND "Old" (\Seen) {1573}
> + go ahead
> (1 in progress) >>> 18 APPEND "Old" (\Seen) {5105}
> 17 BAD Invalid Argu
On Wed, Jun 24, 2015 at 08:00:47AM +0200, Oswald Buddenhagen wrote:
> and you're sure you have the latest revision? what do git describe and
> mbsync --version say?
$> git describe
fatal: No annotated tags can describe
'ccd1340bf46e62c3be5796b665dd62779ffc9d40'.
$> mbsync --version
isync 1.3.0
> same question as in the other mail: what mbsync version exactly
> are you using?
It's the HEAD from 'git://git.code.sf.net/p/isync/isync'.
Greetings,
Daniel
--
Monitor 25 network devices or servers for free with OpMa
Hi,
when syncing with gmail I'm now getting:
>>> 17 APPEND "Old" (\Seen) {1573}
+ go ahead
(1 in progress) >>> 18 APPEND "Old" (\Seen) {5105}
17 BAD Invalid Arguments: Unable to parse message
IMAP command 'APPEND "Old" (\Seen) ' returned an error: BAD Invalid Arguments:
Unable to parse message
> i have no clue what that means, but most likely it has something to do
> with the fact that the tunneled server's ssl certificate does not match
> "mail". you can play with the "openssl s_client" command. if you get
> some more helpful error message, i'd be interested in that (to make
> mbsync m
> well, the server disagrees about your needs, and you aren't in a
> position to argue (unless you are the server's admin or can influence
> them).
>
> run with -Dn and see what auth methods the server offers. choose the
> most "boring" one it accepts.
Ok, running with '-Dn' gives me:
* OK [CAPABI
Hi,
I'm accessing an imap server over openvpn, so I don't need any kind of
further
secure connection to the imap server.
I tried something like:
IMAPAccount abc
Host ***
User ***
Pass ***
SSLType None
AuthMeths LOGIN
But with this config I'm getting:
IMAP error: server supports no acceptable aut
12 matches
Mail list logo
