- dovecot - dovecot.org

[Dovecot] Multiple Mail Environments?
by Marc Perkel 28 Aug '05

28 Aug '05

The default_mail_env is very powerful, but .... If you have multiple databases wouldn't it make sense to have a separate mail environment for each database? For example: userdb passwd { default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/vmail/passwd.%d default_mail_env = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX:INDEX=/nobackup/imap-cache/%d-%n } Is this possible? If not - perhaps it should be? -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

3 3

[Dovecot] Installation error on "make"
by Lisandro Grullon 28 Aug '05

28 Aug '05

I am not sure what the problem is. I try ./configure as the intallation point out;however, when I try make I am getting the bellow error. PS. I am running Solaris 10 X86, GNU gcc. 1. [04:05:24][root@www:~/dovecot-1.0.alpha1]$ make 2. make all-recursive 3. Making all in src 4. Making all in lib 5. Making all in lib-sql 6. Making all in lib-ntlm 7. Making all in lib-settings 8. Making all in lib-charset 9. Making all in lib-mail 10. Making all in lib-imap 11. Making all in lib-index 12. Making all in lib-storage 13. Making all in index 14. Making all in maildir 15. Making all in mbox 16. Making all in subscription-file 17. Making all in register 18. make all-am 19. Making all in lib-auth 20. Making all in auth 21. if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -DAUTH_MODULE_DIR=\""/usr/local/lib/dovecot/auth"\" -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -MT mycrypt.o -MD -MP -MF ".deps/mycrypt.Tpo" -c -o mycrypt.o mycrypt.c; \ 22. then mv -f ".deps/mycrypt.Tpo" ".deps/mycrypt.Po"; else rm -f ".deps/mycrypt.Tpo"; exit 1; fi 23. In file included from /usr/include/unistd.h:18, 24. from mycrypt.c:5: 25. /usr/include/sys/feature_tests.h:332:2: #error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications" 26. *** Error code 1 27. make: Fatal error: Command failed for target `mycrypt.o' 28. Current working directory /root/dovecot-1.0.alpha1/src/auth 29. *** Error code 1 30. The following command caused the error: 31. failcom='exit 1'; \ 32. for f in x $MAKEFLAGS; do \ 33. case $f in \ 34. *=* | --[!k]*);; \ 35. *k*) failcom='fail=yes';; \ 36. esac; \ 37. done; \ 38. dot_seen=no; \ 39. target=`echo all-recursive | sed s/-recursive//`; \ 40. list='lib lib-sql lib-ntlm lib-settings lib-charset lib-mail lib-imap lib-index lib-storage lib-auth auth master login-common imap-login imap pop3-login pop3 deliver util'; for subdir in $list; do \ 41. echo "Making $target in $subdir"; \ 42. if test "$subdir" = "."; then \ 43. dot_seen=yes; \ 44. local_target="$target-am"; \ 45. else \ 46. local_target="$target"; \ 47. fi; \ 48. (cd $subdir && make $local_target) \ 49. || eval $failcom; \ 50. done; \ 51. if test "$dot_seen" = "no"; then \ 52. make "$target-am" || exit 1; \ 53. fi; test -z "$fail" 54. make: Fatal error: Command failed for target `all-recursive' 55. Current working directory /root/dovecot-1.0.alpha1/src 56. *** Error code 1 57. The following command caused the error: 58. failcom='exit 1'; \ 59. for f in x $MAKEFLAGS; do \ 60. case $f in \ 61. *=* | --[!k]*);; \ 62. *k*) failcom='fail=yes';; \ 63. esac; \ 64. done; \ 65. dot_seen=no; \ 66. target=`echo all-recursive | sed s/-recursive//`; \ 67. list='src doc'; for subdir in $list; do \ 68. echo "Making $target in $subdir"; \ 69. if test "$subdir" = "."; then \ 70. dot_seen=yes; \ 71. local_target="$target-am"; \ 72. else \ 73. local_target="$target"; \ 74. fi; \ 75. (cd $subdir && make $local_target) \ 76. || eval $failcom; \ 77. done; \ 78. if test "$dot_seen" = "no"; then \ 79. make "$target-am" || exit 1; \ 80. fi; test -z "$fail" 81. make: Fatal error: Command failed for target `all-recursive' 82. Current working directory /root/dovecot-1.0.alpha1 83. *** Error code 1 84. make: Fatal error: Command failed for target `all' 85. [04:05:28][root@www:~/dovecot-1.0.alpha1]$ ----------------------------------------------------------------------------------------------------------------------- Lisandro Grullon New York City College of Technology Division of Continuing Education Director of Network Operations Lisandro Office: 1718-552-1178 Lisandro E-mail: lgrullon(a)citytech.cuny.edu "The only reason for time is so that everything doesn't happen at once.". <Albert Einstein>

2 1

[Dovecot] Authentication with encrypted passwords
by Sebastjan Trepca 28 Aug '05

28 Aug '05

Hello, I have a postgresql database which contains users that will access dovecot, but their passwords are hashed and I don't have them in plain text. I was reading documentation that you can add tell dovecot which password scheme should it use. For example: password_query = "select '{MD5}'||password from users where userid=%u" Which would mean that dovecot will hash the password with MD5 from client and match it with the one in database. Did I understand this correctly ? Thanks, Sebastjan

2 1

[Dovecot] Namespace Feature
by Marc Perkel 28 Aug '05

28 Aug '05

I've never used namespaces and don't quite know what they do. If I add a namespace then do things like shared folders magically appear to users? Also - I wonder if this is possible. I'd like to create a write only shared folder. I know this is unusual but I have a reason. I'd like to have a folder that people can drag spam into to report missed spam. I want to write only so people aren't reading each other's spam. I have a bot that comes by and reads this to train the bayesian filter. Right now I have to create these folders individually. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

3 2

[Dovecot] Postfix/Dovecot
by Micah Stevens 28 Aug '05

28 Aug '05

Hi, I searched through the maillist archives and the docs, but didn't find anything that directly addresses my question, so here goes if anyone has some time to address it. I'm running a redhat el3 server, with Postfix as the MTA, and I'd like to setup Dovecot to provide IMAP/POP3 services. Postfix uses MySQL lookups to do mailbox lookups, and I configured dovecot to do the same thing. The mail is delivered to /usr/local/virtual/<domainname>/<end.address>/ in maildir format by Postfix. This is working fine. I've setup dovecot, and set it do user auth and user lookups to MySQL. This seems to be working fine as I get no mysql errors from the queries, and my login process (to IMAP from localhost) is fine. Here's a typical scenario: telnet localhost imap Trying 127.0.0.1... Connected to localhost.domain (127.0.0.1 <http://127.0.0.1>). Escape character is '^]'. * OK dovecot ready. 1login micah(a)9250x.com "rigid2" 1 OK Logged in. 2 select INBOX 2 NO If I look in the directory for micah(a)9250x.com I find: # ls cur new tmp The permissions are 777 for now to eliminate that possibility. The dovecot log file lists: imap-login: Aug 28 12:27:11 Info: Login: micah(a)9250x.com [127.0.0.1<http://127.0.0.1> ] each time I log in, and nothing after that indicating why it's not seeing any mail. Why isn't it seeing any mail? Do I need to make an Inbox directory and tell postfix to deliver there? From reading the docs, having the delivery into the main maildir directory should be okay, but I might be mis-reading. Any thoughts would be much appreciated.. Thank you, -Micah

1 0

[Dovecot] thanks for changing the name of the alpha tarfile!
by Joakim Verona 28 Aug '05

28 Aug '05

Its much easier to build RPM:s now, thanks :) -- Joakim Verona www.verona.se

1 0

[Dovecot] Permission denied changing to mail directory
by Chris Hogan 28 Aug '05

28 Aug '05

I have 3 domains using one mail server. I've set the dovecot mail directories to be /mail/mail/%d/%n When someone logs on, dovecot attempt to navigate to the domain directory first & we get a permission denied, and we get no further. Its very odd because (a) it was working up until 16:50 on Thursday & (b) the directories now have 777 access. Each user is (at present) a separate unix user & the directories are owned by root & have a file group of mail. I would have thought that the 777 access would have been enough. I don't know what we did on Thursday evening, but any ideas about how to fix the permissions problem? Chris

3 2

