- dovecot - dovecot.org

[Dovecot] sieve filters
by Ian P. Christian 19 Feb '09

19 Feb '09

Hi all, I'm trying to figure out a way of filtering mail from a commercial anti-spam platform. Unfortunately you need to compare part of one header against part of another header. I figured I could solve this using sieve variables and pattern matching, however I'm having little luck and don't know how to debug sieve issues. # example headers: must compare 0.00799 against 1:0000 (the 2nd number in the 2nd header) # X-pstn-levels: (S: 0.00799/98.42547 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) # X-pstn-settings: 3 (1.0000:1.0000) s cv gt3 gt2 gt1 r p m c if header :matches "X-pstn-levels" "(S: */*" { set "score" "${1}"; if header :matches "X-pstn-settings" " ? (*:*) *" { fileinto "somewhere"; } } The first if appears to match, as if I move the fileinto up there it works - however it doesn't work as it shown here. Can anyone suggest why? Can I achieve what I'm trying to do with sieve? How can I go about debugging scripts? Thanks, Ian

2 2

[Dovecot] kerberos trying to obtain credentials for wrong machine
by Nikolay Shopik 19 Feb '09

19 Feb '09

Hi, I'm currently trying to configure Dovecot to use kerberos. My KDC is Windows 2003 and I successful generated keytab file for Dovecot machine. Problem is when I'm trying to use GSSAPI it told me Obtaining credentials for imap@debian5 - and of course this fails because debian5 isn't KDC, it should look for imap/debian5.inblock.local(a)INBLOCK.LOCAL. What I'm missing?

2 1

[Dovecot] Time moved backwards ....
by Harry Lachanas 18 Feb '09

18 Feb '09

OK.. So I synced the clock.... and got .... dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards ( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time ..... Suggestions ...??? Harry.

8 10

[Dovecot] mbox snarf plugin + idle
by Jonathan Siegle 18 Feb '09

18 Feb '09

I'm having a problem with mbox snarf not looking at /var/spool/mail/ when in idle mode thus never giving me a RECENT line even though there are new messages in /var/spool/mail/ . Here are the imap commands to reproduce the problem: 1 login userid password 2 select inbox 3 idle When I run "select inbox" it does see my messages in /var/spool/mail/ and moves them over fine. When I truss the process, I see it only running stat calls on my "mbox- snarf" file. To get new messages I issue DONE, CLOSE, and SELECT INBOX. I'm not sure why it is reporting alpha5 two lines below. I did an hg pull just the other day and see 1.2.beta1 in the output of hg tags. # /usr/ladmin2/sbin/dovecot -n # 1.2.alpha5: /usr/ladmin2/etc/dovecot.conf Warning: fd limit 2000 is lower than what Dovecot can use under full load (more than 4224). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: AIX 3 0001112AD300 syslog_facility: local0 protocols: imap listen: *:2222 ssl: no disable_plaintext_auth: no login_dir: /usr/ladmin2/var/run/dovecot/login login_executable: /usr/ladmin2/libexec/dovecot/imap-login login_greeting: Dovecot ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h/new:INBOX=/var/spool/mail/14/%u mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mbox_lazy_writes: no mail_plugins: mbox_snarf imap_client_workarounds: delay-newmail auth default: mechanisms: plain gssapi krb5_keytab: /etc/krb5/dovecot.keytab gssapi_hostname: $ALL verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd plugin: mbox_snarf: /gpfs/inbox/14/%u Thanks, Jonathan

2 2

Re: [Dovecot] from postfix deliver to dovecot deliver
by dovecot＠corwyn.net 18 Feb '09

18 Feb '09

you're using maildir? (I only ask because I am). In that case, no making the change doesn't require changes in the mailboxes. I made the appropriate changes (just a few days ago) to main.cf and I was good to go. Rick At 08:01 AM 2/18/2009, Johan Hendriks wrote: >Hello all. >I use dovecot in combination with postfix, postfixadmin for virtual users. >Deliver to the mailbox now is done by postfix >Now i want to enable quota's and therefor i need dovecot deliver. >Can i just switch to dovecot deliver? >Or must i first do some prrperations in the mailboxes. > >regards >-- >_______________________ >*Johan Hendriks* >*Schavemaker Transport* > >Tel: +31 (0)251 229098 >Fax: +31 (0)251 212016 >email: j.hendriks(a)schavemaker.com <mailto:j.hendriks@schavemaker.com> >web: http://www.schavemaker.com >_______________________ >/Confidentiality Notice: The information in this document may be >confidential. It is intended only for the use of the named recipient. >If you are not the intended recipient, please notify me immediately >and then delete this document. Do not disclose the contents of this document >to any other person, nor take any copies. Violation of this notice >may be unlawful. / >_______________________

1 0

[Dovecot] assertion failed
by Ian P. Christian 18 Feb '09

18 Feb '09

Does anyone know what might cause this? # dovecot --version 1.1.7 Feb 17 18:21:51 imap-proxy-temp dovecot: Panic: auth(default): file passdb-cache.c: line 121 (passdb_cache_lookup_credentials): assertion failed: (*scheme_r != NULL || *password_r == NULL) Feb 17 18:21:51 imap-proxy-temp dovecot: auth(default): Raw backtrace: dovecot-auth [0x42c0ea] -> dovecot-auth [0x42c143] -> dovecot-auth [0x42b7f6] -> dovecot-auth [0x41acb6] -> dovecot-auth(auth_request_lookup_credentials+0x6f) [0x411cdf] -> dovecot-auth [0x416caf] -> dovecot-auth(auth_request_handler_auth_continue+0xc9) [0x4128e9] -> dovecot-auth [0x40e40a] -> dovecot-auth(io_loop_handler_run+0xf8) [0x42fb48] -> dovecot-auth(io_loop_run+0x1d) [0x42ea4d] -> dovecot-auth(main+0x2f7) [0x416367] -> /lib/libc.so.6(__libc_start_main+0xda) [0x7f83990e54ca] -> dovecot-auth [0x40cdba] Feb 17 18:21:51 imap-proxy-temp dovecot: child 20579 (auth) killed with signal 6

2 4

[Dovecot] Maildir hierarchy sep bug ?
by Thomas Hummel 17 Feb '09

17 Feb '09

Hello Timo, I'm experiencing the following different behaviors with dovecot-1.1.8/Maildir. My Maildir hierarchy separator is the "." (dot) character. My namespaces, when I use them, separator is "/". When I run the server without any namespaces, I can create mailboxes named something like first.name which, of course, are shown to the client as first/ (non selectionnable) first/name For instance in Mutt, if I save a message (the "s" key) from first.name(a)some.domain dovecot happilly creates the .first.name/ Maildir But if I create a public Namespace, then I have to create a private default namespace as well and the server doesn't behave the same way : They're set up like this : namespace private { separator = / prefix = location = maildir:/courriel/boites/%u:CONTROL=/courriel/meta/%u:INDEX=/var/dovecot/indexes/%1u/%u inbox = yes hidden = no list = yes subscriptions = yes } namespace public { separator = / prefix = '#Foo/' location = maildir:/courriel/boites/public/foo inbox = no hidden = yes list = no subscriptions = no } Then users cannot create mailboxes with a dot in it : Character not allowed in mailbox name: '.' which seems normal but can be confusing since, a user used to saving his mail in first.name (in Mutt for instance) wouldn't be able to do so anymore if the server goes from the first to the second setting described above. Granted, a user which does so, probably doesn't do what he thinks he does (he probably thinks he save his message in a folder named "first.name" while instead he actually saves it in a subfolder of "first" named "name"). Still it can be confusing. Is that difference of behavior normal ? Which is the correct behavior ? And is there still no way (except to patch the source) to allow dots in mailbox names in Maildir ? Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 7

[Dovecot] Error: IMAP(user): nfs_flush_file_handle_cache_dir: rmdir(/var/mail) failed: Device busy
by Grandy Fu 17 Feb '09

17 Feb '09

Hi, I am running dovecot 1.1.10 and 1.1.11 on Solaris 10, mailboxes are in mbox format and served by Solaris 10 NFSv3, the dovecot cache is on local disk. Some of my users always had above nfs error and their mailbox usually very big, over 100M, 400M, or even 800M. Grandy

2 1

[Dovecot] dbox redesign
by Timo Sirainen 17 Feb '09

17 Feb '09

This is about how to implement multiple msgs/file dbox format. The current v1.1's one msg/file design would stay pretty much the same and it would be compatible with this new design. dbox directories with multiple msgs/file would be like: ~/dbox/storage/ has the actual mail data for all mailboxes ~/dbox/mailboxes/ has subdirectories containing mailboxes and their indexes Also since dbox supports already the single msg per file, those files would be stored in the mailboxes/ directory. So the idea would be that either you use multiple msgs per file using a global storage, or you use single msg per file without a global storage (or it's also possible to be in a mixed setup with some mails in storage/ and some in mailboxes/, mainly to allow migration between those configurations). The storage/ directory would have a new "map index" which is a regular dovecot index (dovecot.index and dovecot.index.log). So the mailbox index would point to mails using an intermediary "map UID". This way if mails are moved to another file only the map index needs to be updated. GUID would be a globally unique 128 bit ID for messages. So if map indexes get corrupted for any reason it's possible to rebuild it by finding the mails using GUIDs. v1.1 dbox has this "dbox.index" file which I was originally planning on using with multiple msgs/file. It had complex file range locking stuff. Now I'm thinking that it's pretty much useless. The only reason for its existence with the new design is for listing metadata for files converted from Maildir. Map index record would contain: - 32 bit map UID - 8 bit flags (MAIL_DELETED flag = message marked as expunged) - 8 bit unused wasted space - 16 bit refcount - 32 bit file sequence - 32 bit file offset --> total 128 bits/msg Mailbox index: - IMAP UID, flags, keywords, etc. - 32 bit map UID - 128 bit GUID dbox file metadata: - 128 bit GUID - size, vsize, received time, saved time, etc. - initial mailbox name (if all indexes get trashed, we can still figure out at least one mailbox where to put the mail. copies would get lost though.) (- no map UID, no imap UID) How to save a message with multiple msgs/file: 1. Find dbox file where to append to: 1.1. Look up the last message from map index 1.2. Is the file "too old"? (or doesn't exist at all) - Yes -> Create new dbox file 1.3. Is the file "too large"? - Yes -> Look at the previous file (one sequence less) and goto 1.2. 1.4. Try to lock the file. - Fail -> Look at prev file and goto 1.2. Now we have a locked/new dbox file where we can write to. Because 1.4. step only tries to lock the file, there's no waiting on locks. This also means that if e.g. two processes are writing new messages rapidly they may be appending actively to two different files. I don't think that's a problem, better than waiting for locks. 2a) We're using an existing file and we need to find the append offset. Since we found the file by finding the last msg in the file, we also know the last message's offset. I wasn't really planning on saving the message sizes in the index file, so to get the append offset I guess it needs to do an extra read on the last msg's header to find the size and skip over it. Hmm. Or would it be less disk I/O to store the size on the index so it could be found directly? I'm not really sure.. In any case, after we find the append offset, check to see if it's at EOF. If not, that means that either another process just saved a new message there or a process crashed previously and left garbage lying around. Refresh the map index to see if this file+offset exists in it. If not, truncate the file and just continue writing there. If it exists, figure out the new append offset and see again if the file limit would be reached. If the file would become too large, unlock the file and goto step 1. 2b) We're writing to a new file. No need to worry about anything in 2a) 3. Write the message and its metadata to dbox file (including generated 128 bit GUID). 4. Assign map UIDs for the written mails and write APPEND records to map index's transaction log. The record would contain the map UID, file seq, offset, refcount=1. The transaction is saved with a "weak" flag (wonder if there's a better name for this) and its offset is remembered. - If we're creating a new dbox file, it's assigned the file seq and rename()d to the final file name while the map index is locked. 5. Write APPEND record to mailbox index's transaction log with IMAP UID, map UID and GUID (and flags, keywords, etc). 6. Write "commit offset=x" record where x is the offset remembered in step 4. This marks the 4's weak transaction as being fully finished. 7. dbox file is unlocked (if we weren't creating a new file). When reading the index and we see a weak transaction without a commit record, call a resolve() function in dbox code. It finds the dbox file in the weak transaction and tries to lock it. If it can't lock it, it (probably) means that there's still a process that's going to finish the save. If a locking succeeded, run a fixup code that goes through all files that are referenced in weak transactions and makes sure all the refcounts and such are valid. Then it writes commit records for each such transaction. Copying can be done by locking source dbox file, writing a weak "refcount++" transaction and continuing from saving step 5. The only step I can think of where there's a small problem is if data is written to dbox file, then process dies, but no saving is attempted to the same file later. The data is left there as garbage until maybe some day later when a message is expunged from that file and cleanup code notices that there's extra data. I thought about reordering steps so that the records are written to map index first, but that's less efficient when writing multiple messages, because each one would need to be saved separately to the map index (where each save would be lock + fstat (+ read) + write + unlock). This is probably a rare problem which doesn't really matter.. Expunging: The "expunge" and "cleanup to remove deleted space" are separate steps. Preferably the cleanup would be done when the server is "less busy", but I guess it could also be configured to happen either immediately or during logout (or once an hour or so). 1. Write "want to expunge" record to mailbox's transaction log. 2. Write a weak "refcount--" to map index's transaction log. 3. Write "expunged" record to mailbox's transaction log. 4. Write "commit" for the weak refcount--. (The two-stage want-to-expunge(1)/expunged(3) is already done for maildir/mbox also.) I was also thinking maybe this could be just 3 steps without a weak transaction. Especially since without a fsync() between 2 and 3 there's really no guarantee about the order in which 2 and 3 happen. And fsync()s are kind of annoying. But then again if that isn't done and it crashes between 2 and 3 the expunge is tried again later which now decrements the refcount again. If the message's original refcount was 1 it would now be negative. That's not really a problem. More problematic is if the message had been copied to another mailbox and refcount=2, now the refcount would be 0 and the message in the other mailbox would get unexpectedly lost. Not good. Space deletion cleanup: 1. Check from map index header to see there are any refcount=0 mails. Although having this step probably requires some annoying dbox-specific code in index handling code. I guess I'll have to see later if there's a non-horribly-ugly way to do this. 2. Go through all records in the map index. Get a list of files that have refcount=0 records. Also make a copy of file seq+offsets and sort them (so at step 3 we can easily find what mails exist). 3. For each file that has refcount=0 records: 3.1. Try to lock the file. -> Fail: Skip to next file. Either someone's appending to it or cleaning it up already. 3.2. Refresh map index. Add any newly added records to the sorted records list (rare). 3.2. Find the first refcount=0 mail. 3.3. Copy all mails after that with refcount>0 to a new file. 3.4. Lock map index, assign new file seq for the new file, rename() it, for each mail we just copied, using a weak transaction write the seq +offset updates to map index's transaction log. Unlock map index. 3.5. Depending on if first refcount=0 mail was the first mail, either unlink() the file or ftruncate() it. 3.6. Write "commit" record to finish the weak transaction. That's a bit inefficient when cleaning up multiple dbox files, but I'm not sure if there's a much better way unless the map index is locked for the entire time. Since the copying might take a while, a long map index lock is bad since it prevents messages from being saved. Reading mails can be done without locking. But since a file can be truncated unexpectedly, the code must be able to find the new file and offset in that situation and continue reading from there. If the message we were reading was just expunged+cleaned up, the client will have to be just disconnected. Since the cleanup shouldn't normally happen immediately after expunge, this should happen rarely/never. Oh and about all these new temp files that are created. When dbox is opened the dir is stat()ed and if its atime is older than 1 week (currently hardcoded) it readdir()s through the dir to see if there are any old temp* files and then unlinks them. With the new design flags/keywords would never be written to actual dbox files. This helps with backups and also avoids the horribleness of having to increase metadata area. To avoid complete data loss due to index corruption (which really shouldn't be happening nowadays), the indexes are also once in a while backed up to e.g. dovecot.index.backup file. If Dovecot detects missing/broken index, it uses this backup copy to rebuild the index as well as it can. I'm also wondering if it's better for each mailbox to have its separate dovecot.index.cache file or if there should be one cache file for the map index. The upside with one index is that if a mail is copied there's no need to duplicate its cached data. The downside is that I'm worried it would cause more disk I/O, since mailboxes are typically accessed separately, so it might be better that the cache data for one mailbox is stored together rather than all around one bigger cache file.

