- dovecot - dovecot.org

[Dovecot] Custom password encryption scheme, how to do it?
by Madison Kelly 06 Oct '07

06 Oct '07

Hi all, I'm a fairly recent convert to Dovecot/Postfix from Sendmail, so please be gentle (and assume I know nothing). :) I've got a Postfix/Dovecot/PostgreSQL setup with a custom DB schema for my email. This database is also used for a bigger program I use for all my hosting needs (domains, etc.). Currently, I've set it up to use plain-text authentication while I was developing it and getting things running. Now though it's up and running fine, so I want to increase the strength of my passwords that Postfix/Dovecot use. I currently have two fields in a table called 'users'; 'usr_password' which is plain-text and what Postfix/Dovecot currently use and 'usr_strong_password', which stores a stronger hash and is used by the main program. My question is, can I have Postfix/Dovecot use a custom password hashing system? The way I store my strong password (as used by the web-interface) is; - Take the password provided from the user - Read a stored 'salt' value from the database (unique per user and changed on password [re]sets). - Generate an initial SHA256 hash out of the password+salt. - Re-hash the initial SHA256 hash many thousands of times. - Compare the final hash with the hash stored in 'usr_strong_password'. If I can tell Dovecot how to do this, where would I do it? Is there a document/howto/etc someone could point me to? Is there a file I should look at? Thanks all!! Madi

3 3

[Dovecot] saslauth for digest or cram-md5?
by Knute Johnson 06 Oct '07

06 Oct '07

Is it possible to use saslauth for digest-md5 or cram-md5 authentication? If so how would one go about configuring dovecot? Thanks, -- Knute Johnson Molon Labe...

2 1

[Dovecot] imap sort assertion failure
by Andrew Garner 06 Oct '07

06 Oct '07

The following error occurred after a "SORT (TO) US-ASCII ALL" command. This only seems to happen with "to", all our other tests work as expected. Oct 1 20:32:49 dovecot: IMAP(example(a)example.com): pool_data_stack_realloc(): stack frame changed Oct 1 20:32:49 dovecot: IMAP(example(a)example.com): Raw backtrace: imap [0x80c5ed1] -> imap [0x80c5dec] -> imap [0x80cde63] -> imap [0x80c43c0] -> imap(buffer_write+0x85) [0x80c46f5] -> imap(buffer_append+0x26) [0x80c4766] -> imap [0x80be2f5] -> imap(message_header_decode+0x75) [0x80be3d5] -> imap(message_header_decode_utf8+0x56) [0x80be5f6] -> imap [0x80903c4] -> imap(index_mail_get_first_header+0x3e) [0x809125e] -> imap(mail_get_first_header_utf8+0x26) [0x80b4726] -> imap [0x809386b] -> imap [0x8093900] -> imap [0x809414e] -> imap(index_sort_list_finish+0x33) [0x80949d3] -> imap(index_storage_search_next_nonblock+0x3b6) [0x80924a6] -> imap(mailbox_search_next+0x30) [0x80b5b70] -> imap(imap_sort+0xdd) [0x806407d] -> imap(cmd_sort+0x2a4) [0x805d454] -> imap [0x805e7b9] -> imap [0x805e862] -> imap(client_input+0x65) [0x805ee85] -> imap(io_loop_handler_run+0x162) [0x80cc2a2] -> imap(io_loop_run+0x28) [0x80cb628] -> imap(main+0x4ab) [0x806643b] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc Oct 1 20:32:49 dovecot: child 31161 (imap) killed with signal 6 # dovecot -n # 1.1.beta2: /etc/dovecot/dovecot.conf protocols: imap pop3 listen: 127.0.0.1 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(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 89 mail_location: maildir:~/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): mail_plugins(imap): mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: mechanisms: plain cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf 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: vmail group: vmail

2 1

[Dovecot] Folder renaming oddities.
by Tan Shao Yi 06 Oct '07

06 Oct '07