[Dovecot] Dovecot and Active Directory Authentication
by Dave Smith 28 Aug '05

28 Aug '05

First off, sorry if this has been asked before - I have looked, honest. Is it possible to get dovecot to authenticate users against active directory, treating the AD as a plain ldap server? I have this working with cyrus saslauthd. Currentlt I get a long delay (30 seconds or so) then * BYE Disconnected for inactivity. All I get in the maillog is imap-login: Disconnected: Inactivity [::ffff:127.0.0.1] I am using dovecot-0.99.11-2.EL4.1 on CentOS 4. If anybody has got this to work then please let me know - otherwise I will be forced to use Cyrus........ Cheers Dave Smith

2 1

[Dovecot] Dovecot Delivery Bug
by Marc Perkel 27 Aug '05

27 Aug '05

Ran into an interesting bug in Dovecot delivery. A friend forwards an email to me as an atachment. When I receive it - it comes in as two separate messages. One is the forwarding message which is empty, and the other is the original message that was forwarded but it comes in as if I had got the email directly. If I use exim to deliver the message to the mailbox it works. But when exim pipes the message into dovecot deliver it gats split. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

Re: [Dovecot] Authenticate user thru PAM
by Chris Wakelin 27 Aug '05

27 Aug '05

Adrian Mak wrote: > my mailsystem is using postfix and virtual mailbox which stored in mysql db. > SMTP AUTH is using PAM, pam-mysql to authenticate against a mysql db. > > I installed dovecot 0.99-14. In the dovecot example config file > it mentioned that auth_passdb can check against thru PAM but auth_userdb didn't > > Does it mean that auth_userdb should use other means e.g. /etc/passwd, > shadow, vpopmail, etc and in my case it is mysql. Right ? Yes, at least in 1.0-alpha1/stable, so I guess the same for 0.99. Dovecot can authenticate via mysql directly, of course (but I've never done it, so don't ask me how!) 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] Dovecot and Active Directory Authentication
by Chris Wakelin 27 Aug '05

27 Aug '05

Dave Smith wrote: > First off, sorry if this has been asked before - I have looked, honest. > > Is it possible to get dovecot to authenticate users against active > directory, treating the AD as a plain ldap server? I have this working > with cyrus saslauthd. > I have it working with PAM and pam_ldap in 1.0-stable/alpha1, but with userdb = passwd (we have users in NIS as well as AD). Search the mail archives for details! LDAP auth won't work directly as it expects to find a hashed version of the password. > I am using dovecot-0.99.11-2.EL4.1 on CentOS 4. Probably a good idea to upgrade to dovecot-1.0-stable or dovecot-1.0-alpha1 (0.99.11 is pretty old, even 0.99.14 is pretty well obsolete). 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

1 0

[Dovecot] Wiki of dovecot.conf file
by Tim Schaefer 26 Aug '05

26 Aug '05

What would be extremely helpful is a really clean explanation of how to set up connections for MySQL. It would have to start with basic information and some real-world examples that make no assumptions, and clearly spell it out without confusion. In fact good examples reduce the need to subscribe to mailing lists and ask dumb questions! The current assumptions in the docs to date are that somehow non-geeks and those of us who have learned far more about email servers than we ever wanted to will somehow "get it" without decent examples. This has got to be the biggest problem using Dovecot. I've tried just about every pop-server I can find and I am about to give up on Dovecot if I can't get the connection to MySQL to work. I just want decent pop server that understands Maildir, now that I went through Cyrus SASL hell and got that working--again with incredibly poor documentation. And I don't give a rats-ass about IMAP, just need a pop server. Maybe IMAP later, for now just a pop server that understands Maildir and comes from open source. I'm using Postfix but it shouldn't matter. So far I've tried the following pop servers: nupop-1.3.9 -- can't compile qmail-1.03 -- a f**ing nightmare cyrus-imap/pop -- poor-to-no docs for pop server -- another nightmare vm-pop3d-1.1.6 -- works only on mbox flexpop-1.0.1 -- no docs , doesn't compile popular-1.5.5 -- docs are too sketchy for installation, too complicated and doesn't work I thought Dovecot would be the last one I have to screw with, but maybe I'm wrong... Thanks, Tim

2 1

[Dovecot] Compile trouble with mysql
by Tim Schaefer 26 Aug '05

26 Aug '05

Hi, I had a devil of a time compiling Dovecot with MySQL, but got it as follows: MYSQL=/usr export CPPFLAGS="-I${MYSQL}/include -I${MYSQL}/lib -I/usr/local/ssl/ -I/usr/local/ssl/include/ " export LDFLAGS="-L${MYSQL}/lib -R${MYSQL}/lib -I${MYSQL}/include -I${MYSQL}/lib -L/usr/local/lib -L/usr/local/ssl/lib" export SSL_FLAGS="-I/usr/local/ssl/ -I/usr/local/ssl/include/" export SSL_LIBS="-L/usr/local/lib -L/usr/local/ssl/lib" ./configure --localstatedir=/var --with-mysql=/usr ... Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with user database modules . : static passdb passwd passwd-file checkpassword mysql (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword mysql (modules) This is basically for somebody who RPM'd MySQL into /usr . I also figured out the less you give ./configure the better off you are. And...maybe you could help **me**.. :-) If you could post a few samples of how to actually connect to MySQL that would be great, for some reason I STILL cannot connect to MySQL even though I know the user/pass works for my dovecot userid. I know MySQL is compiled into dovecot but still cannot get the connect to work. I've tried: my dovecot.conf: auth default { mechanisms = plain passdb sql { args = /usr/local/etc/dovecot-mysql.conf } userdb sql { args = /usr/local/etc/dovecot-mysql.conf } } my dovecot-mysql.conf: driver = mysql connect = host=127.0.0.1 dbname=dovecot user=dovecot password=dovecot port=3306 connect = host=mydomain dbname=dovecot user=postfix password=postfix port=3306 connect = host=mydomain dbname=dovecot user=dovecot password=dovecot port=3306 connect = host=localhost dbname=dovecot user=dovecot password=dovecot port=3306 connect = host=/var/lib/mysql/mysql.sock dbname=dovecot user=dovecot password=dovecot port=3306 I get: Aug 26 10:45:35 dovecot: auth-worker(default_with_listener): mysql: Connect failed to (null) (dovecot): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 1 seconds before retry Aug 26 10:45:35 dovecot: auth-worker(default): mysql: Connect failed to (null) (dovecot): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 1 seconds before retry Aug 26 10:47:17 dovecot: Killed with signal 15 Aug 26 10:47:21 dovecot: auth-worker(default): mysql: Connect failed to (null) (dovecot): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 1 seconds before retry Help! Tim

1 0

[Dovecot] Compile trouble with mysql
by Tim Schaefer 26 Aug '05

26 Aug '05

1 0

[Dovecot] Dovecot.1.0.alpha1+mysql+mysql
by jigen 26 Aug '05

26 Aug '05

Hi, we are trying to track down the problem that prevents two mysql password databases from working. Instead of connecting to each database, it looks like dovecot tries to connect *twice* to the second specified. Do do this we just inserted some i_warning()s in the code. We noticed that passdb_sql_init (auth/passdb-sql.c) is called twice, once per configuration file, with the correct argument (path to config file). However, as you can see in the following maillog piece, this function calls sql_connect with the SAME parameters (the parameters of the second database). So the first call works and dovecot connects to the host correctly (lines 7-8), but in the second call dovecot finds the connection already up and obviously doesn't try again (last line). Could this be the origin of the problem? Now we are trying to understand why the argument to sql_connect isn't updated correctly. Maybe a bug in the linked list of sql_connection's? [...] dovecot: auth-worker(default): passdb_sql_init("/etc/dovecot/dovecot-mysql_django.conf") [...] dovecot: auth-worker(default): now calling sql_connect(passdb_sql_conn->db): [...] dovecot: auth-worker(default): passdb_sql_conn->config_path="/etc/dovecot/dovecot-mysql_debord.conf" [...] dovecot: auth-worker(default): passdb_sql_conn->set.connect="host=debord port=3306 dbname=posta_debord user=posta password=foobar" [...] dovecot: auth-worker(default): driver_mysql_connect: host=debord, user=posta, password=foobar. [...] dovecot: auth-worker(default): driver_mysql_connect: conn=0x3c00a6b0 [...] dovecot: auth-worker(default): actually connecting to debord [...] dovecot: auth-worker(default): mysql: Connected to debord (posta_debord) [...] dovecot: auth-worker(default): passdb_sql_init("/etc/dovecot/dovecot-mysql_debord.conf") [...] dovecot: auth-worker(default): now calling sql_connect(passdb_sql_conn->db): [...] dovecot: auth-worker(default): passdb_sql_conn->config_path="/etc/dovecot/dovecot-mysql_debord.conf" [...] dovecot: auth-worker(default): passdb_sql_conn->set.connect="host=debord port=3306 dbname=posta_debord user=posta password=foobar" [...] dovecot: auth-worker(default): driver_mysql_connect: host=debord, user=posta, password=foobar. [...] dovecot: auth-worker(default): driver_mysql_connect: conn=0x3c00a6b0 [...] dovecot: auth-worker(default): already connected to debord!!!! altivec & jigen

1 0

[Dovecot] Dovecot Virtual Users & Sendmail
by Chris Hogan 26 Aug '05

26 Aug '05

Not directly Dovecot, but a configuration problem. We have a working set-up with Dovecot+Procmail+Sendmail, using POP-before-SMTP. We want to be able to offer email accounts to some local schools, using SquirrelMail (keeps their costs & maintenance down). The whole arrangement is working, but we don't want to have to have 300+ School children as users of our Red Hat Enterprise server, so I've set up a passwd style file for authentication. This all works fine, they can access mailboxes & send emails, but to receive Sendmail is checking that they are unix users & bounces messages back if they aren't in /etc/passwd too. Has anybody ever got Sendmail working with Dovecot virtual users? Or is it time I switched to Postfix? Chris Hogan

3 2

[Dovecot] 1.0alpha1: assert and core
by Jeff A. Earickson 26 Aug '05

26 Aug '05

Hi, I've been running 1.0alpha1 in production since August 18, and got my first assert and core yesterday. Otherwise it has been running flawlessly. My setup: Sun E220R, Solaris 9, compiled dovecot with gcc 4.0.1, configured dovecot like so: #!/usr/bin/sh VERSION=1.0-alpha1 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.$VERSION --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl > configure.out The syslog message: Aug 25 04:15:43 emerald dovecot: [ID 107833 mail.error] IMAP(user): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) Gdb analysis of the resulting core file is attached, I hope this helps. The user's mailbox is 41003432 bytes in size. Jeff Earickson Colby College

1 0

[Dovecot] [Fwd: Re:Dovecot] Finally PEBKAC was Failed authentication to a mysql database (bug or PEBKAC?)]
by jigen 25 Aug '05