5 7

[Dovecot] Changing level an error logs at
by Thomas M Goerger 17 Feb '09

17 Feb '09

Hi, I'd like to change the log levels of a few of the errors that Dovecot throws. Our servers throw errors at the console above the 'Error' level, and there are a few that I'd like to change to 'Warn' so that they don't do so. Has anyone out there attempted this and can give me a few pointers? Or is there a doc somewhere about how to do this? Thanks, ************************************************************************* * Tom Goerger - Email/Unix System Administrator * * * * University of Minnesota Email: tmg(a)umn.edu * * Operations, Infrastructure and Architecture Phone: 4-5804 * * Internet Services Office: 626J WBOB * * * *************************************************************************

3 3

[Dovecot] Replication status
by Asheesh Laroia 16 Feb '09

16 Feb '09

I remember last year we discussed Dovecot replication a bit on this list, e.g. http://www.dovecot.org/list/dovecot/2008-May/030446.html . Has there been any development related to this, and can I help at all? The more I think about the hacks I'm employing to synchronize mail, the more I realize I want this. So hopefully I can put either some money or some time where my mouth is. -- Asheesh. -- Its name is Public Opinion. It is held in reverence. It settles everything. Some think it is the voice of God. -- Mark Twain

7 10

[Dovecot] Access denied when client is connecting
by Florian Wörter 16 Feb '09

16 Feb '09

Hello! I'm having a problem with dovecot on my gentoo linux box. it would be great if you could help me. i'm planing to use dovecot as imap server. the incoming mails for the different useres are fetched by getmail. for every user a script should be called, which fetches the e-mails of this user from a pop3 server and puts them in ~/mailbox/new. this allready works. now i installed dovecot but everytime a client connects, i find these lines in my dovecot logfile (/var/log/dovecot.log) dovecot: Feb 16 09:08:09 Fatal: chdir(/home/woefl81) failed with uid 1001: Permission denied dovecot: Feb 16 09:08:09 Error: child 16211 (imap) returned error 89 (Fatal failure) the username of the connected user is woefl81, his user id is 1001 and his home directory is /home/woefl81/. i can't figure out why this user has no permission for his own files. well, for testing i now adjusted the directory permissions: in /: drwxr-xr-x 5 root root 152 Feb 10 09:19 home in /home: drwxr-xr-x 6 woefl81 users 296 Feb 11 08:27 woefl81 in /home/woefl81: drwxrwxrwx 5 woefl81 users 120 Feb 9 13:09 mailbox in /home/woefl81/mailbox: drwxrwxrwx 5 woefl81 users 120 Feb 9 13:09 . drwxr-xr-x 6 woefl81 users 296 Feb 11 08:27 .. drwxrwxrwx 2 woefl81 users 48 Feb 9 13:09 cur drwxrwxrwx 2 woefl81 users 120 Feb 9 13:13 new drwxrwxrwx 2 woefl81 users 48 Feb 9 13:13 tmp and finally in /home/woefl81/mailbox/new i find the email which was retrieved by getmail: drwxrwxrwx 2 woefl81 users 120 Feb 9 13:13 . drwxrwxrwx 5 woefl81 users 120 Feb 9 13:09 .. -rwxrwxrwx 1 woefl81 users 4.6K Feb 9 13:13 1234181629.M605602P32438Q0R5b6a645fa35278a9.proxystu as i said before i adjusted the rights for the mailbox subdir for testing to 0777, so everyone really should be able to do everything... my dovecot version is 1.1.11 my config: # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-gentoo-r7 i686 Gentoo Base System release 1.12.11.1 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot_info.log protocols: imap ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_chroot: no verbose_proctitle: yes mail_location: maildir:~/mailbox auth default: passdb: driver: pam args: * userdb: driver: passwd the user woefl81 is a "normal" system user (from /etc/passwd): woefl81:x:1001:100::/home/woefl81:/bin/bash his main group is users. on the client i installed mozilla tunderbird.. the user connects to the ip of the linux box with his username (woefl81) and the same password as his account pwd on the linux box. it would be great if somebody had an idea what else i should try to get dovecot to work as imap server. thank you very much in advance! best regards, Florian

