February 2006 - dovecot

[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

[Dovecot] Re: Mail.app help
by Roger Weeks 14 Feb '06

14 Feb '06

I'm wondering if this is a version issue with Mail.app? Are you on OS X 10.3 or 10.4? The reason I ask is that we also migrated from Courier IMAP to Dovecot 1.0alpha5 and then beta3, and we did not have this problem with Mail.app that either of you are describing. I did have to remove the "INBOX." prefix from my Mail.app configurations. I also renamed all of the existing folders in my Maildir from INBOX.foldername to .foldername, because after removing the "INBOX." prefix Mail.app could not see them. Before I renamed all of the existing folders and changed the prefix in Mail.app, I had also tried setting up alternate namespaces as described in the wiki documentation for converting from Courier, but that did not seem to work. Mail.app and Thunderbird clients could not see their IMAP folders with the courier-style namespace configuration. -- Roger J. Weeks Systems & Network Administrator Mendocino Community Network On Feb 14, 2006, at 8:45 AM, dovecot-request(a)dovecot.org wrote: > Date: Tue, 14 Feb 2006 08:44:53 -0800 > From: Steve Pellegrin <steve(a)convoglio.com> > Subject: Re: [Dovecot] Mail.app help > To: Mike Garfias <mike(a)garfias.org> > > Sorry to respond so late to this, perhaps my experience will help. > > I believe that Mike's problem is caused by weird behavior in > Mail.App. I had the same issue after switching from Courier IMAP to > Dovecot 1.0beta2. (Courier requires the INBOX prefix). > > I only experienced this problem for folders that I defined myself. In > other words, the "standard" Sent, Trash and so on were OK. What I > found was that if I had a custom folder, call it Dovecot, and a rule > that directed mail list messages into that folder, Mail.App would > insist on creating INBOX.Dovecot, even though .Dovecot already > existed. > > It's as if Mail.App had internalized the INBOX prefix in some secret > place and would not let go of it even though I changed the prefix > setting to be empty. > > My solution was to delete my mail account, shut down Mail.App, re- > launch it, and recreate the mail account. Now, everything works as > expected. > > -Steve

2 3

[Dovecot] Dovecot-1.0.beta1: New mail sometimes fails to appear
by Tom Alsberg 14 Feb '06

14 Feb '06

Hi there... Having updated to 1.0.beta1, I for a while thought a bad bug with IDLE handling that caused new mail in INBOX not to appear when using Mozilla Thunderbird has been solved. Although I can not reproduce one kind of problem anymore, after a short while it again appears that one does not always see one's new mail with Thunderbird. I can not consistently reproduce the bug, but from some network captures it indeed appears that sometimes Thunderbird has (in one of its connections to the server) INBOX SELECTed and IDLE on it, new mail arrives, but 10 minutes afterwards it was still not sent an EXISTS message. Initially the symptoms appeared to suggest that something really bad happened to the index files, but I tried INDEX=MEMORY and that did not help much. Thunderbird using multiple connections to the server does of course only make debugging more difficult. But it appears that without multiple connections, one has to constantly cycle around SELECTing to get notified on more than one mailbox, so that may justified. I am a bit lost on this now, and would appreciate some ideas. Although there were several related bugs I noticed in Thunderbird 1.0, it appears that they are gone in 1.5, and yet now it really seems Dovecot is doing something wrong here. Attached is the configuration file I use for the testing installation of Dovecot 1.0.beta1 (somebody tell me if you see something wrong there). The mailbox arrangement is as follows, right now (until we have a better way): * INBOX in /var/mail/%u * most mailboxes in ~/imap.maildir/... as maildirs. * mboxes in ~/imap.mbox/... accessible as #imap.mbox/... * the mbox:~/mail/ is for when namespaces are not used - now there are so it should not be relevant Except for myself, and one test account I have, I have two guinea-pigs using it (who are well aware that it is still under development and that it will break once in a while) and reporting problems to me. Vaguely (since I can't figure the exact reasons), the symptom can be described as follows: When using Mozilla Thunderbird to access mail, new mail arrives to INBOX (mbox:/var/mail/%u), but is sometimes not seen for a long while after it arrives. Sometimes the first (or first few) message arriving appears, but then no new messages appear, and sometimes everything works right and immediately new mail is seen. However whenever (according to Thunderbird) something changes in the mailbox, the mailbox is seen up-to-date as it really was at that time. Thanks, any help appreciated, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further. # Dovecot IMAP server configuration at CS.HUJI ############################################## # # $Id$ # GENERAL PARAMETERS: ##################### # Base directory where to store runtime data: base_dir = /var/run/dovecot # Protocols we want to be serving: protocols = imap pop3 # IP or host address where to listen in for connections: listen = * ssl_disable = yes # LOGIN PROCESSES: ################## # Directory for authentication sockets: #login_dir = /var/run/dovecot/login # chroot login process to the login_dir: #login_chroot = yes # User to use for the login process: login_user = nobody # Maximum process size in megabytes: #login_process_size = 16 # Have each login be processed in its own process: #login_process_per_connection = yes # Number of login processes to create: #login_processes_count = 3 # Maximum number of extra login processes to create: #login_max_processes_count = 128 # Maximum number of connections allowed in login state: #login_max_logging_users = 256 # Greeting message for clients: login_greeting = Dovecot mail access server at CS.HUJI ready. # MAIL PROCESSES: ################# # Maximum number of running mail processes: #max_mail_processes = 1024 # Show more verbose process title (in ps): verbose_proctitle = yes # Valid UID range for users: first_valid_uid = 10 #last_valid_uid = 0 # Valid GID range for users: #first_valid_gid = 1 #last_valid_gid = 0 # Extra groups for mail processes: #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed: #valid_chroot_dirs = # Default chroot directory for mail processes: #mail_chroot = # Default MAIL environment to use when it's not set: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # NAMESPACES: ############# namespace private { separator = / prefix = "" location = maildir:~/imap.maildir/ } namespace private { separator = / prefix = "#imap.mbox/" location = mbox:~/imap.mbox/:INBOX=/var/mail/%u inbox = yes } # MAIL STORE: ############# # Space-separated list of fields to initially save into cache file: #mail_cache_fields = # Space-separated list of fields to never save into cache file: #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command: #mailbox_idle_check_interval = 30 # Whether to allow full filesystem access to clients: #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name: #mail_max_keyword_length = 50 # Whether to save mails with CR+LF instead of plain LF: #mail_save_crlf = no # Whether to use mmap to access mail files: #mail_read_mmaped = no # Whether to disable mmap at all: mmap_disable = yes # Whether to disable write to mmap: #mmap_no_write = no # Locking method for index files: lock_method = dotlock # Whether to list only directories in LIST command: maildir_stat_dirs = yes # Whether to copy mail to other folders using hard links: #maildir_copy_with_hardlinks = no # Locking methods to use for locking mbox: mbox_read_locks = dotlock mbox_write_locks = dotlock # Maximum time in seconds to wait for lock (all of them): mbox_lock_timeout = 300 # Timeout to overwrite dotlock files if mailbox isn't modified: mbox_dotlock_change_timeout = 30 # Whether to read only appended data on change (unless corrupt): #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but no full syncs with SELECT, EXAMINE, # EXPUNGE, or CHECK: #mbox_very_dirty_syncs = no # Whether to delay writing mbox headers until doing a full write sync: #mbox_lazy_writes = yes # umask to use for mail files and directories: umask = 0077 # Whether drop all privileges before exec of mail process: #mail_drop_priv_before_exec = no # Maximum mail process size in megabytes: #mail_process_size = 256 # Log prefix for mail processes: mail_log_prefix = "%Us(%u): " # IMAP SPECIFIC SETTINGS: ######################### protocol imap { # Login executable location: #login_executable = /usr/local/dovecot/libexec/dovecot/imap-login # IMAP executable location: #mail_executable = /usr/local/dovecot/libexec/dovecot/imap # Maximum IMAP command line length in bytes: #imap_max_line_length = 65536 # Suypport for dynamically loadable modules: #mail_use_modules = no #mail_modules = /usr/local/dovecot/lib/dovecot/imap # Whether to send IMAP capabilities in greeting message: login_greeting_capability = yes # Workarounds for various client bugs: imap_client_workarounds = outlook-idle netscape-eoh } # POP3 SPECIFIC SETTINGS: ######################### protocol pop3 { # Login executable location: #login_executable = /usr/local/dovecot/libexec/dovecot/pop3-login # POP3 executable location: #mail_executable = /usr/local/dovecot/libexec/dovecot/pop3 # Whether to not update recent/seen flags in POP3 sessions: #pop3_no_flag_updates = no # Whether to support deprecated LAST command: #pop3_enable_last = no # POP3 UIDL format to use: #pop3_uidl_format = %08Xu%08Xv # Support for dynamically loadable modules #mail_user_modules = no #mail_modules = /usr/local/dovecot/lib/dovecot/pop3 # Workarounds for various client bugs: pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } # AUTHENTICATION PROCESSES: ########################### # Authentication executable location: #auth_executable = /usr/local/dovecot/libexec/dovecot/dovecot-auth # Maximum authentication process size in megabytes: #auth_process_size = 256 # Authentication cache size in kilobytes: #auth_cache_size = 0 # Time to live in seconds for cached data: #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms: #auth_realms = # Default realm/domain to use if none was specified: #auth_default_realm = # List of allowed characters in username: #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789.-_@ # Username character translation before it's looked up in database: #auth_username_translation = # Whether to disable plaintext authentication disable_plaintext_auth = no # More verbose authentication logging: auth_verbose = yes # Even more verbose authentication logging for debugging purposes: auth_debug = yes auth default { # Space separated list of wanted authentication mechanisms mechanisms = plain # Password database specification: passdb pam { } # User database specification: userdb passwd { } # User to use for the authentication process: user = root # Directory where to chroot the process: #chroot = # Number of authentication processes to create: #count = 1 # Whether to require a valid SSL client certificate for # authentication: #ssl_require_client_cert = no }

5 28

[Dovecot] Mail.app help
by Mike Garfias 14 Feb '06

14 Feb '06

I'm having a problem with Mail.app and imap folders. I've got a new install of dovecot 1.0beta2, and am only experiencing this problem with Mail. Mutt works as expected, as well as thunderbird. When I create a folder using Mail.app, it is written to ~/Maildir/.INBOX.newfolder, which would be fine, if I wasn't telling everything that I wanted no prefixes. If I move that folder to ~/Maildir/.newfolder, Mail.app can no longer see it, but mutt and thunderbird can. Thunderbird _CAN_ see the folders created as .INBOX.Folder, and even shows it as a subfolder of my inbox, but Mutt completely refuses to see it. Any ideas what I'm doing wrong here?

4 4