similar to: vmailmgr user database

Hello folks, Time ago I worked on a patch for dovecot to work with vmailmgr http://mij.oltrelinux.com/net/dovecot-qmail-vmailmgr/ The patch was required because, despite vmailmgr complies with the checkpassword interface supported by dovecot, dovecot snips the mailbox directory returned by the authentication module at colon characters ':'. Incidentally, vmailmgr maps any

hello now that dovecot supports authentication with checkpassword-compatible modules, I tried to get it working for IMAP on a qmail + vmailmgr server. For a subtle detail, while claiming to be "a drop-in replacement for the standard checkpassword", checkvpw (auth module for vmailmgr) is not "drop in". It actually expects 2 args on its command line, not 1. So, a wrapper

hello some times ago I posted some patches to workaround vmailmgr not fitting into dovecot's passdb-checkpassword authentication module. Yesterday I spent some spare time for carrying out a cleaner solution for this problem. Check out these patches. If you're not interested in merging them, I will make them available at the same page I used for the former solution [

Dear dovecot maintainers: I'm using SSL client certificates together with a checkpassword scripts to authenticate our users. My problem is: In the checkpassword script the AUTH_USER environment variable will either contain the username that was configured in the mailclient (if auth_ssl_username_from_cert=false) or the username from the certificate (if auth_ssl_username_from_cert=true). I

Dear Dovecot-Team, I am implementing a plugin (for the pop3/imap process) that requires some data to provided from the authentication phase (a derivative of the password). For that, I have now implemented a passdb plugin that generates this data and I would like to "pass" this data down to the mail process (pop3/imap) via extra_fields in the reply of the authentication. The general idea

hi, does dovecot supports vmailmgr authentication? any recomended reading? and, in a vmailmgr context, what are the benefits of dovecot over courier-imap or bincimap? Best regards, Alejandro Mery

I'm trying to hack together a new authentication back-end and I wanted to know if it's possible to pass values from passdb to userdb in the auth_request structure at authentication time. I modified struct auth_request in auth-request.h to contain a new variable and it gets set properly in my passdb, however the value is not there when checking for it userdb. I'm very novice when it

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them

https://bugzilla.samba.org/show_bug.cgi?id=10445 Summary: flag to suppress link_stat error messages Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mij at bitchx.it

Hi, First, I'm not sure if dovecot should alter this, but it seems vpopmail writes the IP into the 'remote_ip' field instead of the auth type. Dovecot still writes the auth type.? I want both. So I modified my vpopmail install to write an additional field into the lastauth table.? My custom vpopmail writes the remote IP into remote_ip, and the auth type into a 'type'

We brought up a test cluster to investigate GlusterFS. Using the Quick Start instructions, we brought up a 2 server 1 brick replicating setup and mounted to it from a third box with the fuse mount (all ver 3.4.1) # gluster volume info Volume Name: mailtest Type: Replicate Volume ID: 9e412774-b8c9-4135-b7fb-bc0dd298d06a Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks:

dovecot seems to have an issue with :'s in pathnames: imap(test.user): Fatal: Failed to create storage with data: /home/ hosted/example.com/users/test:user This causes a bit of a problem with vmailmgr since it, by default, replaces .'s in maildir path with :'s. I'm curious as to why :'s in paths are an issue? Do they have special meaning to dovecot? --- Lars Hansson

Hi all, I've a problem with prefetch userdb function on 1.0.alpha4 ? I get this : Error: auth(default): ldap(mylogin,10.3.245.xxx): Multiple password replies Info: auth(default): ldap(mylogin,10.3.245.xxx): base=dc=boursorama,dc=fr scope=subtree filter=(&(objectClass= boursoramaMailAccount)(mailInternalAllowedProtocol=imap)) fields=uid,userPassword An ldapsearch with the same

Hallo I am very impressed from this howto's: 1) Postfix-Cyrus-Web-cyradm-HOWTO (mysql) http://www.delouw.ch/linux/postfix.phtml 2) Pop-Toaster using Qmail-Vmailmgr-Courier-SquirrelMail http://qvcs-guide.sourceforge.net/ (this work for me) I hope to build anything like above, but with Dovecot: [Postfix-tls-smtpauth-Dovecot-Mailadmin*-MySQL-SquirrelMail-https] Postgresql is ok for

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

Hi Timo I use LDAP auth on a system with around 2000 email account. I use dual OpenLDAP servers. I haven't noticed a leak of memory. Is there any more information and I will have a look to see if I can see anything that might help. Is it only affecting certain machines or all? Regards Daniel Rowe Date: Mon, 16 Oct 2006 02:39:26 +0300 From: Timo Sirainen <tss at iki.fi> Subject:

OpenBSD 3.6 -current (i386) dovecot-1.0-test51 I'm now getting this error message as soon as I start dovecot: "Authentication client 0 not compatible with this server (mixed old and new binaries?)" Here's the process I'm using: ./configure --sysconfdir=/etc \ --with-ssl=openssl \ --with-pam=NO \ --with-ldap=no \ --with-vpopmail=no \

not possible make operation with dovecot version 2.x as was possible in version 1.x: requisites description: connect to dovecot service on IP1 - dovecot must serve users that related to domain1 located in database1 connect to dovecot service on IP2 - dovecot must serve users that related to domain2 located in database2 login must be with username that form not as "user at domain" but

My log is full of blocks like this: auth(default): pam(?): PAM child process 13576 timed out, killing it auth(default): PAM: kill(13576) failed: No such process Often, this is recorded for several pids at once. Occasionally, there's a single burst when a virtual user logs in, immediately before pam_authenticate() fails and checkpassword is executed. When this happens, pam() contains the