- dovecot - dovecot.org

[Dovecot] ugly hack to make maildir quotas work
by Joshua Goodall 16 Feb '06

16 Feb '06

Timo encouraged me to forward this to the list. Basically it pokes the right value into the right place to make quota deltas work properly when saving mail to Maildirs. It's a nasty hack workaround, so don't rely on it without understanding that it should be superseded in future. Without this, saving to a maildir doesn't increment quota. --- src/lib-storage/index/maildir/maildir-save.c 14 Jan 2006 18:47:50 -0000 1.64 +++ src/lib-storage/index/maildir/maildir-save.c 16 Feb 2006 04:32:49 -0000 @@ -9,6 +9,7 @@ #include "str.h" #include "maildir-storage.h" #include "maildir-uidlist.h" +#include "index-mail.h" #include <stdio.h> #include <stdlib.h> @@ -233,6 +234,7 @@ struct utimbuf buf; const char *path; int output_errno; + struct stat st; if (ctx->failed && ctx->fd == -1) { /* tmp file creation failed */ @@ -264,6 +266,9 @@ "fsync(%s) failed: %m", path); ctx->failed = TRUE; } + if (fstat(ctx->fd, &st) < 0) { + ctx->failed = TRUE; + } if (close(ctx->fd) < 0) { mail_storage_set_critical(STORAGE(ctx->mbox->storage), "close(%s) failed: %m", path); @@ -297,6 +302,8 @@ if (mail_set_seq(dest_mail, ctx->seq) < 0) return -1; + + ((struct index_mail *)dest_mail)->data.physical_size = st.st_size; } t_pop(); /k -- Josh "Koshua" Goodall "as modern as tomorrow afternoon" joshua(a)roughtrade.net - FW109

3 3

[Dovecot] Question regarding 'dovecot-auth'
by Paul E Virgo 15 Feb '06

15 Feb '06

Hello Timo, I am compiling dovecot-1.0.beta3, and I get the following message when the dovecot-auth module is being compiled: Undefined symbol sql_drivers_register_all first referenced in main.o Now I had run 'configure' with the '--without-sql-drivers' since I neither have MySQL or PostgresSQL installed on my server. Does this mean I DO have to get either package, install, and run it '--with-sql-drivers'? Or is it that the '--without...' feature doesn't work as intended? Am I making ANY sense? Thanks.

2 1

[Dovecot] NFS Stale File Handles on Indexes
by Tony Kay 15 Feb '06

15 Feb '06

The configuration files has settings that seem to address the issues of using indexes on NFS (i.e. locking and mmap fixes), but we are using Dovecot on NFS, and when the load gets high we start to see a lot of NFS stale file handle errors, particularly with MS clients like Outlook. I see the discussion about these errors from last year. Any updates on the state of the code? Should we be using in-memory or local indexes instead for now? - Dovecot 1.0b3 - four physical IMAP servers - mbox format accounts on NFS netapps - currently allowing NFS indexes w/mmap disabled, and using dotlocks -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Perfection uncanned Like a beautiful redhead Fresh from her trailer from Spam-Ku : Tranquil Reflections on Luncheon Loaf by John Cho

2 1

[Dovecot] imap_capability setting
by Bill Boebel 15 Feb '06

15 Feb '06

In src/master/master-settings.c, there is a config variable "imap_capability" that is read in from the conf file... but in the rest of the code it looks like that variable is never used. I assume this is there for future use, but just wanted to confirm that the code not using it was intentional. Since we are using Dovecot as an IMAP proxy for a Courier backend (for now), we need to advertise a different capability string than the Dovecot default. I have changed the hardcoded value in the ./configure script (@ 31015) for now. Bill

2 1

[Dovecot] Dovecot RFC non-compliance: Mailbox names
by Tony Kay 15 Feb '06

15 Feb '06

