- dovecot - dovecot.org

[Dovecot] Restricting IP and/or user access (POP3/IMAP)
by Phil Clare 25 Aug '06

25 Aug '06

Hi, The documentation says to authenticate only from a specific IP or network… if you set this to 127.0.0.1 to indicate the local loop then this effectively blocks every IP address but this one. Since the extra field is in passdb then this would imply it can be done on a per user basis. Have you tried this? Phil ________________________________________ From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Jos Chrispijn Sent: 24 August 2006 15:08 To: dovecot(a)dovecot.org Subject: [Dovecot] Restricting IP and/or user access (POP3/IMAP) Hi, Just new on this mailinglist; I sure hope my questions wouldn't be too dumb for words :-) Q: Restricting IP and/or user access (POP3/IMAP) What I would like to do is blocking some of my user from fetching their mail with neither POP3 nor IMAP. The only way of letting them read/write their e-mail is to be done with my/their Webmail client. On the site of Dovecot I read: 'It's possible to allow user to authenticate only from a specific IP or network. This is especially useful for master users. This can be done by returning allow_nets extra field in passdb.' Actually I am looking for a way of _blocking_ user(names) or certain IP adress(es) instead of _allowing_ certain IP adresses to get their POP3/IMAP mail. Pls could someone hint me out on this? Thanks in advance. Jos -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.5/426 - Release Date: 23/08/2006

3 3

[Dovecot] multiple mailboxes in imap
by einKI.ml 25 Aug '06

25 Aug '06

Hi I try to setup a mail server which fetches mails from some pop accounts and presents them through imap (with dovecot) to my local network. I get the mails with getmail at this works as it should. To use dovecot as a pop3 and imap server works too. Now I am trying to setup multiple mailboxes which then should be presented to the user as different folders. I think I have to use namespaces for this (is this correct?) So I tried to configure two namespaces with the following statement. namespace private { separator = / inbox = yes prefix = } namespace private { separator = / prefix = ns location = maildir:/data/server/mail/in/%u/ns } when i try to access the imap server with thunderbird I can receive mails for Inbox but when I want to subscripe an additional folder ns can be seen but is grayed out in thunderbird. To summarize this can anybody give me a hint or example how to configure multiple mailboxes which are located in different directories on the server. thx

1 0

[Dovecot] forward flag metadata
by Tim Schafer 24 Aug '06

24 Aug '06

In testing the migration from courier-imap to dovecot I've discovered that the forward flag on messages isn't kept track of in a standard way. courier-imap seems to keep track of forwarded messages in courierimapkeywords/:list dovecot seems to add an 'a' flag to the filename. Unfortunately this 'a' flag information doesn't seem to be given out by dovecot. It's like it's write only. Is it a bug that dovecot doesn't hand out the "forwarded" metadata? -- Regards, Tim Schafer Information Technology Logistics Easier with Technology Freight Solution Providers direct 916-376-6190 10453 Old Placerville Road fax 916-376-6156 Sacramento, CA 95827 tim_schafer(a)shipfsp.com

3 3

[Dovecot] getting dovecot unwedged
by Scott Murman 24 Aug '06

24 Aug '06

I'm having a problem with the dovecot server. I've upgraded to 1.0rc7 to no avail. My naive view is that a cache file is corrupt, or a lock file cannot be unset. Certain mailboxes cannot be accessed to read or write. Checking the process, the server looks stuck in an infinite poll/wait loop. telnetting directly to the server shows that things are definately amiss, though the original problem may have been caused by a faulty client (Apple Mail or Outlook). My question at this point is how to unwedge the server. Is there a cache repair utility, or a list of files which shouldn't exist? I don't see this info on the Wiki. After sortinig this out, I'm going to install mysql, since this seems to be the more-tested installation. Will dovecot automatically rebuild my current databases or do i need to prepare for sql by hand? -SM-

1 0

[Dovecot] dovecot v1.0 rc7 hung up
by Jack Chen 24 Aug '06

24 Aug '06

