- dovecot - dovecot.org

[Dovecot] Thunderbird trouble with Dovecote and dbox
by Hannes Dorbath 27 Jan '08

27 Jan '08

Hi, I'm new to Dovecot -- migrating from Cyrus. Version and config: # 1.1.beta14: /etc/dovecot/dovecot.conf protocols: imaps login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: dbox:/data/mail/%u auth default: passdb: driver: pam args: * userdb: driver: passwd Linux 2.6.22-gentoo-r10 x86_64 GNU/Linux I have chosen dbox as mailbox format as it is claimed to be the best performing -- and performance is the reason I'd like to migrate away form Cyrus. I'm aware that dbox might not be 100% mature, but I'm good at doing backups. Anyway, so far I have the following problems: - Greyed out Inbox After creating a new user and connecting to that account with Thunderbird the first time, the INBOX folder is greyed out and in italic. Restarting Thunderbird 3-4 times seems to fix the problem. Google suggests that other people have seen the same, but they never found a solution. - After creating sub folders they are not displayed, I need to manually subscribe to them after creation. - When "Trash" contains folders, Thunderbird is unable to "Empty Trash". While the folder is removed from Thunderbird's folder tree, it's there again after a restart of Thunderbird. - Deleted folders are never deleted from the file system. I'm not sure if this is intended with dbox. - Moving folders via drag & drop does not work, it just does nothing. So basically nothing besides reading existing mails seems to work reliable. My basic questions now is, are those problems related to dbox, or to Dovecot and Thunderbird in general? -- Best regards, Hannes Dorbath

2 3

[Dovecot] User-specific mail_location using passwd database
by Maxime Brugidou 26 Jan '08

26 Jan '08

current version : 1.0.rc15 Hi, I would just like to know if it's possible to have different mail locations for different UNIX users, using pam authentication and the passwd userdb. We also have some virtual users using an SQL db. The current config is : auth default: username_translation: %@ verbose: yes debug: yes passdb: driver: pam passdb: driver: passwd passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf Then we can only modify mail locations for virtual users on the sql userdb. But how could we change it for real users ? Thanks for help, -- Maxime Brugidou

3 4

[Dovecot] Dovecot LDA (deliver) stopped working
by falz 26 Jan '08

26 Jan '08

Hello, One day a week or so ago, a server that's Postifx w/ Local users, dovecot w/ LDA decided to stop working. The only thing that stopped is the LDA portion, the rest all works fine. I also posted to the postfix mailing list yesterday but wasn't able to debug any further. Here's the situation: if I use mailbox_command to point to deliver, postfix will always put the message in the deferred queue. However, if I run deliver from the command line, it works fine. I've recompiled Dovecot and Postfix cleanly and reinstalled a few times to ensure permissions are OK. It's not a virtual setup, so I do NOT have setuid root on the deliver binary. Postfix people suggested placing a wrapper script for mailbox_command, which I did, and have it log to a text file, so I do know that deliver is being called. However, although I have LDA debug logging on, and it DID log prior to this, when postfix supposedly calls deliver, dovecot does NOT log anything. It DOES however log if I call deliver from any account (root or not) from the command line (ls / | /path/to/deliver -d localaccountname). Any way I can debug this further? I would assume that deliver would log something even if it's called, but it appears that it does not. My postfix related details are here: http://marc.info/?l=postfix-users&m=120119147917409&w=2 I followed the postfix/lda wiki (http://wiki.dovecot.org/LDA/Postfix) when setting it up, and it worked perfectly for months. I did indeed only have to change mailbox_command and it worked (I'm also using sasl auth, but that should be unrelated). Obviously something happened on my system, but I would assume recompiling/reinstalling would reset things. Nothing in the config files for postfix or dovecot changed, from what I can see, as generally I am the only one making changes. Thanks, --falz

3 7

[Dovecot] Count breaks socket
by Marc Perkel 26 Jan '08

26 Jan '08

If I use the socket option I can't use the count option to create more authentication processes. I get this error. Thanks in advance. dovecot: Jan 25 06:57:04 Error: auth(default): Socket already exists: /var/run/dovecot/auth-client auth default { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/exim/control/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/exim/control/vmail/passwd.%d } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } client { path = /var/run/dovecot/auth-client mode = 0666 } } # Number of authentication processes to create # count = 10 }

3 3

[Dovecot] dovecot HEAD, assertion failed after 7193:e5af14239137 changeset
by Daniel 26 Jan '08

26 Jan '08

