New answers tagged authentication
Found an answer to my own question. Cron does not set the environment variable USER. Thus, one solution is to run mbsync from inside a script like this: #!/bin/sh USER="YOURUSERNAME"; export USER mbsync gmail
It turns out that virtually all web pages out there the walk you through installing login_ldap, ypldap and ypind to do this leave out one thing. Because /etc/login.conf is a termcap-formatted file, you need to do 'cap_mkdb login.conf' for the login_ldap routines to actually see your configuration in the resulting /etc/login.conf.db file. This is different ...
Judging by aharris88's description, Gmail was blocking access to his account via mutt because mutt is using insecure connections when communicating with Gmail's servers. This means that your username and password are being sent across the local network and the Internet in an unencrypted form; generally a really bad idea, and something to be avoided whenever ...
Adding the --no-verify-peer option will fix the certification verification error. If you want to authentication, just add the user/pass to the url like https://user:firstname.lastname@example.org/path
I can recommend a solution by using Univention Corporate Server (UCS). It is a Debian-based Linux enterprise distribution that integrates an Actice Directory compatible domain using Samba 4. So this could become the centralized Active Directory you are speaking of. As to the LDAP issue, UCS also includes OpenLDAP. This means, you can integrate your existing ...
Top 50 recent answers are included