- dovecot - dovecot.org

[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 15 Aug '05

15 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

[Dovecot] IMAP can't read inbox: istream_raw_mbox_get_body_size assertion failed
by Paul Schreiber 15 Aug '05

15 Aug '05

Yesterday, I upgraded my debian packages from 0.99.14 to 0.99.20050712-2. IMAP service has not been reliable since, and I was seeing crashes with one user. I tried deleting the user's .subscriptions and .imap folders, and forcing the client (Mac OS X's Mail.app) to redownload everything, but that resulted in an empty inbox. Here's what I have: # dpkg -l dovecot* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=====================-=====================-========================================================== ii dovecot 0.99.14-1 dummy package for upgrades to dovecot IMAP and POP3 server ii dovecot-common 0.99.20050712-2 secure mail server that supports mbox and maildir mailboxe ii dovecot-imapd 0.99.20050712-2 secure IMAP server that supports mbox and maildir mailboxe ii dovecot-pop3d 0.99.20050712-2 secure POP3 server that supports mbox and maildir mailboxe Here's what's in mail.log: Aug 13 15:09:10 sandbox dovecot: imap-login: Login: stan [70.48.39.107] Aug 13 15:09:10 sandbox dovecot: IMAP(stan): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) Aug 13 15:09:10 sandbox dovecot: child 6748 (imap) killed with signal 6 I got a core dump. Here it is: # gdb /usr/lib/dovecot/imap core (gdb) bt full #0 0x4004d83b in raise () from /lib/tls/libc.so.6 #1 0x4004efa2 in abort () from /lib/tls/libc.so.6 #2 0x08096fcb in i_set_failure_file () #3 0x08096ac7 in i_panic () #4 0x0807070f in istream_raw_mbox_get_body_size () #5 0x0806d1de in mbox_sync_has_changed () #6 0x0806eb50 in mbox_sync () #7 0x0806f9e7 in mbox_storage_sync_init () #8 0x0805ead5 in imap_sync_nonselected () #9 0x08057508 in _cmd_select_full () #10 0x080576d1 in cmd_select () #11 0x08058bf6 in _client_input () #12 0x0809c0c1 in io_loop_handler_run () #13 0x0809b65b in io_loop_run () #14 0x080602aa in main () I downgraded to 0.99.14 and put in the old configuration file and it seems to be working now. What's going on? Paul

3 2

[Dovecot] Authentication based on client host
by Sebastjan Trepca 15 Aug '05

15 Aug '05

Hi, I am wondering if it's possible to authenticate users that come from specific IP differently then other users. I will be authenticating them by postgresql so something like this would be very useful: password_query = SELECT password from get_user('%username','%host') Is that possible? Can it be done any other way? Thanks, Sebastjan

2 2

[Dovecot] Upgraded from 0.99 to 1.0 stable on FC3
by Obantec Support 15 Aug '05

15 Aug '05

Hi I upgraded to 1.0 stable and saw this in the maillog UIDs broken with partial sync in mbox file /var/spool/mail/thejohns_brian i am using mbox files with default_mail_env = mbox:/var/spool/mail/%u Is this a problem that i should worry about? Mark

2 1

[Dovecot] hangs on dovecot test77, mutt
by Tzafrir Cohen 15 Aug '05

15 Aug '05

Hi My toy mail server runs dovecot. My client is mutt, which I use normally use a a remote screen session. I normally connect to imap locally: account-hook imap://localhost/ 'set tunnel="/usr/local/bin/imap-local"' After a long frustration from the new mail notification in 0.99, I have decided to bite the bullet and try the -test series. Ever since I have not had stable mutt sessions. Occasionally mutt hangs on the imap connection. Usually when openning a new mailbox. But sometimes even when closing an existing mailbox. Occasionally mutt will even crash (which is annoying, but certainly not a bug of dovecot). How do I debug this? -- Tzafrir Cohen | tzafrir(a)jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir(a)cohens.org.il | | best ICQ# 16849755 | | friend

3 4

[Dovecot] dovecot update ?
by Brent Clark 14 Aug '05

14 Aug '05

Hi list Im currently run debian sarge / testing. I upgraded my dovecot this morning on my mail server this morning, and my dovecot stopped working for my mail users email clients. I told debconf to replace the dovecot.conf (Baring in mind I saved my conf file). The output I was getting was as so: ====================================================================== Aug 11 10:09:56 mail dovecot: Dovecot v1.0-test70 starting up Aug 11 10:10:21 mail dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Ilip=192.168.111.11^Irip=192.168.111.225^Iresp=AGdjaXZvbG FuaQBwYXNzd29yZA== Aug 11 10:10:21 mail dovecot: auth(default): client out: OK^I1^Iuser=gcivolani Aug 11 10:10:21 mail dovecot: auth(default): master in: REQUEST^I1^I2040^I1 Aug 11 10:10:21 mail dovecot: auth(default): master out: USER^I1^Igcivolani^Isystem_user=gcivolani^Iuid=1009^Igid=1009^Ihome=/home/gcivolani Aug 11 10:10:21 mail dovecot: imap-login: Login: gcivolani [192.168.111.225] Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): Effective uid=1009, gid=1009 Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): Namespace: type=public, prefix=Public/, sep=/, inbox=no, hidden=no, subscriptions=no Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): maildir autodetect: stat(/tmp/cur) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: data=/tmp Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: INBOX file: is a directory (/tmp) Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: has .imap/: stat(/tmp/.imap) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: has inbox: stat(/tmp/inbox) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: has mbox: stat(/tmp/mbox) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): Failed to create storage for 'Public/' with data: /tmp Aug 11 10:10:21 mail dovecot: child 2052 (imap) returned error 89 Aug 11 10:10:21 mail dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Ilip=192.168.111.11^Irip=192.168.111.225^Iresp=AGdjaXZvbG FuaQBwYXNzd29yZA== Aug 11 10:10:21 mail dovecot: auth(default): client out: OK^I1^Iuser=gcivolani ======================================================================== I killed dovecot and restarted it with my old conf fike (I have attached my conf file). I then proceed by uninstalling this version of dovecot and reinstalled the previous version (still using the old conf file) On doing so I, started getting this error message in my syslog: ======================================================================== Aug 11 12:24:46 mail dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Ilip=192.168.111.11^Irip=192.168.111.225^Iresp=AGdjaXZvbG FuaQBwYXNzd29yZA== Aug 11 12:24:46 mail dovecot: auth(default): client out: OK^I1^Iuser=gcivolani Aug 11 12:24:46 mail dovecot: auth(default): master in: REQUEST^I115^I4435^I1 Aug 11 12:24:46 mail dovecot: auth(default): master out: USER^I115^Igcivolani^Isystem_user=gcivolani^Iuid=1009^Igid=1009^Ihome=/home/gcivolani Aug 11 12:24:46 mail dovecot: IMAP(gcivolani): Effective uid=1009, gid=1009 Aug 11 12:24:46 mail dovecot: IMAP(gcivolani): maildir: data=/home/gcivolani/Maildir Aug 11 12:24:46 mail dovecot: IMAP(gcivolani): maildir: root=/home/gcivolani/Maildir, index=/home/gcivolani/Maildir, control=, inbox= Aug 11 12:24:46 mail dovecot: imap-login: Login: gcivolani [192.168.111.225] ======================================================================== Although dovecot's port was up and running, my users still could not read or see there folders. It was only once I realised that when I copied and renamed my .subscription file to subscription, did it all work. Obviously the mistake was on myside but telling debconf to over write the conf file, but I find it a bit weid that when on killing dovecot and then restarting the with the old conf file, it still did not work. To be honest, im a bit lost as to how im going to rectify this, but I know that I want to upgrade my packages. If you can help in anyway, it would be most appreciated. Kind Regards and thanks in advance. Brent Clark ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. login_greeting = Dovecot ready. ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # 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 = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # 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's 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 = #default_mail_env = maildir: #default_mail_env = maildir:%h/Maildir 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. # default namespace #namespace private { # separator = / # prefix = # inbox = yes #} # for backwards compatibility: #namespace private { # separator = / # prefix = mail/ # hidden = yes #} #namespace private { # separator = / # prefix = ~/mail/ # hidden = yes #} #namespace private { # separator = / # prefix = ~%u/mail/ # hidden = yes #} #namespace public { # separator = / # prefix = Public/ # location = /tmp #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # 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 # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #pop3_uidl_format = %v.%u # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. 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. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = yes # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. #passdb { # args=/etc/passwd #} passdb pam { } userdb passwd { } #passdb pam { # Service name or * as parameter. * means the authenticating service name # is used, eg. pop3 or imap. #args = dovecot #args= /etc/passwd #} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. # passdb passwd { # args= /etc/passwd # } # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. # passdb shadow { # args= /etc/shadow # } # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication #passdb checkpassword { # Path for checkpassword binary #args = #} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:%h/mail nice=10 # #args = #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

3 2

[Dovecot] dovecot-auth: BUG: login gave a PID of existing connection
by m.durnthaler＠aon.at 14 Aug '05

14 Aug '05

hi, first of all i have to say that i´m new to dovecot and to mailinglist. i´m trying to setup my owen imap-server on fc3, but i have some trouble with dovecot. wenn i try to log in with telnet lovalhost 143 /var/log/maillog says: dovecot-auth: BUG: login gave a PID of existing connection. can someone please give me an hint or a link to solve this problem. yours, martin. ------------------------------------------- Versendet durch aonWebmail (webmail.aon.at)

3 3

[Dovecot] crash (assertion failed: (uidlist->lock_count == 1)
by Jakob Hirsch 14 Aug '05

14 Aug '05

Hi, with 1.0-test79 Aug 3 16:18:23 ymmv dovecot: IMAP(jh): file maildir-uidlist.c: line 536 (maildir_uidlist_rewrite): assertion failed: (uidlist->lock_count == 1) Aug 3 16:18:23 ymmv dovecot: child 10780 (imap) killed with signal 6 Any idea what that is? I did no special operation, just selected a mail to read with thunderbird (1.06). After restarting TB it worked.

2 3

[Dovecot] Problem with dovecot and system crashing
by Colin Kingsbury 14 Aug '05

14 Aug '05

Hi all, I am running dovecot on a linux server (FC3) in conjunction with Sendmail. My configuration is quite vanilla and I am having the following problem: occasionally (once every 3-10 days) the dovecot server will become unresponsive and attempting to access mail via pop3 will produce an error message on the client side. As best as I can tell, the dovecot process dies because if I restart it with /sbin/service dovecot restart I get [failed] on the stop and [ok] on the start. Now, here's the interesting part: within 5 minutes of this happening, the whole machine becomes completely unresponsive and requires a power-cycle to restart it. In between dovecot dying and the server going down, the other applications (apache, mysql) continue to run. Naturally, there are no messages in the syslog or the maillog and it is set to log all messages of info or higher. Any suggestions on how to attack this would be greatly appreciated. Best, -cwk.

3 4

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

14 Aug '05

aries:/etc/init.d# netstat -ltnp | grep ':143' aries:/etc/init.d# Right I found that cyrus was in the inet config uncommented and now I recieve outputs for dovecot :) As for SquirrelMail Config test: Warning: fsockopen(): unable to connect to localhost:143 in /var/www/mail/src/configtest.php on line 247 ERROR: Error connecting to IMAP server "localhost:143".Server error: (111) Connection refused Right so obiously I need to put dovecot in the inet conf any ideas what to put in? Thanks Mark 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. >

2 3

[Dovecot] Mailbox written with normalized headers
by Kenneth Porter 14 Aug '05

14 Aug '05

Over on the SpamAssassin list someone noted that some spam generators add leading spaces to the subject line, but it was impossible to detect this when using Dovecot for POP3 service. Some quick testing shows that dovecot-0.99.13-4.FC2 writes the mailbox back with the extra spaces in the header squeezed out. I think Dovecot should avoid reformatting headers any more than necessary to avoid interfering with spam detectors.

2 1

[Dovecot] Dovecot & SquirrelMail
by admin＠downend.org 14 Aug '05

14 Aug '05

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 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!

1 0

[Dovecot] debs for 1.0?
by Lorens 12 Aug '05

12 Aug '05

Hi, 0.99 is running nicely on my sarges, but I need pop3_uidl_format = %f for Courier compatibility. I can't find any debs more recent than test22 of over a year ago (those are at http://src.braincells.com/dovecot-test/) Even though google turns up http://hemma.tobbe.nu/debian/mini-dinstall/incoming/dovecot_1.0.test46-1_i3… searching for dovecot on packages.debian.org (any distribution or source) only yields 0.99.14 and 0.99.20050712. I know Jaldhar called for vounteers to take over, but I don't feel qualified... but I've managed to do away with all non-deb installations, so if I have to I'll make a .deb myself, is there maybe an already-written script to do that with dovecot? Thanks for suggestions.

4 6

[Dovecot] Dovecot & SquirrelMail HELP!
by admin＠downend.org 12 Aug '05

12 Aug '05

Hi All, I just installed Dovecot-Imap because uw-imap is awful... and Dovecot seems like a good Imap Server. Anyway I am using a Debian Server and apt-get install dovecot Seems to be working... I can telnet to port 143 and run /var/run/dovecot/login However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SquirrelMail please let me know... THis is quite urgent matter and need to fix this ASAP! Thanks! Mark Smith

6 12

Fwd: Re: [Dovecot] Dovecot & SquirrelMail HELP!
by admin＠downend.org 11 Aug '05

11 Aug '05

aries:/etc/postfix# netstat -ltnp | grep ':143' tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 22272/cyrmaster Well we are getting somewhere :) Just one now... Cyrus has been removed and purged off the system.. i found something about cyrus commented in postfix config, i have removed it, restarted and reloaded postfix still there aries:/etc/postfix# pidof cyrmaster 22272 aries:/etc/postfix# kill 22272 and it is still alive argg!!! Quoting Johannes Berg <johannes(a)sipsolutions.net>: > On Fri, 2005-08-12 at 02:03 +1000, admin(a)downend.org wrote: > > > > I have installed previous Imap Servers could that be it? > > > > How can I check if port 143 is being used by another imap server? > > > > > > netstat -tan|grep 143 > > > > I recieved the following output: > > > > aries:~# netstat -tan|grep 143 > > tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN > > There's something listening on 143. Run the following as root: > > netstat -ltnp | grep ':143' > > to see which process it is. > > johannes > ----- End forwarded message -----

1 0

[Dovecot] vpopmail directory permissions denied
by bclements＠io-networks.com 11 Aug '05

11 Aug '05

I've moved from a postfix setup to a qmail/vpopmail setup I've setup the dovecot.conf file for vpopmail That works fine, users can log in, but the problem is when they go to see their folders. Nothing is there. INBOX, Drafts, nothing. This is using any imap client, imp, evolution, outlook, outlook express This is using 99.14 and the latest vpopmail/qmail I looked at the directory structure and everything is there. The dovecot log file says something about permissions denied. I am using freebsd 4.10 Anybody have a clue on whats going on? -Brent ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

[Dovecot] Mail disappearing
by bclements＠io-networks.com 11 Aug '05

11 Aug '05

My users are complaining that their mail is dissappearing out of folders or if they go into a folder, the mail will be there one minute, the next it isn't. Anybody see this before...and if so..is there a fix? I'm running dovecot 99.11 Brent ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

11 25

[Dovecot] Need Help with Dovecot-Imapd and SquirrelMail
by admin＠downend.org 11 Aug '05

11 Aug '05

Hi All, I just installed Dovecot-Imap because uw-imap is awful... and Dovecot seems like a good Imap Server. Anyway I am usnig a Debian Server and apr-get install dovecot Seems to be working... I can telnet to it and /var/run/dovecot/login However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SQuirrelMail please let me know... THis is quite urgent. Thanks! Mark Smith

1 0

[Dovecot] Re: dovecot 0.99.20050712-1
by Jaldhar H. Vyas 11 Aug '05

11 Aug '05

On Sun, 24 Jul 2005, Nick Maynard wrote: > Yep - I too saw that posting on the dovecot list... sadly after I posted > to this one. I thought the best thing to do was probably to wait > quietly, but I suppose giving him a friendly poke can't do any harm > (Hello, Jaldhar!). > > Thanks all, > Apologies for the delay but I have now prepared a backport. The problem is I don't know how to upload it to backports.org but while I get that sorted out you can get the files from http://www.braincells.com/backports/ (It's not aptable, you'll have to download the packages and manually install them with dpkg -i) -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

[Dovecot] Starting Dovecot Imap [FAILED]
by hettige＠mfac.kln.ac.lk 10 Aug '05

10 Aug '05

I want to configure dovecot in FC 4. Set the "protocols = Imap Imaps Pop3 Pop3s" in dovecot.conf Test the service by giving "service dovecot start" command and finally I got "Starting Dovecot Imap [FAILED]" Can somebody explain WHY? Saman ---------------------------------------------------

4 3

[Dovecot] new inotify patch
by Johannes Berg 10 Aug '05

10 Aug '05

Hi, As discussed on IRC, the attached patch changes the notification API and fixes inotify. johannes

1 0

[Dovecot] Strange index problem
by Andrew Hutchings 09 Aug '05

09 Aug '05

Hi, OK, I have 2 servers accessing the same mailboxes via NFS (indexes on each servers local HDD). They are on a round robin connection system. I have had a mailbox (customer using Eudora for Mac and storing mail for a certain amount of days) that on one server says there are 281 messages and the other says there are 194 messages. Of course this leads to re-downloading the difference. The mails that are invisible to the second machine are not sequential, they are at random places in the mailbox. Deleting the indexed on the machine that is inconsistent seems to fix it. We seem to get this problem about once a week or 2 over 6000 mailboxes. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 147: "The Internet? We are not interested in it" - Bill Gates, 1993

1 0

[Dovecot] Re: Problem with dovecot and system crashing
by Paul Vatta 09 Aug '05

09 Aug '05

We have experienced similar problems with version 0.99.11 that comes with Redhat Enterprise Linux 4. If I'm not wrong, it appears to be related to the number of file descripters available to the dovecot user. To abate the situation, we stop the service, kill any remaining dovecot processes (some hang around), and then restart dovecot. Sometimes it appears that the limit of connection processes isn't honoured (as defined in the conf file) so the number can spiral out of control. I hope this helps in the absense of a workaround. Let me know if there is an obvious configuration setting to remedy this.

1 0

[Dovecot] out of disk space notification
by David Weilers 09 Aug '05

09 Aug '05

Hi Dovecot readers, My server (squirrelmail) provides me with the following error-message when selecting a mailbox (trash): ERROR : Could not complete request. Query: SELECT "Trash" Reason Given: Out of disk space The user is not over quota but for some reason dovecot still thinks this to be true. Can anyone give me a hint for finding a solution for this problem. I have installed: dovecot-0.99.10.9-2.0.rh9.dag Thanks in advance.. David

3 4

[Dovecot] corrupted binary tree and index data files
by Gary Sandine 09 Aug '05

09 Aug '05

Hi. I am using dovecot 0.99.14 as an imaps server with mbox folders (in an NFS-mounted directory) in x86 Debian testing. I have searched the archives of this list and have seen other evidence of the problems I am having. I get lots of log messages like these: Jul 29 07:47:09 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/.imap/INBOX/.imap.index.tree: UID to be inserted isn't higher than existing (290 <= 291) ... Jul 29 07:47:13 HOST imap(USER): Corrupted index data file /home/USER/IMAP_MBOX_DIR/.imap/INBOX/.imap.index.data: Field 1 size points outside file (14648 / 14656) for record 290 This is from the midst of a herd of messages starting at 82 <= 144: Jul 28 08:01:31 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (82 <= 144) ... Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (143 <= 144) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (144 <= 144) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (92 <= 154) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (93 <= 154) ... Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (101 <= 154) Jul 28 08:01:34 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/SUBFOLDER_DIR/.imap/MBOX2/.imap.index.tree: UID to be inserted isn't higher than existing (79 <= 80) Jul 28 08:01:34 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/SUBFOLDER_DIR/.imap/MBOX2/.imap.index.tree: UID to be inserted isn't higher than existing (80 <= 80) Jul 28 08:11:27 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (102 <= 164) ... I don't know how to reproduce this. It happens (repeatedly) for some users and seems to be independent of the number of mboxes, mbox sizes, mail client, .... I have tried deleting .imap directories, and this helps for a while, but the problem always comes back for a few users. The proposed solution for "Corrupted binary tree" or "Corrupted index data file" log messages is usually to change to a different version of dovecot. I will try that, but want to check in here first in case something obvious is happening that I don't understand. Thanks, -- Gary Sandine <gars(a)lanl.gov>

2 2

[Dovecot] Header problems
by Andrew Hutchings 08 Aug '05

08 Aug '05

Hi, I don't know if this has been covered or not as I have been out of action most of the last few weeks getting married and stuff. My query / slight problem is when I re-install an IMAP client or change client all mails that have been read so far show an empty header with the date set back to 1970 but the mails are fully readable. New mails that weren't read in a previous client show fine. Could this be something do to with me using fcntl? I am using the latest test version with Maildir boxes. I haven't got any diagnostic data of this yet, I want to make sure this isn't a common problem first. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 114: "Both the PC industry and consumers alike would be better off with some modest limits on Microsoft's zeal." - JOHN BLACKFORD, Editor, Computer Shopper

2 2

[Dovecot] directory names - have to begin with a dot?
by Tom Alsberg 07 Aug '05

07 Aug '05

Hi there... Two questions: (1) Is there an easy way to have Dovecot recognize subdirectories that do not begin with a dot as sub-hierarchies? (2) Is there a way to have the root folder map to a certain other mbox/maildir? I want a setup like this: / -> $HOME/mbox /INBOX -> /var/spool/<username> /folder -> $HOME/mail/folder /folder/foo -> $HOME/mail/folder/foo /folder/bar -> $HOME/mail/folder/bar /folder/foo/bar -> $HOME/mail/folder/foo/bar (Assuming / as a hierarchy separator - that is, /folder/foo/bar is the IMAP folder 'bar' inside 'foo' inside 'folder') The idea is something resembling and compatible with the default behaviour of elm/pine/mutt/KMail/evolution, so a user can use both those locally and whatever IMAP client remotely in a similiar organisation... I would love some further documentation regarding the working of Dovecot's folder lookup and how to achieve different IMAP folder organisations with dovecot. I have not yet looked deep enough into the sources to understand where most of the flexibiliy stems. Cheers, -- Tom P.S. anyone checked my trivial patch for settings parsing after closing braces? -- 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.

2 5

[Dovecot] auth_passdb using MySQL fails at starup
by Josh Joslyn 07 Aug '05

07 Aug '05

I've got dovecot v0.99.14, MySql 4.1.11 and postfix on fedora core 4. when using uxix socket I get: dovecot-auth: MySQL: Can't connect to database vmail: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) when using tcp socket I get: dovecot-auth: MySQL: Can't connect to database vmail: Can't create TCP/IP socket (13) * the mysql.sock exists * I can connect to mysql -u vmail and select on the table mailbox * I can run mysqladmin successfully using the port or the socket As you can see below I modified the password query to be very simple. I am surprised to get the error on startup since the password query should not be executed at this point. The problem is not MySql as I am able to query all day long the the vmail database table called mailbox with the vmail user. Not sure what else I can check Dovecot error message lacks the reason it can not connect - unless the (13) means anything to anybody??? Anybody have any ideas??? dovecot.conf : . auth_assdb = mysql /etc/dovecot-mysql.conf dovecot-mysql.conf : db_host = localhost db_unix_socket = /var/lib/mysql/mysql.sock #db_port = 3306 db = vmail db_user = vmail db_passdb = temp password_query = SELECT 'test' as password from mailbox vmail.sql: create database vmail; use vmail; grant insert,select,update,delete on vmail.* to 'vmail'@'localhost' identified by 'temp'; CREATE TABLE mailbox ( user varchar(20) not null, domain varchar(30) not null, password varchar(20) not null, status char, PRIMARY KEY (user,domain) ); insert into mailbox values('someone', 'domain.org', 'secret', 'Y');

2 1

[Dovecot] Copying keyworded messages kills IMAP process(test78)
by Sebastjan Trepca 07 Aug '05

07 Aug '05

Hi, when I try to copy/move messages with keywords, IMAP process dies: dovecot: Jul 24 23:49:47 Info: imap-login: Login: user=<seba>, method=PLAIN, rip=192.168.0.192 <http://192.168.0.192>, lip=192.168.0.188<http://192.168.0.188> dovecot: Jul 24 23:49:47 Info: IMAP(seba): Effective uid=1000, gid=100 dovecot: Jul 24 23:49:47 Info: IMAP(seba): maildir: data=/home/seba/Maildir dovecot: Jul 24 23:49:47 Info: IMAP(seba): maildir: root=/home/seba/Maildir, index=/home/seba/Maildir, control=, inbox= dovecot: Jul 24 23:49:53 Error: child 22903 (imap) killed with signal 11 I'm using dovecot-test78 on Suse 9.2 with hardlink support. Regards, Sebastjan

2 1

[Dovecot] Dieing?
by Matt Juszczak 07 Aug '05

07 Aug '05

Our dovecot process died out of no where today, with no sign of reasons why. I'm running a beta from a few weeks ago of 1.0 ... are there any security vulns I should know about that might have caused this crash (someone trying something?) Thanks, Regards, Matt

2 1

[Dovecot] How is the correct "auth" method selected in 1.0-stable?
by Ben Beuchler 07 Aug '05

07 Aug '05

In the example config for 1.0-stable, I see several "auth <blah> {}" blocks. The only one uncommented is the "auth default{}" block. How does dovecot decide which one to use? If I want it to use LDAP, should I just modify the "userdb" and "passdb" entries in the "auth default" block? Or should I be using the "auth ldap" block and somehow telling dovecot to use it? Thanks! -Ben

2 1

[Dovecot] POP and IMAP at the same time
by Marc Perkel 07 Aug '05

07 Aug '05

If a user was accessing their mailbox with POP and another process accessed it with IMAP - would that create an error? Trying to track down an unusual bug.

2 1

[Dovecot] error sha1
by Alex Romijn 07 Aug '05

07 Aug '05

Hello, I have a problem. When I do 'make' it gives the following error: gcc -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecot-auth auth-cache.o au th-client-connection.o auth-master-connection.o auth-module.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech- cram-md5.o mech-digest-md5.o mech-ntlm.o mech-rpa.o mech-apop.o passdb.o passdb- bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o pass db-pam.o passdb-checkpassword.o passdb-shadow.o passdb-vpopmail.o passdb-sql.o u serdb.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-static.o userd b-vpopmail.o userdb-sql.o -Wl,--export-dynamic libpassword.a ../lib-settings/li bsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -L/usr/lib /mysql /usr/lib/mysql/libmysqlclient.a -lcrypt -lnsl -lm -lc -lnss_files -lnss_d ns -lresolv -lz -ldl /usr/lib/mysql/libmysqlclient.a(sha1.o)(.text+0x60): In function `sha1_result': : multiple definition of `sha1_result' ../lib/liblib.a(sha1.o)(.text+0x7f4):/usr/local/src/dovecot/dovecot-1.0-stable/s rc/lib/sha1.c:233: first defined here /usr/bin/ld: Warning: size of symbol `sha1_result' changed from 158 in ../lib/li blib.a(sha1.o) to 126 in ../lib/liblib.a(sha1.o) collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-stable/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-stable/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-stable' make: *** [all] Error 2 What is wrong? And how can I fix this? thanks, Alex

2 1

[Dovecot] what does it mean first_uid
by G�khan Alkan 07 Aug '05

07 Aug '05

i installed qmail + vpopmail + dovecot.i installed dovecot without problems.but i run telnet localhost 143 x login user password it seems to error about first_uid.and i change first_uid vpopmail_uid (89) its ok.but i dont understand first_uid.and sholud i change last_uid , first_gid ,last_guid . do you recommend it thanks everynbody ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

2 1

[Dovecot] mechanisms?
by Marc Perkel 07 Aug '05

07 Aug '05

ok - if I'm using a password/shadow file arrangement, what auth mechanisms besides "plain" should I turn on? -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] Dovecot 1.0-test77 endless loop hang
by Todd Vierling 07 Aug '05

07 Aug '05

