- dovecot - dovecot.org

[Dovecot] Client can't connect to SMTP
by Jeremy Gillick 04 May '08

04 May '08

I've just installed Dovecot and Postfix and my email client (Mac Mail) cannot authenticate with the SMTP server. The error I receive says that "The SMTP server doesn't support SSL (TLS) on port 465" -- yet, I've installed SSL. Is there any good way to test or debug this? Setup: * SSL * Dovecot SASL * Dovecot LDA * Virtual Users (http://wiki.dovecot.org/HowTo/SimpleVirtualInstall) Client SMTP Setup: * Use SSL * Port: 465 * Authentication: Password By the way, I followed these instructions: http://wiki.dovecot.org/HowTo/SimpleVirtualInstall Dovecot version: 1.0.13 (from source) Postfix version: 2.5.1 (from source) OS: Fedora Core 4 Here's are my config files: DOVECOT # 1.0.13: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap pop3 imaps pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/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 mail_location: maildir:~/Maildir dotlock_use_excl: 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 pop3_uidl_format: %08Xu%08Xv auth default: mechanisms: plain login verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=postfix gid=postfix home=/home/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: vmail ------ POSTFIX (main.cf) alias_maps = $alias_database broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 html_directory = no inet_interfaces = $myhostname, localhost mail_owner = postfix mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = mixermixer3.com myhostname = mixermixer3.com newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix/ readme_directory = no relay_domains = $mydestination sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /etc/postfix/ssl/smtpd.pem smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_key_file = /etc/postfix/ssl/smtpd.pem smtpd_tls_loglevel = 1 smtpd_tls_session_cache_timeout = 3600s unknown_local_recipient_reject_code = 550 virtual_mailbox_domains = mixermixer3.com virtual_transport = dovecot ------ POSTFIX (a few key lines from master.cf) smtp inet n - n - - smtpd smtps inet n - n - - smtpd # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING smtp unix - - n - - smtp # Dovecot LDA dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} THANKS, Jeremy

2 1

[Dovecot] Dovecot 1.1: Ignoring Trash/Junk for maildirsize?
by richs＠whidbey.net 04 May '08

04 May '08

Hi all, We're testing Dovecot 1.1rc3, but have run into a snag with IMAP Quota's and the way Trash and Junk folders can be handled. Our MTA (Exim) quota configuration uses this option: maildir_quota_directory_regex = ^(?:cur|new|\.(?!Junk$)(?!Trash$).*)$ This completely excludes "Junk" and "Trash" from the "maildirsize" file and quota calculations. Dovecot 1.0 could do this using "ignore=Trash" (although only on one folder). Is there any way to duplicate this behavior in Dovecot 1.1? We see that "quota_rule" can be used to set an unlimited quota (storage=0), but for some reason Dovecot still records their tallies in "maildirsize", which breaks the MTA. Thanks! -Rich

2 1

[Dovecot] Cross-Realm Krb5 Patch
by Zachary Kotlarek 04 May '08

04 May '08

I've updated my krb5 cross-realm auth patch for dovecot 1.1-rc4; there are not any (intentional) changes in functionality from the last patch, the diff just didn't apply cleanly anymore. As before the most recent version of the patch is available at: http://zinux.cynicbytrade.com/svn/servers/dovecot/cross-realm.diff.bz2 I see the cross-realm patch for Solaris made it into the mainline. What if anything can I do to encourage the mainline adoption of my non- Solaris patch? Zach

2 1

[Dovecot] Patch for zlib and maildir for 1.0.13
by Richard Platel 04 May '08

04 May '08

When using the zlib plugin with maildir and copying with hardlinks, if a compressed message is copied, the 'Z' suffix on the file isn't copied, so the new message isn't uncompressed when it's fetched. I wasn't smart enough to figure out a clean way to carry a file suffix through a copy, so I changed how the zlib-plugin detects if a message is compressed. This patch peeks at the first two bytes of the message looking for the zlib header. -- Richard Platel Tucows

3 3

[Dovecot] 1.1rc4 problem with maildir++ quota and POP3
by Laurent Papier 04 May '08

04 May '08

Hi, it looks like there is a bug (in dovecot or in my config) with quota on maildir mailboxes when accessed via POP3. The maildirsize is not created when not already present (even after a DELE + QUIT command). The quota limit (the first line of maildirsize) is not updated if values are not in sync with those in the database. If maildirsize is present, DELE commands are correctly reported in maildirsize. maildirsize is correctly updated when the same mailbox is accessed in IMAP or mail is delivered with dovecot LDA. Here is my config. Timo 'dovecot -n' does not show the lda config part... # 1.1.rc4: /etc/dovecot.conf protocols: imap pop3 ssl_disable: yes 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: please to meet you login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 100 login_max_processes_count: 512 max_mail_processes: 3072 mail_uid: 1000 mail_gid: 1000 mail_location: maildir:~/ mmap_disable: yes maildir_stat_dirs: 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): imap_quota quota mail_plugins(imap): imap_quota quota 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): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls auth default: user: nobody passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: mailonly group: mailonly plugin: quota: maildir quota_rule2: Trash:storage=12288:messages=100 --- SQL queries ---- # prefetch auth password_query = SELECT cpasswd as password, home as userdb_home, concat('*:bytes=',quotas,':messages=',quotai) AS userdb_quota_rule FROM `mail` WHERE email='%u' # for delivery user_query = SELECT home, concat('*:bytes=',quotas,':messages=',quotai) AS quota_rule FROM `mail` WHERE email='%u' -- Laurent Papier - 03 88 75 80 50 Admin. système - SdV Plurimedia - <http://www.sdv.fr/>

2 1

[Dovecot] Global and personal sieve scripts
by Juan Asensio Sánchez 04 May '08

04 May '08

Hi According to Dovecot documentation (): # If there is no user-specific Sieve-script, global Sieve script is # executed if set. (v1.0.1 and older used "global_script_path") #sieve_global_path = Then, if one user has its own script, the global script won't be executed? I would like to execute first the global script (for moving SPAM to the Junk folder), and then the user scripts is they exists. Any idea? Thanks in advance.

2 1

[Dovecot] GETQUOTAROOT?
by Ralf Hildebrandt 04 May '08

04 May '08

All over a sudden the getquota plugin in SquirrelMail doesn't work anymore. I activated debugging an got: IMAP command sent: a001 GETQUOTAROOT "INBOX" IMAP response received: Array ( [0] => * QUOTAROOT "INBOX" "" [1] => * QUOTA "" () ) A manual test results in: . GETQUOTAROOT "INBOX" * QUOTAROOT "INBOX" "" * QUOTA "" () . OK Getquotaroot completed. But that mailbox DOES have a quota defined. This is dovecot-1.0.x from the Mercurial repo. I'm using: quota = maildir quota = maildir:ignore=Trash quota_warning = storage=10%% /usr/local/scripts/quota-warning 90 quota_warning2 = storage=5%% /usr/local/scripts/quota-warning 95 quota_warning3 = storage=1%% /usr/local/scripts/quota-warning 99 which works fine otherwise. -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de In brightest day, in blackest night no evil shall escape my sight!

2 4

[Dovecot] [patch] let valgrind run on login process with GDB=1
by Diego Liziero 04 May '08

04 May '08

Not sure if this should be included in dovecot, just posting if someone feels like using valgrind. Diego. ----- diff -r ba634d2c0ab9 src/master/login-process.c --- a/src/master/login-process.c Wed Apr 30 20:18:37 2008 +0300 +++ b/src/master/login-process.c Thu May 01 00:59:10 2008 +0200 @@ -689,7 +689,8 @@ static pid_t create_login_process(struct fd_limit = 16 + listen_count + ssl_listen_count + 2 * (group->set->login_process_per_connection ? 1 : group->set->login_max_connections); - restrict_fd_limit(fd_limit); + if (getenv("GDB") == NULL) + restrict_fd_limit(fd_limit); /* make sure we don't leak syslog fd, but do it last so that any errors above will be logged */

2 1

[Dovecot] Need Help! (Bug Report)
by 이경준 04 May '08

04 May '08

Need Help!! Server : AIX 5.3 Compile Error Message configure --------------------------------- checking jfs/quota.h usability... no checking jfs/quota.h presence... yes configure: WARNING: jfs/quota.h: present but cannot be compiled configure: WARNING: jfs/quota.h: check for missing prerequisite headers? configure: WARNING: jfs/quota.h: see the Autoconf documentation configure: WARNING: jfs/quota.h: section "Present But Cannot Be Compiled" configure: WARNING: jfs/quota.h: proceeding with the preprocessor's result configure: WARNING: jfs/quota.h: in the future, the compiler will take precedence configure: WARNING: ## ---------------------------------- ## configure: WARNING: ## Report this to dovecot(a)dovecot.org ## configure: WARNING: ## ---------------------------------- ## checking for jfs/quota.h... yes checking mntent.h usability... yes make -------------------------- et/libcharset.a ../../../src/lib/liblib.a -liconv + exec /usr/vacpp/bin/xlc -g -bexpall -brtl -o convert-tool convert-tool.o ./../../src/lib-storage/register/libstorage-register.a ../../../src/lib- storage/index/maildir/libstorage_maildir.a ../../../src/lib- storage/index/mbox/libstorage_mbox.a ../../../src/lib- storage/index/libstorage_index.a ../../../src/lib-index/libindex.a ./../../src/lib-storage/libstorage.a ../../../src/lib-storage/subscription- file/libstorage_subscription_file.a ../../../src/lib-imap/libimap.a ../../.. /src/lib-mail/libmail.a ../../../src/lib-charset/libcharset.a ./../../src/lib/liblib.a -liconv -bE:.libs/libstorage-register.exp - bE:.libs/libstorage_maildir.exp -bE:.libs/libstorage_mbox.exp - bE:.libs/libstorage_index.exp -bE:.libs/libindex.exp - bE:.libs/libstorage.exp -bE:.libs/libstorage_subscription_file.exp - bE:.libs/libimap.exp -bE:.libs/libmail.exp -bE:.libs/libcharset.exp - bE:.libs/liblib.exp Target "all" is up to date. Making all in quota source='quota.c' object='quota.lo' libtool=yes DEPDIR=.deps depmode=aix /bin/sh ../../../depcomp /bin/sh ../../../libtool --tag=CC -- mode=compile /apps1/bea8/domains/eipDomain/handy/down/dovecot/imap/dovecot- 1.0.13/dovecot-cc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib - I../../../src/lib-dict -I../../../src/lib-index -I../../../src/lib-mail - I../../../src/lib-storage -I../../../src/lib-storage/index - I../../../src/lib-storage/index/maildir -g -c -o quota.lo quota.c mkdir .libs /apps1/bea8/domains/eipDomain/handy/down/dovecot/imap/dovecot- 1.0.13/dovecot-cc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I.. /../../src/lib-dict -I../../../src/lib-index -I../../../src/lib-mail -I../.. /../src/lib-storage -I../../../src/lib-storage/index -I../../../src/lib- storage/index/maildir -g -c -M quota.c -DPIC -o .libs/quota.o + exec /usr/vacpp/bin/xlc -DHAVE_CONFIG_H -I. -I. -I../../.. - I../../../src/lib -I../../../src/lib-dict -I../../../src/lib-index - I../../../src/lib-mail -I../../../src/lib-storage -I../../../src/lib- storage/index -I../../../src/lib-storage/index/maildir -g -c -M quota.c - DPIC -o .libs/quota.o "/usr/include/sys/ras.h", line 273.49: 1506-207 (W) Integer constant 0x5200000000000110ul out of range. "/usr/include/sys/ras.h", line 273.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 276.49: 1506-207 (W) Integer constant 0x5200000000000210ul out of range. "/usr/include/sys/ras.h", line 276.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 279.49: 1506-207 (W) Integer constant 0x5200000000000310ul out of range. "/usr/include/sys/ras.h", line 279.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 283.49: 1506-207 (W) Integer constant 0x5200000000000120ul out of range. "/usr/include/sys/ras.h", line 283.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 286.49: 1506-207 (W) Integer constant 0x5200000000000220ul out of range. "/usr/include/sys/ras.h", line 286.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. "/usr/include/sys/ras.h", line 289.49: 1506-207 (W) Integer constant 0x5200000000000320ul out of range. "/usr/include/sys/ras.h", line 289.1: 1506-195 (S) Integral constant expression with a value greater than zero is required. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 2.

2 1

[Dovecot] deliver: handling of quota_full_tempfail and -e
by Ulrich Zehl 04 May '08

04 May '08

Hi, while testing out dovecot 1.1, I found that when you set quota_full_tempfail = yes in dovecot.conf and use the deliver -e command line flag, no deferral reason is printed, thus breaking my fancy quota_exceeded_message. This appears to be because of the if() block in lines 1003-1009 in src/deliver/deliver.c, and should be easily fixable (if it is indeed a bug, and not intended behavior). However, I shied away from creating a patch because either there is a mismatch between the documentation and deliver's actual behavior, or I misunderstood the code (likely, since I'm not really a C programmer). The lines in question (in src/deliver/deliver.c) read: | 1003 if (error != MAIL_ERROR_NOSPACE || | 1004 getenv("QUOTA_FULL_TEMPFAIL") != NULL) { Does this mean that the corresponding block gets executed whenever quota_full_tempfail is set? If so, setting it transforms all errors into TEMPFAILs, and not only those relating to quota/space issues. I think dovecot-example.conf should at least mention this it's inteded; otherwise, the code should be changed (I'm not completely sure what Timo's intensions are, so I won't comment on possible solutions). Regards, Ulrich PS: All line numbers are taken from rev 080dd4d2fd94, which was the most recent at the time of writing.

4 3

[Dovecot] Replication protocol design
by Timo Sirainen 03 May '08

03 May '08

