- dovecot - dovecot.org

[Dovecot] Dovecot 2.1 mbox + maildir
by Alan Brown 29 May '12

29 May '12

What syntax is needed to make this work? The 2.0 wiki recomendations don't work - I can see the inboxes or the folders but not both at once and there are lots of error messages about prefix clashes if I simply use the existing 2.0.20 conf file on 2.1.6 The layout I have is: Inboxes in mbox format - /var/spool/mail/%u Folders in maildir format - /var/spool/imap/%u/Maildir/ Control and index folders are under separate trees (/var/spool/control & /var/spool/indexes) There's also a mbox area mainly for moving oversized inboxes (/var/spool/imap/%u/mbox/ - prefixed as OLD) Presumably I'm not the only one who's had problems of this type? Thanks in advance for any help Alan

2 1

[Dovecot] Bug report - crash on group lookup
by Peter Meier 29 May '12

29 May '12

Hi I was doing some migration from a 1.2 installation to a 2.1. While testing my new installation dovecot crashed at two test-cases constantly with with a "Panic: Trying to allocate 0 bytes" message. Both times it was because I was using a wrong group (or none) in my config. The output I got by dovecot was not that helpful. I only figured it out, that it has something to do with the group by looking at the code, to figure out where the stacktrace I got could come from. Unfortunately, I don't remember one of the examples anymore that correctly (except that it was also a group configuration related issue). The other example, was that I was testing the quota warning scripts: Normal delivery worked fine, but as soon as dovecot should send a quota warning, after the mail got already delivered, I received said panic. For the MTA the mail delivery failed (-> bounce), although the LDA already delivered the mail, but failed in post processing (sending the quota warning). My fix was to add: unix_listener quota-warning { group = mail mode = 0660 } to the quota warning service. The LDA process has an own user per mailbox and the mail group. It looks to me as it would panic by looking up the user of the lda process, but that's pure guess. Attached is a debug output and the configuration that triggered the problem. I see two problems: 1. Don't panic while "looking" up a group 2. Give a meaningful error messages. If you have any further questions, please let me know. ~pete ==> /var/log/dovecot/debug.log <== May 25 12:19:50 lda: Debug: Loading modules from directory: /usr/lib/dovecot May 25 12:19:50 lda: Debug: Module loaded: /usr/lib/dovecot/lib10_quota_plugin.so May 25 12:19:50 lda: Debug: Module loaded: /usr/lib/dovecot/lib90_sieve_plugin.so May 25 12:19:50 lda: Debug: auth input: dovecot(a)example.com home=/var/mail/dovecot(a)example.com uid=41407 gid=12 quota_rule=*:storage=1M May 25 12:19:50 lda: Debug: Added userdb setting: plugin/quota_rule=*:storage=1M May 25 12:19:50 lda(dovecot(a)example.com): Debug: Effective uid=41407, gid=12, home=/var/mail/dovecot(a)example.com May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota root: name=User quota backend=maildir args= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=* bytes=1048576 messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=INBOX.Trash bytes=+104857 (10%) messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=996147 (95%) messages=0 reverse=no command=quota-warning 95 dovecot(a)example.co, May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=838860 (80%) messages=0 reverse=no command=quota-warning 80 dovecot(a)example.com May 25 12:19:50 lda(dovecot(a)example.com): Debug: Namespace inbox: type=private, prefix=INBOX., sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/dovecot@example.com May 25 12:19:50 lda(dovecot(a)example.com): Debug: maildir++: root=/var/mail/dovecot(a)example.com/mail, index=, control=, inbox=/var/mail/dovecot(a)example.com/mail, alt= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota root: name=User quota backend=maildir args= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=* bytes=0 messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=INBOX.Trash bytes=0 (10%) messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=0 (95%) messages=0 reverse=no command=quota-warning 95 raw mail ur May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=0 (80%) messages=0 reverse=no command=quota-warning 80 raw mail ur May 25 12:19:50 lda(dovecot(a)example.com): Debug: none: root=, index=, control=, inbox=, alt= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Destination address: dovecot(a)example.com (source: -a parameter) May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: user's script path /var/mail/dovecot(a)example.com/dovecot.sieve doesn't exist (usinglobal script path in stead) May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: using sieve path for user's script: /var/lib/dovecot-sieve/default.sieve May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: opening script /var/lib/dovecot-sieve/default.sieve May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: script binary /var/lib/dovecot-sieve/default.svbin successfully loaded May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: binary save: not saving binary /var/lib/dovecot-sieve/default.svbin, because its already stored May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: executing script from /var/lib/dovecot-sieve/default.svbin May 25 12:19:51 lda(dovecot(a)example.com): Debug: quota: Executing warning: quota-warning 80 dovecot(a)example.com ==> /var/log/dovecot/deliver-errors.log <== May 25 12:19:51 lda(dovecot(a)example.com): Panic: Trying to allocate 0 bytes May 25 12:19:51 lda(dovecot(a)example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xbd4e70] -> /usr/lib/dovecot/libdoveco t.so.0(default_fatal_handler+0x43) [0xbd4f63] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd4784] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd 241d] -> /usr/lib/dovecot/libdovecot.so.0(t_malloc0+0x29) [0xbd2619] -> /usr/lib/dovecot/libdovecot.so.0(restrict_get_groups_list+0x43 ) [0xbef183] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd2b39] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd2dd2] -> /usr/lib/dovecot/libdove cot.so.0 [0xbd34c6] -> /usr/lib/dovecot/lib10_quota_plugin.so(quota_transaction_commit+0x5ff) [0xeeeaff] -> /usr/lib/dovecot/lib10_quo ta_plugin.so [0xef3f6c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x42) [0xc922d2] -> /usr/li b/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0x33) [0xc92323] -> /usr/lib/dovecot/libdovecot-sieve.so.0 [0xd4cfa4] -> /usr/lib/dovecot/libdovecot-sieve.so.0 [0xd44821] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x2d1) [0xd44b41] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x69) [0xd550f9] -> /usr/lib/dovecot/lib90_sieve_plugin.so [0x11211c] -> /usr/lib /dovecot/libdovecot-lda.so.0(mail_deliver+0x4c) [0x843e1c] -> /usr/libexec/dovecot/deliver(main+0x725) [0x804a185] -> /lib/i686/nosegn eg/libc.so.6(__libc_start_main+0xdc) [0x65ce9c] -> /usr/libexec/dovecot/deliver [0x80498c1] == config # dovecot -n # 2.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.el5xen i686 CentOS release 5.8 (Final) xfs debug_log_path = /var/log/dovecot/debug.log dict { expire = sqlite:/etc/dovecot/dovecot-expire.conf.ext } disable_plaintext_auth = no first_valid_gid = 12 first_valid_uid = 40001 info_log_path = /var/log/dovecot/infos.log lda_mailbox_autocreate = yes log_path = /var/log/dovecot/error.log mail_debug = yes mail_location = maildir:/var/mail/%u/mail maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. } passdb { args = /usr/libexec/dovecot/checkpassword-bcrypt/checkpassword-bcrypt.rb driver = checkpassword } plugin { expire = INBOX.Trash 14 INBOX.Trash/* 14 INBOX.Spam 14 INBOX.spam 14 INBOX.Papierkorb 14 INBOX.Papierkorb/* 14 INBOX.Junk 14 expire_dict = proxy::expire quota = maildir:User quota quota_rule = *:storage=0 quota_rule2 = INBOX.Trash:storage=+10%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/dovecot.sieve sieve_default = /var/lib/dovecot-sieve/default.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot-sieve/global/ } postmaster_address = postmaster(a)example.com protocols = imap pop3 sieve service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service quota-warning { executable = script /usr/libexec/dovecot/quota-warning.sh } ssl_cert = </etc/certs/server.crt ssl_cipher_list = HIGH:MEDIUM:!aNULL:!SSLv2:@STRENGTH ssl_key = </etc/certs/server.key userdb { driver = prefetch } userdb { args = /usr/libexec/dovecot/checkpassword-bcrypt/checkpassword-bcrypt.rb driver = checkpassword } version_ignore = yes protocol lda { info_log_path = /var/log/dovecot/deliver.log log_path = /var/log/dovecot/deliver-errors.log mail_plugins = sieve quota } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 30 mail_plugins = expire quota imap_quota } protocol pop3 { mail_plugins = expire quota }