Client: Bynari Insight Connector 3.0.5. (http://www.bynari.net/) This is an IMAP-based plugin for Outlook that can also store Outlook collaboration objects (calendar, tasks, notes, etc.) in IMAP messages on the server side. It does not require special server extensions, and it was actually (mostly) working with 1.0-stable. Below is a rawlog dump showing what is going back and forth. After fetching the second message, the imap process pegs the CPU and sends no more data. This also triggers a bug in the Bynari product, for which I've entered a bug report too. (mmm, mutual bug triggering :) The Connector opens two simultaneous IMAP connections: one for subscription control and one for data transfer. So I've noted the log dumps. I've also checked, and Pine is having no troubles reading any of the messages in the INBOX folder. The last BODYSTRUCTURE line (with a bunch of NILs) makes me wonder if there's something wrong with the indexing. Or perhaps something is not carrying forward the requested FETCH data to the second and later messages in a multi-message fetch? I can go further to check a gdb trace or something similar, but I wanted to mention this problem here first in case it's obvious where this endless loop may be happening. Non-default config variables (all work fine with Pine): default_mail_env = maildir:%h/.maildir protocol imap { ... imap_client_workarounds = delay-newmail outlook-idle ... } ===== subscription control connection (IN) 00000002 CAPABILITY 00000003 NAMESPACE 00000004 Subscribe INBOX 00000005 LSUB "" %* 00000006 LSUB "" %* ===== subscription control connection (OUT) * OK [RAWLOG TIMESTAMP] 2005-08-01 16:49:30 * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 00000002 OK Capability completed. * NAMESPACE (("" "/")) NIL NIL 00000003 OK Namespace completed. 00000004 OK Subscribe completed. * LSUB () "/" "INBOX" * LSUB () "/" "INBOX/Outbox" * LSUB () "/" "INBOX/Sent Items" * LSUB () "/" "INBOX/Deleted Items" * LSUB () "/" "INBOX/Calendar" * LSUB () "/" "INBOX/Contacts" * LSUB () "/" "INBOX/Journal" * LSUB () "/" "INBOX/Notes" * LSUB () "/" "INBOX/Tasks" * LSUB () "/" "INBOX/Drafts" * LSUB () "/" "INBOX/Junk E-mail" 00000005 OK Lsub completed. * LSUB () "/" "INBOX" * LSUB () "/" "INBOX/Outbox" * LSUB () "/" "INBOX/Sent Items" * LSUB () "/" "INBOX/Deleted Items" * LSUB () "/" "INBOX/Calendar" * LSUB () "/" "INBOX/Contacts" * LSUB () "/" "INBOX/Journal" * LSUB () "/" "INBOX/Notes" * LSUB () "/" "INBOX/Tasks" * LSUB () "/" "INBOX/Drafts" * LSUB () "/" "INBOX/Junk E-mail" 00000006 OK Lsub completed. ===== data connection (IN) 00000002 CAPABILITY 00000003 NAMESPACE 00000004 Subscribe INBOX 00000005 NOOP 00000006 SELECT INBOX/Contacts 00000007 UID FETCH 1:* FLAGS 00000008 NOOP 00000009 SEARCH HEADER X-Bynari-Folder-Class "" 0000000a FETCH 1 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Date X-Priority X-Bynari-Folder-Class X-PR-CONTAINER-CLASS X-Message-Flag Received)] INTERNALDATE RFC822.SIZE FLAGS) 0000000b NOOP 0000000c SELECT INBOX 0000000d UID FETCH 1:* FLAGS 0000000e NOOP 0000000f SEARCH HEADER X-Bynari-Folder-Class "" 00000010 FETCH 1:51 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Date X-Priority X-Bynari-Folder-Class X-PR-CONTAINER-CLASS X-Message-Flag Received)] BODYSTRUCTURE INTERNALDATE RFC822.SIZE FLAGS) ===== data connection (OUT) * OK [RAWLOG TIMESTAMP] 2005-08-01 16:49:32 * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 00000002 OK Capability completed. * NAMESPACE (("" "/")) NIL NIL 00000003 OK Namespace completed. 00000004 OK Subscribe completed. 00000005 OK NOOP completed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1122927796] UIDs valid * OK [UIDNEXT 2] Predicted next UID 00000006 OK [READ-WRITE] Select completed. * 1 FETCH (FLAGS (\Seen) UID 1) 00000007 OK Fetch completed. 00000008 OK NOOP completed. * SEARCH 1 00000009 OK Search completed. * 1 FETCH (UID 1 INTERNALDATE "01-Aug-2005 16:23:17 -0400" RFC822.SIZE 319 FLAGS (\Seen) ENVELOPE ("Mon, 1 Aug 2005 16:23:17 -0400 (Eastern Daylight Time)" "Hidden synchronization message" ((NIL NIL "Bynari" "MISSING_DOMAIN")) ((NIL NIL "Bynari" "MISSING_DOMAIN")) ((NIL NIL "Bynari" "MISSING_DOMAIN")) NIL NIL NIL NIL NIL) BODY[HEADER.FIELDS (DATE X-PRIORITY X-BYNARI-FOLDER-CLASS X-PR-CONTAINER-CLASS X-MESSAGE-FLAG RECEIVED)] {135} Date: Mon, 1 Aug 2005 16:23:17 -0400 (Eastern Daylight Time) X-Bynari-Folder-Class: IPF.Contact X-PR-CONTAINER-CLASS: IPF.Contact ) 0000000a OK Fetch completed. 0000000b OK NOOP completed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 522 EXISTS * 0 RECENT * OK [UNSEEN 111] First unseen. * OK [UIDVALIDITY 1122905893] UIDs valid * OK [UIDNEXT 577] Predicted next UID 0000000c OK [READ-WRITE] Select completed. * 1 FETCH (FLAGS (\Seen) UID 1) * 2 FETCH (FLAGS (\Seen) UID 2) * 3 FETCH (FLAGS (\Seen) UID 3) * 4 FETCH (FLAGS (\Seen) UID 4) * 5 FETCH (FLAGS (\Seen) UID 5) * 6 FETCH (FLAGS (\Seen) UID 6) * 7 FETCH (FLAGS (\Answered \Seen) UID 7) * 8 FETCH (FLAGS (\Seen) UID 8) * 9 FETCH (FLAGS (\Answered \Seen) UID 9) * 10 FETCH (FLAGS (\Answered \Seen) UID 10) * 11 FETCH (FLAGS (\Seen) UID 11) * 12 FETCH (FLAGS (\Seen) UID 12) * 13 FETCH (FLAGS (\Seen) UID 13) * 14 FETCH (FLAGS (\Seen) UID 14) * 15 FETCH (FLAGS (\Seen) UID 15) * 16 FETCH (FLAGS (\Seen) UID 16) * 17 FETCH (FLAGS (\Seen) UID 17) * 18 FETCH (FLAGS (\Seen) UID 18) * 19 FETCH (FLAGS (\Seen) UID 19) * 20 FETCH (FLAGS (\Seen) UID 20) * 21 FETCH (FLAGS (\Seen) UID 21) * 22 FETCH (FLAGS (\Seen) UID 22) * 23 FETCH (FLAGS (\Seen) UID 23) * 24 FETCH (FLAGS (\Seen) UID 24) * 25 FETCH (FLAGS (\Seen) UID 25) * 26 FETCH (FLAGS (\Seen) UID 26) * 27 FETCH (FLAGS (\Answered \Seen) UID 27) * 28 FETCH (FLAGS (\Seen) UID 28) * 29 FETCH (FLAGS (\Seen) UID 29) * 30 FETCH (FLAGS (\Seen) UID 30) * 31 FETCH (FLAGS (\Seen) UID 31) * 32 FETCH (FLAGS (\Seen) UID 32) * 33 FETCH (FLAGS (\Seen) UID 33) * 34 FETCH (FLAGS (\Seen) UID 34) * 35 FETCH (FLAGS (\Seen) UID 35) * 36 FETCH (FLAGS (\Seen) UID 36) * 37 FETCH (FLAGS (\Seen) UID 37) * 38 FETCH (FLAGS (\Seen) UID 38) * 39 FETCH (FLAGS (\Seen) UID 39) * 40 FETCH (FLAGS (\Seen) UID 40) * 41 FETCH (FLAGS (\Seen) UID 41) * 42 FETCH (FLAGS (\Seen) UID 42) * 43 FETCH (FLAGS (\Seen) UID 43) * 44 FETCH (FLAGS (\Seen) UID 44) * 45 FETCH (FLAGS (\Seen) UID 45) * 46 FETCH (FLAGS (\Seen) UID 46) * 47 FETCH (FLAGS (\Seen) UID 47) * 48 FETCH (FLAGS (\Seen) UID 48) * 49 FETCH (FLAGS (\Seen) UID 49) * 50 FETCH (FLAGS (\Seen) UID 50) * 51 FETCH (FLAGS (\Seen) UID 51) * 52 FETCH (FLAGS (\Seen) UID 52) * 53 FETCH (FLAGS (\Seen) UID 53) * 54 FETCH (FLAGS (\Seen) UID 54) * 55 FETCH (FLAGS (\Seen) UID 55) * 56 FETCH (FLAGS (\Seen) UID 56) * 57 FETCH (FLAGS (\Seen) UID 57) * 58 FETCH (FLAGS (\Answered \Seen) UID 58) * 59 FETCH (FLAGS (\Answered \Seen) UID 59) * 60 FETCH (FLAGS (\Seen) UID 60) * 61 FETCH (FLAGS (\Seen) UID 61) * 62 FETCH (FLAGS (\Seen) UID 62) * 63 FETCH (FLAGS (\Seen) UID 63) * 64 FETCH (FLAGS (\Seen) UID 64) * 65 FETCH (FLAGS (\Seen) UID 65) * 66 FETCH (FLAGS (\Seen) UID 66) * 67 FETCH (FLAGS (\Seen) UID 67) * 68 FETCH (FLAGS (\Seen) UID 68) * 69 FETCH (FLAGS (\Seen) UID 69) * 70 FETCH (FLAGS (\Seen) UID 70) * 71 FETCH (FLAGS (\Seen) UID 71) * 72 FETCH (FLAGS (\Seen) UID 72) * 73 FETCH (FLAGS (\Seen) UID 73) * 74 FETCH (FLAGS (\Seen) UID 74) * 75 FETCH (FLAGS (\Seen) UID 75) * 76 FETCH (FLAGS (\Seen) UID 76) * 77 FETCH (FLAGS (\Seen) UID 77) * 78 FETCH (FLAGS (\Seen) UID 78) * 79 FETCH (FLAGS (\Seen) UID 79) * 80 FETCH (FLAGS (\Seen) UID 80) * 81 FETCH (FLAGS (\Seen) UID 81) * 82 FETCH (FLAGS (\Seen) UID 82) * 83 FETCH (FLAGS (\Seen) UID 83) * 84 FETCH (FLAGS (\Seen) UID 84) * 85 FETCH (FLAGS (\Seen) UID 85) * 86 FETCH (FLAGS (\Seen) UID 86) * 87 FETCH (FLAGS (\Seen) UID 87) * 88 FETCH (FLAGS (\Seen) UID 88) * 89 FETCH (FLAGS (\Seen) UID 89) * 90 FETCH (FLAGS (\Seen) UID 90) * 91 FETCH (FLAGS (\Seen) UID 91) * 92 FETCH (FLAGS (\Seen) UID 92) * 93 FETCH (FLAGS (\Seen) UID 93) * 94 FETCH (FLAGS (\Seen) UID 94) * 95 FETCH (FLAGS (\Seen) UID 95) * 96 FETCH (FLAGS (\Seen) UID 96) * 97 FETCH (FLAGS (\Seen) UID 97) * 98 FETCH (FLAGS (\Seen) UID 98) * 99 FETCH (FLAGS (\Seen) UID 99) * 100 FETCH (FLAGS (\Seen) UID 100) * 101 FETCH (FLAGS (\Answered \Seen) UID 101) * 102 FETCH (FLAGS (\Seen) UID 102) * 103 FETCH (FLAGS (\Seen) UID 103) * 104 FETCH (FLAGS (\Seen) UID 104) * 105 FETCH (FLAGS (\Seen) UID 105) * 106 FETCH (FLAGS (\Seen) UID 106) * 107 FETCH (FLAGS (\Seen) UID 107) * 108 FETCH (FLAGS (\Seen) UID 108) * 109 FETCH (FLAGS (\Seen) UID 109) * 110 FETCH (FLAGS (\Seen) UID 110) * 111 FETCH (FLAGS () UID 111) * 112 FETCH (FLAGS () UID 112) * 113 FETCH (FLAGS () UID 113) * 114 FETCH (FLAGS () UID 114) * 115 FETCH (FLAGS () UID 115) * 116 FETCH (FLAGS () UID 116) * 117 FETCH (FLAGS (\Seen) UID 117) * 118 FETCH (FLAGS () UID 118) * 119 FETCH (FLAGS (\Seen) UID 119) * 120 FETCH (FLAGS (\Answered \Seen) UID 120) * 121 FETCH (FLAGS (\Seen) UID 121) * 122 FETCH (FLAGS (\Seen) UID 122) * 123 FETCH (FLAGS (\Seen) UID 123) * 124 FETCH (FLAGS () UID 124) * 125 FETCH (FLAGS (\Seen) UID 125) * 126 FETCH (FLAGS (\Seen) UID 126) * 127 FETCH (FLAGS (\Seen) UID 127) * 128 FETCH (FLAGS (\Seen) UID 128) * 129 FETCH (FLAGS (\Seen) UID 129) * 130 FETCH (FLAGS (\Seen) UID 130) * 131 FETCH (FLAGS (\Seen) UID 131) * 132 FETCH (FLAGS (\Seen) UID 132) * 133 FETCH (FLAGS (\Seen) UID 133) * 134 FETCH (FLAGS (\Seen) UID 134) * 135 FETCH (FLAGS (\Seen) UID 135) * 136 FETCH (FLAGS (\Seen) UID 136) * 137 FETCH (FLAGS (\Seen) UID 137) * 138 FETCH (FLAGS () UID 138) * 139 FETCH (FLAGS () UID 139) * 140 FETCH (FLAGS () UID 140) * 141 FETCH (FLAGS () UID 141) * 142 FETCH (FLAGS (\Seen) UID 142) * 143 FETCH (FLAGS (\Seen) UID 143) * 144 FETCH (FLAGS (\Answered \Seen) UID 144) * 145 FETCH (FLAGS () UID 145) * 146 FETCH (FLAGS () UID 146) * 147 FETCH (FLAGS (\Seen) UID 147) * 148 FETCH (FLAGS () UID 148) * 149 FETCH (FLAGS (\Seen) UID 149) * 150 FETCH (FLAGS () UID 150) * 151 FETCH (FLAGS (\Seen) UID 151) * 152 FETCH (FLAGS (\Seen) UID 152) * 153 FETCH (FLAGS () UID 153) * 154 FETCH (FLAGS () UID 154) * 155 FETCH (FLAGS () UID 155) * 156 FETCH (FLAGS () UID 156) * 157 FETCH (FLAGS (\Flagged) UID 157) * 158 FETCH (FLAGS () UID 158) * 159 FETCH (FLAGS () UID 159) * 160 FETCH (FLAGS () UID 160) * 161 FETCH (FLAGS () UID 161) * 162 FETCH (FLAGS () UID 162) * 163 FETCH (FLAGS () UID 163) * 164 FETCH (FLAGS (\Seen) UID 164) * 165 FETCH (FLAGS () UID 165) * 166 FETCH (FLAGS () UID 166) * 167 FETCH (FLAGS () UID 167) * 168 FETCH (FLAGS () UID 168) * 169 FETCH (FLAGS () UID 169) * 170 FETCH (FLAGS () UID 170) * 171 FETCH (FLAGS () UID 171) * 172 FETCH (FLAGS () UID 172) * 173 FETCH (FLAGS () UID 173) * 174 FETCH (FLAGS (\Seen) UID 174) * 175 FETCH (FLAGS () UID 175) * 176 FETCH (FLAGS () UID 176) * 177 FETCH (FLAGS (\Seen) UID 177) * 178 FETCH (FLAGS () UID 178) * 179 FETCH (FLAGS () UID 179) * 180 FETCH (FLAGS () UID 180) * 181 FETCH (FLAGS () UID 181) * 182 FETCH (FLAGS (\Seen) UID 182) * 183 FETCH (FLAGS (\Seen) UID 183) * 184 FETCH (FLAGS (\Seen) UID 184) * 185 FETCH (FLAGS (\Seen) UID 185) * 186 FETCH (FLAGS (\Seen) UID 186) * 187 FETCH (FLAGS () UID 187) * 188 FETCH (FLAGS () UID 188) * 189 FETCH (FLAGS () UID 189) * 190 FETCH (FLAGS () UID 190) * 191 FETCH (FLAGS (\Seen) UID 191) * 192 FETCH (FLAGS (\Seen) UID 192) * 193 FETCH (FLAGS () UID 193) * 194 FETCH (FLAGS () UID 194) * 195 FETCH (FLAGS () UID 195) * 196 FETCH (FLAGS (\Seen) UID 196) * 197 FETCH (FLAGS (\Seen) UID 197) * 198 FETCH (FLAGS () UID 198) * 199 FETCH (FLAGS () UID 199) * 200 FETCH (FLAGS () UID 200) * 201 FETCH (FLAGS (\Seen) UID 201) * 202 FETCH (FLAGS (\Seen) UID 202) * 203 FETCH (FLAGS () UID 203) * 204 FETCH (FLAGS (\Answered \Seen) UID 204) * 205 FETCH (FLAGS (\Seen) UID 205) * 206 FETCH (FLAGS () UID 206) * 207 FETCH (FLAGS (\Seen) UID 207) * 208 FETCH (FLAGS (\Seen) UID 208) * 209 FETCH (FLAGS (\Answered \Seen) UID 209) * 210 FETCH (FLAGS (\Seen) UID 210) * 211 FETCH (FLAGS (\Answered \Seen) UID 211) * 212 FETCH (FLAGS (\Seen) UID 212) * 213 FETCH (FLAGS (\Seen) UID 213) * 214 FETCH (FLAGS () UID 214) * 215 FETCH (FLAGS (\Answered \Seen) UID 215) * 216 FETCH (FLAGS (\Seen) UID 216) * 217 FETCH (FLAGS () UID 217) * 218 FETCH (FLAGS (\Answered \Seen) UID 218) * 219 FETCH (FLAGS () UID 219) * 220 FETCH (FLAGS () UID 220) * 221 FETCH (FLAGS (\Seen) UID 221) * 222 FETCH (FLAGS () UID 222) * 223 FETCH (FLAGS (\Seen) UID 223) * 224 FETCH (FLAGS (\Answered \Seen) UID 224) * 225 FETCH (FLAGS (\Seen) UID 225) * 226 FETCH (FLAGS (\Seen) UID 226) * 227 FETCH (FLAGS (\Seen) UID 227) * 228 FETCH (FLAGS () UID 228) * 229 FETCH (FLAGS (\Seen) UID 229) * 230 FETCH (FLAGS (\Seen) UID 230) * 231 FETCH (FLAGS () UID 231) * 232 FETCH (FLAGS () UID 232) * 233 FETCH (FLAGS () UID 233) * 234 FETCH (FLAGS (\Seen) UID 234) * 235 FETCH (FLAGS (\Seen) UID 235) * 236 FETCH (FLAGS (\Seen) UID 236) * 237 FETCH (FLAGS (\Seen) UID 237) * 238 FETCH (FLAGS (\Seen) UID 238) * 239 FETCH (FLAGS () UID 239) * 240 FETCH (FLAGS () UID 240) * 241 FETCH (FLAGS () UID 241) * 242 FETCH (FLAGS () UID 242) * 243 FETCH (FLAGS () UID 243) * 244 FETCH (FLAGS (\Seen) UID 244) * 245 FETCH (FLAGS (\Seen) UID 245) * 246 FETCH (FLAGS () UID 246) * 247 FETCH (FLAGS () UID 247) * 248 FETCH (FLAGS () UID 248) * 249 FETCH (FLAGS () UID 249) * 250 FETCH (FLAGS (\Seen) UID 250) * 251 FETCH (FLAGS (\Seen) UID 251) * 252 FETCH (FLAGS () UID 252) * 253 FETCH (FLAGS (\Seen) UID 253) * 254 FETCH (FLAGS () UID 254) * 255 FETCH (FLAGS () UID 255) * 256 FETCH (FLAGS (\Seen) UID 256) * 257 FETCH (FLAGS () UID 257) * 258 FETCH (FLAGS () UID 258) * 259 FETCH (FLAGS (\Seen) UID 259) * 260 FETCH (FLAGS (\Flagged \Seen) UID 260) * 261 FETCH (FLAGS () UID 261) * 262 FETCH (FLAGS () UID 262) * 263 FETCH (FLAGS () UID 263) * 264 FETCH (FLAGS () UID 264) * 265 FETCH (FLAGS () UID 265) * 266 FETCH (FLAGS (\Seen) UID 266) * 267 FETCH (FLAGS () UID 267) * 268 FETCH (FLAGS () UID 268) * 269 FETCH (FLAGS () UID 269) * 270 FETCH (FLAGS () UID 270) * 271 FETCH (FLAGS () UID 271) * 272 FETCH (FLAGS () UID 272) * 273 FETCH (FLAGS () UID 273) * 274 FETCH (FLAGS () UID 274) * 275 FETCH (FLAGS () UID 275) * 276 FETCH (FLAGS () UID 276) * 277 FETCH (FLAGS () UID 277) * 278 FETCH (FLAGS (\Seen) UID 278) * 279 FETCH (FLAGS () UID 279) * 280 FETCH (FLAGS (\Seen) UID 280) * 281 FETCH (FLAGS () UID 281) * 282 FETCH (FLAGS (\Seen) UID 282) * 283 FETCH (FLAGS () UID 283) * 284 FETCH (FLAGS (\Seen) UID 284) * 285 FETCH (FLAGS () UID 285) * 286 FETCH (FLAGS () UID 286) * 287 FETCH (FLAGS () UID 287) * 288 FETCH (FLAGS () UID 288) * 289 FETCH (FLAGS () UID 289) * 290 FETCH (FLAGS () UID 290) * 291 FETCH (FLAGS () UID 291) * 292 FETCH (FLAGS () UID 292) * 293 FETCH (FLAGS () UID 293) * 294 FETCH (FLAGS () UID 294) * 295 FETCH (FLAGS (\Seen) UID 295) * 296 FETCH (FLAGS (\Seen) UID 296) * 297 FETCH (FLAGS () UID 297) * 298 FETCH (FLAGS () UID 298) * 299 FETCH (FLAGS () UID 299) * 300 FETCH (FLAGS () UID 300) * 301 FETCH (FLAGS () UID 301) * 302 FETCH (FLAGS (\Seen) UID 302) * 303 FETCH (FLAGS (\Answered \Seen) UID 303) * 304 FETCH (FLAGS () UID 304) * 305 FETCH (FLAGS (\Seen) UID 305) * 306 FETCH (FLAGS () UID 306) * 307 FETCH (FLAGS () UID 307) * 308 FETCH (FLAGS () UID 308) * 309 FETCH (FLAGS () UID 309) * 310 FETCH (FLAGS (\Seen) UID 310) * 311 FETCH (FLAGS () UID 311) * 312 FETCH (FLAGS () UID 312) * 313 FETCH (FLAGS (\Answered \Seen) UID 313) * 314 FETCH (FLAGS () UID 314) * 315 FETCH (FLAGS (\Seen) UID 315) * 316 FETCH (FLAGS (\Seen) UID 316) * 317 FETCH (FLAGS (\Seen) UID 317) * 318 FETCH (FLAGS () UID 318) * 319 FETCH (FLAGS () UID 319) * 320 FETCH (FLAGS () UID 320) * 321 FETCH (FLAGS (\Seen) UID 321) * 322 FETCH (FLAGS () UID 322) * 323 FETCH (FLAGS () UID 323) * 324 FETCH (FLAGS (\Seen) UID 324) * 325 FETCH (FLAGS () UID 325) * 326 FETCH (FLAGS () UID 326) * 327 FETCH (FLAGS () UID 327) * 328 FETCH (FLAGS () UID 328) * 329 FETCH (FLAGS () UID 329) * 330 FETCH (FLAGS (\Seen) UID 330) * 331 FETCH (FLAGS (\Seen) UID 331) * 332 FETCH (FLAGS (\Seen) UID 332) * 333 FETCH (FLAGS () UID 333) * 334 FETCH (FLAGS (\Seen) UID 334) * 335 FETCH (FLAGS () UID 335) * 336 FETCH (FLAGS () UID 336) * 337 FETCH (FLAGS () UID 337) * 338 FETCH (FLAGS (\Seen) UID 338) * 339 FETCH (FLAGS () UID 339) * 340 FETCH (FLAGS (\Seen) UID 340) * 341 FETCH (FLAGS () UID 341) * 342 FETCH (FLAGS () UID 342) * 343 FETCH (FLAGS () UID 343) * 344 FETCH (FLAGS () UID 344) * 345 FETCH (FLAGS (\Seen) UID 345) * 346 FETCH (FLAGS () UID 346) * 347 FETCH (FLAGS () UID 347) * 348 FETCH (FLAGS () UID 348) * 349 FETCH (FLAGS () UID 349) * 350 FETCH (FLAGS () UID 350) * 351 FETCH (FLAGS () UID 351) * 352 FETCH (FLAGS () UID 352) * 353 FETCH (FLAGS () UID 353) * 354 FETCH (FLAGS (\Seen) UID 354) * 355 FETCH (FLAGS (\Seen) UID 355) * 356 FETCH (FLAGS (\Seen) UID 356) * 357 FETCH (FLAGS () UID 357) * 358 FETCH (FLAGS () UID 358) * 359 FETCH (FLAGS () UID 359) * 360 FETCH (FLAGS (\Seen) UID 360) * 361 FETCH (FLAGS () UID 361) * 362 FETCH (FLAGS (\Seen) UID 362) * 363 FETCH (FLAGS (\Seen) UID 363) * 364 FETCH (FLAGS (\Seen) UID 364) * 365 FETCH (FLAGS (\Seen) UID 365) * 366 FETCH (FLAGS (\Seen) UID 366) * 367 FETCH (FLAGS () UID 367) * 368 FETCH (FLAGS (\Seen) UID 368) * 369 FETCH (FLAGS (\Answered \Seen) UID 369) * 370 FETCH (FLAGS (\Seen) UID 370) * 371 FETCH (FLAGS (\Seen) UID 371) * 372 FETCH (FLAGS () UID 372) * 373 FETCH (FLAGS (\Seen) UID 373) * 374 FETCH (FLAGS (\Answered \Seen) UID 374) * 375 FETCH (FLAGS (\Seen) UID 375) * 376 FETCH (FLAGS (\Answered \Seen) UID 376) * 377 FETCH (FLAGS () UID 377) * 378 FETCH (FLAGS (\Answered \Seen) UID 378) * 379 FETCH (FLAGS (\Seen) UID 379) * 380 FETCH (FLAGS (\Seen) UID 380) * 381 FETCH (FLAGS () UID 381) * 382 FETCH (FLAGS (\Answered \Seen) UID 382) * 383 FETCH (FLAGS (\Seen) UID 383) * 384 FETCH (FLAGS (\Seen) UID 384) * 385 FETCH (FLAGS () UID 385) * 386 FETCH (FLAGS (\Answered \Seen) UID 386) * 387 FETCH (FLAGS (\Seen) UID 387) * 388 FETCH (FLAGS () UID 388) * 389 FETCH (FLAGS (\Seen) UID 389) * 390 FETCH (FLAGS () UID 390) * 391 FETCH (FLAGS () UID 391) * 392 FETCH (FLAGS () UID 392) * 393 FETCH (FLAGS (\Seen) UID 393) * 394 FETCH (FLAGS () UID 394) * 395 FETCH (FLAGS () UID 395) * 396 FETCH (FLAGS (\Seen) UID 396) * 397 FETCH (FLAGS (\Answered \Seen) UID 397) * 398 FETCH (FLAGS (\Seen) UID 398) * 399 FETCH (FLAGS (\Seen) UID 399) * 400 FETCH (FLAGS (\Seen) UID 400) * 401 FETCH (FLAGS () UID 401) * 402 FETCH (FLAGS () UID 402) * 403 FETCH (FLAGS (\Seen) UID 403) * 404 FETCH (FLAGS (\Seen) UID 404) * 405 FETCH (FLAGS () UID 405) * 406 FETCH (FLAGS () UID 406) * 407 FETCH (FLAGS () UID 407) * 408 FETCH (FLAGS () UID 408) * 409 FETCH (FLAGS () UID 409) * 410 FETCH (FLAGS (\Seen) UID 410) * 411 FETCH (FLAGS () UID 411) * 412 FETCH (FLAGS () UID 412) * 413 FETCH (FLAGS (\Seen) UID 413) * 414 FETCH (FLAGS (\Answered \Seen) UID 414) * 415 FETCH (FLAGS () UID 415) * 416 FETCH (FLAGS (\Seen) UID 416) * 417 FETCH (FLAGS () UID 417) * 418 FETCH (FLAGS (\Seen) UID 418) * 419 FETCH (FLAGS () UID 419) * 420 FETCH (FLAGS (\Seen) UID 420) * 421 FETCH (FLAGS (\Seen) UID 421) * 422 FETCH (FLAGS () UID 422) * 423 FETCH (FLAGS () UID 423) * 424 FETCH (FLAGS (\Seen) UID 424) * 425 FETCH (FLAGS () UID 425) * 426 FETCH (FLAGS (\Seen) UID 426) * 427 FETCH (FLAGS (\Seen) UID 427) * 428 FETCH (FLAGS (\Seen) UID 428) * 429 FETCH (FLAGS () UID 429) * 430 FETCH (FLAGS () UID 430) * 431 FETCH (FLAGS () UID 431) * 432 FETCH (FLAGS () UID 432) * 433 FETCH (FLAGS () UID 433) * 434 FETCH (FLAGS () UID 434) * 435 FETCH (FLAGS () UID 435) * 436 FETCH (FLAGS () UID 436) * 437 FETCH (FLAGS () UID 437) * 438 FETCH (FLAGS () UID 438) * 439 FETCH (FLAGS () UID 439) * 440 FETCH (FLAGS () UID 440) * 441 FETCH (FLAGS (\Seen) UID 441) * 442 FETCH (FLAGS () UID 442) * 443 FETCH (FLAGS (\Seen) UID 443) * 444 FETCH (FLAGS () UID 444) * 445 FETCH (FLAGS () UID 445) * 446 FETCH (FLAGS () UID 446) * 447 FETCH (FLAGS (\Seen) UID 447) * 448 FETCH (FLAGS (\Seen) UID 448) * 449 FETCH (FLAGS (\Seen) UID 449) * 450 FETCH (FLAGS (\Seen) UID 450) * 451 FETCH (FLAGS (\Seen) UID 451) * 452 FETCH (FLAGS () UID 452) * 453 FETCH (FLAGS () UID 453) * 454 FETCH (FLAGS () UID 454) * 455 FETCH (FLAGS () UID 455) * 456 FETCH (FLAGS () UID 456) * 457 FETCH (FLAGS (\Seen) UID 457) * 458 FETCH (FLAGS (\Answered \Seen) UID 458) * 459 FETCH (FLAGS () UID 459) * 460 FETCH (FLAGS () UID 460) * 461 FETCH (FLAGS (\Seen) UID 461) * 462 FETCH (FLAGS (\Seen) UID 462) * 463 FETCH (FLAGS (\Seen) UID 463) * 464 FETCH (FLAGS () UID 464) * 465 FETCH (FLAGS () UID 465) * 466 FETCH (FLAGS () UID 466) * 467 FETCH (FLAGS () UID 467) * 468 FETCH (FLAGS () UID 468) * 469 FETCH (FLAGS (\Seen) UID 469) * 470 FETCH (FLAGS () UID 470) * 471 FETCH (FLAGS () UID 471) * 472 FETCH (FLAGS () UID 472) * 473 FETCH (FLAGS (\Seen) UID 473) * 474 FETCH (FLAGS () UID 474) * 475 FETCH (FLAGS () UID 475) * 476 FETCH (FLAGS (\Seen) UID 476) * 477 FETCH (FLAGS (\Seen) UID 477) * 478 FETCH (FLAGS (\Seen) UID 478) * 479 FETCH (FLAGS () UID 479) * 480 FETCH (FLAGS () UID 480) * 481 FETCH (FLAGS (\Seen) UID 481) * 482 FETCH (FLAGS () UID 482) * 483 FETCH (FLAGS () UID 483) * 484 FETCH (FLAGS (\Seen) UID 484) * 485 FETCH (FLAGS () UID 485) * 486 FETCH (FLAGS (\Answered \Seen) UID 486) * 487 FETCH (FLAGS (\Seen) UID 487) * 488 FETCH (FLAGS () UID 488) * 489 FETCH (FLAGS (\Answered \Seen) UID 489) * 490 FETCH (FLAGS () UID 490) * 491 FETCH (FLAGS () UID 491) * 492 FETCH (FLAGS (\Answered \Seen) UID 492) * 493 FETCH (FLAGS (\Seen) UID 493) * 494 FETCH (FLAGS () UID 494) * 495 FETCH (FLAGS (\Seen) UID 495) * 496 FETCH (FLAGS () UID 496) * 497 FETCH (FLAGS (\Seen) UID 497) * 498 FETCH (FLAGS (\Seen) UID 498) * 499 FETCH (FLAGS (\Seen) UID 499) * 500 FETCH (FLAGS () UID 500) * 501 FETCH (FLAGS () UID 501) * 502 FETCH (FLAGS (\Answered \Seen) UID 502) * 503 FETCH (FLAGS () UID 503) * 504 FETCH (FLAGS (\Seen) UID 504) * 505 FETCH (FLAGS (\Seen) UID 505) * 506 FETCH (FLAGS (\Seen) UID 506) * 507 FETCH (FLAGS () UID 507) * 508 FETCH (FLAGS (\Seen) UID 508) * 509 FETCH (FLAGS (\Seen) UID 509) * 510 FETCH (FLAGS () UID 510) * 511 FETCH (FLAGS () UID 511) * 512 FETCH (FLAGS () UID 512) * 513 FETCH (FLAGS (\Seen) UID 513) * 514 FETCH (FLAGS () UID 514) * 515 FETCH (FLAGS (\Seen) UID 515) * 516 FETCH (FLAGS (\Answered \Seen) UID 516) * 517 FETCH (FLAGS (\Seen) UID 517) * 518 FETCH (FLAGS () UID 564) * 519 FETCH (FLAGS () UID 570) * 520 FETCH (FLAGS () UID 571) * 521 FETCH (FLAGS (\Seen) UID 572) * 522 FETCH (FLAGS () UID 576) 0000000d OK Fetch completed. 0000000e OK NOOP completed. * SEARCH 0000000f OK Search completed. * 1 FETCH (UID 1 INTERNALDATE "05-Jan-2002 06:03:50 -0500" RFC822.SIZE 1606 FLAGS (\Seen) ENVELOPE ("Sat, 5 Jan 2002 12:03:14 +0100" "further m4 change" (("Marc Espie" NIL "espie" "schutzenberger.liafa.jussieu.fr")) (("Marc Espie" NIL "espie" "schutzenberger.liafa.jussieu.fr")) ((NIL NIL "Marc.Espie" "liafa.jussieu.fr")) (("Todd Vierling" NIL "tv" "wasabisystems.com")) NIL NIL "<Pine.WNT.4.40.0111140959180.284-100000@todd>; from tv(a)wasabisystems.com on Wed, Nov 14, 2001 at 10:21:15AM -0500" "<20020105120314.A17920(a)schutzenberger.liafa.jussieu.fr>") BODY[HEADER.FIELDS (DATE X-PRIORITY X-BYNARI-FOLDER-CLASS X-PR-CONTAINER-CLASS X-MESSAGE-FLAG RECEIVED)] {769} Received: from mononoke.wasabisystems.com (lion.ninthwonder.com [151.199.66.147]) by mail.duh.org (8.11.3nb1/8.11.3/dsb-1.2a1) with ESMTP id g05B2d618330 for <tv+wasabi(a)duh.org>; Sat, 5 Jan 2002 06:02:39 -0500 (EST) Received: by mononoke.wasabisystems.com (Postfix) id 015A030709; Sat, 5 Jan 2002 06:03:17 -0500 (EST) Received: from schutzenberger.liafa.jussieu.fr (schutzenberger.liafa.jussieu.fr [132.227.81.123]) by mononoke.wasabisystems.com (Postfix) with ESMTP id 741E030706 for <tv(a)wasabisystems.com>; Sat, 5 Jan 2002 06:03:16 -0500 (EST) Received: (from espie@localhost) by schutzenberger.liafa.jussieu.fr (8.11.3/8.10.1) id g05B3Fa00656 for tv(a)wasabisystems.com; Sat, 5 Jan 2002 12:03:15 +0100 (CET) Date: Sat, 5 Jan 2002 12:03:14 +0100 BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 207 3 NIL ("inline" NIL) NIL)) * 2 FETCH (UID 2 INTERNALDATE "30-Dec-2001 21:59:14 -0500" RFC822.SIZE 1083 FLAGS (\Seen) ENVELOPE ("Sun, 30 Dec 2001 19:07:28 -0800" "Registration information at I-Appliance BBS (http://www.linux-hacker.net)" ((NIL NIL "codeman" "linux-hacker.net")) ((NIL NIL "codeman" "linux-hacker.net")) ((NIL NIL "codeman" "linux-hacker.net")) ((NIL NIL "tv" "duh.org")) NIL NIL NIL "<200112310307.fBV37SV08829(a)www.linux-hacker.net>") BODY[HEADER.FIELDS (DATE X-PRIORITY X-BYNARI-FOLDER-CLASS X-PR-CONTAINER-CLASS X-MESSAGE-FLAG RECEIVED)] {376} Received: from www.linux-hacker.net (www.linux-hacker.net [12.110.32.118]) by mail.duh.org (8.11.3nb1/8.11.3/dsb-1.2a1) with ESMTP id fBV2vqg21976 for <tv(a)duh.org>; Sun, 30 Dec 2001 21:57:52 -0500 (EST) Received: (from admin@localhost) by www.linux-hacker.net (8.10.2/8.10.2) id fBV37SV08829; Sun, 30 Dec 2001 19:07:28 -0800 Date: Sun, 30 Dec 2001 19:07:28 -0800 BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 470 17 NIL NIL NIL)) -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

2 2

[Dovecot] Moving folder issue
by Andrew Hutchings 07 Aug '05

07 Aug '05

Hi, My wife who has thousands of IMAP boxes keeps getting errors when moving mailboxes in Thunderbird in Windows. I am using the same server (dovecot test 77) with Thunderbird in Linux and don't see the problem. What happens is she moves the mail box and Thunderbird comes up with an error saying it can't access the old box (odd!?). It has however completed the move. The following is what I got from logging, any ideas?: in log: 1843 lsub "" "eBay.Sales - Current.Ready to post.lollipop letters.*" 1844 close 1845 rename "eBay.Sales - Current.Ready to post.lollipop letters" "eBay.Sales - Complete.lollipop letters" 1846 subscribe "eBay.Sales - Complete.lollipop letters" 1847 unsubscribe "eBay.Sales - Current.Ready to post.lollipop letters" 1848 select "eBay.Sales - Complete.lollipop letters" out log: 1843 OK Lsub completed. 1844 OK Close completed. 1845 OK Rename completed. 1846 OK Subscribe completed. 1847 OK Unsubscribe completed. 1848 NO Internal error occured. Refer to server log for more information. [2005-08-01 20:59:50] server log: Aug 1 20:59:50 sever dovecot: IMAP(natalie): stat() failed with file /home/natalie/Maildir/.eBay.Sales - Current.Ready to post.lollipop letters/dovecot.index.log: No such file or directory Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 4: "Avoid the Gates of Hell. Use Linux" - Unknown

2 1

[Dovecot] Canot move messages out of my inbox
by _ 07 Aug '05

07 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm using thunderbird on top of Maildir, dovecot latest. For some weeks i cannot move messages out of the inbox folder anymore. Looking at the logfile, i see Error: child 19591 (imap) killed with signal 1 which by now is the only error i can see. I have already compared permissions on working folders with the inbox, all are the same (rwx, owner, owner). Any ideas? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2rc1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC60HQA+RTBSZx+AcRAnXEAJ9fpA4qbQaGf34fHMnMior515/LRACfYgj5 W+uOx4kJfKdKEJVckvp2Xcc= =Kezu -----END PGP SIGNATURE-----

2 1

[Dovecot] [PATCH] settings parsing section/context return bug
by Tom Alsberg 07 Aug '05

07 Aug '05

There seems to be a minor bug in the settings parsing code (as of today's dovecot-stable snapshot - 20050731) - after the closing bracket of protocol (imap/pop3) {} section, the parser still regards all options as affecting only that protocol and not globally (I have some options, protocol imap {}, protocol pop3 {}, and then some more options - now those latter options seem to only affect POP3). It seems to be solved by the attached patch. Merely that the sub-section level has to be decreased after checking that it is positive (for returning the protocol in context to ANY). Would that change (prefix to postfix decrement) break anything else? If not, can it be applied? -- 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.

2 1

[Dovecot] 1.0 stable 20050725 assert, signal 6
by Jeff A. Earickson 07 Aug '05

07 Aug '05

Hi, I was brave enough to upgrade from UW-imap to stable 1.0 20050725 today for our IMAP service. I have seen a few of the following in my syslog: Jul 26 15:37:18 emerald dovecot: [ID 107833 mail.error] IMAP(bjkupke): file mbox -sync-update.c: line 372: assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid == mail->uid) Jul 26 15:37:18 emerald dovecot: [ID 684838 mail.error] child 16755 (imap) kille d with signal 6 Only for user bjkupke; his mailbox is not corrupted when I open it with Pine. My setup: Solaris 9, configured dovecot like so: CC=cc CFLAGS="-g" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug > configure.out Using Sunstudio 9 compiler. I can't find any core files lying around. Bug? Problem? Suggestions please? BTW, are there searchable dovecot list archives someplace? Jeff Earickson Colby College

2 1

[Dovecot] Compile trouble with mysql
by Michael Goth 06 Aug '05

06 Aug '05

Hello! I tried to compile the latest 1.0-test (79) with mysql support, but there is the following error: ... /usr/local/mysql/lib/libmysqlclient.a(sha1.o)(.text+0x5c): In function `sha1_result': : multiple definition of `sha1_result' ../lib/liblib.a(sha1.o)(.text+0x830):/usr/local/src/dovecot/dovecot-1.0-test79/src/lib/sha1.c:233: first defined here ... So 'sha1_result' is defined by mysqlclient and dovecot. This is an issue I already reported some time ago. According to a search in the list archives, it seems no one else has this problem. But there must be more people using dovecot with MySQL support. Probably this only happens with the statically linked MySQL version from mysql.org? I'd really appreciate any help on this, as I have to set up a new mail server quickly (and Courier just doesn't work the way I want it to). Thanks, Michael

2 1

[Dovecot] Help with Virtual user setup.. need pointers
by Andre Bunting 03 Aug '05

03 Aug '05

I have been reading this : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql I decide to use the postgresql instead of mysql.. but now i am in problem.. I cant seem to get postfix-pgsql sasl2-bin libsasl2-modules libpam-pgsql rpms or files for the fedora core 4.. Is there anyone who is using Fedora Core 4.. and have dovecot.. with postifx running virtual users ... or is there another way besides the link ontop to do this ? Andre Bunting Information Technology Manager Integrated Telecommunication Consultants Limited Unit No.1 - Ground Floor, 23 -27 Eastern Main Road, Barataria, Trinidad, West Indies. Telephone : 675-1438 Cell: 748-8587

1 0

[Dovecot] when will the version 1.0 released ...
by wiki kaha 03 Aug '05

03 Aug '05

Hi all. I work with the version 0.99.14 on an openbsd. There are an issue with b-tree and maybe something more. I know about the 1.x-test versions but they will never be in the ports on freebsd and openbsd because of the funny title "*-test..." This looks like an RC and the half world is waiting for a release. Is there no way to release a version so that the port world can go around :) I'm looking forward. ps: great software! regards ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

1 0

[Dovecot] Default_mail_env..
by Guillermo Llenas 02 Aug '05

02 Aug '05

Hi, I 'm new to Dovecot and we are trying to do some tests in a production environment. We use mysql to authenticate and dovecot imap only. But our structure directory is something special. All of ours accounts are stored in maildir and the path is the following: For example the account pepe(a)inter.net /export/maildir/inter.net/p/e/pepe and into pepe we have cur, tmp, new. This is a problem because we cannot modify the database adding home for all users, so in the other side I played with the default_mail_env default_mail_env = maildir:/export/maildir/%d/%1u/%2u/%n:INBOX=/export/maildir/%d/%1u/%2u/%n but didn't wok out. Because imap(pepe(a)inter.net): Aug 01 18:26:04 Fatal: Failed to create storage with data: INBOX=/export/maildir/inter.net/p/pe/pepe I need only export / maildir / domain / first letter of the username / second letter / and last username Is there any way to do this ?, thanks in advance -- Guillermo Llenas Tecnología Inter.net Argentina ________________________ +54 011 6328-1500 fax 0054 11 6328-1530 www.ar.inter.net guillermo.llenas(a)team.ar.inter.net

2 2

[Dovecot] where is "pam_listfile.so" for static userdb?
by OpenMacNews 02 Aug '05

02 Aug '05

hi all, i'm setting up Dovecot on OSX to use PAM authentication against a flat_file/static userdb (tho i will _eventually_ mv to pgsql ...). iiuc, to do so i need something like: =================================== (EDITOR) /etc/pam.d/dovecot.imap auth required pam_listfile.so item=user sense=allow file=/var/dovecot/imapusers onerr=fail =================================== for a userdb listing in "/var/imapuser". all simple & good, except -- -- where's "pam_listfile.so" on OSX? % ls /usr/lib/pam/ pam_afpmount.so pam_nologin.so pam_securetty.so pam_uwtmp.so pam_deny.so pam_permit.so pam_securityserver.so pam_wheel.so pam_netinfo.so pam_rootok.so pam_unix.so do i have to grab-n-install it from somewhere? or are one of these ^ an 'equivalent' ... this _should_ be simple :-} thanks, richard