I'll probably be implementing multi-master replication this summer. My previous thoughts about it are here: http://dovecot.org/list/dovecot/2007-December/027284.html Below is a description of how the replication protocol will probably work. It should work just as well for master-slave and multi-master setups. Comments welcome. I'll write later a separate mail about how it'll be implemented to Dovecot. Goals ----- 1. If a single (or configurable number of) server dies, no mails must be lost that have been reported to IMAP/SMTP clients as being successfully stored. 2. Must be able to automatically recover from a server desynchronization, such as: - server has been offline for a long time - some mail files have been manually added/deleted - corrupted data/mail files if they're noticed 3. In multi-master setup if the link between servers die, the servers must be able to proceed autonomously (kind of conflicts with goal 1 though). When the link comes back, the changes are replicated as soon as possible. 4. Normal IMAP commands must not be able to cause desynchronization between servers. For example making conflicting flag changes simultaneously in two servers must not result in the servers having different flags. 5. Must perform well with at least 3 servers in a multi-master setup, preferrably still with tens of servers. 6. Latency shouldn't be increased noticeably when using servers distributed into 3 or more data centers. Must be usable over high-latency links (in optimistic async mode). 7. In normal operation send minimal incremental changes. Protocol -------- There are two major parts in the protocol: Handling the normal incremental changes and fixing desynchronization. Originally I thought that maybe the changes could be sent using the same format as Dovecot's transaction logs, but now I'm beginning to think that it's probably not that good idea. The code reuse potential is quite minimal and the format would still have to be extended in several ways so that it won't be directly compatible anyway. So I'm thinking the protocol could be something text-based. The main benefit is that text-based protocols are easier to debug. Stream compression should drop most of the extra overhead if bandwidth is a problem. The exact on-wire protocol anyway doesn't matter in the design that's discussed below. The commands have tags similar to IMAP commands, because some commands may have to be forwarded to other servers and it may take a while to get a reply. During the wait the server may process other commands. Mailbox master -------------- Each mailbox has a single master server selected. In multi-master setups the master server may be moved by having the destination server simply request it from the current master. The current master must then give it up. If link is lost to the current master, one of the remaining servers will become the new master within the remaining servers. Each server must be connected to the current master server. Since each mailbox can have a different master server, this typically means all servers are connected to each others. However it's possible to create setups where server connects to only one other server, which in turn connect to more servers. This is useful if there are bandwidth bottlenecks between some servers. This kind of a situation can also happen if in a network A-B-C the link A-C dies, but A-B and B-C continues to work. Because of this all commands must be able to function in a way that the server proxies them to the current master, instead of failing the command and trying to make it the caller's problem to resend the command to the actual master. When the cluster starts up, a single server is selected as the root master for all mailboxes. If a server doesn't know who the current mailbox master is, it asks from the root. All servers cache the currently known mailbox masters to avoid constant requests to the root. If the root server dies, another server is selected as the root. Because the new root doesn't know what masters have been requested (and asking all of them from all servers would just waste bandwidth), all the servers are expected to flush their master caches and drop their own master status. The new root doesn't respond to any requests before all servers have notified that they've dropped being a master. The master status doesn't have to be at mailbox level granularity. It could just as well be configured to move at user, domain or even global level. Perhaps this could be done dynamically, so that higher granularity is used when the master is beginning to change too often between servers. Mailbox ID ---------- Mailbox IDs are session-specific numbers dynamically assigned for user+mailbox+UIDVALIDITY combinations. All connections have different mailbox IDs. Also send and receive directions have different IDs. This allows the sender to easily replace existing IDs to point to new mailboxes without causing any confusion. MBOX: - Mailbox ID - User name - Mailbox name - Mailbox UIDVALIDITY - Mailbox UIDNEXT - Mailbox message count If the receiver finds out it has a different UIDVALIDITY, the mailbox requires a full resync. Message count and UIDNEXT may also be used to determine if replication servers are out of sync. Requesting master status ------------------------ MASTER-MOVE: - Mailbox ID - [Destination SID] (if forwarding) The command is sent to the last known master for the mailbox. The server will keep forwarding the command until it reaches the current master. During the forwarding other servers may want to request something from the master. These requests must be delayed by the forwarding servers until the move is finished. Saving messages --------------- SAVE: - Mailbox IDs - Received date - [IMAP UID] (only if we're the master) - Global UID (stays the same when copying the message) - Message text Reply: - [IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) If current server is not the master, the SAVE is sent to the master which gives the message its UID. The master server then replicates the message to other servers with the UID parameter set. The mailbox master may have already changed by the time server receives a save request. If server receives a SAVE without IMAP UID parameter, it's responsible for finding out the new mailbox master and sending a new SAVE request to it. Once the new master replies with the IMAP UID, the server can reply to the original SAVE request, also providing the new master SID so the future requests can be sent there directly. To be sure the message doesn't get lost, the server should not reply OK to the IMAP/SMTP client until it has received a reply from SAVE. Copying messages ---------------- COPY: - Source mailbox ID - Destination mailbox ID - Source IMAP UID - Global UID - [Destination IMAP UID] (only if we're the master) - Destination received date Reply: - [Destination IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) Source mailbox ID + source IMAP UID identifies the message to be copied. It's expected to contain the given global UID (which is just an extra sanity check). Otherwise it works the same way as SAVE. Since the message already exists, it's probably not necessary to wait for a reply before replying OK to originating IMAP client. Expunging messages ------------------ EXPUNGE: - Mailbox ID - UID range (No reply) Expunges also have to be sent via master server (the same way as SAVE) to avoid COPY command failing in some servers because it was just expunged. Changing message flags ---------------------- STORE: - Mailbox ID - UID range - Added flags/keywords - Removed flags/keywords - [Current modseq] (master sends) - [Highest modseq of the messages before this change] (non-master sends) - [flag: this is a CONDSTORE STORE UNCHANGEDSINCE] (non-master may send) [Reply: - UIDs where STORE was rejected to (if CONDSTORE flag was used) ] Stores also have to be sent via master server to avoid flag desynchronization. Master first checks if it has higher modseqs in the messages. Then it applies all the changes and forwards the changes to other servers. For messages that had higher initial modseqs their flags are sent to the server sending the STORE to fix a potential desync. If CONDSTORE flag is set, the change is rejected for messages that had a higher modseq. Non-masters shouldn't reply to a STORE UNCHANGEDSINCE command before the change has been replicated to master and the rejections have been processed. Mailbox synchronization ----------------------- If a mailbox is determined to have changed externally (e.g. network connection down for too long, causing replication logs to get full) the mailbox state needs to be synchronized between servers. SYNC: - UIDVALIDITY - UIDNEXT - Message count - For each message: - UID - Global UID - Modseq - Flags and keywords - Received date Reply: - (Sync finished) Receiving server compares the parameters with its own mailbox state. If it finds previously unseen global UIDs, their message texts are requested: FETCH: - Mailbox ID - UID Reply: - Message text SAVE, EXPUNGE and STORE commands are used to synchronize the mailbox. A special case is when two servers have been saving messages independently from each others. In this case it's possible that the servers have used the same UIDs for different messages (different global UIDs). These need to be resolved by giving both conflicting UIDs new unused UIDs, otherwise IMAP clients may show them as wrong messages from their caches. FIXME: If the other server had expunged a conflicting UID it still should be given a new UID. How do we find out this has happened?

4 13

[Dovecot] 1.1rc4 file-offset-size unsupported?
by David Jonas 03 May '08

03 May '08

Is --with-file-offset-size no longer supported in 1.1? # ./configure \ --prefix=/usr/local/dovecot-1.1 \ --with-mysql \ --with-file-offset-size=32 \ --with-ioloop=best \ --with-pop3d \ --with-ssl \ --with-deliver \ ... checking for _FILE_OFFSET_BITS value needed for large files... 64 ... Install prefix ...................... : /usr/local/dovecot-1.1 File offsets ........................ : 64bit I/O loop method ..................... : epoll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword sql nss Building with password lookup modules : passwd passwd-file shadow pam checkpassword sql Building with SQL drivers ............: mysql # cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 6) # uname -r 2.6.9-42.0.10.ELsmp

2 2

[Dovecot] (no subject)
by Chris Beech 02 May '08

02 May '08

I'm trying to set up a pop3 server for a project for class, but it keeps giving me the following error: Error: Login user doesn't exist: dovecot Fatal: Invalid configuration in /usr/local/etc/dovecot.conf And I have no clue what's wrong. I've look and modifying the dovecot.conffile for days and I am not having any luck. ## Dovecot configuration file # If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration # "dovecot -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting this file when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown for each setting, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples with # the real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". protocols = imap imaps pop3 pop3s # A space separated list of IP or host addresses where to listen in for # connections. "*" listens in all IPv4 interfaces. "[::]" listens in all IPv6 # interfaces, but may also listen in all IPv4 interfaces depending on the # operating system. Use "*, [::]" for listening both IPv4 and IPv6. # # If you want to specify ports for each service, you will need to configure # these settings inside the protocol imap/pop3 { ... } section, so you can # specify different ports for IMAP/POP3. For example: # protocol imap { # listen = *:10143 # ssl_listen = *:10943 # .. # } # protocol pop3 { # listen = *:10100 # .. # } listen = *:143 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP # matches the local IP (ie. you're connecting from the same computer), the # connection is considered secure and plaintext authentication is allowed. disable_plaintext_auth = no # Should all IMAP and POP3 processes be killed when Dovecot master process # shuts down. Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is eg. because of a security fix). This however # means that after master process has died, the client processes can't write # to log files anymore. #shutdown_clients = yes ## ## Logging ## # Log file to use for error messages, instead of sending them to syslog. # /dev/stderr can be used to log into stderr. log_path = /var/log/dovecot.log # Log file to use for informational and debug messages. # Default is the same as log_path. info_log_path = /var/log/dovecot-info.log # Prefix for each line written to log file. % codes are in strftime(3) # format. log_timestamp = "%b %d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## SSL settings ## # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # If key file is password protected, give the password here. Alternatively # give it when starting dovecot with -p parameter. #ssl_key_password = # File containing trusted SSL certificate authorities. Set this only if you # intend to use ssl_verify_client_cert=yes. The CAfile should contain the # CA-certificate(s) followed by the matching CRL(s). #ssl_ca_file = # Request client to send a certificate. If you also want to require it, set # ssl_require_client_cert=yes in auth section. #ssl_verify_client_cert = no # Which field from certificate to use for username. commonName and # x500UniqueIdentifier are the usual choices. You'll also need to set # ssl_username_from_cert=yes. #ssl_cert_username_field = commonName # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW:!SSLv2 # Show protocol level SSL errors. #verbose_ssl = no ## ## Login processes ## # <doc/wiki/LoginProcess.txt> # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = usr/local/var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. <doc/wiki/Rootless.txt> login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. <doc/wiki/UserIds.txt> login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 64 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to keep for listening new connections. #login_processes_count = 3 # Maximum number of login processes to create. The listening process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until the limit set by # this setting is reached. #login_max_processes_count = 128 # Maximum number of connections allowed per each login process. This setting # is used only if login_process_per_connection=no. Once the limit is reached, # the process notifies master so that it can create a new login process. #login_max_connections = 256 # Greeting message for clients. #login_greeting = Shall we play a game??? # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. login_log_format = %$: %s ## ## Mailbox locations and namespaces ## # Location for users' mailboxes. This is the same as the old default_mail_env # setting. The default is empty, which means that Dovecot tries to find the # mailboxes automatically. This won't work if the user doesn't have any mail # yet, so you should explicitly tell Dovecot the full location. # # If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u) # isn't enough. You'll also need to tell Dovecot where the other mailboxes are # kept. This is called the "root mail directory", and it must be the first # path given in the mail_location setting. # # There are a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/wiki/Variables.txt for full list. Some examples: # # mail_location = maildir:~/Maildir # mail_location = mbox:~/mail:INBOX=/var/mail/%u # mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n # # <doc/wiki/MailLocation.txt> # mail_location = mbox:/var/empty:INBOX=/var/mail/%u:INDEX=MEMORY # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections. # NOTE: Namespaces currently work ONLY with IMAP! POP3 and LDA currently ignore # namespaces completely, they use only the mail_location setting. # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. mail_location does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. # The default however depends on the underlying mail storage format. #separator = # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # mail_location, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension. You'll most likely also want to set list=no. This is mostly # useful when converting from another server with different namespaces which # you want to deprecate but still keep working. For example you can create # hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes # Show the mailboxes under this namespace with LIST command. This makes the # namespace visible for clients that don't support NAMESPACE extension. #list = yes # Namespace handles its own subscriptions. If set to "no", the parent # namespace handles them (empty prefix should always have this as "yes") #subscriptions = yes #} # System user and group used to access mails. If you use multiple, userdb # can override these by returning uid or gid fields. You can use either numbers # or names. <doc/wiki/UserIds> #mail_uid = #mail_gid = # Group to enable temporarily for privileged operations. Currently this is # used only for creating mbox dotlock files when creation fails for INBOX. # Typically this is set to "mail" to give access to /var/mail. mail_privileged_group = mail # Grant access to these supplementary groups for mail processes. Typically # these are used to set up access to shared mailboxes. Note that it may be # dangerous to set these if users can create symlinks (e.g. if "mail" group is # set here, ln -s /var/mail ~/mail/var could allow a user to delete others' # mailboxes, or ln -s /secret/shared/box ~/mail/mybox would allow reading it). #mail_access_groups = # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no ## ## Mail processes ## # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Log prefix for mail processes. See doc/wiki/Variables.txt for list of # possible variables you can use. mail_log_prefix = "%Us(%u): " # Max. number of lines a mail process is allowed to log per second before it's # throttled. 0 means unlimited. Typically there's no need to change this # unless you're using mail_log plugin, which may log a lot. This setting is # ignored while mail_debug=yes to avoid pointless throttling. #mail_log_max_lines_per_sec = 10 # Don't use mmap() at all. This is required if you store indexes to shared # filesystems (NFS or clustered filesystem). #mmap_disable = no # Rely on O_EXCL to work when creating dotlock files. NFS supports O_EXCL # since version 3, so this should be safe to use nowadays by default. #dotlock_use_excl = yes # Don't use fsync() or fdatasync() calls. This makes the performance better # at the cost of potential data loss if the server (or the file server) # goes down. #fsync_disable = no # Mail storage exists in NFS. Set this to yes to make Dovecot flush NFS caches # whenever needed. If you're using only a single mail server this isn't needed. #mail_nfs_storage = no # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and fsync_disable=no. #mail_nfs_index = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. NFS users: flock doesn't work, remember to change mmap_disable. #lock_method = fcntl # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. first_valid_uid = 1000 last_valid_uid = 5000 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. max_mail_processes = 2048 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot, mail_chroot or auth chroot # settings. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. <doc/wiki/Chrooting.txt> #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. <doc/wiki/Chrooting.txt> #mail_chroot = ## ## Mailbox handling optimizations ## # The minimum number of mails in a mailbox before updates are done to cache # file. This allows optimizing Dovecot's behavior to do less disk writes at # the cost of more disk reads. #mail_cache_min_mail_count = 0 # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time in seconds to wait between those checks. Dovecot can also use dnotify, # inotify and kqueue to find out immediately when changes occur. #mailbox_idle_check_interval = 30 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #mail_save_crlf = no ## ## Maildir-specific settings ## # By default LIST command returns all entries in maildir beginning with a dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # When copying a message, do it with hard links whenever possible. This makes # the performance much better, and it's unlikely to have any side effects. #maildir_copy_with_hardlinks = yes # When copying a message, try to preserve the base filename. Only if the # destination mailbox already contains the same name (ie. the mail is being # copied there twice), a new name is given. The destination filename check is # done only by looking at dovecot-uidlist file, so if something outside # Dovecot does similar filename preserving copies, you may run into problems. # NOTE: This setting requires maildir_copy_with_hardlinks = yes to work. #maildir_copy_preserve_filename = no ## ## mbox-specific settings ## # Which locking methods to use for locking mbox. There are four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # dotlock_try: Same as dotlock, but if it fails because of permissions or # because there isn't enough disk space, just skip it. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 120 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. mbox_very_dirty_syncs = yes # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. mbox_lazy_writes = yes # If mbox size is smaller than this (in kilobytes), don't write index files. # If an index file already exists it's still read, just not updated. #mbox_min_index_size = n ## ## dbox-specific settings ## # Maximum dbox file size in kilobytes until it's rotated. #dbox_rotate_size = 2048 # Minimum dbox file size in kilobytes before it's rotated # (overrides dbox_rotate_days) #dbox_rotate_min_size = 16 # Maximum dbox file age in days until it's rotated. Day always begins from # midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled. #dbox_rotate_days = 0 ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location. Changing this allows you to execute other # binaries before the imap process is executed. # # This would write rawlogs into ~/dovecot.rawlog/ directory: # mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # # This would attach gdb into the imap process and write backtraces into # /tmp/gdbhelper.* files: # mail_executable = /usr/libexec/dovecot/gdbhelper /usr/libexec/dovecot/imap # #mail_executable = /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # IMAP logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client #imap_logout_format = bytes=%i/%o # Override the IMAP CAPABILITY response. #imap_capability = # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example OSX # Mail (<v2.1). Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. # The list is space-separated. #imap_client_workarounds = } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. login_executable = /usr/local/libexec/dovecot/pop3-login # POP3 executable location. See IMAP's mail_executable above for examples # how this could be changed. mail_executable = /usr/local/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. pop3_enable_last = no # If mail has X-UIDL header, use it as the mail's UIDL. #pop3_reuse_xuidl = no # Keep the mailbox locked for the entire POP3 session. #pop3_lock_session = no # POP3 UIDL (unique mail identifier) format to use. You can use following # variables, along with the variable modifiers described in # doc/wiki/Variables.txt (e.g. %Uf for the filename in uppercase) # # %v - Mailbox's IMAP UIDVALIDITY # %u - Mail's IMAP UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier : %f or %v-%u (both might be used simultaneosly) # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Dovecot v0.99.x : %v.%u # tpop3d : %Mf # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # pop3_uidl_format = %08Xu%08Xv # POP3 logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client # %t - number of TOP commands # %p - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %b - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s # Maximum number of POP3 connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 3 # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # The list is space-separated. #pop3_client_workarounds = } ## ## LDA specific settings ## protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)example.com # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. #hostname = # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/lda # If user is over quota, return with temporary failure instead of # bouncing the mail. #quota_full_tempfail = no # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. "saved to INBOX") # %m - Message-ID # %s - Subject # %f - From address #deliver_log_format = msgid=%m: %$ # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # Human readable error message for rejection mails. Use can use variables: # %n = CRLF, %r = reason, %s = subject, %t = recipient #rejection_reason = Your message to <%t> was automatically rejected:%n%r # UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot/auth-master } ## ## Authentication processes ## # Executable location auth_executable = /usr/local/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. We also try to handle password changes automatically: If # user's previous authentication was successful, but this one wasn't, the # cache isn't used. For now this works only with plaintext authentication. auth_cache_ttl = 3600 # TTL for negative hits (user not found). 0 disables caching them completely. #auth_cache_negative_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username formatting before it's looked up from databases. You can use # the standard variables here, eg. %Lu would lowercase the username, %n would # drop away the domain if it was given, or "%n-AT-%d" would change the '@' into # "-AT-". This translation is done after auth_username_translation changes. #auth_username_format = # If you want to allow master users to log in by specifying the master # username within the normal username string (ie. not using SASL mechanism's # support for it), you can specify the separator character here. The format # is then <username><separator><master username>. UW-IMAP uses "*" as the # separator, so that could be a good choice. #auth_master_user_separator = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Requires auth_debug=yes to be set. #auth_debug_passwords = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Number of auth requests to handle before destroying the process. This may # be useful if PAM plugins leak memory. #auth_worker_max_request_count = 0 # Host name to use in GSSAPI principal names. The default is to use the # name returned by gethostname(). #auth_gssapi_hostname = # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = # Do NTLM authentication using Samba's winbind daemon and ntlm_auth helper. # <doc/wiki/Authentication/Mechanisms/Winbind.txt> #auth_ntlm_use_winbind = no # Path for Samba's ntlm_auth helper binary. #auth_winbind_helper_path = /usr/bin/ntlm_auth # Number of seconds to delay before replying to failed authentications. #auth_failure_delay = 2 auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi otp skey # gss-spnego # NOTE: See also disable_plaintext_auth setting. mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # <doc/wiki/PasswordDatabase.txt> # # By adding master=yes setting inside a passdb you make the passdb a list # of "master users", who can log in as anyone else. Unless you're using PAM, # you probably still want the destination user to be looked up from passdb # that it really exists. This can be done by adding pass=yes setting to the # master passdb. <doc/wiki/Authentication.MasterUsers.txt> # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM # authentication to actually work. <doc/wiki/PasswordDatabase.PAM.txt> passdb pam { # [session=yes] [setcred=yes] [failure_show_msg=yes] # [cache_key=<key>] [<service name>] # # session=yes makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work, such as pam_mkhomedir. # # setcred=yes makes Dovecot establish PAM credentials if some PAM plugins # need that. They aren't ever deleted though, so this isn't enabled by # default. # # cache_key can be used to enable authentication caching for PAM # (auth_cache_size also needs to be set). It isn't enabled by default # because PAM modules can do all kinds of checks besides checking password, # such as checking IP address. Dovecot can't know about these checks # without some help. cache_key is simply a list of variables (see # doc/wiki/Variables.txt) which must match for the cached data to be used. # Here are some examples: # %u - Username must match. Probably sufficient for most uses. # %u%r - Username and remote IP address must match. # %u%s - Username and service (ie. IMAP, POP3) must match. # # The service name can contain variables, for example %Ls expands to # pop3 or imap. # # Some examples: # args = session=yes %Ls # args = cache_key=%u dovecot #args = dovecot } # System users (NSS, /etc/passwd, or similiar) # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. <doc/wiki/AuthDatabase.Passwd.txt> passdb passwd { # [blocking=yes] - See userdb passwd for explanation #args = } # Shadow passwords for system users (NSS, /etc/shadow or similiar). # Deprecated by PAM nowadays. # <doc/wiki/PasswordDatabase.Shadow.txt> passdb shadow { # [blocking=yes] - See userdb passwd for explanation #args = } # PAM-like authentication for OpenBSD. # <doc/wiki/PasswordDatabase.BSDAuth.txt> #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location # <doc/wiki/AuthDatabase.PasswdFile.txt> passdb passwd-file { # [scheme=<default password scheme>] [username_format=<format>] # <Path for passwd-file> driver = passwd-file args = /usr/local/etc/dovecot.passdb } # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. # <doc/wiki/PasswordDatabase.CheckPassword.txt> #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database <doc/wiki/AuthDatabase.SQL.txt> #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf #args = #} # LDAP database <doc/wiki/AuthDatabase.LDAP.txt> #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap-example.conf #args = #} # vpopmail authentication <doc/wiki/AuthDatabase.VPopMail.txt> #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. # [quota_template=<template>] - %q expands to Maildir++ quota # (eg. quota_template=quota_rule=*:backend=%q) #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # <doc/wiki/UserDatabase.txt> # # System users (NSS, /etc/passwd, or similiar). In many systems nowadays this # uses Name Service Switch, which is configured in /etc/nsswitch.conf. # <doc/wiki/AuthDatabase.Passwd.txt> userdb passwd { # [blocking=yes] - By default the lookups are done in the main dovecot-auth # process. This setting causes the lookups to be done in auth worker # proceses. Useful with remote NSS lookups that may block. # NOTE: Be sure to use this setting with nss_ldap or users might get # logged in as each others! #user = root #args = } # passwd-like file with specified location # <doc/wiki/AuthDatabase.PasswdFile.txt> userdb passwd-file { # [username_format=<format>] <Path for passwd-file> driver = passwd-file args = /usr/local/etc/dovecot.passdb } # static settings generated from template <doc/wiki/UserDatabase.Static.txt> #userdb static { # Template for the fields. Can return anything a userdb could normally # return. For example: # # args = uid=500 gid=500 home=/var/mail/%u # # If you use deliver, it needs to look up users only from the userdb. This # of course doesn't work with static because there is no list of users. # Normally static userdb handles this by doing a passdb lookup. This works # with most passdbs, with PAM being the most notable exception. If you do # the user verification another way, you can add allow_all_users=yes to # the args in which case the passdb lookup is skipped. # #args = #} # SQL database <doc/wiki/AuthDatabase.SQL.txt> #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf #args = #} # LDAP database <doc/wiki/AuthDatabase.LDAP.txt> #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap-example.conf #args = #} # vpopmail <doc/wiki/AuthDatabase.VPopMail.txt> #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # <doc/wiki/UserDatabase.Prefetch.txt> #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using # X509_NAME_get_text_by_NID() which returns the subject's DN's # CommonName. #ssl_username_from_cert = no # It's possible to export the authentication interface to other programs: socket listen { master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/run/dovecot/auth-master mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = dovecot group = mail } #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/run/dovecot/auth-client #mode = 0660 #} } } # If you wish to use another authentication server than dovecot-auth, you can # use connect sockets. They are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than the path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in the login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #} ## ## Dictionary server settings ## # Dictionary can be used by some plugins to store key=value lists. # Currently this is only used by dict quota backend. The dictionary can be # used either directly or though a dictionary server. The following dict block # maps dictionary names to URIs when the server is used. These can then be # referenced using URIs in format "proxy:<name>". dict { #quota = mysql:/etc/dovecot-dict-quota.conf } ## ## Plugin settings ## plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin. Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory. # Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota # # Quota limits are set using "quota_rule" parameters, either in here or in # userdb. It's also possible to give mailbox-specific limits, for example: # quota_rule = *:storage=1048576 # quota_rule2 = Trash:storage=102400 # User has now 1GB quota, but when saving to Trash mailbox the user gets # additional 100MB. # # Multiple quota roots are also possible, for example: # quota = dict:user::proxy::quota # quota2 = dict:domain:%d:proxy::quota_domain # quota_rule = *:storage=102400 # quota2_rule = *:storage=1048576 # Gives each user their own 100MB quota and one shared 1GB quota within # the domain. # # You can execute a given command when user exceeds a specified quota limit. # Each quota root has separate limits. Only the command for the first # exceeded limit is excecuted, so put the highest limit first. # Note that % needs to be escaped as %%, otherwise "% " expands to empty. # quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 # quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 #quota = maildir # ACL plugin. vfile backend reads ACLs from "dovecot-acl" file from maildir # directory. You can also optionally give a global ACL directory path where # ACLs are applied to all users' mailboxes. The global ACL directory contains # one file for each mailbox, eg. INBOX or sub.mailbox. cache_secs parameter # specifies how many seconds to wait between stat()ing dovecot-acl file # to see if it changed. #acl = vfile:/etc/dovecot-acls:cache_secs=300 # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (mail_location) when the user logs in. # The existing mail directory is renamed to <dir>-converted. #convert_mail = mbox:%h/mail # Skip mailboxes which we can't open successfully instead of aborting. #convert_skip_broken_mailboxes = no # Skip directories beginning with '.' #convert_skip_dotdirs = no # If source storage has mailbox names with destination storage's hierarchy # separators, replace them with this character. #convert_alt_hierarchy_char = _ # Trash plugin. When saving a message would make user go over quota, this # plugin automatically deletes the oldest mails from configured mailboxes # until the message can be saved within quota limits. The configuration file # is a text file where each line is in format: <priority> <mailbox name> # Mails are first deleted in lowest -> highest priority number order #trash = /etc/dovecot-trash.conf # Expire plugin. Mails are expunged from mailboxes after being there the # configurable time. The first expiration date for each mailbox is stored in # a dictionary so it can be quickly determined which mailboxes contain # expired mails. The actual expunging is done in a nightly cronjob, which # you must set up: # dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool #expire = Trash 7 Spam 30 #expire_dict = db:/var/lib/dovecot/expire.db # Lazy expunge plugin. Currently works only with maildirs. When a user # expunges mails, the mails are moved to a mailbox in another namespace # (1st). When a mailbox is deleted, the mailbox is moved to another namespace # (2nd) as well. Also if the deleted mailbox had any expunged messages, # they're moved to a 3rd namespace. The mails won't be counted in quota, # and they're not deleted automatically (use a cronjob or something). #lazy_expunge = .EXPUNGED/ .DELETED/ .DELETED/.EXPUNGED/ # Events to log. Default is all. #mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename # Group events within a transaction to one line. #mail_log_group_events = # Available fields: uid, box, msgid, size, vsize # size and vsize are available only for expunge and copy events. #mail_log_fields = uid box msgid size } And here's what's in the dovecot.passdb file Yoda:{PLAIN}littlegreenjedi:1001:1001:User 1 Name:/var/mail/folders/Yoda DVader:{PLAIN}DarkMaster:1002:1002: User 2 Name: /var/mail/folders/DVader HSolo:{PLAIN}Gokissawookiee:1003:1003: User 3 Name: /var/mail/folders/HSolo LSkywalker{PLAIN}Jediknight:1004:1004: User 4 Name: /var/mail/folders/LSkywalker Thanks for any help. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 2

Re: [Dovecot] FAQ: setting thunderbird to talk to dovecot
by Mauricio Tavares 02 May '08

02 May '08

On Fri, May 2, 2008 at 7:54 AM, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > Is thunderbird set to use pop3 or imap? It can do both. I'd rather use imap but I am that kind of guy. ;) > Anyway, I don't support thunderbird as I have never used it, but I can tell > you how to connect to imap via telnet: > > telnet mail.thespider.com 143 > 1 login boris(a)mail.thespider.com creepycrawly > 1 logout > > You can see this: > http://www.macgeekery.com/tips/troubleshooting/troubleshooting_imap > This is what happened: [raub@yakko ~]$ telnet mail.thespider.com 143 Trying 192.168.1.12... Connected to mail.thespider.com (192.168.1.12). Escape character is '^]'. * OK dovecot ready. 1 login boris(a)mail.thespider.com creepycrawly 1 NO Authentication failed. 1 login boris(a)thespider.com creepycrawly 1 OK Logged in. 1 logout * BYE Logging out 1 OK Logout completed. Connection closed by foreign host. [raub@yakko ~]$ I wonder if it has to do with the fact the virtual mailbox domain I created in postfix is defined as thespider.com while the machine running postfix/dovecot is mail.thespider.com. > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254733744121/+254722743223 > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > "Oh My God! They killed init! You Bastards!" > --from a /. post

1 0

[Dovecot] [RFC] FreeBSD port for dovecot 1.1 series
by Xin LI 02 May '08

02 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have put together a preliminary patchset for dovecot 1.1 at: http://people.freebsd.org/~delphij/misc/dovecot-1.1-rc4.diff My intention is to repocopy the current dovecot port to dovecot11 and make changes on the latter. In this version of patchset, I have intentionally removed the following chunk of change which by default allows gid=0 users to log in. %%% @@ -333,6 +338,7 @@ ~ # belongs to supplementary groups with non-valid GIDs, those groups are ~ # not set. ~ #first_valid_gid = 1 +first_valid_gid = 0 ~ #last_valid_gid = 0 ~ # Maximum number of running mail processes. When this limit is reached, %%% Please let me know if you want more features, have comments, etc., for the FreeBSD port. I am subscribed to this list but I would appreciate if you could use 'Reply all' which will give me more opportunity to get your e-mail from the thousands I receive :) Cheers, - -- Xin LI <delphij(a)delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgY420ACgkQi+vbBBjt66CKNACfdGlItaGCo88W4ZdlLjkZ+Dlb ug8AoJkp9z9nMzwU3K/LLpzOKwD2KDXK =UzzN -----END PGP SIGNATURE-----

3 2

[Dovecot] Truncated emails in Dovecot (v1.0.13)
by Iain 02 May '08

02 May '08

Odd situation started recently whereby emails that are delivered into a maildir folder are being truncated when read. The emails are delivered via Exim and I can see the emails are complete when I look inside them. However, when viewing the emails via Thunderbird or a webmail client, they are truncated. *** START 'dovecot -n' *** # 1.0.13: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/mail.log info_log_path: /var/log/mail.log protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/server_certs/mail.example.com.crt ssl_key_file: /etc/ssl/server_certs/mail.example.com.key ssl_cipher_list: ALL:!LOW 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 login_greeting: Welcome to the example IMAP server first_valid_uid: 8 mail_access_groups: mail mail_location: maildir:/home/vmail/%d/%n/mail 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/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 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 namespace: type: private separator: . location: maildir:/home/vmail/%d/%n/mail inbox: yes auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen master: path: /var/spool/mail/dovecot/auth-master mode: 511 user: root plugin: trash: /etc/dovecot-trash.conf quota: maildir:storage=102400 *** END *** I've deleted the dovecot cache and rebuilt, but there's no change here. This is running on a Gentoo Linux server (Xen) with kernel 2.6.20. Any ideas? Iain.

2 4

[Dovecot] new auth connection (for ever)
by Evaggelos Balaskas 02 May '08

02 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, I have a little problem, when i am trying to read an email via imap my thunderbird is trying (for ever) to read it. My dovecot tells me : dovecot: Apr 29 22:47:23 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:24 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:24 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:25 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:25 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:25 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:26 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:26 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:27 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:27 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 ... dovecot: Apr 29 22:47:27 Info: IMAP(ebalaskas): Disconnected: Disconnected dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19349 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19350 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19351 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19352 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19353 dovecot: Apr 29 22:47:27 Info: auth(default): new auth connection: pid=19354 ... It's seems that the for the specific mail the dovecot tries to reconnect for EVER. But why ? Why i cant read this specific mail ? i have more than 72.000 but in some messages i get problems like that. And there are not corrupted (the messages, it's an oreilly newsletter mail for god shake :p ). Any ideas ? i think this is relative to Authentication Cache options. dovecot 1.0.13 $ dovecot -n base_dir: /usr/local/var/run/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info.log protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run//login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: Hi buddy, have an account ? max_mail_processes: 512 verbose_proctitle: yes first_valid_uid: 1000 last_valid_uid: 5000 mail_privileged_group: mail mail_location: maildir:/var/mail/folders/%u:INDEX=/var/mail/index/%u:CONTROL=/var/mail/control/%u mbox_read_locks: dotlock fcntl imap_client_workarounds: tb-extra-mailbox-sep auth default: cache_size: 10240 cache_ttl: 18000 verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb userdb: driver: passwd-file args: /usr/local/etc/dovecot.passdb socket: type: listen master: path: /usr/local/var/run/dovecot-auth-master mode: 432 user: dovecot group: mail PS: Btw timo this is the only one problem i have from the very start with dovecot (almost 2 years) Sorry for bad English ! Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIF4GGWIK+Pe9twhoRAvW3AJ9C01bRQkbF7vGdmzc5yorzmSLxEACgo7YE kB2QtWrkf8l+qIWpOKk70C4= =PlnJ -----END PGP SIGNATURE-----

