search for: testsaslauthd

...htest esimon at example.tld Authentication succeeded. Authenticated: esimon at example.tld (uid 501, gid 501) Home Directory: /home/vmail/domains/ Maildir: (none) Quota: (none) Encrypted Password: (none) Cleartext Password: (none) Options: (none) With testsaslauthd, i have Authentication [root at dc9f8f585 ~]# testsaslauthd -u esimon at example.tld -p edu+123* 0: OK "Success." But wen try with dovecot, the logs say Sep 21 13:51:31 dc9f8f585 dovecot-auth: ldap(esimon at example.tld): No password in reply Sep 21 13:51:31 dc9f8f585 imap-login: Abort...

Hello, I'm having trouble to get saslauthd running on a centos-5.3. I can't autheticate via testsaslauthd. Here's what I do using a fresh /etc/sasldb2: 1) start saslauthd in debug mode: saslauthd -d -a shadow -O /usr/lib64/sasl2/smtpd.conf -r -l 2) saslpasswd2 -c -a mail -u mail testuser 3) testsaslauthd -u testomat -p <mypassword> -s smtp -r mail shell output of testsaslauthd: 0: NO "...

Am 24.03.2019 um 10:01 schrieb Wojciech Puchar via dovecot: > solved by setting saslauthd to authenticate over imap - through dovecot > server. > testsaslauthd shows it works fine. > > but it seems sendmail strips domain name from entered login. No, it is saslauthd. Check the documention and see the "-r" parameter of saslauthd. Alexander

...slauthd is running and conigured >> according to your specs. So, I'm not sure what's missing. > > Still googling around and found some things that appear to be > missing from the sendmail config, but when I test saslauthd it > doesn't appear to be working. > > testsaslauthd -u username -p mypassword > 0: NO "authentication failed" Usually, testsaslauthd needs a service name. In this case, testsaslauthd -u username -p mypassword -s smtp If your password has any characters a shell might misinterpret (*, !, <, >, &, ...), make sure you enclo...

...root. The result on host: Jan 18 21:05:31 host libvirtd: 21:05:31.620: error : remoteDispatchAuthSaslStep:3691 : sasl step failed -20 (SASL(-13): user not found: no secret in database) on client (virt-manager gui): ... ('virtConnectOpenAuth() faild') .. I have tested it with tool "testsaslauthd" and their result: e.g.: # testsaslauthd -u root -p root 0: OK "Success." When i set it manually with saslpasswd: # saslpasswd2 -a libvirt root -p it works. Although I use, in the configuration of sasl, shadow, libvirt does not use it (i think so). Host: debian6.0.3 (squeez) libv...

On 03/08/2017 06:42 PM, Paul Heinlein wrote: > On Wed, 8 Mar 2017, Mark Weaver wrote: > > > On 03/08/2017 11:00 AM, Paul Heinlein wrote: > >> On Wed, 8 Mar 2017, Mark Weaver wrote: > >> > >> > Hello all, > >> > > >> > I've been googling my brains out since yesterday looking for > >> > up-to-date information on this

i've tried to replace saslauthd with dovecot sasl service stopped saslauthd daemon and added service auth { unix_listener /var/run/saslauthd/mux { mode = 0660 user = root group = mail } } so it will listen on the same socket. the effect with sendmail is as below Mar 23 21:23:29 <2.3> puchar dovecot: auth: Error: Authentication client not compatible with this server (mixed

...join - result okay and wbinfo -u i& wbinfo -g work wbinfo -a test%password wbinfo -K test%password work. I have /etc/pam.d/imap-test setup to loo like auth required pam_winbind.so auth required pam_deny.so account required pam_winbind.so account required pam_deny.so when i try testsaslauthd -u test -p password -s imap-test I get 0: NO "authentication failed" if I change imap-test config file to remove pam_winbind and use shadow and then retest with a shadow userid/password it works. I have tried setting debug for pam_winbind but I don't see anything Thanks Alex ---...

Am 2017-03-09 02:20, schrieb Mark Weaver: [ ... ] > Still googling around and found some things that appear to be missing > from the sendmail config, but when I test saslauthd it doesn't appear > to be working. > > testsaslauthd -u username -p mypassword > 0: NO "authentication failed" How is your saslauthd configured? Which backend does it use? For debugging purposes it is helpful not to start saslauthd as a service but to run it with parameter -d to see its output on stdout. Alexander

...it a minute before reading this e-mail. thank you works fine. almost ;) Why authenticating over imap takes so slow? my saslauthd runs like that /usr/local/sbin/saslauthd -a rimap -O 127.0.0.1 -n 0 -r imap server is handled by dovecot of course. to be sure it's not sendmail i've tried testsaslauthd testsaslauthd -u wojtek at puchar.net -p mypassword works but takes 5-10 seconds. server is lightly loaded. telnet 127.0.0.1 imap responds instantly. what to check?