1 0

[Dovecot] Feature request - umask for index files
by Marc Perkel 02 Aug '05

02 Aug '05

I'd like a separate feature for setting umask for index and cache files differently from email files. The reason is that I'm putting indexes in a separate location and I need group create rights in directories. Otherwise what happens is that the first user creates the directories, but the second user for the domain that has a different UID gets an error. default_mail_env = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX:INDEX=/nobackup/imap-index/%d/%n -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 2

[Dovecot] wiki's howto and mailman
by kramer＠freemail.it 02 Aug '05

02 Aug '05

hello, i've implemented this on my mailserver : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql but now mailman is broken. This is the error i got from postfix: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) of course the user mylist(a)mydomain.org does not exsist on the postgres db, but how i can fix this issue? someone wanna help, please? thanks, peppe --------------------------------------------------------------- Scegli il tuo dominio preferito e attiva la tua email! Da oggi l'eMail di superEva e' ancora piu' veloce e ricca di funzioni! http://webmail.supereva.it/new/ ---------------------------------------------------------------

2 1

[Dovecot] Not the server can do anything about it, but...
by Stewart Dean 01 Aug '05

01 Aug '05

WIBNI if the clients' message composition windows displayed the size of the prospective outgoing message as a color-coded BIG number... <50K green <200K yellow <500K orange >1MB red ...or some such.. Idiot clueless users occasionally send inadvertantly huge messages...the problem is that there is currently no feedback loop (like this suggestion)....nobody would mail a 100 pound hardcopy 'quick' USPS note to Aunt Mildred, but they're often doing the equivalent in email. If you bump into any client designers, give them the suggestion -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] Just converted to Dovecot
by Marc Perkel 31 Jul '05

31 Jul '05

I'm using Test79 - wish me luck! Seems to be working ....... -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

Re: [Dovecot] Supporting charsets
by Alan Premselaar 29 Jul '05

29 Jul '05

Peter Evans wrote: > Armando Soto Baeza (asbaeza(a)catsanet.com.mx) wrote: > >>We are trying to use support for japanese language, but when composing in >>squirrelmail or while resending either in squirrel or in Outlook, we do >>not get the right symbols. > > > Send me an email, in Japanese. > 私に日本語メール送ってくれませんか？ > > 妻もＤＯＶＥＣＯＴを使っているけどほとんど問題なし。 > > > ぴ > > > I'm also using Dovecot in a Japanese intensive environment with no problems. I would venture to guess that this is either a problem with the squirrelmail installation or the MTA. I'm also using a recent version of Squirrelmail in Japanese without any problems. Earlier versions had some issues (like if you had SM set to english menu mode and tried to read or send Japanese, it would appear as 'mojibake' ... that seems to have been fixed in the most recent release) for what it's worth, this mail that I'm replying to came across without any issues whatsoever. alan

1 0

[Dovecot] Outlook + Outlook Express
by Andrew Gargan 29 Jul '05

29 Jul '05

Hi I am having problems with users accessing their maildir mail stores through dovecot I am working on version 0.99.11-1 (on fedora core) It seems to be when the email size is large (450KB +) The errors are (the server disconnected unexpectedly) Have turned on the three Outlook and Outlook Express workarounds I found but no luck. Have read through logs and looked for clues but am just getting no where ... All the linux boxes here seem to be able to handle things fine ... (kmail evolution etc.) Thunderbird is also giving me hassles when trying to pull large mail files. The server is a 2.8 P4 HT with 1024 MB RAM 200GB SATA RAID. +- 7 domains and +-1200 users. Squirrel Mail seems fine and users are using that to get around the problem for now but I really need the pop3 access working ... My MTA is postfix and I am using virtual mailboxes using mysql_lookups. I am also running MailScanner and ClamAV and SpamAssassin (using the hold queue method) Regards Andrew Andrew Gargan Developer Interface Media (PTY) Ltd. Tel: 011 507 3003

2 3

[Dovecot] Handling virtual domains
by Phillip Davis 28 Jul '05

28 Jul '05

Hello all, I'm Having a sticky problem, and Im pretty sure I've configured dovecot wrong, I just don't know what I'm doing wrong. I have a system running sendmail. I need to sue virtual domains, as several domains will be hosted on this box. I am using squirrelmail for webmail and it has a vlogin plugin that allows me to use virtual domains, and it is working correctly, so far as I can tell. If a user goes to their email domain via http://www.domain.com/webmail/ and logs in, it correctly converts their login from just user that they typed in to user(a)domain.com, and if another domain was domain2.com and they went to http://www.domain2.com/webmail it will send user(a)domain2.com to dovecot. This is where I think I'm doing it wrong. Dovecot seems to just try that username which doesnt exist to the local OS of course, its just user, not user(a)domain.com. I read the part about dovecot using the auth_passdb and auth_userdb but was really confused how it works. if I use those, does it expect sendmail to deliver mail for those virtual domains to a new path I have supplied? also do I have to create a new and separate login and password flat file for it to authenticate? if so, how do I configure sendmail to deliver only those specific mails from each separate user from different virtual domains to be delivered? I'm just trying out the virtual domain thing, and I'm definitely really really confused because it seems each piece of software I have running here wants to do it differently. any pointers, hits or help would greatly be appreciated. -- Phil Phil(a)daviszone.org

1 0

[Dovecot] MySQL authentication
by Andrew Gargan 28 Jul '05

28 Jul '05

Hi I am wanting to install : dovecot 1.0-stable I currently have dovecot 0.99.11-1 which came packaged on Fedora Core 3 It is doing auth off a MySQL db an working well I have downloaded the latest stable tarball and extracted ... I don't see how to enable mysql lookups at compile time... Help please ... I am getting a lot of pressure from the people at work ... Regards Andrew Andrew Gargan Developer Interface Media (PTY) Ltd. Tel: 011 507 3003

2 1

[Dovecot] Need Help About My Problem ( Dovecot / Postfix / MySQL / Postfixadmin )
by Pratchaya Chatuphian 28 Jul '05

28 Jul '05

Dear , Dovecot List ( Everyone ) I have some problem about dovecot/postfix/mysql Would u like to tell me about the solution ? sir Thank you very much for advance. Sir Best Regards, Pratchaya ================================== ================================== ================================== This is my problem/error sir 1. ERROR = "" A NO "" and 2. ERROR = "" -ERR No INBOX for user. " I run Dovecot + Postfix + Postfixadmin + MySQL When i work with command line .. i have problem like this ( When i 'm in command line ) ##############################*###### [root@server etc]# telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK dovecot ready. A LOGIN test...(a)pepocono.com 123456 A OK Logged in. A SELECT inbox A NO A LOGOUT * BYE Logging out A OK Logout completed. Connection closed by foreign host ##############################*###### [root@server etc]# telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK dovecot ready. USER test...(a)pepocono.com +OK PASS 123456 +OK Logged in. -ERR No INBOX for user. Connection closed by foreign host. [root@jenus etc]# ##############################*####### My Config ==============================*======== dvecot.conf ==============================*======== default_mail_env = maildir:/var/mail/virtual/%1u/*%u/Maildir auth = plain auth_mechanisms = plain digest-md5 auth_userdb = mysql /usr/local/etc/dovecot-mysql.c*onf auth_passdb = mysql /usr/local/etc/dovecot-mysql.c*onf auth_user = mailusers ==============================*======== dvecot-mysql.conf ==============================*======== db_host = localhost db_unix_socket = /var/lib/mysql/mysql.sock db = postfix db_user = postfix db_passwd = postfix db_client_flags = 0 password_query = SELECT password FROM mailbox WHERE username = '%u' #user_query = SELECT concat('/var/mail/virtual/', maildir) as home, 10000 as uid, 10000 as gid FROM mailbox WHERE username = '%u' #user_query = SELECT '10000' AS uid, '10000' AS gid FROM mailbox WHERE username = '%u' AND active = '1' #user_query = SELECT home, uid, gid FROM users WHERE user = '%u' user_query = SELECT home, uid, gid FROM users WHERE user = '%u' AND active = '1' ( i use all case #comment but it'doesn't work ) ==============================*======== main.cf ==============================*======== virtual_mailbox_base = /var/mail/virtual virtual_mailbox_domains = mysql:/etc/postfix/postfixmysq*l/mysql_virtual_domains_maps.c*f virtual_mailbox_limit = 51200000 virtual_mailbox_maps = mysql:/etc/postfix/postfixmysq*l/mysql_virtual_mailbox_maps.c*f virtual_alias_domains = $virtual_alias_maps virtual_minimum_uid = 10000 virtual_uid_maps = static:10000 virtual_gid_maps = static:10000 # Additional for quota support virtual_create_maildirsize = yes virtual_mailbox_extended = yes virtual_mailbox_limit_maps = mysql:/etc/postfix/postfixmysq*l/mysql_virtual_mailbox_limit_*maps.cf virtual_mailbox_limit_override = yes virtual_maildir_limit_message = Sorry, the user's maildir has overdrawn his diskspace quota, please try again later. virtual_overquota_bounce = yes ========================= Note ( more information ) :: ========================= mailusers uid=10000 gid = 10000 home = /var/mail/virtual

1 0

[Dovecot] Preventing IMAP folder removal?
by John R. Dennison 28 Jul '05

28 Jul '05

Is there a way to configure Dovecut (version: dovecot-stable) to prevent the removal of an IMAP folder? We are planning on rolling out the @Mail webmail client to our user base in the next few weeks. This package has an internal Spam folder that we use to deliver spam into to allow our users to get to both their main mailbox and also their spam repository in one location. We are a Maildir shop, so the folder appears as: '~username/Maildir/..Spam' We want to use a sym-link to point '..Spam' to a location on another filesystem. Our testing shows that dovecot will happily follow a sym-link properly and no badness occurs as a result. Our concern, however, is that a user will attempt to remove their Spam folder, which will break the symlink and the next time a spam message is delivered the folder will be re-created as a directory and will reside on the same filesystem as their Maildir. Preventing the removal of the folder would be the easiest solution. If such a restriction is not already present in dovecot, might something be added to allow admins to lock down removal of folders? If this question has already been asked and answered on the list I apologize - I did quickly browse some of the back list and did not see a reference to the topic, but I admit, I may have missed it. Thank you in advance, John -- "I'm sorry but our engineers do not have phones." As stated by a Network Solutions Customer Service representative when asked to be put through to an engineer. "My other computer is your windows box." Ralf Hildebrandt

4 3

[Dovecot] Index File Permissions - Perhaps feature Request
by Marc Perkel 27 Jul '05

27 Jul '05

Trying an experiment to put the index files on a different volume than the mailbox files The idea being that the mailbox files are in a limited space slow raid1 array and the index files are somewhere else that is fast and not backed up. I'm using a virtual file structure as follows: /vhome/%d/home/%n The index files are set to: /nobackup/indexes/%d/%n Upon startup it created the index files correctly making all the missing directories. But I have an issue with the permissions. The problem is that it works for the first user, but the second user will have a permission error on the /%d/ level because of the 700 permissions. So - I would like to specify that directories that are automatically created have 770 permissions instead of 700, and, that perhaps I might want to ser the group permissions to 660 instead of 600. This might make Dovecot more ready for shared mailboxes in the future.

1 1

[Dovecot] Master Password Setup
by Marc Perkel 27 Jul '05

27 Jul '05

This should be easy but can someone tell me how to do this. I want to set up a master password to read anyone's email account for tech support reasons. How would you do that?

2 1

[Dovecot] Dovecot, Postfix, Mysql and Virtual Users
by Andre Bunting 27 Jul '05

27 Jul '05

I have been reading up : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql to create virtual users who can access the email. Can i follow these steps with a few changes to get to use mysql instead of Postgresql ? Also i dont know if u all can help.. but i have tried to do : SASL2 authentication configuration in main.cf(Postfix): smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = domain.org smtp_sasl_auth_enable = no And when i start postfix with these settings i get an error saying"invlaid boolean" .. can anyone help ? Regards, Andre

2 1

[Dovecot] Small Feature Dovecot Should Have
by Marc Perkel 27 Jul '05

27 Jul '05

There should be a config command that allows you to change the default ".subscriptions" file to ".mailboxlist" for WU-IMAP compatibility. Yes - I can rename them all but it would be handy for testing purposes and it should be trivial to add this feature. I'm still someone who is going to convert soon, but still testing and waiting for stability.

1 0

[Dovecot] Supporting charsets
by Armando Soto Baeza 27 Jul '05

27 Jul '05

Hi there! We are trying to use support for japanese language, but when composing in squirrelmail or while resending either in squirrel or in Outlook, we do not get the right symbols. The server and client PCs have all the required software. Indeed, we receive japanese written messages and can display them well. The problem arises when we resend or compose a message. In the squirrel configuration, we found that our imap has to support the charsets we want to use. The question is, how can we add this to dovecot. We are using release 0.99.14-1 on GNU Debian 3.1 r0 (sarge) Any idea? Thanks for helping -- Alta tecnologia para la empresa mexicana

2 1

[Dovecot] last access file for 1.0-stable?
by Jeff A. Earickson 26 Jul '05

26 Jul '05

Hi, I am almost ready to convert from UW-imap to dovecot 1.0 stable for my imap use. I hacked UW-imap to touch a file in the user's home directory so I can always tell the last time they used imap. My hack looks something like this: if(authenticated) { touchfile = (char *) malloc((strlen (home) + 15); sprintf(touchfile,"%s/.imapd.last",homedir); fd = open(touchfile,O_WRONLY|O_CREAT|O_TRUNC,0600); if(fd < 0) syslog (LOG_NOTICE|LOG_AUTH,"touchfile failed for %s:%s",user,strerror(errno)); else close(fd); free(touchfile); } Where to do this in the dovecot code? Is there something like this already available? I realize that the index/cache files contain last-access data, but if the cache files become corrupted and have to be removed, then this last-access information is lost. I would like something independent of the cache files. Advice please... Jeff Earickson Colby College

2 1

[Dovecot] Commercial support
by Timo Sirainen 26 Jul '05

26 Jul '05

1.0 release is slowly (but surely :) getting nearer and I'd like to be able to offer commercial support for it for those who want or need it. I have a few different plans for how to do that, but I haven't really decided yet what to do. So I thought I'd ask a few questions here to see how much interest there is currently, which could help me make some decisions sooner. You should probably reply privately to me so this list won't get spammed. So, assume that Dovecot v1.0 will really be stable, will have real documentation, and the support isn't going to be completely in hands of just one or two guys. I think there would basically be two types of support available: 1. Basic support Guaranteed replies to questions within some time interval. - what response times? a few days? - phone support needed? - what would you be willing to pay for it? 2. Mission critical support For those who *really* can't afford any unexpected downtime, and so would be willing to pay more for quick response times. Problems divided to different categories (eg. normal, high, critical) with different response times. - what response times? a few days for normal, about one day for high, less for critical? - sanctions? - customized modifications, kept up-to-date for new Dovecot versions? - what would you be willing to pay for it? I'm not sure if there should be "outsourced email server maintenance" option too. Or maybe some really low cost support for a limited number of questions. Any other ideas, suggestions or tips? Did I miss something important? And finally, would you like to have a job related to Dovecot? :)

2 1

[Dovecot] virtual mailboxes with postfix
by David Cake 26 Jul '05

26 Jul '05

I have set up postfix with virtual mailboxes stored via mysql, and using postfixadmin, and dovecot as pop/imap server My postfix and mysql setup are pretty much standard for postfixadmin, as described here <http://postfixwiki.org/index.php?title=Virtual_Users_and_Domains_with_Couri…> (except for the parts about courier-imap.) Everything appears to be working fine except actually checking and authenticating mail via dovecot. I am fairly sure all I really need is the appropriate incantations in /etc/dovecot/dovecot.conf and dovecot-mysql.conf - does anyone have this set up and working? I should add that I want to allow both virtual mailboxes, and also local accounts, so I presumably need to support two different kinds of authentication. Regards David

2 1

[Dovecot] removing (hopefully) unneeded access to $HOME
by adsmith＠math.duke.edu 25 Jul '05

25 Jul '05

Hi, Thanks for dovecot. It's the best IMAP server ever. Okay, here's my problem: I use mbox INBOXes from /var/spool/mail/%u, and the INDEX lies in /var/spool/mail/dovecot/%d/%u. Users' other folders are found in /%h/mail. Now, I notice that when a user is accessing her INBOX, the imap process cwd's to the user's home, which I'd like to prevent as much as possible. E.g., when the user's client is only watching INBOX, I still see: [root@tock:~]$ lsof | grep home_kt imap 6422 kt cwd DIR 0,17 12288 7602177 /home/kt (other.host:/home/kt) Is there a way I can tweak the dovecot settings so that this cwd isn't holding open the NFS mount? Many thanks, Abe Smith -- # Abraham David Smith, <adsmith(a)math.duke.edu> # # http://fds.duke.edu/db/aas/math/grad/adsmith # # Mathematics Graduate Student, Duke University #

1 1

Re: [Dovecot] pop3 authentication failure - password mismatch
by James Sun 25 Jul '05

25 Jul '05

On 7/22/05, Girish Patangay <girish(a)intoto.com> wrote: > Shouldn't you be using "shadow" instead of passwd for the passdb? > > Just a curious question. > Yes! You are right. "shadow" should work as well. I just give it a try and auth worked! Thanks. However, I am not hitting another problem : no proper permission. If I understand correctly I have set it in dovecot.conf file to use "root" for processing. How come I don't have enough permission? Jul 23 02:26:56 hsiufen dovecot: Dovecot v1.0-stable starting up Jul 23 02:28:10 hsiufen dovecot: pop3-login: Login: jam [24.6.106.170] Jul 23 02:28:10 hsiufen dovecot: POP3(jam): open(/var/mail/.temp.hsiufen.net.15682.f3c4cf83d750e6e4) failed: Permission denied Jul 23 02:28:10 hsiufen dovecot: POP3(jam): file_lock_dotlock() failed with mbox file /var/mail/jam: Permission denied Jul 23 02:28:31 hsiufen dovecot: Killed with signal 2 Any ideas? Jun

3 3

[Dovecot] Re: Bug#319504: Bug in 0.99.14 mbox handling - mail UIDs are renumbered without bumping UIDVALIDITY
by Jaldhar H. Vyas 25 Jul '05

25 Jul '05

On Fri, 22 Jul 2005, David McBride wrote: > Package: dovecot-imapd > Version: 0.99.14-1 > Severity: important > > Hi, > > I think I've identified a bug in Dovecot 0.99.14 as packaged and > distributed by Debian Sarge. I believe the bug lies in the original > Dovecot source, not with any modifications made by Debian. > > Specifically, this bug deals with Dovecot's handling of message unique > identifiers (UIDs) for IMAP clients when using the mbox mailbox storage > format. > David, can you check if the problem persists with 0.99.20050712-1 which is in sid? This is actually the 1.0stable branch of dovecot and has many fixes not included in 0.99.x The package should work correctly on sarge (a proper sarge backport is forthcoming) but you will also need libpq4 from sid and you'll need to make sure dovecot-common is also upgraded to 0.99.20050712-1 also. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

2 1

[Dovecot] dovecot permission denied problems.
by John Mc Donald 25 Jul '05

25 Jul '05