Hi Timo, We are observing some weird behaviour when we try to rename an inferior folder, followed by the superior folder. These folders have an asterisk in the name. * LIST (\HasChildren) "." "*Own Family" * LIST (\HasChildren) "." "*Own Family.Tour" * LIST (\HasNoChildren) "." "*Own Family.Maid" * LIST (\HasNoChildren) "." "*Own Family.Tour.NZ" a OK List completed. a rename "*Own Family.Tour.NZ" "Own Family.Tour.NZ" a OK Rename completed. a LIST "" * * LIST (\HasChildren) "." "*Own Family" * LIST (\HasNoChildren) "." "*Own Family.Tour" * LIST (\HasNoChildren) "." "*Own Family.Maid" * LIST (\HasNoChildren) "." "Own Family.Tour.NZ" a OK List completed. a rename "*Own Family.Tour" "Own Family.Tour" a rename "*Own Family.Tour" "Own Family.Tour"a NO Internal error occurred. Refer to server log for more information. [2007-10-02 11:02:59] a LIST "" * * LIST (\HasChildren) "." "*Own Family" * LIST (\HasNoChildren) "." "*Own Family.Maid" * LIST (\HasChildren) "." "Own Family.Tour" * LIST (\HasNoChildren) "." "Own Family.Tour.NZ" dovecot: Oct 02 11:02:59 Error: IMAP(XXX): rename(/XXX/Maildir/.*Own Family.TourNZ, /XXX/Maildir/.Own Family.TourNZ) failed: No such file or directory It seems that the renaming of the folder succeeds, though the "a NO Internal error occurred" is reported. However, when the folders do not have an asterisk in the name. * LIST (\HasChildren) "." "Own Family" * LIST (\HasNoChildren) "." "Own Family.Maid" * LIST (\HasChildren) "." "Own Family.Tour" * LIST (\HasNoChildren) "." "Own Family.Tour.NZ" a rename "Own Family.Tour.NZ" "*Own Family.Tour.NZ" a OK Rename completed. a rename "Own Family.Tour" "*Own Family.Tour" a OK Rename completed. a LIST "" * * LIST (\HasChildren) "." "Own Family" * LIST (\HasNoChildren) "." "Own Family.Maid" * LIST (\HasChildren) "." "*Own Family.Tour" * LIST (\HasNoChildren) "." "*Own Family.Tour.NZ" The rename operation completes successfully with no error. Is there something that I am doing wrong? P.S., Will it be possible to also request the mail-log plugin to log rename operations too? :) Thanking in advance. Cheers, Tan Shao Yi

2 2

[Dovecot] Dovecot + OCFS2
by Jon Blazquez 06 Oct '07

06 Oct '07

Hello, We are running Red Hat Enterprise Linux AS release 4 (Nahant Update 4) with OCFS2 for our mail servers. There are three nodes in the cluster with shared storage and OCFS2 filesystem on it. The filesystem is used for mail storage(using Maildir layout) and is accessed by smtpd, pop3 and imap processes(DOVECOT). The system works fine but when there are mailing lists the load increases dramatically. It only occurs when there are mailing lists. We have tested it in lab with good results and now in production we are having some load problems caused by dovecot´s deliver process. In lab we had sent lots of mails but always to a few accounts. It was OK. Now there are sent less mails but there are more accounts. The load increases until it reaches about 100 and only restart fixes the problem. The umounting of the OCFS2 filesystem is not possible even when all process accessing it are killed. Any suggestions? TIA Info: Three nodes. OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 4) Mailbox format: Maildir SMTP daemon: Dovecot deliver + Sendmail OCFS2 version: 1.2.5-6 Kernel Version: 2.6.9-42.0.10.ELsmp Pop3 and imap daemon: Dovecot 1.0.3 -- _________________________________________________ Jon Blázquez Diez jblazquez(a)unav.es Servicios Informáticos https://www.unav.es/SI/ Universidad de Navarra https://www.unav.es _________________________________________________

4 4

[Dovecot] Subscribe to root of Maildir namespace?
by Adam Tilghman 06 Oct '07

06 Oct '07

Our users currently make use of a single namespace, mbox format: namespace private { separator = / prefix = hidden = no inbox = yes location = mbox:~/:INBOX=/var/spool/mail/%u:INDEX=/var/spool/poptemp/dovecot/%u } I'd like to give them access to additional Maildir-format storage area, so to the above I've added: namespace private { separator = / prefix = archive/ hidden = no location = maildir:/newmail/%-3.3i/%u/:INDEX=/var/spool/poptemp/dovecot/%u.a-thumper-mail } I can set up subfolders of archive/, and they work as expected. I can also designate the "root" of archive/ as INBOX and that works properly. But "SUBSCRIBE archive" fails. Is it possible to subscribe to the "root" of this new Maildir heirarchy as if it were just another folder? If not, would this be a useful feature to add? Thanks, -- Adam Tilghman | Systems Support / Academic Computing | +1 858 822 0711 agt(a)ucsd.edu | University of California, San Diego | fax +1 858 534 7018

2 1

[Dovecot] problematic ACL with shared folders and maildir
by Dominik L. Borkowski 05 Oct '07

05 Oct '07

