similar to: saslauthd

Displaying 20 results from an estimated 500 matches similar to: "saslauthd"

2011 Mar 31
1
POP3 connection issue & SASL not compiled in
After I've configured dovecot for SSL according to the info given in the link below: ? ?https://access.redhat.com/kb/docs/DOC-6671 (tried both POP3 & secure POP3 & got the same result) I tested POP3 access from my unblocked (no firewall rule for outgoing) broadband PC's Outlook to connect to the postfix/dovecot server & got the following : Tasks ? ? ? ? ? ? ? ?
2011 Jun 20
1
Error
I tested POP3 access from my laptop's Outlook which is on the same subnet as the dovecot/postfix server (so there's no firewall in between them & was able to get the emails in Outlook with following statuses shown when "Test Connection" is clicked: > Tasks Status > ===================== ========
2008 Jan 15
3
DO NOT REPLY [Bug 5203] New: rsync aborts because of glibc invalid pointer
https://bugzilla.samba.org/show_bug.cgi?id=5203 Summary: rsync aborts because of glibc invalid pointer Product: rsync Version: 2.6.9 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:
2006 Dec 20
0
Unable to authenticate with Pam
Hi, I'm trying to solve this problem for several weeks and this is a SOS! I've 2 Debian server runing heartbeat and drbd for high availability. I'm using LDAP for user database, PAM for authentication and Dovecot for Pop3s access. On the master server all is fine. If dovecot is started on the slave server (instead of the master) it does not accept to authenticate with the
2005 Sep 19
1
pam and sasl2-sample-server failure
I'm setting up a postfix server using "The Book of Postfix". In ch 15 there is a section on testing saslauthd which I can't get to work. I can get it to work using shadow password authentication, but it fails on pam. I don't kow squat about troubleshooting pam. Any PAM wizzes out there that can help? I saw a unrelated post talking about something needing to be in the pam
2017 Oct 03
1
Postfix + saslauthd SASL With Kerberos (FreeIPA) unable to send mail
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,
2017 Apr 24
0
Issues with exposing USB serial dongle to guest VM
Hi. I have Centos 7 (updated) running as my host, and I?m using Qemu and KVM, version 2.0.0 and 2.6.0. I have a Trendnet TU-S9 USB serial dongle attached to the host, which uses the Prolific 2303 chipset. I blacklisted the pl2303 driver so the host doesn?t grab the device, and want to expose it to the guest. On the client, I see 2 USB hubs (3.0 and 2.0), and I see 2 USB endpoints (even though
2017 Oct 03
2
Postfix + saslauthd SASL With Kerberos (FreeIPA) unable to send mail
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.
2010 Sep 19
1
linking problems of dovecot 2.0.3
Hello, I'm currently packaging dovecot 2.0.3 under Mandriva Linux. It has been using LDFLAGS="-Wl,--as-needed -Wl,--no-undefined" for shared libraries for over two years[1]. And I've found there are lots of linking problems with dovecot 2.0.3. After some investigation, I've made small patch regarding dovecot 2.0.3, posted here:
2000 Jan 19
1
New liblogin release
Hi, I've just put a new version of liblogin[1] on my website. This version is fully tested on Linux RH6, OpenBSD, HPUX10.20 and Solaris 2.6. It may well work on other systems now, as it supports login(), [uw]tmp, [uw]tmpx, and lastlog (filemode only.) If you're feeling adventurous, please check out the web page and try it out. By 'tested', I mean that the library is known to
2009 Oct 06
8
compiling issue 1.2.6 - Solaris
Heya, I am expiriencing compiling issues on Solaris 8 and Solaris 10 boxes with dovecot 1.2.6. On Solaris 8 the compiler is gcc 64bit 3.2.2, on Solaris 10 gcc 3.4.3. On both systems the compiling fails with: /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2
2004 Jun 22
0
Update: Compile error
Offending lines in src/login-common/ssl-proxy-gnutls.c 519 ret = gnutls_certificate_set_dh_params(x509_cred, dh_params); 520 if (ret < 0) 521 i_fatal("Can't set DH parameters: %s", gnutls_strerror(ret)); 522 ret = gnutls_certificate_set_rsa_params(x509_cred, rsa_params); 523 if (ret < 0) 524 i_fatal("Can't set RSA parameters: %s",
2019 Sep 11
0
Increase logging verbosity of saslauthd?
On Wed, Sep 11, 2019 at 01:34:27PM +1000, Jobst Schmalenbach wrote: > CentOS 7.X, sendmail.x86_64 8.14.7-5.el7, cyrus-sasl.x86_64 2.1.26-23.el7 > > There are conflicting message on how to increase the logging of saslauthd. > > I know I can do this: > /usr/sbin/saslauthd -d -n0 -m /var/run/saslauthd -a pam > > but that requires a terminal as saslauthd logs the output
2010 Jul 27
2
Cant compile managesieve 0.11.11 on Solaris10
hi, i can't compile managesieve-0.11.11 on Solaris 10 against Sieve 0.1.17 and Dovecot 1.2.13: [...] gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -o managesieve-login client.o client-authenticate.o managesieve-capability.o managesieve-proxy.o cmd-noop.o
2000 Jan 31
0
New liblogin 0.3alpha
FYI a new version of liblogin, 0.3alpha, is up on my website at http://dspace.dial.pipex.com/andre.lucas/liblogin.html This version fixes a few bugs and has implementations for the full API, including 'get last login time' support, even for systems without lastlog. New OpenSSH patches against 1.2.2 are also available, to enable the last login time features. Again, the function (in
2005 Oct 06
1
saslauthd/dovecot/root
Hi, I am using SMTP-AUTH over TLS with sendmail, to allow remote users to authenticate and send mail via my server, and this uses saslauthd to authenticate users. I have set up saslauthd with the "MECH=rimap" mechanism, so it uses the local IMAP server, Dovecot, for authentication. I want to do this because Dovecot is set up to use /etc/passwd for user credentials (so I don't
2008 Jun 16
2
Installation Problem -
Hello, I have installed dovecot Version 1.0.14 on Centos Linux 4.6. When I do ./configure --with-pam, I get below mentioned error. Please help Best Regards Kaushal ---------------- Error ---------- Making all in imap-login make[3]: Entering directory `/tmp/dovecot-1.0.14/src/imap-login' /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes
2019 Sep 12
0
Increase logging verbosity of saslauthd?
On Sep 11, 2019, at 7:34 PM, Jobst Schmalenbach <jobst at barrett.com.au> wrote: > I have tried that as well before I asked for help, however systemd refuses to accept this as the "-d" keeps saslauthd in foreground. > Systemd kills the process after a minute as systemd cannot see that required PID's. You?ll need to also create an
2019 Sep 11
3
Increase logging verbosity of saslauthd?
Hi CentOS 7.X, sendmail.x86_64 8.14.7-5.el7, cyrus-sasl.x86_64 2.1.26-23.el7 There are conflicting message on how to increase the logging of saslauthd. I know I can do this: /usr/sbin/saslauthd -d -n0 -m /var/run/saslauthd -a pam but that requires a terminal as saslauthd logs the output to STDOUT, this is not what I want. I would like to have it started as a daemon and verbosity of
2008 May 25
1
saslauthd for sendmail SMTP relay
Hi, I'm running a Centos 5.1 server that uses saslauthd to allow sendmail SMTP relaying for some clients. saslauthd is configured to use method "shadow" to lookup the username / password directly from /etc/shadow. This setup has been working for several month now, but is broken since last Monday. I haven't changed anything neither on the server nor on the clients. Now whenever a