- dovecot - dovecot.org

Re: [Dovecot] Dovecot & SquirrelMail
by admin＠downend.org 15 Aug '05

15 Aug '05

Update On the Following: Hey Everyone got some good news and some wierd things... Firstly, netstat -ltnp | grep ':143' -- does not show an output telnet localhost 143 -- Cannot Connect Secondly, I have no firewall installed. Thirdly, If I type "mail" as the user in SSH I can read my mail and I can send mail from other servers... which is strange considering it cannot connect Fourthly, /etc/init.d/dovecot start (Just start) -- Does not show an output. pidof dovecot -- Does not state a process for dovecot Any ideas what I should do... or anyone knows the reason. I checked mail.err and comes up with the following: Aug 14 07:15:04 aries imap-login: Can't load private key file /etc/ssl/private/dovecot.pe.................. and of course because of the above SquirrelMail cannot detect the Dovecot Imap Server. I would appreciate some step to step guidience as it is getting important. I also appreciate the people who have helped me and thank you for not being cocky... or big headed... Once dovecot is running I won't be touching it for a very long time :) Regards, Mark Smith Quoting Allen Parker <infowolfe(a)gmail.com>: > On 8/14/05, admin(a)downend.org <admin(a)downend.org> wrote: > > Hi I am back thought I should start a new mail... since i lost track of > > previous. Anyways, > > > > Does Dovecot require courier-authdaemon or whatever it is called to run? > > When running the following i recieve the following output should I kill > inet > > from 143 or not. > > > > aries:/etc/init.d# netstat -ltnp | grep ':143' > > tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN > > 24715/inetd > > more than likely, you should check in your distribution's inetd.conf > (under xinetd, normally /etc/xinetd.d/ is where configurations are > kept) and remove any reference to an imap server in there since you're > not launching dovecot from inetd... you should be seeing errors like > "unable to bind to port" in your syslog coming from dovecot.. (i > personally don't use inetd for launching things... but to each their > own) > > hope this helps > > > I am recieving the same response with the dovecot init file: > > > > aries:/etc/init.d# /etc/init.d/dovecot > > aries:/etc/init.d# /etc/init.d/dovecot > > > > aries:/etc/init.d# /etc/init.d/dovecot restart > > aries:/etc/init.d# > > > > > > There is no output possible because of inet? > > Any Help will be great! > > Thanks! > > > > > -- > ________________________________________ > To avoid being added to my spam filter: > 1. Utilize list replies unless otherwise requested. > 2. If you DO send me a personal email, use english. > 3. HTML isn't cute. It belongs on the web, not in my inbox. >

4 4

[Dovecot] Error message? less messages
by Jakub Tencl 15 Aug '05

15 Aug '05

Hello, I was upgrade dovecot and after installing i had see this message: Starting mail server: dovecotWarning: Ignoring deprecated 'login' section handling. Use protocol imap/pop3 { .. } instead. Some settings may have been read incorrectly. Warning: Ignoring deprecated 'login' section handling. Use protocol imap/pop3 { .. } instead. Some settings may have been read incorrectly. What is it? I red the dovecot.conf and i thing there isn't some bad or there is? Please could you advice me? And on the server when MS Outlook Express download the messages, on the local computer/station have a less messages then on the server, how can be possible? When i create account on the station again it is good for this time. Thanx for reply Jakub Tencl

1 0

[Dovecot] 1.0-test80
by Timo Sirainen 15 Aug '05

15 Aug '05

http://dovecot.org/test/ If nothing new comes up in a few days, this will become the first release in 1.0alpha series. Authentication code got some larger changes, so something might be broken in it. - inotify patch by Johannes Berg - Send untagged FLAGS / PERMANENTFLAGS replies if keywords list changed. - Don't even open mbox file when changing flags and mbox_lazy_writes=yes - Fixed assert crash in maildir syncing if another process was renaming the maildir files - Dovecot went to infinite loop with certain kinds of FETCH commands - mbox: Don't crash in some situations with broken X-UID headers - Preserve TZ environment so timezones work in AIX - some other fixes

1 0

[Dovecot] After Debian testing upgrade, dovecot doesn't work
by Martin Marques 15 Aug '05

15 Aug '05

