I have a postfix/dovecot mail server.
On centos6 works great,sso with gssapi on linux and windows clients.
On Slackware i have problems,Linux clients(thunderbird and mutt) connect ok,but not windows clients.
on logfile only this
Auth with normal password work ok,only gssapi doesn't work
I have installed all packages required(openldap,kerberos,cyrus-sasl)
but when i did ldapsearch -Y gssapi return
ldapsearch -Y gssapi -H ldap://ldapserver-d -1 cn=prova
ldap_sasl_interactive_bind_s: Unknown authentication method (-6)... (0 Replies)
We have two HP-UX machines, both are B.11.31.
When I FTP from the HP-UX boxes to a remote IBM server,-
Connected to xxxx.
220-FTPD1 IBM FTP CS V1R12 at R2, 12:24:39 on 2013-08-30.
220 Connection will close if idle for more than 15 minutes.
HP-UX 2:... (2 Replies)
While trying ftp from newly setup Linux box it is giving following error.
GSSAPI error major:Unspecified GSS failure.Minor code may provide more information
GSSAPI error minor:Unknown code krb5 195
GSSAPI error:initializing context
GSSAPI authntication failed
504 AUTH... (1 Reply)
Configure ldap client:
I have configured my ldapclient with the AuthenticationMethod=simple and with the credentialLevel=proxy. However, as soon as i want to set the AuthenticationMethod=sasl/GSSAPI, and credentiallevel=self, then it fails to configure. Kerberos is already setup successfully. The... (0 Replies)
I've been using Sendmail for several months - no problem. Shortly, a need appeared to provide remote access to mail - POP3/IMAP. I worked a little with Dovecot, and there was some success, than I read that Cyrus is cooler or so, like better for production sites because it makes links and not copies... (0 Replies)
These are the warning messages I am getting but the FTP works fine.How do I get rid of these?
220 FTP server (SunOS 5.8) ready.
500 'AUTH GSSAPI': command not understood.
500 'AUTH KERBEROS_V4': command not understood.
KERBEROS_V4 rejected as an authentication type (0 Replies)
Discussion started by: csviking
LEARN ABOUT DEBIAN
DOVEADM-AUTH(1) Dovecot DOVEADM-AUTH(1)NAME
doveadm-auth - Test authentication for a user
doveadm [-Dv] auth [-a auth_socket_path] [-x auth_info] user [password]
The auth command can be used to test the authentication for the given user.
Global doveadm(1) options:
-D Enables verbosity and debug messages.
-v Enables verbosity, including progress counter.
Command specific options:
This option is used to specify an absolute path to an alternative UNIX domain socket.
By default doveadm(1) will use the socket /var/run/dovecot/auth-client. The socket may be located in another directory, when the
default base_dir setting was overridden in /etc/dovecot/dovecot.conf.
auth_info specifies additional conditions for the auth command. The auth_info option string has to be given as name=value pair.
For multiple conditions the -x option could be supplied multiple times.
Possible names for the auth_info are:
The service for which the authentication lookup should be tested. The value may be the name of a service, commonly used with
Dovecot. For example: imap, pop3 or smtp.
lip The local IP address (server) for the test.
rip The remote IP address (client) for the test.
lport The local port, e.g. 143
rport The remote port, e.g. 24567
user The user's login name. Depending on the configuration, the login name may be for example jane or email@example.com.
Optionally the user's password. doveadm(1) will prompt for the password, if none was given.
This example demonstrates an imap authentication test for user john, assuming the user is connected from the host with the IP address
doveadm auth -x service=imap -x rip=192.0.2.143 john johns_password
passdb: john auth succeeded
Report bugs, including doveconf -n output, to the Dovecot Mailing List <firstname.lastname@example.org>. Information about reporting bugs is avail-
able at: http://dovecot.org/bugreport.html
SEE ALSO doveadm(1), doveconf(1)Dovecot v2.1 2010-06-09 DOVEADM-AUTH(1)