similar to: Dovecot dies with PAM error?

Hi, I am running dovecot with postfix and OTRS2 on a fresh Ubuntu 8.10 Server system. OTRS2 is configured to poll new email to otrs-incoming at localhost via POP3 every 5 minutes. It works, but after approximately 20 hours it suddenly stops working and only a restart of dovecot helps. The outage starts at different times during night (00:15 on Thursday, 1:15 on Friday, 3:20 on

Hi, I'm using dovecot 1.1.3 on FreeBSD 6.3, x86, files are on NFS, except control and index files, which are local, on UFS2. It's moderately loaded, there are usually not more than 30 clients simultaneously. dovecot runs fine for 3-10 days, then people can't connect any more, and dovecot says: Nov 18 13:20:44 dizzy dovecot-auth: pam_ldap: ldap_simple_bind Can't contact LDAP

I would guess this is unlikely to be dovecot's fault, but I'm wondering if anyone has any ideas of what might have happened based on the evidence. My best guess is some kind of resource limit was reached but I don't see any evidence in the logs, and the condition is now gone. Suddenly this morning, one (and only one) of my dovecot servers decided to start failing all logins since

Hello List, I have a question about dovecot-1.1.0-beta3 but first I'll ramble a little bit: Recently I upgraded a 0.99 installation of dovecot to 1.0.5. All went relatively smoothly until the dovecot-auth process began returning "out of memory" after a day. There is a rather large user base here. The current setup is using passdb pam with blocking=yes, with pam_ldap.so handling

Hi all! I`m using dovecot for a while with no problems. Some days ago it started to delay the authentication until the timeout. syslog... Oct 3 09:00:10 coan dovecot: auth(default): pam(rodrigo.botan,121.120.119.179): pipe() failed: Too many open files Oct 3 09:00:11 coan dovecot: auth(default): pam(katia,121.120.200.97): pipe() failed: Too many open files Oct 3 09:00:11 coan dovecot:

>> passdb { >> driver = pam >> } >> passdb { >> driver = pam >> name = pam >> } > Are those two passdb blocks intentional? > > One of them is missing the name parameter. doh. first removed. Aug 3 06:49:23 psg auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid facility Aug 3 06:49:23 psg dovecot:

While configuring my server with dovecot I noticed that the PAM authentication driver does not support the username_format option as does the password file driver. This didn't seem too hard to implement so I through together a patch. As you can see in the attached patch I only modify the username sent to PAM. Despit doing this I run into the domain lost

Hello, Here's the situation I'm facing : I'm running OpenSSH on a server. On a gateway, I forward TCP:22 to the server TCP:22. So far, so good. I can log in from inside the lan by connecting using standard SSH port, or from the other network through the gateway. Now, I'd like a different configuration for connections from the outside. I start another SSHd on the

# dovecot --version 2.2.31 (65cde28) on freebsd 64 10.3 system converted to dovecot 2 against my will and consuming a lot of time sorting it out. i am glad google does not charge. have spent two hours on this one alone; and undoubtedly it is my st00pidity. so excuse my desperate posting to lazynet. cram-md5 works, pam not so much Aug 3 06:06:35 psg auth: in openpam_parse_chain():

I'm having trouble getting dovecot to compile with PAM support. Output from the configure command says its checking for pam_start in -lpam .... no. I've checked, there is a pam_start in there. So how can I force configure to see what its looking for? I've tried the --with-pam switch and that doesn't work. I'm trying to build the latest RC7 on a Debian Sarge box. Regards

Hello everybody, I try to compile dovecot 2.1.7 with a customized --prefix setting and --with-pam . Although I installed libpam into the same --prefix, dovecot does not find it: checking for pam_start in -lpam... no configure: error: Can't build with PAM support: libpam not found The same or a similar problem seems to have appeared 4 years ago:

>From /var/log/auth.log (Dovecot 1.1.4 on Ubuntu 8.10): Feb 10 08:29:06 home dovecot-auth: PAM unable to dlopen(/lib/security/pam_ck_connector.so): libdbus-1.so.3: failed to map segment from shared object: Cannot allocate memory Feb 10 08:29:06 home dovecot-auth: PAM adding faulty module: /lib/security/pam_ck_connector.so English, please? :) Strangely, it seemed to disappear after increasing

Hi there, Other auth modules (eg passwd-file) allow a username_format to be specified, but not the PAM module. The use-case, is where I want a static userdb configuration which takes the domain into account but still want to use PAM for authentication, eg: userdb { driver = static args = uid=8 gid=12 home=/mnt/storage/mail/vhosts/%d/%n } passdb { driver = pam args = username_format=%n

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Running Dovecot 1.1.3 and after dovecot has been running for awhile it will just stop authenticating. Only fix is to stop and restart dovecot. Here is the errors in the logs: ct 4 09:34:32 goku dovecot: [ID 107833 mail.info] auth-worker(default): pam(KVogel22,74.125.78.25): lookup service=dovecot Oct 4 09:34:32 goku dovecot: [ID 107833

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Been running dovecot 1.1.2 for about a month now. I Have strange issue that I have not been able to trouble shoot. What I'm seeing is that dovecot runs along just fine for about 4 days, and then it will just stop authenticating everyone (IMAP and POP). No errors in the logs other than all authentication attempts comes out as password mismatch.

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz.sig Hopefully the next release can be v1.1.beta1. I'm not aware of any major problems and I think I'm pretty much done with new features (except for dbox). The largest changes since alpha1: * Removed THREAD indexing. It's a bit buggy and I think

Howdy, Googling: dovecot: auth-worker(default): pam_start() failed: Critical error - immediate abort dobbeltganger dovecot: auth-worker(default): pam(user,1.2.3.4): lookup service=dovecot dobbeltganger out of memory [4543] returns just 3 references. Examining memory server side reveals use of virtual memory but not 100% OS: Ubuntu 14.04 client 10.04 server-side. Email client: Thunderbird

Hi, I'm new here in the list so Hello to everyone! I'm compiling dovecot 1.0.10 with pam support in SLES 9 but i'm getting errors in config.log and it won't compile with pam support. Here are the results: s1:~/dovecot-1.0.10# ./configure --with-pam | grep pam checking for pam_start in -lpam... no and in config.log: configure:28830: checking for pam_start in -lpam

Fellow Dovecot'ers, I've -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin at

Hi all I have two samba server and I would like to set up one of them as a central authentication server (server a) and the other one (server b) to send username/password requests to server a I have followed the instruction on http://www.skippy.net/linux/2000/smb-howto.html However it doesn't seem to function properly. Has anyone been able to achieve remote authentication What minimum