25 Aug '05

-----Forwarded Message----- From: jigen <jigen(a)metalabs.org> To: Timo Sirainen <tss(a)iki.fi> Subject: Re:Dovecot] Finally PEBKAC was Failed authentication to a mysql database (bug or PEBKAC?) Date: Sat, 20 Aug 2005 18:33:11 +0200 On Fri, 2005-08-19 at 16:56, Timo Sirainen wrote: > Dovecot just passes these values to Mysql library without doing anything > to them itself. So if it happens, it's Mysql library bug. It isn't a bug of mysql or dovecot. It's the most simple problem: mysql permissions :P In mysql 127.0.0.1 and localhost are differents things, and if you copy the user (posta in my case), it doesn't copy the password (and so it works without a password). And more: if you put password, you have to flush privileges. Finally PEBKAC :| > > One more question: how I can specify more different mysql-db conteining > > different users? > > I try in the following way: > > passdb sql { > > args = /etc/dovecot/dovecot-mysql_debord.conf > > } > > passdb sql { > > args = /etc/dovecot/dovecot-mysql_django.conf > > } > > This should work. After trying to authenticate against the first one it > should try the second. Although I'm not sure if I've tried two passdb > sqls before, maybe Dovecot has problems with that.. Well, I'll try once > I get home. I'm working on this problem, but at the moment it doesn't work. It always connects only to second db. Another PEBKAC? This is my configuration file, maybe there's something wrong. (i've cut out commented lines) ----dovecot.conf---- base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s ssl_disable = yes ssl_cert_file = /etc/ssl/django_posta.pem ssl_key_file = /etc/ssl/private/django_posta.pem verbose_proctitle = yes verbose_ssl = yes first_valid_uid = 507 last_valid_uid = 507 first_valid_gid = 507 last_valid_gid = 507 default_mail_env = maildir:/var/vmail/%d/%n@%d/ mail_full_filesystem_access = yes protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb sql { args = /etc/dovecot/dovecot-mysql_debord.conf } passdb sql { args = /etc/dovecot/dovecot-mysql_django.conf } userdb static { args = uid=507 gid=507 } user = root count = 2 } --------------- ciao jigen

1 0

[Dovecot] Thread sorting problem
by Greg Trounson 24 Aug '05

24 Aug '05

I've just installed Dovecot on a Debian Sarge machine and am seeing some very strange thread sorting. In Mozilla Mail and Thunderbird on both Fedora and Debian clients my threads served up by Dovecot look like this (number denotes message time): |-11 | `-12 |-2 |-3 |-4 | `-5 | `-6 | `-7 | `-8 |-1 `-9 `-10 Where the exact same threads served by Sendmail/imap look like this: |-1 |-2 |-3 |-4 | `-5 | `-6 | `-7 | `-8 |-9 | `-10 |-11 | `-12 Squirrelmail shows the threads correctly in both cases too, so I suspect there might be something funny going on with how Thunderbird handles Maildir threads. I notice that Dovecot doesn't support the THREAD=ORDEREDSUBJECT capability, might that have something to do with it? thanks, Greg

3 2

[Dovecot] verbose imap logging
by Jens Laas 24 Aug '05

24 Aug '05

Implements more verbose imap logging (when client exits). Similar to existing logging in POP3. Due to the nature of imap and my incomplete understanding (of the dovecot code) the session statistics reported have varying accuracy. Much better than nothing IMO. Cheers, Jens ----------------------------------------------------------------------- 'This mail automatically becomes portable when carried.' ----------------------------------------------------------------------- Jens Låås Email: jens.laas(a)data.slu.se Department of Computer Services, SLU Phone: +46 18 67 35 15 Vindbrovägen 1 P.O. Box 7079 S-750 07 Uppsala SWEDEN -----------------------------------------------------------------------

1 0

[Dovecot] thunderbird pop3 delete bug workaround
by Jens Laas 24 Aug '05

24 Aug '05

Following is patch that allows tbird to download and redelete the last deleted message. Not particularily nice but for "normal" usage the bug/workaround is not triggered. Tested with huge inbox. --- src/pop3/client.h.orig 2005-08-23 15:00:48.000000000 +0200 +++ src/pop3/client.h 2005-08-23 15:02:18.000000000 +0200 @@ -35,6 +35,9 @@ unsigned int top_count; unsigned int retr_count; + unsigned int last_deleted; + int tbirdbug; + uoff_t *byte_counter; uoff_t byte_counter_offset; --- src/pop3/commands.c.orig 2005-08-24 13:24:33.000000000 +0200 +++ src/pop3/commands.c 2005-08-24 13:26:49.000000000 +0200 @@ -47,8 +47,15 @@ if (client->deleted) { if (client->deleted_bitmask[num / CHAR_BIT] & (1 << (num % CHAR_BIT))) { - client_send_line(client, "-ERR Message is deleted."); - return NULL; + if((client->tbirdbug<256) && (num == client->last_deleted)) + { + client->tbirdbug++; + } + else + { + client_send_line(client, "-ERR Message is deleted."); + return NULL; + } } } @@ -109,6 +116,7 @@ client->deleted_count++; client->deleted_size += client->message_sizes[msgnum]; client_send_line(client, "+OK Marked to be deleted."); + client->last_deleted = msgnum; return TRUE; } ----------------------------------------------------------------------- 'This mail automatically becomes portable when carried.' ----------------------------------------------------------------------- Jens Låås Email: jens.laas(a)data.slu.se Department of Computer Services, SLU Phone: +46 18 67 35 15 Vindbrovägen 1 P.O. Box 7079 S-750 07 Uppsala SWEDEN -----------------------------------------------------------------------

1 0

[Dovecot] Dovecot Deliver?
by Marc Perkel 24 Aug '05

24 Aug '05