2 2

[Dovecot] Replication protocol design #2
by Timo Sirainen 01 May '08

01 May '08

Changes: - Added goal 8 and rewrote mailbox synchronization plan. - Added new SELECT command to change active mailbox and removed mailbox ID from command parameters Goals ----- 1. If a single (or configurable number of) server dies, no mails must be lost that have been reported to IMAP/SMTP clients as being successfully stored. 2. Must be able to automatically recover from a server desynchronization, such as: - server has been offline for a long time - some mail files have been manually added/deleted - corrupted data/mail files if they're noticed 3. In multi-master setup if the link between servers die, the servers must be able to proceed autonomously (kind of conflicts with goal 1 though). When the link comes back, the changes are replicated as soon as possible. 4. Normal IMAP commands must not be able to cause desynchronization between servers. For example making conflicting flag changes simultaneously in two servers must not result in the servers having different flags. 5. Must perform well with at least 3 servers in a multi-master setup, preferrably still with tens of servers. 6. Latency shouldn't be increased noticeably when using servers distributed into 3 or more data centers. Must be usable over high-latency links (in optimistic async mode). 7. In normal operation send minimal incremental changes. 8. Make non-incremental synchronization fast enough to allow replication with users' untrusted Dovecot servers which may connect only rarely. Support also super high latency replication (e.g. using USB sticks). Protocol -------- There are two major parts in the protocol: Handling the normal incremental changes and fixing desynchronization. Originally I thought that maybe the changes could be sent using the same format as Dovecot's transaction logs, but now I'm beginning to think that it's probably not that good idea. The code reuse potential is quite minimal and the format would still have to be extended in several ways so that it won't be directly compatible anyway. So I'm thinking the protocol could be something text-based. The main benefit is that text-based protocols are easier to debug. Stream compression should drop most of the extra overhead if bandwidth is a problem. The exact on-wire protocol anyway doesn't matter in the design that's discussed below. The commands have tags similar to IMAP commands, because some commands may have to be forwarded to other servers and it may take a while to get a reply. During the wait the server may process other commands. Mailbox master -------------- Each mailbox has a single master server selected. In multi-master setups the master server may be moved by having the destination server simply request it from the current master. The current master must then give it up. If link is lost to the current master, one of the remaining servers will become the new master within the remaining servers. Each server must be connected to the current master server. Since each mailbox can have a different master server, this typically means all servers are connected to each others. However it's possible to create setups where server connects to only one other server, which in turn connect to more servers. This is useful if there are bandwidth bottlenecks between some servers. This kind of a situation can also happen if in a network A-B-C the link A-C dies, but A-B and B-C continues to work. Because of this all commands must be able to function in a way that the server proxies them to the current master, instead of failing the command and trying to make it the caller's problem to resend the command to the actual master. When the cluster starts up, a single server is selected as the root master for all mailboxes. If a server doesn't know who the current mailbox master is, it asks from the root. All servers cache the currently known mailbox masters to avoid constant requests to the root. If the root server dies, another server is selected as the root. Because the new root doesn't know what masters have been requested (and asking all of them from all servers would just waste bandwidth), all the servers are expected to flush their master caches and drop their own master status. The new root doesn't respond to any requests before all servers have notified that they've dropped being a master. The master status doesn't have to be at mailbox level granularity. It could just as well be configured to move at user, domain or even global level. Perhaps this could be done dynamically, so that higher granularity is used when the master is beginning to change too often between servers. Mailbox ID ---------- Mailbox IDs are session-specific numbers dynamically assigned for user+mailbox+UIDVALIDITY combinations. All connections have different mailbox IDs. Also send and receive directions have different IDs. This allows the sender to easily replace existing IDs to point to new mailboxes without causing any confusion. MBOX: - Mailbox ID - User name - Mailbox name - Mailbox UIDVALIDITY Reply: - [Mailbox UIDVALIDITY] (if changed - command failed) - Mailbox UIDNEXT - Highest modseq If the receiver finds out it has a different UIDVALIDITY, the mailbox requires a full resync. UIDNEXT and modseq can be used to determine if replication servers are out of sync. After mailbox ID has been assigned, the active mailbox can be changed using a command: SELECT: - Mailbox ID Requesting master status ------------------------ MASTER-MOVE: - [Destination SID] (if forwarding) The command is sent to the last known master for the selected mailbox. The server will keep forwarding the command until it reaches the current master. During the forwarding other servers may want to request something from the master. These requests must be delayed by the forwarding servers until the move is finished. Saving messages --------------- SAVE: - Received date - [IMAP UID] (only if we're the master) - Global UID (stays the same when copying the message) - Message text Reply: - [IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) If current server is not the master, the SAVE is sent to the master which gives the message its IMAP UID. The master server then replicates the message to other servers with the IMAP UID parameter set. The mailbox master may have already changed by the time server receives a save request. If server receives a SAVE without IMAP UID parameter, it's responsible for finding out the new mailbox master and sending a new SAVE request to it. Once the new master replies with the IMAP UID, the server can reply to the original SAVE request, also providing the new master SID so the future requests can be sent there directly. To be sure the message doesn't get lost, the server should not reply OK to the IMAP/SMTP client until it has received a reply from SAVE. Copying messages ---------------- FIXME: Source or destination mailbox ID parameter should probably be removed and the selected mailbox's ID used instead. COPY: - Source mailbox ID - Destination mailbox ID - Source IMAP UID - Global UID - [Destination IMAP UID] (only if we're the master) - Destination received date Reply: - [Destination IMAP UID] (only if not specified in parameters) - [Current mailbox master SID] (if it was moved) Source mailbox ID + source IMAP UID identifies the message to be copied. It's expected to contain the given global UID (which is just an extra sanity check). Otherwise it works the same way as SAVE. Since the message already exists, it's probably not necessary to wait for a reply before replying OK to originating IMAP client. Expunging messages ------------------ EXPUNGE: - IMAP UIDs (No reply) Expunges also have to be sent via master server (the same way as SAVE) to avoid COPY command failing in some servers because it was just expunged. Changing message flags ---------------------- STORE: - IMAP UIDs - Added flags/keywords - Removed flags/keywords - [Current modseq] (master sends) - [Highest modseq of the messages before this change] (non-master sends) - [flag: this is a CONDSTORE STORE UNCHANGEDSINCE] (non-master may send) [Reply: - IMAP UIDs where STORE was rejected to (if CONDSTORE flag was used) ] Stores also have to be sent via master server to avoid flag desynchronization. Master first checks if it has higher modseqs in the messages. Then it applies all the changes and forwards the changes to other servers. For messages that had higher initial modseqs their flags are sent to the server sending the STORE to fix a potential desync. If CONDSTORE flag is set, the change is rejected for messages that had a higher modseq. Non-masters shouldn't reply to a STORE UNCHANGEDSINCE command before the change has been replicated to master and the rejections have been processed. Mailbox synchronization ----------------------- Network connections to other servers are always initiated by the same servers. From replication point of view they could be thought of as client/server. The clients keep track of the last seen server state for all mailboxes: - UIDVALIDITY - UIDNEXT - Highest modseq Client requests mailbox ID with MBOX command. If UIDVALIDITY changed, state is reset by setting UIDNEXT=1 and highest modseq=0. MBOX command is then resent using the updated UIDVALIDITY. If server's UIDNEXT (server-UIDNEXT) is higher than last seen UIDNEXT (old-UIDNEXT), it means the server has added new messages and we want to fetch them. If the client's UIDNEXT (client-UIDNEXT) is higher than the old-UIDNEXT, it means the client has added new messages and they need to be sent to the server. All messages with UID >= old-UIDNEXT and UID < min(client-UIDNEXT, server-UIDNEXT) have an UID conflict and they must be given new unused UIDs. The synchronization is done in two batches of commands. Client first selects the mailbox and then starts the sync: SYNC-BEGIN: - server's last highest modseq - client's current highest modseq - QRESYNC-like sequence + IMAP UID lists for optimizing EXPUNGE replies Client then proceeds to send all its changes using SAVE, EXPUNGE and STORE commands. The sync is finished with SYNC-END command. Server replies with: - List of expunged IMAP UIDs (EXPUNGE command): - IMAP UIDs - Added messages (SAVE command?): - IMAP UID - Global UID - Modseq - Flags and keywords - Received date - [Message text] - Changed flags/keywords/modseqs (STORE commands): - IMAP UID - Modseq - Changed flags and keywords (or if not easily determined, their current values) - IMAP UID conflict fixes (UIDFIX command): - Source IMAP UIDs - Destination IMAP UIDs - Sync finish: - Updated UIDNEXT - Updated highest modseq Server may also reply with STORE commands that change nothing except modseqs. This is needed to get the modseqs synchronized. If in high-latency + high-bandwidth mode the message texts are always sent. The message texts are also sent if the server can determine that the client couldn't have previously seen the message (i.e. the message was saved, not copied). Otherwise they have to be requested for the messages with previously unseen global UIDs: FETCH: - IMAP UIDs Reply: - Message texts By the time client receives the reply from server, it may already have done further changes. This means it may have to fix modseqs and IMAP UIDs internally as well.

3 6

[Dovecot] virtual mbox case sensitive?
by Anil 01 May '08

01 May '08

This is on dovecot 1.1.rc4. I have this mail_location: mail_location = maildir:/apps/mail/%d/%n/Maildir When I receve mail to a virtual mailbox, its putting it in different Maildir's depending on what the sender used for the caseness of the recipient's email address: I have these Maildirs: JasonK JuliaM info jasonk juliam JasonK and jasonk should be the same maildir. So should JuliaM and juliam. Now the 2nd question is, how do I "move" the mail from JasonK back to jasonk? Thanks, this is very odd!

2 1

[Dovecot] Where to find 1.1 RPM for CentOS 4?
by Patrick 30 Apr '08

30 Apr '08

Hiya, I'm trying to find an rpm for the 1.1 version, since it appears to work better with NFS. Does anyone have a link to the i386 version? Thanks in advance. - Patrick

4 6

[Dovecot] dovecot-1.0.3: Backtrace:/usr/local/libexec/dovecot/imap
by Ralf Hildebrandt 30 Apr '08

30 Apr '08

GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". Reading symbols from /lib/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/i686/cmov/libdl-2.7.so...done. done. Loaded symbols for /lib/i686/cmov/libdl.so.2 Reading symbols from /lib/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/i686/cmov/libc-2.7.so...done. done. Loaded symbols for /lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.7.so...done. done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/local/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib11_trash_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib11_trash_plugin.so Reading symbols from /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/imap/lib20_mail_log_plugin.so Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `/usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. #0 0xb7f97424 in __kernel_vsyscall () #0 0xb7f97424 in __kernel_vsyscall () #1 0xb7e64ef5 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e66871 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080aebea in i_internal_panic_handler ( fmt=0x80bea9c "file %s: line %d (%s): assertion failed: (%s)", args=0xbfdb2944 "�}\f\bk") at failures.c:403 #4 0x080aeafc in i_panic ( format=0x80bea9c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:183 #5 0x0809d23a in mail_transaction_log_view_set (view=0x929e2a0, min_file_seq=0, min_file_offset=26588, max_file_seq=1, max_file_offset=2280, type_mask=MAIL_TRANSACTION_EXPUNGE) at mail-transaction-log-view.c:107 #6 0x08097ce2 in view_sync_set_log_view_range (view=0x928db88, type_mask=<value optimized out>) at mail-index-view-sync.c:103 #7 0x08098279 in mail_index_view_sync_begin (view=0x0, sync_mask=<value optimized out>, ctx_r=0x929e280) at mail-index-view-sync.c:132 #8 0x08086ec4 in index_mailbox_sync_init (box=0x9287740, flags=<value optimized out>, failed=false) at index-sync.c:156 #9 0x0806af41 in maildir_storage_sync_init (box=0x9287740, flags=<value optimized out>) at maildir-sync.c:1557 #10 0x08063f10 in imap_sync_init (client=0x92872f0, box=0x9287740, imap_flags=0, flags=MAILBOX_SYNC_FLAG_FAST) at imap-sync.c:46 #11 0x0806404b in cmd_sync (cmd=0x9287334, flags=MAILBOX_SYNC_FLAG_FAST, imap_flags=0, tagline=0x80be9b3 "OK Fetch completed.") at imap-sync.c:246 #12 0x0805997f in cmd_fetch_finish (ctx=0x9289fc8) at cmd-fetch.c:103 #13 0x08059cca in cmd_fetch (cmd=0x9287334) at cmd-fetch.c:173 #14 0x0805cbe0 in cmd_uid (cmd=0x9287334) at cmd-uid.c:19 #15 0x0805d16f in client_handle_input (cmd=0x9287334) at client.c:344 #16 0x0805d1fc in client_handle_input (cmd=0x9287334) at client.c:398 #17 0x0805d89f in _client_input (context=0x92872f0) at client.c:441 #18 0x080b4a37 in io_loop_handler_run (ioloop=0x92849b0) at ioloop-epoll.c:203 #19 0x080b3cac in io_loop_run (ioloop=0x92849b0) at ioloop.c:329 #20 0x080658ec in main (argc=) at main.c:290 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Windows has detected that a gnat has farted near your computer. Press any key to reboot.

1 0

[Dovecot] How dovecot deal with the request to leave posts on the server?
by Ilan Shalif 30 Apr '08

30 Apr '08

Me just request to direction to the documentation of the mechanism of dovecot. Specificly about the mechanism dovecot deal with the request to leave posts on the server, the duration, and the finishing of this mode. (I know I can mark the approptiate places in the mail client (Thunderbird) Ilan Shalif

2 1

[Dovecot] Avelsieve 1.9.7 and Dovecot/TLS
by Michael Firnau 30 Apr '08

30 Apr '08

Hi, i'm installing a new mail server for our faculty and want to use the squirrelmail plugin 'avelsieve' (1.9.7). As documented on the dovecot wiki there is a problem in the STARTTLS code and i found a solution (that works for my installation): i've traced the server output in 'get_response' and instead of a script list i saw "IMPLEMENTATION". So i took a look at the file 'managesieve.lib.php' and the STARTTLS code: /* If we allow STARTTLS, use it */ if($this->capabilities['starttls'] === true && function_exists('stream_socket_enable_crypto') === true) { fputs($this->fp,"STARTTLS\r\n"); $starttls_response = $this->line=fgets($this->fp,1024); if(stream_socket_enable_crypto($this->fp, true, STREAM_CRYPTO_METHOD_TLS_CLIENT) == false) { $this->error=EC_UNKNOWN; $this->error_raw = "Failed to establish TLS connection."; return false; } else { $this->loggedin = true; // RFC says that we need to ask for the capabilities again $this->sieve_get_capability(); $this->loggedin = false; } } With my limited time and debugging possibilities i've found that the dovecot managesieve server seems to send capability lines 'automagically'. I've added a few "debugging" lines /* If we allow STARTTLS, use it */ if($this->capabilities['starttls'] === true && function_exists('stream_socket_enable_crypto') === true) { fputs($this->fp,"STARTTLS\r\n"); $starttls_response = $this->line=fgets($this->fp,1024); if(stream_socket_enable_crypto($this->fp, true, STREAM_CRYPTO_METHOD_TLS_CLIENT) == false) { $this->error=EC_UNKNOWN; $this->error_raw = "Failed to establish TLS connection."; return false; } else { $this->loggedin = true; $starttls_response = $this->line=fgets($this->fp,1024); $errormsg .= _("MFI fgets ") . $starttls_response . '<br>'; print_errormsg($errormsg); // RFC says that we need to ask for the capabilities again $this->sieve_get_capability(); $this->loggedin = false; } } and could read MFI fgets "IMPLEMENTATION" "dovecot" what will throw the following 'sieve_get_capability' out of sync. Then i've added a second 'fgets' and received: MFI fgets "SASL" "PLAIN" Then i've added a third 'fgets' and received: MFI fgets "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex" Then i've added a fourth 'fgets' and received: MFI fgets OK "TLS negotiation successful." Now the protocol should be in sync again and after removing the lines $errormsg .= _("MFI 1 fgets ") . $starttls_response . '<br>'; print_errormsg($errormsg); i could load my scripts back. So, adding four lines reading $starttls_response = $this->line=fgets($this->fp,1024); $starttls_response = $this->line=fgets($this->fp,1024); $starttls_response = $this->line=fgets($this->fp,1024); $starttls_response = $this->line=fgets($this->fp,1024); solved the problem. I know this is not a sound "fix", but i hope to help you with this. One addendum: a "debugging" using my errormsg-printout of the output from /* If we allow STARTTLS, use it */ if($this->capabilities['starttls'] === true && function_exists('stream_socket_enable_crypto') === true) { fputs($this->fp,"STARTTLS\r\n"); $starttls_response = $this->line=fgets($this->fp,1024); resulted in the response: MFI fgets OK "Begin TLS negotiation now." what looks proper to me, but the negotiation makes the server send the four lines mentioned above. Cheers

2 1

[Dovecot] Broken Header uidvalidity problem after upgrade
by Robert Henjes 30 Apr '08

30 Apr '08

Hi, we use a current Debian etch distribution as basis for our servers, which are running within a vmware server environment. Our current configuration consists of a dovecot server with imap enabled and a ldap based authentication. Mails are stored using the Maildir format on a central nfs store. We do not use any virtual mailboxes. Since upgrading from dovecot version 1.0.rc15 (debian stable) to 1.0.13 (debian etch-backport) we got the following error logs. Excerpt from mail.err: Apr 21 12:04:38 servera deliver(usera): /var/mail/Maildir/usera/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=9) Apr 21 15:37:50 servera deliver(userb): /var/mail/Maildir/userb/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=16) Apr 23 10:37:17 servera dovecot: IMAP(userc): /var/mail/Maildir/userc/.Sent/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=2) Apr 25 17:00:17 servera dovecot: IMAP(userd): /var/mail/Maildir/userd/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=8) I did already some mailinglist reviews. They confirmed in some way the problem, but there is still no explanation where it comes from, and how it can be solved or if it may affect the proper operation of the system. Here are some links with a short comment, which are related to this problem: http://www.dovecot.org/list/dovecot/2007-September/025541.html This post also uses nfs, but pam for authentication, error message is exactly the same as in our case. http://www.dovecot.org/list/dovecot/2007-July/024001.html Version upgrade from 1.0.0 to one above, also problems with uidvalidity. They described, that it happens only once for each user after upgrading. This is similar to our observations. No user complains as well ;). So it would be only of interest if it is so. http://wiki.dovecot.org/Clients/NegativeUIDs The number for uidvalidity is zero, so it is non-negative. But maybe it is correlated with these hints. From my point of view, there could be some problems with time synchronization as well between nfs server and dovecot server machine. But we checked this and they differ never more than 2 seconds. In total we are running two servers in parallel, each has it's own userspace, all accounts are strictly separated. One server is running the rc15 version, the other (more experimental) is running the backport 1.0.13. The described problem occurs only on the 1.0.13 server, which was previously updated. All other configurations are exaclty the same. Any hints? Best regards, Robert -- Dipl.-Inform. Robert Henjes University of Wuerzburg, Institute of Computer Science, Department of Distributed Systems (Informatik III), Am Hubland, 97074 Wuerzburg, Germany henjes(a)informatik.uni-wuerzburg.de Tel: +49 931 888-6652 Fax: +49 931 888-6632

2 5

[Dovecot] fourat wants to keep up with you on Twitter
by fourat 30 Apr '08

30 Apr '08

To find out more about Twitter, visit the link below: http://twitter.com/i/8859b2431664c01a1adfe2051a644a79b4cc1689 Thanks, -The Twitter Team About Twitter Twitter is a unique approach to communication and networking based on the simple concept of status. What are you doing? What are your friends doing—right now? With Twitter, you may answer this question over SMS, IM, or the Web and the responses are shared between contacts.

1 0

[Dovecot] Quota not showing properly in webmail
by Eden 29 Apr '08

29 Apr '08

Hi I have a virtual users system using postfix / mysql / dovecot. Everything is working like a charm except for the quota display on webmail systems. It is working properly but showing GB instead of MB. For example. If I create a user with 100MB of quota and send him 50MB of mail, squirrelmail and roundcubemail display 50MB of 100GB If I create another user with 20MB quota and send him 10MB of mail, squirrelmail and roundcube dipslay 10MB of 20GB. if I send 50MB more I get the quota error msg I should get. So everything is workign but its displaying incorrectly. At first I though it was squirrelmail`s fault but it happens with roundcube as well, since both get their quota info from the imap server than I think its dovecot. I`m using Debian 4.0 This is the output of the --version and the -n dovecot commands. qgalvao-dns:/# dovecot --version 1.0.rc15 qgalvao-dns:/var/log# dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3s pop3 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/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 150 last_valid_uid: 150 mail_privileged_group: mail mail_location: maildir:/vmail/%n@%d maildir_copy_with_hardlinks: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: login plain digest-md5 cram-md5 user: nobody verbose: yes debug: 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: 432 user: vmail group: mail

4 12

[Dovecot] Connection problems using dovecot proxy
by Adrian Wojcicki | Unternehmensberatung Wojcicki 29 Apr '08

29 Apr '08

Hi Maybe somebody could help me with the following problem: I have set up a dovecot imap proxy in the dmz and a dovecot imap server in the intranet. Both in version 1.05. Now, while this setup works using Thunderbird, iPhone, etc. I have problems connecting using a Samsung Qbowl. It simply aborts with a connection error. Using the same setup but bypassing the proxy and connecting to the imap server directly does work for the phone. Logs on both servers don't show any errors. There is simply a "Info: IMAP(test): Connection closed" at the end. I enabled the rawlogs on the imap server but they don't long anything (They do log access from other imap clients but nothing from the phone). Could somebody point me into a direction where to look next? LOGS: Dovecot proxy: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_cert_file: <pathToCert> ssl_key_file: <pathToCert> disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_debug: yes auth default: cache_size: 4096 cache_ttl: 7200 debug: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: static args: static uid=5000 gid=5000 home=/dev/null dovecot: Apr 23 15:42:45 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.3.200 rip=80.187.64.167 resp=<hidden> dovecot: Apr 23 15:42:45 Info: auth(default): cache(test,80.187.64.167): hit dovecot: Apr 23 15:42:45 Info: auth(default): cache(test,80.187.64.167): NULL password access dovecot: Apr 23 15:42:45 Info: auth(default): client out: OK 1 user=test host=192.168.0.205 destuser=test nologin proxy pass=<hidden> dovecot: Apr 23 15:42:45 Info: imap-login: proxy(test): started proxying to 192.168.0.205:143: user=<test>, method=PLAIN, rip=80.187.64.167, lip=192.168.3.200 dovecot: Apr 23 15:42:45 Info: imap-login: proxy(test): disconnecting 80.187.64.167 Dovecot server: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/home/%u/.maildir mail_debug: yes mail_executable: /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap auth default: debug: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=1001 gid=100 home=/home/%u dovecot: Apr 23 15:42:45 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.0.205 rip=192.168.2.1 resp=<hidden> dovecot: Apr 23 15:42:45 Info: auth(default): passwd-file(test,192.168.2.1): lookup: user=test file=/etc/dovecot/passwd dovecot: Apr 23 15:42:45 Info: auth(default): client out: OK 1 user=test dovecot: Apr 23 15:42:45 Info: auth(default): master in: REQUEST 6 11785 1 dovecot: Apr 23 15:42:45 Info: auth(default): master out: USER 6 test uid=1001 gid=100 home=/home/test dovecot: Apr 23 15:42:45 Info: imap-login: Login: user=<test>, method=PLAIN, rip=192.168.2.1, lip=192.168.0.205 dovecot: Apr 23 15:42:45 Info: IMAP(test): Effective uid=1001, gid=100, home=/home/test dovecot: Apr 23 15:42:45 Info: IMAP(test): maildir: data=/home/test/.maildir dovecot: Apr 23 15:42:45 Info: IMAP(test): maildir: root=/home/test/.maildir, index=/home/test/.maildir, control=, inbox= dovecot: Apr 23 15:42:45 Info: IMAP(test): Connection closed

2 3

[Dovecot] reason to switch to 1.1
by Cor Bosman 29 Apr '08

29 Apr '08

We've been running 1.1 on about half of our servers for about a week now. Ive mailed before that I was pleasantly surprised by its better use of resources. Here's a graph showing that fact. Server load in the last 10 days. http://uwimages.smugmug.com/photos/286355874_9FNp2-L.png Cor

5 10

[Dovecot] Imap sent folder sometimes dosen't get updated in dovecot-1.1-rc3(+some current hg patches)
by Diego Liziero 29 Apr '08

29 Apr '08

Yes, again, some sent emails don't get copied to sent folder. This time I get the following error: Error: IMAP(username): UIDs broken with partial sync in mbox file /maildir/username/Sent This happened at least with thunderbird and with evolution. Dovecot is running on vith fcntl locking on Centos5, sendmail should use fcntl, too. Filesystem is ext3 on drbd partition. After a grep vith dovecot.log I see the same error message also with other imap folders as well (mainly Trash imap folder). Should I try to get a rawlog? Regards, Diego.

2 3

[Dovecot] icedove update
by Karl Schmidt 29 Apr '08

29 Apr '08

Something came up that Confounded problems in my move from UW-imap to dovecot. I found a problem with the new icedove update in Debian lenny when moving from 1.5.0.13+1.5.0.14b.dfsg1-0etch1 to 2.0.0.9-3 that could look like a dovecot issue. Icedove runs for a while but eventually quits updating the displayed email, yet appears to be working and busy trying to get messages from the server. I think it is related to message filters, but not sure. The fix was to move .mozilla-thundrebird somewhere and restart icedove and create a new profile. There may be a more elegant fix. ---------------------------------------------------------------- Karl Schmidt EMail Karl(a)xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 "Never let school interfere with your education." - Mark Twain ----------------------------------------------------------------

3 2

[Dovecot] sieve doesn't sift yet
by Colin Brace 28 Apr '08

28 Apr '08

Hi all, I am having difficulty getting sieve working. I created a simple set of rules which I've validated on the sieve-php page at SF. I placed this file, .dovecot.sieve, in the root of my maildir, which I understand is the default location. I also created a logfile in /var/log, but nothing has gotten written to it yet. Here is my configuration: $ sudo dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot.info ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_gid: 0 mail_access_groups: mail mail_location: maildir:/var/spool/vmail/%n mail_debug: yes pop3_uidl_format: %08Xu%08Xv auth default: verbose: yes passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/spool/vmail/%n What piece of the puzzle am I still missing? Running dovecot-sieve-1.0.2, postfix, etc under FreeBSD v7. TIA -- Colin Brace Amsterdam http://lim.nl

5 10

[Dovecot] Public Namespace + ACLs + virtual users
by Fintec 28 Apr '08

28 Apr '08

g'day! I'd just like to share my experience with public namespace and ACLs. I know this has been discussed a number of times in the past, but there were no definite answers. dovecot version i'm using: 1.0.13 Got a public namespace setup in dovecot.conf as follows: namespace public { separator = . prefix = Public_Folders. location = maildir:/home/vmail/domains/% d/Public_Folders:CONTROL=/home/vmail/domains/%d/% n/Public_Folders/support:INDEX=/home/vmail/domains/%d/% n/Public_Folders/index hidden = no } In it's own right this works just fine and it's been in use for some time now. But we need some control over who can access and delete things. So I had a go at configuring ACLs. I configured global ACLs, because as far as I can tell, per directory ACLs seem to be ignored. Once configured global ACLs work fine, except for 1 major issue; users cannot create new folders because ACLs do not get propagated (are not applied to the subfolders). If an user attempts to create a new (sub)folder, the folder is created on the filesystem however email client throws an error and the folder is inaccessible to the user as there is no ACL for it. Any pointers how to get around this? Has this been dealt with in v1.1? Regards Natko Muzina

2 1

[Dovecot] Problems with Public Folders
by Matt Rude 27 Apr '08

27 Apr '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to implement public folders on my Fedora 8 + Postfix 2.5.1 + MySQL + Dovecot 1.0.13. I have Public folder shown in for my users but when they choose the folder "Public" they receive the error "The mail server responded: Mailbox doesn't exist: Public" (in Thunderbird) or just simply "Mailbox doesn't exist: Public" (In SquirrelMail). They are also reciveing the same errors when they try to subscribe to the Public Folder. Thanks - -Matt - ------------------- # /usr/local/sbin/dovecot --version 1.0.13 - ------------------- # /usr/local/sbin/dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf listen: ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: postfix mail_location: maildir:/var/spool/virtualmailboxes/%d/%u/imap/:INBOX=/var/spool/virtualmailboxes/%d/%u/:INDEX=/var/spool/virtualmailboxes/%d/%u/imap/index/ mail_plugins: quota imap_quota namespace: type: public separator: / prefix: Public/ location: maildir:/var/spool/virtualmailboxes/%d/Public/ namespace: type: private separator: / inbox: yes auth default: mechanisms: plain digest-md5 cram-md5 cache_size: 128 cache_ttl: 600 passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: virtualmail group: virtualmail plugin: quota: maildir:storage=10240 - ------------------- # grep -v '^ *$#.*$\?$' /etc/dovecot-mysql.conf driver = mysql connect = dbname=postfix user=postfix host=localhost password=postfix default_pass_scheme = md5sum password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 1000 AS uid, 1000 AS gid, CONCAT('maildir:storage=', ROUND( mailbox.quota / 1024 ) ) AS quota FROM mailbox WHERE username = '%u' AND active = '1' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIDW+KyxB1nuZfLEYRAmigAJ44kfgX2Nh6Mi6PAukq4pxMBL3SpgCZASJG qmmZr0N1HJPeWsKnQN+qcSs= =xNyb -----END PGP SIGNATURE-----

2 3

[Dovecot] Mail deletion
by Johannes Grimm 26 Apr '08

26 Apr '08

Hi, when im deleting messages with my mail-client thunderbird, those mails dissapear in the client. but they stay on the server dovecot 1.0.13 on reiserfs. is there a special expunge timer or when will those orphaned messages whiped out of the filesystem? -- ============================================================== Hochschule für angewandte Wissenschaften - Fachhochschule Rosenheim University of Applied Sciences Rechenzentrum Johannes Grimm Hochschulstr.1 D-83024 Rosenheim Tel: +49-8031/805-229 Fax: +49-8031/805-223 http://www.fh-rosenheim.de/ johannes.grimm(a)fh-rosenheim.de ==============================================================

2 1

[Dovecot] antispam for Dovecot 1.1
by Anders 26 Apr '08

26 Apr '08

Hi Johannes. I wanted to try out the antispam plugin for a Dovecot 1.1 install, only to learn that 1.1 is actually not supported. Are there any plans to remedy this? If not, is it known how much effort is required? (i.e. could I do it myself?). Thanks, Anders.

3 4

[Dovecot] Does a script exist to fix broken maildir timestamps?
by drbob 26 Apr '08

26 Apr '08

Hello, When I upgraded to dovecot (changing servers at the same time) in November last year I copied the maildirs from my old server without using the -p option to preserve timestamps! Since my mail client displays the email dates based on the Date header rather than the imap "internaldate" I didn't notice the problem until today when I tried to migrate an account to gmail using imapsync and found that all emails prior to November display the wrong date in the web interface (they show the date they were copied in November). I feel very silly. Before I go try to hack together a script which parses all my older email files and changes the timestamps to the time recorded in the "Date:" header, does anyone know if robust, tested version of such a script is alrady available? Would correcting the timestamps in this way cause any problems for dovecot (e.g in the index files)? Thanks in advance for any help. drbob NB In my googling for a solution to this problem I found this hack to imapsync which would rewrite the "internaldate" based on the date header during a sync. Whilst I'd rather fix the timestamps that are the source of the problem, it may be useful for others finding this post in the future, see: http://www.zimbra.com/forums/installation/237-received-date-appears-incorre…