2 1

[Dovecot] Time stamp or expire_stamp not updating to DATABASE table expires in mysql
by Steve Wells 29 May '12

29 May '12

Debian OS Dovecot upgraded from 1.2 to 2.0.18 RoundCubeMail Web Client which uses imap to make connection mysql-server-5.1 version = 5.1.61-0+squeeze1 RoundCubeMail = 0.7.2 As users delete mail in Roundcubemail the database timestamp not entered. The database is blank /var/log/dovecot.log shows no error Do you know where I can look to resolve this problem? If you need any further information/test feel free to ask. Below is dovecot -n, dovecot-dict-expire.conf, and mysql describe of table expire Thanks in advance? Steven Wells Advanced Business Networks wells(a)netabn.com nm2:/var/lib/dovecot# dovecot -n # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.3 auth_mechanisms = PLAIN LOGIN dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf expire = mysql:/etc/dovecot/dovecot-dict-expire.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } disable_plaintext_auth = no first_valid_uid = 1001 last_valid_uid = 1001 listen = * log_path = /var/log/dovecot.log mail_gid = 1001 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = " expire" mail_uid = 1001 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk expire = Trash 7 Trash/* 7 Junk 30 Sent 30 expire_dict = proxy::expire quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /var/vmail/sieve sieve_global_path = /var/vmail/sieve/dovecot.sieve } protocols = pop3 imap sieve service auth { unix_listener /var/spool/postfix/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl_ca = </etc/ssl/certs/gd_bundle.pem ssl_cert = </etc/ssl/certs/nm2.abgnetwork.net.pem ssl_key = </etc/ssl/private/nm2.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes log_path = /var/log/sieve.log mail_plugins = quota sieve autocreate expire postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota imap_quota autocreate expire } protocol pop3 { mail_plugins = quota expire pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } cat dovecot-dict-expire.conf connect = host=127.0.0.1 dbname=vmail user=vmail password=********************* map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } mysql> describe expires; +--------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +--------------+--------------+------+-----+---------+-------+ | username | varchar(75) | NO | PRI | NULL | | | mailbox | varchar(255) | NO | PRI | NULL | | | expire_stamp | int(11) | NO | | NULL | | +--------------+--------------+------+-----+---------+-------+ 3 rows in set (0.00 sec)