2 1

[Dovecot] LDAP, MD5-CRYPT, invalid credentials, BUG or config issue?
by Guenther Falk 16 Feb '09

16 Feb '09

Hi, I read a lot of howto's and I got problems with LDAP and Dovecot to work together. I'm using: Gentoo Linux 2008.0 hardened Dovecot 1.1.7 Kernel 2.6.26 OpenLDAP 2.3.43 My dovecot-ldap.conf is: uris = ldaps://auth.mydomain.com:636 auth_bind = yes auth_bind_userdn = uid=%u,ou=People,dc=mydomain,dc=com ldap_version = 3 base = ou=People,dc=mydomain,dc=com deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT I also tried default_pass_scheme = MD5-CRYPT In the logs I find smething like this: Feb 16 12:20:49 mail dovecot: Dovecot v1.1.7 starting up Feb 16 12:20:50 mail dovecot: auth(default): new auth connection: pid=30582 Feb 16 12:20:50 mail dovecot: auth(default): new auth connection: pid=30583 Feb 16 12:20:50 mail dovecot: auth(default): new auth connection: pid=30584 Feb 16 12:20:53 mail dovecot: auth(default): new auth connection: pid=30585 Feb 16 12:20:58 mail dovecot: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=172.30.0.10 rip=172.30.0.254 lport=993 rport=51269 Feb 16 12:20:58 mail dovecot: auth(default): client out: CONT 1 Feb 16 12:20:58 mail dovecot: auth(default): client in: CONT 1 AGd1ZW50aGVyADE*********= Feb 16 12:20:58 mail dovecot: auth(default): ldap(guenther,172.30.0.254): invalid credentials Feb 16 12:21:00 mail dovecot: auth(default): client out: FAIL 1 user=guenther Feb 16 12:21:00 mail dovecot: auth(default): client in: AUTH 2 PLAIN service=imap secured lip=172.30.0.10 rip=172.30.0.254 lport=993 rport=51269 resp=AGd1ZW50aGVyADE*********= Feb 16 12:21:00 mail dovecot: auth(default): ldap(guenther,172.30.0.254): invalid credentials Feb 16 12:21:02 mail dovecot: auth(default): client out: FAIL 2 user=guenther It seems dovecot ignores the CRYPT password scheme. The password seems to be encrypted in SSHA. What am I doing wrong please?? I am sure, the password is correct as I can login into the machine via nss_ldap and pam_ldap. Regards Günther

2 1

[Dovecot] LDAP, MD5-CRYPT, invalid credentials, BUG or config issue?
by guenther 16 Feb '09

16 Feb '09

Hi, I read a lot of howto's and I got problems with LDAP and Dovecot to work together. I'm using: Gentoo Linux 2008.0 hardened Dovecot 1.1.7 Kernel 2.6.26 OpenLDAP 2.3.43 My dovecot-ldap.conf is: uris = ldaps://auth.mydomain.com:636 auth_bind = yes auth_bind_userdn = uid=%u,ou=People,dc=mydomain,dc=com ldap_version = 3 base = ou=People,dc=mydomain,dc=com deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT I also tried default_pass_scheme = MD5-CRYPT In the logs I find smething like this: Feb 16 12:20:49 mail dovecot: Dovecot v1.1.7 starting up Feb 16 12:20:50 mail dovecot: auth(default): new auth connection: pid=30582 Feb 16 12:20:50 mail dovecot: auth(default): new auth connection: pid=30583 Feb 16 12:20:50 mail dovecot: auth(default): new auth connection: pid=30584 Feb 16 12:20:53 mail dovecot: auth(default): new auth connection: pid=30585 Feb 16 12:20:58 mail dovecot: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=172.30.0.10 rip=172.30.0.254 lport=993 rport=51269 Feb 16 12:20:58 mail dovecot: auth(default): client out: CONT 1 Feb 16 12:20:58 mail dovecot: auth(default): client in: CONT 1 AGd1ZW50aGVyADE*********= Feb 16 12:20:58 mail dovecot: auth(default): ldap(guenther,172.30.0.254): invalid credentials Feb 16 12:21:00 mail dovecot: auth(default): client out: FAIL 1 user=guenther Feb 16 12:21:00 mail dovecot: auth(default): client in: AUTH 2 PLAIN service=imap secured lip=172.30.0.10 rip=172.30.0.254 lport=993 rport=51269 resp=AGd1ZW50aGVyADE*********= Feb 16 12:21:00 mail dovecot: auth(default): ldap(guenther,172.30.0.254): invalid credentials Feb 16 12:21:02 mail dovecot: auth(default): client out: FAIL 2 user=guenther It seems dovecot ignores the CRYPT password scheme. The password seems to be encrypted in SSHA. What am I doing wrong please?? I am sure, the password is correct as I can login into the machine via nss_ldap and pam_ldap. Regards Günther

1 0

[Dovecot] quota warning issue
by Alex 16 Feb '09

16 Feb '09

Hello to all, I'm using version 1.1.11 of dovecot. I set the quota using the following configuration: in /etc/dovecot/dovecot.conf quota = maildir:%u quota_warning = storage=75%% /root/quota-warning.sh 75 %u in /etc/dovecot/dovecot-sql.conf user_query = SELECT concat('/var/vmail/', maildir) as home, concat('maildir:/var/vmail/', maildir) as mail, 1000 AS uid, 12 AS gid, concat('*:storage=', ROUND(quota/1000)) AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' ## password_query = SELECT username as user, password, concat('/var/vmail/', maildir) as home, concat('maildir:/var/vmail/', maildir) as mail, 1000 AS uid, 12 AS gid, concat('*:storage=', ROUND(quota/1000)) AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.25-hardened-r11 x86_64 Gentoo base_dir: /var/run/dovecot/ log_path: /var/log/mail.log info_log_path: /var/log/mail.log protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 1000 last_valid_uid: 1000 mail_location: maildir:/var/vmail/%d/%u mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %v.%u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail plugin: quota: maildir:%u quota_warning: storage=75%% /root/quota-warning.sh 75 %u sieve: /var/vmail/%d/%n/.dovecot.sieve The warning is not delivered to users. In my logs the user quota's percentage is calculated right dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Loading modules from directory: /usr/lib64/dovecot/imap dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Module loaded: /usr/lib64/dovecot/imap/lib10_quota_plugin.so dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Module loaded: /usr/lib64/dovecot/imap/lib11_imap_quota_plugin.so dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Effective uid=1000, gid=12, home=/var/vmail/foo.org/alex/ dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Quota root: name=alex(a)foo.org backend=maildir args= dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Quota rule: root=alex(a)foo.org mailbox=* bytes=52428800 messages=0 dovecot: Feb 15 23:42:33 Info: imap-login: Login: user=<alex(a)foo.org>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Feb 15 23:42:33 Info: IMAP(alex(a)foo.org): Quota warning: bytes=39321600 (75%) messages=0 command=/root/quota-warning.sh 75 alex(a)foo.org but also overcoming the space defined on quota warning, the command is not performed. The command does not contain errors because if performed by cli correctly sends the alert. Any ideas? Regards. Alex

3 7

[Dovecot] unkillable imap process(es) with high CPU-usage
by Arno Wald 15 Feb '09

15 Feb '09

Hello, I am having a problem with my dovecot-daemon. It is forking one or more (I saw up to perhaps 8 of them) imap processes under my user name. These processes are consuming a lot of CPU time and are not killable: > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 8616 arno 20 0 2900 1600 1204 R 98 0.2 1196:38 imap Stopping dovecot does not quit these processes. Killing them (even "kill -9" as root) is not possible. The only solution to get rid of them is to reboot. I have found a mailing list post of one who seemed to have the same problem. He solved it by upgrading to version 1.1. But in my case this did not help. Is this a known problem? What could I check or do? My system: very up to date debian/sid (sidux) kernel 2.6.27-8.slh.1-sidux-686 CPU: Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz Filesystem: ext3fs tried dovecot from sid: 1:1.0.15-2.3 tried dovecot from experimental: 1:1.1.2-3 My dovecot.conf is the original debian configuration with only one line changed into: protocols = imaps # dovecot -n # 1.1.2: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail auth default: passdb: driver: pam userdb: driver: passwd I am using dovecot locally on my system with me as the only user. As client I am using thunderbird alias icedove 2.0.0.17-1. Icedove retrieves the Mails from another imap server and sorts them into Maildir-folders in dovecot. I do not know when the imap-process are going mad. It happens after the system (and the mail-client) is up for a while. Do you need more information? Thanks, Arno