I guess Dovecot has an LDA called deliver. What is it and how do I use it? Or is it ready to be used. can't find any docs on it. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

9 18

[Dovecot] public/private email accounts
by Ashvin Meetoo 24 Aug '05

24 Aug '05

Hi, I am running FC4 with postfix/dovecot/amavisd-new etc on my box with 50 staff email accounts (say 10 per 5 departments)... everything is working ok... I want to create 5 more accounts for each department (to be redirected to respective staffs, e.g. sales(a)xyz.com) as well one for everyone... that can be easily done by creating an account and modifying the .forward file in the /home/<user> folder. My great concern is that if by a virus attachment or spam is not detected and sent to everyone(a)xyz.com, it will be replicated to 50 email addresses... what I want is to have the 6 accounts mentionned above to be used only by the personnel and not the outside world... is there a way of doing this? Thank you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[Dovecot] Well, "Hard filesystem quota can also be problematic"
by Jeroen Scheerder 24 Aug '05

24 Aug '05

"Hard filesystem quota can also be problematic", quoth <http://www.dovecot.org/>. Since we actually use quota for our userbasg, this merited further investigation. Using 1.0-stable, we enabled quota on /var and /users filesystems, and set very low quota for a test account. Then we had some mail delivered on it, and we moved some messages about. At some point, Thunderbird started to croak about "The current command did not succeed. The mail server responded: Internal error occured. Refer to server log for more information. [<timestamp>].", "The current command did not succeed. The mail server responded: .", "The current command did not succeed. The mail server responded: Out of disk space." This I can live with. Hoever, at some point in our experiments we also found that a mailbox (mbox format) that did contain a few dozen messages suddenly was truncated to 0 bytes. Not so hot. Can anyone tell me whether or not there is, or will be, some way of using dovecot on a system with quota without risk of data loss when quota limits are reached? How do people cope with this? Regards, Jeroen. p.s. That first error message gave rise to the enclosed patch. diff -r -c1 dovecot-1.0-stable-patched/doc/auth-protocol.txt dovecot-1.0-stable/doc/auth-protocol.txt *** dovecot-1.0-stable-patched/doc/auth-protocol.txt Wed Jul 27 08:08:35 2005 --- dovecot-1.0-stable/doc/auth-protocol.txt Mon Jan 31 17:37:54 2005 *************** *** 171,173 **** ! FAIL reply means an internal error occurred. Usually either a configuration mistake or temporary error caused by lost resource (eg. database down). --- 171,173 ---- ! FAIL reply means an internal error occured. Usually either a configuration mistake or temporary error caused by lost resource (eg. database down). diff -r -c1 dovecot-1.0-stable-patched/doc/index.txt dovecot-1.0-stable/doc/index.txt *** dovecot-1.0-stable-patched/doc/index.txt Wed Jul 27 08:08:39 2005 --- dovecot-1.0-stable/doc/index.txt Mon Jan 31 17:37:54 2005 *************** *** 89,91 **** processes has to scan the mailbox, other processes simply check from the ! log file what changes occurred. --- 89,91 ---- processes has to scan the mailbox, other processes simply check from the ! log file what changes occured. diff -r -c1 dovecot-1.0-stable-patched/src/imap/client.h dovecot-1.0-stable/src/imap/client.h *** dovecot-1.0-stable-patched/src/imap/client.h Wed Jul 27 08:08:26 2005 --- dovecot-1.0-stable/src/imap/client.h Mon Jan 31 17:37:54 2005 *************** *** 68,70 **** /* Read a number of arguments. Returns TRUE if everything was read or ! FALSE if either needs more data or error occurred. */ int client_read_args(struct client *client, unsigned int count, --- 68,70 ---- /* Read a number of arguments. Returns TRUE if everything was read or ! FALSE if either needs more data or error occured. */ int client_read_args(struct client *client, unsigned int count, diff -r -c1 dovecot-1.0-stable-patched/src/imap/cmd-idle.c dovecot-1.0-stable/src/imap/cmd-idle.c *** dovecot-1.0-stable-patched/src/imap/cmd-idle.c Wed Jul 27 08:08:30 2005 --- dovecot-1.0-stable/src/imap/cmd-idle.c Mon Jan 31 17:37:54 2005 *************** *** 159,161 **** } else if (ctx->sync_pending) { ! /* more changes occurred while we were sending changes to client */ --- 159,161 ---- } else if (ctx->sync_pending) { ! /* more changes occured while we were sending changes to client */ diff -r -c1 dovecot-1.0-stable-patched/src/lib/file-cache.h dovecot-1.0-stable/src/lib/file-cache.h *** dovecot-1.0-stable-patched/src/lib/file-cache.h Wed Jul 27 08:06:28 2005 --- dovecot-1.0-stable/src/lib/file-cache.h Mon Jan 31 17:37:55 2005 *************** *** 12,14 **** /* Read data from file, returns how many bytes was actually read or -1 if ! error occurred. */ ssize_t file_cache_read(struct file_cache *cache, uoff_t offset, size_t size); --- 12,14 ---- /* Read data from file, returns how many bytes was actually read or -1 if ! error occured. */ ssize_t file_cache_read(struct file_cache *cache, uoff_t offset, size_t size); diff -r -c1 dovecot-1.0-stable-patched/src/lib/istream.h dovecot-1.0-stable/src/lib/istream.h *** dovecot-1.0-stable-patched/src/lib/istream.h Wed Jul 27 08:06:32 2005 --- dovecot-1.0-stable/src/lib/istream.h Mon Jan 31 17:37:54 2005 *************** *** 60,62 **** /* Like i_stream_next_line(), but reads for more data if needed. Returns NULL ! if more data is needed or error occurred. */ char *i_stream_read_next_line(struct istream *stream); --- 60,62 ---- /* Like i_stream_next_line(), but reads for more data if needed. Returns NULL ! if more data is needed or error occured. */ char *i_stream_read_next_line(struct istream *stream); diff -r -c1 dovecot-1.0-stable-patched/src/lib/read-full.h dovecot-1.0-stable/src/lib/read-full.h *** dovecot-1.0-stable-patched/src/lib/read-full.h Wed Jul 27 08:06:38 2005 --- dovecot-1.0-stable/src/lib/read-full.h Mon Jan 31 17:37:54 2005 *************** *** 3,5 **** ! /* Read data from file. Returns -1 if error occurred, or 0 if EOF came before everything was read, or 1 if all was ok. */ --- 3,5 ---- ! /* Read data from file. Returns -1 if error occured, or 0 if EOF came before everything was read, or 1 if all was ok. */ diff -r -c1 dovecot-1.0-stable-patched/src/lib/strfuncs.c dovecot-1.0-stable/src/lib/strfuncs.c *** dovecot-1.0-stable-patched/src/lib/strfuncs.c Wed Jul 27 08:06:47 2005 --- dovecot-1.0-stable/src/lib/strfuncs.c Mon May 16 23:15:10 2005 *************** *** 100,102 **** if (len < 0) { ! /* some error occurred */ len = 0; --- 100,102 ---- if (len < 0) { ! /* some error occured */ len = 0; diff -r -c1 dovecot-1.0-stable-patched/src/lib/write-full.h dovecot-1.0-stable/src/lib/write-full.h *** dovecot-1.0-stable-patched/src/lib/write-full.h Wed Jul 27 08:06:43 2005 --- dovecot-1.0-stable/src/lib/write-full.h Mon Jan 31 17:37:55 2005 *************** *** 3,5 **** ! /* Write data into file. Returns -1 if error occurred, or 0 if all was ok. If there's not enough space in device, -1 with ENOSPC is returned, and --- 3,5 ---- ! /* Write data into file. Returns -1 if error occured, or 0 if all was ok. If there's not enough space in device, -1 with ENOSPC is returned, and diff -r -c1 dovecot-1.0-stable-patched/src/lib-imap/imap-parser.h dovecot-1.0-stable/src/lib-imap/imap-parser.h *** dovecot-1.0-stable-patched/src/lib-imap/imap-parser.h Wed Jul 27 08:07:00 2005 --- dovecot-1.0-stable/src/lib-imap/imap-parser.h Mon Jan 31 17:37:55 2005 *************** *** 88,90 **** need to do that. Returns number of arguments read (may be less than count ! in case of EOL), -2 if more data is needed or -1 if error occurred. --- 88,90 ---- need to do that. Returns number of arguments read (may be less than count ! in case of EOL), -2 if more data is needed or -1 if error occured. diff -r -c1 dovecot-1.0-stable-patched/src/lib-mail/message-parser.h dovecot-1.0-stable/src/lib-mail/message-parser.h *** dovecot-1.0-stable-patched/src/lib-mail/message-parser.h Wed Jul 27 08:06:56 2005 --- dovecot-1.0-stable/src/lib-mail/message-parser.h Mon Jan 31 17:37:55 2005 *************** *** 112,114 **** input stream is non-blocking and more data needs to be read, -1 when all is ! done or error occurred (see stream's error status). */ int message_parse_header_next(struct message_header_parser_ctx *ctx, --- 112,114 ---- input stream is non-blocking and more data needs to be read, -1 when all is ! done or error occured (see stream's error status). */ int message_parse_header_next(struct message_header_parser_ctx *ctx, diff -r -c1 dovecot-1.0-stable-patched/src/lib-sql/sql-api.h dovecot-1.0-stable/src/lib-sql/sql-api.h *** dovecot-1.0-stable-patched/src/lib-sql/sql-api.h Wed Jul 27 08:06:51 2005 --- dovecot-1.0-stable/src/lib-sql/sql-api.h Mon Jan 31 17:37:55 2005 *************** *** 23,25 **** /* Go to next row, returns 1 if ok, 0 if this was the last row or -1 if error ! occurred. This needs to be the first call for result. */ int sql_result_next_row(struct sql_result *result); --- 23,25 ---- /* Go to next row, returns 1 if ok, 0 if this was the last row or -1 if error ! occured. This needs to be the first call for result. */ int sql_result_next_row(struct sql_result *result); diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/index/maildir/maildir-sync.c dovecot-1.0-stable/src/lib-storage/index/maildir/maildir-sync.c *** dovecot-1.0-stable-patched/src/lib-storage/index/maildir/maildir-sync.c Wed Jul 27 08:08:03 2005 --- dovecot-1.0-stable/src/lib-storage/index/maildir/maildir-sync.c Mon Jan 31 17:37:55 2005 *************** *** 7,9 **** We want to be as efficient as we can. The most efficient way to ! check if changes have occurred is to stat() the new/ and cur/ directories and uidlist file - if their mtimes haven't changed, --- 7,9 ---- We want to be as efficient as we can. The most efficient way to ! check if changes have occured is to stat() the new/ and cur/ directories and uidlist file - if their mtimes haven't changed, *************** *** 14,16 **** then make a modification. Such modifications wouldn't get noticed ! until a new modification occurred later. --- 14,16 ---- then make a modification. Such modifications wouldn't get noticed ! until a new modification occured later. diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/mail-storage.c dovecot-1.0-stable/src/lib-storage/mail-storage.c *** dovecot-1.0-stable-patched/src/lib-storage/mail-storage.c Wed Jul 27 08:07:58 2005 --- dovecot-1.0-stable/src/lib-storage/mail-storage.c Mon Jan 31 17:37:55 2005 *************** *** 12,14 **** #define CRITICAL_MSG \ ! "Internal error occurred. Refer to server log for more information." #define CRITICAL_MSG_STAMP CRITICAL_MSG " [%Y-%m-%d %H:%M:%S]" --- 12,14 ---- #define CRITICAL_MSG \ ! "Internal error occured. Refer to server log for more information." #define CRITICAL_MSG_STAMP CRITICAL_MSG " [%Y-%m-%d %H:%M:%S]" diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/mail-storage.h dovecot-1.0-stable/src/lib-storage/mail-storage.h *** dovecot-1.0-stable-patched/src/lib-storage/mail-storage.h Wed Jul 27 08:07:25 2005 --- dovecot-1.0-stable/src/lib-storage/mail-storage.h Mon Jan 31 17:37:55 2005 *************** *** 225,227 **** /* Deinitialize mailbox list request. Returns FALSE if some error ! occurred while listing. */ int mail_storage_mailbox_list_deinit(struct mailbox_list_context *ctx); --- 225,227 ---- /* Deinitialize mailbox list request. Returns FALSE if some error ! occured while listing. */ int mail_storage_mailbox_list_deinit(struct mailbox_list_context *ctx); *************** *** 239,241 **** ! /* Returns the error message of last occurred error. */ const char *mail_storage_get_last_error(struct mail_storage *storage, --- 239,241 ---- ! /* Returns the error message of last occured error. */ const char *mail_storage_get_last_error(struct mail_storage *storage, *************** *** 252,254 **** const char *name, enum mailbox_open_flags flags); ! /* Close the box. Returns FALSE if some cleanup errors occurred, but the mailbox was closed anyway. */ --- 252,254 ---- const char *name, enum mailbox_open_flags flags); ! /* Close the box. Returns FALSE if some cleanup errors occured, but the mailbox was closed anyway. */ *************** *** 373,378 **** /* Get the time message was received (IMAP INTERNALDATE). ! Returns (time_t)-1 if error occurred. */ time_t (*get_received_date)(struct mail *mail); /* Get the Date-header in mail. Timezone is in minutes. ! Returns (time_t)-1 if error occurred, 0 if field wasn't found or couldn't be parsed. */ --- 373,378 ---- /* Get the time message was received (IMAP INTERNALDATE). ! Returns (time_t)-1 if error occured. */ time_t (*get_received_date)(struct mail *mail); /* Get the Date-header in mail. Timezone is in minutes. ! Returns (time_t)-1 if error occured, 0 if field wasn't found or couldn't be parsed. */ *************** *** 380,385 **** /* Get the full virtual size of mail (IMAP RFC822.SIZE). ! Returns (uoff_t)-1 if error occurred */ uoff_t (*get_virtual_size)(struct mail *mail); /* Get the full physical size of mail. ! Returns (uoff_t)-1 if error occurred */ uoff_t (*get_physical_size)(struct mail *mail); --- 380,385 ---- /* Get the full virtual size of mail (IMAP RFC822.SIZE). ! Returns (uoff_t)-1 if error occured */ uoff_t (*get_virtual_size)(struct mail *mail); /* Get the full physical size of mail. ! Returns (uoff_t)-1 if error occured */ uoff_t (*get_physical_size)(struct mail *mail); diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/subscription-file/subscription-file.h dovecot-1.0-stable/src/lib-storage/subscription-file/subscription-file.h *** dovecot-1.0-stable-patched/src/lib-storage/subscription-file/subscription-file.h Wed Jul 27 08:08:08 2005 --- dovecot-1.0-stable/src/lib-storage/subscription-file/subscription-file.h Mon Jan 31 17:37:55 2005 *************** *** 9,11 **** ! /* Deinitialize subscription file listing. Returns FALSE if some error occurred while listing. */ --- 9,11 ---- ! /* Deinitialize subscription file listing. Returns FALSE if some error occured while listing. */ diff -r -c1 dovecot-1.0-stable-patched/src/login-common/ssl-proxy-gnutls.c dovecot-1.0-stable/src/login-common/ssl-proxy-gnutls.c *** dovecot-1.0-stable-patched/src/login-common/ssl-proxy-gnutls.c Wed Jul 27 08:08:22 2005 --- dovecot-1.0-stable/src/login-common/ssl-proxy-gnutls.c Mon Jan 31 17:37:55 2005 *************** *** 82,84 **** if (verbose_ssl) { ! /* fatal error occurred */ if (error == GNUTLS_E_FATAL_ALERT_RECEIVED) { --- 82,84 ---- if (verbose_ssl) { ! /* fatal error occured */ if (error == GNUTLS_E_FATAL_ALERT_RECEIVED) { diff -r -c1 dovecot-1.0-stable-patched/src/login-common/ssl-proxy.h dovecot-1.0-stable/src/login-common/ssl-proxy.h *** dovecot-1.0-stable-patched/src/login-common/ssl-proxy.h Wed Jul 27 08:08:14 2005 --- dovecot-1.0-stable/src/login-common/ssl-proxy.h Mon Jan 31 17:37:55 2005 *************** *** 9,11 **** /* establish SSL connection with the given fd, returns a new fd which you ! must use from now on, or -1 if error occurred. Unless -1 is returned, the given fd must be simply forgotten. */ --- 9,11 ---- /* establish SSL connection with the given fd, returns a new fd which you ! must use from now on, or -1 if error occured. Unless -1 is returned, the given fd must be simply forgotten. */