I am trying to setup dovecot on a FC4 machine. Access to the machine is provided through pam. When I login to the machine my home directory is mounted over nfs from a central file server. I have dovecot installed and running but it can't seem to access my home directory. When I try and access my mail I get the following three lines in /var/log/maillog: > Jul 25 12:46:04 escher imap-login: Login: ###### [::ffff:###.###.###.###] > Jul 25 12:46:04 escher dovecot: chdir(/home/######) failed with uid > ####: Permission denied > Jul 25 12:46:04 escher dovecot: child 13182 (imap) returned error 89 The uid that is used is the one associated with my home directory. As far as I understand it when you connect to dovecot the imap connection setuid's to the uid of the authenticated user so there should be no permission problems. To try and help in the debugging process I also setup a local user "testimap" using > /usr/sbin/useradd -d /tmp/testimap testimap I then try to use thunderbird to connect to it and I get the following in /var/log/maillog > Jul 25 12:54:54 escher imap-login: Login: testimap > [::ffff:###.###.###.###] > Jul 25 12:54:54 escher imap(testimap): mbox: Can't create root IMAP > folder /tmp/testimap/mail: Permission denied > Jul 25 12:54:54 escher imap(testimap): MAIL environment missing and > autodetection failed (home /tmp/testimap) > Jul 25 12:54:54 escher dovecot: child 13360 (imap) returned error 89 Can anyone tell me what I am doing wrong here? TIA, John. -- ================================== John Mc Donald, Dept. of Computer Science, National University of Ireland, Maynooth, Co. Kildare, Ireland. Email : johnmcd(a)cs.nuim.ie Tel: +353-1-7084589 Fax: +353-1-7083848 Web: http://www.cs.nuim.ie/~johnmcd GnuPG Key: http://www.cs.nuim.ie/~johnmcd/public_key.asc ==================================

2 2

[Dovecot] inotify support in dovecot
by Reuben Farrelly 25 Jul '05

25 Jul '05

Hi, I note that dovecot supported inotify from -test77, and now the Linux kernel supports it starting from linux-2.6.13-rc3. So in theory I should be set to go. I'm using an -mm kernel, and it was built with inotify, on FC4/devel. However when trying to build with it using --with-notify=inotify, I always seem to be getting this message: checking for poll... yes configure: error: inotify requested but not available, check for existence of <linux/inotify.h> /bin/sh ./config.status --recheck What is required for inotify to be recognised and built into dovecot? I've tried copying the header from linux-2.6/include/linux/inotify.h to the /usr/include/linux directory, but that didn't help - and seems wrong to do anyway. Has anyone else had any experiences with inotify/dovecot? reuben

2 3

[Dovecot] 1.0-test79
by Timo Sirainen 25 Jul '05

25 Jul '05

http://dovecot.org/test/ Now checks that field alignmentations are in indexes as they're expected. test78 crashed if it was wrong, earlier versions ignored the problem (and crashed with 64bit systems). Now if it's wrong, it prints error to log file and recreates the index. That means you probably should delete all dovecot.index files to avoid tons of errors in log files. Only mbox users need to do this. - LSUB: Don't crash if .subscriptions file can't be opened. Also in general give proper "permission denied" error if LIST/LSUB failed because of permission problems. - Maildir: Fix deadlocking when saving messages (noticeable with copying lots of messages with Thunderbird) - LDAP: user_global_uid/gid wasn't working. Also now they support having user/group names from /etc/passwd instead of just numbers. - passwd-file now supports variables in filename, so you can do eg. args = /etc/passwd.%d - Open/close PAM session if -session option is given. Patch by Pasi Sjöholm. - Added tb-extra-mailbox-sep workaround for Thunderbird+mbox problems.

6 9

[Dovecot] dovecot 1.0-stable (050721) rpm for FC3
by James Sun 25 Jul '05

25 Jul '05

OK, thanks for the all the helps I got from the list. I finally managed to get stable 1.0 (050721) built and running. To avoid the same hassels for others, I made an rpm. You can check it out at http://linux.junsun.net/rpms My main motivation to upgrade to this version is to avoid the "Status: O" header re-write bug in 0.99 versions. Cheers. Jun

1 0

[Dovecot] ssl_cipher_list
by Robert Allerstorfer 24 Jul '05

24 Jul '05

Hi, I have noticed the 'ssl_cipher_list' directive in the 1.0-test snapshots which is not in 0.99. It's default value seems to be "all:!low". However, this would not be compatible with openssl's cipher listing format. Thus, I would vote to change it's format to be openssl compatible. To be compatible, it has to be changed to "ALL:!LOW" (just upercased in this case). IMO, this would be helpful because executing openssl ciphers -v 'all:!low' would not return any cipher, but openssl ciphers -v 'ALL:!LOW' would return the expected cipher list such as ADH-AES256-SHA SSLv3 Kx=DH Au=None Enc=AES(256) Mac=SHA1 DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 ADH-AES128-SHA SSLv3 Kx=DH Au=None Enc=AES(128) Mac=SHA1 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-RC4-SHA SSLv3 Kx=DH Au=DSS Enc=RC4(128) Mac=SHA1 EXP1024-DHE-DSS-RC4-SHA SSLv3 Kx=DH(1024) Au=DSS Enc=RC4(56) Mac=SHA1 export EXP1024-RC4-SHA SSLv3 Kx=RSA(1024) Au=RSA Enc=RC4(56) Mac=SHA1 export EXP1024-DHE-DSS-DES-CBC-SHA SSLv3 Kx=DH(1024) Au=DSS Enc=DES(56) Mac=SHA1 export EXP1024-DES-CBC-SHA SSLv3 Kx=RSA(1024) Au=RSA Enc=DES(56) Mac=SHA1 export EXP1024-RC2-CBC-MD5 SSLv3 Kx=RSA(1024) Au=RSA Enc=RC2(56) Mac=MD5 export EXP1024-RC4-MD5 SSLv3 Kx=RSA(1024) Au=RSA Enc=RC4(56) Mac=MD5 export EXP-KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(40) Mac=MD5 export EXP-KRB5-RC2-CBC-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC2(40) Mac=MD5 export EXP-KRB5-DES-CBC-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=DES(40) Mac=MD5 export EXP-KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(40) Mac=SHA1 export EXP-KRB5-RC2-CBC-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC2(40) Mac=SHA1 export EXP-KRB5-DES-CBC-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=DES(40) Mac=SHA1 export KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=MD5 KRB5-DES-CBC3-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=MD5 KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=SHA1 KRB5-DES-CBC3-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 EXP-EDH-RSA-DES-CBC-SHA SSLv3 Kx=DH(512) Au=RSA Enc=DES(40) Mac=SHA1 export EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 EXP-EDH-DSS-DES-CBC-SHA SSLv3 Kx=DH(512) Au=DSS Enc=DES(40) Mac=SHA1 export DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 EXP-DES-CBC-SHA SSLv3 Kx=RSA(512) Au=RSA Enc=DES(40) Mac=SHA1 export EXP-RC2-CBC-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 EXP-RC4-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export ADH-DES-CBC3-SHA SSLv3 Kx=DH Au=None Enc=3DES(168) Mac=SHA1 EXP-ADH-DES-CBC-SHA SSLv3 Kx=DH(512) Au=None Enc=DES(40) Mac=SHA1 export ADH-RC4-MD5 SSLv3 Kx=DH Au=None Enc=RC4(128) Mac=MD5 EXP-ADH-RC4-MD5 SSLv3 Kx=DH(512) Au=None Enc=RC4(40) Mac=MD5 export DES-CBC3-MD5 SSLv2 Kx=RSA Au=RSA Enc=3DES(168) Mac=MD5 RC2-CBC-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC2(128) Mac=MD5 EXP-RC2-CBC-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export RC4-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 EXP-RC4-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export I want dovecot to only accept high encrypted ciphers, thus it should support ssl_cipher_list = ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM corresponding to a openssl list such as DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 KRB5-DES-CBC3-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=MD5 KRB5-DES-CBC3-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-RC4-SHA SSLv3 Kx=DH Au=DSS Enc=RC4(128) Mac=SHA1 KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=MD5 KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=SHA1 RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 This would really make "Dovecot (...) written with security primarily in mind" Thanks for consideration! rob.

2 2

[Dovecot] feature or bug on delete?
by Cor Bosman 23 Jul '05

23 Jul '05

RFC 3501 mentions this: The DELETE command MUST NOT remove inferior hierarchical names. For example, if a mailbox "foo" has an inferior "foo.bar" (assuming "." is the hierarchy delimiter character), removing "foo" MUST NOT remove "foo.bar". It is an error to attempt to delete a name that has inferior hierarchical names and also has the \Noselect mailbox name attribute (see the description of the LIST response for more details). It is permitted to delete a name that has inferior hierarchical names and does not have the \Noselect mailbox name attribute. In this case, all messages in that mailbox are removed, and the name will acquire the \Noselect mailbox name attribute. This is what dovecot does: . create foo . OK Create completed. . create foo/bar . OK Create completed. . list "" "*" * LIST (\HasChildren) "/" "foo" * LIST (\HasNoChildren) "/" "foo/bar" . OK List completed. (some other output removed here) . delete foo . OK Delete completed. . list "" "*" * LIST (\HasNoChildren) "/" "foo/bar" . OK List completed. Reading the above section, shouldnt I be seeing a: * LIST (\Noselect \HasChildren) "/" "foo" Regards, Cor

2 2

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

23 Jul '05

I just noticed one instance of this in the current CVS version: dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834 < 2872) dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) dovecot: Jul 18 15:25:48 Error: child 5962 (imap) killed with signal 6 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff438 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x0000174a 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 0x0809a96a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x174a <Address 0x174a out of bounds>) at failures.c:374 No locals. #7 0x0809ad84 in i_panic ( format=0x80a772c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 No locals. #8 0x08082711 in mail_index_buffer_convert_to_uids (t=0x80d14b8, array=0x80d14d0, range=1) at mail-index-transaction.c:129 view = (struct mail_index_view *) 0x80cfdc0 rec = Variable "rec" is not available. (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff438 in ?? () #2 0x00000006 in ?? () #3 0x0000174a in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809a96a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x174a <Address 0x174a out of bounds>) at failures.c:374 #7 0x0809ad84 in i_panic ( format=0x80a772c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x08082711 in mail_index_buffer_convert_to_uids (t=0x80d14b8, array=0x80d14d0, range=1) at mail-index-transaction.c:129 #9 0x08083b87 in mail_index_transaction_commit (t=0x80d14b8, log_file_seq_r=0xbffff65c, log_file_offset_r=0xbffff660) at mail-index-transaction.c:183 #10 0x080703f4 in mbox_sync (mbox=0x80c5bc0, flags=Variable "flags" is not available. ) at mbox-sync.c:1623 #11 0x080710c9 in mbox_storage_sync_init (box=0x80c5bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mbox-sync.c:1700 #12 0x0808ef01 in mailbox_sync_init (box=0x0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mail-storage.c:334 #13 0x0805eb58 in imap_sync_nonselected (box=0x80c5bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at imap-sync.c:166 #14 0x080580f6 in _cmd_select_full (cmd=0x80beba8, readonly=0) at cmd-select.c:39 #15 0x08058281 in cmd_select (cmd=0x80beba8) at cmd-select.c:92 #16 0x0805986b in _client_input (context=0x80beb68) at client.c:334 #17 0x0809ff3a in io_loop_handler_run (ioloop=0x80bd9b0) at ioloop-poll.c:184 #18 0x0809f569 in io_loop_run (ioloop=0x80bd9b0) at ioloop.c:218 #19 0x08060657 in main (argc=1, argv=0xbffffa34, envp=0xbffffa3c) at main.c:228 (gdb) p seq $1 = (uint32_t *) 0x80d4d18 (gdb) p *seq $2 = 0 (gdb) p view->map $3 = (struct mail_index_map *) 0x80c5fd0 (gdb) p *view->map $4 = {refcount = 3, hdr = {major_version = 7 '\a', minor_version = 0 '\0', base_header_size = 120, header_size = 200, record_size = 36, compat_data = "\001\b\004", indexid = 1113829460, flags = 0, uid_validity = 1113827022, next_uid = 2872, messages_count = 929, recent_messages_count = 0, seen_messages_count = 810, deleted_messages_count = 0, first_recent_uid_lowwater = 0, first_unseen_uid_lowwater = 1149, first_deleted_uid_lowwater = 2846, log_file_seq = 8, log_file_int_offset = 27912, log_file_ext_offset = 27912, sync_size = 9241460, sync_stamp = 1113863658, day_stamp = 1121659200, day_first_uid = {2855, 2849, 2849, 2753, 2753, 2753, 2491, 187}}, hdr_base = 0x80c60b0, records = 0x80c61d8, records_count = 929, extension_pool = 0x80ce490, extensions = { buffer = 0x80ce4c0, element_size = 28}, ext_id_map = {buffer = 0x80ce588, element_size = 4}, mmap_base = 0x0, mmap_size = 0, mmap_used_size = 0, buffer = 0x80c61b8, hdr_copy_buf = 0x80c6090, keyword_idx_map = { buffer = 0x0, element_size = 0}, write_to_disk = 0} (gdb) p t $5 = (struct mail_index_transaction *) 0x80d14b8 (gdb) p *t $6 = {refcount = 1, view = 0x80cfdc0, appends = {buffer = 0x80d4830, element_size = 8}, first_new_seq = 930, last_new_seq = 953, expunges = { buffer = 0x80d4810, element_size = 8}, 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 28 times>, "O\v", '\0' <repeats 89 times>, post_hdr_mask = '\0' <repeats 28 times>, "\001\001\001\001", '\0' <repeats 87 times>, ext_rec_updates = {buffer = 0x80d4750, element_size = 8}, ext_resizes = {buffer = 0x0, element_size = 0}, ext_resets = {buffer = 0x0, element_size = 0}, keyword_updates = {buffer = 0x0, element_size = 0}, keyword_resets = {buffer = 0x80d4730, element_size = 8}, cache_trans_ctx = 0x0, hide_transaction = 0, no_appends = 0, external = 1, pre_hdr_changed = 0, post_hdr_changed = 1, log_updates = 1} (gdb) p j $7 = 2 (gdb) p range $8 = 1

2 1

[Dovecot] pop3 authentication failure - password mismatch
by James Sun 23 Jul '05

23 Jul '05

I tried to run dovecot 1.0 built by myself but encountered the above problem. See the error traces below. First of all, the password and user are correct, as it worked with the 0.99 rpm version of dovecot. I also hand verified with ssh. I also attached the dovecot config file below. Any ideas? Jun fetchmail output on client: ------------------------------------- fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< SASL PLAIN fetchmail: POP3< . fetchmail: POP3> USER jam fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. maillog on dovecot server: -------------------------------------- Jul 22 18:28:18 hsiufen dovecot: auth(default): passwd(jam,24.6.106.170): password mismatch Jul 22 18:28:19 hsiufen dovecot: pop3-login: Aborted login [24.6.106.170] Jul 22 18:29:32 hsiufen dovecot: Killed with signal 2 dovecot.conf ------------------ protocols = imap imaps pop3 pop3s listen = * ssl_disable = no disable_plaintext_auth = no protocol imap { login_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/imap-login mail_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/imap } protocol pop3 { login_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/pop3-login mail_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/pop3 } auth_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/dovecot-auth auth_verbose = yes auth default { mechanisms = plain passdb = passwd userdb = passwd user = root }

2 3

[Dovecot] Stable Version
by Marc Perkel 23 Jul '05

23 Jul '05

I'm very new to Dovecot - still testing it - and planing to convert in the futire. I see a lot of rapid development here which I like. But I'm wondering if there is any kind of schedule for blessing 1.0 as official - or - what the custom is for a stable release. Just trying to think about when to jump in. I'm fairly brave, but the feature I need we just added today. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] 1.0-test78
by Timo Sirainen 22 Jul '05

22 Jul '05

http://dovecot.org/test/ Fixes: - Crashes in non-x86 64bit systems - Bugs in cache file header caching (you probably should delete all dovecot.index.cache files to be sure the bug won't haunt you in future) - FETCH ENVELOPE patch by Chris Wakelin (I'll try to figure out what to do with the list patch later) Known bugs left: - Thunderbird + maildir: moving lots of messages from mailbox to another may cause deadlock (lock timeouts in half a minute or so and fails the operation). - I guess I should try to look at the Thunderbird + POP3 + lots of messages -> DELE error too again.. - I've heard that 1.0-tests are a lot slower than 0.99.x or 1.0-stable when checking new mail (with kmail), ie. client asking STATUS of all mailboxes. I've looked at their strace outputs and the difference (5-10x slower) comes from 1.0-test waiting longer in poll() for client input, which doesn't really make any sense to me. Can anyone verify this or think of reasons why this could happen? Maybe I'm setting some socket option differently, although I don't think I've changed anything..

8 15

[Dovecot] 1.0-stable and nfs
by Cyril Feraudet 22 Jul '05

22 Jul '05

Hi all, I've a little pb with 1.0-stable on nfs share without lockd : with : - lock_method = dotlock - mmap_disable = yes I've : - dovecot: Jul 22 11:58:33 Error: IMAP(xxxxxxxx): open() failed with index file (null): Bad address with : - lock_method = dotlock - mmap_disable = no I've : - dovecot: Jul 22 11:59:47 Error: IMAP(xxxxxxxx): lock_method=dotlock and mmap_disable=no combination isn't supported. You don't _really_ want it anyway. Someone have an idea ? Thanks, Cyril Feraudet

2 3

[Dovecot] dovecot starts and exit immediately? - help needed
by James Sun 22 Jul '05

22 Jul '05

Since nobody answered my previous question on dovecot marking new mails as old mails, I decided to build a version of dovecot of my own to debug. I downloaded and compiled dovecot 1.0 (stable). After setting up the conf file, I ran dovecot but it exited immediate with status 0. As a result, remote client cannot connect and retrieve mails. There is no man page, and I only found two command line options, -F and -c. None of these options seem to matter. Any suggestions? I must have done something simple and wrong here. Jun

2 4

[Dovecot] Bug in 0.99.14 mbox handling - mail UIDs are renumbered without bumping UIDVALIDITY
by David McBride 22 Jul '05

22 Jul '05

Package: dovecot-imapd Version: 0.99.14-1 Severity: important Hi, I think I've identified a bug in Dovecot 0.99.14 as packaged and distributed by Debian Sarge. I believe the bug lies in the original Dovecot source, not with any modifications made by Debian. Specifically, this bug deals with Dovecot's handling of message unique identifiers (UIDs) for IMAP clients when using the mbox mailbox storage format. Some background for those not familiar with the details; (I had to look a lot of this stuff up; see also http://www.ietf.org/rfc/rfc2060.txt) --- 8< -------------------------------------------------------------- All IMAP servers are required to maintain unique identifiers for each email in an IMAP mailbox that are persistent between sessions. Dovecot stores the unique identifiers for each email in an mbox in an X-UID header. Clients which maintain a local cache of already-retrieved emails use an email's UID as a key; thus, if the UID of a particular email were to change on a server then the client's cached state would be invalid. To cope with the case that the UIDs need to be invalidated, whether because the original store has been lost or for some other reason, there is also the UIDVALIDITY number. This 32bit integer must be increased to some higher value to indicate that any previously cached email ids are now invalid. In Dovecot-managed mbox files, this number is stored in the X-IMAPbase header in the first message of that mbox and is typically the uid-invalidation time expressed in unix timestamp format (ie the number of seconds elapsed since the epoch.) --- 8< -------------------------------------------------------------- Okay, the actual bug: Dovecot routinely (and apparently unneccessarily) renumbers all of the UIDs in our mbox-backed mailboxes without updating the UIDVALIDITY count. This results in caching mail clients (such as Evolution and Thunderbird) presenting the incorrect email to the user when browsing their mail. Configuration: We are using Dovecot as a standalone daemon (ie without using inetd.) We have configured the default mail environment with the following string: default_mail_env = mbox:%h/Mail/:INBOX=%h/.email:INDEX=MEMORY ie each end-user's primary INBOX is an mbox, ~/.email, and other IMAP folders are also stored as mboxes in the directory ~/Mail/. Indexes are maintained in memory but are not stored on disk. I don't think any of the rest of the configuration is relavant, but I'm happy to detail anything else about the setup if needed. Reproducing the bug: I'm afraid I don't have a proper protocol dump demonstrating this bug, so I'm just going to describe all of the end-user steps to recreate the problem: 1) Connect to the Dovecot IMAP service with a caching mail client, such as Evolution or Thunderbird. Download a local copy of the IMAP server contents of a test mbox-backed mailbox to the local cache. For example, I have a test mbox with old root mail. Messages are numbered from 1 to 163. The most recent message has an X-UID: field of 163. 2) Delete one of the messages in the middle of the mailbox. For example, mark the second-oldest message in the mailbox, which has a UID of 2, for deletion. Expunge the mailbox. 3) The UIDs of the other messages at this point have not been altered. Disconnect from the IMAP server. (With Evolution, I actually had to restart the program to reproduce this bug.) 4) Reconnect to the IMAP service, and allow the client to re-sync. You will find that the X-UID of all of the messages after the one that was deleted have been decremented -- and, if you're using a caching client, all of the message *bodies* will appear to have been shifted down by one. Reading the headers in the mbox file directly, Dovecot has renumbered all of the UIDs from 1 to N but not altered the UIDVALIDITY field: dwm@kalimdor $ grep X-UID: Root X-UID: 1 X-UID: 2 [... all numbers between 2 and 161 follow ...] X-UID: 161 X-UID: 162 dwm@kalimdor $ grep X-IMAPbase: Root X-IMAPbase: 1063356421 162 1063356421 == Sept 2003, when the mailbox was first created. This is a bug. Either Dovecot should not renumber the UIDs of each message, or (if it really is necessary), it should increase the UIDVALIDITY field to some higher number to invalidate the caches stored by any remote clients. This bug wasn't observed when using previous versions of Dovecot (we were previously using 0.99.10.6 before this upgrade without noticing anything broken.) I'm hoping someone familiar with the source tree can identify and suggest a fix relatively quickly; failing that, I'll take a look around to see if I can work out where the problem is and implement a fix it myself. Cheers, David -- David McBride <dwm(a)tastycake.net>

1 0

[Dovecot] Changes made to imap descriptor handling in test78?
by Dominic Marks 22 Jul '05

22 Jul '05

Hello, What has changed from test77 to test78 in the way imap manages its descriptors? I upgraded to test78 this morning on a small site which I use as a testbed for testing various things. Running the same copy of my kqueue patch with test77 works quite well [*], with test78 imap has some problems. Here is some debugging output I recorded: Jul 14 12:55:27 egg dovecot: imap-login: Login: user=<dom>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, SSL Jul 14 12:55:30 egg dovecot: IMAP(dom): kqueue was given an unknown descriptor 1, -1: No such file or directory The second line points refers to io_loop_handler_remove, the tcp/ip socket (1) is having the read filter (-1) removed, suspending events from the socket, or at least, that is what should be happening. From kevent(2) for ENOENT: [ENOENT] The event could not be found to be modified or deleted. This suggests to me that we are incorrectly calling io_loop_handler_remove before we should. This error happens immediately after a client opens their mailbox. I have checked pop3 and it does not share the problem. I'm going to have a look at the CVS mail archive to see if I can work out what has changed. [*] Occasionally I was receiving ENOENT in test77 also in io_loop_handler_remove, but only occasionally, perhaps a few times a day for each client. This also didn't occur when opening the mailbox, but some time later. I'm still looking for the trigger for that. Cheers, -- Dominic Marks

2 1

[Dovecot] dovecot pop3s delivers new messages as old (unread) messages ...
by James Sun 22 Jul '05

22 Jul '05

I just set up dovecot on fedora core 3 with only pop3s protocol enabled. On my client machine, I use fetchmail to get the mail and then go through procmail and eventually ready by mutt. Everything seems to work fine, except that all new emails are marked old unread emails (i.e., marked with 'O' flag instead of 'N'). This is annoying because some open source lists are so large that I really rely on the "N" flag to read my emails. I tested the same client setting with gmail and my isp (comcast) pop3 accounts. They work fine - new mails are marked as "N". This makes me suspect dovecot is not set up correctly or something on the pop3 server machine is not right. Anybody has an idea? Thanks in advance. Jun Here are more detailed info: -bash-3.00# rpm -qa | grep dovecot dovecot-0.99.13-3.FC3 /etc/dovecot.conf: ---------------------------- protocols = pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem login_dir = /var/run/dovecot-login login = imap login = pop3 mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = no .fetchmailrc on client machine -------------------------------------- poll mypop.server.com protocol pop3 user "jsun" password "xxxx" is jsun here ssl

2 3

[Dovecot] Double Emails
by Matt Juszczak 22 Jul '05

22 Jul '05

Hi all, I originally posted this on postfix's mailing list but then realized that this COULD be a pop3 server problem since that downloads and deletes mail. This has only been happening since I upgraded from .99 to 1.0-7 ... Our users have been reporting double messages in their inbox, as well as emails that they deleted a long time ago reappearing. The only thing in my maillog is a bunch of: mbox sync: UID inserted in the middle of mailbox /home/sdf/mail/Level3 (6293 > 3) Thats happening for IMAP folder and /var/mail/* mbox folders alike. I can't seem to figure out the problem, but we have at least 50 customers calling in today alone to complain about double messages. More are probably experiencing it and just not calling. Any ideas? Thanks! -Matt

3 5

Re: [Dovecot] Update notifier
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Great! Yes, of course, I just didn't knew that plugins are supported. Are there any documents on this subject? How do you add a plugin to dovecot? Just compile it and copy it to dovecot's lib/imap (like in example) ? Thanks, Sebastjan On 7/22/05, Timo Sirainen <tss(a)iki.fi> wrote: > On Fri, 2005-07-22 at 12:08 +0200, Sebastjan Trepca wrote: > > I'm trying to add a code in dovecot that will notify my services when > > a message is updated/added/moved/copied. I checked dovecot code a bit > > and mail-storage.c seems to be a nice place for tracking but I'm not > > sure if I can track all changes there. > > There are no update/move commands in IMAP, so you'll just need to hook > into saving and copying. Normally copying also goes through save unless > you're using maildir + maildir_copy_with_hardlinks=yes. > > See quota plugin for example how to hook into saving and copying: > http://dovecot.org/patches/1.0/quota.tar.gz > > Probably better to do it as a plugin than directly modify the sources, > so you don't have to keep patching it for each new release. > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.0 (GNU/Linux) > > iD8DBQBC4PdEyUhSUUBViskRApj9AJoCzEM8iNRNaEIcHdGxZDKoSbatFQCfaTMc > 62w52fPQr0uE8wb1A8y9kUY= > =9gtQ > -----END PGP SIGNATURE----- > > >

2 1

[Dovecot] Another minor IMAP LIST issue
by Chris Wakelin 22 Jul '05

22 Jul '05

I've just noticed that Dovecot 1.0-stable and 1.0-test78 don't include mbox folders with names beginning with "." in the IMAP LIST output. These are often used to store "hidden" folders for storing things like IMAP client configuration (e.g. Pine 4.x, IMHO, Prayer). Usually the user shouldn't be able to see these, but there are occassions when they might. It seems to me to be better to let the client decide. As I understand it, the IMAP RFC suggests that if you can "SELECT folderpath" a folder, you should also be able to list it with 'LIST "" "folderpath"' I've written a patch against 1.0-stable (it also works with test78) to add an extra namespace option "showdotfiles" (default "no"), to include folders beginning with "." (but excluding ".imap" and "." and ".." for obvious reasons!). It's used as follows :- # default namespace namespace private { separator = "/" prefix = inbox = yes showdotfiles = yes } # for backwards compatibility with UW-IMAP: namespace private { separator = "/" prefix = "mail/" hidden = yes showdotfiles = yes } ... Let me know if you find it useful! Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 diff -ruN dovecot-1.0-stable.orig/src/imap/cmd-list.c dovecot-1.0-stable/src/imap/cmd-list.c --- dovecot-1.0-stable.orig/src/imap/cmd-list.c Fri Mar 18 20:00:44 2005 +++ dovecot-1.0-stable/src/imap/cmd-list.c Wed Jul 20 16:36:51 2005 @@ -293,6 +293,8 @@ list_flags = ctx->list_flags; if (*ns->prefix == '\0' || ns->inbox) list_flags |= MAILBOX_LIST_INBOX; + if (ns->showdotfiles) + list_flags |= MAILBOX_LIST_DOTFILES; ctx->list_ctx = mail_storage_mailbox_list_init(ns->storage, cur_ref, cur_mask, list_flags); diff -ruN dovecot-1.0-stable.orig/src/imap/namespace.c dovecot-1.0-stable/src/imap/namespace.c --- dovecot-1.0-stable.orig/src/imap/namespace.c Mon Jan 31 16:37:54 2005 +++ dovecot-1.0-stable/src/imap/namespace.c Wed Jul 20 16:36:51 2005 @@ -31,7 +31,7 @@ { struct namespace *ns; const char *sep, *type, *prefix; - int inbox, hidden, subscriptions; + int inbox, hidden, showdotfiles, subscriptions; ns = p_new(pool, struct namespace, 1); @@ -40,6 +40,7 @@ prefix = getenv(t_strdup_printf("NAMESPACE_%u_PREFIX", num)); inbox = getenv(t_strdup_printf("NAMESPACE_%u_INBOX", num)) != NULL; hidden = getenv(t_strdup_printf("NAMESPACE_%u_HIDDEN", num)) != NULL; + showdotfiles = getenv(t_strdup_printf("NAMESPACE_%u_SHOWDOTFILES", num)) != NULL; subscriptions = getenv(t_strdup_printf("NAMESPACE_%u_SUBSCRIPTIONS", num)) != NULL; @@ -58,6 +59,7 @@ ns->prefix = p_strdup(pool, prefix); ns->inbox = inbox; ns->hidden = hidden; + ns->showdotfiles = showdotfiles; ns->subscriptions = subscriptions; ns->storage = mail_storage_create_with_data(data, user); if (ns->storage == NULL) { diff -ruN dovecot-1.0-stable.orig/src/imap/namespace.h dovecot-1.0-stable/src/imap/namespace.h --- dovecot-1.0-stable.orig/src/imap/namespace.h Mon Jan 31 16:37:54 2005 +++ dovecot-1.0-stable/src/imap/namespace.h Wed Jul 20 16:36:51 2005 @@ -16,7 +16,7 @@ char *prefix; size_t prefix_len; - int inbox, hidden, subscriptions; + int inbox, hidden, showdotfiles, subscriptions; struct mail_storage *storage; }; diff -ruN dovecot-1.0-stable.orig/src/lib-storage/index/mbox/mbox-list.c dovecot-1.0-stable/src/lib-storage/index/mbox/mbox-list.c --- dovecot-1.0-stable.orig/src/lib-storage/index/mbox/mbox-list.c Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-storage/index/mbox/mbox-list.c Wed Jul 20 16:36:51 2005 @@ -225,13 +225,19 @@ enum imap_match_result match, match2; int ret, noselect; - /* skip all hidden files */ - if (fname[0] == '.') + /* skip all hidden files unless show dotfiles is set*/ + if (fname[0] == '.' && !(ctx->flags & MAILBOX_LIST_DOTFILES)) return 0; /* skip all .lock files */ len = strlen(fname); if (len > 5 && strcmp(fname+len-5, ".lock") == 0) + return 0; + + /* skip ".imap" "." and ".." directories in case we show dotfiles */ + if (((len == 5) && strcmp(fname, ".imap") == 0) || + ((len == 1) && fname[0] == '.') || + ((len == 2) && strcmp(fname, "..") == 0)) return 0; /* check the mask */ diff -ruN dovecot-1.0-stable.orig/src/lib-storage/mail-storage.h dovecot-1.0-stable/src/lib-storage/mail-storage.h --- dovecot-1.0-stable.orig/src/lib-storage/mail-storage.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-storage/mail-storage.h Wed Jul 20 16:36:51 2005 @@ -16,7 +16,8 @@ MAILBOX_LIST_SUBSCRIBED = 0x01, MAILBOX_LIST_FAST_FLAGS = 0x02, MAILBOX_LIST_CHILDREN = 0x04, - MAILBOX_LIST_INBOX = 0x04 + MAILBOX_LIST_INBOX = 0x04, + MAILBOX_LIST_DOTFILES = 0x08 }; enum mailbox_flags { diff -ruN dovecot-1.0-stable.orig/src/master/mail-process.c dovecot-1.0-stable/src/master/mail-process.c --- dovecot-1.0-stable.orig/src/master/mail-process.c Tue Feb 8 10:30:11 2005 +++ dovecot-1.0-stable/src/master/mail-process.c Wed Jul 20 16:36:51 2005 @@ -175,6 +175,8 @@ env_put(t_strdup_printf("NAMESPACE_%u_INBOX=1", i)); if (ns->hidden) env_put(t_strdup_printf("NAMESPACE_%u_HIDDEN=1", i)); + if (ns->showdotfiles) + env_put(t_strdup_printf("NAMESPACE_%u_SHOWDOTFILES=1", i)); t_pop(); } } diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.c dovecot-1.0-stable/src/master/master-settings.c --- dovecot-1.0-stable.orig/src/master/master-settings.c Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/master/master-settings.c Wed Jul 20 16:36:51 2005 @@ -194,6 +194,7 @@ DEF(SET_STR, location), DEF(SET_BOOL, inbox), DEF(SET_BOOL, hidden), + DEF(SET_BOOL, showdotfiles), { 0, NULL, 0 } }; diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.h dovecot-1.0-stable/src/master/master-settings.h --- dovecot-1.0-stable.orig/src/master/master-settings.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/master/master-settings.h Wed Jul 20 16:36:51 2005 @@ -163,6 +163,7 @@ int inbox; int hidden; + int showdotfiles; }; struct server_settings {

3 5

[Dovecot] subscriptions vs mailboxlist
by Marc Perkel 22 Jul '05

22 Jul '05

Is there a way to change the name of the .subscriptions file that dovecot looks for to .mailboxlist to be compatible with WU-IMAP? It would be handy for testing and conversion if you had that. BTW - I'm a new user and your software is very well designed. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] Errors after moving to Maildir from mbox format
by Gabe Granger 22 Jul '05

22 Jul '05

Hi All, Over the weekend I bit the bullet and migrated my entire office from server to another and converted everything from MBOX to Maildir. Althought it took ages and their we're a few little problems along the way, the migration was a complete success with no users reporting any problems(Mbox used to always cause file lock ups) or even noticing anything had changed... Which is great!:) I'm starting to see some issues currently only with my Mail. In the log files I'm getting loads of the following for at lease 20 different emails Jul 19 12:12:27 server imap(Some-user): Error parsing IMAP envelope: "Tue, 27 May 2003 16:33:07 +0100" "Re: 2U rack cases + PSU" (("Some User" NIL "some-user" "somedomain.foo")) (("Some User" NIL "some- user" "somedomain.foo")) (("Some Userr" NIL "some-user" "somedomain.foo")) (("Some User" NIL "some-user" "some-other- domain.foo")) NIL NIL "<000f01c32462$699a7130$7264a8c0@Microtech>" NIL I did a find in my Mail.app on my mac and discovered that although my client can find the message based on Subject, it fails to locate its mailbox/mailfolder when I select the message I get the following response The message from Some User <some=user(a)some-other-domain.foo> concerning “RE: 2U rack cases + PSU” has not been downloaded from the server. You need to take this account online in order to download it. The account is fully online, does or has anyone here come across this error? I'm guessing there is a problem within the email file itself. I'm using ServerSide Debian 3.1 Sendmail 8.13 Dovecot 0.99.14-1 ClientSide OSX 10.4 Mail.app Any help / pointers would be great. Gabe

2 1

[Dovecot] Corrupted indices (and accidental checkin)
by Thomas Wouters 22 Jul '05

22 Jul '05

I've seen a number of corrupted-index problems pop up on our test-dovecot servers (used by a few people at the office), and I'm wondering why corrupt indices don't just automatically get deleted ? Something like: if (!MAIL_INDEX_IS_IN_MEMORY(index)) { unlink(index->filepath); } in src/lib-index/mail-index.c:mail_index_set_error() comes to mind. It seems to me like it should work, anyway. You can still treat the error like it's currently treated (as fatal), but at least it won't pop up the next time you try to perform the same action, or trigger the same corrupted entry another way. By the way, I also noticed what is probably an accidental checkin in src/lib-storage/index/maildir/maildir-storage.c:maildir_get_control_path(), where it tries to migrate control files from the default location to the configured location. I think Timo wrote that patch for my colleage Cor, and then accidentily checked it in with: ---------------------------- revision 1.100 date: 2005-06-09 14:31:43 +0000; author: cras; state: Exp; lines: +22 -4 Replaced ':' and ',' character usages with #defines, so they can be changed easily if needed. The patch is 'broken' anyway; it tries to use rename() to move the old control files to the new location, but that doesn't quite work between different filesystems (and that happens to be what we want to do ;). A better way to handle it would probably be to read in the data from the old location, and then write it out to the new location, in a normal load/save procedure. But I think we'll just do the move manually, after all, as it's just a few dozen different accounts at the moment. I'm not sure about the value of the 'implicit' controlfile migration that dovecot currently does. -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

2 1

[Dovecot] Few questions
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Is there a way to list all keywords a mailbox uses? I fetch flags for all messages and then gorup them, but this is a very nasty solution. What's the situation with full text search? Will it ever be implemented? Is it already? Text search on my 0.99.14 is quite slow. Don't understand why no IMAP server wants to implement this feature. Does Dovecot support plugins? Thank you, Sebastjan

2 3

[Dovecot] CR LF in stable
by Thomas Hummel 22 Jul '05

22 Jul '05

Hello, It seems that mbox format mailboxes holding \r\n (CR + LF) character sequences (instead of \n only) still cause assertion failures when moving messages from one folder to another. -- dovecot: Jul 19 17:14:52 Error: IMAP(dovetest): file istream-raw-mbox.c: line 38 3 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != ( uoff_t)-1) -- I seems to work in -test78 though. Is there any plan to handle this in -stable branch ? -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1