Hi! Using HEAD, and after the 7193:e5af14239137 changeset (Store physical message sizes also to dovecot-uidlist if needed.) I'm getting this: (gdb) bt full #0 0x0a0a80dd in kill () from /usr/lib/libc.so.41.0 No symbol table info available. #1 0x0a0e04a7 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 p = (struct atexit *) 0x84992000 cleanup_called = 0 mask = 4294967263 #2 0x1c0746cd in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x3c000100 "file %s: line %d (%s): assertion failed: (%s)", args=0xcfbee4a4 "ĐA") at failures.c:423 backtrace = 0x1c0739f1 ";\003u\vÇ\003" #3 0x1c0741cb in i_panic (format=0x3c000100 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:195 No locals. #4 0x1c029a89 in maildir_mail_get_physical_size (_mail=0x7ee27428, size_r=0xcfbee598) at maildir-mail.c:361 mbox = (struct maildir_mailbox *) 0x7ee22028 data = (struct index_mail_data *) 0x7ee2749c st = {st_dev = -809573008, st_ino = 671359322, st_mode = 3485394200, st_nlink = 134504406, st_uid = 2264813824, st_gid = 671359313, st_rdev = -809573016, st_lspare0 = -809573008, st_atimespec = {tv_sec = 671359322, tv_nsec = 3690}, st_mtimespec = {tv_sec = 0, tv_nsec = 0}, st_ctimespec = {tv_sec = 0, tv_nsec = 0}, st_size = 2883503177569592696, st_blocks = 19440464480, st_blksize = 3485394312, st_flags = 134504965, st_gen = 2264813824, st_lspare1 = 2128748960, __st_birthtimespec = {tv_sec = 671359313, tv_nsec = -809573016}, st_qspare = {20665263472, 3485394280}} path = 0x0 #5 0x1c04a120 in mail_get_physical_size (mail=0x0, size_r=0xcfbee598) at mail.c:100 No locals. #6 0x0804672b in quota_alloc (ctx=0x7d5ec5c0, mail=0x7ee27428) at quota.c:777 size = 3842 #7 0x080465cb in quota_try_alloc (ctx=0x7d5ec5c0, mail=0x7ee27428, too_large_r=0xcfbee5fb) at quota.c:725 size = 3842 ret = 0 #8 0x08049d2e in quota_check (t=0x876b3300, mail=0x7ee27428) at quota-storage.c:148 qt = (struct quota_transaction_context *) 0x7d5ec5c0 ret = 0 too_large = false #9 0x1c04c30b in mailbox_copy (t=0x0, mail=0x7ee27028, flags=0, keywords=0x0, dest_mail=0x0) at mail-storage.c:741 No locals. #10 0x1c0116e6 in fetch_and_copy (client=0x86fe3180, destbox=0x7ee22028, t=0x876b3300, search_args=0x84d55068, src_uidset_r=0x52fe, copy_count_r=0x0) at cmd-copy.c:66 ---Type <return> to continue, or q <return> to quit--- search_ctx = (struct mail_search_context *) 0x876b3700 src_trans = (struct mailbox_transaction_context *) 0x876b3500 keywords = (struct mail_keywords *) 0x0 keywords_list = (const char * const *) 0x87c890e8 mail = (struct mail *) 0x7ee27028 copy_count = 1 srcset_ctx = {str = 0x83e872f0, first_uid = 0, last_uid = 4294967295} src_uidset = (string_t *) 0x83e872f0 ret = 1 #11 0x1c011899 in cmd_copy (cmd=0x84d55028) at cmd-copy.c:136 client = (struct client *) 0x86fe3180 storage = (struct mail_storage *) 0x890a9c28 destbox = (struct mailbox *) 0x7ee22028 t = (struct mailbox_transaction_context *) 0x876b3300 search_arg = (struct mail_search_arg *) 0x84d55068 messageset = 0x876d90d0 "3691:3693,3690" mailbox = 0x876d90e0 "Trash" src_uidset = 0xc "ČÎ\a*,äžĎXäžĎ" msg = 0x0 sync_flags = 0 imap_flags = 0 copy_count = 469853808 uid_validity = 469853899 uid1 = 2213048760 uid2 = 2299171840 ret = 9 #12 0x1c015192 in cmd_uid (cmd=0x84d55028) at cmd-uid.c:26 command = (struct command *) 0x52fe cmd_name = 0x876d90c8 "COPY" #13 0x1c0160f2 in client_command_input (cmd=0x84d55028) at client.c:536 client = (struct client *) 0x86fe3180 command = (struct command *) 0x52fe #14 0x1c015fc9 in client_command_input (cmd=0x84d55028) at client.c:585 client = (struct client *) 0x86fe3180 command = (struct command *) 0x52fe ---Type <return> to continue, or q <return> to quit--- #15 0x1c01614f in client_handle_next_command (client=0x86fe3180, remove_io_r=0xcfbee7db) at client.c:601 size = 36 #16 0x1c0161f5 in client_handle_input (client=0x86fe3180) at client.c:636 _data_stack_cur_id = 3 remove_io = false handled_commands = false #17 0x1c0162b6 in client_input (client=0x86fe3180) at client.c:674 cmd = (struct client_command_context *) 0x24 bytes = 36 #18 0x1c07adb4 in io_loop_handler_run (ioloop=0x86bdf0e0) at ioloop-kqueue.c:149 ctx = (struct ioloop_handler_context *) 0x89236030 events = (struct kevent *) 0x86bdf360 tv = {tv_sec = 3, tv_usec = 424767} ts = {tv_sec = 3, tv_nsec = 424767000} io = (struct io_file *) 0x86bdf360 t_id = 2 ret = 1 i = 0 #19 0x1c07a3c9 in io_loop_run (ioloop=0x86bdf0e0) at ioloop.c:301 No locals. #20 0x1c01ccd4 in main (argc=1, argv=0xcfbee900, envp=0xcfbee908) at main.c:293 No locals. Thanks! Daniel

