similar to: Googling: dovecot: auth-worker(default): pam_start() failed: Critical error - immediate abort

Hi, has anyone seen this issue before as I have not. I'm a long time dovecot user and I don't see anything in the config that should cause this. The mail.log gets hit a lot of times with this same log message: dovecot: imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections) I have noted that it is more evident when I try to mass delete many

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

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

Hello dovecot gods, after using Postfix with webmail for 8 years the new gen of email smartphones forces me to consider using IMAP. Actually, for several months I was successfully using IMAP. I believe the reason why IMAP worked previously (before migrating to the Cloud) the hosting server and the client machines were considered local by the system. Now, I have moved everything to a Cloud service.

Hi list! Need your advice! Im looking for a way to do this: I have one SAMBA+LDAP+DNS+DHCP (DC) server running fine in a debian box, my problem now is that a need to have 2 different logon scripts, one is a specific user only, let's say user1 when this user login in winxp client machine the server send to it a script loginA.cmd, and when all user of group "Domain

>> 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:

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

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

Hi, I'm working on a setup of dovecot 2 + netqmail + vpopmail 5.5 but auth doesn't works :( dovecot -n # 2.0.1: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 2.6.35.1-rscloud x86_64 Ubuntu 10.04.1 LTS auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no log_path =

Just setup a new server on the weekend with Ubuntu 8.10 beta, and Dovecot 1.1.4. Every now and then, the IMAP server dies, and won't let users authenticate. It happens about once or twice a day. In /var/log/mail.log, you can see dovecot complaining about critial errors: Oct 21 14:46:16 tachikoma dovecot: imap-login: Login: user=<jason>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS

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

Package: logcheck-database Version: 1.3.13 Severity: minor Change the rule to clean "Generated config for" from "seconds" to "s". Corrected version: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ bcfg2-server\[[0-9]+\]: Generated config for\ [._[:alnum:]-]+ in [0-9.]+ s$ -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable')

Hi, Auth always crash (segfault) using vpopmail backend. Any idea ? vpopmail 5.5.0 os: ubuntu 10.04 on rackspace cloud # dovecot -n dovecot -n # 2.0.1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.35.1-rscloud x86_64 Ubuntu 10.04.1 LTS auth_debug = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no first_valid_uid =

I append a patch against openssh-3.5p1.tar.gz which adds a config option PAMServiceName. The option allows one to specify the PAM service at runtime in the config file rather than using __progname or having it hardwired to SSHD_PAM_SERVICE at compile time. I expect this to be useful if one wants to run multiple instances of sshd using different PAM configurations. With this patch

Hello, We just switched from UW to Dovecot for our mail server. The transition went smoothly, except we have some users complaining about their email clients re-downloading mail or getting multiple copies of emails. When we go into their accounts, we only see one copy of the email, so I'm assuming there's something odd in the communication between their client and us that's causing