[Dovecot] deleting folders containing subfolders with thunderbird (mbox format) bug
by John Bramley 22 Jul '05

22 Jul '05

When using Thunderbird (dovecot-0.99.13-3.FC3) on Fedora connecting to dovecot-0.99.13-3.FC3 I am having problems deleting folders which have been created with the 'Allow your new folder to contain: Folders only' option picked. The folder appears to get deleted but upon restarting Thunderbird the folder still appears to be there but clicking on it I get the error: 'The current command did not succeed. The mailserver responded: Mailbox doesn't exist: <mailbox name>'. Upon investigation when creating and deleting a folder called 'bilbo' to contain subfolders only: Thunderbird sends 'create bilbo/' imap command and then 'subscribe bilbo/' Dovecot creates a directory 'bilbo' and adds 'bilbo/' to the .subscriptions file which all works ok. Upon trying to delete the folder and confirming that it should be deleted Thunderbird sends: 'delete bilbo/' dovecot replies 'OK Delete completed' Then thunderbird sends 'unsubscribe bilbo/' dovecot replies 'NO Invalid mailbox name' which Thunderbird ignores and all seems to have gone ok until thunderbird is restarted and the folder reappears in the folder list but nothing can be done with it. I believe that if a client sends an 'unsubscribe' command to a mailbox that is currently subscribed the imap server should unsubscribe it - even if the actual mailbox doesn't exist (unsubscribe and then delete seems to work when testing using telnet to port 143 to send imap commands). Dovecot does allow mailboxes to be unsubscribed if they don't exist if they don't have a tailing '/' character (so deleting folders set to contain only messages in Thunderbird works ok). I expect that everything works ok using Maildir mailboxes because then there is no need to mark folders containing folders with a '/' because all folders can contain messages and folders. For my own purposes I have hacked the mbox_get_mailbox_name_status function in src/lib-storage/index/mbox/mbox-storage.c to add a check to see if the mailbox name is already subscribed to and if it is then return status = MAILBOX_NAME_EXISTS, before the 'if (!mbox_is_valid_create_name(storage, name))' check which is returning status = MAILBOX_NAME_INVALID, which seems to work ok for me. UW-imap works ok I'm surprised at this bug (or am I doing something completely wrong), surely lots of people use Thunderbird with dovecot, do they not create sub-folders in folders, or are they all using Maildir format, or do they never find the 'Server supports folders that contain sub-folders and messages' advanced option so they are never able to create folders within folders in the first place? John.

2 1

[Dovecot] Failed to create storage with data - possible reasons?
by vmstech 22 Jul '05

22 Jul '05

Hi I'm getting this error with my attempt at setting up dovecot for virtual mail accounts: Failed to create storage with data: /home/vhostpath/usersname/Maildir/ I cant establish any cause. I dont think its permissions as it was saying 'Permission denied' till I fixed that and the UID and GID are those of the directories owner. I was prompted bythe log files to set the minimum and maximum uid range, which made the prompt go away, but I still have this problem. Can anyone tell me what else might cause this error? Thanks glenn

2 2

[Dovecot] Dovecot 0.99.11 config
by nickr 22 Jul '05

22 Jul '05

I am at wits end...So far it seems dovecot is light years ahead of UW-IMAP. Glad to have UW-IMAP behind me...well almost. My setup = Sendmail 8.13.4 with Procmail delivery to /var/spool/mail/<userfile> openssl 0.9.8 dovecot 0.99.11 I want to continue to use the standard mbox with all the user's mail stored in /var/spool/mail/<userfile>. User's are known to this mail server via NIS and ALL data is mounted accress NFS in read only mode on this machine, including ~home directories. I want to run dovecot like UW-IMAP...trying to keep it simple-->mail delivery to mbox /var/spool/mail/<username>. My /etc/dovecot.conf: I tried both default_ mail_env = INBOX:/var/spool/mail/%u:INBOX:INDEX=MEMORY with and with out the INBOX:INDEX=MEMORY I want to disable the indicies feature. We don't need it we're about 20 engineers or so who want to continue to use the /var/spool/mail mbox-the original Sendmail location. Most users are downloading every piece of mail through OutHouse or Pine, aka OutLook. I keep getting failed to create storage meaages in /var/log/maillog... Jul 21 15:53:26 mailtest pop3-login: Login: nickr [::ffff:172.26.64.2] Jul 21 15:53:26 mailtest pop3(nickr): Failed to create storage with data: INBOX:/var/spool/mail/nickr Jul 21 15:53:26 mailtest dovecot: child 4773 (pop3) returned error 89 Permissions info for /var/spool/mail/nickr: drwxrwxrwt 3 root mail 4096 Jul 21 15:43 mail [root@mailtest mail]# ls -la nickr total 4204 drwxrwxrwx 2 nickr mail 4096 Jul 21 15:19 . drwxrwxrwt 3 root mail 4096 Jul 21 15:43 .. -rwxrwxrwx 1 nickr ftp 0 Jul 21 14:56 inbox -rwxrwxrwx 1 nickr mail 2375 Jul 21 15:12 msg.FAUO -rwxrwxrwx 1 nickr mail 4256870 Jul 20 16:55 nickr As you can see I am spoping just fine.... Thanks in advance for ANY help!!!!!!!!!

2 1

[Dovecot] Update notifier
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Hi, I'm trying to add a code in dovecot that will notify my services when a message is updated/added/moved/copied. I checked dovecot code a bit and mail-storage.c seems to be a nice place for tracking but I'm not sure if I can track all changes there. Does anyone have any experience with this topic or ideas? Thanks, Sebastjan

2 1

[Dovecot] passwd-file command doesn't support %d
by Marc Perkel 22 Jul '05

22 Jul '05

Trying this and it doesn't work: passdb = passwd-file /etc/vmail/test.%d Apparently it doesn't expand the %d according to the log file. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] Dovecot vs.Clients - strange behaviour, diagnostics sought
by Jeroen Scheerder 22 Jul '05

22 Jul '05

I've been experimenting with dovecot-1.0-stable on Solaris. Storage format is mbox. Dovecot, in test, runs in parallel with an UW IMAP, with dovecot running SSL-only on port 994. It seems to work to some extent: * dovecot runs * authentication works * SSL works * all manual IMAP functionality checks seem to work fine However, I'm running into issues with IMAP clients. * Null client: I started by using telnet as a client, and talking IMAP manually. Seems OK. * Mutt: "mutt -f imap://my.imap.server:994" seems to work well, although mutt keeps reporting details about the SSL certificate, informs me that it belongs to the proper server and is a valid Globalsign-issued certificate -- and keeps insisting I either reject it or accept it once. * Apple Mail (Panther's version, 1.3.11 (v622)) works, though it seems to have problems with large mailboxes. Then again, it had these same problems with other IMAP servers as well. * Thunderbird doesn't work at all. After some waiting, it bums out and reports: Unable to connect to your IMAP server. You may have exceeded the maximum number of conenctions to this server. If so, use the Advanced IMAP Server Settings dialog to reduce the number of cached connections. Note that it never even shows an authentication dialog, and the only thing I see in dovecot's log that relates to Thunderbirds attempt is: dovecot: Jul 20 09:41:09 Info: imap-login: Disconnected: \ Inactivity [131.211.143.87] I'm at a loss as to what's causing this. On the one hand, dovecot seems operational, on the other hand at least one client can do nothing with it. All debugging/logging options are enabled. What am I missing?

5 8

[Dovecot] bug in dovecot search
by Cor Bosman 22 Jul '05

22 Jul '05

A007 search from phyllis * SEARCH 484 A007 UID SEARCH CHARSET "US-ASCII" ALL FROM {7} phyllis * SEARCH 007 UID SEARCH CHARSET "US-ASCII" ALL FROM "phyllis" * SEARCH Regards, Cor

3 3

Fwd: [Dovecot] Very slow select() command on large mailboxes
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Maildir, its easier to export and can support hardlinks. What kind of optimizations did you have in mind? What's the downside of mbox? Problem is that version 1.0 is only test release for now. On 7/14/05, Timo Sirainen <tss(a)iki.fi> wrote: > > On Thu, 2005-07-14 at 11:59 +0200, Sebastjan Trepca wrote: > > Hi, > > > > I'm trying to decide if I could use you mail server in our enviroment > > which has about 10k users and mailboxes size about ~1GB. > > So I made a few tests and it all worked quite fast, except that select > > command on large mailboxes. The first time I select a mailbox which > > has 10k messages it takes about 4s to process. I am deliberately > > trying this on a Celeron 850Mhz, 512 MB memory and some shitty > > hard-drive to maximize the times. > > So why is this so slow? Does it index the messages on select? It's > > even slower when I have some new messages in folder, more that I have > > more I wait. So I presume it must be something with indexing? Anyway, > > how could I optimize this? Why don't you index when a mail arrives > > instead of on select? > > mbox or maildir? mbox can be optimized in different ways with > 1.0-stable/test releases, but maildir itself needs to be rescanned all > too often.. > > >

2 1

[Dovecot] configuration of user_global_uid and user_global_gid
by KATOH Yasufumi 22 Jul '05

22 Jul '05

Hi. I'm configuring LDAP auth with dovecot (cvs trunk at 14, July) as follows: /etc/dovecot/dovecot.conf: passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } /etc/dovecot/dovecot-ldap.conf: user_attrs = mail,homeDirectory,mailbox,,, user_global_uid = 10000 user_global_gid = 1000 But "user_global_uid" and "user_global_gid" definition does not work. dovecot: Jul 14 11:50:36 Error: auth(default): ldap(test(a)example.jp,127.0.0.1): ui d not in user_attrs and no default given in user_global_uid dovecot: Jul 14 11:50:36 Error: auth(default): ldap(test(a)example.jp,127.0.0.1): gi d not in user_attrs and no default given in user_global_gid How do I configure to enable "user_global_uid" and "user_global_gid"? Does my configuration have any problem? -- karma(a)jazz.email.ne.jp / KATOH Yasufumi

2 1

[Dovecot] Changing port?
by Matt Juszczak 22 Jul '05

22 Jul '05

Hi all, Trying to setup a test copy of dovecot on my box before I "really" use it. I have it installed into a test dir (/usr/local/dovecot instead of /usr/local), and I've got a config file with valid dirs, etc. Only thing is ... I can't find a way to set the port in the protocol pop3 {} section. Its documented in the "listen" directive area at the top of the config file that says its possible, but no other mention of it is ever made. How can I make my test copy listen on port 111? :) Regards, Matt

2 1

[Dovecot] Can't connect to auth server
by Todd Burroughs 22 Jul '05

22 Jul '05

I've been seeing these errors intermittently for a while now. Here's an example from the logs: dovecot: Jul 12 15:59:05 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable The error is EAGAIN. Sometimes it will resolve itself after a few minutes and sometimes it needs to be restarted (it may fix itself, I usually get a phone call if it goes on for very long). I've looked while the problem is occuring and dovecot and dovecot-auth don't have an excessive number of file descriptors open, maybe 10 or 20. Any ideas or anything else to look at? The system is SuSE Linux 9.2 running kernel 2.6.x. We have seen some odd things happen with these systems, so it is possible that it is not dovecot. The kernel doesn't log anything unusual and other processes seem happy. Todd

2 1

[Dovecot] test76-77 dies at SIGHUP
by Johan Fredin 22 Jul '05

22 Jul '05

Hello people This is on OpenBSD/sparc64. After chickening along with 0.99 for a while, I finally upgraded to 1.0-test. I started out with test73, which worked fine. With the upgrade to test76, I lost the ability to SIGHUP dovecot when I rotated it's logfile. Dovecot would just die abruptly, not a trace in the log. I just upgraded to test77, but the problem is still there. I've put up my logfile and the last bit of a ktrace here: http://legonet.org/~griffin/tmp/dovecot/ The ktrace is partitial mostly because it contains usernames, I can edit those out and upload the hole shebang if that'll help. I'd appreciate any tips/pointers on this one! /Johan

3 2

[Dovecot] 0.99.14 and nfs
by Cyril Feraudet 22 Jul '05

22 Jul '05

Hi, somebody have an idea to make dovecot working safly with nfs without lockd ? It seems working without problem except for files ".customflags" and ".subscriptions" is exists a patch for use the dotlock locking method for these files ? Thanks, Cyril Feraudet

3 4

[Dovecot] test77, yahoo & fetchmail
by Chris Spiegel 22 Jul '05

22 Jul '05

I've run into a rather narrowly scoped problem .. On test77 and test78, mails from Yahoo's webmail are seen, by fetchmail using imaps, to have a 0-length body. When fetching, it claims "0 body octets". Other mail clients (mutt, kmail) can view the messages fine. pop3s retrieval works as well. Every other email I've received so far works fine. It's just those sent by Yahoo's webmail service that have the problem. imaps retrieval does, however, work fine with test76. Let me know if there's anything I can do to help track this down. Thanks, Chris

2 1

[Dovecot] Re: Dovecot 0.99.11 config
by nickr 21 Jul '05

21 Jul '05

----- Original Message ----- From: nickr To: dovecot(a)dovecot.org Sent: Thursday, July 21, 2005 4:19 PM Subject: Dovecot 0.99.11 config I am at wits end...So far it seems dovecot is light years ahead of UW-IMAP. Glad to have UW-IMAP behind me...well almost. My setup = Sendmail 8.13.4 with Procmail delivery to /var/spool/mail/<userfile> openssl 0.9.8 dovecot 0.99.11 I want to continue to use the standard mbox with all the user's mail stored in /var/spool/mail/<userfile>. User's are known to this mail server via NIS and ALL data is mounted accress NFS in read only mode on this machine, including ~home directories. I want to run dovecot like UW-IMAP...trying to keep it simple-->mail delivery to mbox /var/spool/mail/<username>. My /etc/dovecot.conf: I tried both default_ mail_env = INBOX:/var/spool/mail/%u:INBOX:INDEX=MEMORY with and with out the INBOX:INDEX=MEMORY I want to disable the indicies feature. We don't need it we're about 20 engineers or so who want to continue to use the /var/spool/mail mbox-the original Sendmail location. Most users are downloading every piece of mail through OutHouse or Pine, aka OutLook. I keep getting failed to create storage meaages in /var/log/maillog... Jul 21 15:53:26 mailtest pop3-login: Login: nickr [::ffff:172.26.64.2] Jul 21 15:53:26 mailtest pop3(nickr): Failed to create storage with data: INBOX:/var/spool/mail/nickr Jul 21 15:53:26 mailtest dovecot: child 4773 (pop3) returned error 89 Permissions info for /var/spool/mail/nickr: drwxrwxrwt 3 root mail 4096 Jul 21 15:43 mail [root@mailtest mail]# ls -la nickr total 4204 drwxrwxrwx 2 nickr mail 4096 Jul 21 15:19 . drwxrwxrwt 3 root mail 4096 Jul 21 15:43 .. -rwxrwxrwx 1 nickr ftp 0 Jul 21 14:56 inbox -rwxrwxrwx 1 nickr mail 2375 Jul 21 15:12 msg.FAUO -rwxrwxrwx 1 nickr mail 4256870 Jul 20 16:55 nickr As you can see I am spoping just fine.... Thanks in advance for ANY help!!!!!!!!!

1 0

[Dovecot] linux 2.4 vs 2.6 kernel
by vmstech 20 Jul '05

20 Jul '05

hi I read ( I think in dovecot wiki) that ext2 or ext3 fs on a 2.4 kernel can get slow due to the number of files in a directory. Does anyone know if kernel 2.6 has similar limitation? I'm not at that point now, but before the box goes live, I'm wondering if I should resolve that. Glenn

14 25

[Dovecot] Debian has moved to 1.0stable
by Jaldhar H. Vyas 20 Jul '05

20 Jul '05

Now that sarge has been released, I have as requested moved Debians' Dovecot packages to the 1.0stable branch. Most of the work was actually done by Fabio Tranchitella who is joining me as co-maintainer. The new packages should be available in sid later today. A backport to sarge will also be provided as soon as I can get around to it. Please report all problems to the Debian bug tracking system (see http://bugs.debian.org for instructions or use the reportbug package) not to me directly so that Fabio can also see. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

Re: [Dovecot] linux 2.4 vs 2.6 kernel
by Paul Vatta 20 Jul '05

20 Jul '05

> > >> ------------------------------------------------------------------------ > We were posed with the same dilemma, but it was due to the need to stick with RHEL supplied packages (ReiserFS does not come with RHEL) that we stayed with ext3. Our old production mail server, running our in-house flavour of Linux, was based on the 2.4 kernel with ReiserFS. We load tested Dovecot with maildir under RHEL3 (2.4 kernel) using ext3 and found it was unable to standup to our requirements. In part this was due to an inordinate imap-login / pop-login processes being created and hanging around under RHEL3. Using RHEL4 (2.6 kernel), we found we were able to handle the required load - this is the configuration we went live with. Processes ended cleanly too (result of the improved schedular and how it interacted with our IBM x445 and its NUMA architecture?) and the I/O issues seemed to have been resolved - ext3 was fine. >> Subject: >> Re: [Dovecot] linux 2.4 vs 2.6 kernel >> From: >> Marc Perkel <marc(a)perkel.com> >> Date: >> Mon, 18 Jul 2005 18:33:54 -0700 >> >> CC: >> dovecot(a)dovecot.org >> >> >> >> >> Curtis Maloney wrote: >> >>> Marc Perkel wrote: >>> >>>> Actually - yes. Same problem. But the solution is to use the Reiser >>>> Filesystem. It doesn't have the ext3 problem. >>> >>> >>> >>> Now, I don't want to start a religious war, but... >>> >>> Ext2 has the advantages that 1) it can fall back to ext2 in recovery >>> cases, and 2) because of that, it has all the well-tested ext2 >>> recovery tools available. >>> >>> People I know who've used Reiser say it's wonderfuly fast, but if it >>> corrupts, well... save your time, and go straight to restoring your >>> backups. >>> >>> Also, take a look at the tune2fs options. I understand -O dir_index >>> will set it to use a b-tree index for faster handling of large >>> directories. >>> >>> -- >>> Curtis Maloney >>> cmaloney(a)cardgate.net >> >> >> I've been using it for 5 years and it works great. It specifically >> eliminates the speed problems of Maildir where you have thousands of >> files in a single directory. And it has infinite inodes so you never >> run out of them. Reiser is ideal for email systems. >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>dovecot mailing list >>dovecot(a)dovecot.org >>http://dovecot.org/cgi-bin/mailman/listinfo/dovecot >>

5 7

[Dovecot] Compiling under Fedora Core 4 - Problem
by Marc Perkel 19 Jul '05

19 Jul '05

OK - trying to migrate to dovecot and I like what I see so far, but having a hard time getting it to work. I decided to go with the 1.0 version because I need to get away from the ~/Mail namespace. I'm trying to port from a Linuxconf virtual WU-IMAP type config. So - I compiled but then decided I wanted mysql so I tried to reconfigure and now getting compile errors. Looks like I'm missing something? /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x25): In function `report_errors': : undefined reference to `ERR_get_error_line_data' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xa4): In function `vio_ssl_read': : undefined reference to `SSL_read' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xc5): In function `vio_ssl_read': : undefined reference to `SSL_get_error' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xf9): In function `vio_ssl_write': : undefined reference to `SSL_write' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x22d): In function `vio_ssl_close': : undefined reference to `SSL_shutdown' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x23d): In function `vio_ssl_close': : undefined reference to `SSL_free' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x35c): In function `sslaccept': : undefined reference to `SSL_new' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x372): In function `sslaccept': : undefined reference to `SSL_clear' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x380): In function `sslaccept': : undefined reference to `SSL_get_session' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x38f): In function `sslaccept': : undefined reference to `SSL_SESSION_set_timeout' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3a3): In function `sslaccept': : undefined reference to `SSL_set_fd' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3b1): In function `sslaccept': : undefined reference to `SSL_set_accept_state' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3bf): In function `sslaccept': : undefined reference to `SSL_do_handshake' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3d5): In function `sslaccept': : undefined reference to `SSL_get_peer_certificate' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3e3): In function `sslaccept': : undefined reference to `X509_get_subject_name' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3fb): In function `sslaccept': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x40b): In function `sslaccept': : undefined reference to `X509_get_issuer_name' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x423): In function `sslaccept': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x433): In function `sslaccept': : undefined reference to `X509_free' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x453): In function `sslaccept': : undefined reference to `SSL_get_shared_ciphers' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x4c1): In function `sslaccept': : undefined reference to `SSL_free' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x53b): In function `sslconnect': : undefined reference to `SSL_new' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x54d): In function `sslconnect': : undefined reference to `SSL_clear' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x55b): In function `sslconnect': : undefined reference to `SSL_get_session' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x56a): In function `sslconnect': : undefined reference to `SSL_SESSION_set_timeout' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x57e): In function `sslconnect': : undefined reference to `SSL_set_fd' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x58c): In function `sslconnect': : undefined reference to `SSL_set_connect_state' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x59a): In function `sslconnect': : undefined reference to `SSL_do_handshake' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x607): In function `sslconnect': : undefined reference to `SSL_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x8): In function `get_dh512': : undefined reference to `DH_new' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x2a): In function `get_dh512': : undefined reference to `BN_bin2bn' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x49): In function `get_dh512': : undefined reference to `BN_bin2bn' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x67): In function `get_dh512': : undefined reference to `DH_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x9a): In function `report_errors': : undefined reference to `ERR_get_error_line_data' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0xcd): In function `vio_set_cert_stuff': : undefined reference to `SSL_CTX_use_certificate_file' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0xf1): In function `vio_set_cert_stuff': : undefined reference to `SSL_CTX_use_PrivateKey_file' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0xfd): In function `vio_set_cert_stuff': : undefined reference to `SSL_CTX_check_private_key' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x14e): In function `vio_set_cert_stuff': : undefined reference to `ERR_print_errors_fp' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1c1): In function `vio_set_cert_stuff': : undefined reference to `ERR_print_errors_fp' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1e9): In function `vio_verify_callback': : undefined reference to `X509_STORE_CTX_get_current_cert' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1f3): In function `vio_verify_callback': : undefined reference to `X509_STORE_CTX_get_error' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1fb): In function `vio_verify_callback': : undefined reference to `X509_STORE_CTX_get_error_depth' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x209): In function `vio_verify_callback': : undefined reference to `X509_get_subject_name' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x223): In function `vio_verify_callback': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x271): In function `vio_verify_callback': : undefined reference to `X509_get_issuer_name' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x285): In function `vio_verify_callback': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x2e7): In function `new_VioSSLConnectorFd': : undefined reference to `TLSv1_client_method' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x2f2): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_new' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x30c): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_set_cipher_list' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x326): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_set_verify' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x350): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_load_verify_locations' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x379): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_ctrl' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x381): In function `new_VioSSLConnectorFd': : undefined reference to `DH_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x394): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_set_default_verify_paths' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x3bc): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_load_error_strings' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x3cd): In function `new_VioSSLConnectorFd': : undefined reference to `OPENSSL_add_all_algorithms_noconf' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x422): In function `new_VioSSLAcceptorFd': : undefined reference to `TLSv1_server_method' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x42d): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_new' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x447): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_cipher_list' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x469): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_ctrl' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x483): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_verify' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x49c): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_session_id_context' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x4c6): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_load_verify_locations' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x4ef): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_ctrl' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x4f7): In function `new_VioSSLAcceptorFd': : undefined reference to `DH_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x50a): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_default_verify_paths' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x532): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_load_error_strings' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x543): In function `new_VioSSLAcceptorFd': : undefined reference to `OPENSSL_add_all_algorithms_noconf' collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/ctyme/linuxapps/dovecot/dovecot-1.0-test78/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/ctyme/linuxapps/dovecot/dovecot-1.0-test78/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/ctyme/linuxapps/dovecot/dovecot-1.0-test78' make: *** [all] Error 2 -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost
by Dovecot 19 Jul '05

19 Jul '05

I installed Dovecot on our FC3 sendmail server and get this from our Dallas office ( out of state to me ). dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost Only one Dallas user can get mail (pop3 or imap). All local users work fine. I ended upgoing back to UW and all works fine. What should I look for? Thanks

1 0

Re: [Dovecot] linux 2.4 vs 2.6 kernel
by Brian Bartholomew 19 Jul '05

19 Jul '05

I can heartily recommend reiserfs on kernel 2.4 for Intel and Sparc. My spam filtering setup currently has 27K files in a quarantine dir, and it works just fine. In a year and a half over 50 machines I've had three corrupted reiserfs filesystems, none of them on production machines, at least one of which I can blame on a bad disk. I would not be surprised to learn they were all bad disks, because the disks are five+ years old. For the last one I moved the bad dir aside where it sat peacefully for a week, and when I fsck'ed it the more aggressive mode of fsck coredumped partway through and it became unaccessable. I then restored it from the tar I had made prior. Brian

1 0

[Dovecot] IMAP: Get rid of non-existent folders below INBOX
by André Wendt 19 Jul '05

19 Jul '05

Hi, I am using Debian Sarge w/ dovecot-imapd package 0.99.14-1. Squirrelmail created three folders below INBOX, Drafts/Sent/Trash, that I already had elsewhere. Thus, I deleted them (through SqM). However, both Thunderbird and Squirrelmail still show these folders anyway. When I select them, I keep getting "Mailbox does not exist" errors. I already tried to move all .imap.index* files in .INBOX/ out of the way -- dovecot created new ones but the folders still appear. I am stuck. How can I prevent dovecot from advertising those non-existent folders? Is this an index-structure problem? I'd appreciate any suggestions. Thanks, -- André

3 2

[Dovecot] UID errors?
by Matt Juszczak 18 Jul '05

18 Jul '05

Hi all, Keep getting these messages: Jul 18 09:48:47 orxon dovecot: POP3(d2525): mbox sync: UID inserted in the middle of mailbox /var/mail/d2525 (109 > 3) Jul 18 09:48:47 orxon dovecot: POP3(d2525): X-IMAPbase uid-last unexpectedly points outside mbox file /var/mail/d2525 For a bunch of users. Any ideas?

2 2

[Dovecot] dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost
by Donald Gunn 18 Jul '05

18 Jul '05

I installed Dovecot on our FC3 sendmail server and get this from our Dallas office. dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost Only one user can get mail (pop3 or imap). All local users work fine. I ended upgoing back to UW and all works fine. What should I look for? Thanks

1 0

[Dovecot] issues/workarounds to build dovecot on OSX
by OpenMacNews 17 Jul '05

17 Jul '05

hi all, a few notes/issues re: building dovecot on OSX. first, after DL of cvs-head, % autogen.sh reports: autogen.sh: line 2: libtoolize: command not found o OSX, 'libtoolize' has been sed'd to glibtoolize. couple of ways to deal with this: (a) edit in autogen.sh aclocal --- libtoolize --force +++ glibtoolize --force automake --add-missing autoheader autoconf (b) run % autoreconf -i -f instead (c) i suppose yout can link: % ln -s /usr/bin/glibtoolize /usr/bin/libtoolize imho, too 'kludgy' ... never tried it. (d) put some sort of conditional in autogen.sh ... many options of course e.g.: HOSTTYPE=`uname` if [ "$HOSTTYPE" == "Darwin" ]; then LIBTOOLIZE=glibtoolize else LIBTOOLIZE=libtoolize fi fwiw, i'm using (b) --> % autoreconf -i -f successfully. next, dovecot's ./configure fails at the check for openssl: ... checking whether va_lists can be copied by value... yes ./configure: line 27241: syntax error near unexpected token `SSL,' ./configure: line 27241: ` PKG_CHECK_MODULES(SSL, openssl)' % within a pkg-config stanza ... as pkg-config does not exist on OSX, a couple of hacks in 'configure.in': =================================================== (EDITOR) configure.in @1032 if test "$want_openssl" = "yes" && test "$have_ssl" = "no"; then --- if pkg-config --exists openssl; then +++ if test -f openssl; then --- PKG_CHECK_MODULES(SSL, openssl) CFLAGS="$CFLAGS $SSL_CFLAGS" =================================================== , followed, of course, by another: % autoreconf -i -f take care of the problem. with changes as above, 'configure' with: ./configure \ --prefix=/usr/local/dovecot \ --exec-prefix=/usr/local/dovecot \ --bindir=/usr/local/dovecot/bin \ --sbindir=/usr/local/dovecot/sbin \ --libexecdir=/usr/local/dovecot/libexec \ --libdir=/usr/local/dovecot/lib \ --includedir=/usr/local/dovecot/include \ --sysconfdir=/var/Settings/Dovecot \ --localstatedir=/var/Process \ --mandir=/var/Documentation/man \ --datadir=/var/Data/Dovecot \ --with-ssl=openssl --with-ssldir=/usr/local \ --with-rundir=/var/Process/dovecot \ --with-moduledir=/usr/local/dovecot-modules \ --enable-shared \ --enable-static \ --enable-ipv6 \ --with-pgsql \ --disable-debug completes sueccessfully, as do: make make check make install resulting in: % ls -aR .: . .. libexec sbin ./libexec: . .. dovecot ./libexec/dovecot: . checkpassword-reply dovecot-auth imap-login pop3-login .. deliver imap pop3 rawlog ./sbin: . .. dovecot dovecotpw as, i believe, expected. now, onward! cheers, richard

