similar to: Cannot Authenticate via LDAP

Hello Christian, I tried what you suggested by adding "REFERALS off" to /etc/ldap/ldap.conf and restarting slapd and dovecot, but the error persists. On Tue, Jun 4, 2013 at 7:56 AM, Christian Wiese < christian.wiese at securepoint.de> wrote: > Hi Ron, > > I didn't had the time to check all logs but the error log. > First thing you should check if there are LDAP

Hi list, I try to run imaptest, but I get the following errors (as root): # ./imaptest copybox=Trash # or any other command in http://www.imapwiki.org/ImapTest/Examples Logi List Stat Sele Fetc Fet2 Copy Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 33% 50% 100% 100% 100% 100% 30% 5% 5% 0 0 0 0 0 0 0 0 0 0

When I define :db to be a different server than either :web or :app, and run "rake deploy". Switchtower will abort with an Net::SSH::AuthenticationFailed error. The version of Switchtower I''m using is 1.0.0 and the deploy task is the default supplied with Switchtowe. However, I dont have any problem when :db is changed to the same as :web and :app. -------------- next part

Awesome, thanks for the advice. Using the following now works... passdb { driver = static args = proxy=y password=doesnotmatter } Cheers. On Feb 15 2018, at 2:40 pm, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > On 15 February 2018 at 20:22 Travis Dolan <travis.dolan at gmail.com> wrote: > > > Hello, > > I have Director setup to proxy

Instructions at http://wiki2.dovecot.org/BasicConfiguration say the next thing to test after getting IMAP and Telnet working is to create a dummy user file with the following command: echo "$USER:{PLAIN}password:$UID:$GID::$HOME" > users And place it in /etc/dovecot and protect it appropriately. It was also edited to change the plain-text password from `password' to what it

Hello, I have Director setup to proxy requests to backend servers. This works fine when using "standard" username/passwords. I am not try to enable the use of the Dovecot Master user through Director into the backend servers. a.) username is being sent as masteruser*username b.) request hits the proxy and authenticates, and then is passed to the backend servers and fails auth. - logs

thank you for guidance, just to recap the issue was about squirrelmail giving a wrong message : "connection dropped by imap server" instead of "invalid user or password" as advised i connected using command line on both my old and new servers, and have posted the details including the output of dovevcot -n. 1) command prompt login. i put wrong password telnet x.x.x.x 143

I''m having trouble getting Capistrano to work on Dreamhost. I seem to be having problems logging in, but I can ssh fine to my dreamhost server from this machine. This doesn''t seem like a dreamhost specific thing to me, but I''m kind of stuck. Here''s the exception I get from "cap setup":

> On 15 Feb 2018, at 22.16, Travis Dolan <travis.dolan at gmail.com> wrote: > > It would look as though the changes have now negatively affected a "normal" user from logging in. > > > telnet host 143 > > a login username password > > > a NO [AUTHENTICATIONFAILED] Authentication failed. > > > telnet host 143 > > 1 login

On Mon, 15 Jun 2015 17:22:13 +0200, you wrote: >> Now, when I telnet 127.0.0.1 143 and attempt to log in with the >> string: >> >> a login <any username> <any password> >> >> whether it's one in my users file or not, I get: >> >> a NO [AUTHENTICATIONFAILED] Authentication failed. >> > >Logs might give you a clue what

There are two rather clear issues with the state of authentication failure delays. First, the delay length isn't what was (presumably) intended. Second, there is a new way of doing failure delays in Dovecot 2 which was added *in addition to* the old method, rather than replacing it. As a result delays may not be the expected length and settings don't have the expected effect. First, the

Hello, I hope that this mailing list is "alive", since I am looking for a solution for my problem for a long time. I would like to migrate my existing dovecot installation from mysql to pgsql. But I have problems with the passwords when using pgsql. The existing and working mysql-based installation looks like this: dovecot-sql.conf.ext: driver = mysql default_pass_scheme =

I install deprec with gem install deprec but when i write deprec --apply-to . this message display to me " ''deprec'' is not recognized as an internal or external command, operable program or batch file. " what can i do? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on

Hello friends! I am getting following error while using $ cap deplot:setup * executing `deploy:setup'' * executing "mkdir -p ~/public_html/simak-in ~/public_html/simak-in/releases ~/public_html/simak-in/shared ~/public_html/simak-in/shared/system ~/public_html/simak-in/shared/log ~/public_html/simak-in/shared/pids" servers: ["simak-in"] connection failed for:

Hello, In the past (older dovecot versions) I've tuned the SQL "password_query" of our mail server so that when the user has the account blocked for some reason (expired, need password change, etc.) the query returns nologin=1 and a verbose reason like reason="Your account is expired please change the password" and it worked very well with IMAP clients. I'm now

It would look as though the changes have now negatively affected a "normal" user from logging in. telnet host 143 a login username password a NO [AUTHENTICATIONFAILED] Authentication failed. telnet host 143 1 login devteam*masteruser at example.com password 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS

On an Ubuntu Server 12.04 system with Dovecot 2.0.19 I am having some trouble with the Dovecot passwords. I am finding this in the logs when I unsuccessfully try to log in: Jul 07 08:13:25 auth-worker: Debug: pam(user at someDomain.com,212. 179.241.14): lookup service=dovecot Jul 07 08:13:25 auth-worker: Debug: pam(user at someDomain.com,212.179.241.14): #1/1 style=1 msg=Password: Jul 07 08:13:27

Thank you for the reply. In old server (production1), I have changed like this for passdb. rest all i kept the same. passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes #pass = yes } passdb { driver = passwd-file args = username_format=%u /etc/dovecot/passwd } Now I am getting the below Authentication error from

Thank you for the response. So, both password files (master and regular user credentials) have the same contents in this scenario, correct? -Kishore On Mon, Aug 3, 2020 at 11:42 PM Joseph Tam <jtam.home at gmail.com> wrote: > On Mon, 3 Aug 2020, Kishore Potnuru wrote: > > > =============== > > Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there

I''m trying for the first time to use capistrano and things were going well until I tried to run ''cap setup''. This is what I get... cap setup loading configuration /opt/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/recipes/standard.rb loading configuration ./config/deploy.rb * executing task setup * executing "mkdir -p -m 775