It looks like the v.0 RC7 is still not stable. It hangs almost every day. This morning I found that pop3 was not working but imap was working. I know other times when dovecot stop working, neither pop3 and imap worked. I just want to know if other users are getting the same problem.

3 2

[Dovecot] Restricting IP and/or user access (POP3/IMAP)
by Jos Chrispijn 24 Aug '06

24 Aug '06

2 1

[Dovecot] (no subject)
by Joseph D. Wagner 24 Aug '06

24 Aug '06

Ok, I tried: sh -x /etc/rc.d/init.d/dovecot start and it started ok. Then I tried: sh /etc/rc.d/init.d/dovecot start and it started ok too. However, simply using: /etc/rc.d/init.d/dovecot start won't start. On a hunch, I disabled SELinux, and then: /etc/rc.d/init.d/dovecot start started ok. So I have an SELinux problem. Right now I'm doing a filesystem relabel. If that doesn't work, does anyone know where to go from here? Joseph D. Wagner

2 1

[Dovecot] sieve-cvs build failing @ 'make'
by Richard 24 Aug '06

24 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi, i've dovecot-cvs up on osx. logging in with virtual users is working. so far so good. i'm attempting to build sieve support now. after: % cd /usr/ports/dovecot/dovecot-sieve % glibtoolize -f -c % autoreconf -i -f configure.in: installing `./install-sh' configure.in: installing `./missing' src/Makefile.am: installing `./depcomp' configure.in: installing `./ylwrap' Makefile.am: installing `./INSTALL' Makefile.am: installing `./COPYING' a: % ./configure \ --prefix=/usr/local/dovecot \ ... --disable-static --enable-shared \ --with-dovecot=/usr/ports/dovecot/dovecot-cvs % make fails @: ... gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/ports/dovecot/dovecot-cvs - -I/usr/ports/dovecot/dovecot-cvs/src/lib - -I/usr/ports/dovecot/dovecot-cvs/src/lib-dict - -I/usr/ports/dovecot/dovecot-cvs/src/lib-mail - -I/usr/ports/dovecot/dovecot-cvs/src/lib-storage - -I/usr/ports/dovecot/dovecot-cvs/src/deliver - -I/usr/local/berkeley-db/include -I/usr/local/cyrus-sasl/include - -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations - -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast - -I/usr/local/ssl/include -MT map.lo -MD -MP -MF .deps/map.Tpo -c map.c - -fno-common -DPIC -o .libs/map.o if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - -I. -I.. -I/usr/ports/dovecot/dovecot-cvs - -I/usr/ports/dovecot/dovecot-cvs/src/lib - -I/usr/ports/dovecot/dovecot-cvs/src/lib-dict - -I/usr/ports/dovecot/dovecot-cvs/src/lib-mail - -I/usr/ports/dovecot/dovecot-cvs/src/lib-storage - -I/usr/ports/dovecot/dovecot-cvs/src/deliver - -I/usr/local/berkeley-db/include -I/usr/local/cyrus-sasl/include - -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations - -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast - -I/usr/local/ssl/include -MT sieve-cmu.lo -MD -MP -MF ".deps/sieve-cmu.Tpo" -c -o sieve-cmu.lo sieve-cmu.c; \ then mv -f ".deps/sieve-cmu.Tpo" ".deps/sieve-cmu.Plo"; else rm -f ".deps/sieve-cmu.Tpo"; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/ports/dovecot/dovecot-cvs - -I/usr/ports/dovecot/dovecot-cvs/src/lib - -I/usr/ports/dovecot/dovecot-cvs/src/lib-dict - -I/usr/ports/dovecot/dovecot-cvs/src/lib-mail - -I/usr/ports/dovecot/dovecot-cvs/src/lib-storage - -I/usr/ports/dovecot/dovecot-cvs/src/deliver - -I/usr/local/berkeley-db/include -I/usr/local/cyrus-sasl/include - -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations - -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast - -I/usr/local/ssl/include -MT sieve-cmu.lo -MD -MP -MF .deps/sieve-cmu.Tpo -c sieve-cmu.c -fno-common -DPIC -o .libs/sieve-cmu.o sieve-cmu.c: In function 'get_flags': sieve-cmu.c:181: error: 'array_t' undeclared (first use in this function) sieve-cmu.c:181: error: (Each undeclared identifier is reported only once sieve-cmu.c:181: error: for each function it appears in.) sieve-cmu.c:181: error: parse error before 'union' sieve-cmu.c:181: warning: unused variable 'v_modifiable' sieve-cmu.c:181: warning: unused variable 'v' sieve-cmu.c:178: warning: unused parameter 'sieve_flags' sieve-cmu.c:179: warning: unused parameter 'flags_r' sieve-cmu.c:179: warning: unused parameter 'keywords_r' sieve-cmu.c: At top level: sieve-cmu.c:181: warning: type defaults to 'int' in declaration of 'keywords' sieve-cmu.c:181: warning: data definition has no type or storage class sieve-cmu.c:185: warning: type defaults to 'int' in declaration of 'flags_r' sieve-cmu.c:185: warning: data definition has no type or storage class sieve-cmu.c:187: error: parse error before 'void' sieve-cmu.c:187: warning: type defaults to 'int' in declaration of '_array_tmp' sieve-cmu.c:187: warning: initialization makes integer from pointer without a cast sieve-cmu.c:187: warning: data definition has no type or storage class sieve-cmu.c:187: error: parse error before '&' token sieve-cmu.c:193: error: parse error before '&' token sieve-cmu.c:209: warning: type defaults to 'int' in declaration of 'name' sieve-cmu.c:209: error: conflicting types for 'name' sieve-cmu.c:182: error: previous declaration of 'name' was here sieve-cmu.c:209: warning: initialization makes integer from pointer without a cast sieve-cmu.c:209: warning: data definition has no type or storage class sieve-cmu.c:210: error: parse error before 'void' sieve-cmu.c:210: error: parse error before '&' token sieve-cmu.c:212: warning: type defaults to 'int' in declaration of 'keywords_r' sieve-cmu.c:212: error: request for member 'arr' in something not a structure or union sieve-cmu.c:213: error: request for member 'v' in something not a structure or union sieve-cmu.c:213: error: request for member 'arr' in something not a structure or union sieve-cmu.c:213: warning: type defaults to 'int' in declaration of 'type name' sieve-cmu.c:213: warning: cast from function call of type 'const void *' to non-matching type 'int' sieve-cmu.c:213: warning: pointer/integer type mismatch in conditional expression sieve-cmu.c:213: error: initializer element is not constant sieve-cmu.c:213: warning: data definition has no type or storage class sieve-cmu.c:214: error: parse error before '}' token make[3]: *** [sieve-cmu.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 - -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEAREDAAYFAkTpGRwACgkQlffdvTZxCMaAaQCeJVgg9SIx2iezvPwtHGZVghQE h4wAniYsJU//3a010k0bO0p9me8RHIGz =6Dh0 -----END PGP SIGNATURE-----

4 4

[Dovecot] Problems with dovecot 1.0rc5 + MySQL 5.0.24
by Daniel Torreblanca 24 Aug '06

24 Aug '06

Hi all, I'm having an intermittent problem logging users in through a webmail client (RoundCube). My maillog reports this: auth(default): vmysql: sql error[3]: MySQL server has gone away imap-login: Disconnected: user=<sales(a)coppersinkdepot.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured The MySQL server hasn't gone anywhere, I can log into it fine and other apps report no problems with it. Restarting Dovecot fixes this issue, but it'll just happen again later. I'm on OpenBSD 3.9 using vpopmail. I've looked through the mailing list archives but can't find any info on this specific problem. Any ideas?

3 3

Re: [Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3
by Esquivel, Vicente 24 Aug '06

24 Aug '06

I am sorry maybe I confused all of you, but I am not running them side by side. What I did was install one rpm and uninstall it then install 1.0 and then uninstall it. Testing the individually when installed. Vicente ________________________________ From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Jeff Graves Sent: Wednesday, August 23, 2006 4:54 PM To: dovecot(a)dovecot.org Subject: Re: [Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3 The config files are different of 0.99 and 1.0 (and I'm not sure you can run them side by side). Delete the config for 0.99 and install just 1.0rc7 and modify it's config. You may also need to delete the index files and recreate the subscriptions file as I don't think they're compatible. -- Jeff Graves, MCSA Image Source, Inc. 508.966.5200 x31 www.image-src.com -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Esquivel, Vicente Sent: Wednesday, August 23, 2006 4:27 PM To: Dovecot Mailing List Subject: Re: [Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3 Anyone else see something similar to this? Vicente ________________________________ From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Esquivel, Vicente Sent: Wednesday, August 23, 2006 8:39 AM To: Dovecot Mailing List Subject: [Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3 Hello all, I am new to the list so bear with me. I am testing dovecot out on a test server running RHEL ES 3, I have installed 0.99.14-1.1.el3 and 1.0-0_20.rc7.el3. This server is using the mbox mailbox format, running sendmail, procmail, and using PAM to do authentication to an LDAP server. I get varying results between the two version. 0.99.14-1.1.el3 : Upon installing this I leave the defaults and login just fine, I can view mail just fine via outlook express and thunderbird. 1.0-0_20.rc7.el3: Upon installing this I leave the defaults and login just fine but I cannot view my email via outlook express or thunderbird. The logs indicate that it reads my inbox with no errors but I still cannot see anything. Can anyone please help me with this. Thanks Vicente

1 0

Re: [Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3
by Esquivel, Vicente 24 Aug '06

24 Aug '06

Anyone else see something similar to this? Vicente ________________________________ From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Esquivel, Vicente Sent: Wednesday, August 23, 2006 8:39 AM To: Dovecot Mailing List Subject: [Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3 Hello all, I am new to the list so bear with me. I am testing dovecot out on a test server running RHEL ES 3, I have installed 0.99.14-1.1.el3 and 1.0-0_20.rc7.el3. This server is using the mbox mailbox format, running sendmail, procmail, and using PAM to do authentication to an LDAP server. I get varying results between the two version. 0.99.14-1.1.el3 : Upon installing this I leave the defaults and login just fine, I can view mail just fine via outlook express and thunderbird. 1.0-0_20.rc7.el3: Upon installing this I leave the defaults and login just fine but I cannot view my email via outlook express or thunderbird. The logs indicate that it reads my inbox with no errors but I still cannot see anything. Can anyone please help me with this. Thanks Vicente

2 1

[Dovecot] Rename folder bug dovecot-1.0RC6 ?
by Ian Thurlbeck 23 Aug '06

23 Aug '06

Dear All can someone confirm this bug please ? I am using Thunderbird 1.07, TB 1.5.0.4, Horde/IMP webmail as test clients, all running on FC4. Server is 1.0RC6 on CentOS 4 with maildir-sep set to ';' To reproduce: In your favourite mail client: 1. Create a top-level mail folder "atest" 2. Rename "atest" to "atest-extra" (basically hyphen<anything>) Result: Error about mailbox "atest-extra" does not exist If you refresh the folder list you see a new folder called "atest-extra-extra" (read all about it). Anyone else see this or is just me ? Many thanks Ian -- Ian Thurlbeck http://www.stams.strath.ac.uk/ Statistics and Modelling Science, University of Strathclyde Livingstone Tower, 26 Richmond Street, Glasgow, UK, G1 1XH Tel: +44 (0)141 548 3667 Fax: +44 (0)141 552 2079

3 2

[Dovecot] virtual user directories?
by Mike 23 Aug '06

23 Aug '06

I'm installing dovecot and hope to migrate my users from a POP3 system soon. I have the users in LDAP and LDAP is working, dovecot is using LDAP to authenticate my tests. What I'm trying to find is a setting when a user is authenticated by LDAP and dovecot, and that user directory does not exist in the location I have given for the private name space, I want dovecot to create the directory. Mentioning in a log that it created a directory is ok, but I want it to create the directory. I do not want to have to create the directories by hand (easy to do, I know, but that's not the point). Is there a way to tell dovecot to create any missing directories for authenticated users? Mike

1 0

[Dovecot] bug? order dependencies in branch_1_0 conf file
by Richard 23 Aug '06

23 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 bldg dovecot cvs branch_1_0 on osx, i'm seeing a sensitivity to order in protocol statements. e.g., on launch: THIS WORKS FINE: protocol lda { sendmail_path = /usr/local/exim/bin/exim ... plugin { quota = maildir:storage=10240 # 10 MB quota limit } } but, THIS DOES NOT protocol lda { ... plugin { quota = maildir:storage=10240 # 10 MB quota limit 65: } 66: sendmail_path = /usr/local/exim/bin/exim 67: } reporting: /dovecot.conf line 66: Unknown setting: is this, in fact, a bug? feature? thanks, richard - -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEAREDAAYFAkTsnD0ACgkQlffdvTZxCMbu1QCfbyq1bddAz8H5RdDJJYx8iTMw SNkAoIaK6xwJ05zM2aJ0/XJH+UucdPoV =9ajq -----END PGP SIGNATURE-----

1 0

[Dovecot] Maildir folder separator
by Mikko Kortelainen 23 Aug '06

23 Aug '06

Hi, There's been some demand from users to make it possible to use the period character (.) in folder names, but that is impossible when the folder separator is already period. Is there any possibility of replacing that which another separator, say a / ? -Mikko

14 16

[Dovecot] Problems with VersaMail on PalmOS
by Paul Tansom 23 Aug '06

23 Aug '06

I'm at the early stages of debugging this problem, but in case I can save some time because somebody else has already come across these issues I thought I'd try a quick post. I have an installation of Dovecot 0.99.14-1sarge0 from the Debian stable tree (so nothing cutting edge, but it's proving stable and reliable) that I am connecting to from a Palm TX with VersaMail 3.1C over IMAP. Sadly it doesn't display all the mail folders I have available and I'm not entirely sure why. So far I've not found a common link between which are displayed, and if I try renaming them then the ones displayed change - so I suspect there is a certain randomness to this. I am aware that it doesn't cope with subfolders, and all these are root folders. Some of the root folders are empty because they are simply acting as a container for other folders in case that is relevant. As I say I'm at the early stages, and I'm also looking at other Palm mail apps (but this came with it so it seemed a good starting point). I'll post more diagnostic details if I need help further down the line, but in the mean time if anyone has also seen this I'd be interested to hear any details. -- Paul Tansom | Aptanet Ltd. | http://www.aptanet.com

1 0

[Dovecot] Unable to get LDA working
by Gerard Seibert 23 Aug '06

23 Aug '06

FreeBSD 6.1 STABLE Postfix version 2.4-20060806 Dovecot v1.0.rc2 I have the following in the postfix main.cf file: mailbox_command = /usr/local/libexec/dovecot/deliver This is from the dovecot.conf file: default_mail_env = mbox:/var/mail/%u However, mail is never delivered with this configuration. This is an excerpt from the 'dovecot.log' file: deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1928.e70d4dd9d14583ce) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1932.e70d4dd9d14583ce) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1950.dd8b6a29139b74ac) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1951.847c445495634caa) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1952.847c445495634caa) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied I have several different users, and they all receive the same type of error message. I have reverted to having postfix deliver the mail and having dovecot as the POPs server. That works fine. I would like to know what I am doing wrong though in getting Dovecot to work as an LDA. -- Gerard Seibert gerard(a)seibercom.net GREAT MOMENTS IN AMERICAN HISTORY (#17): On November 13, Felix Unger was asked to remove himself from his place of residence.

1 0

[Dovecot] Exempt mailboxes from indexing?
by B H 23 Aug '06

23 Aug '06

I looked through the wiki and the archives, but couldn't find an answer to this question. We use a webmail product that uses three dummy mbox dotfiles for storing configuration and temporary info. I'm trying to find a way to have dovecot's indexing ignore all dotfiles, and so far have had no luck (other than, of course, coding it in myself). Does anyone know if this is possible? Thanks. -Brian Hayden

2 2

[Dovecot] Performance problem with outlook & outlook express
by Luc Rocheleau 23 Aug '06

23 Aug '06

Hi, I've set up a dovecot server under redhat enterprise 4.3 with the basic configuration(mbox). Everything runs fine under webmail(squirrelmail) and thunderbird. When I try it under outlook/outlook express tough, it takes a couple of minutes after the authentication to get all headers where it takes a couple of seconds under thunderbird(both windows and linux version). I tried with these two versions with same results: dovecot-1.0.beta9 and dovecot-1.0.rc7 Any idea? Thanks for help and regards --

2 2

[Dovecot] 0.99.14-1.1.el3 vs 1.0-0_20.rc7.el3
by Esquivel, Vicente 23 Aug '06

23 Aug '06

Hello all, I am new to the list so bear with me. I am testing dovecot out on a test server running RHEL ES 3, I have installed 0.99.14-1.1.el3 and 1.0-0_20.rc7.el3. This server is using the mbox mailbox format, running sendmail, procmail, and using PAM to do authentication to an LDAP server. I get varying results between the two version. 0.99.14-1.1.el3 : Upon installing this I leave the defaults and login just fine, I can view mail just fine via outlook express and thunderbird. 1.0-0_20.rc7.el3: Upon installing this I leave the defaults and login just fine but I cannot view my email via outlook express or thunderbird. The logs indicate that it reads my inbox with no errors but I still cannot see anything. Can anyone please help me with this. Thanks Vicente

1 0

[Dovecot] 1.0 RC7 released
by Timo Sirainen 23 Aug '06

23 Aug '06

http://dovecot.org/releases/dovecot-1.0.rc7.tar.gz http://dovecot.org/releases/dovecot-1.0.rc7.tar.gz.sig Can everyone now agree that there are no more hangs? :) * Require that Dovecot master process's version number matches the child process's, unless version_ignore=yes. Usually it's an accidental installation problem if the version numbers don't match. * Maildir: Create maildirfolder file when creating new maildirs. + ldap+prefetch: Use global uid/gid settings if LDAP query doesn't return them + %variables: Negative offsets count from the end of the string. Patch by Johannes Berg. - kqueue ioloop code rewrite - notify=kqueue might have caused connection hangs sometimes - deliver: If message body contained a valid mbox From_ line, it and the rest of the message was skipped. - mbox: We got into infinite loops if trying to open a 2 byte sized file as mbox. - Don't crash with ssl_disable=yes - quota plugin caused compiling problems with some OSes - mbox: After saving a mail to a synced mbox, we lost the sync which caused worse performance I think my v1.0 TODO list is: - avoid duplicate flag change notifications, or in case the message is also expunged don't bother notifying its flag changes at all (shouldn't be hard) - HFS+ avoid-hardlinks patch? - 32bit -> 64bit upgrade still doesn't work without assert-crashing: mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) - Courier-compatible INBOX. namespace gives "invalid namespace" errors I'm still not sure about the last one though. Could someone give me specific commands that clients send that causes it? As for the 32bit -> 64bit upgrade fix, could someone give me access to a x86-64 machine for a while to test it out?

14 15

[Dovecot] HMAC-MD5 / HMAC-MD5-context
by Chris Laif 23 Aug '06

23 Aug '06

$ dovecotpw -p testpass {HMAC-MD5}fe8522268d91e485ccac8f36800e4fa6b10363e2a371cfa61731109b450906cd I wonder if the prefix 'HMAC-MD5' is the correct notation here. According to RFC2104 an HMAC is calculated as follows: H(K XOR opad, H(K XOR ipad, text)) where H is the cryptographic hash function (MD5 in this case). Therefore the result has to be a 128 bit string, which is obviously not the case in the above shown example. In addition, the input value 'text' is missing if you only have a password K. Maybe it would be better to use {HMAC-MD5-CONTEXT} or {HMAC-MD5-CTX} ? Chris

4 3

[Dovecot] Can't Start dovecot from inetd
by Joseph D. Wagner 23 Aug '06

23 Aug '06

This one has me stumped. After upgrading from dovecot-1.0-beta8 to dovecot-1.0-rc6, I can't start dovecot from /etc/rc.d/init.d/dovecot. I can start dovecot directly from the command line (/usr/sbin/dovecot). I can still use /etc/rc.d/init.d/dovecot to query the status of dovecot and shutdown dovecot, but I can't use it to start dovecot. It just says "FAILED". diff scan of the two different versions of the /etc/rc.d/init.d/dovecot file says they're identical. Ideas? Joseph D. Wagner

2 1

Re: [Dovecot] auth failure with digest-md5
by LeVA 22 Aug '06

22 Aug '06

> .. > > 00:49:28 Info: auth(default): client in: AUTH 1 DIGEST-MD5 > > service=POP3 > > secured lip=192.168.0.202 rip=192.168.0.3 > > > >[...] > > rip=192.168.0.3, lip=192.168.0.202, TLS > > <newline> > >00:49:28 Info: auth(default): passwd-file /etc/dovecot.passwd: Read 1 > > users > Does this contain only the "info" lines and no error lines? 1.0beta9 > fixed this problem: > > - DIGEST-MD5: Trying to use subsequent authentication crashed > dovecot-auth. > > I think that's your problem. The logs should have said that dovecot- > auth crashed though. The problem solved due to the upgrade, thanks! Daniel -- LeVA

1 0

[Dovecot] 1.0rc7: Login process died too early - shutting down
by Vince Valenti 22 Aug '06

22 Aug '06

Hello: Not sure if this is 1.0rc7 specific or not, but everything was working great until Dovecot died completely with this information in the log: Aug 21 14:44:16 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.11 Aug 21 14:44:16 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.4 Aug 21 14:44:16 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.17 Aug 21 14:44:17 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.32 Aug 21 14:44:17 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.24 Aug 21 14:44:17 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.37 Aug 21 14:44:17 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.50 Aug 21 14:44:17 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.44 Aug 21 14:44:17 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.57 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.6 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.31 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.5 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.23 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.3 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.26 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.41 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.59 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.64 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.55 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.39 Aug 21 14:44:19 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.47 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.33 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.51 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.36 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.63 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.60 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.62 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.38 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.43 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.40 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.48 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.34 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.45 Aug 21 14:44:20 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.46 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.69 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.66 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.67 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.65 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.72 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.73 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.68 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.71 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.70 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.95 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.97 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.102 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.116 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.110 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.117 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.109 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.133 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.92 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.87 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.104 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.78 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.122 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.135 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.88 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.93 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.86 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.74 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.131 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.129 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.103 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.123 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.85 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.79 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.114 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.170 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.171 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.172 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.173 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.174 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.175 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.178 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.177 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.176 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.179 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.180 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.181 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.182 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.183 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.184 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.185 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.186 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.187 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.188 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.189 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.190 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.191 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.192 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.193 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.194 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.195 Aug 21 14:44:23 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.196 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.197 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.200 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.204 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.198 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.205 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.208 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.206 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.199 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.201 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.202 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.203 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.207 Aug 21 14:44:24 sh01 dovecot: imap-login: Disconnected: rip=213.13.124.18, lip=67.59.79.209 Aug 21 14:44:24 sh01 dovecot: Login process died too early - shutting down This is a FreeBSD 6.1-RELEASE box with Dovecot built from ports (with kqueue). This box has 253 IP addresses bound to it and Dovecot is listening on everything. It looks like 213.13.124.18 was connecting to every IP, but I'm not sure why this would cause Dovecot to crash. Any ideas? Thanks, -Vince

3 2