1 0

[Dovecot] "dovecot virgin": 1st questions ...
by OpenMacNews 17 Jul '05

17 Jul '05

hi all, "uncle"! i've thrown up my hands with cyrus, and am looking for a 'better alternative' ... i'm brand new to dovecot (haven't even built it yet ...), and have spent the last while reading through the LIST archives here. apart from the TECHNICAL aspects, which seem _more_ than adequate/competitive, i'm most attracted by a comment abt this LIST/community: > awesome technical support with patient developer-dudes on hand which, in a nutshell, is what i seem to be missing. so, i'm preparing to "take the plunge" w/ dovecot. two preliminary questions, if i might: (1) what sort of *interest* is there here (Timo? others?) in Dovecot on OSX? i'm usually able to get most anything up-n-runnig on my OSX boxes, but i'd like to join a community where every issue-on-Mac is not simply ignored/slammed ... and there might be folks willing to work with me on issues (2) here-we-go-again with the Maildir/Mbox decision :-) what's the latest thinking/recommendation here wrt mailbox/mdir? my specifics are -- i intend to backend Dovecot with Exim ... and will run my server 'closed box' ... i.e., no file-system-related User accounts. rather, just 'virtual' spaces. i'm leaning towards Maildir's one-flat-file-per-message format, with an eventual/possible move to storage in PostgreSQL if/when Dovecot adds the capability ... thoughts? (yes, i know, y'all must've had the discussion a g'zillion times ... a pointer to a good/relevant thread is great too!) cheers, richard

2 2

[Dovecot] Authentication feature I need
by Marc Perkel 17 Jul '05

17 Jul '05

OK - here's whay I need to make it work for my Linuxconf compatible authentication system. First - a question: Will this work? I can find docs on "virtualfile. auth virtualfile { mechanisms = plain digest-md5 userdb = passwd-file /etc/vmail/passwd.%d passdb = passwd-file /etc/vmail/shadow.%d user = root } Then - since the dmain name selects the passwd file, if there were a feature to make %n be us user instead of the whole email address then I have what I need. Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and /etc/shadow files. The user name within the files would be the %n part of the email address passed to authenticate with. Basically the password file names are /etc/vmail/passwd.%d with the user withing the file being %n. marc:x:40000:12:Marc Perkel:/vhome/perkel.com/home/marc:/bin/false test:x:40001:12::/vhome/perkel.com/home/test:/bin/false dd:x:40002:12:Atia:/vhome/perkel.com/home/dd:/bin/false test2:x:40003:12::/vhome/perkel.com/home/test2:/bin/false

2 3

[Dovecot] Feature Request - Authentication Scheme - Linuxconf
by Marc Perkel 17 Jul '05

17 Jul '05

This would make my life a lot easier in migrating to Dovecot. And it should be really easy to implement. Here's how linuxconf does it: Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and /etc/shadow files. The user name within the files would be the %n part of the email address passed to authenticate with. Basically the password file names are /etc/vmail/passwd.%d with the user withing the file being %n. marc:x:40000:12:Marc Perkel:/vhome/perkel.com/home/marc:/bin/false test:x:40001:12::/vhome/perkel.com/home/test:/bin/false dd:x:40002:12:Atia:/vhome/perkel.com/home/dd:/bin/false test2:x:40003:12::/vhome/perkel.com/home/test2:/bin/false It also makes merging several servers with separate passwd/shadow files into one virtual system because all you have to do is copy their existing passwd/shadow files into the /etc/vmail directory and rename them with the domain at the end. So - wouldn't that be easy to add? Sure would make migrating easy for me. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 4

[Dovecot] user_db, uid/gid and maildir
by vmstech 17 Jul '05

17 Jul '05

Im experimenting with putting all my virtual users mail under 1 directory with belonging to a system user created for the purpose. The mode on the directory (and subdirectories) is 770. I keep all my virtual users details in a postgres database. My interpretation of the wiki documentation is that if the user_db query returns a uid column and a gid column containing the numeric uid and gid of the owner of the directory, then dovecot should have no problem using mail in these folders. Is that correct? (I'm actually getting permission errors appear in the log file on the directories when I try and attach with a client, which reports "Cannot get LIST information for pattern `*' on IMAP server a.b.com unknown".) thanks Glenn

1 0

[Dovecot] Authenticaing in postgresql
by vmstech 17 Jul '05

17 Jul '05

Hi all - Im new to dovecot and actually all things email serverish. I spent last week wrestling with exim4, and this week its dovecots turn. I'm trying to connect as an imap user (from evolution) and not actually able to make a successful login. I have default_pass_scheme=PLAIN, and am using pass authentication in evolution client. Its the only one available after it queries the server for available types. I'm not getting any errors appear in either the postgres or dovecot log files (anymore :-) that is). I'm getting the exact query I'd like to see in the dovecot log file, after I entering the password in the client, but unfortunately it doesnt give me the reply. I can key this exact query in to the psql client and get the correct answer. dovecots logs don't tell me if I have success or failure. The auth_db query has only 1 column. I have no idea where to go from here - would love a hint thanks Glenn

1 1

Re: [Dovecot] New to dovecot, little luck - signal 10 death for imap
by Jeroen Scheerder 15 Jul '05

15 Jul '05

Peter Evans wrote: > Jeroen Scheerder (Jeroen.Scheerder(a)phil.uu.nl) wrote: > >>However, whenever a mailbox is selected, the imap subprocess dies. >>Jul 13 14:52:05 localhost dovecot: imap-login: Login: js [127.0.0.1] >>Jul 13 14:52:07 localhost dovecot: child 8082 (imap) killed with signal 10 > > > You're going to have to help us to help you. 10 is bus error (I think) > which is badness. > > OS, > version of dovecot > etc. > > you might want to debug a coredump, that will tell you where/why its > dying too. I would merrily gdb into a coredump and stacktrace away, if a core dump were created. No such luck. I'm now logging directly to file using syslog, after having started dovecot. There is no limit on coredumps: % limit cputime unlimited filesize unlimited datasize unlimited stacksize 8MB coredumpsize unlimited descriptors 64 vmemorysize unlimited % more /tmp/dovecot* :::::::::::::: /tmp/dovecot-info.log :::::::::::::: dovecot: Jul 13 15:27:35 Info: Dovecot v1.0-stable starting up dovecot: Jul 13 15:28:21 Info: imap-login: Login: avank [127.0.0.1] :::::::::::::: /tmp/dovecot.log :::::::::::::: dovecot: Jul 13 15:28:21 Error: child 14882 (imap) killed with signal 10 Environmental details: Solaris 7 (sparc) dovecot 1.0-stable compiled with ldap support using gcc 3.3.4 4.0.0 4.0.1 (no difference here) configured for mbox support with locking matching procmail's delivery locking strategies with authentication using passwd/shadow native databases A header dump shows nothing suspect: % elfdump -d /phil/sunos/sparc/pkg/dovecot-1.0-stable/libexec/dovecot/imap Dynamic Section: .dynamic index tag value [0] NEEDED 0x1 libsocket.so.1 [1] NEEDED 0x117 librt.so.1 [2] NEEDED 0x140 libc.so.1 [3] NEEDED 0x397 libnsl.so.1 [4] NEEDED 0x3b3 libdl.so.1 [5] RPATH 0x3cc /phil/sw/sunos/sparc/lib [snip] Will try on Solaris 10.

4 9

[Dovecot] OS X Mail.app 2 (Tiger) + dovecot -> new mail count doubled
by Alan Schmitt 14 Jul '05

14 Jul '05

Hello, I've noticed a strange bug with Mail.app 2 (from OS X.4) and dovecot, and I'm trying to identify where it comes from. I have a bunch of mailboxes that can receive new mail (delivered by procmail) and I have Mail set up as to automatically synchronize all maiboxes. When I start up Mail, the count for new mail is doubled in every mailbox that I have not seen yet. Looking at a mailbox restores the correct count (mail is not actually duplicated, it's just the new mail counter that is wrong). Has anyone else seen this? Would this bug be from Mail.app or from dovecot? (I suspect the former.) Thanks a lot, Alan Schmitt

3 6

[Dovecot] Very slow select() command on large mailboxes
by Sebastjan Trepca 14 Jul '05

14 Jul '05

Hi, I'm trying to decide if I could use you mail server in our enviroment which has about 10k users and mailboxes size about ~1GB. So I made a few tests and it all worked quite fast, except that select command on large mailboxes. The first time I select a mailbox which has 10k messages it takes about 4s to process. I am deliberately trying this on a Celeron 850Mhz, 512 MB memory and some shitty hard-drive to maximize the times. So why is this so slow? Does it index the messages on select? It's even slower when I have some new messages in folder, more that I have more I wait. So I presume it must be something with indexing? Anyway, how could I optimize this? Why don't you index when a mail arrives instead of on select? Thanks for help and keep doing a great job with Dovecot. Sebastjan

4 3

[Fwd: Re: [Dovecot] Dovecot and ActiveDirectory]
by Chris Wakelin 14 Jul '05

14 Jul '05

Oops! Thought I'd CC'd this to the list. Sorry, Oliver! Chris -------- Original Message -------- Date: Wed, 13 Jul 2005 20:09:35 +0100 From: Chris Wakelin <c.d.wakelin(a)reading.ac.uk> To: Jeroen Scheerder <Jeroen.Scheerder(a)phil.uu.nl> CC: Chris Wakelin <c.d.wakelin(a)reading.ac.uk> Subject: Re: [Dovecot] Dovecot and ActiveDirectory Jeroen Scheerder wrote: > Chris Wakelin (13/7/05 16:08 +0100) [Re: [Dovecot] Dovecot and > ActiveDirectory]: > > >>I've got it working via PAM and pam_ldap on Solaris. [..] > > > That's exactly what I'm striving to do. > > I've never set up LDAP authentication for Solaris itself, and actually > never used PAM before. > > If I may be so bold, could I bother you for details about your > configuration in these respects? /opt/RDGpldap/etc/ldap.conf: host xxx.rdg.ac.uk base dc=xxxxx,dc=ad,dc=rdg,dc=ac,dc=uk binddn cn=xxxuser,cn=users,dc=xxxxx,dc=ad,dc=rdg,dc=ac,dc=uk bindpw xxxpasswd nss_map_objectclass posixAccount user nss_map_objectclass shadowAccount user nss_map_attribute uid sAMAccountName nss_map_attribute homeDirectory unixHomeDirectory nss_map_attribute shadowLastChange pwdLastSet nss_map_objectclass posixGroup group nss_map_attribute uniqueMember member pam_login_attribute sAMAccountName pam_filter objectclass=User pam_password ad xxxuser is a read-only account in the AD. /etc/pam.conf: ... dovecot auth required /opt/RDGpldap/lib/pam_ldap.so dovecot account required /opt/RDGpldap/lib/pam_ldap.so dovecot session required /opt/RDGpldap/lib/pam_ldap.so dovecot.conf: auth_username_translation = AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz auth default { mechanisms = plain login passdb = pam userdb = passwd user = root } The auth_username_translation is because AD users are case-insensitive but UNIX ones aren't! We have users in both AD and UNIX (but could use something like "userdb=static uid=xxxx gid=yyyy home=/var/mail/%Lu" assuming xxxx:yyyy has appropriate permissions on the spool files) pam_ldap-178 was configured with ./configure --prefix=/opt/RDGpldap \ --with-ldap-conf-file=/opt/RDGpldap/etc/ldap.conf Hope this helps, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

Re: [Dovecot] problem with server certificate: dovectot.pem
by Joseph Tam 14 Jul '05

14 Jul '05

> Date: Wed, 13 Jul 2005 23:46:33 +0300 > From: vladone <vladone(a)spaingsm.com> > Subject: [Dovecot] problem with server certificate: dovectot.pem > > I have an mail server with postfix and dovecot. > All works fine, but now is change my domain. After changed > configurations i can receive (or send) mail without STARTTLS, > but when i try to use this option i receive: > "TLS handshake failure. Invalid server certificate (Key material > mismatch)" > > I dont know what is this. > I use certificate that is generate with script for dovecot (that work > at begining). > Even i try to rebuild this certificate acording with new domain but > nothing. > Where is my problem? Yes, of course. Certificates are made out to a particular hostname (e.g. smtp.wahtever.com) and if you change your server hostname or move it to another server, a new certificate will have to be made out to the new hostname. You could also configure your client ignore certificate mismatches, but this wouldn't be the best option. Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] Search with specified charset
by Chris Wakelin 14 Jul '05

14 Jul '05

I've seen a problem with searching in the Prayer webmail client that turns out to be caused by Prayer insisting on a charset called "ISO-8859-1" and Dovecot, using Solaris iconv, not recognising it (all the Solaris 8 iconv modules appear to be "ISO8859-1" etc. or just "8859-1"). This isn't a problem in Linux: % iconv --list | grep 8859.1/ 8859_1// ISO-8859-1// ISO8859-1// ISO885911// ISO_8859-1// I've hacked together a patch for Dovecot to try matching without the "ISO-" prefix if matching fails at first, which works for Solaris (as would creating an extra symbolic link in /usr/lib/iconv or hacking Prayer to use "ISO8859-1") and it doesn't break Linux, but it's not pretty :( Better may be to try substituting underscores, hyphens, spaces(?) and nothing in the string, but that makes the change much more complicated! Best Wishes, Chris --- dovecot-1.0-stable/src/lib-charset/charset-iconv.c.orig Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-charset/charset-iconv.c Wed Jul 13 21:47:03 2005 @@ -36,9 +36,17 @@ ascii = FALSE; cd = iconv_open("UTF-8", charset); if (cd == (iconv_t)-1) { - if (unknown_charset != NULL) - *unknown_charset = TRUE; - return NULL; + /* Try matching charset without "ISO" prefix */ + if (strncasecmp(charset, "ISO-", 4) == 0 || + strncasecmp(charset, "ISO ", 4) == 0) + cd = iconv_open("UTF-8", charset + 4); + else if (strncasecmp(charset, "ISO", 3) == 0) + cd = iconv_open("UTF-8", charset + 3); + if (cd == (iconv_t)-1) { + if (unknown_charset != NULL) + *unknown_charset = TRUE; + return NULL; + } } } @@ -137,9 +145,17 @@ cd = iconv_open("UTF-8", charset); if (cd == (iconv_t)-1) { - if (unknown_charset != NULL) - *unknown_charset = TRUE; - return NULL; + /* Try matching charset without "ISO" prefix */ + if (strncasecmp(charset, "ISO-", 4) == 0 || + strncasecmp(charset, "ISO ", 4) == 0) + cd = iconv_open("UTF-8", charset + 4); + else if (strncasecmp(charset, "ISO", 3) == 0) + cd = iconv_open("UTF-8", charset + 3); + if (cd == (iconv_t)-1) { + if (unknown_charset != NULL) + *unknown_charset = TRUE; + return NULL; + } } if (unknown_charset != NULL) -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] problem with server certificate: dovectot.pem
by vladone 13 Jul '05

13 Jul '05

Hi! I have an mail server with postfix and dovecot. All works fine, but now is change my domain. After changed configurations i can receive (or send) mail without STARTTLS, but when i try to use this option i receive: "TLS handshake failure. Invalid server certificate (Key material mismatch)" I dont know what is this. I use certificate that is generate with script for dovecot (that work at begining). Even i try to rebuild this certificate acording with new domain but nothing. Where is my problem? P.S. All works before changed my domain!!!

1 0

[Dovecot] file locks
by Obantec Support 13 Jul '05

13 Jul '05

Hi I am trying to install 1.0 stable from source on a test server running 0.99 on FC3. i did basic ./configure etc and get this result Jul 13 17:24:26 proteus4 dovecot: Dovecot v1.0-stable starting up Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): open(/var/spool/mail/.temp.proteus4.4485.e3eec7b26a559bac) failed: Permission denied Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): file_lock_dotlock() failed with mbox file /var/spool/mail/obantec: Permission denied Jul 13 17:24:35 proteus4 dovecot: pop3-login: Login: obantec [192.168.0.10] when trying to access a test account. permissions all look as per old 0.99 which did work. Mark

3 5

[Dovecot] Minor bugs still in test77
by Chris Wakelin 13 Jul '05

13 Jul '05

Thinking of patches I always apply, I've got a couple (attached) that fix minor bugs and maybe should be applied - or implemented better and then applied ;) - to the main distribution? 1) LIST bugs: LIST "~/mail/" "" and LIST "" "~/mail/" (where "~/mail/" is a namespace prefix) don't reply the same way as UW-IMAP does and in at least the first case, still violates the spec (your fix breaks, as namespace_find() modifies its argument) The second issue breaks Pine 4.x, I think. 2) Angle-addresses If a header address is just "<someone(a)somewhere.org>" rather than "Someone <someone(a)somewhere.org>" or "someone(a)somewhere.org", then the FETCH ... ENVELOPE command responds with "" as the personal name, rather than NIL, which may confuse clients (without being wrong, technically, I think). (In case anyone's interested, I also use patches to: 1) fix the 64bit issue mentioned earlier today 2) introduce extra logging of LIST, SUBSCRIBE and UNSUBSCRIBE (for debugging during our migration from UW-IMAP) 3) rename .subscriptions to .mailboxlist and store folder names in it including the namespace prefix (to emulate UW-IMAP) 4) implement a Reading-specific hashing algorithm for the mail spool location as an extra variable modifier "%H" (e.g. "/export/mail/%Hu/%u/INBOX") 5) remove the need for /dev/urandom, which isn't available on our mail server (though there is a Solaris patch available to create it). 6) add an option to hide "AUTH=PLAIN" in the CAPABILITY string as Pine 4.x complains loudly when this is advertised on a non-SSL connection ) Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 --- dovecot-1.0-test77.orig/src/imap/cmd-list.c Sun Apr 17 17:37:05 2005 +++ dovecot-1.0-test77/src/imap/cmd-list.c Wed Jul 13 16:10:27 2005 @@ -372,7 +372,8 @@ concept which probably no other client uses than Pine. Just try our best to emulate UW-IMAP behavior and hopefully we're fine. */ - ns = namespace_find(client->namespaces, &ref); + const char *ref_copy = t_strdup(ref); + ns = namespace_find(client->namespaces, &ref_copy); if (ns == NULL) { const char *empty = ""; ns = namespace_find(client->namespaces, &empty); @@ -405,6 +406,28 @@ } client_send_tagline(cmd, "OK List completed."); } else { + + if (*ref == '\0' && !lsub) { + /* LIST "" "something" */ + const char *mask_copy = t_strdup(mask); + ns = namespace_find(client->namespaces, &mask_copy); + if (ns == NULL) { + const char *empty = ""; + ns = namespace_find(client->namespaces, &empty); + } + if (*ns->prefix != '\0' && *mask_copy == '\0') { + /* namespace, return it */ + string_t *str = t_str_new(64); + str_printfa(str, "* LIST (\\Noselect) \"%s\" ", + ns->sep_str); + imap_quote_append_string(str, ns->prefix, + FALSE); + client_send_line(client, str_c(str)); + client_send_tagline(client, "OK List completed."); + return TRUE; + } + } + ctx = p_new(cmd->pool, struct cmd_list_context, 1); ctx->ref = ref; ctx->mask = mask; --- dovecot-1.0-test77.orig/src/lib-mail/message-address.c Fri Apr 8 12:16:36 2005 +++ dovecot-1.0-test77/src/lib-mail/message-address.c Wed Jul 13 16:15:15 2005 @@ -140,6 +140,10 @@ return -1; ctx->addr.name = p_strdup(ctx->pool, str_c(ctx->str)); + if (*ctx->addr.name == '\0') { + /* Cope with "<address>" without display name */ + ctx->addr.name = NULL; + } if (parse_angle_addr(ctx) < 0) { /* broken */ ctx->addr.domain = p_strdup(ctx->pool, "SYNTAX_ERROR");

1 0

[Dovecot] Dovecot and ActiveDirectory
by Hoffmann, Oliver 13 Jul '05

13 Jul '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Is there a solution to auth dovecot against an windows active directory? i've tried this config: - --- # Space separated list of LDAP hosts to use. host:port is allowed too. hosts = dc.foo.bar # Distinguished Name - the username used to login to the LDAP server dn = cn=oh,cn=Users,dc=foo,dc=bar # Password for LDAP server dnpass = password # LDAP protocol version to use. Likely 2 or 3. ldap_version = 3 # LDAP base base = cn=Users,dc=foo,dc=bar # Dereference: never, searching, finding, always #deref = never # Search scope: base, onelevel, subtree scope = subtree # User attributes in order: user_attrs = uid,homeDirectory,,,uidNumber,gidNumber # Filter for user lookup. Some variables can be used: #user_filter = (&(objectClass=posixAccount)(uid=%u)) # Password checking attributes in order: pass_attrs = uid,userPassword # Filter for password lookups #pass_filter = (&(objectClass=posixAccount)(uid=%u)) # Default password scheme. "{scheme}" before password overrides this. #default_pass_scheme = CRYPT # You can use same UID and GID for all user accounts if you really want # to. # If the UID/GID is still found from LDAP reply, it overrides these values. #user_global_uid = #user_global_gid = - --- but got this error: - --- dovecot-auth: Jul 13 16:42:09 Error: ldap(oh): unknown user - --- thx & greets oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFC1S162+wHtX4o3oARAo+SAJ9EGVQPXBG+gtZmcbkOjMiy0xF2JACgigDs +6q+EW0zjsICqME310Ky41M= =sMRS -----END PGP SIGNATURE-----

2 1

[Dovecot] New to dovecot, little luck - signal 10 death for imap
by Jeroen Scheerder 13 Jul '05

13 Jul '05

Hi, I'm a new prospective dovecot user. I'm planning to migrate a medium-scale mail site (a few thousand users) from UW to something better. I've set up dovecot on a test system. I can connect and authenticate just fine. IMAP clients get to see the right mailboxes. However, whenever a mailbox is selected, the imap subprocess dies. The log shows: Jul 13 14:52:05 localhost dovecot: imap-login: Login: js [127.0.0.1] Jul 13 14:52:07 localhost dovecot: child 8082 (imap) killed with signal 10 When I either telnet to it manually or run the "imap" process in a terminal window, everything seems to work: ---- Snip ---- * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as js x select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1300 EXISTS * 0 RECENT * OK [UNSEEN 2] First unseen. * OK [UIDVALIDITY 1119092680] UIDs valid * OK [UIDNEXT 1590] Predicted next UID x OK [READ-WRITE] Select completed. x fetch 1 full * 1 FETCH (FLAGS (\Seen) INTERNALDATE "18-Jun-2005 05:00:02 +0200" RFC822.SIZE 1773 ENVELOPE ("Sat, 18 Jun 2005 05:00:01 +0200 (MET DST)" "Waarschuwing: uw inbox overschrijdt 80% van de groottelimiet (18-06-2005)" (("Super-User" NIL "helpdesk" "phil.uu.nl")) (("Super-User" NIL "helpdesk" "phil.uu.nl")) (("Super-User" NIL "helpdesk" "phil.uu.nl")) ((NIL NIL "js" "phil.uu.nl")) NIL NIL NIL "<20050618030001.B5F3952048(a)goedel.admin.phil.uu.nl>") BODY ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 1082 25)) x OK Fetch completed. x fetch 1 body[text] * 1 FETCH (BODY[TEXT] {1082} Beste Jeroen Scheerder, [...] Met vriendelijke groet, het systeembeheer. ) x OK Fetch completed. x list * * * LIST (\Noselect \HasChildren) "/" "Archive/" [...] * LIST (\Unmarked) "/" "INBOX" x OK List completed. ---- Snip ---- I'm at a loss here, and no amount of logging or sniffing with tcpdump has revealed anything interesting so far. Does anyone else see these "signal 10" aborts? Is there any way in which I can force a coredump (in case it's *really* a bus error)? Regards, Jeroen.

1 0

Re: [Dovecot] mysql
by John Peacock 13 Jul '05

13 Jul '05

Peter Evans wrote: > Because you might, just possibly want performance that > doesn't resemble mollasses in midwinter? > Optionally, you might even want something where the response > time is deterministic. I think you need to take your biases and go someplace else. If you don't like MySQL because of some personal bias, then don't use it. Anyone halfway competent can build Dovecot themselves and not rely on some third-party RPM's that have dependencies. This is a discussion list for Dovecot. Please try and stay on topic... John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747

1 0

Re: [Dovecot] mysql
by Andrew Hutchings 13 Jul '05

13 Jul '05

Peter Evans wrote: > Dominic Marks (dom(a)goodforbusiness.co.uk) wrote: > > Because you might, just possibly want performance that > doesn't resemble mollasses in midwinter? > Optionally, you might even want something where the response > time is deterministic. > > Points at the company mail system here for a prime example > of why not to use mysql. But then again, this is actually > a prime example of "it works, but we don't know how." > > P > > We use mysql here as it makes a perfect integration with the rest of our systems, we have over 6000 mail accounts (probably closer to 7000 now) on it and the mysql lookup time is pretty much instant, the load never goes above 0.5 on the systems (2x1GHz Epias on round robin with replicated databases on each) and most of that is because the POP/IMAP servers are also round robin MX servers so Exim can take a chunk out of the CPU. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 2: "In most countries selling harmful things like drugs is punishable. Then howcome people can sell Microsoft software and go unpunished?" - Hasse Skrifvars

1 0

[Dovecot] Headers "missing" in new CVS version
by Todd Burroughs 13 Jul '05

13 Jul '05

We're experiencing an odd problem with dovecot "losing" headers. This started happening with the CVS release as of July 4 and still happens with July 12. It was working properly June 28. It does not happen using pine or thunderbird. It happens using webmail (twig). When you open the inbox, you see subject, etc. When you open a mail, all of the headers are gone. Returning to the inbox, all the headers are missing. It seems to cache this as well. After returning to the older dovecot, all of the headers are missing. Deleting the cache files fixes this and there does not seem to be any mbox corruption. It does not log any errors or crash. Todd Burroughs

2 1

[Dovecot] separate SSL certificates for pop3s and imaps
by Michael Weiser 13 Jul '05

13 Jul '05

Hi, I'm migrating a uw-imap installation to dovecot. With uw-imap I had different SSL certificates and keys for ipop3d and imapd. How can I configure dovecot to do the same with its pop3s and imaps services? Thanks in advance, -- _________________________creating IT solutions Michael Weiser science + computing ag bei Eisenbahn und Haefen Postfach 11 02 63 Hagellocher Weg 71-75 47142 Duisburg 72070 Tuebingen, Germany phone +49 203 52 26341 www.science-computing.de

2 2

[Dovecot] add inotify support to dovecot
by Johannes Berg 13 Jul '05

13 Jul '05

Hi, attached patch against test76 adds inotify support and the --with-notify=... configure option that defaults to the current check for dnotify using no special method if dnotify cannot be compiled, and can be set to none, dnotify and inotify. If it is set to dnotify or inotify, failure to compile a test program results in an error. Also, it adds | file change notification method ..... : <method> to the output at the end of configure. The only thing I don't like about this patch is the fact that I had to add a field notify_context to struct io, but I didn't see a different way to handle this. Also, the patch doesn't support the condition parameter, it simply always asks for all the relevant changes. I don't really see that it is useful for in the context of file system notifications anyway. I modeled this after ioloop-notify-dn.c with my other patch applied to it, if you don't like the other patch you'll want to "revert" that change in the new ioloop-notify-inotify.c file as well. Oh, and obviously I didn't include patches to configure and all the Makefiles, so of course you'll have to run automake. But you already knew that :) I only tested this with maildir. I did add IN_MODIFY so I think it should work with mbox too, but someone should probably verify. Have fun, johannes