Hi, I think I already know the answer to this and I agree with it, but I have a question about "invalid" mailbox naming decisions in dovecot. Technically, RFC3501 (Section 5.1, pg. 18, client consideration 3) says that * and % are legal in mailbox names, though it implicitly discourages their use. We just migrated to dovecot, and unfortunately have a few users who used * in their mailbox naming (which worked on our old IMAP server). I looked in the mailing list and source comments, but I could not find any discussion. Was there any discussion about the imap/commands-util.c:48? 46: /* make sure it even looks valid */ 47: sep = mail_storage_get_hierarchy_sep(storage); 48: if (*mailbox == '\0' || strspn(mailbox, "\r\n*%?") != 0) { 49: client_send_tagline(cmd, "NO Invalid mailbox name."); which is technically not RFC-compliant? I have a feeling it fixes much more important things than it breaks (i.e. LIST/LSUB), but then again we never had complaints from people using those characters in names until they stopped being supported. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Sanity is a cozy lie. Susan Sontag

2 2

[Dovecot] Solaris and T1
by Martin Preen 15 Feb '06

15 Feb '06

Hello, is someone using Dovecot with Solaris on a T1 cpu ? I would like to hear about pros and cons. Martin --------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

1 0

[Dovecot] dovecot-LDA and fromwho-argument
by Björn Ketelaars 15 Feb '06

15 Feb '06

Hello, Im using dspam 3.6.3 in combination with Dovecot, procmail and Sendmail. Everything works fine but I want to replace procmail by dovecot-LDA. A few changes to dspam.conf results in a takeover by dovecot-LDA. Unfortunately this is where it goes awry; besides the d argument (user), dspam also supplies the f argument (fromwhom). The use of the f argument results in an error because dovecot-LDA does not know what to do with it. Is there an option to ignore the passing of 'fromwhom' from dspam? -- In individuals, insanity is rare; but in groups, parties, nations and epochs, it is the rule.

2 1

[Dovecot] Upgrade alpha5 to beta3
by Jan-Piet Mens 15 Feb '06

15 Feb '06

Hello, after an upgrade from alpha5 to beta3, every operation after login from an MUA returns ERROR: Could not complete request. Query: COPY 9 "Trash" Reason Given: (null) Both were built with ./configure --prefix=/usr/local \ --disable-ipv6 \ --with-passwd \ --with-passwd-file \ --with-ldap \ --with-ssl=openssl \ --with-ssldir=/etc/dovecot/ssl \ --localstatedir=/var \ --sysconfdir=/etc/dovecot \ --with-mysql \ --without-deliver \ --with-moduledir=/usr/local/lib/dovecot Just before `make install' on beta3, I removed content of /usr/local/lib/dovecot to ensure a clean install of the modules. My dovecot.conf contains base_dir = /var/run/dovecot/ protocols = imaps imap listen = * ssl_disable = no ssl_cert_file = /etc/dovecot/ssl/net.crt ssl_key_file = /etc/dovecot/ssl/net.key ssl_ca_file = /etc/dovecot/ssl/chain.pem ssl_cipher_list = ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM:!SSLv2 disable_plaintext_auth = yes syslog_facility = mail login_user = dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle = yes mail_debug = no default_mail_env = maildir:%h/Maildir namespace private { separator = / prefix = inbox = yes } mail_full_filesystem_access = no mail_log_prefix = "%Us %p %r [%u]: " protocol imap { mail_use_modules = yes mail_modules = /usr/local/lib/dovecot/imap login_greeting_capability = no } protocol pop3 { } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_verbose = yes auth_debug = yes auth default_with_listener { mechanisms = plain user = root passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot-auth-client/sock mode = 0666 } } } Can someone please help me? Thank & regards, -JP

2 16

[Dovecot] SASL und APOP
by Luca Bertoncello 14 Feb '06

14 Feb '06

Hi, all! I configured Dovecot to use many protocols. To do this, I wrote: mechanisms = plain digest-md5 cram-md5 apop ntlm Very strange, if I ask the capability, I get: CAPA TOP UIDL RESP-CODES PIPELINING STLS USER SASL PLAIN DIGEST-MD5 CRAM-MD5 NTLM . I can't understand why APOP is not written (but I can use it!) and why I can see SASL, that I didn't configure... How can I change these message so that I get PLAIN APOP DIGEST-MD5 CRAM-MD5 NTLM? Thanks a lot! -- _______________________________ Luca Bertoncello -Programmierung / Mailserver- IMS Internet-Media-Service GmbH Bärensteiner Straße 7 01277 Dresden Fon: +49 351 2112034 Fax: +49 351 2112020 email: bertoncello(a)internet24.de

2 2

[Dovecot] Message index corruption when using Thunderbird and Dovecot
by Reuben Pearse 14 Feb '06

14 Feb '06

Hi all, I have recently upgraded from UW-IMAP to Dovecot 1.0.beta3 on Redhat9. I migrated my mailbox to from Mbox to Maildir using the mb2md perl script, and created a procmail recipe file to get email arriving in the Maildir directories. However, when accessing my mailbox from Thunderbird (version 1.5), it occasionally mixes up the email header with the email content. I also occasionally get errors like this when clicking on old messages (ones that got converted as part of the mb2md script). The current command did not succeed. The mail server responded: Error in IMAP command UID: Invalid BODY[..] parameter: Missing '>' in '<16384.-15744>' However, if I click on the email item again, Thunderbird is then able to retrieve the message correctly. Can anyone provide some help with these problem. Thanks in advance -- Reuben Pearse Principal Technical Consultant reuben.pearse(a)pslconnect.com T +44 121 428 4440 F +44 121 428 3454 PSL The Old Sewing Factory 5a Greenfield Road Harborne Birmingham B17 0ED To find out more about our services please visit http://www.pslconnect.com -- CONFIDENTIALITY NOTICE The information contained in this e-mail is intended only for the confidential use of the above named recipient. If you are not the intended recipient or person responsible for delivering it to the intended recipient, you have received this communication in error and must not distribute or copy it. Please accept the sender's apologies, notify the sender immediately by return e-mail and delete this communication. Thank you.

3 3