10 35

Re: [Dovecot] unkillable imap process(es) with high CPU-usage
by Robert Schetterer 15 Feb '09

15 Feb '09

just again to the list wasnt in reply Robert Schetterer schrieb: > Hi Gene , small tips depending suse > > Gene Steinberg schrieb: >> On Feb 14, 2009, at 9:57 AM, agent59624285 wrote: >> >>> I have this EXACT same problem after upgrading to SuSE 11.1, which >>> uses this >>> exact kernel version!! >>> >>> After reading this, I was excited to think that if I killed the nfsserver >>> daemon (which I had running for no good reason), that it would sort my >>> problem.... >>> >>> Sure enough, my computer - which up to now had been going unresponsive >>> every >>> 24 hours - was running fine for 72 hours and then BOOM... it happened >>> again. >>> >>> Just wanted to let people know that it seems that at the minute, the >>> dovecot >>> that ships with SuSE and the kernel they are using in 11.1 exhibit this >>> problem. ---my reply > > Suse kernels are not like vanilla kernels, > they are deeply patched an mostly have stuff from the next kernel > version allready in > you might use yast for upgrading latest suse kernel it might fixed allready > a short look gives > http://download.opensuse.org/repositories/home:/tristanhoffmann/openSUSE_11… > gives dovecot 1.1.11 which is latest > also loadable by yast or just download rpm and upgrade wtih rpm -u > > standart rep for mail stuff is > http://download.opensuse.org/repositories/server:/mail/openSUSE_11.1/ > but here dovecot is not at latest > but it shouldnt be any big problem downloading src and > prepare the spec with latest src dovecot > and compile by yourself > which is the best way and gives you the suse splitted packs > too and the advantage to see compile stuff > for sure you need some others libs etc cause of dependencies > befor but they are mostly downloadable also by yast > > be aware that suse sometimes splits up funktions > in own packs like > dovecot-autocreate11, dovecot-antispam11 > etc this musnt be the same by versions compile from home suse users > > also help full send a mail to the build service, > normally it takes only days and the newest version gets compiled > > > use http://software.opensuse.org/search > if looking for newer versions of software ----- > >>> Gino >>> >> This is sounding similar to the problem I have with my setup: >> >> 1. High CPU usage. >> >> 2. Can't kill IMAP. >> >> 3. Server becomes unresponsive. >> >> I'm using CentOS 5.2 64-bit version with the latest cPanel. >> >> So what am I missing, other than the problem nobody else is having is >> clearly something they ARE having? >> >> Peace, >> Gene > > -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] digest-md5 problem
by Nigel Kukard 15 Feb '09

15 Feb '09

Info: v1.1.11 OS = Linux 32bit, custom build CPU Arch = i686 Filesystem = NFSv4 Problem: Digest-md5 not working. Tested plain, login and cram-md5 with pop3, imap and smtp/sasl fine. Using digest-md5 doesn't authenticate with the below error.... *** Feb 15 12:46:45 s03-400-134 dovecot: auth(default): client in: AUTH^I1^IDIGEST-MD5^Iservice=pop3^Ilip=10.0.2.134^Irip=10.0.2.1^Ilport=110^Irport=41579^Iresp=<hidden> Feb 15 12:46:45 s03-400-134 dovecot: auth(default): client out: CONT^I1^IcmVhbG09IiIsbm9uY2U9IktvMkFoK0lyeVhHRWtmY1k5TjM1TXc9PSIscW9wPSJhdXRoIixjaGFyc2V0PSJ1dGYtOCIsYWxnb3JpdGhtPSJtZDUtc2VzcyI= Feb 15 12:46:45 s03-400-134 dovecot: auth(default): client in: CONT<hidden> Feb 15 12:46:47 s03-400-134 dovecot: auth(default): client out: FAIL^I1 Feb 15 12:46:47 s03-400-134 dovecot: pop3-login: Disconnected (auth failed, 1 attempts): method=DIGEST-MD5, rip=10.0.2.1, lip=10.0.2.134 *** The decoded reply is ... authzid="USERNAME_HERE",charset=utf-8,cnonce="32d669a1334164b3362bff5f809acf12",digest-uri="pop/SERVER_URL_HERE",nc=00000001,nonce="rDWjRuMzuvbr5TLsinsE0A==",qop=auth,realm="",response=5c7c2ff3284f350fc62c5a2a80d2be64,username="USERNAME_HERE" On the same database cyrus imap & sasl is working 100%. All passwords are in plaintext format. Maybe I"m doing something wrong? Below my dovecot config... # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.10 i686 none protocols: imap imaps pop3 pop3s listen: 10.0.2.134 shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: s03-400-134 Secure server ready. max_mail_processes: 100 verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_location: maildir:/var/vmail/%h mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: digest-md5 cram-md5 login plain cache_size: 256 user: nobody master_user_separator: * verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: dovecot group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: vmail plugin: quota: maildir trash: /etc/dovecot/trash.conf

1 0

[Dovecot] great disappearing email mystery
by dhottinger＠harrisonburg.k12.va.us 14 Feb '09

14 Feb '09

Have there been any issues with dovecot and using outlook express (imap) as an email client? I have had a couple of users come up with random missing emails. Im trying to figure out if it is user error, or something wacky in my mailserver. I cant find anything telling in maillog files or my messages. Dovecot version is 1.0.3. Its ok to reply to me, I get list messages digest. thanks, ddh -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante

10 25

Re: [Dovecot] pop3_lock_session question
by Alan Ferrency 14 Feb '09

14 Feb '09

Rob Mangiafico <rmang(a)lexiconn.com> wrote: >On Wed, 4 Feb 2009, Timo Sirainen wrote: >> On Wed, 2009-02-04 at 11:17 -0700, Mark Costlow wrote: >>> Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. >>> So far testing has gone very well. One problem we haven't figured >>> out is that long-running POP sessions keep the mailbox locked, so that >>> the MDA times out while trying to deliver. >> .. >> >> Switch to Maildir and the problem goes away. > > We see this as well with mbox and pop3 accesses where some pop3 clients do > not logout (iphone's are the worst offenders) for 30-90 minutes it seems. > Timeout settings in dovecot.conf do not seem to help. procmail backs up > waiting to get access to the inbox to deliver mail. We are having the same problem. It's not a problem with imap, only with pop3. We're using deliver as the MDA. We're also using flock() locking for the mbox: is that what everyone else is using as well? Migrating our servers to maildir globally is also not an option for us. In some cases, even convincing customers to use IMAP isn't going to work. One problem which might be making this worse than it needs to be, is the fact that mbox_lock_flock in mbox-lock.c is not using a blocking flock(); instead, it's polling for a non-blocking lock. This technique can cause lock starvation, if another process is dropping the lock and picking it back up again frequently: other processes will only see the lock as being available if they happen to poll for the lock at just the right instant. A better technique to use here, if it's adequately cross-platform, would be to set an alarm() for the max_wait_time, and use a blocking flock(). If the alarm times out and you don't have a lock, it's a timeout. In the meantime, you're guaranteed to eventually get the lock, if it is dropped. That said: I'm not sure whether this will solve our problem in practice. Why doesn't this happen with imap? Why can't we make pop3 do what imap does? Even if it's inefficient, it's better than hanging all incoming mail delivery while deliver eats up our local concurrency limits. Thanks! Alan Ferrency pair Networks, Inc. alan(a)pair.com

11 33

[Dovecot] Expire failing with error Remote Disconnected
by dovecot＠corwyn.net 14 Feb '09

14 Feb '09

I'm trying to follow the instructions from: http://wiki.dovecot.org/Plugins/Expire for the BDB backend. Everything is set up as indicated, but when I run: dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool I get back: Error: read(/var/run/dovecot/dict-server) failed: Remote disconnected I'm sure it's something simple.... Thx rick dovecot -n: # 1.1.8: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 i686 Red Hat Enterprise Linux Server release 5.2 (Tikanga) ext3 ssl_cert_file: /etc/httpd/certs/_com.crt ssl_key_file: /etc/httpd/certs/.com.key.no.password login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_uid: 1015 mail_gid: 105 mail_location: maildir:/var/spool/mail/%d/%n/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota expire trash mail_plugins(imap): quota imap_quota expire trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle imap_client_workarounds(imap): delay-newmail outlook-idle imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: static socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vuser group: vuser plugin: quota: maildir quota_rule: *:storage=102400000 quota_rule2: Trash:storage=100M trash: /etc/dovecot-trash.conf expire: Trash 14 Trash/* 14 Spam 14 expire_dict: proxy::expire dict: expire: db:/var/lib/dovecot/expire.db Rick Steeves http://www.sinister.net "The journey is the destination"

4 9

[Dovecot] Smooth mailbox to maildir migration
by Luciano Mannucci 14 Feb '09

14 Feb '09