2 1

[Dovecot] Active Directory : searches in root tree
by nicolasfo 29 May '12

29 May '12

Hello everyone ! I'm trying to make a mail server with dovecot and postfix. Users will authenticate with Active Directory server. I've got an problem with Dovecot. To make the mail server, I'm using IredMail, and I used this tutorial : http://www.iredmail.org/wiki/index.php?title=Integration/Active.Directory.i… here Here's my dovecot-ldap.conf : hosts = dc.domain.lan:389 ldap_version = 3 auth_bind = yes dn = vmail(a)domain.lan dnpass = vmail_passwd base = ou=some_ou,dc=domain,dc=lan scope = subtree deref = never user_filter = (&(userPrincipalName=%u)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) pass_filter = (&(userPrincipalName=%u)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) user_attrs = =home=/home/mail/%Ld/%Ln/Maildir/,=mail=maildir:/home/mail/%Ld/%Ln/Maildir/ pass_attrs = userPassword=password default_pass_scheme = CRYPT With this configuration file, it works. BUT : To allow Dovecot to find users in my AD database, I must specify an OU in "base". If I only set "dc=domain,dc=lan" the research doesn't work. It seems that Dovecot is not capable to make a research without an OU specified in base. Am I wrong ? The root research works fine with postfix, samba+winbind, and I've an enterprise sized hardware firewall, and it works fine too. I'll be surprised if you tell me that Dovecot can't make a research without OU... That's why I'm posting here.. I've already post about this problem on the Iredmail forum, http://www.iredmail.org/forum/post15184.html#p15184 here , but no solution were found. You're my last hope :) Thanks a lot for replies Nicolas -- View this message in context: http://old.nabble.com/Active-Directory-%3A-searches-in-root-tree-tp33881379… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] GETQUOTAROOT under roundcube
by Adam Szpakowski 29 May '12