Today I upgraded my Debian testing server (just personal testing server), and one of the updates was dovecot-common and dovecote-imapd. I passed through the dovecot.conf file changing things so that I would have similar features as before, and everything looked OK. Now, after restarting, and all, I try to connect the the imap server with my user acount, and it passes OK, but when I try to see my INBOX folder the conection gets reset, and I have this in the mail.log file: Aug 11 15:20:53 bugs dovecot: imap-login: Login: martin [xxx.xxx.xxx.xxx] Aug 11 15:20:54 bugs dovecot: child 8085 (imap) killed with signal 10 I erased the .imap folder in ~martin/mail/ but with no luck. What happened, and how can I fix this. bugs:/etc/dovecot# dpkg -l | grep dovecot ii dovecot-common 0.99.20050712-2 secure mail server that supports mbox and ma ii dovecot-imapd 0.99.20050712-2 secure IMAP server that supports mbox and ma ii dovecot-pop3d 0.99.20050712-2 secure POP3 server that supports mbox and ma -- 11:55:01 up 155 days, 1:49, 3 users, load average: 0.12, 0.72, 0.86 ----------------------------------------------------------------- Lic. Martín Marqués | select 'mmarques' || '@' || 'unl.edu.ar' Centro de Telematica | DBA, Programador, Administrador Universidad Nacional del Litoral -----------------------------------------------------------------

4 4

[Dovecot] Assertion failure in mail-index-transaction.c
by Todd Burroughs 15 Aug '05

15 Aug '05

This just started happening with the current CVS version (2005-07-23). The "user" is a monitoring tool that we use called Sitescope. It has been monitoring dovecot for a long time and I've never seen an error before this. Deleting the .imap directory seems to have resolved the problem. This did not start until several hours into running the new version. dovecot: Jul 25 19:45:38 Error: 16590 IMAP(sitescope): file mail-index-transaction.c: line 588 (mail_index_update_flags_range): assertion failed: (seq1 <= seq2 && seq1 > 0) dovecot: Jul 25 19:45:39 Error: child 16590 (imap) killed with signal 6 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff2c8 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x00004207 in ?? () No symbol table info available. #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 No symbol table info available. #6 0x0809acca in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x4207 <Address 0x4207 out of bounds>) at failures.c:374 No locals. #7 0x0809b0e4 in i_panic ( format=0x80a7a8c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 No locals. #8 0x08083411 in mail_index_update_flags_range (t=0x80d2320, seq1=0, seq2=0, modify_type=MODIFY_ADD, flags=128) at array.h:99 rec = Variable "rec" is not available. (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff2c8 in ?? () #2 0x00000006 in ?? () #3 0x00004207 in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809acca in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x4207 <Address 0x4207 out of bounds>) at failures.c:374 #7 0x0809b0e4 in i_panic ( format=0x80a7a8c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x08083411 in mail_index_update_flags_range (t=0x80d2320, seq1=0, seq2=0, modify_type=MODIFY_ADD, flags=128) at array.h:99 #9 0x0806e262 in mbox_sync_read_index_syncs (sync_ctx=0xbffff710, uid=1, sync_expunge_r=0xbffff58c) at mbox-sync.c:213 #10 0x0806ec1e in mbox_sync_loop (sync_ctx=0xbffff710, mail_ctx=0xbffff680, partial=Variable "partial" is not available. ) at mbox-sync.c:1070 #11 0x080704c0 in mbox_sync (mbox=0x80c4bc0, flags=Variable "flags" is not available. ) at mbox-sync.c:1441 #12 0x08071379 in mbox_storage_sync_init (box=0x80c4bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mbox-sync.c:1766 #13 0x0808f221 in mailbox_sync_init (box=0x0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mail-storage.c:334 #14 0x0805ed08 in imap_sync_nonselected (box=0x80c4bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at imap-sync.c:171 #15 0x08058166 in _cmd_select_full (cmd=0x80beba8, readonly=0) at cmd-select.c:39 #16 0x080582f1 in cmd_select (cmd=0x80beba8) at cmd-select.c:92 #17 0x0805997b in _client_input (context=0x80beb68) at client.c:334 #18 0x080a029a in io_loop_handler_run (ioloop=0x80bd9b0) at ioloop-poll.c:184 #19 0x0809f8c9 in io_loop_run (ioloop=0x80bd9b0) at ioloop.c:218 #20 0x08060847 in main (argc=1, argv=0xbffffa24, envp=0xbffffa2c) at main.c:229 (gdb) p seq1 $1 = 0 (gdb) p seq2 $2 = 0 (gdb) p *t $3 = {refcount = 1, view = 0x80d0120, appends = {buffer = 0x0, element_size = 0}, first_new_seq = 466, last_new_seq = 0, expunges = { buffer = 0x0, element_size = 0}, updates = {buffer = 0x0, element_size = 0}, last_update_idx = 0, pre_hdr_change = '\0' <repeats 119 times>, pre_hdr_mask = '\0' <repeats 119 times>, post_hdr_change = '\0' <repeats 119 times>, post_hdr_mask = '\0' <repeats 119 times>, ext_rec_updates = {buffer = 0x0, element_size = 0}, ext_resizes = {buffer = 0x0, element_size = 0}, ext_resets = {buffer = 0x0, element_size = 0}, keyword_updates = { buffer = 0x0, element_size = 0}, keyword_resets = {buffer = 0x0, element_size = 0}, cache_trans_ctx = 0x0, hide_transaction = 0, no_appends = 0, external = 1, pre_hdr_changed = 0, post_hdr_changed = 0, log_updates = 1}

