- dovecot - dovecot.org

Re: [Dovecot] Postfix with Deliver (LDA) - user unknown
by Branislav Baca 06 Oct '07

06 Oct '07

Glenn wrote: > Howdy BB! Hopefully this helps to answer your questions... > > /etc/mail/postfix/vmailboxes contains: > > test(a)geekinetdev.com test/ > > /etc/passwd contains: > > test:*:5000:5000:test account for email:/var/mailboxes/test:/nonexistent probably you need here to have a full user@domain name. i.e: test@geekinetdev.com:*:5000:5000:test account for email:/var/mailboxes/test:/nonexistent > > The reason for the virtual_* stuff is that I am testing each program > configuration as I set up a new SMTP server. The goal is to move all > the virtual_* settings to MySQL. However, I want to walk before I run. > Not sure if that is part of my problem.?. Of course, you can leave it there, I've just said it is not necessary for dovecot to work. Also try to avoid using mysql, except you have dedicated mysql server or playing on small site with a lot of RAM. This is by my own experiences. LDAP is probably better solution but more complex to setup. > > Thanks for your assistance! > > glenn > > > Branislav Baca wrote: >> You have set in the main.cf: >> virtual_mailbox_maps = hash:/etc/mail/postfix/vmailboxes >> but dovecot deliver is using userdb for this purpose, which you have >> set to >> passwd. Have you equivalent data in both places? Similary nearly all >> configuration parameters in the main.cf of the postfix starting with >> virtual_??? are not required, but should be provided by userdb for >> dovecot >> deliver. >> >> BB >> >> On 1:26 04/10/07 "Karin Gregorec" <karinnv1(a)gmail.com> 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] dovecot cloning mails?
by Andreas Schneider 06 Oct '07

06 Oct '07

Hi, I have a strange issue here. I have a large message of a svn commit and the message is cloning itself more and more. I've deleted it several time completely but it doesn't go away. http://www.cynapses.org/tmp/dovecot.png How can I debug it? Thanks, -- andreas milliways:~ # dovecot -n # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): *:2000 ssl_ca_file: /etc/ssl/certs/cacert.pem ssl_cert_file: /etc/ssl/certs/milliways.pem ssl_key_file: /etc/ssl/private/milliways.key login_dir(default): /var/run/dovecot//login login_dir(imap): /var/run/dovecot//login login_dir(managesieve): 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 first_valid_uid: 150 last_valid_uid: 150 mail_extra_groups: mail mail_location: maildir:/srv/mail/%u maildir_copy_with_hardlinks: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): dspam mail_plugins(imap): dspam mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/modules/managesieve auth default: 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: mail plugin: dspam_spamfolder: Junk -- http://www.cynapses.org/ - cybernetic synapses

2 2

[Dovecot] Strange errors
by Ralf Hildebrandt 06 Oct '07

06 Oct '07

One of our users seems to have strange problems with his mailbox: Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096, but next_uid = 1097 Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096, but next_uid = 1097 Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Unexpected transaction log desync with index /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: marked corrupted Oct 2 02:40:54 postamt dovecot: IMAP(rbxxxx): Unlinked a duplicate: 1191278050.P11797Q0M631938.postamt.charite.de,S=3164:2, Oct 2 02:40:54 postamt dovecot: IMAP(rbxxxx): Maildir /home/r/b/rbxxxx/Maildir/.listen.CCL sync: UID inserted in the middle of mailbox (1097 > 1096, file = 1191278202.P12120Q0M512940.postamt.charite.de,S=5349:2,) Oct 2 13:46:12 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.jmol/dovecot.index.log: Append with UID 570, but next_uid = 571 Oct 2 13:46:12 postamt dovecot: IMAP(rbxxxx): Transaction log file /home/r/b/rbxxxx/Maildir/.listen.jmol/dovecot.index.log: marked corrupted Oct 2 13:46:12 postamt dovecot: IMAP(rbxxxx): Unlinked a duplicate: 1191322757.P13572Q0M515987.postamt.charite.de,S=3982:2,a Oct 2 13:46:12 postamt dovecot: IMAP(rbxxxx): Maildir /home/r/b/rbxxxx/Maildir/.listen.jmol sync: UID inserted in the middle of mailbox (571 > 570, file = 1191325571.P17909Q0M852537.postamt.charite.de,S=5674:2,) This is dovecot 1.0.5. -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Never underestimate the bandwidth of a station wagon full of tapes. -- Dr. Warren Jackson, Director, UTCS

2 2

[Dovecot] Timeout leak
by Lars Stavholm 06 Oct '07

06 Oct '07

In my development environment I sometimes get: dovecot: IMAP(stava): Timeout leak: 0x4425d0 Does anyone know what it means or how I can use this information? Cheers /Lars

2 2

[Dovecot] Corrupt Message?
by Daniel Watts 06 Oct '07

06 Oct '07

Dear List, Am accessing dovecot imap through squirrelmail. Squirrelmail paginates the message list into pages. All works fine except for the page one particular email is in. When I try to open that page (or in fact click 'show all') the server returns: ERROR: Bad or malformed request. Query: FETCH 549,551,555:557,563,565,567:569 (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type)]) Server responded: No mailbox selected. Could you possibly let me know what I should do and also how I can find the guilty mail file from that error? Can I just delete the email? Or is there a nice script to repair a dovecot maildir? Many thanks for your advice, Daniel -- Squirrelmail Stable 1.4.8 PHP 5.x Hardened with Eaccelerator Apache 2.x Imapproxy over Dovecot/Maildir all running on Gentoo Linux for ~5,000 users.

2 2

[Dovecot] How to upgrade a running Dovecot?
by Mike Brudenell 06 Oct '07

06 Oct '07

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? 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? 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? 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. *

2 1

[Dovecot] "Corrupted index cache file" error (Dovecot 1.0.3)
by Mike Brudenell 06 Oct '07

06 Oct '07

Greetings - Now that users are beginning to pile up more on our new Dovecot-based IMAP service I'm seeing a small number of entries like this in the logfiles: Corrupted index cache file /mailstore/index/o/ozw100/.INBOX/ dovecot.index.cache : invalid record size We are using Dovecot 1.0.3 with Maildir folders served over NFS from NetApp filers, but the index files are stored on local disk. By "a small number" I mean 4 or 5 on each of our two IMAP servers since midnight. * Should I be worried? * Is there anything I need to do fix the files? (I'm guessing not as no problem reports have come in, and the logs show the people affected continuing to work throughout the day.) * Would upgrading to 1.0.5 help? (I couldn't see anything in the Release Notes for either 1.0.4 or 1.0.5 about this) Cheers, 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. *

3 2

[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