Hi all, I have a postfix+procmail+dovecot installation, now running basicaly on pop3 hence mailbox format, with few thousand users and less than twenty gigabytes mail. I need to move all of them to maildir, to take advantage of IMAP subfolders that do not work with mbox format (so I'm told :). Of course I cannot safely stop the service for more than a bunch of seconds... What I'm about to do: create a second dovecot instance to cope with imap client configured for maildir (and possibly pop3 on another port for those using both), which means a dovecot launched with -c /path/to/alternate.conf and a new /etc/init.d/dovecot2-theRevenge having the proper -i option given to startproc in order to make it ignore the other instance. for each user: convert the mailbox with some sort of mb2mb (which is the better one?) create a .procmailrc with a proper DEFAULT= bearing the magic trailing slash indicating maildir to procmail for each converted user. And I'm done... Have I forgotten something? Is there a better way? Any one else tryed such a thing? Cheers to all, luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.mannucci.ORG/

4 6

[Dovecot] Weird Dovecot 1.1.6 + pop3s certificate issues
by Bernhard Schmidt 14 Feb '09

14 Feb '09

Hello everyone, I've been asked by a colleague to have a look at some extremely weird dovecot SSL issue they are seeing on one of the student mailservers. They are running dovecot 1.1.6 (yes, I know, a bit old ...) on SLES 10.2 x86_64 with imap(+starttls), imaps, pop3(+starttls) and pop3s enabled. Every couple of weeks the pop3s and pop3+starttls part bail out out. Clients can't connect, when you try openssl s_client you get this: 15960:error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01:rsa_pk1.c:100: 15960:error:04067072:rsa routines:RSA_EAY_PUBLIC_DECRYPT:padding check failed:rsa_eay.c:699: 15960:error:1408D07B:SSL routines:SSL3_GET_KEY_EXCHANGE:bad signature:s3_clnt.c:1414: server logs don't show much except for various SSL_accept() errors, including TLS handshaking: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac TLS handshaking: SSL_accept() syscall failed: Connection reset by peer TLS handshaking: SSL_accept() failed: error:1409441B:SSL routines:SSL3_READ_BYTES:tlsv1 alert decrypt error imaps and imap+starttls work fine during the whole time (and always have), although they are much more used. Restarting dovecot fixes the issue for a couple of weeks. Does anyone have an idea where to start debugging? As far as I understand the whole SSL_accept() thing is a giant blackbox for Dovecot, but how comes it only affects POP3? dovecot -n (paths and addresses altered, not sure how much I can reveal without getting shot): # 1.1.6: /mnt//usr/local/etc/dovecot.conf # OS: Linux 2.6.16.60-0.25-smp x86_64 SUSE Linux Enterprise Server 10 # (x86_64) protocols: imap imaps pop3 pop3s listen(default): [ipv6]:143, ipv4:143 listen(imap): [ipv6]:143, ipv4:143 listen(pop3): [ipv6]:110, ipv4:110 ssl_listen(default): [ipv6]:993, ipv4:993 ssl_listen(imap): [ipv6]:993, ipv4:993 ssl_listen(pop3): [ipv6]:995, ipv4:995 disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /mnt//usr/local/libexec/dovecot/imap-login login_executable(imap): /mnt//usr/local/libexec/dovecot/imap-login login_executable(pop3): /mnt//usr/local/libexec/dovecot/pop3-login login_process_per_connection: no login_max_connections: 128 max_mail_processes: 2500 mail_uid: campus mail_gid: lmu mail_location: maildir:~/Maildir:INDEX=/home/something/indexes/%-1.1n/%n mmap_disable: yes mail_nfs_index: yes mail_executable(default): /mnt//usr/local/libexec/dovecot/imap mail_executable(imap): /mnt//usr/local/libexec/dovecot/imap mail_executable(pop3): /mnt//usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /mnt//usr/local/lib/dovecot/imap mail_plugin_dir(imap): /mnt//usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /mnt//usr/local/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: worker_max_request_count: 500 passdb: driver: ldap args: /mnt//usr/local/etc/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /mnt//usr/local/etc/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: campus group: lmu plugin: quota: maildir quota_rule: Trash:ignore quota_rule2: *:storage=512M Anyone having an idea? bernhard

1 0

Re: [Dovecot] Dovecot-antispam does not work
by Jehan Pagès 14 Feb '09

14 Feb '09

Hi all, just to say that finally the patch of Marcin worked great. Just my configuration is different from yours to get it work: antispam_signature = X-DSPAM-Signature antispam_trash = trash;Trash;Deleted Items antispam_spam = SPAM;Junk antispam_dspam_binary = /usr/bin/dspam antispam_dspam_args = --client;--source=error;--user;%u antispam_mail_tmpdir = /tmp The difference here is in the syntax. You write "--user=somemail" though in the manual, it is written "--user somemail". But also you were proposing 2 lines "antispam_dspam_args" though in all my tests, when I was doing such a thing, the second line seemed to override the first (in the launch logs, only the second line was displayed, so I guess...). Are you sure that it works exactly the way you intend to, Marcin? And that the "--source=error" (your first line) is indeed added as a parameter to the call of dspam? For the patch to the dovecot-antispam, probably it should not be integrated "as is", but I guess that the return code of call_dspam function must probably be checked and fixed if the call can succeed but still give a failure return code. I set Johannes as a main recipient, maybe you will see this email. Bye and thanks all. Jehan On Wed, Feb 4, 2009 at 12:45 PM, Jehan Pagès <jehan.marmottard(a)gmail.com>wrote: > Hi, > > On Wed, Feb 4, 2009 at 12:40 PM, Marcin Rzepecki <m.rzepecki(a)iem.pw.edu.pl > > wrote: > >> Wed, Feb 04, 2009 at 12:12:44PM +0100, Jehan Pag?s wrote: >> > I saw this piece of code and did the same as you in my change of course. >> > Unfortunately, it didn't work (no logged "marked as SPAM", nor change in >> my >> > stats. I have dovecot 1.1.7-r1 though, so it is probably the reason. >> >> Logging '...markes as SPAM..' lines to syslog is my idea, I can send some >> dspam patches, to make it work. It's usefull for me. > > > Ok. Anyway the stats don't change... > > >> >> Are you using mbox or maildir? If you are using mbox, try to upgrade to >> Dovecot >=1.1.8 - it contains several mbox bug fixes (e.g 'Next message >> unexpectedly lost') which are needed to make antispam plugin work. > > > No maildir... > I am doing some stuffs about another way to interact dspam/dovecot/postfix > and will go back to this issue soon. > > Jehan >

2 1

[Dovecot] "failed to map segment from shared object: Cannot allocate memory"
by Vegard Svanberg 13 Feb '09

13 Feb '09

>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 login_processes_count, login_max_processes_count and/or auth_worker_max_count. -- Vegard Svanberg <vegard(a)svanberg.no> [*Takapa@IRC (EFnet)]

2 3

[Dovecot] Production server migration from mbox to maildir ( need advice )
by Frank Bonnet 13 Feb '09

13 Feb '09

Hello I'm going to change the raid array of my mailhub in fews days/weeks and I wonder if it would be a good idea to take the opportunity of this migration to also change the storage method from mailbox to maildir. I've never used maildir on my production server only on small satellites. So I really need advice of admins that use maildir format on prod servers. My server has approx 3500 users/mailboxes that is approx 450 Gb of data. The OS is Debian etch amd64 but could change also during the migration Opensuse X86_64, CAOS-NSA, FreeBSD 64 are some options. Any infos/experiences welcome, I'll summarize answers. Thanks a lot.

4 8

[Dovecot] Corrupted index cache file
by Proskurin Kirill 13 Feb '09

13 Feb '09

Hello all. I run on a problems? dovecot: Feb 13 08:36:13 Error: IMAP(logistic(a)fxclub.org): Maildir filename has wrong W value: /var/spool/dovecot/domains/fxclub.org/logistic/.fxclub/1135926892.Re1a4ad89Q1436.newmail.fxclub.org,S=24630,W=2 4849:2, dovecot: Feb 13 08:36:13 Error: IMAP(logistic(a)fxclub.org): Corrupted index cache file /var/spool/dovecot/domains/fxclub.org/logistic/.fxclub/dovecot.index.cache: Broken virtual size for mail UID 332 dovecot: Feb 13 08:36:13 Info: IMAP(logistic(a)fxclub.org): Disconnected: Disconnected bytes=435/135596 dovecot: Feb 13 08:36:14 Info: imap-login: Login: user=<logistic(a)fxclub.org>, method=PLAIN, rip=194.87.53.162, lip=78.129.148.74, TLS dovecot: Feb 13 08:36:15 Info: IMAP(chief(a)omsk.fxclub.org): Disconnected: Logged out bytes=349/5517 dovecot: Feb 13 08:36:15 Info: IMAP(chief(a)omsk.fxclub.org): Disconnected: Logged out bytes=63/280 dovecot: Feb 13 08:36:15 Error: IMAP(logistic(a)fxclub.org): FETCH for mailbox fxclub UID 332 got too little data: 318 vs 319 dovecot: Feb 13 08:36:15 Error: IMAP(logistic(a)fxclub.org): Maildir filename has wrong W value: /var/spool/dovecot/domains/fxclub.org/logistic/.fxclub/1135926892.Re1a4ad89Q1436.newmail.fxclub.org,S=24630,W=2 4849:2, dovecot: Feb 13 08:36:15 Error: IMAP(logistic(a)fxclub.org): Corrupted index cache file /var/spool/dovecot/domains/fxclub.org/logistic/.fxclub/dovecot.index.cache: Broken virtual size for mail UID 332 dovecot: Feb 13 08:36:15 Info: IMAP(logistic(a)fxclub.org): Disconnected: Disconnected bytes=395/135319 It got then reconfigure MS Outlook 2007 SP1 to make a full download of email - not only headers. Then I reconfig it back to headers only - all work fine. How can I fix it? It is safe to delete index files? Self healing seems to not work here. #dovecot -n mail# dovecot -n # 1.1.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.0-RELEASE-p9 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_greeting_capability(managesieve): no login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location(default): maildir:/var/spool/dovecot/domains/%d/%n/ mail_location(imap): maildir:/var/spool/dovecot/domains/%d/%n/ mail_location(pop3): maildir:/var/spool/dovecot/domains/%d/%n/ mail_location(managesieve): mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_plugins(imap): quota imap_quota autocreate mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): % sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve auth default: mechanisms: plain login user: dovecot-auth username_format: %Lu verbose: yes worker_max_count: 100 passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: exim master: path: /var/run/dovecot/auth-master mode: 384 user: dmail plugin: quota: maildir quota_rule: *:storage=1024M quota_rule2: Trash:storage=1256M quota_rule3: SPAM:ignore quota_warning: storage=80%% /usr/local/bin/quota-warning.sh 80 quota_warning2: storage=95%% /usr/local/bin/quota-warning.sh 95 autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam -- Best regards, Proskurin Kirill

3 3

[Dovecot] Bynari Insight connector
by Maarten Bezemer 13 Feb '09

13 Feb '09

Hi, Since IMAP support in Outlook is 'somewhat broken', and Bynari has some promising specifications on their website, I might want to try their product. Does anyone here have any experience with their software? Would you recommend it? Or maybe point me at alternatives? (If there are any.. aside from ditching Outlook of course :-P ) Regards, Maarten Bezemer

3 3

[Dovecot] Google Summer of Code
by Charles Marcus 13 Feb '09

13 Feb '09

On another list, someone wrote: > Google Summer of Code is on it's Way. Start collecting students to > throw at projects now! This sounds like a great idea for dovecot too... Timo, maybe there are a few dovecot enhancements that would be good candidates for this? Maybe the test suite? Replication? LMTP server? Anyway, its just a thought... -- Best regards, Charles

1 0

[Dovecot] Corrupted index cache file
by Frank Bonnet 13 Feb '09

13 Feb '09

Hello I got this error yesterday dovecot: Feb 11 16:07:27 Error: IMAP(dumontj): FETCH for mailbox Sent UID 7139 got too little data: 11112 vs 11160 dovecot: Feb 11 16:07:27 Error: IMAP(dumontj): Corrupted index cache file /user/dumontj/.imap/Sent/dovecot.index.cache: Broken virtual size for mail UID 7139 Does remove the cache will cure the problem ? Thanks

4 5

Re: [Dovecot] Mapping usernames [RESOLVED]
by Henry 13 Feb '09

13 Feb '09

Resolved. For others, this is the simple solution which works for me: /etc/dovecot.conf: auth default { userdb passwd-file { args = /etc/passwd } passdb passwd-file { args = scheme="MD5-CRYPT" /etc/dovecot.passwd } } /etc/dovecot.passwd: bob@vhost.com:$1$yAOjs09l$...::::::userdb_user=vabc_bob (the encrypted password "$1$yAOjs09l$..." comes from /etc/shadow) /etc/passwd: vabc_bob:x:20838:2362:bob:/home/mailusers/vabc_bob:/sbin/nologin "abc" could also be the domain ("vhost"), but this might be too large for really long domain names. So we rather use a short unique prefix for each domain. Cheers Henry -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.5 (GNU/Linux) mOIESXlwDRECAOycneJPOwSkETRkjJZdArag8V2rKOR2IUwlDOydIZXv/ITDlWDU dookzEdWh7Ektf1Jlh+YbPNEGoPpQunL8O8AoJbWmNkpoX7jP0Sw/5rDN2eKGHR7 Af9mxTqQ/j3C5LkrTRo9iCTt1TxoqPi6R/w0KkIAuTXBq6j+vIFJcOFgABlMQoXs V2crh1BUCmXVsV1puRJsLWKbAf4uL0V+N8WF4rvWHmJiYjgDn6exv3XHS0F6NhRz n1KVnV0XDWMDq/B/tmj4L2JYxEzWzeNulC5yQBOdx/dLU12XtCNIZW5yeSAoemVu LmNvLnphKSA8aGVucnlAemVuLmNvLnphPohgBBMRAgAgBQJJeXANAhsjBgsJCAcD AgQVAggDBBYCAwECHgECF4AACgkQCHhhdg2iQafVGACdEMtEuUGIW2XJyn9Fig7n sX4qzb4An0PGStBZvAP2qtzYP3SGlzsllzLjuI0ESXlwDRACAMsi4nl8/Yar2m9F ex4dFDgWylLgScQrEhhb2xN0Upcglm60nHQD7c1rP+63Iu+lU0eWvyr8o3JTCN4y PpoGMOMAAwUCAIUnLDMW/tz+qsYaOPyoh7HdAYqcrvVar7t+eKpihNBqfP4CT2Py aRVMN6cSJj9NKZDW6b0QQSCGgN7PpzrLqf6ISQQYEQIACQUCSXlwDQIbDAAKCRAI eGF2DaJBpxeiAJ9cNiuaftSoWke75RT1pn7qoibFfgCdHl6BgP9f450/oziDwaMM w49UeHQ= =qgmL -----END PGP PUBLIC KEY BLOCK-----

1 0

[Dovecot] file name missing component in error message
by Mike Abbott 13 Feb '09

13 Feb '09

Hi, we occasionally see this error message from maildir_mail_set_cache_corrupted(): "Maildir filename has wrong W value: %s/%s" but the path it prints is missing a component, specifically, the new/cur/tmp component. For example: /Volumes/Spool/user/maildir/12345.M123P123.example.com.... should be /Volumes/Spool/user/maildir/cur/12345.M123P123.example.com.... This is using dovecot-1.1.10. Now I just have to figure out why the file is corrupted in the first place.

2 3

[Dovecot] quota - implement via dovecot or postfix? which is easier ?
by Linux Advocate 13 Feb '09

13 Feb '09

Guys, i m new to dovecot. I m setting up a new mailserver and planning to run dovecot and postfix of a centos 5.2 box. I have been reading of quota management from various sources and understand that mail box quota can be implemented either thru postfix ( with vda patch ) or thru dovecot. i rather not patch postfix and m therefore leaning towards quota via dovecot. But after reading some posts ,etc, it seems that the information on the dovecot wiki is inaccurate. A.Any comments on this? B. Am i right in concluding that its easier and better in the long run to implement and enforce quotas thru dovecot instead of postfix? C. The right instructions for implementing quota thru dovecot? Regards, marco.

5 6

[Dovecot] CentOS 5 ... again
by Roderick A. Anderson 13 Feb '09

13 Feb '09

At this point I don't think I can do anymore damage to my mail server but I'd like to know if anyone else is using the pre-built RPM files from ATrpms before I install them? http://dl.atrpms.net/all/dovecot-1.1.11-0_90.el5.i386.rpm http://dl.atrpms.net/all/dovecot-sieve-1.1.6-9.el5.i386.rpm Or is there a dovecot-sieve for 1.0.7 from the rpmforge repo? I haven't found it yet but could have sworn I had it before. Thanks, Rod --

6 9

[Dovecot] Released Sieve v0.1.3 and ManageSieve v0.11.3 for Dovecot v1.2.beta1
by Stephan Bosch 13 Feb '09

13 Feb '09

Hello Dovecot users, It has been about two months since the last release of the new Sieve implementation and the ManageSieve service for Dovecot v1.2. Therefore, this release contains quite a few changes. It adds new sieve features like the enotify extension and multiscript support. Also, quite a few (user-reported) bugs were fixed since the last release. Changelog Sieve v0.1.3: * Adapted to changes in Dovecot, making this release dependent on Dovecot >= 1.2.beta1 * Made mail address comparison fully case-insensitive. This is particularly noticeable for the :addresses argument of the vacation command. + Finished enotify extension. Currently, only the mailto notification method is implemented. All still needs to be tested thoroughly. + Implemented multiscript support. It is now possible to execute multiple Sieve scripts sequentially. Administrator-controlled scripts can be executed before and after the user's script. Still needs to be tested thoroughly. + Implemented support for configuring the available Sieve extensions. + Made the subaddress extension (partially) configurable using the sieve_subaddress_sep setting, which allows specifying a (multi-charater) separator other than '+'. + Compiler now warns about invalid header field names used for the header and address tests. + Vacation extension now properly generates a References header for the response message. + Added testing of basic result execution to the test suite. Also added support for testing the outgoing messages produced by the Sieve interpreter. + Included execution of the actual result in the sieve-test command line tool. The undocumented sieve-exec tool that existed for this is now removed as planned. + Added support for the now obsolete 'imapflags' extension for backwards compatibility with CMUSieve. This also implements the mark/unmark commands. - Fixed bugs in the regex extension: 1) if an optional match value did not in fact match, subsequent match values would get unexpected indexes. 2) fixed segfault bug occuring when regex is freed. - Fixed bug in the use of the :from agrument for the vacation command. If this address included a phrase part, the response would not be a valid RFC822 message. - Plugged a theoretical security hole occuring when a directory is opened as a Sieve binary. - Cleaned up and fixed various log messages. - Fixed bug in the outgoing address verification. Addresses ending in ',' were erroneously accepted. Changelog ManageSieve v0.11.3: * Changed the SASL service name from "managesieve" into "sieve" as required in the protocol specification. Don't forget to adjust your configuration if your authentication mechanism depends on this service name. * Adapted to changes in Dovecot, making this release dependent on Dovecot >= v1.2.beta1. * Adapted to changes in the new Sieve implementation, making this release dependent on Dovecot Sieve >= v0.1.3 if used. The old cmusieve plugin is still supported. + Implemented making the SIEVE and NOTIFY capability fully dynamic, meaning that the sieve_extensions setting that was introduced for the new Sieve plugin properly affects the ManageSieve daemon as well. + Added support for the CHECKSCRIPT command. In terms of the supported commands, the ManageSieve daemon now complies with protocol VERSION 1.0 as listed in the CAPABILITY response. - Fixed maximum permissions for uploaded scripts; was 0777. This was shielded however by the default umask (not documented to be configurable), so the actual permissions would never have been 0777. - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed handling of ~/ in use of mail-data for script location. - Fixed small problems in the login proxy support. The following files are released: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.3.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.3.tar.gz.sig ManageSieve package: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.3.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.3.tar.gz.s… ManageSieve patch: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.beta1-managesieve-0.11.3.di… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.beta1-managesieve-0.11.3.di… Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] delivering to folder based on recipient_delimiter?
by dovecot＠corwyn.net 13 Feb '09