2 1

[Dovecot] Dovecot hangs randomly
by Jacob Elder 15 Aug '05

15 Aug '05

I have been run into a weird problem with dovecot. We have 4 identical servers running dovecot, serving both IMAP and POP3 clients. Every few hours, clients start timing out after the PASS command. Here is what the process tree looks like at that time: 6718 ? Ss 0:00 /usr/sbin/dovecot 6719 ? S 0:00 \_ dovecot-auth 6881 ? S 0:00 | \_ dovecot-auth 6883 ? S 0:00 | \_ dovecot-auth 6890 ? S 0:00 | \_ dovecot-auth 6928 ? S 0:00 | \_ dovecot-auth 6929 ? S 0:00 | \_ dovecot-auth 6934 ? S 0:00 | \_ dovecot-auth 6936 ? S 0:00 | \_ dovecot-auth 6939 ? S 0:00 | \_ dovecot-auth 6720 ? S 0:00 \_ imap-login 6721 ? S 0:00 \_ imap-login 6722 ? S 0:00 \_ imap-login 6782 ? S 0:00 \_ pop3-login 6808 ? S 0:00 \_ pop3-login 6884 ? S 0:00 \_ pop3-login 6885 ? S 0:00 \_ pop3-login 6886 ? S 0:00 \_ pop3-login 6887 ? S 0:00 \_ pop3-login 6888 ? S 0:00 \_ pop3-login 6889 ? S 0:00 \_ pop3-login 6931 ? S 0:00 \_ pop3-login 6937 ? S 0:00 \_ pop3-login 6940 ? S 0:00 \_ pop3-login After running invoke-rc.d dovecot stop, the process tree looks like this: 6782 ? S 0:00 pop3-login 6808 ? S 0:00 pop3-login 6881 ? S 0:00 dovecot-auth 6883 ? S 0:00 dovecot-auth 6884 ? S 0:00 pop3-login 6885 ? S 0:00 pop3-login 6886 ? S 0:00 pop3-login 6887 ? S 0:00 pop3-login 6889 ? S 0:00 pop3-login 6890 ? S 0:00 dovecot-auth 6928 ? S 0:00 dovecot-auth 6929 ? S 0:00 dovecot-auth 6931 ? S 0:00 pop3-login 6934 ? S 0:00 dovecot-auth 6936 ? S 0:00 dovecot-auth 6939 ? S 0:00 dovecot-auth If I run "killall -9 dovecot-auth pop3-login; invoke-rc.d dovecot start", service resumes for a few hours. This happens both on 2.6.8 and 2.4.27. This is Debian testing, 512 MB RAM, about 20 users per server. We use libnss-ldap and libpam-ldap for all users other than root. Samba, SSH, saslauthd (for Postfix), login, etc all work as expected. There is a 5th server that is identical to the other 4 except is NOT using libpam-ldap, and dovecot does not hang on this machine. Any ideas? -- Jacob Elder

2 2

[Dovecot] Documentation
by Enrique 15 Aug '05

15 Aug '05

Hello, I have added a few questions and answers to the wiki, about stuff that caused me long hunts when trying to set up dovecot with maildir storage. Some of it I have gleaned from the source. Some of it is actually already documented, but I had not been able to spot it when I needed it. At the time of writing I had a particular advantage: I did not know, or had mostly forgotten, the peculiarities of the imap protocol. I say 'advantage', because I think that when writing documentation it is important, yet difficult, to see things from the perspective of a user that is quite ignorant, although not stupid. These need the documentation most, and they are in majority. (Some will say the "stupid" ones are in majority, but writing for them is almost futile anyway. Anyway, I doubt they are a majority; average intelligence is adequate for all normal tasks. What we often judge and condemn as "stupidity" is most often the result of a different perspective that _we_ are too limited to understand.) Since I am not yet too spoiled, and yet recently had my hands (or rather my eyes) in the source, this may be a golden opportunity to produce some more documentation. I therefore urge you to suggest what I should look at and write about. Do you have any ideas about how the documentation should be organized? some questions are not strictly dovecot or even imap questions, yet they arise quite naturally for an administrator that is migrating to dovecot or to imap in general. The existing migration documentation was not as usefull to me as it could have been because I was both migrating to imap from a non-imap solutions, and from mbox to maildir, both at the same time. That placed me in a particularly "ignorant" position. It is quite likely that much of what I write is not exactly true. I have suggested procmail as a delivery agent for maildir stores, because it is the only one I know about at the moment. I just occurred to me that I have not even checked if /bin/mail (on GNU/Linux systems) can do it. Any ideas? I have not (yet) found out anything about the CONTROL= part of the mail environment. Should I write something about it? Is it usefull for system administrators to know about it? What is it? Regards -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