29 May '12

Hi, I'm struggling with the proper quota displaying under roundcube webmail. I've tracked the problem to the different responses on GETQUOTAROOT command. Roundcube aquire quota usage using IMAP command: GETQUOTAROOT INBOX Example dump of the roundcube <-> dovecot communication: > GETQUOTAROOT inbox < QUOTAROOT "inbox" "User quota" < QUOTA "User quota" (STORAGE 1198415 10485760) < OK Getquotaroot completed. The same communication using python imaplib: > GETQUOTAROOT inbox < QUOTAROOT "inbox" "User quota" < QUOTA "User quota" (STORAGE 1431260 10485760) < OK Getquotaroot completed. Quota reported to python client is the same as the one reported to Thunderbird and seems to be the proper one. Python test was performed from the webmail same server, the same user. Can someone point me in the right direction? If there is no explanation on IMAP level i'll move the question to roundcube list. software used: - dovecot: 2.0.15, quota limit set in LDAP, usage tracked in SQL - roundcube: 0.7 - python: 2.6.7 Relevant parts of the dovecot config (taken selectively from different files): quota = dict:User quota::proxy::quota quota_rule2 = Trash:storage=+10%% quota_rule3 = spam:storage=+10%% user_attrs = mailQuota=quota_rule=*:bytes=%$ mail_plugins = quota imap_quota dict { quota = mysql:/etc/dovecot/dovecot-dict-used-quota.conf.ext } #dovecot-dict-used-quota.conf.ext map { pattern = priv/quota/storage table = used_quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = used_quota username_field = username value_field = messages } -- Adam Szpakowski

2 1

[Dovecot] per-mailbox message limits
by Alan Brown 29 May '12

29 May '12

This is something Timo hacked up for me a few years ago and I realised should be on the list in case anyone else wants them. The following patches will limit maildir folders to 4000 messages on Dovecot 2.0.* and 2.1.* The Specfile patch is against the Cityfan Redhat EL5 SRPM but is likely to work on most build platforms Changing the message limit requires a recompile. It's brutal and ugly but it prevents users overloading FSes that can't cope with huge numbers of files (EG: GFS2)

3 3

[Dovecot] (no subject)
by Phil Petree 29 May '12

29 May '12