1 1

[Dovecot] permission problems
by Cor Bosman 25 Apr '08

25 Apr '08

Hi, ever since i switched a few servers to 1.1RC4 im finding control dirs with the wrong permissions: 80023615 8 drw------- 2 xxxxxxx user 4096 Apr 23 09:46 ./a/an/xxxxxxx/INBOX/.INBOX.Maatschappijen When dovecot then wants to write a file inside, it gets a permission denied. Cor

2 4

[Dovecot] Mixing LDAP and static
by Anders 25 Apr '08

25 Apr '08

I want to read quota size from LDAP, but I have a static value for home. How can I mix these? Right now, I have this LDAP configuration: user_attrs = uid=home=/var/mail/vhosts/%d/%n,gosaMailQuota=quota_rule=*:bytes=%$M which works fine, but looks up the uid attribute needlessly, and is not scalable: I have to pick a different, always-existing LDAP attribute for each static extra field that I want to set. Is there some LDAP configuration syntax like the SQL "SELECT '/var/...' AS home" ? Thanks, Anders.

2 9

[Dovecot] 1.0.5: many pop3-login processes?
by Alan Ferrency 25 Apr '08

25 Apr '08

Hello, We are running dovecot 1.0.5 on a test server, with FreeBSD 6.2 (though I have noticed the same problem since dovecot versions in the 0.99 range). We don't have very many simultaneous pop/imap users, but we have a proliferation of pop3-login processes. Currently we have 128 such processes. We have 11 imap-login processes, but only a few actual imap processes running. Is this normal? Can we stop it? Is anyone else successfully running dovecot on FreeBSD 6.2? Thanks for your help. Alan Ferrency pair Networks, Inc. alan(a)pair.com

4 14

[Dovecot] Problem with Dovecot Delivery Agent, Extra "From" lines and mbox
by Hokan 25 Apr '08

25 Apr '08

When an mbox email contains a line that looks like a "Mail" header it should be quoted (per RFC 4155). Sendmail's delivery agent does this, as does Procmail delivery agent. Dovecot deliver does not do this. Example line, with ">" quote: >From hokan(a)hokan.org Thu Mar 8 17:28:01 2008 When reading email (IMAP) that contains such an unquoted line, the email abruptly ends before the "Mail" line. There may (or may not) appear another email (visible to the client) that contains the rest of the email. -- Hokan MEnet, a wholly owned subsidiary of Enet System Administrator Department of Mechanical Engineering hokan(a)me.umn.edu Institute of Technology 612.626.9800 University of Minnesota

2 4

[Dovecot] Authentication: Dovecot -> Vpopmail - > MySQL with one table per domain
by James Nordstrom 25 Apr '08

25 Apr '08

Hi All, I am using Dovecot 1.0.13 with Vpopmail (Qmail Toaster current) backed by MySQL with one table per domain (--disable-many-domains) . What I cannot figure out is how to have Dovecot authenticate to Vpopmail when Vpopmail uses one table per domain. Basically I need dynamic SQL in the Dovecot-sql.conf file. Currently I have: password_query = select pw_clear_passwd as password from domainname_com where pw_name = '%n' I need something like password_query = select pw_clear_passwd as password from %d where pw_name = '%n' Where %d is the name of the table. I can't use the exact domain name at it will not match the vpopmail format domainname_com. I would be happy to use some sort of sting builder but and not sure what my options are in the .conf file. Please help Thanks in advance James James Nordstrom Nordstrom Design Inc. E-mail: james(a)nordstromdesign.com US: 908-419-5597 Europe: 001/908-419-5597

2 1

[Dovecot] Index maintenance
by Anders 25 Apr '08

25 Apr '08

Hi. I am unable to find information about what happens to the index file if I use something like the cron script at the bottom of http://wiki.dovecot.org/Plugins/Expire There must be some information in the index that is no longer needed. When and how will Dovecot clean this up? Thanks, Anders.

2 5

[Dovecot] sieve header :matches for multiline header
by Anton Yuzhaninov 25 Apr '08

25 Apr '08

RFC3028 say: Folding of long header lines (as described in [IMAIL] 3.4.8) is removed prior to interpretation of the data. The folding syntax (the CRLF that ends a line plus any leading whitespace at the beginning of the next line that indicates folding) are interpreted as if they were a single space. But it seems to be not true for dovecot-sieve-1.0.2 for header Received: from example.ru (example.ru [192.168.105.14]) by myserver (Postfix) with ESMTP id D4DA5D85927 This sieve test work: header :matches "Received" "from *by myserver (Postfix) with ESMTP id *" But this test not work, while should also work according to RFC: header :matches "Received" "from * by myserver (Postfix) with ESMTP id *" -- WBR, Anton Yuzhaninov

4 3

[Dovecot] ACLs generating plugin problems.
by "Fábio M. Catunda" 25 Apr '08

25 Apr '08

Hi! I'm trying to use an ACL to avoid deletion of messages that are inside .Trash folder, the ACL is already working very well, the problem that I'm facing is that even if the message is not deleted, mail_log logs that it has been deleted. Also, in some cases part of the lazy_expunge code is executed too, but sometimes I just dont know where the message is, thats weird. I erased deleted and expunged folders, then I deleted a message, It hasn't been deleted, but "deleted" and "expunged" folders has been created. Anyway, I would like to know if there is a way to stop plugin execution when an ACL matches. Thanks a lot.

2 3

[Dovecot] alert function, V2
by Stewart Dean 25 Apr '08

25 Apr '08

I guess the alert function is not part of the spec, because it appears to be unimplemented in Dovecot, even though most clients implement it. Timo, I would hope this would be easy to implement, and it's functionality that will be valuable to every installation. Here's why. America recently had the tragedy of a shooting rampage on a large university campus (yes, America should do something about the violence and free access to guns in our culture/society). What was worse was that, due to the lack of an emergency notification process, some 20+ people died needlessly. Now all college and university administration are scrambling to set up emergency notification processes. Our first take on this is a massive all-hands mailing list, but a) best case, it would take 15 minutes (and as much as an hour) to get to everybody's mailbox. b) users would have to read through their mail and stumble on the message What's needed is an "in-your-face" unavoidable alert, and the UWIMAP alert functionality provides this. As I recall, you touch just about anything in your IMAP client and there's a popup message in the middle of the client IMAP window...and it happens repeatedly. We tried it back 3-4 years ago and found it too annoying to use. For this purpose, it's perfect. The wy UWIMAP did it, the presence of the file /etc/imapd.alert triggers it, and the text in that file is transmitted to the client. The message has to be short, a one-liner for a small popup window, but this could be a pointer to a shared system message folder. Of course, DC could sense the activation of the alert in some other fashion that the presence of a file. Ideally, whatever activates the alert function should be able to be turned on remotely; I had in mind to do it using a mail aliases that is a pipe to a executable... What say you? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

6 9

[Dovecot] dovecot-1.1.rc3 assertion failure in index-sync.c
by richs＠whidbey.net 25 Apr '08

25 Apr '08

We just came across a mailbox today that, when accessed via POP3 or IMAP, crashes Dovecot. It seems to be another index-related corruption issue (as removing "dovecot.index" for INBOX fixed it); Using POP3: dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:28:14 Panic: POP3(USERNAME): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Apr 09 10:28:14 Error: POP3(USERNAME): Raw backtrace: pop3 [0x80c04e4] -> pop3 [0x80c013c] -> pop3 [0x808eb9a] -> pop3(index_mailbox_set_recent_seq+0x3e) [0x808ebde] -> pop3(maildir_sync_index+0x923) [0x8064173] -> pop3 [0x8062e22] -> pop3(maildir_storage_sync_init+0x58) [0x8062f98] -> pop3(mailbox_sync+0x1f) [0x80912af] -> pop3(client_create+0x1de) [0x805968e] -> pop3(main+0x403) [0x805b503] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x707dec] -> pop3 [0x8058e71] dovecot: Apr 09 10:28:14 Error: child 28169 (pop3) killed with signal 6 Using IMAP (after "SELECT INBOX"): dovecot: Apr 09 10:56:31 Warning: IMAP(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:56:31 Panic: IMAP(USERNAME): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Apr 09 10:56:31 Error: IMAP(USERNAME): Raw backtrace: imap [0x80cd564] -> imap [0x80cd1bc] -> imap [0x809b32a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809b36e] -> imap(maildir_sync_index+0x923) [0x8070903] -> imap [0x806f5b2] -> imap(maildir_storage_sync_init+0x58) [0x806f728] -> imap(mailbox_sync+0x1f) [0x809da3f] -> imap(cmd_select_full+0xd5) [0x805dec5] -> imap(cmd_select+0x19) [0x805e069] -> imap [0x805f799] -> imap [0x805f827] -> imap [0x805ffb5] -> imap(client_input+0x5e) [0x80601ce] -> imap(io_loop_handler_run+0x100) [0x80d4d50] -> imap(io_loop_run+0x28) [0x80d42e8] -> imap(main+0x4ac) [0x8067bdc] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x125dec] -> imap [0x8059d61] dovecot: Apr 09 10:56:31 Error: child 7057 (imap) killed with signal 6 We made a copy of the mailbox and index in case any further testing would be helpful, -Rich

2 1

[Dovecot] Rare problem with Indexes?
by richs＠whidbey.net 25 Apr '08

25 Apr '08

We've been running 1.1 rc3 now for about a month, and overall it's been very fast and stable. There is however an Index-related problem that keeps cropping up which prevents a user from accessing their mailbox until their Indexes are manually removed. Somehow, an Index becomes problematic, and Dovecot hangs forever when the mailbox is accessed. It manifests when a user logs in and issues a "SELECT INBOX", or "GETQUOTAROOT" when "maildirsize" needs rebuilding. When Dovecot hangs, no data is returned and no further commands are accepted, and the daemon must be killed. We see no errors in the logs, but have yet to catch the problem with "mail_debug" enabled. We're using NFS with Maildir's and these related options: mail_location = maildir:/mail/%Lu/Maildir:INDEX=/mail/%Lu/Cache mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_drop_priv_before_exec = yes mail_cache_min_mail_count = 128 mailbox_idle_check_interval = 5 maildir_stat_dirs = yes maildir_copy_with_hardlinks = yes maildir_copy_preserve_filename = no Has anyone else run across the need to purge Indexes manually? Could this be unrecoverable Index corruption, or a locking issue? We've made a copy of the mailbox when the problem occurs. However, when we test it later, Dovecot re-builds the "dovecot.index" file itself just fine, and functions normally. We plan to "mail_debug" when this happens next to see if we can get more information. Thanks! -Rich

2 1

[Dovecot] Dovecot features
by Phan Thanh Diện 25 Apr '08

25 Apr '08

Hi, We would like to switch from courier-imap to dovecot. I have installed dovecot on a machine running FreeBSD 6.3 and now testing it. My questions are below: 1. Can I configure dovecot to delete all files that are older, say 10 days, from defined mail boxes (for example Trash or Spam). 2. After I access mail box (using web mail squirrel imap) all emails moved from 'new' directory to 'cur'. Then messages are not accessible for pop3. Such behavor doesn't occur with courier-imap. Can I force dovecot to behave like courier-imap? Many thanks for help. Dien Phan

7 10

[Dovecot] 1.1 a major improvement
by Cor Bosman 24 Apr '08

24 Apr '08

I recently switched one of our 30 imap servers to 1.1RC4 from 1.0.x, and the difference is huge. The load on the server dropped from 5+ to 0.3 or so. This means there is no more io waiting going on. Thats on FreeBSD 6.2. Great work Timo! Cor

2 1

[Dovecot] dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor
by Mart Pirita 24 Apr '08

24 Apr '08

Hello. Since I upgraded few months ago from version 1.0 to 1.1 (right now using v1.1.rc4) in logs for some users only (but in different servers) I noticed errors: dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor dovecot: Fatal: IMAP(user3): write(event_pipe) failed: Bad file descriptor So only for some imap users. And in different servers. And this error happens suddenly, I already tried to delete delete cache and index files. However the users themselves haven't noticed any problems. Shall I just ignore these errors on what? Configuration is quite simple: dovecot -n # 1.1.rc4: /etc/dovecot.conf protocols: imaps pop3 pop3s ssl_parameters_regenerate: 0 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 login_log_format_elements: %u [%r] %m %c mail_max_userip_connections(default): 90 mail_max_userip_connections(imap): 90 mail_max_userip_connections(pop3): 9 maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/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): outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail imap_client_workarounds(imap): outlook-idle netscape-eoh tb-extra-mailbox-sep delay-newmail imap_client_workarounds(pop3): 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): bytes=%i/%o, del=%d/%m, size=%s auth default: cache_size: 1024 failure_delay: 3 passdb: driver: pam args: cache_key=%u%r%s * userdb: driver: passwd -- Mart

2 1

[Dovecot] Dbox + imap_quota still crashing on 1.1rc4
by Eric T 24 Apr '08

24 Apr '08

Emailed about this with 1.1rc3 and didn't get a reply. Tried upgrading to 1.1rc4 and got the same crashing: Centos 5 (in openvz container) 2.6.18-53.1.4.el5.028stab053.4 #1 SMP Fri Jan 18 12:29:44 MSK 2008 x86_64 x86_64 x86_64 GNU/Linux /usr/local/dovecot/sbin/dovecot -n # 1.1.rc4: /usr/local/dovecot/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap imaps pop3 pop3s listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 ssl_listen(default): *:10943 ssl_listen(imap): *:10943 ssl_listen(pop3): *:10993 ssl_cert_file: /usr/local/dovecot/etc/ssl/certs/dovecot.pem ssl_key_file: /usr/local/dovecot/etc/ssl/private/dovecot.pem ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_user: dovecot-auth first_valid_uid: 2000 last_valid_uid: 2000 first_valid_gid: 2000 last_valid_gid: 2000 mail_uid: 2000 mail_gid: 2000 mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): fts fts_squat quota imap_quota mail_plugins(imap): fts fts_squat quota imap_quota mail_plugins(pop3): expire quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 auth default: default_realm: flerd.com verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf socket: type: listen client: path: /usr/local/dovecot/var/run/dovecot/auth-client mode: 438 master: path: /usr/local/dovecot//var/run/dovecot/auth-master mode: 438 user: dovecot-auth plugin: fts: squat quota: dict:user::proxy::quotadict quota_rule: *:storage=1G quota_rule2: Trash:storage=100M expire: Trash 7 Trash/* 7 Spam 3 expire_altmove: * 30 expire_dict: proxy::expire dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-dict-quota.conf expire: db:/usr/local/dovecot/var/lib/dovecot/expire.db -------------------------- Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x00000000004640f9 in mail_index_get_header_ext (view=0x0, ext_id=2, data_r=0x7fffdbbcff90, data_size_r=0x7fffdbbcff88) at mail-index-view.c:550 550 view->v.get_header_ext(view, NULL, ext_id, data_r, data_size_r); (gdb) bt full #0 0x00000000004640f9 in mail_index_get_header_ext (view=0x0, ext_id=2, data_r=0x7fffdbbcff90, data_size_r=0x7fffdbbcff88) at mail-index-view.c:550 No locals. #1 0x000000000044631c in dbox_sync_want_flush_dirty (mbox=0xdd47598, close_flush_dirty_flags=true) at dbox-sync.c:262 hdr = <value optimized out> data = <value optimized out> data_size = <value optimized out> #2 0x00000000004463d1 in dbox_sync_begin (mbox=0x0, ctx_r=0x7fffdbbd00c8, close_flush_dirty_flags=144, force=144) at dbox-sync.c:297 storage = (struct mail_storage *) 0xdd3dc98 ctx = <value optimized out> sync_flags = <value optimized out> ret = <value optimized out> rebuild = <value optimized out> #3 0x0000000000446b98 in dbox_sync (mbox=0x0, close_flush_dirty_flags=144) at dbox-sync.c:396 sync_ctx = (struct dbox_sync_context *) 0xdd47598 #4 0x000000000043f3f4 in dbox_storage_mailbox_close (box=0x0) at dbox-storage.c:311 mbox = <value optimized out> ret = <value optimized out> #5 0x00002aaaab62df50 in fts_mailbox_close (box=0xdd47598) at fts-storage.c:65 fbox = (struct fts_mailbox *) 0xdd48fb0 ret = <value optimized out> #6 0x00002aaaab42a5ed in cmd_getquotaroot (cmd=0xdd3e758) at imap-quota-plugin.c:98 storage = <value optimized out> box = (struct mailbox *) 0x0 iter = (struct quota_root_iter *) 0x0 root = <value optimized out> orig_mailbox = 0xdd42938 "INBOX" mailbox = 0x49ab6a "INBOX" str = (string_t *) 0xdd311c0 #7 0x000000000041abfc in client_command_input (cmd=0xdd3e758) at client.c:553 client = (struct client *) 0xdd3e370 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #8 0x000000000041acb2 in client_command_input (cmd=0xdd3e758) at client.c:602 client = (struct client *) 0xdd3e370 command = (struct command *) 0x7fffdbbcff90 __PRETTY_FUNCTION__ = "client_command_input" #9 0x000000000041b46f in client_handle_input (client=0xdd3e370) at client.c:643 _data_stack_cur_id = 3 ret = <value optimized out> remove_io = <value optimized out> handled_commands = false #10 0x000000000041b693 in client_input (client=0xdd3e370) at client.c:698 cmd = <value optimized out> output = (struct ostream *) 0xdd3e608 bytes = 27 __PRETTY_FUNCTION__ = "client_input" #11 0x0000000000486de8 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:201 ctx = <value optimized out> event = (const struct epoll_event *) 0xdd39dc0 list = (struct io_list *) 0xdd3a780 io = (struct io_file *) 0xdd3e6a0 tv = {tv_sec = 1799, tv_usec = 999607} events_count = <value optimized out> t_id = 2 msecs = <value optimized out> ret = 1 i = 0 call = <value optimized out> #12 0x00000000004860cd in io_loop_run (ioloop=0xdd39b60) at ioloop.c:301 No locals. #13 0x0000000000422b01 in main (argc=<value optimized out>, argv=0x0, envp=0x7fffdbbd03c8) at main.c:293 No locals.

2 1

[Dovecot] Dovecot timeout over NFS
by Guy 24 Apr '08

24 Apr '08

Hi, I'm using postfix with Dovecot 1.0.5 and getting the following errors when a user moves a massive folders contents to trash (65000 or so messages): Apr 21 15:31:01 mink dovecot: IMAP(dev2(a)aluminati.net): Timeout while waiting for lock for transaction log file /virtual/store1/mail/d/dev2_aluminati.net/Maildir/.Deleted Items/dovecot.index.log Is there anything I can do to compensate for situations like this? Thanks Guy -- Don't just do something...sit there!

2 3

[Dovecot] Sieve script executed, but nothing happens
by Wouter Amsterdam 24 Apr '08

24 Apr '08

Hi all, I think I have almost solved my dovecot-deliver lookup problems, but now sieve still fails to work. From deliver's logfile I can tell the user's homedir is found and the sieve script is executed, but not as expected. My sieve testscript is very basic: /home/virtual/user.dovecot.sieve: ************* require "fileinto"; if address :is "to" "user@ mydomain.nl" { fileinto "sieve"; ( I also tried INBOX.sieve, without succes) } ************* But incoming messages for this account are still delivered in the normal inbox, not in the sieve folder. Why won't this work? /var/log/deliver: ************* deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: Loading modules from directory: /usr/lib/dovecot/lda deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: Module loaded: /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: auth input: user(a)mydomain.nl deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: auth input: home=/home/virtual/user deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: auth input: uid=5000 deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: auth input: gid=5000 deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: maildir: data=/data/mail/mydomain/user deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: maildir: root=/data/mail/mydomain/user, index=/data/mail/mydomain/user, control=, inbox= deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: cmusieve: Using sieve path: /home/virtual/user/.dovecot.sieve deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: cmusieve: Executing script /home/virtual/user/.dovecot.sievec deliver(user(a)mydomain.nl): Apr 17 09:55:40 Info: msgid=<20080417075530.5E8BD20111(a)termsrv.mydomain.local>: saved mail to INBOX ************* TIA, Wouter