Hello, Recently we have been asked to deploy some shared imap folders within our instance of dovecot. However, we ran into a problem with how ACLs are implemented, and consequences regarding maildir++ mailboxes. Long story short: * IMAP clients sees the hierarchy as a tree: sample/1, where 1 is a child of sample * on the filesystem, sample/1 is represented as .sample and .sample.1, both on the same level This presents a problem: dovecot-acl file meant for sample mailbox does not apply to mailbox 1. In fact, a user with permissions to create mailboxes under sample, will not be able to access those mailboxes, once created. Wonder if anybody has been in a similar predicament, and found a solution. Any hints would be greatly appreciated. PS) I'm also documenting this process, maybe others will find it useful: https://collaboration.vbi.vt.edu/display/~dom/dovecot+-+shared+imap+folders -- Dominik L. Borkowski - Senior Systems Administrator Virginia Bioinformatics Institute - www.vbi.vt.edu

1 0

Re: [Dovecot] How to upgrade a running Dovecot?
by Jerry Yeager 05 Oct '07

05 Oct '07

On Oct 5, 2007, at 12:41 PM, dovecot-request(a)dovecot.org wrote: > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Oct 2007 10:25:49 +0100 > From: Mike Brudenell <pmb1(a)york.ac.uk> > Subject: Re: [Dovecot] How to upgrade a running Dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <B9A4EC9A-82C0-4250-BC98-606695775041(a)york.ac.uk> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Hi, Jerry/et al - > Hello Mike, (stuff chomped out) > >>> Scenario 2: Altered SSL Certificates >>> ===================================== >>> I need to replace our current certificates and have prepared new >>> files containing the replacement certificate and private key. Am I >>> right in thinking that I can simply modify dovecot.conf to point at >>> the new files and send a HUP signal to dovecot? Specifically, will >>> new connections use the revised certificates, and existing >>> connections continue to work OK without interruption? >> >> Ehh not really, the auth child processes can be killed and new ones >> started. See your next scenario question. > > ...So here you're saying that although the "dovecot" master process > re-reads the configuration file, it doing so has no effect on the > existing authenticator child processes? And is it these processes > that are dealing with the SSL connection? ... I'd have thought it was > either the "imap-login" or "imap" processes? > Just to be clear about this for myself, (instead of relying on the 'ol saying 'that is how it used to work' -- because I am switching over to 1.1 from 1.0.n your question takes on new relevance for me as well) I tested this and yes it works as before, the new files seem to be used for the new connections (all of the dovecot auth processes are killed on the HUP signal -- dovecot itself just rereads the conf file and new auth listeners are started -- assuming that you use Dovecot for the auth mechanism to Postfix) and existing connections seem to handle things okay. I did find something new (or I have not noticed it before) If you kill (not just restart) the Dovecot process itself and restart it with existing connections (someone was connected to IMAPS when you killed Dovecot) Dovecot will not restart, complaining that port 993 is taken already. This happens regardless of the shutdown_clients = yes/no setting. This may be particular to the new version 1.1, I do not know. > Jerry

1 0

[Dovecot] Thunderbird and imap alerts
by Marco De Benedetto 05 Oct '07

05 Oct '07

Is Thunderbird supposed to show alerts sent via post-login scripts as in the wiki example? dovecot-imapd 1.0.5-1 (Debian) Thunderbird (Icedove) 2.0.0.4 (Debian) # dovecot -n|grep 'mail_executable(imap)' mail_executable(imap): /usr/local/sbin/dovecot-alert.sh # cat /usr/local/sbin/dovecot-alert.sh #!/bin/sh echo "* OK [ALERT] Hello World." exec /usr/lib/dovecot/imap Logging in with Thunderbird I get this alert: "Mail server imap.example.org is not an IMAP4 server". -- Thank you, Marco De Benedetto

1 0

Re: [Dovecot] How to upgrade a running Dovecot?
by Jerry Yeager 05 Oct '07

05 Oct '07

> Have you considered sending out a message to each user to the effect that on some day, darned-early a.m. the system will be offline for 30 minutes for maintenance (no incoming email will be lost, etc., etc.). > Message: 3 > Date: Thu, 4 Oct 2007 13:57:03 +0100 > From: Mike Brudenell <pmb1(a)york.ac.uk> > Subject: [Dovecot] How to upgrade a running Dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <06B4C604-41E3-4061-96B2-C7C719E21D49(a)york.ac.uk> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Greetings - > > Could someone confirm how to perform various upgrades on a live > system running Dovecot please? > > > Scenario 1: Change to dovecot.conf > =================================== > If I make a change to dovecot.conf am I right in thinking I can > simply send a HUP signal to the main dovecot process to get it to re- > read the configuration file and act on its revised content? > Yes, this is correct. > > Scenario 2: Altered SSL Certificates > ===================================== > I need to replace our current certificates and have prepared new > files containing the replacement certificate and private key. Am I > right in thinking that I can simply modify dovecot.conf to point at > the new files and send a HUP signal to dovecot? Specifically, will > new connections use the revised certificates, and existing > connections continue to work OK without interruption? > > Ehh not really, the auth child processes can be killed and new ones started. See your next scenario question. > Scenario 3: Software Upgrade > ============================= > I build a particular version of Dovecot into the tree /usr/local/ > dovecot-A.B.C and then have a symlink called "dovecot" pointing at > the this directory. To upgrade I can then build the new version > into /usr/local/dovecot-X.Y.Z and test. > > To actually switch over the live service to the new X.Y.Z version do > I need to: > > a) Totally shut down the old A.B.C version of Dovecot, thereby > breaking all > open connections for users? or > > b) Assuming I am using "shutdown_clients = no" can I just kill the > master > "dovecot" process and then start up the new version? > See the preface, do the update when you typically have few folks using the system -- which gives you fewer complaints from users should things break on their end. > Ideally I want existing connections to remain running, but new > connections to start up using the new X.Y.Z version of Dovecot. > > The comment for "shutdown_clients" implies this, but also says: > > "This however means that after master process has died, the > client > processes can't write to log files anymore." > > So if I understand this correctly then with "shutdown_clients = no" > in force then the sequence and behaviour is this? ... > > 1. Old version A.B.C of Dovecot running, clients can log > through the > master "dovecot" process to the logfiles. > > 2. Kill the old master "dovecot" process, start new X.Y.Z > version up. > > 3. New connections get served by version X.Y.Z. > Old connections DON'T get killed and can continue, BUT can > no longer > write anything to the logfiles? > > > With many thanks, > Mike B-) > > -- > The Computing Service, University of York, Heslington, York Yo10 > 5DD, UK > Tel:+44-1904-433811 FAX:+44-1904-433740 > > * Unsolicited commercial e-mail is NOT welcome at this e-mail > address. * > > > > >