2 2

[Dovecot] sorting question
by Johannes Berg 13 Jul '05

13 Jul '05

Hi, If I understand the thread sorting algorithm correctly (from draft-ietf-imapext-sort-17.txt and the code), it will sort like this (where I use numbers instead of dates with higher numbers being newer mails) 4 10 3 11 2 12 1 13 etc into all the lower levels. Thunderbird will actually sort this like this: 1 13 2 12 3 11 4 10 where threads are sorted by the newest child in them. Now, I am thinking that evolution simply uses dovecot's THREAD feature and doesn't implement anything itself, so that if I wanted to have that kind of threading, I'd have to implement it in dovecot. Would this be easy? I'm thinking that I should just treat all nodes as if they were dummy nodes in sort_root_nodes, but that only fixes the first level afaict, because later dates are not propagated up. Essentially, I think what the algorithm tb uses does is not use a nodes date as it's sorting criterion, but it's newest child, and apply this rule recursively. Does anyone else think this feature would be useful? I regularly end up almost missing mail because it is sorted at such a low position and I don't see the thread at all.. johannes

4 5

[Dovecot] Dovecot runs as ...
by Matt Juszczak 13 Jul '05

13 Jul '05

Hi all, We're using LDAP 100% for everything ... So does that mean that for the following user, I can put another user, like nobody? user = root I guess that user still has to be able to access /var/mail and such, correct?

2 1

[Dovecot] 1.0-test77
by Timo Sirainen 13 Jul '05

13 Jul '05

http://dovecot.org/ It's hot in here. Something like 25-30c for many days now. My brains don't work in that heat. So, this is still not an 1.0-alpha1. I'll put it out when I think the release will actually be fully working :) Changes since test76: - Fixes to FETCHing MIME body parts, especially with message/rfc822 attachments. We hadn't been handling this entirely correctly ever (this part of IMAP spec was pretty difficult for me to understand earlier..). This also caused Dovecot to sometimes disconnect clients fetching [n.MIME] body parts earlier, if someone had that problem. - Maildir: Several bugs fixed with APPEND/COPYing mails - mbox: Keywords weren't stored to index with APPEND - inotify patch by Johannes Berg (and possibly broken by me). Can be enabled with --with-notify=inotify parameter to configure. - SEARCH now doesn't fail if a messageset outside valid range is given to it. Some mobile IMAP client was broken because this didn't work. - Cache mail headers when saving mails to mbox. We should cache everything, but this is a start.. - And other cache file fixes/optimizations

2 3

[Dovecot] PERMANENTFLAGS bug?
by Nils Henrik Tvetene 12 Jul '05

12 Jul '05

Hi, Im new to the list, so might be a FAQ allthough I havent found it anywhere: When I try to connect to dovecot/imap from snappermail (palm), I get a IMAP protocol error. The complaint is about: OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft ) \*)] Flags permitted. As you can see, theres an extra " )" after "Draft". Any clues on how to fix/bypass this? Regards, Nils Henrik Tvetene

3 5

[Dovecot] Dovecot 1.0-stable mbox performance and disconnections
by Chris Wakelin 12 Jul '05

12 Jul '05

I've got some of our busiest users now using Dovecot instead of UW-IMAP with mbox-format mailboxes and predominantly Outlook Express as the client. Doing some perfomance monitoring (with Solaris 8 process accounting), it looks like Dovecot needing to read only 30-50% of the disk blocks needed by UW-IMAP, but I was hoping for better! What seems to happen, is that most of the connections use only a small number of blocks (due to Dovecot indexes, presumably) but occassionally a process will read lots of blocks, sometimes even more than a UW-IMAP session. Is this expected, or is something going wrong with the index updates? I have the default sync settings, I think (mbox_dirty_syncs = yes, mbox_very_dirty_syncs = no, mbox_lazy_writes = yes) My INBOX is an extreme example with ~10,000 messages and most processes reading a few hundred blocks but a couple using 20,000 or so! Also, Dovecot seems to be dropping connections, sometimes, for no good reason (putting some extra i_info lines suggests for "inactivity"). Thunderbird tends to reconnect automatically, though. It seems it may be happening at the end of an IDLE command, something like:- 4 IDLE + idling * 1005 EXISTS DONE * 1005 EXPUNGE but then the expected 4 OK Idle completed never comes. Has anybody else seen this? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] newbie questions
by Stewart Dean 12 Jul '05

12 Jul '05

Thanks in advance for your patience and assistance. Since a system administrator's work is most successful when nobody knows you've done anything....(ugly that...you get neither raises nor equipment funding as a result), I prefer to learn from other's experiences rather than fail in the same pits. We are considering a switch from UW to Dovecot, since our users persist in using the INBOX as a file cabinet (maybe 25% use homedir folders) and we currently have, I think, .mbox INBOXes which are thus getting massively unmanageable and fragile. Machine config: Running IBM AIX 5.2/5.3 on an F80 with 4GB memory (may be upgraded to 16GB), with IBM's sendmail binary at V8.11.6p2, hand compiled procmail at 3.22, 64-bit binary from C for AIX V6.0 Some questions I couldn't find answered in the docs: 1) Crispin of UW has a formats.txt file in which he lists and evaluates the various formats. He calls the INBOX format type we use .unix (one big honking flat file). Q1: Is this what is described in the Dovecot docs mail-storages.txt file as .mbox? 2) Authentication: The DC docs don't mention using NIS/yp for authentication, that I can find. Q2: Does DC support NIS/yp authentication? I guess I could periodically do a ypcat passwd to a file and point DC at it... 3) on IBM's AIX Unix... Q3: Is there anyone out there running DC on AIX? 5.x or 4.3.3? JFS or JFS2? 4) Inbox location/format: = I will want to move from our legacy .mbox format to, I suppose, the DC default of Maildir++. = I will want to do this in groups over time, rather than all at once, so both formats will have to work = The legacy location of INBOXes has been /var/spool/mail/<userid>. The docs appear to say that Maildir format INBOXes should be in ~/Maildir. Q4:Can the INBOXes be in two location, the converted new Maildirs in ~, and the old unconverted in vsm? Or will I have to override the DC cfg'ed INBOX location to be VSM until I get them all converted and then move them all to ~/Maildir and change the DC config to that? 5) Some mention was made of procmail configuration issues Q5: Can procmail support both formats/locations, or will I have to put changes in the migrated users' procmailrc (what fun!)? Again, thanks! -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

5 4

[Dovecot] mysql
by Jim Edwards 12 Jul '05

12 Jul '05

Hello, Does dovecot require mysql in order to work? Fedora rpms are claiming mysql dependencies. I'm sure you're aware of the long-lived arguement of postgresql v. mysql. If it wasn't your intention to force this, then please snarl at Red Hat. If it was your intention, then grrrrr! Thanks for this product. I like it for it's speed and stability. Jim Edwards

4 3

[Dovecot] bug: very strange behavior with pop3
by Yannick Majoros 12 Jul '05

12 Jul '05

Hello, We have some strange problem which could be related to authentication here. All our user info is in an openldap directory. We normally use pam/getpwent in dovecot to access our user accounts, via nss_ldap/pam_ldap, but we tried to connect directly to the ldap server, with the very same results. We have one user (out of 100) which just cannot use dovecot with pop3. His login/password are accepted, and then dovecot doesn't say anything. I am sure it isn't a client issue: same result with Eudora, Thunderbird and while directly connecting through openssl to POP3s port and "talking POP3". Here is some session transcript: +OK dovecot ready. USER rinstalle +OK PASS M=/)p365 +OK Logged in. And it then stops responding (without giving a reason, breaking the connection). Nothing in the logs, it sees this as a regular login and that's all... Now, it seems that when I copy this user in ldap, the new one occasionaly works. I first thought it did depend on the user name (uid or dn), but it doesn't seem to be the case. I think it is just random. Here is an ldif of this user: dn: uid=rinstalle,ou=divers,ou=login,ou=Autres,ou=Personnes,dc=inma,dc=ucl,dc= ac,dc=be uid: rinstalle cn: compte foireux homeDirectory: /home/xx sn: xxxx uidNumber: 9999 objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount gidNumber: 999 ... And getent result (with nss_ldap): #getent passwd rinstalle rinstalle:x:9999:999:compte foireux:/home/xx: To be complete, I should mention that it _does_ work when using local password files... I solved the user problem just by copying his entry a few times. Now, I don't think it is purely ldap-related, as the login _is_ accepted. Is there some guru out here who could help us? Thank you, -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

2 4

[Dovecot] weird IDLE behaviour
by Johannes Berg 12 Jul '05

12 Jul '05

Hi, So I was testing things with inotify notifications enabled and noticed that when I a) select a mailbox other than the inbox b) IDLE c) copy mail into the /new folder in that mailbox nothing happens! So I straced it and it always opens the inbox's new/ and cur/ directories for notifications. Is that the correct behaviour? I assumed that if I select some mailbox other than the inbox, IDLE should inform me of status updates in that box, since RFC 2177 says: The Internet Message Access Protocol [IMAP4] requires a client to poll the server for changes to the selected mailbox (new mail, deletions). Now, I get this behaviour by applying the attached patch. But even if I'm wrong, dovecot doesn't implement any sensible behaviour, as it only ever creates *any* notifications during IDLE when the INBOX is selected. [hm. note that I'm only testing maildir] johannes

2 1

[Dovecot] xinetd + dovecot
by vlad 12 Jul '05

12 Jul '05

Hello dovecot, Help me running imapd & pop3d server on xinetd. My file: # cat /etc/xinetd.d/pop-3 service pop3 { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/pop3-login } ####################################### # cat /etc/xinetd.d/imap service imap { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/imap-login flags = IPv4 log_type = FILE /var/log/mail/dovecot log_on_success = PID HOST USERID } ####################################### But... # nmap 192.168.1.1 Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2005-07-12 16:53 YEKST Interesting ports on myhost.ru (192.168.1.1): (The 1653 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 25/tcp open smtp 80/tcp open http 110/tcp open pop3 143/tcp open imap 3128/tcp open squid-http ########### # telnet 192.168.1.1 143 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. # telnet 192.168.1.1 110 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. Help :) -- With best wishes, vlad mailto:faktroot@mail.ru System/Network Administrator TV/Video Engineer ICQ 163227020 ---------------------------------------------- В любом из нас спит гений. И с каждым днем все крепче...

2 1

[Dovecot] POP retrieval, then reading, of mail does not udpate server status.
by Paul Vatta 12 Jul '05

12 Jul '05

We are currently using the version of Dovecot (0.99.11) that comes with Redhat Enterpise Linux version 4, running on an IBM x445 server (8 CPU, hyperthreading on, 14GB RAM) using the maildir format. We have had to patch this with a change from 0.99.12 so that it doesn't incorrectly report SASL capability upon connection but otherwise it is the version supplied with the OS (we do this to ensure that we don't deviate from the supplied packages too much). The problem encountered is the status of emails on the server isn't being updated. The POP client (Eudora 6.2 in this instance) will retrieve the message, have the message read, apparently update the status on the server (via the "Check Mail" function), but yet the status on the server has not been updated as read (verified by going into our IMP Webmail client, and looking at the mail message in the mailstore - there is no ".S" extension). Using the IMAP protocol doesn't bring about this behaviour. The inconsistency The inconsistency between POP clients and the server status doesn't occur when it comes to deleting messages. Is this a bug, or have we misunderstood how the POP protocol works. Looking at the following: http://www.eudora.com/techsupport/kb/2587hq.html I'm guessing that the POP protocol doesn't update the status? Your confirmation would be most appreciated. Thanks, Paul P.S. As an aside, if you are hesitant about the move from mbox to maildir, don't consider this an obstacle. Our migration was painless and the benefits far outweigh the conversion effort. Dovecot has introduced huge improvements over our Qpopper/UW-IMAP configuration.

2 1

[Dovecot] Calypso or Opera Mail problem?
by Obantec Support 12 Jul '05

12 Jul '05

Hi Are there any know issues with dovecot using pop3 & (Calypso or Opera Mail) ? Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): File isn't in mbox format: /var/spool/mail/cambcom_brianlj Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): Couldn't open INBOX: Internal error occurred. Error report written to server log. [2005-07-11 09:14:47 there is a file cambcom_brianlj and using webmin or neomail the mails can be read. Mark -- Obantec Support

2 1

Re: [Dovecot] mysql
by Dominic Marks 12 Jul '05

12 Jul '05

On Tuesday 12 July 2005 14:55, Peter Evans wrote: > Tomi Hakala (tomi.hakala(a)clinet.fi) wrote: > > Jim Edwards wrote: > > > Does dovecot require mysql in order to work? > > > > For common email serving with IMAP and POP3, no. > > For IMAP and POP3 session proxying with 1.0-test releases, yes. > > Ew, YUCK. > Why does everyone think $DATABASE is the panacea for all ills? Why you think this is a misuse of a database? Shared network storage might not have been the original purpose, but most DBs can do a pretty good job of this. > Just because they can't/won't cope with multiplicity, does not > mean that X megabytes of general purpose database and all the > overheads have to be used. I can't tell if you have a problem with databases in general, or just the MySQL implementation from this. I guess that you could modify the code easily to use another DBMS which is much smaller such as sqlite. > If it's just proxying, why can't it speak LDAP, or even just a > plain file ... Why write code from scratch when you can use an API for a trusted piece of software which is likely to be available on most systems already? > P > > (I haven't looked at 1.0-test-903 yet, I think I'm still on 70 > something, but no way am I installing mysql ...) Cheers, -- Dominic Marks

1 0

[Dovecot] Mail spools keep getting corrupted with .99.x
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, My mail spools (mbox format) keep getting corrupted with .99.x. I was thinking of running dovecot-stable-20050709.tar.gz ... is this fairly stable? Also, can I use the .99 config file with that code? Thanks! -MAtt

2 1

[Dovecot] Dovecot without a chroot
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, We're running dovecot without a chroot (mail admin's request), but we're running it as a non-priv'd user with proper firewall setup. Does this seem to be an OK and average setup? Or is it considered a MUST to chroot something like the imapd daemon, etc. Thanks! -Matt

2 1

[Dovecot] multiple instances of dovecot ?
by Flavien 12 Jul '05

12 Jul '05

Hello, I got a dovecot server running on a Debian Linux machine. I'd like to run another instance of it. I start it with another config file with debug output on stderr. The auth parameters are different : dovecot1: Imapd only, listens on 143, auth=/etc/passwd dovecot2: Imapd only, listens on 144, auth=mysql It kinda works... But... How does one instance of it recognizes the right "imap-login" it should talk to ? What happens in my tests, you guess it: dovecot1 talks to imap-login2, trying to authenticate users that are in /etc/password against mysql... # dovecot -F -c dovecot-config2.conf dovecot: Jul 05 22:49:03 Info: Dovecot starting up dovecot-auth: Jul 05 22:49:04 Info: MySQL: connected to localhost dovecot-auth: Jul 05 22:49:04 Info: Login process 6 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 6 sent handshake: PID 26368 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 sent handshake: PID 26369 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 sent handshake: PID 26370 dovecot-auth: Jul 05 22:49:27 Info: Login process 9 connected dovecot-auth: Jul 05 22:49:27 Info: Login process 9 sent handshake: PID 26374 dovecot-auth: Jul 05 22:50:02 Info: Login process 10 connected dovecot-auth: Jul 05 22:50:02 Info: Login process 10 sent handshake: PID 26402 dovecot-auth: Jul 05 22:50:02 Info: MySQL: Performing query: SELECT password FROM users WHERE uid='flavien' dovecot-auth: Jul 05 22:50:02 Info: mysql(flavien): Unknown user 'flavien' is not known to the sql db. It's thunderbird trying to get my regular mail using the config1 on port 143, and it has nothing to do with the instance 2 whose output I'm just looking at !!! Any hint ? A+ Flavien.

2 1

[Dovecot] Connection dropped by imap server Query: CAPABILITY
by Srinivas 12 Jul '05

12 Jul '05

Hi all, I have installed squirrelmail-1.4.4 and dovecot 0.9.11 on a debian sarge machine. The tls/ssl support is disabled from both squirrelmail and dovecot imap server. When i try to login i get the following error message: ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY If i give wrong password, it gives the message Unknown user or password incorrect. which is fine. The file /var/log/mail.err, is appended with the following message: Jul 5 18:40:20 server dovecot: chdir(/home/username) failed with uid 1240: Permission denied Jul 5 18:40:20 server dovecot: child 20807 (imap) returned error 89 when i run the command: dovecot -c /etc/dovecot.conf it gives the following error: Fatal: listen(143) failed: Address already in use Later i enabled tls in squirrelmail and dovecot.conf. i got the following error: Warning: fgets(): SSL: fatal protocol error in /usr/share/squirrelmail/functions/imap_general.php on line 88 ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY Any suggestions? Thank you Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] cannot download eMails from POP3
by Bastian 12 Jul '05

12 Jul '05

Hi dovecot users, IŽve got a problem with downloading emails: dovecot is installed and configured, I can login but I cannot download mails wich are at my harddisc. After trying to download an email thatŽs in the logfile: pop3-login: Jul 05 10:41:00 Info: Login: webmaster(a)myDomain.de [xx.xxx.xx.xxx] dovecot-auth: Jul 05 10:41:00 Info: Login process 9 disconnected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 connected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 sent handshake: PID 5754 QueryŽs are successfully, like they are required in dovecot-mysql.conf: First password clear, then home directory (/var/opt/vmail/myDomain.de/webmaster), uid and gid. My eMails are at /var/opt/vmail/myDomain.de/webmaster/Maildir/new, does dovecot automatically search for emails in Maildir/new? IŽve no idea, why I cannot download any eMails :( Can you help me? Thank you Bye, Bastian

2 1

[Dovecot] Altering newly created mailboxes
by Thomas Wouters 12 Jul '05

12 Jul '05

There seems to be a bug in updating uid/uidvalidity when copying mail to an empty or newly created mailbox: <new connection> . OK Logged in. . CREATE testfolder4 . OK Create completed. . SUBSCRIBE testfolder4 . OK Subscribe completed. . SELECT otherfolder * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 3 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121171128] UIDs valid * OK [UIDNEXT 4] Predicted next UID . OK [READ-WRITE] Select completed. . UID COPY 1 testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:45] . SELECT testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:49] <wait a while, doing nothing else> . SELECT testfolder4 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121173545] UIDs valid * OK [UIDNEXT 2] Predicted next UID . OK [READ-WRITE] Select completed. The errorlog entries for those two errors are: Jul 12 15:05:45 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:05:49 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 I also managed to trigger an assertion failure this way, by trying another COPY after that first failure: . UID COPY 1 testfolder6 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:16:54] . UID COPY 1 testfolder6 Connection closed by foreign host. The errors for that connection are: Jul 12 15:16:54 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): file mail-index-transaction.c: line 128 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) Jul 12 15:17:01 dovecot0 dovecot: child 6666 (imap) killed with signal 6 Another assertion error I triggered was by trying another SELECT right after the failed SELECT (after the failed COPY): Jul 12 15:14:04 dovecot0 dovecot: IMAP(ynnoz): Maildir /var/spool/mail/.4a/S/tmp/ynnoz/.testfolder5 sync: UIDVALIDITY changed (1121174026 -> 1121174044) Jul 12 15:14:09 dovecot0 dovecot: IMAP(ynnoz): Corrupted transaction log file /var/run/dovecot-index/ynnoz/.testfolder5/dovecot.index.log: Append with UID 1, but next_uid = 2 Jul 12 15:14:12 dovecot0 dovecot: IMAP(ynnoz): file mail-index-view.c: line 595 (mail_index_view_open): assertion failed: (index->map != NULL) Jul 12 15:14:12 dovecot0 dovecot: child 6654 (imap) killed with signal 6 I was able to reproduce this on a near-virgin test76 -- it has one patch that should not interfere; we use default_mail_env = maildir:%Nu:INDEX=/var/run/dovecot-index/%u where %N is a new var_expand character that looks up the argument in a NIS map (we store actual maildir location there, for scalability.) The INDEX setting we use might matter, though. But it feels like a missing update-uid or invalidate-uid call somewhere, I just don't know where :) -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

1 0

[Dovecot] Re: separate SSL certificates for pop3s and imaps
by sean finney 11 Jul '05

11 Jul '05

On Thu, Jul 07, 2005 at 08:58:35PM +0300, dovecot-request(a)dovecot.org wrote: > Hi, > > I'm migrating a uw-imap installation to dovecot. With uw-imap I had > different SSL certificates and keys for ipop3d and imapd. How can I > configure dovecot to do the same with its pop3s and imaps services? i run dovecot in a multihomed server with three different names: mail.foo.edu smtp.foo.edu imap.foo.edu which, for ssl purposes, means we need three different certs to keep applications happy. my approach is to start a seperate dovecot process for each address, and manage the configuration in three seperate files, each one telling dovecot to specifically bind to only one address, and use a seperate runtime directory specific to that address. so for example, in my initscript, instead of just doing something like: start() { echo -n $"Starting $prog: " daemon $prog -c /etc/dovecot.conf RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } i do something like: start() { echo -n $"Starting $prog: " for s in imap mail smtp; do mkdir -p /var/run/dovecot/${s}.foo.edu daemon $prog -c /etc/dovecot/${s}.foo.edu.conf done RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } where the value of the ssl cert config is different in each of the files. you could extend this to also have one config file to only listen for pop and the other only for imap. hth, sean

4 5

[Dovecot] Creating encrypted passwords for new users /etc/imap.passwd
by John_R._McWade 09 Jul '05

09 Jul '05

Hello. I've been attempting to locate information on how to actually create the encrypted passwords for a new user in /etc/imap.passwd file. Im really going into this blindly, not having ever used dovecot before, and really just need to be pointed to any existing resources on this topic. This is a setup of dovecot (w/ sendmail,squirrelmail) on FC2. I've got one successful auth so far as a test user, with their info cut/pasted directly from /etc/passwd (it works) whereas using {PLAIN}password causes dovecot to drop the connection with an aborted login. So what I'm actually looking for is a resource or a quick response regarding the actual creation of the encrypted password in /etc/passwd style. Any clues on where I should look for this info? John

2 1

[Dovecot] io leak when dnotify is enabled but not available
by Johannes Berg 08 Jul '05

08 Jul '05

Hi, When dnotify is enabled, but not in the kernel, there's an io leak: $ /sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes a select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 787 EXISTS * 0 RECENT * OK [UIDVALIDITY 1106061449] UIDs valid * OK [UIDNEXT 790] Predicted next UID a OK [READ-WRITE] Select completed. b IDLE imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument + idling DONE b OK Idle completed. q logout * BYE Logging out q OK Logout completed. imap(johannes): Warning: I/O leak: 0x10068ff0 (8) Attached patch fixes it, I hope the patch is correct :) johannes

1 0

[Dovecot] stat() failed with mbox /var/mail/%u
by Jungshik Shin 08 Jul '05

08 Jul '05

Hello, Over the last 12 hours or so, I've been wrestling with a mysterious dovecot issue. After upgrading a mail server I'm helping my friend with maintaining from Fedora Core1 to Fedora Core4, I realized that I couldn't use UW-IMAP4 anymore (well, I can compile it myself, but it turned out that UW-IMAP was the main cause of the server's having load average as high as 30 from time to time so that I decided to move onto dovecot). Although I loved to migrate to maildir, I didn't dare to tackle the migration (I have a lot more important things to do :-)) to maildir. Instead, I thought that dovecot's indexing of mbox files should make the performance of the server a lot better than UW-IMAP. (in addition, we upgraded the HW from P3 800MHz single to P4 dual 3GHz). Last night, I experimented with several mboxes of one user's account (INBOX in /var/mail/<userid> and others in ~/mail/) and it worked perfectly well. So, I moved mboxes of other users and launched 'dovecot' informing users that the mail server is back up again. However, it didn't work with inbox (for IMAP) and POP3. There's no problem accessing mail folders in '~/mail', but accessing /var/mail/%u (inbox for IMAP) and using the same folder with POP3 didn't work. The error I got in the log file is: Jul 8 01:17:24 biosoft dovecot: pop3-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 01:17:24 biosoft dovecot: POP3(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: auth(default): Error sending status request (Operation not permitted) Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: IMAP(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied ls -ld / /var /var/mail/ /var/mail/xyz123 drwxr-xr-x 23 root root 4096 Jul 7 19:28 / drwxr-xr-x 26 root root 4096 Jul 7 23:35 /var drwxrwxrwt 2 root mail 4096 Jul 8 00:36 /var/mail/ -rw-rw---- 1 xyz123 mail 130751237 Jul 7 23:37 /var/mail/xyz123 I tried various combinations of permissions and ownerships for /var/mail (1777, 2775) and /var/mail/<userid>, but nothing made any difference. I also tweaked mbox locking methods ('dotlock fcntl' or 'fcntl' alone) When I came across this problem with the latest stable (2005-07-06), I went back to FC4's default package (0.99??), but with a slightly different error message in the log file, basically I had the same problem. I kept the default values for most configuration parameters. What I changed are listed below: mail_extra_groups = mail pop3_uidl_format = %08Xv%08Xu protocols = imap imaps pop3s default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u Also attached is the entire /etc/dovecot.conf I'm really desperate to get some enlightening answers on this problem, for which I'll really appreciate you. Thanks tons in advance, Jungshik ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/usr/share/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port", although with multiple protocols you probably want to move this # setting inside protocol imap/pop3 { ... } section, so you can specify # different ports for IMAP/POP3. listen = [::] # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /usr/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. login_dir = /var/run/dovecot-login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # 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 = mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # 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's 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 = default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # 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 #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # 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 # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl mbox_read_locks = fcntl mbox_write_locks = fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. pop3_uidl_format = %08Xv%08Xu # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # You can have multiple authentication processes. With plaintext authentication # the password is checked against each process, the first one which succeeds is # used. This is useful if you want to allow both system users (/etc/passwd) # and virtual users to login without duplicating the system users into virtual # database. # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. 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. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # checkpassword <path>: checkpassword executable authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf passdb = pam # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf userdb = passwd # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # PAM doesn't provide a way to get uid, gid or home directory. If you don't # want to use a separate user database (passwd usually), you can use static # userdb. #auth onlypam { # mechanisms = plain # userdb = static uid=500 gid=500 home=/var/mail/%u # passdb = pam # user = dovecot-auth #} #auth ldap { # mechanisms = plain # userdb = ldap /etc/dovecot-ldap.conf # passdb = ldap /etc/dovecot-ldap.conf # user = dovecot-auth #} #auth virtualfile { # mechanisms = plain digest-md5 # userdb = passwd-file /etc/passwd.imap # passdb = passwd-file /etc/passwd.imap # user = dovecot-auth #} # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb = passwd # userdb = pam # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 2

[Dovecot] "Leave a copy on server" not marking messages as read...
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, Our customers who have "Leave a copy on server" with POP3 continue to check their email, and each time they check it it re-downloads all emails (so it doesn't seem to be updating those messages already downloaded). Any ideas? Thanks! -Matt

1 0

[Dovecot] IMAP Folders
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, We're using the mbox format and I tried setting up IMAP on my boss's computer tonight. He likes subfolders, and although they work, he can't seem to remove subfolders once he created them, nor create new folders without using something other than his mail client (like mkdir from the command line). Any ideas on this? Does dovecot just not officially support IMAP and subfolders with the mbox format? Or could it be a permissions issue? -Matt

2 1

[Dovecot] RE: dovecot not able to access sentmail folder in home directory(chdir)
by vineet 07 Jul '05

07 Jul '05

problem is solved the problem was with the access permissions to the folder having the users' folders make sure that dovecot has the permission to access the folders containg the users' folders vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] test76 segfaults?
by Johannes Berg 06 Jul '05

06 Jul '05

Hi, I was just trying to port my dspam plugin to the latest test release but ran into trouble so I decided to test the code itself first. I have the following maildir: johannes:~/.mail$ find . ./cur ./new ./new/test ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/tmp Now I run $ exec /usr/sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes A SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1120680468] UIDs valid * OK [UIDNEXT 2] Predicted next UID A OK [READ-WRITE] Select completed. B COPY 1 SPAM imap(johannes): Error: Corrupted index file /home/johannes/.mail/.SPAM/dovecot.index: uid_validity = 0, next_uid = 2 Segmentation fault However, it actually did copy something: johannes:~/.mail$ find . ./cur ./cur/test:2, ./new ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/new/1120680473.P1535Q0M900310.johannes ./.SPAM/tmp ./.SPAM/dovecot.index ./.SPAM/dovecot-uidlist ./.SPAM/dovecot-uidlist.lock ./.SPAM/dovecot.index.log.2 ./.SPAM/dovecot.index.log ./dovecot.index.log ./dovecot.index ./dovecot.index.cache ./dovecot-uidlist The mail in that, for reference, is just this: --- A: xxx Subject: hallo! From: johannes X-DSPAM-Signature: asdf wow! --- johannes

1 1

[Dovecot] I need sleep (dovecot auth / postfix 2.3)
by /dev/rob0 06 Jul '05

06 Jul '05

I need the new sleep feature (smtpd_*_restrictions) of Postfix 2.3 snapshots, but I'm using the Dovecot auth patch. The 2.2.1 patch had problems in the snapshots I tried. Fortunately the problems were very simple. rob0@room101:~/src/mail/postfix-2.3-20050630$ patch -p1 < ~/dl/postfix-2.2.1-dovecot-auth.patch [snip] patching file src/smtpd/Makefile.in Hunk #1 FAILED at 1. Hunk #2 FAILED at 296. 2 out of 2 hunks FAILED -- saving rejects to file src/smtpd/Makefile.in.rej patching file src/smtpd/smtpd.c Hunk #1 FAILED at 854. Hunk #2 succeeded at 1006 (offset 16 lines). Hunk #3 succeeded at 1173 (offset 1 line). Hunk #4 succeeded at 1306 (offset 20 lines). Hunk #5 succeeded at 1562 (offset 33 lines). Hunk #6 succeeded at 1692 (offset 54 lines). Hunk #7 succeeded at 1834 (offset 72 lines). Hunk #8 succeeded at 2918 (offset 135 lines). Hunk #9 succeeded at 2952 (offset 73 lines). Hunk #10 succeeded at 3262 (offset 152 lines). Hunk #11 succeeded at 3301 (offset 73 lines). Hunk #12 succeeded at 3551 (offset 154 lines). 1 out of 12 hunks FAILED -- saving rejects to file src/smtpd/smtpd.c.rej [snip] I fixed the failures manually. Attached is a patch which only changes those two files ... it's a supplement to the existing patch as provided by Timo: http://dovecot.org/patches/postfix/postfix-2.2.1-dovecot-auth.patch I have not yet tested either sleep or AUTH, because I *do* need sleep for real. :) But it did compile with no errors nor [noted] warnings. I do have this running. -- mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

1 1

[Dovecot] Username mapping
by nodata 06 Jul '05

06 Jul '05

Hello. We're using dovecot with mysql for authentication, with postfixadmin for the admin web interface. We are moving users from passwd file usernames to email@domain style logins. Is there a better way to allow both sets of usernames (old and new) to work with dovecot than by adding extra copies of rows to the mailboxes table and changing the username? i.e. does dovecot support some kind of username mapping or aliasing? Thanks a lot

3 2

[Dovecot] dovecot not able to access sentmail folder in home directory(chdir)
by vineet 06 Jul '05

06 Jul '05

using dovecot version 0.99.11 while accessing through squirrelmail or even connecting manually(using openssl) to the server dovecot is not able to access the folder the mail.err log file has the following entry: dovecot: (/home/user) permission denied error no 89 returned by child process the squirrel mail error was connection dropped by imap server Query capability thanks vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] dovecot 1 for production? which one?
by Jeff A. Earickson 06 Jul '05

