mbsync not running with cron
I'm trying to get mbsync to run every minute via cron. I have the following line in my crontab: * * * * * mbsync -qqa >/dev/null 2>&1 Running mbsync manually works, but nothing seems to be happening via cron. Any suggestions? This is on an Ubuntu Server. This is also my first attempt at using cron -- not sure if I'm missing anything obvious. I did run a test for the environment, and cron seems to be using my user, but sh instead of bash. Any help would be much appreciated! -- dwrz|朱为文 -- 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
Re: Sasl: No worthy mechs found
This is mine: Reading configuration file /home/user/.mbsyncrc Channel example Opening master store example-remote... Resolving mail.example.com... ok Connecting to mail.example.com (xx.xx.xx.xxx:993)... Opening slave store example-local... Connection is now encrypted * OK IMAP4 ready >>> 1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN 1 OK completed Logging in... IMAP error: authentication mechanism PLAIN is not supported This is with "AuthMechs *". With "AuthMecs LOGIN" everything works. Just saw you email about the config file, though; I have a suspicion it applies to me as well. --- dwrz|朱为文 On 2016-12-02 09:15, Oswald Buddenhagen wrote: > On Fri, Dec 02, 2016 at 03:47:01AM +, david wen riccardi-zhu wrote: > >> Glad to hear! I'd made the same assumption. > >> Not sure if something is broken, > sounds like it. a -Dn dump from such a failing session would be > interesting. > > -- > 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-- 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
Re: Sasl: No worthy mechs found
Glad to hear! I'd made the same assumption. Not sure if something is broken, if the documentation needs to be updated, or if users need to be better informed. : ) --- dwrz|朱为文 On 2016-12-01 18:57, Peter P. wrote: > * dwrz [2016-12-01 16:19]: > >> Hi Peter, >> >> Just a shot in the dark -- have you tried setting AuthMechs to LOGIN? > > And back from the dark I report that this works. Please excuse me, I did > misunderstand the manpage saying approximately that "AuthMechs defaults > to * and all mechanismes deemed secure enough for the given SSL method." > (of which I thought LOGIN was included). This is on imap.aol.com btw. > > Thanks dwrz! > P-- 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
Re: SASL(-7) error plain_clienttoken.c?
Thank you -- this seems to have resolved my issue as well. Not sure why * isn't working anymore, though . . . --- dwrz|朱为文 On 2016-11-27 14:24, David Brumley wrote: > Hi, > After a bit more work, I found I was missing the following line (this email > is for anyone with similar problems): > --- > > AuthMechs LOGIN > > > > All works now. > > Thanks! -david > > _ _ > _Bosch Professor of Computer Security and Privacy_ > _Professor of Electrical and Computer Engineering_ > Director, CMU CyLab Security and Privacy Institute > > On Sun, Nov 27, 2016 at 6:48 AM, David Brumley wrote: > >> Hi, >> I'm trying to configure mbsync with a password for gmail. I get a SASL >> error: >> >> $ mbsync gmail >> C: 0/4 B: 0/3 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0 >> Password (gmail): >> Error: SASL(-7): invalid parameter supplied: Parameter Error in >> /BuildRoot/Library/Caches/com.apple.xbs/Sources/passwordserver_saslplugins/passwordserver_saslplugins-192/plain_clienttoken.c >> near line 195 >> C: 4/4 B: 0/3 M: +0/0 *0/0 #0/0 S: +0/0 *0/0 #0/0 >> >> My .mbsyncrc is below. Anyone else run into this difficulty? I'm running >> OSX 10.12.1 (Sierra) and installed isync (1.2.1) from homebrew. >> >> I searched the archives but nothing turned up. >> >> Thanks! >> -David >> >> _ _ >> >> # ACCOUNT INFORMATION >> IMAPAccount gmail >> Host imap.gmail.com [1] >> User dbrum...@gmail.com >> # PassCmd "security find-generic-password -s mbsync-gmail-password -w" >> Pass >> SSLType IMAPS >> CertificateFile /usr/local/etc/ssl/certs/ca-certificates.crt >> >> # THEN WE SPECIFY THE LOCAL AND REMOTE STORAGE >> # - THE REMOTE STORAGE IS WHERE WE GET THE MAIL FROM (E.G., THE >> # SPECIFICATION OF AN IMAP ACCOUNT) >> # - THE LOCAL STORAGE IS WHERE WE STORE THE EMAIL ON OUR COMPUTER >> >> # REMOTE STORAGE (USE THE IMAP ACCOUNT SPECIFIED ABOVE) >> IMAPStore gmail-remote >> Account gmail >> >> # LOCAL STORAGE (CREATE DIRECTORIES with mkdir -p Maildir/gmail) >> MaildirStore gmail-local >> Path ~/Mail/Gmail-mbsync/ >> Inbox ~/Mail/Gmail-mbsync/INBOX >> >> # CONNECTIONS SPECIFY LINKS BETWEEN REMOTE AND LOCAL FOLDERS >> # >> # CONNECTIONS ARE SPECIFIED USING PATTERNS, WHICH MATCH REMOTE MAIl >> # FOLDERS. SOME COMMONLY USED PATTERS INCLUDE: >> # >> # 1 "*" TO MATCH EVERYTHING >> # 2 "!DIR" TO EXCLUDE "DIR" >> # 3 "DIR" TO MATCH DIR >> # >> # FOR INSTANCE IN THE SPECIFICATION BELOW: >> # >> # gmail-inbox gets the folder INBOX, ARCHIVE, and everything under >> "ARCHIVE*" >> # gmail-trash gets only the "[Gmail]/Trash" folder and stores it to the >> local "trash" folder >> >> #Channel gmail-inbox >> #Master :gmail-remote: >> #Slave :gmail-local: >> #Patterns "INBOX" "Arch*" >> #Create Both >> #Expunge Both >> #SyncState * >> >> Channel gmail-inbox >> Master ":gmail-remote:INBOX" >> Slave ":gmail-local:INBOX" >> Create Both >> SyncState * >> >> Channel gmail-trash >> Master :gmail-remote:"[Gmail]/Trash" >> Slave :gmail-local:trash >> Create Both >> Expunge Both >> SyncState * >> >> Channel gmail-sent >> Master :gmail-remote:"[Gmail]/Sent Mail" >> Slave :gmail-local:sent >> Create Both >> Expunge Both >> SyncState * >> >> Channel gmail-archive >> Master ":gmail-remote:[Gmail]/All Mail" >> Slave ":gmail-local:archive" >> Create Both >> SyncState * >> >> # GROUPS PUT TOGETHER CHANNELS, SO THAT WE CAN INVOKE >> # MBSYNC ON A GROUP TO SYNC ALL CHANNELS >> # >> # FOR INSTANCE: "mbsync gmail" GETS MAIL FROM >> # "gmail-inbox", "gmail-sent", and "gmail-trash" >> # >> Group gmail >> Channel gmail-inbox >> Channel gmail-sent >> Channel gmail-trash >> Channel gmail-archive > > -- > > ___ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel Links: -- [1] http://imap.gmail.com-- ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: unknown/misplaced keyword 'AuthMechs' (plus 'SSLType' and 'SSLVersions')
Thanks, Robert! I've just tried this, but I'm still getting the same error. Really lost. I have this email syncing on an Android phone with no issues. Settings there are 993, SSL/TLS, and "Normal" password (not "Encrypted" or "Client certificate") -- which I assume means PLAIN authentication. --- dwrz|朱为文 On 2016-11-27 09:36, Robert Nilsson wrote: > Hi David! > > Without remembering exactly, I had that problem when getting isync to > work on my gentoo install, and found that I needed some more > libraries, to get more authentication options. I think it is the SASL > library you would need. > > If you had it working before on the same raspbian install, it suggests > that the needed package should already be installed, but you will > probably need the '-dev'-package to be able to include it in your > custom build. > > regards > > Robert > On Sat, Nov 26, 2016 at 07:53:02PM +, david wen riccardi-zhu wrote: I am > still having issues getting sync to work again and would really > appreciate some guidance. > > I am now running 1.2.1, built from source, and am getting the following > error when I try to sync: > > IMAP ERROR: AUTHENTICATION MECHANISM PLAIN IS NOT SUPPORTED > > -Dn displays the following: > > [. . .] > Connection is now encrypted > * OK IMAP4 ready 1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN 1 OK completed Logging in... IMAP error: authentication mechanism PLAIN is not supported I've tried changing AuthMechs, SSLType, and SSLVersions in the config file, but this issue persists. Does anyone have any suggestions on how to resolve this, or can point me to any useful resources? What's really puzzling me is that everything was working fine before, on Raspbian and 1.1.1. Thanks, David --- dwrz|朱为文 On 2016-11-04 03:00, david wen riccardi-zhu wrote: > I had mbsync working perfectly until a recent server upgrade. > > Not sure if it matters, but I went from a Raspberry Pi 3 running Raspbian to > a Dell Chromebox running Ubuntu server. > > Installed isync to the new sever, copied my .mbsyncrc, and now it's not > working. > > I am getting the following errors when trying to run mbsync: > > /home/user/.mbsyncrc:5: unknown/misplaced keyword 'AuthMechs' > /home/user/.mbsyncrc:6: unknown/misplaced keyword 'SSLType' > /home/user/.mbsyncrc:7: unknown/misplaced keyword 'SSLVersions' > > If I comment out those lines, I get the following: > > Socket error from wtf.imap.com (##.##.##.###:993): Connection reset by peer > > I'm struggling to figure out what is going on and why. As far as I know, > nothing has changed with either my mail provider's IMAP server or my > MaildirStore. > > After reading through the list, I tried using a new Maildirstore, but I'm > still getting the same error. > > Any insights or suggestions? > > Thank you, > > David > > -- > dwrz|朱为文 > -- > ___ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel-- ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: unknown/misplaced keyword 'AuthMechs' (plus 'SSLType' and 'SSLVersions')
I am still having issues getting sync to work again and would really appreciate some guidance. I am now running 1.2.1, built from source, and am getting the following error when I try to sync: IMAP ERROR: AUTHENTICATION MECHANISM PLAIN IS NOT SUPPORTED -Dn displays the following: [. . .] Connection is now encrypted * OK IMAP4 ready >>> 1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN 1 OK completed Logging in... IMAP error: authentication mechanism PLAIN is not supported I've tried changing AuthMechs, SSLType, and SSLVersions in the config file, but this issue persists. Does anyone have any suggestions on how to resolve this, or can point me to any useful resources? What's really puzzling me is that everything was working fine before, on Raspbian and 1.1.1. Thanks, David --- dwrz|朱为文 On 2016-11-04 03:00, david wen riccardi-zhu wrote: > I had mbsync working perfectly until a recent server upgrade. > > Not sure if it matters, but I went from a Raspberry Pi 3 running Raspbian to > a Dell Chromebox running Ubuntu server. > > Installed isync to the new sever, copied my .mbsyncrc, and now it's not > working. > > I am getting the following errors when trying to run mbsync: > > /home/user/.mbsyncrc:5: unknown/misplaced keyword 'AuthMechs' > /home/user/.mbsyncrc:6: unknown/misplaced keyword 'SSLType' > /home/user/.mbsyncrc:7: unknown/misplaced keyword 'SSLVersions' > > If I comment out those lines, I get the following: > > Socket error from wtf.imap.com (##.##.##.###:993): Connection reset by peer > > I'm struggling to figure out what is going on and why. As far as I know, > nothing has changed with either my mail provider's IMAP server or my > MaildirStore. > > After reading through the list, I tried using a new Maildirstore, but I'm > still getting the same error. > > Any insights or suggestions? > > Thank you, > > David > > -- > dwrz|朱为文-- ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
unknown/misplaced keyword 'AuthMechs' (plus 'SSLType' and 'SSLVersions')
I had mbsync working perfectly until a recent server upgrade. Not sure if it matters, but I went from a Raspberry Pi 3 running Raspbian to a Dell Chromebox running Ubuntu server. Installed isync to the new sever, copied my .mbsyncrc, and now it's not working. I am getting the following errors when trying to run mbsync: /home/user/.mbsyncrc:5: unknown/misplaced keyword 'AuthMechs' /home/user/.mbsyncrc:6: unknown/misplaced keyword 'SSLType' /home/user/.mbsyncrc:7: unknown/misplaced keyword 'SSLVersions' If I comment out those lines, I get the following: Socket error from wtf.imap.com (##.##.##.###:993): Connection reset by peer I'm struggling to figure out what is going on and why. As far as I know, nothing has changed with either my mail provider's IMAP server or my MaildirStore. After reading through the list, I tried using a new Maildirstore, but I'm still getting the same error. Any insights or suggestions? Thank you, David -- dwrz|朱为文-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