Hey All, I'm developing a site on a VPS that comes stock with dovecot 1.2.17 and I'm trying to setup some functionality that is very specific to our business model. My question is this: How do I create (programatically) aliases for a forwarder? I have an address, email(a)domain.com that gets sent to a php script and I want users to be able to send to that script via any number of different names (could ultimately be 1000's). I'm thinking that I append/delete from the etc/aliases file and then run #newaliases So that email(a)domain.com will answer on dummy(a)domain.com or dothis(a)domain.com, once the email comes in, I can check the header, get who it was really sent to, do all my checks, perform the necessary action blah blah blah... and be able to do it all on one piece of code (my fantasy LOL). Am I on the right track here or is this simply not going to work? Thanks, Pete

2 1

[Dovecot] AUTH PLAIN fails while AUTH LOGIN succeeds with Exim -> Dovecot SASL auth
by Sandro Tosi 29 May '12

29 May '12

Hello, we're trying to setup a platform with authenticated SMTP with exim and relying on dovecot as auth agent. We've read http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL and so made the changes mentioned there, also setting auth_mechanisms = plain login in conf.d/10-auth.conf . With this setup, we're able to use AUTH LOGIN method on an SMTP session, but using AUTH PLAIN fails. What we receive in the SMTP session is: auth plain `echo -e -n `\0user\0password' | mimencode` 535 Incorrect authentication data (it's actually the output of that command that we put there), and in the dovecot log we see: 2012-05-24 15:04:20 auth: Debug: client in: AUTH 1 PLAIN service=smtp secured rip=127.0.0.1 lip=127.0.0.1 nologin resp=<hidden> 2012-05-24 15:04:20 auth: Info: plain(?,127.0.0.1): invalid input Do you know where we can look to resolve this problem? If you need any further information/test feel free to ask. Thanks in advance? -- Sandro Tosi Product Engineer Shared Hosting Products R&D | Dada.pro eml sandro.tosi(a)register.it

1 1

[Dovecot] Released Pigeonhole v0.3.1 for Dovecot v2.1.6
by Stephan Bosch 27 May '12

27 May '12

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script retrieval. It now possible to fetch Sieve scripts from an SQL database using the Dovecot dict facility. Read the INSTALL file and the referenced additional documentation for more information. Note that this feature currently is not usable with sieve_before/sieve_after and ManageSieve. Additionally, it is now possible to specify multiple sieve_before and sieve_after scripts. This for instance enables administrators to specify both global and user-specific scripts that are to be executed before and after the user's personal script. User-specific scripts configured in sieve_before and sieve_after can not be seen or changed through the ManageSieve protocol. Finally, as promised a while back, I've incorporated the vnd.dovecot.duplicate extension into the main Pigeonhole package. Using this Dovecot-specific extension it is possible to detect duplicate deliveries (such as for example caused by mailing list subscriptions). The detection is based on the message ID and uses the same database file (~/.dovecot.lda-dupes) as the vacation extension. Since the changes introduced in the release are rather large, I strongly advise you to experiment with it a bit before deployment. Changelog v0.3.1: * Added support for retrieving Sieve scripts from dict lookup. This means that Sieve scripts can now be downloaded from a database. Compiled script binaries are still put on disk somewhere if used. The INSTALL documentation is updated with information on this new feature and the (backwards-compatible) changes to the configuration. Note that his feature is currently not supported for sieve_before/sieve_after or script management through ManageSieve. + Incorporated the sieve_duplicate plugin into main Pigeonhole tree as a normal extension (vnd.dovecot.duplicate). This Dovecot-specific extension adds the ability to check for duplicate deliveries based on message ID. Specification can be found in: doc/rfc/spec-bosch-sieve-duplicate.txt + Added support for specifying multiple sieve_before and sieve_after paths. This adds much more flexibility to the multiscript configuration. One application is to have user-specific Sieve scripts outside the user's normal control through ManageSieve. + Added a "session ID" string for managesieve connections, available in %{session} variable (analogous to Dovecot change). - Fixed several small issues, including a few potential segfault bugs, based on static source code analysis. - ManageSieve: changed use of EPROTO error to EIO in ManageSieve string stream implementation because it is apparently not known in BSD. - Gave stamp.h.in (needed for autotools) some content to prevent it from disappearing in patch files. - Fixed bug that caused a SunStudio CC compile failure (reported by Piotr Tarnowski). The release is available as follows: http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.1.tar.gz http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.1.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 5

[Dovecot] Checkpassword Perl LDAP Implementation
by Jeff Hardy 27 May '12

27 May '12

A few years back I hacked up a perl chkpassldap.pl script to authenticate against ldap, and optionally authorize against groups and/or ldap attributes. This works with both qmail and Dovecot, and it also supports a somewhat generic method to alter the environment suitable to use for Dovecot as a prefetch userdb. Anyway, I have been running the script on a qmail-ldap and Dovecot 1.2 proxying cluster using the stock qmail-ldap attributes without any troubles, and figured I would finally release it in the thought someone might find it useful. http://fritz.potsdam.edu/projects/chkpassldap I tried to document the ins and outs of userdb configuration. If anyone finds anything that could use correction or clarification, please let me know. It has been awhile since I was in the middle of it all. Cheers, -Jeff -- Jeffrey Hardy Network / Systems Administrator hardyjm(a)potsdam.edu

1 0