13 Feb '09

I'm currently running postfix + dovecot, with virtual users In postfix I have set recipient_delimiter = + so that postfix accepts mail for user(a)example.com, user+foo(a)example.com, and user+spam(a)example.com all deliver to inbox. what I would like is to have email directed to user+foo(a)example.com delivered to the IMAP folder foo (and, in the context of amavisd, have amavis configured for recipient_delimited, and add addr_extension_spam_maps add +spam to each mail identified as spam, and thus the mail would go to the spam folder on delivery. The postfix guys say I should be able to do this. can someone point me to how to implement this with dovecot? (as I don't see how to even start). Thx Rick Rick Steeves http://www.sinister.net "The journey is the destination"

3 3

[Dovecot] Can't remove folder (no thunderbird issue)
by Jan Niggemann 12 Feb '09

12 Feb '09

Hi, first of all: yes, I already dug the internet but didn't find a solution - that's why I'm asking you. My provider uses dovecot, although I can't tell you more about the version - sorry. Mail is stored in mbox format. My trouble: I was unable to create subfolders and googled a bit. A proposed solution was to append a slash at the end of the folder name. I used Thunderbird to create a folder and called it "test/" (yes, with a slash). Now, in both, Thunderbird and Mulberry, I'm unable to delete that folder (that contains neither messages nor subfolders). Mulberry doesn't give an error message, and in Thunderbird I can't find an option to remove this folder (no matter if subscribed or not). My provider uses roundcube as a webmail interface. Trying to delete the folder there seems to work OK, but after refreshing the folder-view it re-appears. I have no (ssh|telnet|...) access to the server, so I can't remove the folder using the shell.. Do I have other options than calling support? Thank you already jan