2 4

[Dovecot] Capturing credentials for imap sync
by Master Abi 26 Jan '08

26 Jan '08

Hi List All the imap sync apps I could find requires the username /password credentails to be known before a sync occurs. I have Dovecot using ldap acting as a nearline backup mail server to MS Exchange. Every hour imapsync syncs mail between Exchange and Dovecot. This all works fine becuase the users credentials are known, but when new users are added I would like the process to work seemless like this: The user is added to the Active Directory. The mail client is configured with 2 accounts with identical credentials, one of which is connected to Dovecot. When the new client connects to dovecot, the credentials are captured and stored so that imapsync can use it. This If there is another way this can be done with dovecot, could I please be enlighten. I have read the doco on migration but I am not quite migrating but more replicating. Thank you

3 2

[Dovecot] symbolic links to root node
by Martin Preen 25 Jan '08

25 Jan '08

Hello, I have a question about the way Dovecot limits file system access. Currently we're using Dovecot 1.0.5 (Solaris 10). In some cases users have a symbolic link like "z: -> /" in their mail directory. As a result there are log entries like Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz): stat(/home/xyz/.wine/dosdevices/c:/windows/profiles/xyz/.../z:/proc/28381/root/proc/28381/.../root/proc/28381/Player/#SharedObje Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz): x) failed: File name too long We know the reason (the links are create by Wine) but unfortunately we cannot get rid of them. Is there something I can do (these links should be ignored) ? Or is it a bug ? Greetings. Martin --------------------------------------------------------------- Martin Preen, Universität Freiburg, Institut für 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

3 3

[Dovecot] New server error
by Anne Wilson 25 Jan '08

25 Jan '08

I'm setting up a replacement mail server on a CentOS 5.1 box. The dovecot version is 1.0.rc15. 'dovecot -n' returns # /etc/dovecot.conf 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 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 auth default: passdb: driver: pam userdb: driver: passwd I can telnet localhost 143 and log in. I have given kmail the address of the server and an Inbox has been created, but no option to create sub-folders. If I attempt to send a message kmail freezes. Clearly something's wrong. I am using configuration files from the old server, modified only to the new server details. I have alias and transport hashes. What else should I be looking at? Thanks Anne

7 11

[Dovecot] dovecot + antispam + sendmail
by Anil 25 Jan '08

25 Jan '08

Whats a good antispam solution? I am using sendmail and dovecot 1.1. I came across dovecot's antispam plugin, but it seems it does not support 1.1 yet. I am also looking for something non-perl based. I am already doing some greylisting with sendmail milter. Any other good suggestions? If not, I guess I might have to downgrade back to 1.0 dovecot. Thanks

7 9

[Dovecot] Is there a way to limit multiple POP3 connections?
by patrickm 25 Jan '08

25 Jan '08

Hi all, Please correct me if I'm going about this the wrong way. We currently have a 3 system Mail server set up - two machines are the load balanced frontends running Dovecot and Postfix, and the third machine is our NFS. Over the past 4 months or so, I've tweaked and optimized our mail servers, and we receive roughly 3 million emails a day combined through this setup. Sometimes, the IO Wait is horrible on the load balanced servers - it can get up into the 80-90% range sometimes - it's usually when a lot of email is being passed, or there are a lot of POP3 and IMAP connections. One item which I believe to be hurting I/O performance is the fact I used a RAID 10 setup using SATA II drives on an LSI Logic SATA I controller, in 32 bit mode. Until we rebuild our mail setup (which may be another year down the road), I want to make sure these servers are optimized to the fullest just in case we get heavy I/O usage, it doesn't slow down if at all possible. One thing I noticed is that when issuing a 'ps aux | grep -i pop' or 'ps aux | grep -i imap' I see the same username 2,3,4,5 times, sometimes more. When issuing a 'tail -f /var/log/dovecot.log' I notice that some users log into POP3 every 3 seconds, sometimes sooner. Without upsetting the customer, is there anything I can do on my end to disallow people logging into POP3 multiple times at once? Any tips on this is very much appreciated. Thanks in advance. Patrick

7 16