June 2006 - dovecot - dovecot.org

[Dovecot] dovecot-1.0_beta9 : (auth) killed with signal 11
by Paul Harrington 24 Jun '06

24 Jun '06

I have just upgraded from courier to dovecot and things seem to be working okay (after a few problems getting shared folders working correctly). I notice the following error message in my logs:- Jun 23 11:17:32 calzone dovecot: child 1258 (auth) killed with signal 11 I am using the beta9 ebuild that is available from gentoo portage. I have followed the steps to try to get a core dump but it doesn't seem to be working. My config file is as follows:- =============================================================== protocols = imap imaps protocol imap { listen = 127.0.0.1:143 ssl_listen = *:993 } mail_drop_priv_before_exec = yes auth_debug = yes #mail_debug = yes default_mail_env = maildir:/var/spool/mail/virtual/users/%u auth default { mechanisms = plain digest-md5 cram-md5 userdb passwd-file { args = /etc/imap.passwd } passdb passwd-file { args = /etc/imap.passwd } } namespace private { separator = . prefix = Inbox. inbox = yes } namespace public { separator = . prefix = Allstar. location = maildir:/var/spool/mail/virtual/users/shared::CONTROL=/var/spool/mail/virtual/control/%u:INDEX=/var/spool/mail/virtual/control/%u } ================================================================== All users use UID/GID 5000. /etc/imap.passwd contains enteries such as:- paul:rMPY999gvr2kU:5000:5000::/var/spool/mail/virtual/users/paul Any advise on how I can produce a core dump and get this fixed? Thanks Paul

3 2

[Dovecot] LMTP revisited
by Glenn Leavell 24 Jun '06

24 Jun '06

During the early Dovecot LDA brainstorming discussions, there was some talk about the possibility of including an LMTP interface, and I've noticed that there's an "is it needed?" question about LMTP in Dovecot's TODO file. I'd like to put in a vote for LMTP, and I'm wondering if anyone else has a need for it. Specifically, I'd love an LMTP-enabled LDA that uses hard links when when delivering the same message to multiple recipients (I'm thinking Maildir files), as it would be a nice way to facilitate so-called Single Instance Storage. Glenn

7 12

[Dovecot] imap - mailbox in an inconsistant state
by Patrick Carney 24 Jun '06

24 Jun '06

Can anyone help me with this issue? The CEO of our company keeps getting IMAP time out errors and "mailbox is in an inconsistent state" messages. He uses Outlook 2003. There are errors on the server side. This is what it says: "Jun 19 08:08:34 burmail imap(ed): Corrupted binary tree file /home/ed/mail/.imap/INBOX/.imap.index.tree: UID to be inserted isn't hi gher than existing (2 <= 504)" Can someone tell me what that means?? I have been assigned to take over for a departed sys admin and have never used or administered Dovecot before. Thank You! Patrick

4 10

[Dovecot] Patch for rawlog.c
by Andreas Schulze 24 Jun '06

24 Jun '06

hello The homedirectories are stored as a relative path in my userdb One problem ocoures with rawlog: rawloging occures only if a directory $HOME/dovecot.rawlog exist. this is checked with lstat for me $HOME is always "username/". This is relative to /var/mail and works. in rawlog.c lstat should now check "username//dovecot.rawlog" which fails. lstat can check "/var/mail/username//dovecot.rawlog" or "./dovecot.rawlog" ( All checks test the existence of the same dir. ) I patched rawlog.c for me to force always the test of "./dovecot.rawlog" I think, this is no problem, because imap-auth / pop3-auth always change to the correct location. mayby I am wrong, because I'm _NOT_ dealing with mboxes, only maildirs. then you may discard this ... --- snip diff -Naur dovecot-1.0.beta9.orig/src/util/rawlog.c dovecot-1.0.beta9/src/util/rawlog.c --- dovecot-1.0.beta9.orig/src/util/rawlog.c 2006-02-26 11:05:31.000000000 +0100 +++ dovecot-1.0.beta9/src/util/rawlog.c 2006-06-23 08:37:57.684368256 +0200 @@ -21,6 +21,7 @@ #define TIMESTAMP_WAIT_TIME 5 #define TIMESTAMP_FORMAT "* OK [RAWLOG TIMESTAMP] %Y-%m-%d %H:%M:%S\n" +#define RAWLOG_DIRNAME "./dovecot.rawlog" static struct ioloop *ioloop; @@ -261,20 +262,14 @@ static void rawlog_open(bool write_timestamps) { - const char *home, *path; struct stat st; int sfd[2]; pid_t pid; - home = getenv("HOME"); - if (home == NULL) - home = "."; - /* see if we want rawlog */ - path = t_strconcat(home, "/dovecot.rawlog", NULL); - if (lstat(path, &st) < 0) { + if (lstat(RAWLOG_DIRNAME, &st) < 0) { if (errno != ENOENT) - i_warning("lstat() failed for %s: %m", path); + i_warning("lstat() failed for %s: %m", RAWLOG_DIRNAME); return; } if (!S_ISDIR(st.st_mode)) @@ -305,7 +300,7 @@ dec2str(getppid()))); ioloop = io_loop_create(system_pool); - rawlog_proxy_create(0, 1, sfd[0], path, write_timestamps); + rawlog_proxy_create(0, 1, sfd[0], RAWLOG_DIRNAME, write_timestamps); io_loop_run(ioloop); io_loop_destroy(&ioloop); ---- snap -- Andreas Schulze DATEV eG, Paumgartner Strasse 6-14, D - 90429 Nürnberg Abt. Internet- und Securitydienste Telefon : +49 911 276 2648 Telefax : +49 911 276 7892 Mobil : +49 172 8122883 E-Mail : andreas.schulze_at_datev.de

2 1

[Dovecot] courier imap features I miss in dovecot
by Andreas Schulze 24 Jun '06

24 Jun '06

hello, courier imap has two features: ##NAME: IMAP_MOVE_EXPUNGE_TO_TRASH:0 # # Set IMAP_MOVE_EXPUNGE_TO_TRASH to move expunged messages to Trash. This # effectively allows an undo of message deletion by fishing the deleted # mail from trash. Trash can be manually expunged as usually, and mail # will get automatically expunged from Trash according to IMAP_EMPTYTRASH. # # NOTE: shared folders are still expunged as usual. Shared folders are # not affected. # IMAP_MOVE_EXPUNGE_TO_TRASH=1 ##NAME: IMAP_EMPTYTRASH:0 # # The following setting is optional, and causes messages from the given # folder to be automatically deleted after the given number of days. # IMAP_EMPTYTRASH is a comma-separated list of folder:days. The default # setting, below, purges 7 day old messages from the Trash folder. # Another useful setting would be: # # IMAP_EMPTYTRASH=Trash:7,Sent:30 # # This would also delete messages from the Sent folder (presumably copies # of sent mail) after 30 days. This is a global setting that is applied to # every mail account, and is probably useful in a controlled, corporate # environment. # is this possible with dovecot too ? -- Andreas Schulze DATEV eG, Paumgartner Strasse 6-14, D - 90429 Nürnberg Abt. Internet- und Securitydienste Telefon : +49 911 276 2648 Telefax : +49 911 276 7892 Mobil : +49 172 8122883 E-Mail : andreas.schulze_at_datev.de

4 3

[Dovecot] different locations for different reals
by Arne Van Theemsche 24 Jun '06

24 Jun '06

Hi I've been reading a lot, but I think I'am confused about namespaces. We are planning a migration of our pshychical mail storage. This will mean that subfolders are moving from /home to /var/spool/mail. I was thinking, for the migrations of creating a realm. I would like that if a user logs in with his username, the old location is used, if the user logs in with username@REALM, the subfolders are to be searched in the new location, is this possible? Can I use a different mail location per realm? thx in advance Arne

2 1

[Dovecot] Large mbox files.
by Kevin Warren 24 Jun '06

24 Jun '06

I'm very sorry if this is a faq. I've spent considerable time reading documentation and doing Google searches to no avail...and the mailing list archive isn't searchable as far as I can tell. Anyway, the question: When I try to open a large mbox file from Squirrel Mail I receive the following Dovecot error: Jun 23 10:47:55 jetta dovecot: [ID 107833 mail.error] IMAP(kevin): file mbox-sync-rewrite.c: line 400 (mbox_sync_read_and_move): ass ertion failed: (need_space == (uoff_t)-mails[idx].space) Jun 23 10:47:56 jetta dovecot: [ID 684838 mail.error] child 28535 (imap) killed with signal 6 Not sure what other information you will need. (There's no posting guideline for the mailing list) Here's my guess: Dovecot version: 1.0.beta9 OS version: Solaris x86 v10 I'm guessing a listing of non-default values in dovecot.conf would be useful too: $ grep -vE "^ *#" dovecot.conf | grep -E "^ *[a-z\}]" ssl_listen = *:993 first_valid_uid = 100 protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)example.com } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } plugin { }