4 5

Re: [Dovecot] Mapping usernames
by Henry 12 Feb '09

12 Feb '09

On Thu 12/02/09 18:36 , Timo Sirainen tss(a)iki.fi sent: > abc(a)123.com:. > ...:user=realnamea_abc Thanks Timo, Unfortunately this is still not working. Any further comments would be appreciated. I've tried it two ways:- ATTEMPT 1 ---------------- /etc/dovecot.conf: auth default { userdb passwd-file { args = /etc/dovecot.passwd } passdb passwd-file { args = scheme=plain-md5 username_format=%u /etc/dovecot.passwd } } /etc/dovecot.passwd: bob@vh1.com:$1$Vh6a...::::::userdb_user=vh1_bob Error: auth(default): passwd-file(bob@vh1.com,::ffff:127.0.0.1): no passwd file: scheme=plain-md5 username_format=bob(a)vh1.com /etc/dovecot.passwd ATTEMPT 2 ---------------- /etc/dovecot.conf: auth default { userdb passwd-file { args = /etc/dovecot.passwd } passdb passwd-file { args = /etc/dovecot.passwd } } /etc/dovecot.passwd: bob@vh1.com:{PLAIN-MD5}$1$Vh6a...::::::userdb_user=vh1_bob Error: auth(default): passwd-file(bob@vh1.com,::ffff:127.0.0.1): unknown user I'm missing something obvious, I'm sure of it. Any pointers appreciated. Thanks -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.5 (GNU/Linux) mOIESXlwDRECAOycneJPOwSkETRkjJZdArag8V2rKOR2IUwlDOydIZXv/ITDlWDU dookzEdWh7Ektf1Jlh+YbPNEGoPpQunL8O8AoJbWmNkpoX7jP0Sw/5rDN2eKGHR7 Af9mxTqQ/j3C5LkrTRo9iCTt1TxoqPi6R/w0KkIAuTXBq6j+vIFJcOFgABlMQoXs V2crh1BUCmXVsV1puRJsLWKbAf4uL0V+N8WF4rvWHmJiYjgDn6exv3XHS0F6NhRz n1KVnV0XDWMDq/B/tmj4L2JYxEzWzeNulC5yQBOdx/dLU12XtCNIZW5yeSAoemVu LmNvLnphKSA8aGVucnlAemVuLmNvLnphPohgBBMRAgAgBQJJeXANAhsjBgsJCAcD AgQVAggDBBYCAwECHgECF4AACgkQCHhhdg2iQafVGACdEMtEuUGIW2XJyn9Fig7n sX4qzb4An0PGStBZvAP2qtzYP3SGlzsllzLjuI0ESXlwDRACAMsi4nl8/Yar2m9F ex4dFDgWylLgScQrEhhb2xN0Upcglm60nHQD7c1rP+63Iu+lU0eWvyr8o3JTCN4y PpoGMOMAAwUCAIUnLDMW/tz+qsYaOPyoh7HdAYqcrvVar7t+eKpihNBqfP4CT2Py aRVMN6cSJj9NKZDW6b0QQSCGgN7PpzrLqf6ISQQYEQIACQUCSXlwDQIbDAAKCRAI eGF2DaJBpxeiAJ9cNiuaftSoWke75RT1pn7qoibFfgCdHl6BgP9f450/oziDwaMM w49UeHQ= =qgmL -----END PGP PUBLIC KEY BLOCK-----

1 0

[Dovecot] sendmail smtp auth using client socket
by EQX 12 Feb '09

12 Feb '09

Hi list I searched the net, but could not find something related. Is it possible to export the client socket to sendmail for smtp auth? What would be the sendmail.mc configuration for this? #client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. #path = /var/spool/postfix/private/auth #mode = 0660 #user = postfix #group = postfix #} It can also be the other way round: can Dovecot use Cyrus SASL for user authentication? I need to use sendmail, ip based solutions like pop-before-smtp or poprelay are not an option. Thanks, Mike

4 4

[Dovecot] Mapping usernames
by Henry 12 Feb '09

12 Feb '09