3 3

[Dovecot] using mysql from within a plugin
by Alexander Prinsier 24 Apr '08

24 Apr '08

Hello, I'm trying to access a mysql database in a plugin. -What special compiler flags do I need? I discovered that when I don't explicitly link lib-sql/libsql.a in, then I get an undefind symbol error about sql_init when loading the plugin. Shouldn't the imap process itself have sql support linked in, rather than each plugin? -It appears that I need to call sql_drivers_init() and sql_drivers_register_all() before sql_init. Again, shouldn't the imap process do this, instead of each plugin? It should probably only be called once, so if one plugin already does it, then the second one will create problems. -When linking libsql.a in, and calling the functions mentioned above, then I get this error when starting dovecot: undefined symbol: mysql_ssl_set I'm guessing it's part of the mysql library itself, not dovecot. Can someone give me some hints on how to use dovecot's mysql library in a plugin? Thanks, Alexander

2 1

[Dovecot] Sharing Folders - or views?
by Nigel Allen 24 Apr '08

24 Apr '08

Hi All Running Dovecot v1.0.3 on FC 6. We have a Dovecot account which contains folders used by all staff. Think of the account as "Customers" and the folders as "Customer-1", "Customer-2", "Customer-3" and so on. We currently have around 650 of these customer folders. The problem is that there are currently 12 members of staff who need to see a subset of these folders (i.e. the customers that they are the manager for) but who also need to see (sometimes) the entire range of customer folders. Ideally what they would like to see is this kind of layout: +Personal Folders Inbox Trash Copies + My Customers Cust-1 Cust 7 Cust-25 Cust 33 + All Customers Cust-1 Cust-2 Cust-3 Cust-4 Cust-5 Cust-6 Cust-7 etc I suppose we could achieve this with symlinks but thought I would ask in case there is a "clever" way to achieve the same end. Thanks and Regards Nigel. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] dovecot 1.1.rc4 -> 1.0.10 : Recent counter wrong
by Laurent Papier 24 Apr '08

24 Apr '08

Hi, I have tested dovecot 1.1.rc4. I seems to works fine with my configuration. I have also tested the downgrade from 1.1rc4 to 1.0.10. It seems to work fine too expect the following messages. Apr 15 14:46:44 dev dovecot: IMAP(lolo(a)gretel.com): Fixing header counts in index /data/mail/gretel.com/l/o/lolo//dovecot.index: Recent counter wrong Apr 15 14:46:49 dev dovecot: IMAP(lolo(a)gretel.com): Fixing header counts in index /data/mail/gretel.com/l/o/lolo//.spam/dovecot.index: Recent counter wrong Apr 15 14:46:49 dev dovecot: IMAP(lolo(a)gretel.com): Fixing header counts in index /data/mail/gretel.com/l/o/lolo//.z&AOkA4AD2-l/dovecot.index: Recent counter wrong Apr 15 14:46:49 dev dovecot: IMAP(lolo(a)gretel.com): Fixing header counts in index /data/mail/gretel.com/l/o/lolo//.z&AOkA4AD2-l/dovecot.index: Recent counter wrong Is it just some info messages or should I care about those lines ? Thanks. -- Laurent Papier - 03 88 75 80 50 Admin. système - SdV Plurimedia - <http://www.sdv.fr/>

2 3

[Dovecot] Internal login failure
by David Andel 24 Apr '08

24 Apr '08

Hi all My postfix/dovecot installation seems to be working fine - on the machine. But I cannot connect from the outside by IMAP. I am desperately searching for the reason of the following error: bit:/var/log# telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. 1 LOGIN test test1 * BYE Internal login failure. Refer to server log for more information. Connection closed by foreign host. The PW sould be correct: bit:/etc/dovecot# grep ^test passwd test:{PLAIN}test1 /var/log/dovecot-info.log sais (I have removed the last block in the IP): ovecot: Apr 22 04:27:05 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=217.150.250.xxx rip=127.0.0.1 resp=AHRlc3QAdGVzdDE= dovecot: Apr 22 04:27:05 Info: auth(default): client out: OK 1 user=test dovecot: Apr 22 04:27:05 Info: auth(default): master in: REQUEST 4 4739 1 dovecot: Apr 22 04:27:05 Info: auth(default): master out: USER 4 test uid=111 gid=8 home=/srv/vmail//test dovecot: Apr 22 04:27:05 Info: imap-login: Internal login failure: user=<test>, method=PLAIN, rip=127.0.0.1, lip=217.150.250.xxx Any ideas what this could be caused by? Thank you in advance and best regards, David

2 2

[Dovecot] Windows Mobile and IMAP proxy
by Onno Molenkamp 24 Apr '08

24 Apr '08

Hi, We are running Dovecot proxies in front of our Dovecot IMAP servers, and were having problems with Windows Mobile clients not being able to connect. The clients would send a LOGIN command, and immediately after the succes reply a LOGOUT command. It turns out the Windows Mobile IMAP client gets confused by the IMAP proxy first sending the command tag in the reply and then, in a seperate packet, the rest of the line. Although not being able to handle this looks like a very bad design to me (how can one ever expect to read a full line in a single read() call?) I fixed it in our Dovecot proxies because we do have clients that want to use it. Attached is my fix for the problem. Onno

2 1

[Dovecot] disconnect error
by ML 24 Apr '08

24 Apr '08

a user complain about suddent disconnect error from time to time (he's using pop3 with Apple Mail) Looking at dovecot logs I discover that, each time the error shows up for him, I have this : dovecot: pop3[95137]: Info: user=<dan(a)userdomain.com> Disconnected top=0/0, retr=0/0, del=0/4, size=127101 but all other "regular" pop3 session looks like this one : dovecot: pop3[94777]: Info: user=<dan(a)userdomain.com> Disconnected: Logged out top=0/0, retr=0/0, del=0/3, size=67947 What is the difference beetween "Disconnected: Logged out" and "Disconnected" and how can I solve this ? Thanks for any tips... # dovecot.conf : protocols: imap pop3 imaps pop3s disable_plaintext_auth: no shutdown_clients: 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 login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 10 verbose_proctitle: yes first_valid_uid: 26 last_valid_uid: 26 first_valid_gid: 6 last_valid_gid: 6 mail_privileged_group: mail mail_location: maildir:/usr/local/mail/%d/%u 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_plugins(default): quota imap_quota antispam mail_plugins(imap): quota imap_quota antispam mail_plugins(pop3): quota 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_log_prefix: %Ls[%p]: Info: user=<%u> 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): UID%u-%v pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private prefix: INBOX. inbox: yes auth default: mechanisms: plain login digest-md5 cram-md5 user: nobody verbose: yes debug: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: prefetch socket: type: listen client: path: /var/run/dovecot/auth-client mode: 384 master: path: /var/run/dovecot/auth-master mode: 384 user: mailnull group: mail plugin: sieve: /usr/local/mail/.dovecot.sieve trash: /usr/local/etc/dovecot-trash.conf antispam_signature: X-DSPAM-Signature antispam_trash: trash;Trash;Deleted Items antispam_spam: Junk;Spam;junk;spam;SPAM;SpamTrain antispam_unsure: Draft;draft antispam_mail_tmpdir: /tmp antispam_mail_spam: spam@localhost antispam_mail_notspam: nospam@localhost antispam_mail_sendmail: /usr/sbin/sendmail

3 5

[Dovecot] Adding new storage backend to Dovecot
by Earl Dreller 24 Apr '08

24 Apr '08

I'm exploring adding a new storage backend to dovecot, storing mail in some sort of database, and had a few questions. Hoping someone here might be able to help :) -Is all of the 'storage' specific code in housed in lib-storage/index? Would adding a new storage backend be as simple as recreating all of the public functions of the current /mbox or /maildir code such as they pertain to that storage mechanism? -Where is the particular storage method controlled? I've had a look around but can't seem to find where the decision to use the 'mbox' or 'maildir' code is. -Finally, if there isn't a filesystem associated with the mail storage area, obviously the index data code will need to change somewhere. Any ideas on the complexities of that? Thanks!

3 2

Re: [Dovecot] mailtrain with dovecot antispam plugin
by Johannes Berg 24 Apr '08

24 Apr '08

Please don't take mail private. I tend to not reply at all in that case. Can you try this patch? johannes diff --git a/mailtrain.c b/mailtrain.c index dbe770c..75c0fc8 100644 --- a/mailtrain.c +++ b/mailtrain.c @@ -213,7 +213,9 @@ int backend_handle_mail(struct mailbox_transaction_context *t, struct istream *mailstream; struct ostream *outstream; int ret; - char *buf, *firstline; + char *buf; + const unsigned char *beginning; + size_t size; int fd; if (!ast->tmpdir) { @@ -266,15 +268,25 @@ int backend_handle_mail(struct mailbox_transaction_context *t, goto failed_to_copy; } - firstline = i_stream_read_next_line(mailstream); + if (i_stream_read_data(mailstream, &beginning, &size, 5) < 0 || + size < 5) { + ret = -1; + mail_storage_set_error(t->box->storage, + "Failed to read mail beginning"); + goto failed_to_copy; + } - if (strncmp(firstline, "From ", 5) != 0) - if (o_stream_send_str(outstream, firstline) < 0) { + /* "From "? skip line */ + if (memcmp("From ", beginning, 5) == 0) { + i_stream_read_next_line(mailstream); + } else { + if (o_stream_send_str(outstream, "From ") < 0) { ret = -1; mail_storage_set_error(t->box->storage, "Failed to write line to temp"); goto failed_to_copy; } + } if (o_stream_send_istream(outstream, mailstream) < 0) { ret = -1;

2 2

[Dovecot] Dovecot + iPhone
by Tim Riley 24 Apr '08

24 Apr '08

dovecot version: 1.0.13 (RPM from http://atrpms.net/) protocol: IMAP dovecot -n: # 1.0.13: /etc/dovecot.conf log_path: /var/log/dovecot/dovecot.log listen: *removed* ssl_cert_file: /etc/pki/dovecot/certs/dovecot.pem ssl_key_file: /etc/pki/dovecot/private/dovecot.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mbox_lazy_writes: no imap_client_workarounds: outlook-idle delay-newmail auth default: cache_size: 1024 passdb: driver: pam args: session=yes cache_key=%u dovecot userdb: driver: passwd I want to start out by saying that Dovecot works 100% when viewing/moving mail (on our company mail server that I maintain) via Outlook Express and/or Windows Mail. I'm having issues with moving mail via my iPhone. If I move a message from my Inbox to another folder, the mail gets COPIED...not moved. So it exists in my Inbox as well as the folder I moved it to. When I test on my iPhone to Yahoo's mail server, the moved process works 100%. Is there a Dovecot setting that needs to be tweeked or possibly another CentOS 5 OS setting? Any help is greatly appreciated! This message has been scanned for viruses and dangerous content by MailScanner & ClamAV. This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently delete this e-mail.

4 8

Re: [Dovecot] Compiling with SSL
by Jerry Yeager 22 Apr '08

22 Apr '08

On Apr 22, 2008, at 5:00 AM, dovecot-request(a)dovecot.org wrote: (stuff cut out) Assuming that you have openssl installed and it is running okay, you can usually get this option included by using the LDFLAGS and CPPFLAGS For example: CPPFLAGS='-I/usr/local/include/openssl' LDFLAGS='-L/usr/local/lib -R/ usr/local/lib' \ ./configure \ --prefix=/usr/local \ --with-ssl=openssl \ --with-libiconv-prefix=/usr/local \ with the paths modified for your installation. HTH, Jerry > ------------------------------ > > Message: 6 > Date: Tue, 22 Apr 2008 01:35:01 -0400 > From: "Tom Ray [Lists]" <lists(a)blazestudios.com> > Subject: [Dovecot] Compiling with SSL > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <480D7905.7030100(a)blazestudios.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I have Dovecot 1.0.9 running right now and I'm looking to upgrade > but at > the same time re-compile with SSL support. Dovecot's been working > great > for me so far. When I try to compile I keep getting this at the end: > > Building with SSL support ........... : no > Building with IPv6 support .......... : yes > Building with pop3 server ........... : yes > > This is what my configure line looks like: > > ./configure --prefix=/usr/local/dovecot --with-pop3d --with- > ssl=openssl > --with-ssldir=/usr/local/vps/sharedssl/openssl --with-passwd-file > > Am I not doing something right? Am I reading the configuration setup > wrong? Any help would be great! > > Thanks. > snip

1 0

Re: [Dovecot] Compiling with SSL
by Anders 22 Apr '08

22 Apr '08

Tom Ray [Lists] wrote: > Building with SSL support ........... : no > Am I not doing something right? Am I reading the configuration setup wrong? (now with correct sender address for this list) Hi. I would guess that you need to install an openssl-dev development package for whatever your distribution is. cheers Anders.

3 2

[Dovecot] IMAP clients generate user home folders one level higher than needed
by andel 22 Apr '08

22 Apr '08

Hi (Of course not the clinets generate the folders, dovecot does, but I wanted to have the title not be too long.) I am using static userdb: userdb static { args = uid=vmail gid=mail home=/srv/vmail/%d/%n } and I have configured the hostname in protocol lda. Now when mail arrives for a known virtual user, the home directory with all subdirectories is being created correctly unter /srv/vmail/$domain/$vuser. But when connecting from an IMAP client (I have tested Thunderbird and Outlook) a new home directory with apparently correct subfolders is bring created unter /srv/vmail/$vuser ! The connection works, I just don't see the mails which arrived since the client is mapping a directory one level higher than needed. Where do I have to look for the cause? I did not find anything reasonable yet. Thank you in advance, David

2 4

[Dovecot] Compiling with SSL
by Tom Ray [Lists] 22 Apr '08

22 Apr '08

I have Dovecot 1.0.9 running right now and I'm looking to upgrade but at the same time re-compile with SSL support. Dovecot's been working great for me so far. When I try to compile I keep getting this at the end: Building with SSL support ........... : no Building with IPv6 support .......... : yes Building with pop3 server ........... : yes This is what my configure line looks like: ./configure --prefix=/usr/local/dovecot --with-pop3d --with-ssl=openssl --with-ssldir=/usr/local/vps/sharedssl/openssl --with-passwd-file Am I not doing something right? Am I reading the configuration setup wrong? Any help would be great! Thanks.

1 0

[Dovecot] odd behaviour with antispam plugin
by ZyanKLee 22 Apr '08

22 Apr '08

hey, in my dspam database there has been some odd behaviour: during training dspam had created an uid entry named by the local part of the email. i.e.: user1 I use a virtual setup using dovecot, postfix and postfixadmin. On my first try I set up a database for dspam itself and there this happened. After I couldn't figure out how to solve this, I merged the database into the postfixadmin database. But using just the username for identifying email adresses is a bit critical within a virtual environment with multiple domains, isn't it? if one would not merge the databases - how could he solve this problem? Greetz, Zyan K Lee

2 1

[Dovecot] Moving Maildir email messages and backing things up.
by Karl Schmidt 22 Apr '08

22 Apr '08

I just moved to dovecot with Maildir. I think this is probably a stupid question, but I couldn't find an answer after an hour of googling and searching the wiki. What would happen if I ran a script that did this: mv ~/Maildir/.folder_one/cur/* ~/Maildir/.folder_two/cur/ My hunch is it might break things. What if dovecot was stopped? ,.,.,. Where can I find a list of files in ~/Maildir/ and a note on what they are? (And similarly for a ~/Maildir/.folder) I'm wondering if everything needs to be backed up, or if I can/should skip the indexes. What happens if any of these files changes during the backup? (I'm thinking I shouldn't have to stop dovecot for a backup). ---------------------------------------------------------------- Karl Schmidt EMail Karl(a)xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 "Give me four parameters and I can fit an elephant; Give me five and I can wag its tail." (The source of the above quote?? Variants have been attributed to C.F. Gauss, Niels Bohr, Lord Kelvin, Enrico Fermi.) ----------------------------------------------------------------

3 6

[Dovecot] antispam plugin ehancement
by ML 22 Apr '08

22 Apr '08

I'm not a developper so I can't do it by myself, but I wonder if it could be possible to use tagSpam and tagNospam DSPAM feature to ehance user's dspam lerning experience. I even don't know if this must be done by DSPAM itself or by dovecot, but let me explain : The feature would be done by a signature replacement into tagSpam and tagNospam text, so the user would simply have to click on the link at end of the mail to learn DSPAM : # dspam.conf tagSpam on tagNonspam on # msgtag.spam If this message was classified SPAM by mistake, please click here : http://example.com/dspam-retrain.cgi?sig= {DSPAM_SIG} # msgtag.nonspam If this message should have been classified SPAM, please click here : http://example.com/dspam-retrain.cgi?sig= {DSPAM_SIG} I think a click is easier and faster than a forward, what do you think of such an implementation ? Regards, David.

4 6

[Dovecot] Feature Request - starting dovecot, config file behavior
by Charles Marcus 21 Apr '08

21 Apr '08

Hey Timo, I was wondering how much trouble it would be to again emulate the way postfix does something - in this case, the way it reads its config file when starting up. Current behavior: Postfix: If postfix encounters the same setting defined more than once, the last one wins. Dovecot: If dovecot encounters the same setting defined more than once it gives an error (also when using the 'dovecot -n' command). I like to add all of my changes to the very bottom of the config file, but otherwise leave the config file as is... this makes it very easy when updating - I can easily keep all of the new default config file, and simply merge my customizations at the end. So - how hard would it be to make dovecot simply accept the last defined setting read, instead of refusing to start? Thanks much, and glad to have you back in action! -- Best regards, Charles

4 5

[Dovecot] mailtrain with dovecot antispam plugin
by Hugo Monteiro 21 Apr '08

21 Apr '08

Hello all, and Johannes if you're around, I was trying to set up the "new" antispam plugin with the mailtrain backend, and i was trying to use the sendmail binary that's part of a qmail system. The message wouldn't get sent and i kept getting exit error 100 from the /var/qmail/bin/sendmail binary. To try to figure out what was happening, i mean a fake sendmail program, which is nothing more than a bash script to capture the command call input. The script is rather simple, it just places the calling parameters into a txt file and the stdin into another. code is #!/bin/bash echo $* > /tmp/sendmail-parms.txt exec cat<&0 >> /tmp/sendmail-msg.txt exit 0 So i tried a retrain and went to see what those txt files had. The parms.txt file was fine apparently, with cat /tmp/sendmail-parms.txt i got -f hm(a)hmonteiro.net notspam-hm(a)hmonteiro.net Then i did the same to the message file, with cat /tmp/sendmail-msg.txt, and i got the follwing Return-Path: <hugo.monteiro(a)fct.unl.pt>Delivered-To: hm(a)hmonteiro.net Received: (qmail 21616 invoked from network); 19 Apr 2008 16:21:17 -0000 Received: (simscan 1.4.1 ppid 21609 pid 21611 t 0.1451s) (scanners: regex: 1.4.1 attach: 1.4.1 clamav: 0.92.1 /m:46/d:6803); 19 Apr 0108 16:21:17 -0000 Received: from femme-fatal.resnet.costabasto.com (HELO femme-fatal) (192.168.0.20) by hmonteiro.net with SMTP; 19 Apr 2008 16:21:17 -0000 Subject: buy some viagra HURRAY X-DSPAM-Result: Innocent X-DSPAM-Processed: Sat Apr 19 17:21:17 2008 X-DSPAM-Confidence: 0.4945 X-DSPAM-Probability: 0.0330 X-DSPAM-Signature: 480a1bfd216125429498786 viagra sale really HURRAY cheap! only $5! As you can see, there is no new line in the first line. Return-Path and Delivered-To are set in a single line, which makes qmail-inject (which is later used by /var/qmail/bin/sendmail) to abort like this cat /tmp/sendmail-msg.txt | /var/qmail/bin/sendmail -f hm(a)hmonteiro.net notspam-hm(a)hmonteiro.net qmail-inject: fatal: unable to parse this line: Return-Path: <hugo.monteiro(a)fct.unl.pt>Delivered-To: hm(a)hmonteiro.net Before i go into digging the plugin code i was wondering if i'm not seing things clearly and thinking this is in fact a bug in the plugin code. Thank you all in advance, Hugo Monteiro. -- ci.fct.unl.pt:~# cat .signature Hugo Monteiro Email : hugo.monteiro(a)fct.unl.pt Telefone : +351 212948300 Ext.15307 Centro de Informática Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa Quinta da Torre 2829-516 Caparica Portugal Telefone: +351 212948596 Fax: +351 212948548 www.ci.fct.unl.pt apoio(a)fct.unl.pt ci.fct.unl.pt:~# _

2 2

[Dovecot] Run command when moving messages
by Juan Asensio Sánchez 21 Apr '08

21 Apr '08

Hi Is it possible to run a command when a message is moved from a folder to another? I want this to simulate the antispam plugin, so one script would be ran when a message is moved to/from the spam folder, so the sa-learn command would be called. Thanks

3 2

[Dovecot] building a simple antispam plugin
by Alexander Prinsier 21 Apr '08

21 Apr '08

Hello, I'm trying to build another antispam plugin, but some things are a bit unclear. In backend_handle_mail I put store the signature returned from signature_extract into my antispam_transaction_context. In backend_commit it appears that the signature is empty. (It wasn't in backend_handle_mail). Somehow between backend_handle_mail en backend_commit it has been cleared... When I use i_strdup it appears to work. Anyone can tell me where this clearing happens? Is i_strdup the right way to do it then? Thanks, Alexander

3 4

[Dovecot] How to deal with mail to unknown virtual recipients?
by Andreas Ntaflos 19 Apr '08

19 Apr '08

Hello list, I am not quite sure whether this is a questions for Dovecot or Postfix. I have set up, virtual hosting for one domain (for test purposes) using a passwd-file as passdb and a static userdb (see dovecot -n at the end) along with Postfix in a manner described in [1], i.e. a non-Postfix mail store. Other than that I also do hosting for the canonical domain which is for users with a regular Unix account on the system (looked up via PAM) The virtual domain shall be "example.org", with two users "alice(a)example.org" and "bob(a)example.org". But today I received spam mail (which was correctly identified as such by amavisd-new) for "info(a)example.org" and "sales(a)example.org", two recipient addresses that do not exist. According to [1] "it's left up to the non-Postfix delivery agent to reject non-existent recipients from local submission or from local alias expansion." How to deal with such a situation? The sender address was clearly forged so returning a failed delivery message is pointless. The messages are now hanging around in the queue with a status of "deferred: temporary failure". The logs show: dovecot: auth(default): passwd(info(a)exmaple.org): unknown user dovecot: auth(default): passwd-file(info(a)mexample.org): unknown user dovecot: auth(default): static(info(a)example.org): passdb doesn't support lookups, can't verify user's existence postfix/pipe[25328]: C7EA18BC0B5: to=<info(a)exmaple.org>, relay=dovecot, delay=1.4, delays=0.07/0.02/0/1.3, dsn=4.3.0, status=deferred (temporary failure) The dovecot relay is defined in /etc/postfix/master.cf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} The question, once again, is: what to do in such a situation? A catch-all address could be set up, but to what end? It would just catch a lot of spam over time. What is the correct way to deal with this? More importantly: is there even anything Dovecot could (or should) do? Thanks in advance, Andreas [1] http://www.postfix.org/VIRTUAL_README.html#in_virtual_other # 1.0.10: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_cert_file: /path/to/ssl_cert ssl_key_file: /path/to/private_key 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 mail_extra_groups: mail mail_location: maildir:~/Maildir 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_executable(managesieve): /usr/local/libexec/dovecot/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): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle imap_client_workarounds(managesieve): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_uidl_format(managesieve): sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/public:CONTROL=~/Maildir/control/public:INDEX=~/Maildir/index/public namespace: type: private separator: / inbox: yes auth default: mechanisms: plain login verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd passdb: driver: pam userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%d/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

5 6

[Dovecot] Delete antispam emails
by David Reid 19 Apr '08

19 Apr '08

I'm using dovecot with the antispam plugin to allow for training, but how do I delete emails once they've been trained? If I delete them from the folder using an email client they get retrained as valid emails when they're moved to the trash folder! D'oh. I'm looking, ideally, for a solution that doesn't need a script to be run per user as I have a number of users using this feature. Also, the cleanspam script doesn't seem to be able to find the folder I'm using ('SpamTrain') so what format should I use? Thanks. david

3 11

[Dovecot] Cannot connect to dovecot imap server -- nothing in log
by David Benfell 18 Apr '08

18 Apr '08

Hello all, I'm trying to connect to a dovecot server I've just installed, using evolution. And I'm not having any success: starshine# tail -f /var/log/dovecot.log dovecot: 2008-04-16 20:11:37 Info: Dovecot v1.0.10 starting up dovecot: 2008-04-17 16:40:30 Warning: Killed with signal 15 dovecot: 2008-04-17 16:40:30 Info: Dovecot v1.0.10 starting up starshine# man dovecot starshine# dovecot -n # 1.0.10: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: none login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/Maildir:INBOX=~/failed-to-sort-Maildir:INDEX=% h/imap-folders namespace: type: private separator: / prefix: folders/ location: ~/imap-folders inbox: yes auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd starshine# All evolution tells me is that an error occurred. I have no idea what the problem is here. The server is on mail.parts-unknown.org if you wish to try to connect to it. And yes, it is actually running: starshine# ps aux | grep dovecot root 3072 0.0 0.0 2072 580 ? Ss 16:40 0:00 /usr/sbin/dovecot root 3073 0.0 0.1 9000 2148 ? S 16:40 0:00 dovecot-auth root 3559 0.0 0.0 3004 748 pts/0 R+ 16:48 0:00 grep dovecot starshine# I installed it from the Ubuntu package (hardy heron) and it is: starshine# dovecot --version 1.0.10 starshine# I'm simply mystified. What now? -- David Benfell benfell(a)parts-unknown.org Skype: greybeard95a

2 4

[Dovecot] CRAM-MD5 HMAC-MD5 password algorithm for PHP
by Hajo Noerenberg 18 Apr '08

18 Apr '08

Hi, based on the recent discussion by Bill Cole and Douglas Willcocks I've quickly put together a PHP script which generates MD5 'contexts' for Dovecot's password files: http://www.noerenberg.de/hajo/pub/dovecot_hmacmd5.php.txt The script has not been tested extensively, so use it on your own risk :) Most of the code has been shamelessly stolen from various sources. You'll find the names in the header of the script. Hajo

1 0

[Dovecot] Message UID Question
by Joe Allesi -X (joallesi - Coyote Creek Consulting at Cisco) 18 Apr '08

18 Apr '08

I have referred to the wiki and the RFC, but I still can't find the exact answer I'm looking for. From what I know, Dovecot uses the IMAP standard of 32 bit integers to uniquely identify messages. After a message is deleted from the mbox, can this UID ever be reissued to a new message or is that UID retired? What about after the 2 billion limit is reached? Thanks!

2 1

[Dovecot] Please help: LDAP configuration _almost_ works.
by Jack McKinney 18 Apr '08

18 Apr '08

Red Hat Linux release 7.2 (Enigma) OpenLDAP 2.3.38 Dovecot 1.0.12 SHORT VERSION ----- ------- Here is my dovecot-ldap.conf: hosts = ldap.lrtz dn = cn=varmail,ou=users,dc=lorentz,dc=com dnpass = ********* ldap_version = 3 auth_bind = yes pass_filter = (&(objectClass=inetOrgPerson)(mail=%Lu)) base = ou=users, dc=%Dd scope = onelevel I have tested using the above information with ldapsearch, and it works fine. However, when dovecot tries to authenticate the user, the LDAP server receives the query and responds to it (according to the LDAP log file), but dovecot just hangs there. 180 seconds later, it drops the IMAP client. E.g.: The dovecot log shows: Apr 3 08:13:21 fourier dovecot: auth(default): new auth connection: pid=15774 Apr 3 08:13:30 fourier dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Isecured^Ilip=x.x.x.x^Irip=y.y.y.y^Iresp=<hidden> Apr 3 08:13:30 fourier dovecot: auth(default): ldap(jackmc(a)lorentz.com,y.y.y.y): bind search: base=ou=users, dc=lorentz,dc=com filter=(&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com)) Apr 3 08:16:30 fourier dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=y.y.y.y, lip=x.x.x.x, TLS The OpenLDAP log shows that the query is received and that it returns a match: Apr 3 08:13:30 fourier slapd[14039]: conn=7 op=3 SRCH base="ou=users,dc=lorentz,dc=com" scope=1 deref=0 filter="(&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com))" Apr 3 08:13:30 fourier slapd[14039]: conn=7 op=3 SRCH attr=uid Apr 3 08:13:30 fourier slapd[14039]: conn=7 op=3 SEARCH RESULT tag=101 err=0 nentries=1 text= LONG VERSION ---- ------- My users login using their email address as username. Each domain has their own LDAP subtree. Each user has an entry in the ou=users subtree of the domain subtree, and has a mail: field (inetOrgPerson) listing their email address/login name. I am trying to use auth_bind: when I login with jackmc(a)lorentz.com, dovecot should search for mail=jackmc(a)lorentz.com in the onelevel below ou=users,dc=lorentz,dc=com and find me as "cn=Jack McKinney,ou=users,dc=lorentz,dc=com". I have created an entry in LDAP (varmail) that should be able to do this query. Indeed, from the command line, it works: ldapsearch -h ldap.lrtz -b 'ou=users, dc=lorentz, dc=com' -D 'cn=varmail,ou=users,dc=lorentz,dc=com' -x -W -s onelevel '(&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com))' Enter LDAP Password: # extended LDIF # # LDAPv3 # base <ou=users, dc=lorentz, dc=com> with scope oneLevel # filter: (&(objectClass=inetOrgPerson)(mail=jackmc(a)lorentz.com)) # requesting: ALL # # Jack McKinney, users, lorentz.com dn: cn=Jack McKinney,ou=users,dc=lorentz,dc=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson cn: Jack McKinney givenName: Jack McKinney sn: McKinney mail: jackmc(a)lorentz.com # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 It appears that dovecot performs the above query successfully, but then never uses the password and retrieved DN to attempt to bind and authenticate the user. Instead, it just times out. (See log files above in the SHORT VERSION). I tried to add pass_attrs, in case there was a bug in dovecot where it ignores the reply if there are no pass_attrs (even though none are needed), but it still fails the same way. Timo Sirainen suggested that I add a debug line to src/auth/db-ldap.c ldap_input() around line 372: msgid = ldap_msgid(res); // added line: i_info("LDAP: Received reply %d", msgid); I did this. Now, when the server first starts up, this line is logged. However, it is not logged when it queries the LDAP server as a result of an IMAP connection needing authentication. -- Jack McKinney GPG 1024D/99C6A174 jackmc(a)lorentz.com YM:lfaatsnat2006 AIM:jackmclorentz "There is no parameter that makes it impossible for you to perform still more excellently." -Mario Cuomo, on the lack of a clock in baseball