12 19

[Dovecot] Thunderbird got "Mail Server does not support secure authentication" ???
by Adrian Mak 23 Aug '05

23 Aug '05

System: Redhat AS3 postfix 2.2.5 cyrus-sasl 2.1.15 pam-mysql 0.6 dovecot 0.99.14 ( compile from source tarball) The same email account and machine, using thunderbird 1.06 to get email thru dovecot pop3, it returned "Mail Server does not support secure authentication" But in outlook express , there is no such problem I have tested SASL thru pam-mysql is work properly before install dovecot Below is my dovecot.conf /etc/dovecot.conf base_dir = /var/run/dovecot/ protocols = imap pop3 imap_listen = * pop3_listen = * ssl_disable = yes login = imap login = pop3 login_dir = /var/run/dovecot-login login_executable = /usr/local/libexec/dovecot/imap-login login_executable = /usr/local/libexec/dovecot/pop3-login imap_executable = /usr/local/libexec/dovecot/imap pop3_executable = /usr/local/libexec/dovecot/pop3 disable_plaintext_auth = no login_user = dovecot first_valid_uid = 1000 last_valid_uid = 1000 valid_chroot_dirs = /var/spool/virtual default_mail_env = /var/spool/virtual/%u auth = default auth_mechanisms = plain auth_userdb = mysql /etc/dovecot/mysql.conf auth_passdb = mysql /etc/dovecot/mysql.conf auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_user = dovecot-auth /etc/dovecot/mysql.conf db_host = localhost db_port = 3306 db_unix_socket = /tmp/mysql.sock db = postfix db_user = postfixuser db_passwd = userpostfix db_client_flags = 0 password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 1000 AS uid, 1000 AS gid FROM mailbox WHERE username = '%u'