Greets, We're using Dovecot 1.0.7 (which comes with CentOS 5.x). I have successfully configured dovecot to change a username from abc(a)123.com to realname1_abc for a machine which only has a single domain (using auth_username_format=realname1_%Ln). However, I'm pulling my hair out trying to get dovecot to handle multiple domains (the machine has existing /etc/passwd /etc/shadow and /etc/mail/virtusertable users). On an older machine, I simply hacked the source code to perform a berkeley DB lookup in /etc/mail/virtusertable.db for the realname[a-z0-9]_xx. This time round, though, I'm trying to do this cleanly. I've been reading the docs/wiki/etc but I now can't see the forest for the trees. This is what I've got so far: In /etc/dovecot.conf: ... auth default { userdb passwd-file { args = /etc/dovecot.passwd } passdb passwd-file { args = /etc/shadow #args = /etc/dovecot.passwd } } /etc/dovecot.passwd contains: realnamea_abc:{PLAIN-MD5}$1$Vjkfhaa....::::::userdb_user=abc@123.com I've been fiddling around blindly with all kinds of settings in userdb {} above, but I always get the error: "passwd-file(abc@123.com,::ffff:127.0.0.1): unknown user", amongst others. In a nutshell, I want to allow a user to login with abc(a)123.com, this name must be mapped to a real system user (eg, using /etc/dovecot.passwd), then authenticated against /etc/shadow or the MD5 password in /etc/dovecot.passwd I would appreciate any kind of pointers or advise here. It would have been nice if vpopmail allowed me to call an external perl script where I could perform the username mapping, but alas, this is not possible. Thanks Henry -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.5 (GNU/Linux) mOIESXlwDRECAOycneJPOwSkETRkjJZdArag8V2rKOR2IUwlDOydIZXv/ITDlWDU dookzEdWh7Ektf1Jlh+YbPNEGoPpQunL8O8AoJbWmNkpoX7jP0Sw/5rDN2eKGHR7 Af9mxTqQ/j3C5LkrTRo9iCTt1TxoqPi6R/w0KkIAuTXBq6j+vIFJcOFgABlMQoXs V2crh1BUCmXVsV1puRJsLWKbAf4uL0V+N8WF4rvWHmJiYjgDn6exv3XHS0F6NhRz n1KVnV0XDWMDq/B/tmj4L2JYxEzWzeNulC5yQBOdx/dLU12XtCNIZW5yeSAoemVu LmNvLnphKSA8aGVucnlAemVuLmNvLnphPohgBBMRAgAgBQJJeXANAhsjBgsJCAcD AgQVAggDBBYCAwECHgECF4AACgkQCHhhdg2iQafVGACdEMtEuUGIW2XJyn9Fig7n sX4qzb4An0PGStBZvAP2qtzYP3SGlzsllzLjuI0ESXlwDRACAMsi4nl8/Yar2m9F ex4dFDgWylLgScQrEhhb2xN0Upcglm60nHQD7c1rP+63Iu+lU0eWvyr8o3JTCN4y PpoGMOMAAwUCAIUnLDMW/tz+qsYaOPyoh7HdAYqcrvVar7t+eKpihNBqfP4CT2Py aRVMN6cSJj9NKZDW6b0QQSCGgN7PpzrLqf6ISQQYEQIACQUCSXlwDQIbDAAKCRAI eGF2DaJBpxeiAJ9cNiuaftSoWke75RT1pn7qoibFfgCdHl6BgP9f450/oziDwaMM w49UeHQ= =qgmL -----END PGP PUBLIC KEY BLOCK-----

2 1

[Dovecot] v1.2: Can't subscribe to shared user folder
by Sascha Wilde 12 Feb '09

12 Feb '09

Hi *, I stumbled across a small bug (missing feature?) in the new shared name space stuff: a001 list "" "*" * LIST (\Noselect \HasChildren) "/" "user" * LIST (\Noselect \HasChildren) "/" "user/bob(a)example.com" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "INBOX/bar" * LIST (\HasNoChildren) "/" "user/bob(a)example.com/brooklebookle" * LIST (\HasNoChildren) "/" "user/bob(a)example.com/foobar" a001 OK List completed. a002 lsub "" "*" a002 OK Lsub completed. a003 subscribe "user/bob(a)example.com/foobar" a003 NO Unknown subscription namespace. I'm quite sure this once worked in our original code (but of cause I could be mistaken). cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

2 2

[Dovecot] (Somewhat urgent) Problem with maildir++ quota
by Santiago Romero 12 Feb '09

12 Feb '09

Hi. I have an strange problem with dovecot's maildir quota and postfix. I've tested quota and it works fine but sometimes there are users that having their Maildir/ empty, they trigger the "quota exceeded" message when someone sends email to them. Some config / version info: ### Versions: ii dovecot-common 1:1.0.10-1ubuntu5.1 ii dovecot-imapd 1:1.0.10-1ubuntu5.1 ii dovecot-pop3d 1:1.0.10-1ubuntu5.1 ### From dovecot.conf: (...) # SQL database <doc/wiki/AuthDatabase.SQL.txt> userdb sql { # Path for SQL configuration file args = /etc/dovecot/dovecot-mysql.conf } (...) dict { #quota = mysql:/etc/dovecot-dict-quota.conf } (...) plugin { quota = maildir:storage=51200 } ### dovecot-mysql.conf (splitted to be readable): user_query = SELECT maildir, 5000 AS uid, 5000 AS gid, concat('maildir:storage=', floor(quota/1024)) AS quota FROM mailbox WHERE username = '%u' AND active = '1' ### Database "mailbox" record example: | prueba(a)domain.com | Password | prueba | domain.com/prueba/ | 51200000 | domain.com | 2009-02-02 10:01:24 | 2009-02-02 10:07:46 | 1 | The symptons: users are working nicely, and quota works (If I create a new user and set it a quota of, say, 1MB, I can send him msgs until Maildir reachs 1MB, after that I get "quota exceeded" messages). But sometimes there are users with the Maildir empty that can't receive messages and trigger the "quota exceeded" warning. Users always download messages by POP. Removing "maildirsize" file in their folder fixes the problem. Also fixes it changing the quota to any value (maildirsize is then removed and recreated after a new message arrives for the user). Sometime that I don't know if it's strange is that I don't see "removing" messages in the maildirsize file after user downloads messages. I mean that I can't see "-1" lines in maildirsizes: # cat prueba/maildirsize 51200000S 0 0 615 1 1540 1 11446 1 46085 1 2623 1 21218 1 2815301 1 15110 1 21289 1 18330 1 (and so). Any idea of what's going on? Shouldn't appear "MSGSIZE -1" lines in maildirsize file to "restore" space in Maildir after POP RETRs? Currently I'm fixing the problem with a regular: # find /home/vmail/vhosts -name "maildirsize" -exec rm {} \; But there must exist a better solution (or maybe my config is wrong). Thanks a lot for any help. -- Santiago Romero

2 3

[Dovecot] dovecot 1.2.beta1: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor
by e-frog 11 Feb '09

11 Feb '09

I'm currently trying out 1.2.beta1 and get the following error in 'mail.err' log file as soon as I stop dovecot: Feb 11 20:28:30 server dovecot: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor Is that anything critical? Thanks, e-frog -------------------------------------------------------------------------------- >: dovecot -n # 1.2.beta1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-11-server i686 Ubuntu 8.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/.mail mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota expire fts fts_squat mail_plugins(imap): quota imap_quota expire fts fts_squat mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: dovecot group: Debian-exim master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% expire: Trash 10 expire_dict: proxy::expiredict sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve fts: squat fts_squat: partial=4 full=10 dict: expiredict: mysql:/etc/dovecot/dovecot-dict-sql.conf

1 0

[Dovecot] Panic in dovecot 1.2.beta1
by Mark Sapiro 11 Feb '09

11 Feb '09

I tried Dovecot 1.2.beta1 yesterday. I had been using 1.1.11. I started getting "Panic: POP3(xxx): Trying to allocate 0 bytes" There are two kinds of pop3 users. In the attached log.txt file, user u1 is using a pop3 MUA. For users u2, u3, u4 and u5 fetchmail is coming through an ssh tunnel and retrieving their mail. u1 is able to interact normally with dovecot, but the fetchmail users encountered the panics in the log. dovecot -n is attached as dovecot-n.txt. At first I thought it was a locking issue as .lock files were being left behind, so I changed pop3_lock_session to no, and restarted dovecot, but this didn't help so I reverted to 2.1.11. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

[Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
by Harry Lachanas 11 Feb '09

11 Feb '09

Hi all, Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? Here is my conf #------------------------------------------------------------------------------------------ log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps ssl_ca_file: /etc/postfix/sasl/cacert.pem ssl_cert_file: /etc/postfix/sasl/cert.pem ssl_key_file: /etc/postfix/sasl/key.pem login_dir: /var/run/dovecot//login login_executable: /usr/local/dovecot-1.1.11/libexec/dovecot/imap-login valid_chroot_dirs: /var/mail mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes imap_client_workarounds: outlook-idle namespace: type: private separator: / location: maildir:~/Maildir inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/home/Public:INBOX=~/Maildir:INDEX=~/Maildir/p-idx:CONTROL=~/Maildir/p-ctrl list: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix #---------------------------------------------------------------------------------------------------------------- Cheers Harry.

4 6

[Dovecot] Adding new storage
by Romer Ventura 11 Feb '09

11 Feb '09

Hello, I am about to add more storage to the mail server and would like to know if it is as simple as it sounds..? I have: dovecot.conf mail_location: maildir:~/Maildir/ and /etc/dovecot/dovecot-ldap.conf with: user_attrs = sAMAccountName=mail=maildir:/home/vmail/%Ud/%Ln/Maildir/ So all the mail gets stored at /home/vmail/%Ud/%Ln/Maildir/ so if i add a new volume to the VM lets say /dev/disk3 and mount it to /srv/ vmail and then change the user_attrs = sAMAccountName=mail=maildir:/ home/vmail/%Ud/%Ln/Maildir/ to user_attrs = sAMAccountName=mail=maildir:/srv/vmail/%Ud/%Ln/Maildir/ would it work with no problem..? I would also need to move all the mailboxes already in the old location... I just want to make sure before i do anything.. Thanks

2 1

[Dovecot] Understanding dovecot ACLs
by Achim Hut 11 Feb '09

11 Feb '09

Hello List I am running a Cyrus IMAP that needs to be replaced. Geting a Dovecot IMAP up and running was surprisingly simple. My configuration is close to Johnny Chaddas Howto at http://johnny.chadda.se/2007/04/15/mail-server-howto-postfix-and-dovecot-wi… Its a Dovecot 1.1.10 on FreeBSD 6.4 Anyway, while basic setup was easy, i stuck in a couple of details like quota, managesieve, etc. Actual major problem and showstoper is understanding the ACLs the confuses me. So i need a hint to be guided in the right direction. What i need is a scenario, where user1 can get (for example) full access to the folders of user2, read-only access to user3 etc. A real world example: Secretary has full access to the mailfolders of her boss, boss has read-only acces to the sales-department folder. My questions: 1) is the possible? 2) can it be done with dovecot-acl files? 3) Namespaces: is it enough to have the private namespace for the job or do i need another namespace? 4) if yes, how should this namespace look like? Thanks for the help Achim

2 1

Re: [Dovecot] [Dovecot-news] v1.2.beta1 released
by Timo Sirainen 11 Feb '09

11 Feb '09

On Feb 10, 2009, at 10:45 PM, Reuben Farrelly wrote: > Feb 11 14:34:41 tornado dovecot: pop3-login: Login: user=<htperham>, > auth-method=PLAIN, remote=203.29.67.56 > Feb 11 14:34:41 tornado dovecot: Panic: POP3(htperham): Trying to > allocate 0 bytes .. > I can replicate this buy just telnetting to port 110, entering the > user and pass commands - as soon as I hit enter it dies :-( Fixed: http://hg.dovecot.org/dovecot-1.2/rev/22d70947597c

1 0

[Dovecot] dovecot logs to audit.log not to maillog
by Ralf Heidenreich 11 Feb '09

11 Feb '09

Hello, I have a curious phenomenon. Dovecot logs normally to /var/log/maillog. If I restart my server, dovecot loggs to /var/log/audit/audit.log. If I restart dovecot, dovecot loggs to /var/log/maillog again. And I think, wenn logrotate is restarting, dovecot logs to audit.log. But I don't know why. Any Ideas? greetings Ralf

2 3

[Dovecot] mailing lists and Dovecot deliver (lda)
by Roderick A. Anderson 11 Feb '09

11 Feb '09

I'm trying to figure out a way, or if it is even possible, to use mailing list software (majordomo2) on a Postfix + Dovecot + virtual mailboxes system. And where I should be looking. The examples on the Postfix site don't seem to address a purely virtual mailboxes system and I haven't found anything about doing it with deliver. I think I'm at the wrong tree (Dovecot deliver) and should be pestering the Postfix list. FTR, I host some sites for not-for-profits and they have asked about setting up lists. So far I've dodged the question but would like to attempt it now. Thanks, Rod --

2 2