3 2

[Dovecot] dovecot and thunderbird
by Mark Davies 24 Jun '06

24 Jun '06

We've been using dovecot for a while now (currently 1.0beta7) and it works nicely. We have just one reoccuring problem: When using thunderbird as the imap client sometimes when messages are moved from the inbox to other folders (including Trash) they shortly thereafter reappear in the inbox - this can happen multiple times to the same message. We have multiple namespaces set up so that inbox is mbox format in ~/.poffice/username and other folders are maildir in ~/Maildir - both of these are on NFS. Indexes are on local storage. The problem only seems to happen with thunderbird. kmail, mac mail, outlook, pine all work fine. If we effectively move a user so that their inbox is also maildir then the problem doesn't happen. The inbox being mbox format is for historic reasons and medium to long term this should change to maildir but in the interim can anyone see anything different that thunderbird does to other imap clients that might be tickling an underlying bug? cheers mark

3 3

[Dovecot] beta9 (auth) killed with signal 11 - backtrace
by Paul Harrington 23 Jun '06

23 Jun '06

Further to my previous email I managed to find the core file. Version: 1.0.beta9 OS: Gentoo x86 Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. (gdb) bt full #0 0xb7d575ba in strcasecmp () from /lib/tls/libc.so.6 No symbol table info available. #1 0x0805b091 in passdb_get_credentials () No symbol table info available. #2 0x00000000 in ?? () No symbol table info available.

1 0

[Dovecot] 2nd Question on v1.0 setup and maildir
by Patrick Carney 23 Jun '06

23 Jun '06

_____ From: Patrick Carney [mailto:patrick@castandcrew.com] Sent: Thursday, June 22, 2006 8:55 AM To: 'dovecot(a)dovecot.org' Subject: Question on v1.0 setup and maildir Hello all. I appreciate the responses to my problem on v0.99.14. Thank you all. We have built a new server running version 1.0-0_15.beta9.el4. The mail delivery agent is sendmail. We seem to have gotten it up fairly easily. But we have one problem. We are using the maildir feature instead of mbox and when ever mail gets delivered, it is not sending it to the \maildir\new folder. It seems to be dumping it in the root of the maildir directory, thus when a client checks for email, it appears nothing is there. Here is a sample from our config. Any suggestions will be much appreciated. Forgive me if this is elementary question, but I am new to dovecot. ## Mailbox locations and namespaces ## # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. 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/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = maildir:/home/%u/Maildir # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # 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. default_mail_env 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. #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 # default_mail_env, 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 or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_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 ##

4 4