4 3

[Dovecot] Compiling drac.c on a 64 bit system
by Robin Atwood 05 Oct '07

05 Oct '07

I have just installed dovecot and want to set up the drac interface. However, when I compile drac.c I get the following link errors; anybody know what the right compile options are for a 64 bit system? I have a Gentoo Linux system using the amd64 architecture. gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so -ldrac /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libdrac.a(dracauth.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libdrac.a: could not read symbols: Bad value collect2: ld returned 1 exit status TIA -Robin. -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ----------------------------------------------------------------------

2 2

[Dovecot] Deliver prints passwort to the syslog
by Dominik Schulz 05 Oct '07

05 Oct '07

Hi, I've got the problem that dovecot's deliver prints the authentification information to the syslog. Like this: Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: user=user(a)domain.tld Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: password=XXXX Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: home=/home/mail/domain.tld/user Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: uid=8 Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: gid=8 I guess that it's only a configuration option but right now I can't figure out which one I need to change to turn this off. Any help would be appreciated. Thanks in advance. Best Regards Dominik

3 3

[Dovecot] UIDL and IMAP
by Kenneth Porter 04 Oct '07

04 Oct '07

I finally got my aging FC2 box retired and moved all email to my new CentOS 5 box. My site is all-IMAP, no POP3. I have one user who downloads all email to Thunderbird on his laptop so that he can work offline while away from a network connection (eg. on an airplane). I forgot to change the pop3_uidl_format setting as described here: <http://wiki.dovecot.org/Upgrading/1.0> So he was seeing repeated downloads of all his mail (about 300 MBytes) every time he connected. (I'm not sure why it didn't happen only the first time.) I changed the setting and haven't heard back whether if fixed things for him. Does this setting in fact get used by IMAP? It's in the POP3 section, so I'm wondering if it takes effect when one is using IMAP from the client. CentOS 5 is currently shipping with: dovecot-1.0-1.2.rc15.el5 I may look for a newer release. CentOS, based on RHEL, is intended to be a conservative distro, so I'll probably need to look at RPMForge (an addon repository of more exotic and bleeding edge software) to see if it offers a newer release.

2 1

[Dovecot] Dovceot user pop3 last connect info?
by Tim Tyler 04 Oct '07

04 Oct '07

Dovecot experts, I am a newbie to Dovecot. I am in the process of replacing qpopper with dovecot to support pop 3 clients. I have installed the latest version of Dovecot on Fedora Core 6. Everything seems to be working fine using ldap, etc. However, with qpopper, I used to have .pop.username files which would give me a time stamp of the last time a user established a pop3 connection. I know that Dovecot has logs of connection in the /var/log/maillog files, but these files rotate out over a relatively short period of time. Is there a method by which one can keep track of the last time a pop3 connection was established for each user when using Dovecot? Tim Tyler Network Engineer - Beloit College tyler(a)beloit.edu

2 1

[Dovecot] Namespace "hidden" option not working?
by Ed W 04 Oct '07

04 Oct '07

I either misunderstand the namespace hidden option, or else perhaps it's not working correctly in 1.0.5? dovecot.conf # default namespace namespace private { separator = / prefix = inbox = yes hidden = yes } # for backwards compatibility: namespace private { separator = . prefix = INBOX. inbox = yes } Then login and test s6jh LIST "" "*" SND: <<< len(939) Comp_len(118) Time:0.137985 * LIST (\HasNoChildren) "/" "Diary" * LIST (\HasNoChildren) "/" "Spam" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Archive" * LIST (\HasNoChildren) "/" "Sent Items" * LIST (\HasNoChildren) "/" "Subdir" * LIST (\HasNoChildren) "/" "Junk E-mail" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Deleted Items" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "." "INBOX.Diary" * LIST (\HasNoChildren) "." "INBOX.Spam" * LIST (\HasNoChildren) "." "INBOX.Sent" * LIST (\HasNoChildren) "." "INBOX.Archive" * LIST (\HasNoChildren) "." "INBOX.Sent Items" * LIST (\HasNoChildren) "." "INBOX.Subdir" * LIST (\HasNoChildren) "." "INBOX.Junk E-mail" * LIST (\HasNoChildren) "." "INBOX.Trash" * LIST (\HasNoChildren) "." "INBOX.Drafts" * LIST (\HasNoChildren) "." "INBOX.Deleted Items" * LIST (\HasChildren) "." "INBOX" The idea was to support an old client using Courier like access whilst still letting new clients access using the normal process Ed W

3 6

[Dovecot] Disable imap proxy access
by Dominique Feyer 04 Oct '07

04 Oct '07

I work on a dovecot cluster (15 servers) we need to add a new storage array and move the data for a list of user from the old storage to the new one. We use dovecot proxy to redirect imap and pop3 to the same server everytime. How to disable pop3 and imap access during the data migration process (duration 5 minutes to 10 minutes). Can i send a custom error message to our users ? Thanks for your help Dominique Feyer

4 4

[Dovecot] Postfix with Deliver (LDA) - user unknown
by Karin Gregorec 04 Oct '07

04 Oct '07

Good Day All! I am attempting to configure deliver as our LDA. I am also configuring the server to use Postfix instead of Sendmail. I have followed the all the documentation and examples I could find. Below are my Dovecot and Postfix configs. Can someone please smack me upside the head and tell me why I am getting "user unknown" errors? If i don't use deliver as the LDA, all works perfectly. Help... TIA, glenn ========== *** Dovecot Config *** dovecot -n # 1.0.5: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/maillogs/dovecot.log protocols: imap imaps pop3 pop3s ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no verbose_ssl: yes 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_greeting: GID Ready login_log_format_elements: user=<%u> service=%s authMethod=%m rIP=%r lIP=%l encryption=%c login_max_processes_count: 256 verbose_proctitle: yes first_valid_uid: 5000 last_valid_uid: 10000 first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:~/Maildir dotlock_use_excl: yes fsync_disable: yes maildir_copy_with_hardlinks: yes 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_process_size: 1024 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): 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 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(pop3): top=%t/%T, retr=%r/%R, del=%d/%m, size=%s auth default: cache_size: 1024 cache_ttl: 604800 verbose: yes passdb: driver: pam args: cache_key=%Lu userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: maildrop plugin: quota: maildir:storage=10000000:ignore=Trash *** Postfix main.cf *** alias_database = hash:/etc/mail/postfix/aliases alias_maps = hash:/etc/mail/postfix/aliases biff = no command_directory = /usr/local/sbin daemon_directory = /usr/local/libexec/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 >$config_directory/$process_name.$process_id.log & sleep 5 #### Dovecot LDA Service - http://wiki.dovecot.org/LDA/Postfix dovecot_destination_recipient_limit = 1 home_mailbox = Maildir/ html_directory = no inet_interfaces = all mail_owner = postfix mail_spool_directory = /var/mail mailq_path = /usr/local/bin/mailq manpage_directory = /usr/local/man message_size_limit = 12000000 mydestination = $myhostname, localhost.$mydomain, localhost mydomain = geekinternetdevelopment.com myhostname = superman.geekinternetdevelopment.com mynetworks = 72.18.193.0/24, 127.0.0.0/8 newaliases_path = /usr/local/bin/newaliases queue_directory = /var/spool/postfix readme_directory = no sample_directory = /usr/local/etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = maildrop smtpd_banner = $myhostname NO WHAMMIES!!! virtual_gid_maps = static:5000 virtual_mailbox_base = /var/mailboxes virtual_mailbox_domains = hash:/etc/mail/postfix/vdomains virtual_mailbox_maps = hash:/etc/mail/postfix/vmailboxes virtual_minimum_uid = 1000 virtual_transport = dovecot virtual_uid_maps = static:5000 unknown_local_recipient_reject_code = 550 *** Postfix master.cf *** ...snip... dovecot unix - n n - - pipe flags=DRhu user=maildrop:maildrop argv=/usr/local/libexec/dovecot/deliver -e -d ${recipient}

4 3

[Dovecot] autocreate plugin
by Lars Stavholm 04 Oct '07

04 Oct '07

Did anyone get the autocreate plugin working? I've compiled, installed and configured, but no mailboxes/folders are created. /L

1 1

Re: [Dovecot] Postfix with Deliver (LDA) - user unknown
by Lars Stavholm 04 Oct '07

04 Oct '07

Let's try to keep this on the list shall we. hgic(a)geekazoid.com wrote: > Here is the conversation from my maillog: > Oct 3 20:52:15 superman postfix/pickup[179]: B77EA130C28: uid=0 from=<root> > Oct 3 20:52:15 superman postfix/cleanup[232]: B77EA130C28: > message-id=<20071004035215.B77EA130C28(a)superman.geekinternetdevelopment.com> > Oct 3 20:52:15 superman postfix/qmgr[98583]: B77EA130C28: > from=<root(a)superman.geekinternetdevelopment.com>, size=375, nrcpt=1 (queue > active) > Oct 3 20:52:15 superman postfix/pipe[234]: B77EA130C28: > to=<test(a)geekinetdev.com>, relay=dovecot, delay=0.25, > delays=0.16/0.01/0/0.08, dsn=5.1.1, status=bounced (user unknown) > Oct 3 20:52:15 superman postfix/cleanup[232]: E0729130C32: > message-id=<20071004035215.E0729130C32(a)superman.geekinternetdevelopment.com> > Oct 3 20:52:15 superman postfix/bounce[236]: B77EA130C28: sender > non-delivery notification: E0729130C32 > Oct 3 20:52:15 superman postfix/qmgr[98583]: E0729130C32: from=<>, > size=2294, nrcpt=1 (queue active) > Oct 3 20:52:15 superman postfix/qmgr[98583]: B77EA130C28: removed > Oct 3 20:52:16 superman postfix/local[237]: E0729130C32: > to=<geekserver(a)superman.geekinternetdevelopment.com>, Do you have a user called "geekserver". Looks a bit dodgy. > orig_to=<root(a)superman.geekinternetdevelopment.com>, relay=local, dovecot is a bit peculiar with the "root" user. You should always alias that to a real user. Or maybe you have. > delay=0.13, delays=0.06/0.01/0/0.06, dsn=5.1.1, status=bounced (unknown > user: "geekserver") Well, do you have a user called "geekserver"? > Oct 3 20:52:16 superman postfix/qmgr[98583]: E0729130C32: removed > > dovecot.log has: > > dovecot: Oct 03 08:57:04 Info: auth(default): > passwd(test(a)geekinetdev.com): unknown user That seems to be unrelated to the above. /L > dovecot-deliver.log is empty... > > Thanks for your assistance!!! ;-) > > glenn > >> System log could help. >> /L >> >> Karin Gregorec wrote: >>> Good Day All! I am attempting to configure deliver as our LDA. I am >>> also configuring the server to use Postfix instead of Sendmail. I >>> have followed the all the documentation and examples I could find. >>> >>> Below are my Dovecot and Postfix configs. Can someone please smack me >>> upside the head and tell me why I am getting "user unknown" errors? >>> If i don't use deliver as the LDA, all works perfectly. Help... >>> >>> TIA, >>> glenn >>> >>> ========== >>> >>> >>> *** Dovecot Config *** >>> >>> dovecot -n >>> # 1.0.5: /usr/local/etc/dovecot.conf >>> base_dir: /var/run/dovecot/ >>> log_path: /var/log/maillogs/dovecot.log >>> protocols: imap imaps pop3 pop3s >>> ssl_cipher_list: ALL:!LOW >>> disable_plaintext_auth: no >>> verbose_ssl: yes >>> 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_greeting: GID Ready >>> login_log_format_elements: user=<%u> service=%s authMethod=%m rIP=%r >>> lIP=%l encryption=%c >>> login_max_processes_count: 256 >>> verbose_proctitle: yes >>> first_valid_uid: 5000 >>> last_valid_uid: 10000 >>> first_valid_gid: 0 >>> mail_extra_groups: mail >>> mail_location: maildir:~/Maildir >>> dotlock_use_excl: yes >>> fsync_disable: yes >>> maildir_copy_with_hardlinks: yes >>> 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_process_size: 1024 >>> mail_plugins(default): quota imap_quota >>> mail_plugins(imap): quota imap_quota >>> mail_plugins(pop3): >>> 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 >>> imap_client_workarounds(default): delay-newmail outlook-idle >>> netscape-eoh tb-extra-mailbox-sep >>> imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh >>> tb-extra-mailbox-sep >>> imap_client_workarounds(pop3): outlook-idle >>> pop3_uidl_format(default): >>> pop3_uidl_format(imap): >>> pop3_uidl_format(pop3): %08Xu%08Xv >>> pop3_client_workarounds(default): >>> pop3_client_workarounds(imap): >>> pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh >>> pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s >>> pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s >>> pop3_logout_format(pop3): top=%t/%T, retr=%r/%R, del=%d/%m, size=%s >>> auth default: >>> cache_size: 1024 >>> cache_ttl: 604800 >>> verbose: yes >>> passdb: >>> driver: pam >>> args: cache_key=%Lu >>> userdb: >>> driver: passwd >>> socket: >>> type: listen >>> master: >>> path: /var/run/dovecot/auth-master >>> mode: 384 >>> user: maildrop >>> plugin: >>> quota: maildir:storage=10000000:ignore=Trash >>> >>> >>> *** Postfix main.cf *** >>> >>> alias_database = hash:/etc/mail/postfix/aliases >>> alias_maps = hash:/etc/mail/postfix/aliases >>> biff = no >>> command_directory = /usr/local/sbin >>> daemon_directory = /usr/local/libexec/postfix >>> >>> debug_peer_level = 2 >>> debugger_command = >>> PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; >>> echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 >>> >$config_directory/$process_name.$process_id.log & sleep 5 >>> >>> #### Dovecot LDA Service - http://wiki.dovecot.org/LDA/Postfix >>> dovecot_destination_recipient_limit = 1 >>> >>> home_mailbox = Maildir/ >>> html_directory = no >>> inet_interfaces = all >>> mail_owner = postfix >>> mail_spool_directory = /var/mail >>> mailq_path = /usr/local/bin/mailq >>> manpage_directory = /usr/local/man >>> message_size_limit = 12000000 >>> mydestination = $myhostname, localhost.$mydomain, localhost >>> mydomain = geekinternetdevelopment.com >>> myhostname = superman.geekinternetdevelopment.com >>> mynetworks = 72.18.193.0/24, 127.0.0.0/8 >>> newaliases_path = /usr/local/bin/newaliases >>> queue_directory = /var/spool/postfix >>> readme_directory = no >>> sample_directory = /usr/local/etc/postfix >>> sendmail_path = /usr/local/sbin/sendmail >>> setgid_group = maildrop >>> smtpd_banner = $myhostname NO WHAMMIES!!! >>> >>> virtual_gid_maps = static:5000 >>> virtual_mailbox_base = /var/mailboxes >>> virtual_mailbox_domains = hash:/etc/mail/postfix/vdomains >>> virtual_mailbox_maps = hash:/etc/mail/postfix/vmailboxes >>> virtual_minimum_uid = 1000 >>> virtual_transport = dovecot >>> virtual_uid_maps = static:5000 >>> unknown_local_recipient_reject_code = 550 >>> >>> *** Postfix master.cf *** >>> ...snip... >>> dovecot unix - n n - - pipe >>> flags=DRhu user=maildrop:maildrop >>> argv=/usr/local/libexec/dovecot/deliver -e -d ${recipient} >

1 0

[Dovecot] In-site migration from /etc/passwd to LDAP
by Maykel Moya 04 Oct '07

04 Oct '07

I'm doing in-site migration of accounts from /etc/passwd to an LDAP directory. The migration should be progressive (not all users at the same time). I'm already able to check mail for accounts in /etc/passwd and accounts in LDAP. The problem is with mail delivery. I'm using Postfix + Dovecot-LDA. This is the error I get with every delivery -- dovecot: Oct 03 00:16:09 Info: auth(default): master in: USER 1 moya service=deliver dovecot: Oct 03 00:16:09 Info: auth(default): ldap(moya): user search: base=ou=users,dc=sld,dc=cu scope=subtree filter=(&(objectClass=posixAccount)(uid=moya)) fields=sldMailbox,uidNumber dovecot: Oct 03 00:16:09 Info: auth(default): master out: USER 1 moya home=/srv/vmail/m/moya/ uid=29174 gid=101 deliver(moya): Oct 03 00:16:09 Fatal: setuid(29174) failed: Operation not permitted -- 29174 is the uid for moya, is the same in /etc/passwd or in LDAP via posixAccount class. Any advise please? Regards, maykel

3 4

[Dovecot] new antispam plugin
by Johannes Berg 03 Oct '07

03 Oct '07

Sparked from the discussion on the list, I've put my antispam plugin into git and split up the code into a frontend and possibly multiple backends. See http://git.sipsolutions.net/dovecot-antispam.git/ (URL functions as both gitweb and git URL) Andreas, I took your README file and adjusted it, I hope you don't mind. I didn't fork from your git tree because you'd already implemented the libdspam backend there. Maybe you could take a look at the new backend/frontend separation and implement a libdspam backend. Aria, it should be possible to write a spamassassin plugin, quite easily if spamassassin supports training based on signatures, not quite so easily otherwise though I intend to plan this. Timothy, you could write the mysql logger as a backend too. I take patches :) Oh and as always thanks to Timo for implementing such a nice server and string, memory and mail handling API. johannes