9 21

[Dovecot] Binc IMAP "IMAPdir" style layout
by Martin Lucina 15 Aug '05

15 Aug '05

Hi, I'm in the process of migrating several years worth of mail to be accessible via an IMAP server. Some time ago, I evaluated both Binc IMAP and Dovecot and found Dovecot to be much faster on large folders, which is quite important to me. One thing I did not however manage to determine from the documentation on namespaces is whether or not it is possible to implement what Binc IMAP calls an "IMAPdir" style layout. IMAPdir lets me layout mailboxes in the filesystem like so: $HOME/ Maildir/ <---- users mail goes here Mail/ <---- IMAP root INBOX -> ../Maildir/ <---- (symlink) folder/ <---- some other mailbox in Maildir format folder.subfolder/ <---- '.' is the hierarchy separator folder.subfolder-2/ other-folder/ So IMAP clients subscribe to 'INBOX' and 'folder' and 'folder/subfolder' respectively. This gives me two features that I want: 1) The ability to easily access all my mail using a command line Maildir capable client such as nail, for when I'm connection over a super-slow SSH over GPRS connection. Also, I can actually see my folders (and their subfolders) without having to look for Maildir++ style names with 'ls -a' (e.g. Maildir/.subfolder/). 2) Mail folders are organized logically, unlike the standard Maildir++ layout where everything is a subfolder of 'INBOX', which strikes me as stupid. Is such a thing possible with Dovecot? Any help would be much appreciated. Thanks, -mato

6 22

[Dovecot] Plugin development
by Sebastjan Trepca 15 Aug '05

15 Aug '05

Hi, I have a few questions regarding copy and save_finish methods. How can I get a filename or processing mail from the parameters you get in that methods? How could I use the logger you use for dovecot inside my plugin? Thanks, Sebastjan

2 3

[Dovecot] migration from bincimap to dovecot (imaps)
by Andrea Riela 14 Aug '05

14 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, I've installed dovecot 0.99.14 (last port on my freebsd system), and now I've to migrate from bincimap. My system uses qmail with vpopmail (uid/gid 89) and Maildir format. Well, now the authentication is ok, but when I try to connect to mailbox I receive an error like "IMAP command SELECT failed". My dovecot.conf: protocols = imaps imaps_listen = 192.168.17.10:993 ssl_disable = no ssl_cert_file = /var/qmail/certs/mail.nesys.it_cert.pem ssl_key_file = /var/qmail/certs/mail.nesys.it_key.pem log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login_user = dovecot first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 last_valid_gid = 89 ... default_mail_env = maildir:/usr/local/vpopmail/domains/%d/%u/Maildir ... auth_userdb = vpopmail auth_passdb = vpopmail auth_user = root My Maildir directory: elessar# ls -la total 520 drwx------ 5 vpopmail vchkpw 512 Jul 11 12:40 . drwx------ 3 vpopmail vchkpw 512 Feb 7 12:10 .. - -rw------- 1 vpopmail vchkpw 23 Jul 11 10:43 .bincimap-subscribed - -rw------- 1 vpopmail vchkpw 307344 Jul 11 12:40 bincimap-cache - -rw------- 1 vpopmail vchkpw 75 Jul 11 12:39 bincimap-uidvalidity drwx------ 2 vpopmail vchkpw 190464 Jul 11 12:40 cur drwx------ 2 vpopmail vchkpw 512 Jul 11 12:39 new drwx------ 2 vpopmail vchkpw 512 Jul 11 12:18 tmp - -rw------- 1 vpopmail vchkpw 75 Jun 23 15:09 uidvalfilename I've forgotten something? Any advice will be appreciated :) Regards Andrea -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFC0k92MakHrsrHP9wRAgIrAJ9rkNALg2l/ZoJ5+YyChw5SLhXDtACgyA4T VHnceVpLb1VO9Nm5GeyLIN8= =SEHK -----END PGP SIGNATURE-----

2 5