> Why authenticating over imap takes so slow? > > my saslauthd runs like that > > /usr/local/sbin/saslauthd -a rimap -O 127.0.0.1 -n 0 -r > > imap server is handled by dovecot of course. > > to be sure it's not sendmail i've tried testsaslauthd > > testsaslauthd -u wojtek at puchar.net -p mypassword > > works but takes 5-10 seconds. server is lightly loaded. > > telnet 127.0.0.1 imap responds instantly. > > what to check? > > seems like saslauthd problem, tried telnetting to imap server and entering login c...

...hd running together so that I can get squirrelmail to work. I have accomplished this on several other servers and have relatively complete documentation on how to do this. What I am running into in this case has me baffled. If I start saslauthd as a service: # service saslauthd start And I try testsaslauthd -u cyrus -p test Then I see this: 0: NO "authentication failed" and in the syslog I see this:: saslauthd[5995]: do_auth : auth failure: [user=cyrus] [service=imap] [realm=] [mech=pam] [reason=PAM auth error] However, if I stop the system service: # service saslauthd stop an...

The dovecot instance set up with auth_realms and auth_default_realm variables and it is working well. In saslauthd configurations setting same variables giving configuration parsing error (I think it is not right way to configure kerberos realm in saslauthd). However testsaslauthd working without any problems even if I don't specify realm parameter from command line. On 03/10/17 06:17, Trever L. Adams wrote: > On 10/02/2017 07:00 PM, Anvar Kuchkartaev wrote: >> Hello I just finished setting up FreeIPA with Dovecot + Postfix + Saslauthd. I can easily access to...

...d > recompiling sendmail.mc. saslauthd is running and conigured according to > your specs. So, I'm not sure what's missing. Still googling around and found some things that appear to be missing from the sendmail config, but when I test saslauthd it doesn't appear to be working. testsaslauthd -u username -p mypassword 0: NO "authentication failed" >

...ecot: auth: Error: Authentication client not > compatible with this server (mixed old and new binaries?) > > > do i need to specify something while compiling sendmail to make it > compatible? > > solved by setting saslauthd to authenticate over imap - through dovecot server. testsaslauthd shows it works fine. but it seems sendmail strips domain name from entered login.

...endmail to authenticate with Active Directory. I have saslauthd configured > for Sendmail authentication, /etc/sasl2/Sendmail.conf: > > pwcheck_method: saslauthd > mech_list: LOGIN PLAIN > > and saslauthd is started as: /usr/sbin/saslauthd -a shadow > > This fails when doing testsaslauthd on a domain user. > > Is there a way to get sendmail to authenticate using domain credentials? > > My distro (Slackware) does not provide PAM, but I can get it if needed. > > --Mark I am doing this on Opensuse. I use samba for ActiveDirectory Domain integration, and use pam_winbi...

...ersion: 3 /etc/default/saslauthd START=yes DESC="SASL Authentication Daemon" NAME="saslauthd" MECHANISMS="ldap" MECH_OPTIONS="" THREADS=5 OPTIONS="-O /etc/saslauthd.conf -c -m /var/run/saslauthd -r" Testing the configuration works: # testsaslauthd -u myuser -p mypass 0: OK "Success." However, if I attempt to connect over the libvirt TCP connection I am denied: virsh -c qemu+tcp://my_vm_host/system nodeinfo error: authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: ) error: failed t...

...uid=%u)(mailAddress=%u))(status=active)) default_pass_scheme = PLAIN-MD5 When I try to connect using either KMail or SquirrelMail (which worked just fine before I switched schemes), the following error appears in /var/log/syslog: ldap(user at mydomain.tld): password mismatch But when I try 'testsaslauthd -u user at mydomain.tld -p longpassword' it authenticates just fine. I have the line 'password-hash {MD5}' in /etc/ldap/slapd.conf, and I used 'slappasswd -h {MD5}' to create the MD5 versions of the passwords. Dovecot is v. 0.99.11. If I can't figure out how to get...

...ldap_bind_pw: xxxx ldap_search_base: dc=domain,dc=com #ldap_filter: (|(mail=%u)(cn=%U)) ldap_filter: (&(|(mail=%u)(cn=%U)(mail=%U@%d))(accountActive=TRUE)(delete=FALSE)) PS: Removed my real server and search_base. Here is the test with saslauthd configuration: testsaslauthd -u novoemail01 -p teste123 0: OK "Success." And here is my dovecot-ldap.conf: hosts = myldapserver dn = uid=admin,ou=administrators,ou=topologymanagement,o=netscaperoot dnpass = xxxx ldap_version = 3 base = dc=domain,dc=com user_attrs = mail,,,,, user_filter = (&(object...

Hello I just finished setting up FreeIPA with Dovecot + Postfix + Saslauthd. I can easily access to mails using imap via dovecot with gssapi authentication and postfix also delivering mails very well. But I cannot send email from postfix using gssapi authentication (plain and login authentication working fine) because saslauthd is not specifying realm when requesting service from freeipa domain.