2 1

[Dovecot] Problem with AUTH causes serverside lockup
by Tom Sommer 23 Aug '05

23 Aug '05

Hello all, I am running Dovecot alpha1, and after about 24 hours of the server working fine, it starts to lock up when I open Thunderbird to check mail. Basically I can see new mail, but when I click it, it just hangs at "Loading message...". I get the following in my maillog: Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: CONT 1 [BASE64 SUM] Aug 23 09:25:28 palantir last message repeated 2 times Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: CONT 1 [BASE64 SUM] And then it just hangs untill it finally says Aug 23 09:26:17 palantir dovecot: imap-login: Disconnected: Inactivity: method=plain, rip=80.197.147.147, lip=194.192.14.150 When I do: # killall dovecot # dovecot (restarting dovecot) then it works fine again. -- Tom Sommer

1 1

[Dovecot] Wiki of dovecot.conf file
by Marc Perkel 23 Aug '05

23 Aug '05

I made yet another new wiki page documenting the mail configuration file. Looks really nice. We can all start working on improving the docs in this file and eventually merge the docs here back into the example config file. http://wiki.dovecot.org/moin.cgi/MainConfig -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

[Dovecot] Segfault in imap
by Todd Burroughs 23 Aug '05

23 Aug '05

Found a new segfault in imap. The first log entry always happens on my mailbox, but doesn't seem to affect anything. This is CVS version from Aug. 15. dovecot: Aug 21 17:16:56 Error: 28017 IMAP(todd): Corrupted index cache file /mailhome/new/t/b/todd/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Aug 21 17:19:44 Error: child 28017 (imap) killed with signal 11 (gdb) bt full #0 0x08076b50 in index_mail_get_flags (_mail=0x80cbd20) at index-mail.c:152 data = (struct index_mail_data *) 0x80cbd84 #1 0x0808eb4d in mail_get_flags (mail=0xb7de7088) at mail.c:32 No locals. #2 0x0805a9d5 in fetch_flags (ctx=0x80c1ed0, mail=0x80cbd20, context=0x0) at imap-fetch.c:445 flags = Variable "flags" is not available. (gdb) bt #0 0x08076b50 in index_mail_get_flags (_mail=0x80cbd20) at index-mail.c:152 #1 0x0808eb4d in mail_get_flags (mail=0xb7de7088) at mail.c:32 #2 0x0805a9d5 in fetch_flags (ctx=0x80c1ed0, mail=0x80cbd20, context=0x0) at imap-fetch.c:445 #3 0x0805af0c in imap_fetch (ctx=0x80c1ed0) at imap-fetch.c:265 #4 0x0805693b in cmd_fetch (cmd=0x80bfba8) at cmd-fetch.c:166 #5 0x0805999b in _client_input (context=0x80bfb68) at client.c:334 #6 0x080a045a in io_loop_handler_run (ioloop=0x80be9b0) at ioloop-poll.c:184 #7 0x0809f9d9 in io_loop_run (ioloop=0x80be9b0) at ioloop.c:230 #8 0x08060877 in main (argc=1, argv=0xbffffa44, envp=0xbffffa4c) at main.c:229 (gdb) p *data $1 = {flags = 0, date = 0, received_date = 1124608407, virtual_size = 2870, physical_size = 2856, sent_date = {time = -1, timezone = 0}, parse_line = { field_idx = 0, start_pos = 0, end_pos = 0, line_num = 0, cache = 0}, parse_line_num = 0, parts = 0x0, envelope = 0x0, body = 0x0, bodystructure = 0x0, uid_string = 0x0, envelope_data = 0x0, seq = 11473, rec = 0xb7de7088, cache_flags = 0, access_part = 3, stream = 0x80cc224, filter_stream = 0x0, hdr_size = {physical_size = 2545, virtual_size = 2545, lines = 57}, body_size = {physical_size = 311, virtual_size = 325, lines = 14}, parser_ctx = 0x0, parsing_count = 0, keywords = { buffer = 0x0, element_size = 0}, all_cache_fields = 0x0, all_cache_fields_count = 0, save_sent_date = 0, save_envelope = 0, save_bodystructure_header = 0, save_bodystructure_body = 0, parsed_bodystructure = 0, hdr_size_set = 1, body_size_set = 1, messageparts_saved_to_cache = 0} (gdb) p *data->rec Cannot access memory at address 0xb7de7088

1 0

[Dovecot] pop-before-smtp in SQL?
by Lorens 23 Aug '05

23 Aug '05