4 17

[Dovecot] --enable-headers-install problem in 1.0.5
by Trever L. Adams 02 Oct '07

02 Oct '07

I am trying to get a SPEC file for an RPM to build a devel package. I have it working, except for one thing. 1.0.5 doesn't actually install the headers with that option to configure found in the subject. It does create the directory, but it doesn't put the files there. Timo, is this a known/unknown bug, or am I doing something stupid? Thanks, Trever

3 2

[Dovecot] SORT(DATE) and missing Date headers
by Kyle Wheeler 02 Oct '07

02 Oct '07

Hello, Occasionally, I get mail that's missing a Date header. The usual suspects are iTunes weekly mailings and NYTimes email-to-a-friend articles. I use qmail, which doesn't "fix" these malformed emails by adding a Date header (like Sendmail does), so when they get to my mailbox, they're just as badly formed as they were when they were sent, which is to say, they have no Date header. Unfortunately, this means that SORT (DATE) puts them at the beginning of the list---and in a mailbox with lots of old mail, that's usually the wrong spot. Now, my email clients will do some basic guesswork about when the message was sent, usually by falling back on the timestamp of the first-added Received header. So, they will display a date. But they have to then sort all messages themselves in order to get a valid sorting. Would it be possible to get Dovecot to fall back to Received header parsing whenever a message is missing a Date header? The idea is that SORT (DATE) would then become useful even in the face of commonly malformed email. How hard would this be to hack into the current Dovecot source? Does this maybe exist already (e.g. as SORT (X-DATE)? ~Kyle -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -- Ed Howdershelt

3 7

[Dovecot] Slight problem with dovecot + IMAP
by Timothy Murphy 02 Oct '07

02 Oct '07

I'm running dovecot on my desktop with kmail as IMAP client on my laptop. When I start kmail on the laptop it sometimes takes several minutes to "calm down". The number of messages listed in the IMAP inbox increases greatly - maybe from 2500 to 3000 - and then slowly decreases. There are sometimes a large number of duplicate messages, which kmail allows one to delete. I don't know if this is a kmail or dovecot problem. It is quite likely there is something wrong in my setup. Any suggestions or advice gratefully received.

2 4

[Dovecot] IMAP Fetch fails with BAD instead of NO
by Reinier Bezuidenhout 02 Oct '07

02 Oct '07

Hi, I'm running version 1.0.3 of dovecot using IMAP and using javamail to access the mail. The application I'm using (when stress testing the system by doing simultaious creation of email and deleting emails, it sometimes get into the state where the application (via javamail) ask for the UID of a message that has been expunged and deleted (no longer exists). Dovecot returns with the following error: AXXX FETCH 14 (UID) AXXX BAD Error in IMAP command FETCH: Invalid messageset This can easily be reproduced by using telnet to 143 and giving the command by hand. When I read through the source code, there were obvious comments that states the dovecot will not return NO on fetch errors, only BAD. So I assume it is done on purpose. My question is that in RFC 3501 for fetch it says: (section 6.4.5) Result: OK - fetch completed NO - fetch error: can't fetch that data BAD - command unknown or arguments invalid No I guess a UID that is out of range could be considered "arguments invalid", but shouldn't it be a soft error with NO as a result where "can't fetch that data" is more appropriate according the the RFC. The command isn't syntactically BAD, the requested data just does not exists. The same command tested against another IMAP server returns AXXX NO message not available Not that they are necessarily correct, but it just begs the question. Thanks Reinier Running on FreeBSD 6.x (x86) devmail# dovecot -n # 1.0.3: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no 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 valid_chroot_dirs: /var/mail verbose_proctitle: yes first_valid_uid: 3000 last_valid_uid: 5000 first_valid_gid: 0 mail_extra_groups: mail mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_debug: yes maildir_copy_with_hardlinks: yes 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_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 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap-user.conf userdb: driver: prefetch devmail#

2 2