7 25

Re: [Dovecot] Mixing LDAP and static
by k bah 18 Apr '08

18 Apr '08

That didn't work for me: user_attrs = =home=/var/dovecot-test/home/%n,uid=user (at /etc/dovecot/dovecot-ldap.conf) ( /etc/dovecot/dovecot.conf: mail_location = mbox:/var/dovecot-test/data/%n~%d:INBOX=/var/dovecot-test/%n~%d:INDEX=/var/dovecot-test-no-quotas/index/%n~%d ) neither: user_attrs = uid=user,=home=/var/dovecot-test/home/%n neither: user_attrs = =home=/var/dovecot-test/home/%n on the log it says: dovecot: auth(default): ldap(user0027(a)mydomain.tld,1xx.xxx.xxx.x): user search: base=dc=mydomain,dc=tld scope=subtree filter=(&(objectclass=inetlocalmailrecipient)(mail=user0027(a)mydomain.tld)) fields= and at dovecot start up: Starting dovecot ILoading modules from directory: /usr/lib64/dovecot/modules/imap IModule loaded: /usr/lib64/dovecot/modules/imap/lib10_quota_plugin.so IModule loaded: /usr/lib64/dovecot/modules/imap/lib11_imap_quota_plugin.so IEffective uid=65534, gid=65534, home= using dovecot-1.0.5-6 on OpenSuSE 10.3. thanks = Arthritis Specialists in Magnetism Quality hand crafted jewelry with magnets. Necklaces, bracelets, shoe insoles and more. http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=dfcb5a2d4f25ae3051a9c94… -- Powered by Outblaze

3 2

[Dovecot] authentication troubles
by Albert Dengg 18 Apr '08

18 Apr '08

hi i have a strange problem with my dovecot installtion: i configured it to accept digest-md5 authentication only but for some reason mailclients (i tried mutt and thunderbird so far) want to log with PLAIN (which fails of course). authentication basically works, e.g. if i explicitly set set imap_authenticators="digest-md5 in .muttrc everything works... any idea what is going wrong? config attached below tia yours albert # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_listen(default): *:22993 ssl_listen(imap): *:22993 ssl_listen(pop3): *:22995 ssl_cipher_list: ALL:!LOW 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: 107 last_valid_uid: 107 mail_location: maildir:%h/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/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 namespace: type: private location: maildir:%h/Maildir inbox: yes auth default: mechanisms: digest-md5 realms: mailstore.nicenamecrew.com default_realm: mailstore.nicenamecrew.com username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=vmail gid=vmail home=/var/mail/virtual/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 group: vmail

2 2

[Dovecot] postfix, dovecot-lda, sieve & smartsieve not working on 1.1-rc4
by kjetil＠hoiseth.no 18 Apr '08

18 Apr '08

Seems there is a bug in 1.1-rc4 in regards to sieve/managesieve, this problem goes away if I downgrade to 1.0.13. Gentoo x86_64 2.6.18-028stab053 (OpenVZ) Intel(R) Core(TM)2 Quad CPU Q6600 Maildirs are not NFS mounted The VE in question runs daemons with the following USE flags; mail-mta/postfix-2.4.6-r2 USE="dovecot-sasl ipv6 ldap mailwrapper mysql pam ssl" net-mail/dovecot-1.0.13-r1 USE="ipv6 ldap managesieve mysql pam sieve ssl" Sieve rules are setup only in Smartsieve(1.0-RC2), running in Lighttpd(1.4.18-r3). --- # 1.0.13: /etc/dovecot/dovecot.conf protocols: imaps managesieve ssl_cert_file: /etc/ssl/private/hoiseth.no.pem ssl_key_file: /etc/ssl/private/hoiseth.no.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_location: maildir:~/.maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(managesieve): ~/.dovecot.sieve auth default: passdb: driver: pam args: login userdb: driver: passwd --- 1.1-rc4; deliver(kjetil): Apr 04 15:17:43 Info: Loading modules from directory: /usr/lib/dovecot/lda deliver(kjetil): Apr 04 15:17:43 Info: Module loaded: /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so deliver(kjetil): Apr 04 15:17:43 Info: maildir: data=/home/kjetil/.maildir deliver(kjetil): Apr 04 15:17:43 Info: maildir++: root=/home/kjetil/.maildir, index=, control=, inbox=/home/kjetil/.maildir deliver(kjetil): Apr 04 15:17:43 Info: msgid=<567340a538d370592ec2a6da4e0fcdf2(a)langtind.no>: saved mail to INBOX 1.0.13; deliver(kjetil): Apr 04 15:33:14 Info: Loading modules from directory: /usr/lib/dovecot/lda deliver(kjetil): Apr 04 15:33:14 Info: Module loaded: /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so deliver(kjetil): Apr 04 15:33:14 Info: maildir: data=/home/kjetil/.maildir deliver(kjetil): Apr 04 15:33:14 Info: maildir: root=/home/kjetil/.maildir, index=/home/kjetil/.maildir, control=, inbox= deliver(kjetil): Apr 04 15:33:14 Info: cmusieve: Using sieve path: /home/kjetil/.dovecot.sieve deliver(kjetil): Apr 04 15:33:14 Info: cmusieve: Executing script /home/kjetil/.dovecot.sievec deliver(kjetil): Apr 04 15:33:14 Info: msgid=<4b15e68896a9ef204bf00482e948058f(a)langtind.no>: saved mail to priv I upgraded to 1.1-rc4 and indeed the problem re-occured, Id be happy to bring more info/ax to the VE if it helps nailing the issue.

2 1

[Dovecot] Dovecot LDA / Deliver question
by Stacy Trippe 18 Apr '08

18 Apr '08

Problem described: I am trying to get Postfix + Dovecot + MySQL setup to work together in a virtual mail hosting platform. I am running Postfix 2.3.x, and MySQL 5.0.x. I am trying to use Dovecot's LDA for delivery to the users vmail home directory -- usually under /var/vmail/domain.com/j/jdoe for home and /var/vmail/domain.com/j/jdoe/.maildir for mail location, using MAILDIR format. However, I cannot get Dovecot's LDA to write the maildir folders/files into the right location. It wants to write in MBOX format to /var/vmail/mail/inbox instead. When I force the mail_location variable...it just uses the system 'vmail' user (uid: 1101) and 'vmail' group (gid: 1101) that I assigned for the virtual mail user. mail_location = maildir:/var/vmail/%d/%1n/%n I am not sure where to go to troubleshoot Dovecot LDA...and how to turn up/down the verbosity of debug messages (albeit now I am logging the deliver info to /var/log/dovecot-deliver.log). Does anyone know what I am missing? Can Dovecot LDA be told how to deliver mail to the users maildir folder? Here is my postfix master.cf: ... dovecot unix - n n - - pipe flags=DRhu user=vmail argv=/usr/libexec/dovecot/deliver -f ${sender} Here is my postfix main.cf (as it pertains to dovecot LDA): virtual_transport = dovecot mailbox_command = /usr/libexec/dovecot/deliver smtpd_sasl_type = dovecot dovecot_destination_recipient_limit = 1 dovecot --version 1.0.rc15 dovecot -n # /etc/dovecot.conf log_path: /var/log/dovecot.log 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: SMTP ready. login_process_size: 64 login_processes_count: 5 login_max_connections: 512 mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: prefetch userdb: driver: sql args: /etc/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: 432 user: vmail group: vmail grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = host=localhost dbname=mailsql user=mailquery password=m@1l default_pass_scheme = PLAIN-MD5 password_query = SELECT email as user, passwd AS password, concat('/var/vmail',homeDir) as userdb_home, 1101 AS userdb_uid, 1101 AS userdb_gid, concat('maildir:/var/vmail',mailDir) as userdb_mail FROM users WHERE (username = '%u' OR email = '%u' OR email = concat('%u','@domain.net')) AND status = 'A' AND type = 'M' user_query = SELECT concat('/var/vmail',homeDir) as home, 1101 AS uid, 1101 AS gid, concat('maildir:/var/vmail',mailDir) as mail FROM users WHERE username = '%u' .... The schema for my data table is as follows: +----------+--------------+------+-----+-------------------+-------+ | Field | Type | Null | Key | Default | Extra | +----------+--------------+------+-----+-------------------+-------+ | updated | timestamp | YES | | CURRENT_TIMESTAMP | | | username | tinytext | NO | | NULL | | | email | varchar(128) | NO | PRI | NULL | | | passwd | varchar(128) | YES | | NULL | | | name | tinytext | NO | | NULL | | | status | char(1) | NO | | A | | | type | char(1) | NO | | M | | | homeDir | longtext | YES | | NULL | | | mailDir | longtext | YES | | NULL | | | newEmail | varchar(128) | NO | | NULL | | +----------+--------------+------+-----+-------------------+-------+ Any help at all would be greatly appreciated! Thanks, Stacy

2 1

[Dovecot] Feature request
by Ruud Boon 18 Apr '08