I need pop-before-smtp (let's not discuss the advisability of the method), but I'm annoyed at the inefficiency of the classical perl script that parses the logs. A long time ago I modified the perl to add the tuple (IP, time) to an SQL table that the MTA looks at, and to clean up periodically. I found that this was the best way to deal with multiple servers that have to share an SQL database anyway. Wouldn't it be quite trivial to make dovecot write to an SQL table upon sucessful login, instead of all this log file parsing by an additional daemon?

2 4

[Dovecot] Poprelayd released for Dovecot
by dan1 22 Aug '05

22 Aug '05

Hello all. I just wanted to tell you that poprelayd is now compatible with Dovecot. I have just created a parser for the Dovecot server. This might be interesting either for you or your future customers. Maybe you will want to make some advertisement for it ? I remind that poprelayd is a service that allows a POP user to use the SMTP server of the same machine to send e-mails (making relays) for 15 minutes long after the pop login. This comes very handy for people wanting to send e-mails through their servers and also for a larger use. If you could try it that would also give some interesting feedbacks. This is the link: http://sourceforge.net/forum/forum.php?thread_id=1338704&forum_id=21494 BTW, I would need something from you: The POP login information that we can find for Dovecot in the /var/log/maillog is [::ffff:IP_ADDRESS]. Here is an example: Aug 19 23:23:02 anoigo pop3-login: Login: john [::ffff:82.208.12.243] Will this be kept the same all the time or is this ffff value a variable ? Will it be kept like this all the life of Dovecot ? Also, I would need to know if the 'pop3-login' and 'Login:' information there will also be kept. Thanks. Regards, Daniel

3 2

[Dovecot] dovecot-lda user quota
by Renzetti Federico 22 Aug '05

22 Aug '05

Sorry again people! Now my trouble is: /Your message was automatically rejected by Sieve, a mail filtering language. The following reason was given: Internal quota calculation error/ Any ideas? THK.

1 0

[Dovecot] Re: Dovecot inotify problem
by Johannes Berg 22 Aug '05

22 Aug '05

Hi Reuben, I hope you don't mind me copying the dovecot list again. > dovecot: Aug 21 04:08:22 Error: IMAP(reuben): inotify_rm_watch() failed: > Invalid argument Odd. > This is with a 2.6.13-rc6-mm1 release. I've posted to LKML because there is > also a kernel stack produced at one point which looks inotify related (but the > messages above are contant). > See http://www.ussg.iu.edu/hypermail/linux/kernel/0508.2/1180.html and the > followup from akpm. Thanks for the link. I don't think akpm is right, unless something is really odd here. Could you add debugging output for me please? Maybe something like (this is not a patch you can apply, look at line 164 in src/lib/ioloop-notify-inotify.c) ctx->inotify_fd = inotify_init(); + i_warning("inotify_init returned fd %d", ctx->inotify_fd); if (ctx->inotify_fd == -1) { and line 106: IN_CLOSE | IN_MODIFY); + i_warning("inotify_add_watch returned %d", watchdescriptor); if (watchdescriptor < 0) { and line 145: } + inotify_rm_watch("removing wd %d from inotify fd %d", io->notify_context, ctx->inotify_fd); if (inotify_rm_watch(ctx->inotify_fd, io->notify_context) < 0) Or something similar. If that doesn't help and output looks consistent (we're not removing a watch descriptor from a wrong fd etc.), can you try removing the fd_close_on_exec call please (line 171)? I don't know if that could cause trouble (I don't even think that the imap binary ever forks) but you never know. johannes

2 4

[Dovecot] Created Testimonials Page in wiki
by Marc Perkel 22 Aug '05

22 Aug '05

I created a testimonials page. Feel free to add to this. http://wiki.dovecot.org/moin.cgi/Testimonials -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

6 7

Dovecot IDLE problem (was Re: [Dovecot] inotify support in dovecot)
by Reuben Farrelly 22 Aug '05

22 Aug '05

Hi, I've come across some possibly buggy behaviour with regards to Dovecot and the use of the IDLE keyword. Found this while testing out inotify support for Johannes - although after asking him and him reproducing it, he is of the opinion that it's not a inotify specific problem. The behaviour is that when the client is idling, Dovecot seems to only alert to the first new message received, and if a subsequent new message comes in before the client finishes idling, that second new message is not notified to the connected client. To reproduce: $ maildirmake /tmp/imap-test $ cat >/tmp/1 <<EOF From: test To: test Subject: test test! <Ctrl-D> $ MAIL=Maildir:/tmp/imap-test /usr/libexec/dovecot/imap ... A SELECT INBOX B IDLE [now, in a different terminal, copy /tmp/1 to /tmp/imap-test/new, you should instantly be notified of it in your imap session] ** Dovecot correctly responds with: * 1 EXISTS * 1 RECENT [if a second message is delivered, eg by copying /tmp/1 to /tmp/imap-test/new/2 then you should be notified as well, but this never occurs] DONE C LOGOUT $ Timo - what do you think? Reuben

4 5

[Dovecot] Dovecot Feature List
by Marc Perkel 21 Aug '05

21 Aug '05

I've added a new page to the Wiki that's sort of a Dovecot feature list overview. What I have is a good start but if anyone wants to jump in and contribute, go for it. I added it because there isn't any other place I saw that gives new people an overview of what Dovecot does. I personally passed Dovecot over a few times before somone pointed me back to it. http://wiki.dovecot.org/moin.cgi/DovecotFeatures Just my way of giving something back to the Dovecot community. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

[Dovecot] Failed authentication to a mysql database
by Alexandru Craiu 21 Aug '05

21 Aug '05

Hi, I use devecot-1.0.alpha1 and I can't connect to mysql when user have password. If user don't have password I can connect to mysql server. Aug 21 08:28:30 ca dovecot: Dovecot v1.0.alpha1 starting up Aug 21 08:28:32 ca dovecot: auth-worker(default): mysql: Connect failed to localhost (syscp): Access denied for user 'syscp'@'localhost' (using password: YES) - waiting for 1 seconds before retry I have a system and with ssh access. Best regards, Alexandru Craiu ________ Information from NOD32 ________ This message was checked by NOD32 Antivirus System for Linux Mail Server. part000.txt - is OK http://www.nod32.com

2 1

[Dovecot] Dovecot Problem
by Rob Kettle 21 Aug '05

21 Aug '05

Hi, is there a way to get Dovecot to output a Logout line that includes the IP address that has logged out please ? This would make it a lot easier to use with pop-before-smtp. Thanks Rob -- This message has been scanned for viruses and other dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] Sieve Documentation
by Marc Perkel 20 Aug '05

20 Aug '05

Where do I find the docs on Dovecot Sieve and is there a global sieve config file that I can configure for everyone?

2 1

[Dovecot] 1.0 alpha1 and postfix dovecot auth
by Kevin 19 Aug '05

19 Aug '05

Does the postfix-2.2.1-dovecot-auth patch not work with 1.0alpha1? I was using the stable branch and it was working fine. Tried out 1.0alpha1 and now when I connect to postfix it logs this error. Aug 19 11:25:19 redefine postfix/smtpd[17343]: fatal: SASL: connect failed: No such file or directory I've tried with postfix-2.2.4 and 2.2.5. Right now I'm using auth default but I also tried auth default_with_listener. Anybody else using this patch seeing this?

1 0

Re: [Dovecot] lock file
by Obantec Support 19 Aug '05

19 Aug '05

----- Original Message ----- From: "Simon Waters" <simonw(a)zynet.net> To: "Obantec Support" <support(a)obantec.net> Sent: Thursday, August 18, 2005 12:33 PM Subject: Re: [Dovecot] lock file > On Thursday 18 Aug 2005 12:19 pm, Obantec Support wrote: <snip> > > What is your question? > > Yes it is a lock file, by default (if you must use mbox) Dovecot overrides > them in 30s I believe. > > Either work out if it is genuine, and delete it if not. > > You only need to use dotlock locking if you are using NFS (or similar), and > using "mbox". Hopefully this only affects a small number of big mail servers, > and most of them would presumably switch to maildir when deploying dovecot > over NFS anyway. > > Hi not using NFS. my question is what is it, why is it happening and how do i get my users mbox working again. as soon as i delete it it comes back with 1B contents 0 Mark

2 2

[Dovecot] test80: assert/core debug info
by Jeff A. Earickson 19 Aug '05

19 Aug '05

Timo, Attached is gdb information from core dumps related to the following assert in test-80: IMAP(username): file mbox-sync-update.c: line 442 (mbox_sync_update_header_from): assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid_broken || ctx->mail.uid == mail->uid) My setup: Solaris 9, mbox format. test-80 compiled with gcc 4.0.1 using the following configure options: CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.test80 --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug Note that system mailboxes are NFS mounted from the mail server to the IMAP server, which may cause you to groan. The attached debug session was done with gdb 6.3, also compiled with gcc 4.0.1. Note that some of the variables I queried were undefined (or otherwise unknown to gdb). The variable "first_nonexpunged" at line 470 of mbox-sync-rewrite.c is undefined, and I wondered why it was scoped so locally. The value of mails[idx] being undefined at mbox-sync-rewrite.c:353 also seems like bad news. Hope this helps. Jeff Earickson Colby College

3 6

[Dovecot] auth-master socket creation problem?
by Marc Perkel 19 Aug '05

19 Aug '05

I tried activating this code in the example config file and it failed to create the socket. You might want to look inti this. Running alpha1. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 1

[Dovecot] Lost transaction log file
by Brent Clark 19 Aug '05

19 Aug '05

Hi list I seem to be getting quite a bit of this type of messages in my syslog. Aug 19 09:14:45 mail dovecot: IMAP(bclark): Lost transaction log file /home/bclark/Maildir/dovecot.index.log seq 4 Aug 19 09:14:45 mail dovecot: IMAP(bclark): Lost transaction log file /home/bclark/Maildir/dovecot.index.log seq 4 Would anyone know how I can go about fixing / understanding this. Any tips / advice would greatfully be appreciated. Kind Regards Brent Clark

2 3

[Dovecot] ( Dovecot + Postfix + MySQL + Postfixadmin )
by Pratchaya Chatuphian 19 Aug '05

19 Aug '05