06 Jul '05

Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing, advice please. My setup: Solaris 9, mbox format. Jeff Earickson Colby College

2 1

[Dovecot] Root password or key access to pop3?
by Matt Juszczak 05 Jul '05

05 Jul '05

Hi all, We're an ISP, and are currently looking for a way for our tech support guys to access customer's email without having shell access to the server, or knowing the customer's password. We'd like to install a custom webmail client that would only show the user's inbox and the ability to delete the messages. The problem is, that we would have to know the user's password in order for my PHP pop3 code to go out and fetch the mail. Is there a way I can setup and/or patch dovecot so that any connection from <said IP address> can use the password "jq3erjq3535" for any account, and it will authenticate them? Or is this some kind of custom patch I would need to write? Thanks! -Matt

3 5

[Dovecot] error connecting dovecot from squirrelmail
by Srinivas 04 Jul '05

04 Jul '05

the problem is: 1. the error in the mailerr file is: Jul 4 19:42:26 obelix dovecot: chdir(/home/user) failed with uid 1229: Permission denied Jul 4 19:42:26 obelix dovecot: child 16385 (imap) returned error 89 2. the error msg given by Squirrelmail is: ERROR: connection dropped by imapserver QUERY: CAPABILITY the dovecot and squirrelmail settings are same on both the servers 3. the mailbox settings in dovecot.conf: default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u OS: Debian Sarge stable thanks srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] BOGUS files
by Obantec Support 04 Jul '05

04 Jul '05

Hi what does this mean BOGUS.watasiuk.8B8I (watasiuk is a username). FC3 Mark -- Obantec Support www.obantec.net 0845 458 3121 WebHosting and Domains Nominet UK Member & IPStag Holder CentralNic Accredited Reseller

4 6

[Dovecot] dovecot - outlook users keep getting locked out of imap
by Anthony Kolasny 04 Jul '05

04 Jul '05

Greetings: My outlook users accessing mail via dovecot's imaps have been consistantly getting locked out of their email. It happens about once a week per outlook user. It appears to happen when the are cliking on emails with attachments. When this happens, there are two imap deamons running for that user. I kill both deamons and things start working again. Squirrelmail, thunderbird and pine users haven't had this issue. I'm running a version of dovecot dated dovecot-stable-20050610. All user accounts have their mail on nfs mount points. The INBOX directory is local to the imap server but we have a smtp server that gets this data via nfs. Below is the dovecot.conf info: base_dir = /var/run/dovecot/ protocols = imap imaps ssl_disable = no ssl_cert_file = /usr/local/imaps/certs/dovecot_cert.pem ssl_key_file = /usr/local/imaps/certs/dovecot_key.pem disable_plaintext_auth = yes login_dir = /var/run/dovecot/login login_process_size = 128 login_processes_count = 9 login_max_processes_count = 256 login_max_logging_users = 512 verbose_proctitle = yes mail_extra_groups = mail default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u mmap_disable = no lock_method = fcntl mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl mbox_lock_timeout = 300 mbox_dotlock_change_timeout = 30 mbox_dirty_syncs = yes mbox_very_dirty_syncs = no protocol imap { imap_client_workarounds = outlook-idle } protocol pop3 { } auth default { mechanisms = plain passdb = pam userdb = passwd user = root } Your assistance is greatly appreciated. Thanks, Anthony

2 1

[Dovecot] dovecot restart bug?
by Andrew Hutchings 04 Jul '05

04 Jul '05

Using my initd script (no idea of the origin now) to do a restart I randomly get: Jun 28 13:56:05 svr24 dovecot: Killed with signal 15 Jun 28 13:56:05 svr24 dovecot: Dovecot v1.0-test74 starting up Jun 28 13:56:06 svr24 dovecot: Auth process died too early - shutting down Jun 28 13:56:06 svr24 dovecot: auth(default): net_connect_unix(/var/run/dovecot/auth-worker.23322) failed: No such file or directory Jun 28 13:56:06 svr24 dovecot: child 23322 (auth) returned error 89 It then suddenly starts working again, is this something to do with that new mysql timeout feature? This started happening when I migrated from test72 to test73. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 111: "It's possible, you can never know, that the universe exists only for me." - BILL GATES

2 1

[Dovecot] dovecot problem or not ?
by Mircea Hutanu 04 Jul '05

04 Jul '05

Hi, I've setup a postfix mailserver with dovecot and postgres database for virtual domains with virtual users, but I have some problems getting the accounts to work. I've used instruction from this tutorial : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql I want users to be able to get their email with imap or pop3, but I didn't manage to solve this problem. The server makes mbox style user accounts, I can send email to them but when I try to read emails from virtual accounts I get the following error : Jun 28 14:42:52 voodoo dovecot-auth: Login process 10 connected Jun 28 14:42:52 voodoo dovecot-auth: Login process 10 sent handshake: PID 10491 Jun 28 14:42:58 voodoo dovecot-auth: PGSQL: Performing query: SELECT password FROM users WHERE userid = 'user(a)foo.org' Jun 28 14:42:58 voodoo dovecot-auth: PGSQL: Performing query: SELECT '/home/'||home AS home, uid, gid FROM users WHERE userid = 'user(a)foo.org' Jun 28 14:42:58 voodoo pop3(user(a)foo.org): mbox: Can't create root IMAP folder /home/foo.org/mails/user/mail: Permission denied Jun 28 14:42:58 voodoo pop3(user(a)foo.org): Failed to create storage with data: mbox:/home/virtual/foo.org/mails/user Jun 28 14:42:58 voodoo pop3-login: Login: user(a)foo.org [127.0.0.1] Jun 28 14:42:58 voodoo dovecot-auth: Login process 8 disconnected Jun 28 14:42:58 voodoo dovecot: child 10492 (pop3) returned error 89 The error " mbox: Can't create root IMAP folder /home/foo.org/mails/user/mail: Permission denied" appears because, using mbox, the home for virtual accounts is /home/virtual/foo.org/mails/user, where user is allready the mbox file, to the sistem can't create the directory structure for IMAP settings. What I'm doing wrong ? Did someone else got this problem ? Thanks ! -- ------------------------------ Mircea Hutanu voodookid(a)gmail.com ------------------------------

2 1

[Dovecot] Automating message archiving
by Steffen Kaiser 04 Jul '05

04 Jul '05

Hallo, I recently stumple over some discussion about Sieve and what's the advantage to integrate it into the server rather than the LDA. Most of the filtering capabilites local users want to have performed are related to the INBOX or more preciesly the way to filter the message coming in. However, there are few tasks left: 1) Auto-archive old mail. 2) Drop old mail. 3) "Seen" mails are moved from INBOX to somewhere else. To 1) Several people love to store each single mail, but because the system becomes very slow when they open a mailbox with, day, 5000 messages (Mozilla even core dumps sometimes); they archive the mails by year or month, if they got elder than, say, 6 month. I do not want to discuss this habbit, it's like it is and I have the trouble with it. To 2) There is the doing of dropping all messages flagged as SPAM into a specific folder. It would be nice if the does messages are deleted, when they grew get elder. To 3) I don't grasp the idea, but it seems that notebook users want to look, what messages are new, flag and download selected ones; when they connect next time the "old, already seen" ones should be invisible, but still accessable on demand in another folder. Maybe it has to do with that the client sometimes reads the whole IMAP INBOX again, instead just the new ones. I've seen this behaviour with Mozilla myself in conjunction with a variaty of IMAP servers now and then. Those things must be user-configurable, of course ;-), I hoped Sieve would solve this problems, but it doesn't. The MVMF mentioned in the mailing list, doesn't as well. Does somebody has some solution for these tasks, besides to setup a cronjob and hack a webinterface? Is there some Dovecot tool that one can use to manipulate the mail storage? UW-IMAP ships such thing (mailutil), but it does not support Maildir and it would be nice, when the Dovecot extensions are created well. Bye, -- Steffen Kaiser

3 2

[Dovecot] Authenticate login failed: Unsupported authentication mechanism
by Orchun Kolcu 04 Jul '05

04 Jul '05

Hi, I just switched (or tried to) from UW-IMAP to dovecot. When I try to login through the telnet client I get: 1 NO Authentication failed and in the log I get: imap-login: Authenticate PLAIN failed: Unsupported authentication mechanism If I try to login through the IMAP client (Thunderbird), in the log I get the slightly different: imap-login: Authenticate login failed: Unsupported authentication mechanism Here's the auth setup from the conf: auth default { mechanisms = plain passdb = pam imap userdb = passwd user = root } And here's /etc/pam.d/imap for good measure: auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth The server is a fairly standard Redhat 8 setup. Any idea what's going on? Thanks! -- Orchun Kolcu orchunk(a)fastem.com -- http://www.fastmail.fm - The professional email service

3 3

Re: [Dovecot] error while connecting from squirrelmail
by Srinivas 02 Jul '05

02 Jul '05

dovecot and squirrelmail configuration successfull!! The problem was: There were many other options related to ssl,which were enabled, like ssl_cert_file,ssl_parameters_file and so on. i disabled them all, and it's working fine now. Now, only, ssl_disable = no is uncommented. Thank you all. Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] newbie - trying to set up pop3 access for multiple domains
by Andy Green - Green Consulting 01 Jul '05

01 Jul '05

I'm hosting multiple domains, and I'm having problems getting dovecot to play nicely. The only protocol I've got enabled in the conf file is pop3, yet the maillog shows the following entries when I try to authenticate: mbox: Can't create root IMAP folder /mail: Permission denied Failed to create storage with data: mbox:/var/mail/vhosts/<domain name here>/<user name here> returned error 89 Any ideas/suggestions would be greatly appreciated.

1 0

Re: [Dovecot] error while connecting from squirrelmail
by Srinivas 01 Jul '05

01 Jul '05

>Only two things I can think of: >1. Dovecot was not configured for imap with ssl (check that >ssl_disable is not set to yes). Also check the protocols statement >that it supports imaps. > >2. Check that you do not have access lists blocking off 993 to your >squirrelmail. This is often encountered if using tcp wrappers and >you're running dovecot through (x)inetd. > >Regards, Neil The ssl_disable is set to no and the protocols statement contains all the four protocols: imap pop3 imaps pop3s. But i couldn't make out the 2nd point, you suggested.Can you, please, describe it a little more ? Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

3 2

[Dovecot] error while connecting from squirrelmail
by Srinivas 01 Jul '05

01 Jul '05

Hi all, I am new to dovecot and squirrelmail and I am trying to configure squirrelmail with dovecot as its imap server. When i disable "Secure Imap (TLS)" option (2-A-7) from squirrelmail configure menu, it's working fine. But when i try to enable tls support, squirrelmail is giving the following error: Warning: fsockopen(): unable to connect to 192.xx.xx.xx:993 in /usr/share/squirrelmail/functions/imap_general.php on line 445 ERROR Error connecting to IMAP server: tls://192.xx.xx.xx. 111 : Connection refused Go to the login page The port numbers of the imap server are as follows: imap_listen 143 pop3_listen 110 imaps_listen 993 pop3s_listen 995 Squirrelmail and the dovecot imap server are running on different machines, so it is essential to enable tls support. All the machines are running Debian Sarge. Can anyone suggest a solution for the above problem ? Thank you. Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] root login is refused, but....
by Roberto Tagliaferri 01 Jul '05

01 Jul '05

If i try to connect as root (dovecto 1.0) with wrong password doveco exit with an auth error robyt:~# telnet dns pop3 Trying x.x.x.x Connected to dns. Escape character is '^]'. +OK Dovecot ready. user root +OK pass [wrong] -ERR Authentication failed. but if the password is correct dovecot exit but with another error: user root +OK pass [correct] -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. robyt:~# Why dovecot don't close the connection at user root? With this system i may know the root password.. -- Roberto Tagliaferri Responsabile Progettazione & Produzione TosNet s.r.l. - Internet Service Provider r.tagliaferri(a)tosnet.it www.tosnet.it

3 3

[Dovecot] Dovecot doesn't use vchkpw properly :(
by Casey Allen Shobe 01 Jul '05

01 Jul '05

Hey all, It seems that dovecot does NOT call vchkpw properly when using vpopmail-style authentication, I can only guess that it reads the vpasswd{,.cdb} files directly. This is indicated by the syslog log for the mail facitily which reads: Jun 30 16:51:30 [vpopmail] vchkpw-smtp: (PLAIN) login success blah@blah.com:24.17.153.137 Jun 30 17:16:25 [pop3-login] Login: blah(a)blah.com [24.17.153.137] Jun 30 17:47:42 [imap-login] Login: blah(a)blah.com [216.57.201.58] pop3-login and imap-login are dovecot processes - vchkpw is never called or there would also be log entries for it. I've verified this with the vpopmail list, who agree that the problem lies within dovecot. This might not be quite so annoying, but we are using vpopmail compiled with the --enable-learn-passwords option, which will populate the password files with cleartext versions of the passwords where they are missing. Because of dovecot not calling vchkpw, this doesn't work for POP3/IMAP logins, only SMTP (using qmail-smtpd). People don't send mail from every account they poll, and we need to get all of the passwords in cleartext form so that we can complete migration to a PostgreSQL password database which multiple applications will use to authenticate. Are there plans to make dovecot use vchkpw in the normal checkpassword manner? If not, I'd like to request it. We will probably switch back to qmail-pop3d and bincimap for the time being to finish collecting passwords if we can't get a quick fix...I think we can do that without much impact. Cheers, -- Casey Allen Shobe | http://casey.shobe.info cshobe(a)seattleserver.com | cell 425-443-4653 AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523 SeattleServer.com, Inc. | http://www.seattleserver.com

2 3

RE: [Dovecot] LF not found where expected
by Miles Mawyer 01 Jul '05

01 Jul '05

Thanks for the reply. I think I'd found the issue. It seems to be the empty line that is ending up at the top of mail file. I removed that blank line out of one of the mail box files, and it started working without an issue. I'm not sure what is causing the empty line in the mbox file however. Most of my clients use pop3 to download their messages through dovecot. Could this be happening if the client only downloads part of their messages? Pretty easy for me to straighten out, but I didn't know if this was a bug that needed to be addressed. ... Miles Mawyer -=- Webmaster . Centralva.net ... ... mmawyer(a)rosecomputers.com ... ... 434.385.5053 ... -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: Tuesday, June 28, 2005 7:52 AM To: Miles Mawyer Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] LF not found where expected On 27.6.2005, at 18:45, Miles Mawyer wrote: > pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file > /var/mail/mjmurray: LF not found where expected These usually happen because the mbox file has two adjacent From-line, ie: From foo ... From bar ... Message-headers: ... That shouldn't happen normally though. Sounds like something is wrong with how your mails are written. Are all the software that are writing to the mbox using same lock methods? Anyway, 1.0-test/stable versions of Dovecot can handle the adjacent From-lines too without failing.

2 1

[Dovecot] How to lock a user out?
by Kai Wang 29 Jun '05

29 Jun '05

Hi, We are considering to migrate to Dovecot. We can running uw-imap and have a local path which allow us to lock a user by creating a .lockdir directory in the user home directory and put our warning message to .lockdir/mbox. The locked user can still receive messages in ~/mbox. But can not access any messages except ~/.lockdir/mbox. I wonder if Dovecot has any similar feature which we can use to lock a user out without affecting the mail delivery? Kai Wang University of Calgary

2 4

[Dovecot] 1.0-test74
by Timo Sirainen 29 Jun '05

29 Jun '05

http://dovecot.org/test/ Not much has happened, but the APPEND bugfix is important since it was broken in test73 (at least). Summer makes me tired and lazy. :( I've been trying to get keywords implemented in maildir. Hopefully works soon.. After that I'll create 1.0-stable2 (ugh. any other naming ideas?) branch of the code before merging the new master/config code. - Fixed APPEND .. I hope? At least works much better than before - pop3_uidl_format = %m now doesn't return broken 0 MD5 sums when the MD5 sum wasn't written in indexes for some reason (eg. appended/copied to INBOX with IMAP and trying to access mail with POP3). - Authentication cache wasn't working when Dovecot was used for proxying - Index cache file wasn't keeping track of how much of the file was deleted, so it may not have ever shrinked - Maildir+NFS: Fixed skipping mails when moving files from new/ to cur/ - Maildir: We didn't notice if messages were directly deleted from new/

3 2

[Dovecot] imap corrupted indexes
by Emmett Pate 28 Jun '05

28 Jun '05

I've searched the archives and find a lot of references to corrupted indexes but can't seem to find any solutions. It seems like folks either have the problem or they don't. We recently migrated from a RedHat Linux server to an OpenBSD 3.7 server (both using dovecot). Imap was working flawlessly on the RedHat box but now gives numerous index errors. I then upgraded to dovecot-1.0-test66 compiled from ports - still no luck. Here's an example of the errors: Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs are broken Jun 27 12:02:24 mail dovecot: IMAP(epate): Lost transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log seq 7 I found references to "disabling indexing" but they don't say how. Would this be a reasonable temporary solution? Any other suggestions? Thanks for your help, Emmett Pate

3 3

[Dovecot] Sudden IMAP problem - UID Errors
by Jamie Heckford 28 Jun '05

28 Jun '05

Hi, We have quite happily been running dovecot with no issues at all for approx. two years now and have had no problem whatsoever. Great work :) BUT (there is always a but!).... yesterday one of our users started complaining that they were having issues with their mail. I checked and although they can still view their IMAP mailbox ok it constantly throws up error messages such as: "The UID of a message changed unexpectedly. This typically indicates a server bug. Your program may not function properly after this. MsgSeqNum 131: Previous UID: 21402, New UID: 21555 Protocol: IMAP" and "Your server has reported a UID which does not comply with the IMAP standard. This typically indicates a server bug. Your program may not function properly after this." This is using Outlook 2003 as the IMAP client, and is only affecting a single user. Server is dovecot-0.99.14 running on FreeBSD 4.9-RELEASE #1: Thu Apr 15 10:00:08 GMT 2004 Anybody seen this before or have any suggestions? Also is there a way I can make the logging more verbose as I only get info on date/user/ip when they login. I did see a --raw-log or similar compile flag, is this whats needed? I suspect this is Outlook being stupid and not dovecot though. Any help would be greatly received. Many thanks! -- Jamie Heckford Network Manager Trident Microsystems Ltd. t: +44(0)1737-780790 f: +44(0)1737-771908 w: http://www.trident-uk.co.uk/

2 2

[Dovecot] UID confusion
by Andrew Hutchings 28 Jun '05

28 Jun '05

Hi, 2 or 3 customers have reported that they are having problems downloading their mail via. POP3. I have attached the rawlogs of their transactions and the UID list at the time. Is this because I am using an incompatible UID format or is something else at fault? Deleting the UID list and indexes fixes the problem. I am using Test72. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 148: "We had planned to integrate a Web browser with our operating system as far back as 1993" - Microsoft (27 Jul 1998, filing its first court responses to federal antitrust) STAT UIDL DELE 12 DELE 13 DELE 14 DELE 15 DELE 16 DELE 17 DELE 18 DELE 19 DELE 20 DELE 21 DELE 22 DELE 23 DELE 24 DELE 25 DELE 26 DELE 27 DELE 28 DELE 29 DELE 30 DELE 31 DELE 32 DELE 33 DELE 34 DELE 12 DELE 31 DELE 20 DELE 14 DELE 32 DELE 19 DELE 21 DELE 33 DELE 23 DELE 28 DELE 22 DELE 34 DELE 27 DELE 30 DELE 24 DELE 18 DELE 17 DELE 29 DELE 26 DELE 25 DELE 15 +OK 37 3133628 +OK 1 1102086912.6586 2 1102086912.6604 3 1102086912.6606 4 1102086912.6607 5 1102086912.6613 6 1102086912.6614 7 1102086912.6624 8 1102086912.6627 9 1102086912.6628 10 1102086912.6637 11 1102086912.6638 12 1102086912.6642 13 1102086912.6643 14 1102086912.6644 15 1102086912.6645 16 1102086912.6646 17 1102086912.6647 18 1102086912.6649 19 1102086912.6650 20 1102086912.6651 21 1102086912.6652 22 1102086912.6653 23 1102086912.6655 24 1102086912.6656 25 1102086912.6657 26 1102086912.6658 27 1102086912.6659 28 1102086912.6660 29 1102086912.6661 30 1102086912.6662 31 1102086912.6663 32 1102086912.6664 33 1102086912.6665 34 1102086912.6666 35 1102086912.6668 36 1102086912.6669 37 1102086912.6670 . +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Too many bad commands. 1 1102086912 6671 6586 1119365297.H428351P22768.svr34.nsnoc.com:2,S 6604 1119430792.H16069P15059.svr34.nsnoc.com:2,S 6606 1119435803.H269574P27211.svr34.nsnoc.com:2,S 6607 1119438782.H651475P11876.svr34.nsnoc.com:2,S 6613 1119444180.H435092P3752.svr34.nsnoc.com:2,S 6614 1119446623.H168979P14147.svr34.nsnoc.com:2,S 6624 1119519980.H840253P23730.svr34.nsnoc.com:2,S 6627 1119534126.H915877P9542.svr34.nsnoc.com:2,S 6628 1119534129.H58338P9545.svr34.nsnoc.com:2,S 6637 1119590807.H77202P16581.svr34.nsnoc.com:2,S 6638 1119594010.H314838P14558.svr34.nsnoc.com:2,S 6642 1119631309.H826676P15985.svr34.nsnoc.com:2,S 6643 1119634096.H108358P8422.svr34.nsnoc.com:2,S 6644 1119651249.H740483P15403.svr34.nsnoc.com:2,S 6645 1119652382.H85165P25444.svr34.nsnoc.com:2,S 6646 1119662861.H891233P15682.svr34.nsnoc.com:2,S 6647 1119666011.H343203P9515.svr34.nsnoc.com:2,S 6648 1119678421.H726408P9343.svr34.nsnoc.com:2,S 6649 1119682873.H656272P7774.svr34.nsnoc.com:2,S 6650 1119709610.H933163P23969.svr34.nsnoc.com:2,S 6651 1119711088.H95605P27225.svr34.nsnoc.com:2,S 6652 1119717756.H183955P3515.svr34.nsnoc.com:2,S 6653 1119726592.H247339P1807.svr34.nsnoc.com:2,S 6654 1119727779.H102401P8785.svr34.nsnoc.com:2,S 6655 1119749596.H731030P9216.svr34.nsnoc.com:2,S 6656 1119760115.H508676P14834.svr34.nsnoc.com:2,S 6657 1119761702.H762025P27895.svr34.nsnoc.com:2,S 6658 1119774991.H8003P28710.svr34.nsnoc.com:2,S 6659 1119780623.H432714P11671.svr34.nsnoc.com:2,S 6660 1119797027.H333204P330.svr34.nsnoc.com:2,S 6661 1119799332.H700308P15617.svr34.nsnoc.com:2,S 6662 1119800637.H600428P30602.svr34.nsnoc.com:2,S 6663 1119807991.H64209P14572.svr34.nsnoc.com:2,S 6664 1119808834.H473596P22065.svr34.nsnoc.com:2,S 6665 1119838893.H830072P23165.svr34.nsnoc.com:2,S 6666 1119838934.H873217P23186.svr34.nsnoc.com:2,S 6667 1119860409.H899984P26859.svr34.nsnoc.com:2, 6668 1119860596.H249033P27907.svr34.nsnoc.com 6669 1119867953.H904781P22645.svr34.nsnoc.com 6670 1119867978.H374439P22691.svr34.nsnoc.com

2 4

[Dovecot] getpeername() and SSL
by Andreas Goertz 28 Jun '05

28 Jun '05

Hi Timo, first of all: i'm using 0.99.14. You helped me to raw-log the client-IP using something like this in rawlog.c: if (net_getpeername(0, &ip, NULL) == 0) { str = t_strdup_printf("IP: %s\n", net_ip2addr(&ip)); write_full(log_out, str, strlen(str)); } Now i got the problem, that this doesn't work when the client is connected using SSL. After some testing i think, the problem is, that after calling net_getpeername() the ip-family is AF_UNIX, not AF_INET, so net_ip2addr() returns null, but i'm not sure ;-) And i have no clue, how to solve this and find out the ip... Do you have another hint for me? Thanks in advance. Regards, Andreas.

2 2

[Dovecot] Blank messages and problems starting Dovecot
by Lars Karset Grimsrud 28 Jun '05

28 Jun '05

When I use Evolution for viewing my e-mail and display full headers, no content is shown. The number of messages indicated in Evolution is however correct. Logging into webmail (Squirrelmail) doesn't work either, saying "Error connecting to IMAP server: localhost. 13 : Permission denied". I have verified that ~/Maildir/new actually contains valid e-mails. Does anyone have suggestions on how to debug this problem? A connection is established if I telnet. I use Fedora Core 4. Another problem I have, is changing log_path and info_log_path to something useful. If I change either to i.e. /tmp/dovecot.log, dovecot refuses to start (service dovcot restart) with noe error message. If it helps, my /etc/dovecot.conf is here: http://www.stud.ntnu.no/~grimsrud/info/dovecot.conf.txt -- Lars Karset Grimsrud <grimsrud(a)stud.ntnu.no>

2 1

[Dovecot] password scheme
by Nathalie Boulos 28 Jun '05

28 Jun '05

Hi, I have dovecot-0.99.11-1.FC3.4 running on fedora core 3, and authenticating with openLDAP on a remote server. When i try to authenticate, i get the error "Unknown password scheme SSHA". I read that earlier on this mailing list, SSHA was not suported by dovecot. Is it supported now? what should i do to make my password authentication work? The users in the openLDAP database have userPassword {SHA} already used by other services, so i cannot change them. Any suggestions? Regards, Nathalie ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com

2 1

[Dovecot] LF not found where expected
by Miles Mawyer 28 Jun '05

28 Jun '05

I'm using Dovecot 0.99.13 on a fedora core 3 server. I keep getting these errors from time to time. There user ends up retrieving no mail (but no error in their client, be it web mail or pop3 client) What usually fixes it is this procedure: Cp mbox file to mbox_ Remove original mbox Send a test message to recreate mbox. Cat mbox_ >> mbox Problem solved! Can anybody tell me what causes this? pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:16:38 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-06-27 11:16:38] pop3-login: Jun 27 11:17:06 Info: Login: mjmurray [64.203.167.125] pop3(mjmurray): Jun 27 11:17:06 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:17:06 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected pop3(mjmurray): Jun 27 11:17:06 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-06-27 11:17:06] imap-login: Jun 27 11:17:28 Info: Login: mjmurray [127.0.0.1] imap(mjmurray): Jun 27 11:17:28 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected imap(mjmurray): Jun 27 11:17:28 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected imap-login: Jun 27 11:19:12 Info: Login: mjmurray [127.0.0.1] imap(mjmurray): Jun 27 11:19:12 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected imap(mjmurray): Jun 27 11:19:12 Error: Error indexing mbox file /var/mail/mjmurray: LF not found where expected ... Miles Mawyer -=- Webmaster . Centralva.net ... ... mmawyer(a)rosecomputers.com ... ... 434.385.5053 ...

2 1

[Dovecot] possible bug with incoming mail
by Luke Ehresman 28 Jun '05

28 Jun '05

I've been using Dovecot for a couple months now and am very impressed. Thanks for a great package. However, I have noticed a problem that I haven't been able to solve. When a new message comes into my inbox, the last message that was received is marked as new as well as the new one. I originally thought this was a bug in my client (mutt) but I have verified that the same thing happens with Thunderbird, Sylpheed, mutt, and pine. My configuration is as follows: ------------------------------- using mbox: default_mail_env = mbox:/var/spool/vfolders/%d/%n:INBOX=/var/spool/vmail/%d/%n using imaps Linux version 2.6.11-hardened-r1 (root@gondor) (gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)) #2 Thu May 5 13:14:52 EDT 2005 Thanks for any help you can give, Luke

3 3

[Dovecot] Dovecot + MySQL no auth
by Dylan Baxter 28 Jun '05

28 Jun '05

I haven't been able to login to my mail server using MySQL authentication and I believe I've found the issue. My POP log says: dovecot: Jun 07 09:58:56 Error: auth(default): sql(dylan(a)domain.com,127.0.0.1): Password query must return a field named "password" dovecot: Jun 07 09:58:56 Info: pop3-login: Disconnected [127.0.0.1] The password field in MySQL is called "passwd". Am I to understand that there is no way around this? I must rename the field to "password"? My config files all check out. I'm pretty sure I'm at a road block here. Any help would be greatly appreciated. Also, aren't there anough Dovecot users to warrant a forum and/or IRC channel? I cant seem to find either (but thank you for the mailing list!). Thanks all for any help! Dylan

4 4

[Dovecot] Restrictions on User Basis
by Net Cerebrum 28 Jun '05

28 Jun '05

Hi, I am running dovecot on Fedora Linux in our organization and use IMAP as well as POP3 protocols for mail retrieval. I want to impose the following user based restrictions: (a) I want to permit only selective users to access either POP3 or IMAP server or both. (b) The server can be accessed from LAN as well as WAN. However I want to allow only selective users to be able to access POP3 or IMAP server from the WAN side (or on the basis of IP addresses). What do I need to do to impose these restrictions ? Thanks,

3 2

[Dovecot] APPEND issue with Thunderbird
by Todd Burroughs 28 Jun '05

28 Jun '05

I'm getting a strange problem with APPEND and Thunderbird 0.8. This was working fine in the CVS version from June 8 and is not so fine as of June 20. It works fine using Pine. It appears that imap is hanging when trying to append to a folder. Right now, an imap process has the file open for about 1/2 hour. It wrote the headers out, but not the body. When Thunderbird disconnects from it, it closes the file, but does not finish writing the email. Here's the difference in the commands sent by Pine and Thunderbird from rawlogs. These are different accounts. (Thunderbird) (.in file) 2 append "Sent" (\Seen) {520+} Message-ID: <42BAC447.7050901(a)hostopia.com> (rest of headers and message follows) The .out file is empty --------------------------------------- (Pine) (.in file) 00000003 CAPABILITY 03000004 APPEND Sent {392} Date: Wed, 22 Jun 2005 19:35:42 -0400 (EDT) (rest of headers and message follows) 03000005 LOGOUT (.out file) * OK [RAWLOG TIMESTAMP] 2005-06-22 19:36:20 * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 00000003 OK Capability completed. + OK 03000004 OK Append completed. * BYE Logging out 03000005 OK Logout completed. ----------------------------------------- Todd

3 2

[Dovecot] IP Based Access
by kasharif＠citech-bd.com 28 Jun '05

28 Jun '05

Hi, Can someone tell me how can I restrict 110 port access other than my IP block? if it through tcp-wrapper then how can i do that? Thanking Sharif

5 5