18 Apr '08

Hi! I hope I'm using the right mailing for a feature request. I'm using dovecot on my server for a year now and I'm very happy with it. Its extremely stable and fast. Ok what is my situation why I'm asking a feature.. Users are retrieving mail using pop3 over the external ip address. When the user connects to there webmail. The webmail client (Squirrelmail) is using imap on the localhost. I would like to give some users the option to use imap over the external ip, I want to set option in my MySql backend configuration. As far as I know there isn't a possible solution on dovecot right now that's why I hope you can build a extra config parameter that gives me the possibility to allow users to retrieve email by imap by ip. So all users can do an imap request on localhost (for webmail) and some user are allowed to do an imap request over the external ip. I hope that my request is clear and I'm posting in the right group. With regards, Ruud Boon

3 2

[Dovecot] Dovecot sending OK while idling
by John Temples 18 Apr '08

18 Apr '08

When an IDLE command is active, Dovecot sends an OK every two minutes. Is it possible to disable this? I'm trying to eliminate unnecessary traffic on a link that's charged by the kilobyte. Using Dovecot 1.0.7. -- John W. Temples, III

3 2

[Dovecot] How to log login errors?
by Sven Schmidt 18 Apr '08

18 Apr '08

Hi! I used "auth_debug=yes" and "auth_debug_passwords=yes". But I only see connects and disconnects: Apr 11 09:17:43 dovecot: POP3(info(a)xxxx.xx): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 11 09:17:43 dovecot: POP3(info(a)xxxx.xx): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 11 09:18:11 dovecot: pop3-login: Login: user=<pop-test(a)xxxx.xx>, method=PLAIN, rip=80.146.3.204, lip=87.106.66.95

2 1

[Dovecot] Single quote email addresses
by Guy 18 Apr '08

18 Apr '08

Hi, I've just been told that I need to make our mail server cater to accounts with single quotes. Has anyone set dovecot up to do this or know of any documentation/howto on it, assuming it's possible at all. I'm running dovecot 1.0.5 on Ubuntu 7.10 if that makes much of a difference. Thanks for any help anyone can give. Guy -- Don't just do something...sit there!

2 1

[Dovecot] dovecot + qmail - deliver not working...
by Peter Van den Wildenbergh 18 Apr '08

18 Apr '08

Hi List, I have a working qmail server and installed dovecot trying to setup vmail... it's not going as expected... What is working: qmail I can log-in using Thunderbird (IMAP) from dovecot-info.log dovecot: Apr 10 21:19:54 Info: imap-login: Login: user=<peter(a)---.com>, method=PLAIN, rip=192.168.10.50, lip=192.168.10.188 Config bits: Ubuntu (command-line system) 7.10 ls -l /home drwxr-xr-- 2 vmail vmail ... vmail UID GID for vmail = 500 Content of /etc/dovecot/dovecot.conf protocols = imap imaps log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot-info.log ssl_disable = yes disable_plaintext_auth = no mail_location = maildir:~/Maildir dotlock_use_excl=yes maildir_copy_with_hardlinks=yes auth_verbose = yes auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot/passwd } userdb static { args = uid=500 gid=500 home=/home/vmail/%d/%n } } cat /etc/dovecot/passwd peter@meta-logica.com:{SSHA}iDMg--- peter@wilboo.org:{SSHA}iDMg--- cat /var/qmail/control/defaultdelivery |/var/qmail/bin/preline -f /usr/lib/dovecot/deliver -d $EXT@$USER (LWQ setup - verified location of 'deliver') Looks like local delivery for qmail is NOT working :-( from the logs: starting delivery 8: msg 3752525 to local peter@ma--- status: local 1/10 remote 0/20 delivery 8: deferral: Can't_open_log_file_/var/log/dovecot.log:_Permission_denied/ status: local 0/10 remote 0/20 status: exiting permission on /var/log/dovecot.log = -rw-r--r-- 1 vmail vmail 728 2008-04-10 21:36 /var/log/dovecot.log qmailctl stat messages in queue: 7 messages in queue but not yet preprocessed: 3 So I assume that the inability to 'log' is stopping the delivery process... Couldn't find anything obvious on google. Any suggestions? Regards Peter

2 1

[Dovecot] dovecot and postfix virtual mailbox domains, system users
by Dave 18 Apr '08

18 Apr '08

Hello, I'm trying to get dovecot and postfix virtual domains working on an fc6 system. My software versions are postfix 2.4.5 installed from rpm and dovecot 1.0.3 also installed from rpm. I'm only running secure protocols, pop3s at the moment, imaps later on. I've set up postfix for virtual mailbox domains as per it's howto on the subject and confirmed that email sent gets delivered to the virtual area, which in this case is /home/vmail/domain.com/username/, there's a maildir under that area and incoming mail gets delivered by postfix to that area. In the first case the user is a shell user who has a login, in all other cases the users will be completely virtual, having no login account at all. When i atempt to get mail from the server using this user, the one with the login, i am getting a can not map username coming from dovecot. Here's my config: # 1.0.3: /etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot.info protocols: pop3s ssl_ca_file: /etc/dovecot/ca-cert.pem ssl_cert_file: /etc/dovecot/pop.cert ssl_key_file: /etc/dovecot/pop.key ssl_cipher_list: ALL:!LOW disable_plaintext_auth: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login valid_chroot_dirs: /var/spool/vmail mail_extra_groups: mail mail_location: maildir:/home/vmail/%d/%u maildir_copy_with_hardlinks: yes mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 auth default: mechanisms: plain login verbose: yes passdb: driver: passwd userdb: driver: passwd and the specific maillog error is this: Apr 11 23:48:17 s15298471 dovecot: pop3-login: Login: user=<user>, method=PLAIN, rip=66.139.186.37, lip=74.208.64.129, TLS Apr 11 23:48:17 s15298471 dovecot: POP3(user): stat(/home/vmail//user/cur) failed: Permission denied Apr 11 23:48:17 s15298471 dovecot: POP3(user): stat(/home/vmail//user/cur) failed: Permission denied Apr 11 23:48:17 s15298471 dovecot: POP3(user): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2008-04-11 23:48:17] Apr 11 23:48:17 s15298471 dovecot: POP3(user): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 I'd appreciate any pointers. I think i am close, but am not seeing it. Thanks. Dave.

2 1

[Dovecot] Cross Compiling Dovecot?
by stefano＠tiscali.dk 18 Apr '08

18 Apr '08

2 1

[Dovecot] remove mails from shared folders
by Patrick Fischer 18 Apr '08

18 Apr '08

Hallo dovecot This is my first post on this list. I'm new to IMAP servers and i read lots of howtos. If I use the wrong term for some features please tell me the right term. I have installed dovecot under ubuntu 7.10 and it works fine. dovecot + fetchmail + postfix I would like to use shared folders the way that we have an email pool for info(a)mydomain.com user1(a)mydomain.com -> User1 user2(a)mydomain.com -> User2 user3(a)mydomain.com -> User3 info(a)mydomain.com -> Pool (look at this http://decembersoul.dyndns.org/wiki/images/c/c6/IMAP1.jpeg ) The users can see and process emails from the email pool. To process an email the user move the email from the email pool to his own inbox. This should make sure that only one user process a email. Shared folders are created by symlink. The problem is that, if a user move an email out of the email pool, the other users still can see the mail in the pool. It takes a long time to remove the mail from the pool for every user. Move TO the pool works immediatley. The user can make a "compress folder" to remove the emails but this can't be the soulution. Maybe this is a client failed (tested only with thunderbird) Best regards Patrick Fischer

2 1

[Dovecot] Minor namespace issue - inconsistent default value
by Joel Johnson 18 Apr '08

18 Apr '08

I burned some time yesterday over a documentation inconsistency. The dovecot-example.conf file shipped with dovecot (checked with 1.1rc4 and the April 3 nightly), includes an indication at the top that the commented values listed are the defaults for the settings. Line 248 of this file has the inbox setting for a private namespace which indicates that the default value for this setting is true. However, line 358 of ./srv/master/master-settings.c sets the default value of the namespace inbox variable to false. With a single private namespace (what I was setting up), one wants this value to be true, however when using multiple namespaces the default should likely remain false. I propose keeping the coded default and changing the line in the example configuration file to indicate false. Before I determined that this was the issue, I had a single namespace defined (but not as INBOX), and dovecot (both deliver and imap) created and read from a .INBOX directory under the Maildir. Thanks, Joel

2 1

[Dovecot] more than one ldap database.
by Mauro Sanna 18 Apr '08

18 Apr '08

If I have two databases in my ldap, ex: dc=dominio1,dc=it is the first database and dc=dominio2,dc=it is the second one. Can I put these two search bases in dovecot-ldap.conf?

4 4

[Dovecot] Bah! Outlook
by Jason Wohlford 18 Apr '08

18 Apr '08

Hi All, I run a little hosting company. I use Dovecot 1.0.10* with IMAP exclusively. Lots of my customers use Outlook or Outlook Express. This poses a problem. These programs don't and have absolutely no workarounds to move messages to a trash folder when deleted. They only mark the message for deletion. Then, users have to purge the message to actually delete it. Outlook has a way to hide deleted messages and also auto-purge them when moving to a different folder. That just doesn't cut it. (Thanks Microsoft! :-p ) So, I'm thinking Dovecot could pick up where Microsoft left off. It seems to me there needs to be two things done. First, a system that automatically copy a message marked for deletion from one folder (e.g. INBOX) to a trash folder (e.g. Trash, Deleted Messages, etc.) Dovecot's lazy_expunge might already do this, but I couldn't quite discern it from the wiki docs. Second, a way to only do this when Outlook or Outlook Express is the one who is deleting a message. Possibility? Comments? Cheers, Jason P.S. Thanks for the great software! *Yes, I know. I need to upgrade to Dovecot 1.0.13. -- Jason Wohlford <jason(a)wohlford.org> <http://wohlford.org>

9 14

Re: [Dovecot] Development news
by Eugene 18 Apr '08

18 Apr '08

Hi Timo and welcome back! > On Sun, 2008-03-16 at 20:29 +0200, Timo Sirainen wrote: >> Tomorrow begins a 5 week lab course at school. Every day and about 8 >> hours a day. And then we'll also have to write these reports about what >> we have done and how/why, which takes quite a lot of time as well. After >> 5 weeks there's one free week Are you a teacher or a student? And generally speaking, I expected a small bio/CV on the site but was not able to find one. Best wishes Eugene

3 2

[Dovecot] keep users from deleting email
by Adam Williams 17 Apr '08

17 Apr '08

I looked on the dovecot website, but didn't find an answer. With dovecot 1.0, is there a way to keep users from deleting their email? So that when they click the delete button on their email client, nothing happens/dovecot refuses to delete email, etc?

6 17

[Dovecot] Dovecot 1.1rc3 "Out of Memory" crashes from pop3-login?
by richs＠whidbey.net 17 Apr '08

17 Apr '08

We recently began seeing server crashes in our cluster related to "pop3-login", which is causing "oom-killer" to be invoked. The server only recovers after a reboot. From dovecot.conf: login_process_per_connection = yes login_processes_count = 16 login_max_processes_count = 256 (Should we try switching processes_per_connection to no?) From dovecot.log: dovecot: Apr 17 07:48:39 Info: POP3(AAAAAAA): Disconnected: Logged out top=0/0, retr=0/0, del=0/154, size=10250932 dovecot: Apr 17 07:48:40 Info: POP3(BBBBBBB): Disconnected: Logged out top=0/0, retr=2/3729, del=2/2, size=3695 dovecot: Apr 17 07:48:40 Info: imap-login: Login: user=<CCCCCC>, method=PLAIN, rip=10.20.10.129 dovecot: Apr 17 07:48:41 Info: IMAP(CCCCCCC): Disconnected: Logged out bytes=551/7888 dovecot: Apr 17 07:49:06 Error: child 20678 (login) killed with signal 9 dovecot: Apr 17 07:49:12 Info: pop3-login: Login: user=<DDDDDDDD>, method=PLAIN, rip=66.165.6.233 dovecot: Apr 17 07:49:12 Info: pop3-login: Login: user=<EEEEEEEE>, method=PLAIN, rip=71.222.224.38 From /var/log/messages: Apr 17 07:48:42 mail2 kernel: pop3-login invoked oom-killer: gfp_mask=0xd0, order=0, oomkilladj=0 Apr 17 07:48:42 mail2 kernel: [<c0450ace>] out_of_memory+0x3b/0x179 Apr 17 07:48:42 mail2 kernel: [<c0451f01>] __alloc_pages+0x1fe/0x27e Apr 17 07:48:42 mail2 kernel: [<c05c6696>] tcp_sendmsg+0x4e7/0x994 Apr 17 07:48:42 mail2 kernel: [<c05dd85d>] inet_sendmsg+0x35/0x3f Apr 17 07:48:42 mail2 kernel: [<c059967c>] do_sock_write+0xa3/0xaa Apr 17 07:48:42 mail2 kernel: [<c059b653>] sock_writev+0x9b/0xb4 Apr 17 07:48:42 mail2 kernel: [<c04352a1>] autoremove_wake_function+0x0/0x2d Apr 17 07:48:50 mail2 kernel: [<c059bd76>] lock_sock+0x8e/0x96 Apr 17 07:48:50 mail2 kernel: [<c048bba9>] inotify_d_instantiate+0x3c/0x5f Apr 17 07:48:50 mail2 kernel: [<c05fb6bf>] _spin_lock_bh+0x8/0x18 Apr 17 07:48:50 mail2 kernel: [<c059bc63>] release_sock+0xc/0x91 Apr 17 07:48:50 mail2 kernel: [<c05fb6bf>] _spin_lock_bh+0x8/0x18 Apr 17 07:49:11 mail2 kernel: [<c059bd76>] lock_sock+0x8e/0x96 Apr 17 07:49:11 mail2 kernel: [<c04063f2>] do_IRQ+0xa5/0xae Apr 17 07:49:11 mail2 kernel: [<c040492e>] common_interrupt+0x1a/0x20 Apr 17 07:49:11 mail2 kernel: [<c059b5b8>] sock_writev+0x0/0xb4 Apr 17 07:49:11 mail2 kernel: [<c046986a>] do_readv_writev+0x166/0x277 Apr 17 07:49:11 mail2 kernel: [<c048d240>] ep_ptable_queue_proc+0x55/0x65 Apr 17 07:49:11 mail2 kernel: [<c05c5d6b>] tcp_poll+0x19/0x127 Apr 17 07:49:11 mail2 kernel: [<c0471673>] sys_fstat64+0x1e/0x23 Apr 17 07:49:11 mail2 kernel: [<c04699b2>] vfs_writev+0x37/0x43 Apr 17 07:49:11 mail2 kernel: [<c0469df6>] sys_writev+0x3c/0x96 Apr 17 07:49:11 mail2 kernel: [<c0403e95>] sysenter_past_esp+0x56/0x79 Apr 17 07:49:11 mail2 kernel: ======================= Apr 17 07:49:11 mail2 kernel: Mem-info: Apr 17 07:49:11 mail2 kernel: DMA per-cpu: Apr 17 07:49:11 mail2 kernel: cpu 0 hot: high 0, batch 1 used:0 Apr 17 07:49:11 mail2 kernel: cpu 0 cold: high 0, batch 1 used:0 Apr 17 07:49:11 mail2 kernel: cpu 1 hot: high 0, batch 1 used:0 Apr 17 07:49:11 mail2 kernel: cpu 1 cold: high 0, batch 1 used:0 Apr 17 07:49:11 mail2 kernel: DMA32 per-cpu: empty Apr 17 07:49:11 mail2 kernel: Normal per-cpu: Apr 17 07:49:11 mail2 kernel: cpu 0 hot: high 186, batch 31 used:27 Apr 17 07:49:11 mail2 kernel: cpu 0 cold: high 62, batch 15 used:51 Apr 17 07:49:11 mail2 kernel: cpu 1 hot: high 186, batch 31 used:30 Apr 17 07:49:11 mail2 kernel: cpu 1 cold: high 62, batch 15 used:58 Apr 17 07:49:11 mail2 kernel: HighMem per-cpu: Apr 17 07:49:11 mail2 kernel: cpu 0 hot: high 186, batch 31 used:129 Apr 17 07:49:11 mail2 kernel: cpu 0 cold: high 62, batch 15 used:6 Apr 17 07:49:11 mail2 kernel: cpu 1 hot: high 186, batch 31 used:124 Apr 17 07:49:11 mail2 kernel: cpu 1 cold: high 62, batch 15 used:10 Apr 17 07:49:11 mail2 kernel: Free pages: 2871096kB (2863824kB HighMem) Apr 17 07:49:11 mail2 kernel: Active:90263 inactive:9647 dirty:30 writeback:0 unstable:0 free:717774 slab:215197 mapped:2666 pagetables:1253 Apr 17 07:49:11 mail2 kernel: DMA free:3588kB min:68kB low:84kB high:100kB active:0kB inactive:0kB present:16384kB pages_scanned:0 all_unreclaimable? yes Apr 17 07:49:11 mail2 kernel: lowmem_reserve[]: 0 0 880 4848 Apr 17 07:49:11 mail2 kernel: DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no Apr 17 07:49:11 mail2 kernel: lowmem_reserve[]: 0 0 880 4848 Apr 17 07:49:11 mail2 kernel: Normal free:3684kB min:3756kB low:4692kB high:5632kB active:184kB inactive:20kB present:901120kB pages_scanned:361 all_unreclaimable? yes Apr 17 07:49:11 mail2 kernel: lowmem_reserve[]: 0 0 0 31744 Apr 17 07:49:11 mail2 kernel: HighMem free:2863824kB min:512kB low:4748kB high:8988kB active:360868kB inactive:38568kB present:4063232kB pages_scanned:0 all_unreclaimable? no -Rich

2 4

[Dovecot] Dovecot and multiple instances in Geentoo
by Wojciech Matys 17 Apr '08

17 Apr '08

Is there any possiblity to run more than one instance of dovecot in gentoo (I was trying to run second instance but I don't know how to force it to use other pid file than /var/run/dovecot/master.pid) I'm using dovecot from portage dovecot-1.0.13-r1.

2 1

[Dovecot] CRAM-MD5 Password Generation Algorithm
by Douglas Willcocks 17 Apr '08

17 Apr '08

Hi, I'm just in the middle of setting up dovecot to serve IMAPS -- Actually I've finished apart from one thing: CRAM-MD5 passwords. I'm using SQL as a backend for the password storage, and I don't want to store the passwords in plaintext. I've also configured dovecot to be rather restrictive when it comes to authentication methods (only CRAM-MD5 is allowed). To generate the passwords to go into the database I can use the dovecotpw utility, but I'm wanting to stick some sort of minimal admin interface on the server to be able to manage the users etc without having to use the CLI. I've looked at the theoretical explanation of the hashing algorithm, and I've read through the source code that dovecotpw uses to generate the passwords with the intent of creating a higher level language library (Perl, Ruby, PHP ... whatever)) to generate passwords, but I don't seem to be able to replicate the functionality, and there don't seem to be any existing libraries that generate consistent results (that I've found). I don't have that much experience with C, and so I'm sure that I must have misunderstood how dovecotpw does its stuff. Perhaps someone could explain how the algorithm works? Or point me in the right direction? Thanks, Douglas Willcocks

4 11

[Dovecot] Dovecot-deliver lookup fails
by Wouter Amsterdam 17 Apr '08

17 Apr '08

Hi all, I'm still trying to get Dovecot-deliver to work in my config. I have found the problem to be in the maildir lookup for Dovecot-deliver as logged in /var/log/maillog: "Apr 15 16:30:34 termserv dovecot: auth(default): static(user(a)zesgoes.nl): passdb doesn't support lookups, can't verify user's existence" The thing I don't get, is that if I remove the virtual_transport modifications in /etc/postfix/master.cf and /etc/postfix/main.cf and the socket listen in /etc/dovecot.conf, all works well. So dovecot has no problems looking up my users on a LDAP server as a passdb backend, but failes when using the same passdb for dovecot-deliver. How come? TIA, Wouter

2 1