( Dovecot + Postfix + MySQL + Postfixadmin + Spamassassin + Clamav + Amavisd-new ) I need help and sample how to. Anyone can help me sir ? Thank you for advance . Pratchaya

2 1

[Dovecot] compiling dovecot-lda from cvs
by Jakob Hirsch 19 Aug '05

19 Aug '05

current dovecot-lda fails to compile: deliver.c: In function 'main': deliver.c:543: error: 'script_path' undeclared (first use in this function) deliver.c:543: error: (Each undeclared identifier is reported only once deliver.c:543: error: for each function it appears in.) deliver.c:544: warning: implicit declaration of function 'stat' deliver.c:544: error: 'st' undeclared (first use in this function) make[3]: *** [deliver.o] Error 1

2 1

[Dovecot] logging beg - again
by Peter Gervai 19 Aug '05

19 Aug '05

Hello, [Old problem; if it was fixed, I cannot see it (checked Changelog, wiki, source, as much as my grepping counts). Any help appreciated.] I have been begging since 2003 to be able to trash qpopper and use dovecot, but statistical logging of dovecot has been pretty much absent. Qpopper does this: Aug 19 11:18:02 mail in.qpopper[8099]: Stats: userid 0 0 12 51773 user.example.com 193.291.612.5 [pop_updt.c:296] Which provides us with user id, user host and ip, which is fine with dovecot. Provides furthermore unread mail count and bytes, and read but undeleted mail count and bytes. This is essential to handle low-IQ user problems basically coming down to "WE CANNOT USE EMAIL FIX IT". This topic was touched several times: http://www.google.com/search?q=site:dovecot.org+logging&hl=en&lr=&start=0&s… including my original question at http://dovecot.org/list/dovecot/2003-October/002514.html someone even dropped in a patch http://dovecot.org/pipermail/dovecot/2003-June/001618.html which seem to have disappeared in the flow of time. Probably is a member of the TODO list since then, but I cannot find the exact spot. Some comments from Timo was dropped at http://dovecot.org/pipermail/dovecot/2003-May/001545.html http://dovecot.org/pipermail/dovecot/2003-September/002277.html (and reply http://dovecot.org/pipermail/dovecot/2003-September/002281.html ) http://dovecot.org/pipermail/dovecot/2003-November/002524.html So, is there any possibility to log the entry and exit statistics of a session, regarding the amount of mail? Thanks, Peter

2 1

[Dovecot] Multiple folders/fetchmail
by Andreas Jung 19 Aug '05

19 Aug '05

Hi, my emails are processed using procmail and stored the following way: /home/ajung/Maildir/new|cur|tmp /home/ajung/Maildir/Plone|new|cur|tmp /home/ajung/Maildir/Python|new|cur|tmp When I fetch my mail using fetchmail I can only get the mails from "Maildir". However I can not access other folders like "Plone" or "Python" (using fetchmail -r Plone). I tried to tweak mail_default_env but without access. So any ideas how to configure dovecot the way I need it? Thanks in advance, Andreas

2 1

[Dovecot] 1.0alpha1, multiple lock methods?
by Jeff A. Earickson 18 Aug '05

18 Aug '05

Hi, I just upgraded from test80 to 1.0alpha1. I wanted to try something new on the lock_method, so I set: lock_method = fcntl, dotlock I got syslog complaints like: IMAP(username): Unknown lock_method: fcntl, dotlock Can one specify multiple file locking mechanisms? If so, what is the syntax (and can the syntax be shown in the comments of the .conf file)? Jeff Earickson Colby College

2 1

[Dovecot] 1.0 alpha1 released
by Timo Sirainen 18 Aug '05

18 Aug '05

As promised a few days ago, 1.0.alpha1 release is now available from Dovecot web page. Changes since 1.0-test80 include only one mbox assert crashfix and removed fsync() call when writing to transaction log, making it a bit faster. I changed the version number also since 1.0-tests to 1.0.alpha. I know '-' is problematic to binary package builders, maybe the new versioning is better?

4 5

[Dovecot] Discussion of new sending protocol proposal for IMAP
by Marc Perkel 18 Aug '05

18 Aug '05

Timo, I joined the lemonade list for the new IMAP sending protocol and I mage the following suggestion about using IMAP as a front end for SMTP. The idea would be that a client could authenticate to IMAP, then ask for a tunnel to the SMTP server. - Here's my message. I thought I'd get people thinking. --------------------- OK thanks. I would clarify what I'm proposing. I looked at the current proposal and what I'm proposing might be in addition to rather than instead of the current proposal. LDELIVER as it is now offers capabilities of sending messages and forwarding attachments without downloading them, leaving more power on the server side. This is important for mobile clients with limited power on the client end. What I'm suggesting is something in addition to LDELIVER where we add SMTP-TUNNEL as a capability. This is for laptop users who have to deal with finding an outgoing smpt server and who might be behind a firewall that blocks smtp ports. What is different about my proposal is that what I'm suggesting isn't a straight pass through at the beginning. The client has to talk to IMAP, then authenticate, and then upon successfil authentication would ask for an SMTP connection to the local smtp server. At that point it is a tunneled connection. 1) This allows the IMAP ports to be used for SMTP and avoid port blocking. 2) It uses the same IMAP authentication for SMTP so outgoing SMTP nee not be configured separately. It merely acts as an authenticated condiut to get to SMTP. 3) It would in no way interfere with future advancements in SMTP technology at others were concerned about. 4) Client and server recoding would be trivial. 5) This could be used in place of SMTP-AUTH and would eliminate the need for authenticated SMTP making server smtp configuration easier. So - if you look at it as an addition then you don't have to choose between them. Stephane Maes wrote: > Marc, > > Based on the suggestions that we have received so far, we will publish > a proposed update. We are looking at smtp proxy options. > > Note that LDELIVER contributes also in supporting server side > recomposition with upload of only body / header part diffs. I am not > sure that tunneling would allow this. But I am looking into it. > > Thanks > > Stephane > > PS I still have an action item to provide the use cases / reasons / > pros of using it. I will distribute soon on the list. > _____ > Stephane H. Maes, PhD, > Director of Architecture - RTCC & Mobile, Oracle Corporation. > Ph: +1-203-300-7786 (mobile/SMS); Fax / UM: +1-650-607-6296. > e-mail: stephane.maes(a)oracle.com > IM: shmaes (AIM, Y!,Skype) or stephane_maes(a)hotmail.com (MSN Messenger) > -----Original Message----- > From: lemonade-bounces(a)ietf.org <lemonade-bounces(a)ietf.org> > To: lemonade(a)ietf.org <lemonade(a)ietf.org> > Sent: Thu Aug 18 08:41:10 2005 > Subject: [lemonade] Outside the box suggestion about Lemonade > > Hello, > > I'm Marc Perkel - and I'm new to this list. I run a span filtering > service called junkemailfiltercom and do some web hosting. > > I've read sme of the discussion about LDELIVER and I just wanted to > throw out a wild idea and see where it goes. > > The Problem: Sending email without having to separately config > outgoing SMTP so that an IMAP connection can be used especially by > moble users to send email. > > So - suppose that instead of adding something complex - why not just > establish a tunnel to SMTP over IMAP? > > Here's what I propose. The client when sending email would establish a > second IMAP connection to the server. One of the CAPABILITIES will be > SMTP-TUNNEL. After sending the command the IMAP server opens a > connection to the SMTP server and acts as a straight pipe through > until the connection is closed. > > The advantage of this is that you can take your existing SMTP code and > instead of connecting it on port 25 you connect it on port 143. Then > everything you could do with SMTP is available. You would just need to > add a smal layer to the SMTP layer to authenticate to the IMAP server > and tell it to open a tunnel to the SMTP server. On the server side > you just connect to localhost:25 or whatever you configure it to and > pass data. > > Basically what I'm suggesting is that IMAP act as a tunnel to SMTP > providing and authenticated connection using the same credentials as > the imap client uses. > > Unless I'm missing something - and I might be - seems to me this would > be dirt simple to implement and wouldn't impose any of the limitations > to the SMTP protocol that other people here are concerned about. > > Who likes this idea? > > > _______________________________________________ > lemonade mailing list > lemonade(a)ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > > > > > > -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com _______________________________________________ lemonade mailing list lemonade(a)ietf.org https://www1.ietf.org/mailman/listinfo/lemonade

1 0