- dovecot - dovecot.org

[Dovecot] %d interpolation problem fixed
by William Ross 22 Jan '06

22 Jan '06

On 6 Dec 2005, at 17:21, Timo Sirainen wrote: > On Tue, 2005-12-06 at 17:11 +0000, William Ross wrote: >> On 6 Dec 2005, at 16:51, Timo Sirainen wrote: >> >>> On Fri, 2005-10-28 at 17:52 +0200, Riccardo Bini wrote: >>>>> I just wrote this: http://wiki.dovecot.org/Quota >>>> Well... but you have to correct %n with vpopmail backend. %u in the >>>> default_mail_env (like in the log) is always the user name without >>>> the >>>> domain.... >>> >>> That's a bug in Dovecot's vpopmail code. I don't know why it doesn't >>> work. Would be nice if someone using vpopmail fixed that.. >> >> point me in the right direction and I'll have a go. > > src/auth/passdb-vpopmail.c > > If user logs in as user@domain, then they both should be in > request->user string. %d is taken from there. I don't see request- > >user > being modified in that file either, so I think it should have worked.. I finally got round to working on this. I'm a perl programmer, and it has all been very educational, so please bear with me :) I was stuck because the domain name was not interpolated into the Maildir path[0], when using the configuration recommended here: http://wiki.dovecot.org/ QuestionsAndAnswers#head-153aa253aff40951a05cf238da4245b1cc1a4665 It turns out that the answer is really simple. You don't need to supply a default_mail_env parameter with vpopmail and dovecot v1.x. Indeed, you shouldn't: the path to the maildir is retrieved from vpopmail and if you specify default_mail_env then it will be used in place of that correct value. Also, it will be used wrongly, as there is also an interpolation bug, and %d isn't replaced correctly. The code in passdb-vpopmail and userdb-vpopmail works perfectly, by the way: the login email address[1] is parsed correctly, the vpopmail hookup is correct, and the vqpasswd struct that is returned by vpopmail_lookup_vqp contains all the right values. eg (these are debugging-for-dummies lines that I've scattered everywhere): > dovecot: Jan 17 22:51:42 Info: auth(default): * > vpopmail_verify_plain: now vpop_user = sysadmin, vpop_domain = > spanner.org, request->user = sysadmin(a)spanner.org, vpw->pw_dir = / > home/vpopmail/domains/spanner.org/sysadmin in the callback method I got this tab-separated auth_reply_stream: > dovecot: Jan 18 00:30:01 Info: auth(default): userdb_callback str: > USER 2 sysadmin uid=7797 gid=2109 home=/home/ > vpopmail/domains/spanner.org/sysadmin but I still saw these lines later: > dovecot: Jan 18 01:31:46 Info: imap(sysadmin): maildir: root=/home/ > vpopmail/domains//sysadmin/Maildir, index=/home/vpopmail/domains// > sysadmin/Maildir, control=, inbox= I became suspicious, and tested with nonsense values in default_mail_env: sure enough i got the same thing. During the userdb stage we have the correct path to the maildir, but later on we see a different value derived from the nonsense configuration I've just entered. I guess that we're getting the initial value from vpopmail and try the same thing but with no default_mail_env entry at all. It works perfectly. I say some new words I have learned from my wife. I don't know where the failure lies, but I can tell you that the 'user' value passed to get_var_expand_table (which comes from getenv ("USER")) contains only the first part of the email address. That's probably not the intention, because get_var_expand_table then tries to split it on @. As it happens the home-directory value is passed to get_var_expand_table as the expansion for %h, so this works too, in a completely redundant way: default_mail_env = maildir:%h I've tested this with an new tarball of 1.0.beta1 and it works fine - with the configuration change - so if this all sounds sane to you then I'll update the wiki. best, will [0] under vpopmail the maildir for the address brian(a)domain.com usually lives somewhere like: /home/vpopmail/domains/domain.com/brian/, [1] in order to disambiguate usernames, vpopmail has you log in with your full email address as the user id. dovecot would therefore need to split the email address and interpolate the fragments into the maildir path to get to the right place. however, the vpopmail password file also specifies the maildir for each user, which i guess is what dovecot is using now.

2 5

[Dovecot] new configure-option --disable-index
by Marten Lehmann 22 Jan '06

22 Jan '06

Hello, I experimented with dovecot the whole evening yesterday and the mailserver worked fine since there haven't been that much users connecting to it. I'm using dovecot 1.0.alpha5 as pop3 and pop3s server. The maildirs are mounted through NFS and since there is no nfslockd running I disabled mmap in the config and told dovecot to use dotlock. Also I experienced, that dovecot was much faster when using one login-process per connection instead of sharing them throughout several connections. Sharings seems to be a greater performance problem (bottleneck) than additional fork()s. However, under normal load at business time the server load increased to a value that made it impossible to download emails without timeouts, so we switched back to tcpserver/qmail-pop3d for pop3 and only kept dovecot for doing the pop3s part. Dovecot is really fine, but it still isn't NFS ready. Especially when using dovecot as pop3 only this index-stuff must be disengageable. What is the use of generating a complex index file for hundreds of messages, that will be deleted in the next step after downloading them? But the index is also a problem when using IMAP over NFS. Access to the files is too slow, so the connections keep hanging around and the i/o waiting value is raised to a maximum which slows down the whole machine. It simply doesn't make sense to build and update an index every time the maildir is accessed (which is very cpu and timeconsuming), while search operations (the only moment when the index is actually used and not just heavily updated) don't affect even 1% of all IMAP calls (and such a command doesn't even exist for pop3). I would be much obliged if you could create an option called "--disable-index" in the configure-script or something like "disable-index = yes" in dovecot.conf that makes dovecot ignoring existing index files and doesn't care for related operations, so NFS should work much faster and IMAP search would simply parse the files directly instead of looking in the index. I would really appriciate this very much and I'm absolutely sure, that a lot of people beside me are waiting for this. Regards Marten

7 22

[Dovecot] core files
by jared 22 Jan '06

22 Jan '06

Hey all: Was playing around with kill -11 on dovecot processes to see which ones would dump core and which ones wouldn't. If ulimit is correct dovecot and dovecot-auth will dump. If you perform the recommended (Set mail_drop_priv_before_exec = yes in config file) step, imap will also dump core. But I'm unable to force imap-login to dump core. I'm curious if this is possible without the linux kernel patch that's recommended on http://dovecot.org/bugreport.html. (BTW tried the patch on my 2.4.18 kernel but the patch had all kinds of errors.) Thanks, Jared DeMott

2 1

[Dovecot] Assertation failed when trying to login twice in one session
by Steffen Kaiser 22 Jan '06

22 Jan '06

Hello, this command: echo "user testu pass q" ; sleep 5; echo "user testu pass test quit" | nc localhost pop3 results in this assert: dovecot: Jan 20 10:16:09 Error: auth(default_with_listener): file auth-client-connection.c: line 33 (auth_client_send): assertion failed: (conn->refcount > 1) dovecot: Jan 20 10:16:09 Error: child 18656 (auth) killed with signal 6 without listener: dovecot: Jan 20 10:24:07 Error: auth(default): file auth-client-connection.c: line 33 (auth_client_send): assertion failed: (conn->refcount > 1) dovecot: Jan 20 10:24:07 Error: child 18733 (auth) killed with signal 6 The password of user 'testu' is 'test' :) The same with IMAP: 1 login q q 1 NO Authentication failed. 2 login testu test 2 OK Logged in. 3 SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1137748810] UIDs valid * OK [UIDNEXT 1] Predicted next UID 3 OK [READ-WRITE] Select completed. The connection is OK, though. dovecot: Jan 20 10:19:26 Info: imap(testu): maildir: root=/home/testu/MailDir, index=, control=/var/spool/dovecot/30001, inbox= dovecot: Jan 20 10:19:27 Error: auth(default): file auth-client-connection.c: line 33 (auth_client_send): assertion failed: (conn->refcount > 1) dovecot: Jan 20 10:19:27 Error: child 18710 (auth) killed with signal 6 Bye, -- Steffen Kaiser

2 2

[Dovecot] dovecot 1.0beta1 making base_dir world-writable
by Brad 22 Jan '06

22 Jan '06

I can also confirm this, on my own mail server since upgrading to beta1. Dovecot always makes the base_dir world-writable on startup. ----- Forwarded message from Oleg Safiullin <form(a)pdp-11.org.ru> ----- Date: Fri, 20 Jan 2006 07:09:17 +0600 From: Oleg Safiullin <form(a)pdp-11.org.ru> To: brad(a)openbsd.org Subject: dovecot 1.0beta1 Hi. After update dovecot to 1.0beta1 some strange thing happens -- during startup it says "fixing permissions for /var/dovecot to make it world-readable", but actually it makes it world-writable. Please look at it. WBR //form ----- End forwarded message -----

2 1

[Dovecot] Simultaneous POP login - inbox corrumption
by John Woodell 22 Jan '06

22 Jan '06

When two POP clients connect to the same account, within a second or two, the inbox can get corrumpted. Here is a sample of the first few lines of the corrumpted inboxes... # 1-- # # # From... # # > # # From.. # 4504 # # From... # 7-- # # # From... # 4504 # # From... # # > # # From... # 868-- # # From...

2 1

[Dovecot] 1.0 beta 1 feature request: passwd-file vs. prefetch
by Matthias Andree 22 Jan '06

22 Jan '06

Greetings, it appears as though 1.0.beta1 doesn't support "userdb prefetch {}" with "passdb passwd-file { arg=/etc/mailpasswd }" even if the latter contains all necessary information. Is this planned for a future version or would the benefits be too small to justify that? Another idea: can userdb prefetch {} fall back to retrying the passdb entries to see if they come up with useful information? -- Matthias Andree

2 3

[Dovecot] Mail.app message numbering for deleted messages
by jcn-dovecot＠pith.org 22 Jan '06

22 Jan '06

I'm having a strange problem that appeared when I upgraded from .99something to 1.0alpha3 and then disappeared for a while and then re-appeared when I upgraded to 1.0alpha5. I am using mbox and IMAP in Apple's Mail.app to read my mail. When I delete a message in Mail.app, the message gets marked as deleted in the spool and it disappears from the mail listing in Mail. However, the message number does not change until I either manually flush the deleted messages through mail, or I go offline which deletes the messages from the spool. I have mbox_lazy_writes set to 'no' but this didn't seem to have any effect on the behavior. I never saw this type of behavior with UW-IMAP either, which is what I migrated from. Thanks.

2 1

[Dovecot] can I hide or delete the message "don't delete this message -- folder internal data" ?
by Felipe Stuardo 22 Jan '06

22 Jan '06

sorry for my english... is possible that i can hide or delete the message "don't delete this message -- folder internal data" ? this message is see from all accounts of my mail server. i have a system with: Fedora Core 4 dovecot-0.99.14-4.fc4 sendmail-8.13.4-2 thanks _______________________________________________________________________ Advertencia: Este mensaje contiene la opinion personal del remitente y la Universidad Catolica Nuestra Senora de la Asuncion no asume responsabilidad alguna con relacion al contenido del presente mensaje. Cualquier consulta realizar por favor a sysadmin(a)uca.edu.py . Protected by LED

3 2

[Dovecot] in a major jam... authentication
by tallison1 22 Jan '06

22 Jan '06

I was upgrading my debian box and managed to upgrade my dovecot installation at the same time. I wasn't planning on it, but it came along just the same. I took some notes on what I thought I needed to change, but apparently it wasn't enough. I've been running this for quite some time now with pgsql authentication and it's been one of those nice applications that always behave themselves. Until now. I can connect to the database. But I always fail the authentication. From the logs I'm coming in on a PLAIN authentication and failing on "password mismatch" The database hasn't changed the password in years. The database stores the password as (I believe) an md5 encryption of the real password. Whatever it is, it is definitely encrypted in the table. What I had in my configuration file was something like this: disable_plaintext_auth = no (this was marked as the default and I enforced it in the new file) auth_mechanisms = plain auth_passdb = pgsql:/etc/dovecot/dovecot-pgsql.conf auth_user = root login = imap I have updated the configuration as follows: dovecot-pgsql.conf 'driver = pgsql' 'default_pass_scheme = PLAIN-MD5' ( I tried changing this to PLAIN but it didn't help ) dovecot.conf protocols = imap disable_plaintext_auth = no protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } passdb sql { args = /etc/dovecot/dovecot-pgsql.conf } userdb passwd { } user = root } I'm not sure what to try now, all I know is that my IMAP server is just dead and I'm unable to get the authentication working again. I can't find much that says how to set this up again and am reluctant to just start trying stuff.

3 2

[Dovecot] plain text auth
by ohp＠pyrenet.fr 22 Jan '06

22 Jan '06

Hi everyone, This is my second try with dovecot, and still no luck. What I want is twig to work with dovecot on the localhost address . I need to authenticate through pam for real accounts and through pgsql for virtual ones. I just cant autenticate: logs are : imap-:login: Authenticate PLAIN failed: Unsupported authentication mechanism or: Aborted login: method = PLAIN Could someone please share a working config file that does what I want? I'm struggling for weeks now both on tyhe alpha5 and beta1 versions. TIA -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

5 8

[Dovecot] INBOX as either mbox or Maildir
by Tom Alsberg 22 Jan '06

22 Jan '06

In Dovecot 0.99, I recall somewhere I read it was possible for INBOX to be both a Maildir and an mbox in the same configuration (either automatically detected, or depending on the existence in a different location). Perhaps I was wrong, I'm not sure. Any way, I now became interested in this sort of setup: Most users have their spool an mbox in /var/mail/<username>, and then they (or their MUA) have to move read mail from there to ~/mbox or something like that (a state in which users use the spool as a long-time storage space is unacceptable, and we have measures to avoid it). However, for those that will access their mail only via IMAP, it will be easier to set in .forward or something like that automatic delivery directly to their mailbox - some Maildir in their home directory (there can then be a link from /var/mail or /var/maildir or whatever to there), which will contain both read and new messages. In such a case one would want INBOX to be that main mailbox. Would it be possible to set Dovecot to either automatically detect whether /var/mail/<username> is a Maildir or mbox (which relates to my interest in mixing maildirs and mboxes in one namespace which I have written about several months ago) or to configure several options for INBOX with the first one found used? Cheers, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

Re: [Dovecot] Login user doesn't exist: dovecot
by Anne Wilson 21 Jan '06

21 Jan '06

On Thursday 19 Jan 2006 22:37, Willem Riede wrote: > On 01/19/2006 05:11:30 PM, Anne Wilson wrote: > > I think that maybe I should uninstall it and start again. > > Now that you're running Fedora you should use a RPM to install > dovecot. I can help you with that by getting you my working beta1 > src.rpm to rebuild, if you like. > Hi, William. Thanks for the offer. I'm a bit puzzled at the moment as to where I've actually got to. This is what's happened: I had original made an rpm with checkinstall, so I removed the dovecot user, so that a new install would set it up with the expected UID and GID, and removed the rpm. My 'bright' idea was that I would install the official Fedora 0.99.14, then install 1.0bet1 over it. I had been assured earlier that it would install over the executables, so it seemed reasonable. I got 0.99.14 on, but could not find the dovecot.conf.example or dovecot.conf to check paths, which worried me a bit, so I thought that if I attempted a login it would give me errors that would define a path. For the first time ever, it logged in! What's more, I can see my imap directories on another box. The only dovecot.conf that I know about is the copy that was in /home/anne. What do you think is happening? If all is working I will leave well alone. This is to be a temporary mail server while I do an upgrade. I don't want to do any more work on it than I need to, because I will be doing it over again, for a permanent install, on the upgraded box in a week or so. Anne -- Registered Linux User No.293302 (http://counter.li.org/)

5 5

[Dovecot] beta1: assert due to hard fs quota
by Jeff A. Earickson 20 Jan '06

20 Jan '06

Hi, In the "for what it is worth" category... The following assert popped up in beta1 on Solaris 9 this morning: imap(user): file mail-index-view-sync.c: line 155 (view_sync_get_expunges): assertion failed: (ret == 0) The user had hit a hard disk quota on their home directory, ie where the indexes go. Dovecot cored with a zero-byte core file in the user's home directory, naturally. Jeff Earickson Colby College

1 0

[Dovecot] Login user doesn't exist: dovecot
by Anne Wilson 20 Jan '06

20 Jan '06

After completely trashing my system a few days ago, I now have FC4 running, and have compiled dovecot-1.-beta1. Everything is placed in a different place from the debian install, so it's possible that I have a path problem. Attempting to start dovecot in a root console brings up the line Login user doesn't exist: dovecot Advice, please? Anne

5 11

[Dovecot] Major CPU spike for SSL parameters?
by Todd Vierling 20 Jan '06

20 Jan '06

I went from a nightly of about 20051117 or so (about alpha4 generation) to 1.0beta1 yesterday, and dovecot is now spinning the CPU furiously apparently every ~10 minutes per: Jan 18 13:04:36 server dovecot: SSL parameters regeneration completed Jan 18 13:14:14 server dovecot: SSL parameters regeneration completed Jan 18 13:24:00 server dovecot: SSL parameters regeneration completed Jan 18 13:37:09 server dovecot: SSL parameters regeneration completed Jan 18 13:44:21 server dovecot: SSL parameters regeneration completed Jan 18 13:54:37 server dovecot: SSL parameters regeneration completed Jan 18 14:04:03 server dovecot: SSL parameters regeneration completed Jan 18 14:14:58 server dovecot: SSL parameters regeneration completed Jan 18 14:24:03 server dovecot: SSL parameters regeneration completed Jan 18 14:34:18 server dovecot: SSL parameters regeneration completed Jan 18 14:44:11 server dovecot: SSL parameters regeneration completed Jan 18 14:53:44 server dovecot: SSL parameters regeneration completed Jan 18 15:04:16 server dovecot: SSL parameters regeneration completed Jan 18 15:13:59 server dovecot: SSL parameters regeneration completed Jan 18 15:25:22 server dovecot: SSL parameters regeneration completed Jan 18 15:33:58 server dovecot: SSL parameters regeneration completed Jan 18 15:44:03 server dovecot: SSL parameters regeneration completed Jan 18 15:54:13 server dovecot: SSL parameters regeneration completed Note that this is not the DH parameter generation; that completed on the first run, as documented. This is impacting other processes on the machine, and it seems a bit of a radical change. Is the internal default meant to be this short...? I'm going to attempt to set "ssl_parameters_regenerate" explicitly, but I'd like to stick with builtin defaults wherever possible. (Perhaps this regeneration could also be made a little friendlier on the machine, by forking and using setpriority() to lower the CPU demand of this work from the default nice level of the main daemon.) -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

3 5

[Dovecot] beta1: how to use quota plugin???
by Jeff A. Earickson 20 Jan '06

20 Jan '06

Hi, After searching gmane.mail.imap.dovecot on the topic, and wiki.dovecot.org, I'm still clueless on how to use RFC 2087 quotas in dovecot with the quota plugin. How come no wiki doc? My setup: Solaris 9, mbox format. Both the filesystem for INBOXes (/var/mail) and the user's home directories have filesystem-based quotas imposed. For example: % quota -v joeblow Disk quotas for joeblow (uid 20737): Filesystem usage quota limit /export/home 955 298000 302400 (where indices and mail folders go) /var/mail 530 151200 204800 (where joeblow's INBOX lives) If joeblow connects via dovecot IMAP, I want our webmail code (horde/imp) to tell him his disk quotas to keep him out of trouble. Horde/Imp (2.2.5) has quota code that says it works with Courier imap. Dovecot is supposed to be Courier compatible. How do I get the quota info out of Dovecot and down to Horde/IMP? Jeff Earickson Colby College

3 3

[Dovecot] Migrating from UW IMAP - pine - Thunderbird - squirrelmail
by Gerhard Wiesinger 19 Jan '06

19 Jan '06

Hello! In this email you can find a configuration primer for a Migration from UW IMAP with pine, Thunderbird and squirrelmail as client. For compatibility the mbox format is used. A description for pine with imap acces without entering any password is also discussed. Please use dovecot 1.0beta1 or later for correct handling with pine. Short overview of Mail folders: =============================== | Used | elm | pine | Thunderbird | squirrelmail | UW imapd | dovecot | Base directoy | ~/Mail | ~/Mail | ~/mail | as configured | mail | | | Sent Folder | ~/Mail/sent | ~/Mail/sent | ~/mail/sent-mail | Sent | Sent | | | Trash Folder | ~/Mail/Trash | | - | Trash | Trash | | | Drafts Folder | ~/Mail/Drafts | | saved-messages | Drafts | Drafts | | | Templates | ~/Mail/Templates | | | Templates | | | | Unsent Folder | wie Thunderbird | | | Local Folders/Unsent Messages | | | | Postponed | | | postponed-msgs | | | | | Canceled Mail | | ~/Canceled.mail | ~/dead.letter | | | | | Personal namespace | | | | | | | | Public namespace | | | | | | #news | | Other Users | | | | | | | | pine setup: =========== SETUP(S)/collectionLists(L)/Mail Just add the following to Server: localhost/notls Before: Nickname : Mail Server : Path : Mail/ View : After: Nickname : Mail Server : localhost/notls Path : Mail/ View : In ~/.pinerc modify the following configuration parameters: mail-check-interval=15 rsh-open-timeout=30000 rsh-path= rsh-command=/usr/sbin/dovecot --exec-mail imap # For large Mailboxes tcp-read-warning-timeout=180 For details have a look at: http://www.unix.org.ua/orelly/networking_2ndEd/ssh/ch11_03.htm http://www.cs.unc.edu/cgi-bin/howto?howto=pine-imap http://www.ii.com/internet/messaging/pine/ http://www.umanitoba.ca/acn/docs/pine/pine-imap.html Migration from UW Imapd to dovecot: =================================== Disable UW Imapd in xinetd http://wiki.dovecot.org/Migration Migrate Mailboxes: http://wiki.dovecot.org/uw2dovecot.sh or cd $USER cp .mailboxlist .subscriptions dovecot configuration: Config (/etc/dovecot.conf): UW Imapd compatible protocols = imaps default_mail_env = mbox:~:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_read_locks = fcntl mbox_write_locks = fcntl mbox_lazy_writes=no Self signed Certificate for SSL: cd /etc/pki/dovecot/private openssl genrsa -out dovecot.pem 2048 openssl req -new -x509 -nodes -sha1 -days 3650 -key dovecot.pem >../dovecot.pem Enter the data for the certificate http://sial.org/howto/openssl/self-signed/ dovecot debugging: ================== Config (/etc/dovecot.conf): #GW: mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap Directory ~/dovecot.rawlog must exist and the input/output will be logged there For ethereal debugging use the following dovecot configuration: Sniffing: #GW: protocols = imap imaps #GW: disable_plaintext_auth = no maildir/mbox documentation: =========================== http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=fw&db=man&fname… http://people.redhat.com/rkeech/maildir-migration.txt squirrelmail: ============= $use_imap_tls = true; $imapPort = 993; $imap_server_type ='dovecot'; $optional_delimiter = 'detect'; $force_username_lowercase = true; $default_folder_prefix = '~/Mail/'; $sent_folder = 'sent'; $show_prefix_option = false; $show_contain_subfolders_option = false; Thunderbird Plugins =================== With imap Folder the Xpunge plugin is very usefull to have consitent mailboxes. Xpunge https://addons.mozilla.org/extensions/moreinfo.php?application=thunderbird&… http://www.cs.ualberta.ca/~tegos/mozilla/tb/ Hope is helps. Feedback is welcome. Ciao, Gerhard

1 0

[Dovecot] no inbox error?
by John Woodell 19 Jan '06

19 Jan '06

When a new user has no inbox (has not received a message), the box client shows an error dialog. Is there any way to surpress this... besides touching an empty inbox for all valid accounts?

1 0

[Dovecot] Dovecot + mysql on CentOs 4.2 64-bit...
by Anders Kongsted 19 Jan '06

19 Jan '06

Hi, I'm in trouble. Is there any how-to'es to set up a server as described in the subject? Regards Anders

1 0

[Dovecot] Donating
by Timo Sirainen 19 Jan '06

19 Jan '06

I've never really liked all these donation buttons in web pages, or receiving donations at all, but as some extra money could make my life easier in the next few months, I thought I'd give it a try. http://dovecot.org/donate.html (And if you're wondering how I could still promise those 1000 euros for a security hole, I've a credit card but I'd rather not use it :) Also I'm not really expecting for anyone to find holes at least anytime soon.)

9 10

[Dovecot] problems compiling
by Imre Gergely 19 Jan '06

19 Jan '06

hi i downloaded dovecot-1.0.beta1.tar.gz, did a rpmbuild -ta dovecot-1.0.beta1.tar.gz (which uses the dovecot.spec from the tar.gz), and got the following: Making install in quota make[3]: Entering directory `/usr/src/gimre/rpm2/BUILD/dovecot-1.0.beta1/src/plugins/quota' make[4]: Entering directory `/usr/src/gimre/rpm2/BUILD/dovecot-1.0.beta1/src/plugins/quota' mkdir -p -- /usr/lib/dovecot/imap /usr/lib/dovecot/lda mkdir: cannot create directory `/usr/lib/dovecot': Permission denied mkdir: cannot create directory `/usr/lib/dovecot': Permission denied make[4]: *** [install-exec-local] Error 1 make[4]: Leaving directory `/usr/src/gimre/rpm2/BUILD/dovecot-1.0.beta1/src/plugins/quota' make[3]: *** [install-am] Error 2 so everything did compile alright, but it has some problems with installing the plugins. and i dunno why it tries to create those directories in the root directory. of course i'm compiling it as a non-root users, so it doesn't have any write permissions. and it normally shouldn't have to do an install in directories other then buildroot. so what's the catch? if i disable from the src/Makefile.in to not compile the plugins, everything works fine, i got a nice rpm file. i'm on Fedora Core 4. any help would be appreciated. thx.

5 7

[Dovecot] dovecot lda with sendmail
by Michael Surette 18 Jan '06

18 Jan '06

I'm trying to set up dovecot's deliver program as the lda for sendmail. I seem to need a config file for it '/etc/dovecot-deliver.conf'. Is there any documentation for this configuration file and it's contents? sendmail will call it under the recipient's uid, and all it has to do is drop the message into the proper maildir as defined in /etc/dovecot.conf and update the indexes. Mike

2 2

[Dovecot] still strugling
by ohp＠pyrenet.fr 18 Jan '06

18 Jan '06

Hi all, After I posted yesterday, I'm still struggling with dovecot 1.0beta1 I installed it on openbsd with no problem. But I can't get it to authenticate plaintext on Unixware. I had to add two include files <sys/types.h> and <sys/mkdev.h> in compat.h because minor and major where undefined on unixware. I doubt that could fail... What's wrong with that conf: ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr/local --sysconfdir=/usr/local/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap pop3 # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. login_process_per_connection = no # Number of login processes to create. If login_process_per_connection is # yes, this is the number of extra processes waiting for users to log in. login_processes_count = 1 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_connection # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. first_valid_gid = 0 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = mbox:/var/spool/mail/%u # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time to wait between those checks. Dovecot is however able to use dnotify # and inotify with Linux to reply immediately after the change occurs. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. NOTE: If you use NFS, remember to change also mmap_disable setting! # Solaris doesn't support flock, so Solaris users need to change this to fcntl. #lock_method = flock # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/local/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/local/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/local/libexec/dovecot/rawlog /usr/local/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/local/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. login_greeting_capability = yes # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/local/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/local/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # pop3_uidl_format = %08Xu%08Xv # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/local/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ## ## Authentication processes ## # Executable location #auth_executable = /usr/local/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. Also note that currently auth cache doesn't work very well if # you're using multiple passdbs with same usernames in them. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = yes # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous gssapi mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. passdb pam { # [-session] [cache_key=<key>] [<service name>] # # -session makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work. # # cache_key can be used to enable authentication caching for PAM # (auth_cache_size also needs to be set). It isn't enabled by default # because PAM modules can do all kinds of checks besides checking password, # such as checking IP address. Dovecot can't know about these checks # without some help. cache_key is simply a list of variables (see # doc/variables.txt) which must match for the cached data to be used. # Here are some examples: # %u - Username must match. Probably sufficient for most uses. # %u%r - Username and remote IP address must match. # %u%s - Username and service (ie. IMAP, POP3) must match. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. #args = dovecot } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # BSD authentication. Used by at least OpenBSD. #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database #passdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:/home/%u/mail nice=10 # #args = #} # SQL database #userdb sql { # Path for SQL configuration file, see doc/dovecot-sql.conf for example #args = #} # LDAP database #userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using X509_NAME_oneline() # which typically uses subject's Distinguished Name. #ssl_username_from_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot-auth-master # # WARNING: Giving untrusted users access to master socket may be a # # security risk, don't give too wide permissions to it! # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot-auth-master # } # } #} Where can I start to debug? Can someone help? -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

1 0

[Dovecot] Re: Error on login when running dovecot on RH9
by Ismail M. Settenda 18 Jan '06

18 Jan '06

Error on login when running dovecot on RH9 and I get an error msg when I login thru squirrel mail that the user name or password incorrect.. BTW ..installed squirmail from rpm and dovecot from tar file , I had a bit of a problem getting dovecot to run as I had to copy to file from a running copy on Fedora, the two file where - /usr/share/ssl/private/dovecot.pem - /usr/share/ssl/certs/dovecot.pem But it is runnig now...I just cant login!! Can anyone help? Below is the output form maillogs below from login as user : ismail Jan 17 10:45:40 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 10:49:17 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:02:57 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:03:03 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:10:08 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 17 11:10:14 elct dovecot: imap-login: Aborted login: user=<ismail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured -- Ismail

1 0

[Dovecot] Auth wit multiple ldap configfiles
by Dominik Saar 18 Jan '06

18 Jan '06

Hi, trying to deliver local mails with exim over dovecot. The problem is, that i logged in with a username from ldap to imap For this i created in dovecot.conf auth imap { args = /path/to/dovecot-ldap.conf ...... } And for delivery i use command = /path/to/dovecot/deliver -d $local_part@$domain in the exim.conf $local_part is diferent to the loginname in the ldaptree So i create in dovecot.conf auth deliver { args = /path/to/dovecot-ldap_deliver.conf } Sometime dovecot check the "auth deliver" section and sometimes the "auth imap" section i created. I don´t understand why dovecot doesn´t check allways both sections?!? P.S.: Sorry my english :)

1 0

[Dovecot] gdbhelper.c concerns
by Jeff A. Earickson 17 Jan '06

17 Jan '06

Timo, I was surprised to find both an execvp() and a system() call in gdbhelper.c. While gdbhelper should be running as an ordinary user (the person running imap), I find it a bit scary. I realize that the code is getting ready to run gdb, which is god-knows-where in the user's path. But still... Maybe the code should do a getuid() and/or geteuid() and refuse to run if the uid is zero. Also, the code does the fork() *before* checking the argc count. Maybe do it the other way around so the i_fatal is killing one process instead of two. Jeff Earickson Colby College

1 0

[Dovecot] 1.0 beta1 -- kevent() for notify failed: Invalid argument
by John Wong 17 Jan '06

17 Jan '06

after upgrade to 1.0 beta1 i see the warning/error message in mail log like this: kevent() for notify failed: invalid argument I/O leak: 0x1c05b6cc (5) is it normal?

2 1

[Dovecot] 1.0 beta1 plugin-loading
by Jan-Piet Mens 17 Jan '06

17 Jan '06

When a user logs on, the following messages appear in the log: dovecot: imap 21360 : Loading modules from directory: /usr/local/lib/dovecot/imap dovecot: imap 21360 : dlopen(/usr/local/lib/dovecot/imap/lib02_trash_plugin.so) failed: /usr/local/lib/dovecot/imap/lib02_trash_plugin.so: undefined symbol: quota dovecot: imap 21360 : Module loaded: /usr/local/lib/dovecot/imap/lib01_quota_plugin.so dovecot: imap 21360 : dirsize quota path = /shared/homes/rscweb.net/jpm/Maildir/ dovecot: imap 21360 : dirsize quota limit = 512000kB dovecot: imap 21360 : Module loaded: /usr/local/lib/dovecot/imap/lib02_imap_quota_plugin.so dovecot: imap 21360 : dlopen(/usr/local/lib/dovecot/imap/lib01_zlib_plugin.so) failed: /usr/local/lib/dovecot/imap/lib01_zlib_plugin.so: undefined symbol: gzseek Removing those files with rm -f lib01_zlib_plugin.* lib02_trash_plugin.so solves the problem. Platform Centos 4.2 , Linux 2.6.9-22.0.1.ELsmp Regards, -JP

1 0

[Dovecot] 1.0beta1: bullet-proofing dovecot-example.conf
by Jeff A. Earickson 17 Jan '06

17 Jan '06

Timo, I got bit last night during my upgrade to beta1 by uncommenting the following part of dovecot.conf for my site: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} I did a "s/#//" over this block of code, thereby uncommenting the comment too. Then I wondered why beta1 wouldn't start for me, until I found the conf syntax error. I suggest "bullet-proofing" some of the comments in dovecot-example.conf against this error, like so: #passdb passwd-file { ### File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} Attached is a diff against beta1 dovecot-example.conf to fix this kind of dumb mistake. Jeff Earickson Colby College

1 0

[Dovecot] SSL and login_process_per_connection = no
by Chris Wakelin 17 Jan '06

17 Jan '06

Just thought I'd check, but is the combination of SSL and "login_process_per_connection = no" expected? I'm wondering, because imap_login is doing the SSL-proxying, and in our live Dovecot instance we have "login_process_per_connection = no" (we had problems with authentication and running out of file descriptors early on, now fixed by using userdb = passwd-file rather than NIS). This combination seems to work OK in 1.0-beta1, except I just got disconnected with a log entry: Warning: imap-login: SSL_write() syscall failed: Bad file number [<IP address>] which I've never seen before (though I've been testing this with alpha5 for weeks). 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] 1.0 beta1 testing
by Timo Sirainen 17 Jan '06

17 Jan '06

If you have time, please test http://dovecot.org/nightly/dovecot-latest.tar.gz If nothing big comes up, I'll release it as 1.0beta1 tomorrow evening.

8 10

[Dovecot] Duplicate suppression
by Greg Trounson 17 Jan '06

17 Jan '06

Hi there, Does the Dovecot project have plans to implement duplicate suppression at some stage? I have a situation where several people belong to more than one mailing list. One alias ('staff') incorporates several lists. These staff are receiving duplicate messages (one copy for every list they're on) when a message is sent to this staff alias. There is no reason they need to receive more than one copy. There seems to be no way I can turn that feature off in my MTA so I thought I'd try a bit further down the chain. thanks, Greg

6 6

[Dovecot] virtual users with winbind
by Paul Matthews 17 Jan '06

17 Jan '06

hi there, i'm trying to setup virtual users with winbind, i have everything setup in dovecot other than 'Data source for users, homes and IDs'. i have 'Password authentication source' set to auth_passdb = pam my pam module is using winbind with the mkhomedir.so i have 'Mail file location' set to default_mail_env = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u i have 'Data source for users, homes and IDs' set tp auth_userdb = passwd at the moment my local users can sign in, but my winbind users can't, i'm looking for a way to make auth_userdb look up a pam module, or something ... i don't know what i'm looking for, can someone help me with virtual users with winbind?

1 0

[Dovecot] in a major jam...
by Tom Allison 16 Jan '06

16 Jan '06

I upgraded my dovecot installation from something <<1.0 to 0.99.14 today. I wasn't exactly planning to but it just came along for the ride when I upgraded the rest of my system. I was using postgresql for the authentication. Nothing works. the debug logs show that I'm able to make a connection to the database table well enough: auth(default): pgsql: Connected to dbmail (that's my database name) When I attempt to login I get (briefly) password mismatch. I haven't changed the password in well over a year. My old configuration file for dovecot.conf went to the tune of: login = imap auth_mechanisms = plain auth_passdb = pgsql:/etc/dovecot/dovecot-pgsql.conf auth_user = root (probably not the best, but it worked) I now have a config file something like this: dovecot-pgsql.conf -- added the 'driver = pgsql' statement. Because it's able to connect to the database I don't think this is much of a problem here. dovecot.conf (these are all the non-empty lines, except for some logging stuff) protocols = imap disable_plaintext_auth = no protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb pam { } passdb sql { args = /etc/dovecot/dovecot-pgsql.conf } userdb passwd { } user = root } It's fairly obvious that there has been a lot of work done on getting more authentication mechanisms in place for dovecot. That's great, and some day I want to play with it, but this is not the day for it. help.... help.... oh help!

2 2

[Re: [Dovecot] in a major jam...]
by Tom Allison 16 Jan '06

16 Jan '06

Marcus Rueckert wrote: > On 2006-01-16 14:46:36 -0500, Tom Allison wrote: > >>I upgraded my dovecot installation from something <<1.0 to 0.99.14 >>today. I wasn't exactly planning to but it just came along for the ride >>when I upgraded the rest of my system. > > > do you mind to upgrade to the release mentioned in this mail > http://www.dovecot.org/list/dovecot/2006-January/010832.html ? > > the 0.99.14 code base is 2y old and no longer actively maintained. > I upgraded from 0.99.14. It reports 1.0alpha5 now. This is the transistion that broke me. And I just realized I posted this twice to the mailing list. My rather hastily set up connection to another mail server wasn't telling me I actually sent anything.

1 0

[Dovecot] Plain password not authenticating
by Anne Wilson 16 Jan '06

16 Jan '06

I'm trying to set up a temporary mailserver using Debian Sarge and Dovecot 1.0 with maildir format. My only previous experience has been on a simple imap server. I have read the wiki documentation and searched the archives, but can't tie down my problem. The log tells me Info: passwd-file(anne) : unknown user. I have set auth_userdb = passwd-file /etc/imap.passwd auth_passdb = passwd-file /etc/imap.passwd and created the /etc/imap.passwd file as anne:{plain}mypassword:1000:1000::/home/anne What have I missed? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

4 23

[Dovecot] Re: Dovecot memory use and settings
by Roger Weeks 16 Jan '06

16 Jan '06

We're continuing to have dovecot auth-worker failures once or more times per day. The symptoms are these in the log: pop1 dovecot: auth-worker(default): Out of memory (Needed 8164 bytes) or auth-worker(default): sql(lewis1,12.43.59.134): Password query failed: MySQL client ran out of memory Timo suggested that we need to up the auth_process_size = 256 However, we've tried increasing this to 512 and then 768. The comment on the entry says # Set max. process size in megabytes. These changes don't seem to make any difference. On both of our servers (RH ES4, 1MB RAM), we never seem to have more than 300MB of RAM used. However, the auth-worker process continues to fail occasionally. It does respawn itself after a couple of minutes, but in that time all authentication for dovecot fails. Am I missing something else in the config? -- Roger J. Weeks Systems & Network Administrator Mendocino Community Network On Jan 11, 2006, at 12:51 PM, Timo Sirainen wrote: > On Wed, 2006-01-11 at 12:40 -0800, Roger Weeks wrote: >> pop1 dovecot: auth-worker(default): Out of memory (Needed 8164 bytes) >> >> or >> >> auth-worker(default): sql(lewis1,12.43.59.134): Password query >> failed: MySQL client ran out of memory > > These are different from the system running out of memory. It's about > authentication process size hitting its configured limit. Default is: > > # Set max. process size in megabytes. > #auth_process_size = 256 > > So it appears that it's trying to grow above 256MB at which point it > gets killed. This could mean that something is leaking memory, but I > don't remember other people having this problem, so it might be > somehow > specific to your configuration. > > In any case those auth-workers are restarted automatically whenever > they > die so it shouldn't be that big of a problem? > > There are also ways to debug this if you want to.. >

3 5

[Dovecot] Imap working, but not Pop3
by Cyril Spiro 16 Jan '06

16 Jan '06

I'm running Redhat Linux 4.1 and I have dovecot loaded and imap is working. Users can get their mail via squirrelmail. But everytime I try to 'chkconfig ipop3 on' I get the error 'error reading information on service pop3: no such file or directory'. Any ideas?

2 1

[Dovecot] passdb-pam: PAM_RHOST on FreeBSD >= 5.0 (where PAM != Linux-PAM)
by Tom Alsberg 16 Jan '06

16 Jan '06

This is actually something I had on my mind to write about in the past few -stable and alpha releases, but did not get to and instead always patched myself. Now having updated to the latest snapshot (which may be released as beta1), I stumbled on it again: In src/auth/passdb-pam.c, where the client host is passed to PAM, the code looks like this: #ifdef PAM_RHOST const char *host = net_ip2addr(&request->remote_ip); if (host != NULL) pam_set_item(pamh, PAM_RHOST, host); #endif For some reason there is a preprocessor/compile-time check whethere there exists such a preprocessor symbol as the PAM item PAM_RHOST (why check that? IIRC PAM_RHOST is standard and in all PAM implementations). However, PAM_RHOST (or other PAM items, for that matter), are not preprocessor symbols in all PAM implementations. For example, in OpenPAM (the PAM implementation used on FreeBSD >= 5.0, among others; FreeBSD 4 used Linux-PAM), PAM items are elements of an enum, and thus this check fails, and the client host is not passed to PAM. Since it can be defined in several ways, I do not see how to check for it other than using a compilation test (in autoconf) and then defining something like HAVE_PAM_RHOST in config.h. However I do not see why check for it at all, so I propose to remove that #ifdef. Tiny patch attached for that. Cheers, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

1 0

[Dovecot] Looking to upgrade from .99.14 to 1.0alpha5
by Erik Dasque 15 Jan '06

15 Jan '06

Hi all, I was looking to upgrade my dovecot .99.14 installation to 1.0alpha5 today and bumped into an issue. My setup is on Mac OS X 10.4 and I am using After reading http://wiki.dovecot.org/UpgradingDovecot , I created a default dovecot.conf file with the following information grabbed from my prior installation: Snow:~ ed$ grep -v '^ *#' /usr/local/etc/dovecot.conf|grep -v ^$ ssl_disable = yes login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam login auth_user = root auth_verbose = yes So as you can see, I use passwd and pam as my authentication db. So I copied over the dovecot-example.conf and as far as I know the only modifications I needed to make to the default file were to disable ssl and set the verbose and debug auth. Keep in mind that passwd/pam db methods work with .99.14 but with 1.0alpha5, I get the following: Jan 14 15:55:16 Snow dovecot: Dovecot v1.0.alpha5 starting up Jan 14 15:58:15 Snow dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGVkAGFic2ludGhlMzM= Jan 14 15:58:15 Snow dovecot: auth(default): pam(ed,127.0.0.1): pam_authenticate() failed: Authentication failure Jan 14 15:58:15 Snow dovecot: auth(default): client out: FAIL 1 user=ed Jan 14 15:58:21 Snow dovecot: auth(default): client in: AUTH 2 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGVkAGFic2ludGhlMzM= Jan 14 15:58:21 Snow dovecot: auth(default): pam(ed,127.0.0.1): pam_authenticate() failed: Authentication failure Jan 14 15:58:21 Snow dovecot: auth(default): client out: FAIL 2 user=ed and so on and so forth. Any idea what could be causing this or how to debug this further ? Thanks in advance, Erik PS: my pam setup for dovecot is: Snow:~ ed$ more /etc/pam.d/dovecot auth required pam_unix.so nullok account required pam_unix.so

3 2

[Dovecot] Occasional errors opening email folder in SquirrelMail
by Jonathan 15 Jan '06

15 Jan '06

Every once in a while I get this [1] error when trying to open a mail folder in SquirrelMail. I don't know enough about IMAP to tell if it is a SquirrelMail or a Dovecot issue. I also get this [2] error message every time I try to send an email. The email goes through but there is no copy in the Sent folder. If there is some kind of logging I can enable that would help with this please let me know. [1] ERROR: Bad or malformed request. Query: FETCH (FLAGS UID RFC822.SIZE BODY.PEEK[HEADER.FIELDS (Date To Cc >From Subject X-Priority Importance Priority Content-Type)]) Server responded: Error in IMAP command UID: Invalid arguments. [2] ERROR: Bad or malformed request. Server responded: Error in IMAP command APPEND: Thank you, Jonathan

2 2

[Dovecot] How long to 1.0?
by Fredrik Tolf 15 Jan '06

15 Jan '06

Hi! I'm wondering how close Dovecot can be said to be to 1.0 "Final". How stable can the alpha branch be said to be? I was browsing around the Dovecot homepage, but I couldn't find any answer to this question. I hope it hasn't been asked (too many times) before. Fredrik Tolf

15 29

[Dovecot] Corrupted index files
by Andy Cravens 15 Jan '06

15 Jan '06

I'm using alpha 5 and I'm getting "Corrupted index cache files" errors on one user's account. I found several posts in the mail archives on this subject and concluded from the responses that it's not a serious problem because Dovecot can deal with it. I deleted the index files and they were recreated but the error persists. The end user did not notice any problem but it makes me nervous. Is this something I should be concerned about? dovecot: Jan 12 10:22:06 Error: imap(username): Corrupted index cache file /export/home/username/mail/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE dovecot: Jan 12 14:31:08 Error: imap(username): Corrupted index cache file /export/home/username/mail/.syslog_analyzer/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE dovecot: Jan 12 14:43:56 Error: imap(username): Corrupted index cache file /export/home/username/mail/.gl3_ip_allocation/dovecot.index.cache: Duplicated field in header: hdr.CONTENT-TYPE By the way... is there a search function somewhere for searching the mailing list archives? I ended up selecting one month at a time and searching through the thread titles with my browser's "find" button. -- Andy

3 3

[Dovecot] 20060114 snapshot compilation warnings
by Chris Wakelin 15 Jan '06

15 Jan '06

Timo, I've noticed a couple of extra compilation errors in last night's snapshot compared to the snapshot I downloaded on Tuesday, probably due to the int -> bool change :- (gcc 3.3.2 on Solaris 8) mbox-sync.c: In function `mbox_sync': mbox-sync.c:1568: warning: comparison is always false due to limited range of data type index-search.c: In function `search_index_arg': index-search.c:131: warning: comparison is always false due to limited range of data type quota-storage.c: In function `quota_check': quota-storage.c:114: warning: passing arg 3 of `quota_try_alloc' from incompatible pointer type together with a few "unused parameter/variable" errors which were there before. I also needed to rewrite half my internal patches :) but that shouldn't have made any difference (they certainly don't involve those files). 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

3 5

[Dovecot] How can I archive maildir?
by Neal Becker 15 Jan '06

15 Jan '06

Does anyone have a suggestion how to archive old maildir format mail?

2 3

Fwd: Re: [Dovecot] Compile problem on FreeBSD 6.0-STABLE
by Peter Losher 15 Jan '06

15 Jan '06

On Friday 30 December 2005 12:54 pm, Brad wrote: > Why would you install a port of something that comes with > the base OS, especially MIT Kerb5? While Krb5 is included in FreeBSD, it's Heimdal implementation, not MIT's, and some of us have valid reasons for running MIT Krb5 instead and the API's are different between the two. Best Wishes - Peter -- [ http://www.plosh.net/ ] - "Earth Halted: Please reboot to continue"

1 0

[Dovecot] Password changing?
by john 14 Jan '06

14 Jan '06

Hey all, new user to the dovecot mailing list but I promise, this is a neat question. Is it possible to request users change their email password through their email client? I'm currently authenticating email logins to my dovecot server through SSL, with each users password checked against their /etc/passwd password. So far, thunderbird will ask for the users new password (forced change at first logon,) but it fails to change the users password through the encrypted email connection. Any assistance would be gladly appreciated. Getting past this hurdle means i can eliminate one more bill gates server/money hole with a power button. P.S. If anyone isnt using this "feature" to get users to set their email password, how might i ask are you getting users to change their email password to dovecot? --John

2 1

[Dovecot] [BUG] Thread command
by Sebastjan Trepca 14 Jan '06

14 Jan '06

Hi, while implementing thread support in our mail application I found a bug which kills IMAP(alpha5, SUSE 10) process... These are the commands: x OK Logged in. x select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk $Forwarded Spam) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft NonJunk Junk $Forwarded Spam \*)] Flags permitted. * 2280 EXISTS * 1 RECENT * OK [UNSEEN 473] First unseen. * OK [UIDVALIDITY 1136386397] UIDs valid * OK [UIDNEXT 2319] Predicted next UID x OK [READ-WRITE] Select completed. x uid thread references utf8 (SUBJECT "locking") * THREAD (2289 2307) * 2281 EXISTS * 1 RECENT x OK Thread completed. x UID THREAD REFERENCES UTF8 (SUBJECT 'locking') Connection closed by foreign host. This is the code dump: (gdb) bt full #0 0xdededede in ?? () No symbol table info available. #1 0x08060127 in mail_thread_deinit (ctx=0x80c0120) at imap-thread.c:100 No locals. #2 0x080611e2 in imap_thread (cmd=0x80c5c34, charset=0x80c5f48 "UTF8", args=0x80ea980, type=MAIL_THREAD_REFERENCES) at imap-thread.c:156 wanted_headers = {0x80b6645 "message-id", 0x80b2947 "in-reply-to", 0x80b2953 "references", 0x80b1978 "subject", 0x0} client = (struct client *) 0x80c5bf0 headers_ctx = (struct mailbox_header_lookup_ctx *) 0x80eb188 ctx = (struct thread_context *) 0x80c0120 mail = (struct mail *) 0x80ced28 ret = 0 #3 0x080598b5 in cmd_thread (cmd=0x80c5c34) at cmd-thread.c:66 client = (struct client *) 0x80c5bf0 sargs = <value optimized out> args = (struct imap_arg *) 0x80c5ea0 args_count = <value optimized out> pool = 0x80ea930 error = <value optimized out> charset = 0x80c5f48 "UTF8" str = 0x80c5f38 "REFERENCES" #4 0x0805a271 in _client_input (context=0x80c5bf0) at client.c:338 cmd = (struct client_command_context *) 0x80c5c34 ret = <value optimized out> #5 0x080a91c8 in io_loop_handler_run (ioloop=0x80c49b0) at ioloop-epoll.c :250 ctx = <value optimized out> event = (struct epoll_event *) 0x80c4a00 io = (struct io *) 0x80c5da8 tv = {tv_sec = 0, tv_usec = 999991} t_id = 2 msecs = <value optimized out> ret = 0 i = 0 call = <value optimized out> #6 0x080a881b in io_loop_run (ioloop=0x80c49b0) at ioloop.c:230 No locals. #7 0x080617e4 in main (argc=3, argv=0xbfa6e7d4, envp=0xbfa6e7e4) at main.c :235 No locals. Hope this is enough. Sebastjan

2 1

[Dovecot] Errors in /var/log/maillog and /var/log/dovecot.log
by Li Cai 14 Jan '06

14 Jan '06

I am trying to migrate from UW imap to dovecot. OS: RHEL 3 X86 MTA: Postfix Auth: PAM (NIS server) Most of the users are fine, but I have some users have problems: " Jan 14 09:18:42 Info: imap-login: Internal login failure: user=<user1>, method=PLAIN, rip=X.X.X.X, lip=X.X.X.X, TLS " This happens on dovecot version dovecot-1.0.alpha5-1 and dovecot-0.99.11-1 If anyone else has met such problem? Thanks Li

2 3

[Dovecot] "Discarding bogus continuation" message in pine
by Jesse Chan-Norris 14 Jan '06

14 Jan '06

Running 1.0alpha5 (though I've been having this problem for the past couple of versions), and using mbox for the mailboxes. After I've read my mail using Apple's Mail.app (or Thunderbird) and take it offline, when I try to open the INBOX (or any mailbox) with pine, I get the following message (in pine): [Discarding bogus continuation in msg 1: $Forwarded NonJunk] Quitting and re-running pine does not bring up this message again, and it looks like it's getting confused by the internal mbox message's X-IMAP line: X-IMAP: 1076598957 0000257269 NotJunk JunkRecorded $NotJunk $Junk Junk \ Forwarded $Forwarded NonJunk The "$Forwarded NonJunk" part is the only part of that line that is on a new line, and it gets written out like that after I've read mail using an IMAP client, leading me to believe that pine doesn't know how to handle the newline in the X-IMAP line. I don't know if this is a Dovecot, Mail.app, or pine problem, but I never saw this error in UW-IMAP. Any help would be appreciated. Thanks! jcn

2 2

[Dovecot] Upgrade question
by Anne Wilson 14 Jan '06

14 Jan '06

I have 0.99.14 installed. I've downloaded the latest version. Does it install over the old one, in parallel, or need an uninstall of the old one? Anne

2 2

[Dovecot] compiling Dovecot CVS version, 1 problem, 1 wish, 3 questions
by Steffen Kaiser 14 Jan '06

14 Jan '06

Hello, today I checked out a new copy of Dovecot (and LDA) from CVS: File: ChangeLog Status: Up-to-date Working revision: 1.2765 Repository revision: 1.2765 /home/cvs/dovecot/ChangeLog,v I could compile them, but my findings follow: - the problem: I copied dovecot-lda below CVS_ROOT/dovecot, the first make attempt failed with this fatal error: make[3]: Entering directory `/var/autofs/fb02/prgdist/dovecot/dovecot/dovecot-lda/src/libsieve' /bin/sh ../../ylwrap `test -f 'addr.y' || echo './'`addr.y y.tab.c addr.c y.tab.h addr.h y.output addr.output -- bison -y -d -p addr ../../ylwrap: ../../ylwrap: No such file or directory the "ylwrap" is actually located in the Dovecot directory, hence, one directory up, so running ln -s ../ylwrap . in CVS_ROOT/dovecot/dovecot-lda fixed the problem. - the wish: It would be nice, if one could compile dovecot-lda right in the CVS locations without the need to give any option, e.g. the default "dovecot" path could be "../dovecot". - the questions: running ./autogen.sh results in: configure.in:1562: required file `./config.h.in' not found SUBDIRS: variable `DELIVER' is used but `DELIVER' is undefined ^^ Maybe the 2nd error results in that I passed "--without-deliver" to ./configure? running ./configure results in: checking for shared library run path origin... ./config.rpath: ./config.rpath: No such file or directory done running dovecot-lda/autogen.sh results in: configure.in:4: required file `./lda-config.h.in' not found Neither of these error messages prevent to built Dovecot, but they does not look "correct". Bye, -- Steffen Kaiser

3 4

[Dovecot] dovecot+ldap no auth...
by Joaquim Petiz 14 Jan '06

14 Jan '06

Dear sirs, In the configuration of Dovecot I can´t get autentication of the users. My work environment is: OpenBSD 3.8 Postfix 2.2.5 (instaled thru ports with ldap and sasl support) Opendap 2.2.27 (instaled thru ports with sasl support) Dovecot 0.99.14 (instaled thru source with ldap support) I have two domains in ldap, the postfix is just autenticating in ldap (sending e-mails to users of 2 ldap domains), I have one vmail user and one vmail group with uid e gid 800 to e-mail delivery and one dovecot user for dovecot itself. The Dovecot is not autenticating: # telnet localhost 143 * OK dovecot ready 0 login user(a)domain.com password 0 NO Authentication failed. ldap´s LOGS: Jan 11 13:48:56 ldap slapd[6397]: conn=6 op=4 SRCH base="cn=dovecot,o=organization,c=com" scope=2 deref=0 filter="(&(objectClass=qmailUser)(mail=user(a)domain.com))" Jan 11 13:48:56 ldap slapd[6397]: conn=6 op=4 SRCH attr=uid userPassword Jan 11 13:48:56 ldap slapd[6397]: conn=6 op=4 SEARCH RESULT tag=101 err=32 nentries=0 text= my slapd.conf: include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/qmail.schema include /etc/openldap/schema/openldap.schema pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args access to dn.base="" by * read access to attr=userPassword by dn="uid=vmail,o=organization,c=com" read by dn="cn=dovecot,o=organization,c=com" read by anonymous auth by self write by * none database ldbm checkpoint 1024 5 cachesize 10000 suffix "o=organization,c=com" rootdn "cn=administrator,o=organization,c=com" rootpw {CRYPT}xxxxxxxxxxx directory /var/openldap-data index objectClass eq my user.ldif dn: cn=user,ou=domain1.com,o=organization,c=com cn: user ou: domain1.com sn: user objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount objectClass: qmailUser homeDirectory: /var/vmail/domains/domain1.com/user mail: user(a)domain1.com mailHost: mail.domains.com mailQuotaSize: 0 mailQuotaCount: 0 deliveryMode: normal uid: user uidNumber: 2000 gidNumber: 2000 accountStatus: active userPassword: {CRYPT}xxxxxxxxxxxx mailMessageStore: domain1.com/user mailAlternateAddress: user(a)domain1.com my dovecot.conf protocols = imap imap_listen = *:143 ssl_disable = yes login_dir = /var/dovecot/login login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot first_valid_uid = 800 last_valid_uid = 800 first_valid_gid = 800 last_valid_gid = 800 valid_chroot_dirs = /var/vmail/domains/ default_mail_env = mbox:/var/vmail/domains/%d/%u/Maildir auth = default auth_mechanisms = plain auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf My dovecot-ldap.conf hosts = localhost dn = uid=dovecot,o=organization,c=com dnpass = password ldap_version = 3 base = o=organization,c=com deref = never scope = subtree user_attrs = uid,homeDirectory,,uid,uidNumber,gidNumber user_filter = (&(objectClass=qmailUser)(mail=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=qmailUser)(mail=%u)) default_pass_scheme = CRYPT user_global_uid = 800 user_global_gid = 800 []'s

2 1

[Dovecot] New Dovecot installation and OE not POPing problems
by techlist06 14 Jan '06

14 Jan '06

Greetings: Recently I converted my mailserver to Postfix with some local accounts being accessed via Dovecot and POP3S. The clients are OE. The users are reporting that they aren't getting their messages. In the past with my old (IW?) POP server, I just used mail -f /var/spool/user and deleted the "DO NOT DELETE THIS MESSAGE...." message #1 and this cleared any problems with messages being out of sync on what had and had not been downloaded, etc. With Dovecot, I don't know how to "bump" the mailbox to get it "reset" so that OE will download the messages again, and/or get them if it hasn't already. Is this possible? Thanks very much for the time to help, Scott

2 1

[Dovecot] Auth protocol and Perl
by Allan Joergensen 14 Jan '06

14 Jan '06

Hi, does anyone have at working Perl example of how to use the auth protocol with Perl (I'm planing on making a dovecot auth plugin for qpsmtpd but it would a lot easier to reuse somebody elses code :)) tia, -- Allan Joergensen - http://nowhere.dk/ "All right, so it's impossible. How long will it take?"

3 3

[Dovecot] ERROR : Connection dropped by imap-server.
by Paul Matthews 14 Jan '06

14 Jan '06

hi there, i'm trying to setup dovecot with squirrel mail at the moment and i'm getting this error message ERROR: ERROR : Could not complete request. Query: CREATE "Sent" Reason Given: Permission denied ERROR: ERROR : Connection dropped by imap-server. Query: SELECT "INBOX" can someone tell me what this means? and what folders i have to change the permissions on? this is out of my /etc/dovecot.conf file if it helps default_mail_env = mbox:/var/mail/%u:mbox:~/mail/

3 2

[Dovecot] Patch: More of kqueue() support.
by Vaclav Haisman 14 Jan '06

14 Jan '06

Hi, the attached patch contains these changes: 2005-12-15 22:18 Vaclav Haisman <v.haisman(a)sh.cvut.cz> * src/lib/ioloop-kqueue.c: Fix IO_ERROR behaviour. * src/lib/ioloop-notify-kqueue.c: New file. * configure.in: Improve kqueue detection and handling. Cleanup. The configure.in changes that are not related to kqueue are there to make autoconf 2.59, automake 1.9.6 and libtool 1.5.20 are happy. The directory change notification is not really well tested because Dovecot doesn't seem to use it that much. As per Brad's request I have changed all occurrences of FreeBSD to just BSD. Vaclav Haisman

4 3

Re: [Dovecot] Message read not sticking with Apple Mail / dovecot 1.0alpha5
by Andy Cravens 13 Jan '06

13 Jan '06

Yes... I'm seeing this with the Apple mail client on Tiger. Our server is alpha 5/maildir/solaris 9/75 users. The apple user with the problem typically has more that one client open. He tends to leave his home PC connected when he comes in to work. He was able to resolve the last occurrence by closing all clients and resynching his mailboxes. We've also seen this problem on Solaris 9 running Mozilla 1.7.2 and Windows XP running outlook and evolution. These other clients have not seen a problem in over a month. The Apple user has problem every week. One interesting observation on this problem is that it will go away by itself given enough time. It seems that after a few hours to a full day it will go away. -- Andy Michael Stevens wrote: > Hi. > > I'm getting very weird behaviour with Apple Mail on Tiger and > 1.0alpha5 (with Timo's patch for the bug I saw). > > I can read a mail, see Apple Mail flag it as read, quit, come back > later, and find the mail is marked unread again. It seems to also > happen sometimes when I switch folders or get new mail. > > I've not worked out what's triggering it yet. Anyone seen anything > like this? > > Michael > >

1 0

[Dovecot] reply-to address of the list
by Udo Rader 13 Jan '06

13 Jan '06

Hi, is there a chance to alter the list behaviour to not use the sender address of a posting in the reply-to field but dovecot(a)dovecot.org instead? That way one has to either use "reply to all" in the MUA or manually enter dovecot(a)dovecot.org in any replies. And a "reply to all" duplicates postings because the posting once goes to the list and once to the original poster, that get's the reply twice then. Or maybe I am missing something ... :-) Udo BestSolution.at GmbH http://www.bestsolution.at

9 11

[Dovecot] removing folders doesn't always work
by William Astle 13 Jan '06

13 Jan '06

I've been running dovecot for a while now. I've got 1.0alpha5 running on a Slackware linux 10.2 system (i386). My system is using mbox format which means you can't have folders that contain both folders and messages. What I'm seeing is that removing folders doesn't always work. From what I can tell, it only affects folders that contain folders. Dovecot doesn't remove the directory from the server when the folder is removed which means it just keeps coming back. It's easy to duplicate this. Just create a folder that is allowed to contain folders only. You will see a directory created on the server. Then remove the folder. The directory will still be on the server, even if it is empty (i.e. no dovecot index files in it). Of course, most people create folders and never delete them, but occasionally it's useful to do so. For the record, removing folders that contain messages (mbox files) works. -- William Astle Lexicom Ltd. Phone: +1-403-262-6610 Long Distance: 1-877-426-6277 Email: astle(a)lexi.net

1 0

Re: [Dovecot] Message read not sticking with Apple Mail / dovecot 1.0alpha5
by Hauke Fath 13 Jan '06

13 Jan '06

Am 13.01.2006 um 11:17 Uhr +0000 schrieb Michael Stevens: >I can read a mail, see Apple Mail flag it as read, quit, come back >later, and find the mail is marked unread again. It seems to also >happen sometimes when I switch folders or get new mail. > >I've not worked out what's triggering it yet. Anyone seen anything >like this? Same here - Eudora on MacOS 10.4, and Mozilla on NetBSD 3. It is not strictly repeatable, but happens frequently. hauke -- /~\ The ASCII Ribbon Campaign Hauke Fath \ / No HTML/RTF in email Institut für Nachrichtentechnik X No Word docs in email TU Darmstadt / \ Respect for open standards Ruf +49-6151-16-3281

1 0

[Dovecot] dovecot-ldap.conf for usernames/homes/UID/GID
by Paul Matthews 13 Jan '06

13 Jan '06

hi there, Im getting such a headache today, Ive added myself to three mailing lists trying to figure this out, okay here it goes. Ive got a Fedora Core 4 box running dovecot imap, squirrel mail, postfix, samba/winbind. Im running winbind to authenticate against Active Directory, Ive edited my /etc/pam.d/dovecot pam module so to let my users login with there Active directory password, but squirrel mail wont let them I think, let me stress the term, think is has something to do with there home directories, because I have some local users as well, they can login no issues & my users with the same usernames on unix and ADS can login with there ADS passwords Now Im looking at the dovecot webmin module and I see that Data source for users, homes and Ids is set to use Standard unix username database. There is now option of PAM like in Password authentication source. Although I do see LDAP, using config file. Can I set that to query Active directory ldap database and go there Data source for users, homes and Ids? If I can can someone tell me how to, if not can someone tell me what I need to do? Here is what I have so far with my /etc/dovecot-ldap.conf hosts = senior-server.school.cathedral.qld.edu.au:389 dn = cn=administrator,cn=users,dc=school,dc=cathedral,dc=qld,dc=edu,dc=au dnpass = wwvH@cs ldap_version = 3 base = dc=school,dc=cathedral,dc=qld,dc=edu,dc=au deref = never scope = subtree user_attrs = uid,homeDirectory,,uid,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(cn=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=posixAccount)(uid=%u)) CRYPT default_pass_scheme = CRYPT user_global_uid = 100 user_global_gid = 100

2 3

[Dovecot] QUOTA Imap Extension
by Brady Wetherington 13 Jan '06

13 Jan '06

Hi - long time lurker, very rare poster I understand Dovecot's support for mbox quotas is - well, not quite there yet. But I actually am not asking about that. I use vpopmail and qmail and Maildirs and was wondering about the QUOTA imap extension, which allows IMAP clients to query their quota settings. The reason I need to know about this is that I have a mailserver with a chunk of clients and their mail stores are getting large. And starting to exhaust my storage. I could just throw more storage at it - but they're not paying me for that level of storage, so I need to quota them. And my main source of business is one particular consulting company, so I pretty much have to do what they say, within reason, and they said, "Okay, you can quota everyone, so long as they can at least find out what their quota is in Webmail..." Which is pretty reasonable - quota'ing people and then not letting them know how close to their quota they are seems cruel, especially with the meager IQ's of my particular set of clients. Some research on my part has determined that there's an RFC for a QUOTA extension to IMAP, and there are plugins for my webmail program (Squirrelmail) which can display the user's quota usage there. Also, some mail clients are smart enough to also query the QUOTA extensions and let the user know how close they are to their max quota usage. I'm also planning a pretty decent-sized technology transition in the near future (switching to a shared-storage system with two servers, etc, etc), and I could be convinced to perhaps try and change my quotaing system at the same time - for instance, switching to filesystem quotas instead of vpopmail quotas, if that will help. The scary possibility that I guess I have to prepare myself for is that dovecot Just Doesn't Do It, and I need to figure out some other way of informing the clients of their quota usage - possibly a script that goes and recurses through maildirs and sends little emails if users are at a certain percentage of their actual usage, or something...I'm certainly not looking forward to writing that, but it's not a fate worse than death...

2 1

[Dovecot] were are my e-mails?
by Paul Matthews 13 Jan '06

13 Jan '06

hi there, i seam to have pretty much everything under control at the moment other than the ability to recieve email's ... i can send them though and i know they get there because i can login into webmin and look in my user's mail boxes and see the e-mails, but for some reason i can retrive them using squirrel mail, can someone tell me why?

1 0

[Dovecot] pop3 CAPA STLS and stupid clients
by Marten Lehmann 13 Jan '06

13 Jan '06

Hello, is it possible to disable the announcment of STLS in the CAPA-command for the pop3-daemon? I want to support pop3s, but only at port 995, not through the STLS on port 110. The reason for this is that some clients have problems with this and strange errors appear (e.g. older imap-libs) although they don't seem to have a problem with pop3s through port 995. Regards Marten

1 0

Re: [Dovecot] PAM Authentication issues with Dovecot
by david.kolts＠entouch.net 13 Jan '06

13 Jan '06

1 0

[Dovecot] IMAP subscriptions - how, for what and why?
by Tom Alsberg 13 Jan '06

13 Jan '06

Again, not a Dovecot issua - but can someone clarify better what IMAP subscriptions (SUBSCRIBE/UNSUBSCRIBE/LSUB) are and what they are used for? I've seen a few times in Microsoft mail clients, the options to subscribe to folders and to "show only subscribed folders". I haven't played much with them, though. But what's the actual point? Except for being returned in the list of LSUB, what else changes when doing a SUBSCRIBE to a mailbox? Are subscriptions supposed to be remembered by the server outside of the context of a session (so a client that connects to the server at some point and authenticates will already see in LSUB what a possibly other client has subscribed to in a previous session)? Clarifications appreciated, regards, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

5 4

Re: [Dovecot] PAM Authentication issues with Dovecot
by david.kolts＠entouch.net 12 Jan '06

12 Jan '06

2 1

[Dovecot] PAM Authentication issues with Dovecot
by david.kolts＠entouch.net 12 Jan '06

12 Jan '06

2 1

[Dovecot] Outlook Express / Namespaces
by Matthias Rieber 12 Jan '06

12 Jan '06

Hi, I'm planning to switch from courier-imap to dovecot. Everythings seems fine. I adjust the namespaces to avoid client side changes. This works with Thunderbird, but Outlook Express seems to have problmes with the path "INBOX.", that I've configured in the client settings. I can remove that path, but the folders will be sorted under the inbox. Is there something that I've done wrong? I'm using dovecot 1.0alpha5 matthias

2 2

[Dovecot] dovecot-lda: problems compiling
by nospam 12 Jan '06

12 Jan '06

I am trying to compile the dovecot lda and running into some problems. (compiling most recent version on Fedora core 4). I was able to compile the dovecot imap server just fine. However .. when I try to run configure in the lda package (after running autogen) it gets stuck on this line : + eval 'sed -f ./confstatm19105/subs-1.sed | sed -f ./confstatm19105/subs-2.sed | sed -f ./confstatm19105/subs-3.sed' ++ sed -f ./confstatm19105/subs-1.sed ++ sed -f ./confstatm19105/subs-2.sed ++ sed -f ./confstatm19105/subs-3.sed Basically it is getting stuck on the sed portion in config.status. Anyone run into this problem before ?

6 9

[Dovecot] Authentication failure - unknown user
by Anne Wilson 11 Jan '06

11 Jan '06

I'm trying to set up a temporary mailserver using Debian Sarge and Dovecot 1.0 with maildir format. My only previous experience has been on a simple imap server with mbox format. I have read the wiki documentation and searched the archives, but can't tie down my problem. The log tells me Info: passwd-file(anne) : unknown user. I have set auth_userdb = passwd-file /etc/imap.passwd auth_passdb = passwd-file /etc/imap.passwd and created the /etc/imap.passwd file as anne:{plain}mypassword:1000:1000::/home/anne What have I missed? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

1 0

[Dovecot] special variables
by Andrés Pereira 11 Jan '06

11 Jan '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Are there any plans to extend the special variables you can use for ldap query strings (%u,%n,etc)? For instance, say you have an ldap schema like this with multiple domains in a single top-level-domain: dc=domain_1,dc=tld_1 dc=domain_2,dc=tld_1 dc=domain_3,dc=tld_1 dc=domain_4,dc=tld_2 dc=domain_5,dc=tld_2 dc=domain_6,dc=tld_2 Now dovecot (latest CVS snapshot) offers, among others, the following variable: %d - domain part in user@domain, empty if there is no domain But, what if dovecot could offer something like this: %1-9 = domain tokens (%1 = tld, %2 = domain when %d = domain.tld) (actually, these variables are present in auth_ldap module for saslauthd) This way people could create a query like this (just an example): base = ou=some_ou,dc=%2,dc=%1 I know I could modify my ldap schema to: dc=domain_1.tld_1 dc=domain_2.tld_1 .... and it would be solved by using %d, however those "new" variables could be useful, what do you think? Cheers, - -- Andrés Pereira -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDxKDu7iUaNXa3Ta4RAitAAJ9oVoE51QjjSp6sQMe3qtkzwj9tygCcDfkj fnxUHKd/F6i9hjPoVDrHY18= =JdxG -----END PGP SIGNATURE-----

1 0

Re: [Dovecot] mbox assertion failure
by Timo Sirainen 10 Jan '06

10 Jan '06

On Sun, 2006-01-08 at 18:56 +0000, Michael Stevens wrote: > Jan 8 18:53:12 saigo dovecot: imap(mstevens): file > mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion > failed: (start_pos < data_size) For everyone else too, attached patch fixes this.

4 6

[Dovecot] Wild Idea for a feature
by Marc Perkel 10 Jan '06

10 Jan '06

OK - this is a wild idea and wondering what it would take to make it possible. I get a lot of email from a lot of different people about a lot of different issues. What I need is a way to do some server side presorting of email into specific folders. I can build a LOT of Mozilla rules but that is too cumbersome for what I have in mind. Here's what I'm thinking - one classification of email is "customers" and what I want to do is to drag an email into the customers server side folder and once I do that then any incoming email that comes from that person goes into the customers folder. I'm trying to envision how to code this and I think what I would need is if Dovecot were to create an external berkeley db file or mysql database of what is a list of email addresses contained in the folder that could be quickly searched for a match, that might do it. I think I could write a backent in Exim to handle it. This idea isn't yet well though out. I'm just throwing it out there to see if it's feasable. Thoughts?

5 4

[Dovecot] Thunderbird, IDLE, mailbox not always SELECTed
by Tom Alsberg 10 Jan '06

10 Jan '06

Hi there. Although it does not seem to be a Dovecot issue, I'm sending this here as people in this list may know better where exactly the problem is. I am working on Dovecot 1.0 (.alpha5, right now), with the aim that when Dovecot becomes stable we can put that into production. Recently after being more clear with the behaviour (I'm most into namespaces and mbox/maildir mixing issues, as you can see from my past messages), I have adopted a few (two, right now, with the third one gone) "Guinea-Pigs" to use the experimental IMAP server - people who very much want an IMAP service here and thus may help me test bugs. One of them reported, that he does not always see new mail. That user is using Mozilla Thunderbird (1.0.7). Looking a bit with him at the workings, I can see the issue. He has the IDLE extension enabled. However when sniffing the network, I see that sometimes when switching to another mailbox, the SELECT command is not always sent to the server. At the beginning, INBOX is (always) selected. Then another mailbox is selected, and usually a SELECT command is sent and the mailbox is seen. But going back to INBOX again, often no "SELECT INBOX" is seen on the wire. Then of course he sees no "EXISTS" or anything like that. I wonder if anyone else has observed this, or in some other way, that Thunderbird does not always show new mail. Sometimes it appears that a mailbox is selected in Thunderbird, and Thunderbird immediately (remembering from its cache) does a FETCH to show the message in the mailbox/folder, but not SELECT to update the folder itself. Can caching in Thunderbird be completely disabled, so that every action will be done against the server? Regards, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

[Dovecot] new 1.0 config and vpopmail
by Henti Smith 10 Jan '06

10 Jan '06

does anybody have a working config they can send me .. I just cannot seem to get this working. alternativly how can I set the debug so I can see where my config is wrong ? thanks Henti

2 2

[Dovecot] dovecot auth using passwd-file
by Brad 10 Jan '06

10 Jan '06

Im a dovecot newbie and need a little help with the passwd-like file auth mechanism in dovecot I got dovecot to work fine with regular /etc/passwd file auth .. so I wanted to start using another authentication store for virtual users. So .. I created a /etc/dovecot-passdb file and plopped in an encrypted password using md5crypt. Here are the appropriate lines from the dovecot.conf file auth_userdb = passwd-file /etc/dovecot-passdb auth_passdb = pam and here is the /etc/pam.d/dovecot file #%PAM-1.0 auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth So far .. no dice. Dovecot reports constant authentication failures. I fear that the dovecot-passdb file is wonky. Can anyone give me any pointers ?

3 3

[Dovecot] Maildir permissions, shared folders & postfix
by Stroller 09 Jan '06

09 Jan '06

Hi there, It's my understanding that shared folders can be implemented in the Dovecot IMAP server by simply symlinking one maildir to another, eg: $ ls -lan /home/DOMAIN/ned/.maildir/ total 40 drwx------ 9 10012 10000 440 Jan 9 04:23 . drwxr-xr-x 3 10012 10000 160 Jan 6 06:32 .. drwx------ 5 10012 10000 264 Jan 9 04:21 .Deleted Items drwx------ 5 10012 10000 232 Jan 6 06:32 .Drafts drwx------ 5 10012 10000 232 Jan 6 06:39 .Junk E-mail drwx------ 5 10012 10000 264 Jan 9 04:33 .Sent lrwxrwxrwx 1 10012 0 24 Jan 6 07:36 .Stroller -> /home/ stroller/.maildir/ drwx------ 2 10012 10000 336 Jan 9 04:23 cur -rw------- 1 10012 10000 268 Jan 9 04:23 dovecot-uidlist -rw------- 1 10012 10000 192 Jan 9 04:23 dovecot.index -rw------- 1 10012 10000 21504 Jan 9 04:23 dovecot.index.cache -rw------- 1 10012 10000 1908 Jan 9 04:23 dovecot.index.log drwx------ 2 10012 10000 48 Jan 9 04:23 new -rw------- 1 10012 10000 47 Jan 6 07:45 subscriptions drwx------ 2 10012 10000 48 Jan 9 04:23 tmp In the above configuration the user Ned has a mailbox "Stroller", in which he can read messages & stuff - I can log in as ned and drag & drop messages into this mailbox quite happily. I thought all was well with this type of shared configuration until I actually started to try setting it up for the info(a)ourdomain.com mailbox, and tried delivering messages to it. It seems that Postfix doesn't respect the permissions of the parent folder when delivering mail into it: # ls -ldn /home/info/.maildir/ drwxrwx--- 5 10021 10000 120 Jan 9 04:26 /home/info/.maildir/ # ls -ln /home/info/.maildir/ total 0 drwxrwx--- 2 10021 10000 48 Jan 9 04:26 cur drwxrwx--- 2 10021 10000 48 Jan 9 04:33 new drwxrwx--- 2 10021 10000 48 Jan 9 04:31 tmp # ls -ln /home/info/.maildir/new total 0 # cat HungUp.txt | sendmail info # sudo ls -l /home/info/.maildir/new total 4 # sudo ls -ln /home/info/.maildir/new total 4 -rw------- 1 10021 10000 1806 Jan 9 04:39 1136781544.V4804I3606cM633316.mail.domain.local How inconsiderate of Postfix to set secure permissions on the message it delivered!! I need the message to have 660 permissions so that others in the group can read it! At present this causes Squirrelmail to squeal & give nasty messages whenever a shared mailbox is accesses. Can anyone advise me how to resolve this, please? Stroller. PS: should you consider suggesting using Dovecot's "namespaces" type of shared mailbox, I'd be grateful if you could answer this first: http://dovecot.org/pipermail/dovecot/2005-December/010459.html

2 1

[Dovecot] POP3 only - why is cur/ growing?
by Wally Winchester 09 Jan '06

09 Jan '06

Hi, I use Sarge's dovecot for a pop3 mail collection server. IMAP is not used at all. It works well, but I would like to know why one of the accounts also keeps a copy of all e-mail copies in the cur/ folder? Thanks a lot, Wally -- Wally Winchester wally_winchester(a)fastmail.fm -- http://www.fastmail.fm - The way an email service should be

5 7

Re: [Dovecot] mbox assertion failure
by Timo Sirainen 08 Jan '06

08 Jan '06

On Sun, 2006-01-08 at 18:56 +0000, Michael Stevens wrote: > Hi. > > I'm running 1.0alpha5 on FreeBSD 5.3. I'm using mbox mailboxes. > > I keep getting: > > Jan 8 18:53:12 saigo dovecot: imap(mstevens): file > mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion > failed: (start_pos < data_size) > Jan 8 18:53:13 saigo dovecot: child 88663 (imap) killed with signal 6 This happens all the time with one specific mbox? Could you send it and the index files to me? You could put the mbox though http://dovecot.org/tools/mboxcrypt.pl

1 0

[Dovecot] Running dovecot-lda
by Linus Nordberg 08 Jan '06

08 Jan '06

Hi, I'm planning on setting up dovecot with dovecot-lda, for sieve support. What does the list have to say about versions to use? I prefer stability over features but sieve has to be there. Does anybody use the combination dovecot 1.0 alpha5 and dovecot-lda 0.1 with success or would you recommend running -lda from CVS? If so, is there any point in time that's better than another? And, will dovecot 1.0 alpha5 do for -lda from CVS? Finally, are there any release plans for dovecot-lda that can be shared? Thanks, -- Linus

3 3

Re: [Dovecot] invalid mbox files
by Harout S. Hedeshian 08 Jan '06

08 Jan '06

Timo Sirainen wrote .. > On Fri, 2006-01-06 at 19:17 -0700, Harout S. Hedeshian wrote: > > Timo Sirainen wrote .. > > > On Fri, 2006-01-06 at 12:11 -0700, Harout S. Hedeshian wrote: > > > > > From someone@somewhere Wed Jan 5 09:03:48 2005 > > > .. > > > > From - Sat, 6 Apr 2002 04:07:18 > > > > > > How have you added the mails to the mailbox? Dovecot can't handle that > > > kind of a timestamp. > > > > Interesting... The dovecot 0.99 I was using was packaged with Mandriva. > Is it possible that they added support for that time stamp themselves? > My mailbox files get generated one of three ways: thunderbird, fetchmail, > and postfix. I used thunderbird to convert my Outlook files to mbox files, > and thats the one that I sent. Here is a sample timestamp from postfix: > > It worked with 0.99 only because Dovecot didn't check errors as well as > 1.0 does. So it just parsed those timestamps as being invalid, and set > the received-time of mails wrong. > > > > I suppose I could add support for it.. > > > > Unless you know of a conversion utility, I think that would be a good > idea. I don't want to edit thousands of emails for multiple users manually > in order to use dovecot. > > Dovecot's current CVS version supports that timestamp format. How do I compile the CVS version? "configure" seems to be missing. I tried downloading the snapshot from 20060105 but that fails make: ~ main.c:14:25: dict-client.h: No such file or directory main.c: In function `main_init': main.c:162: warning: implicit declaration of function `dict_client_register' main.c: In function `main_deinit': main.c:206: warning: implicit declaration of function `dict_client_unregister' make[3]: *** [main.o] Error 1 make[3]: Leaving directory `/root/dovecot-1.0.alpha5/src/imap' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot-1.0.alpha5/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot-1.0.alpha5' make: *** [all] Error 2 The 20060107 snapshot won't ./configure : configure: creating ./config.status config.status: creating Makefile config.status: creating doc/Makefile config.status: creating src/Makefile config.status: creating src/lib/Makefile config.status: creating src/lib-sql/Makefile config.status: creating src/lib-auth/Makefile config.status: creating src/lib-charset/Makefile config.status: creating src/lib-dict/Makefile config.status: creating src/lib-imap/Makefile config.status: creating src/lib-index/Makefile config.status: creating src/lib-mail/Makefile config.status: creating src/lib-ntlm/Makefile config.status: creating src/lib-settings/Makefile config.status: creating src/lib-storage/Makefile config.status: creating src/lib-storage/index/Makefile config.status: creating src/lib-storage/index/maildir/Makefile config.status: creating src/lib-storage/index/mbox/Makefile config.status: creating src/lib-storage/index/dbox/Makefile config.status: creating src/lib-storage/subscription-file/Makefile config.status: creating src/lib-storage/register/Makefile config.status: creating src/auth/Makefile config.status: error: cannot find input file: src/dict/Makefile.in [root@www dovecot-1.0.alpha5]# make cd . && /bin/sh ./config.status config.h config.status: creating config.h make all-recursive make[1]: Entering directory `/root/dovecot-1.0.alpha5' Making all in src make[2]: Entering directory `/root/dovecot-1.0.alpha5/src' Making all in lib make[3]: Entering directory `/root/dovecot-1.0.alpha5/src/lib' Makefile:423: .deps/base64.Po: No such file or directory Makefile:424: .deps/bsearch-insert-pos.Po: No such file or directory Makefile:425: .deps/buffer.Po: No such file or directory Makefile:426: .deps/compat.Po: No such file or directory Makefile:427: .deps/data-stack.Po: No such file or directory Makefile:428: .deps/env-util.Po: No such file or directory Makefile:429: .deps/failures.Po: No such file or directory Makefile:430: .deps/fd-close-on-exec.Po: No such file or directory Makefile:431: .deps/fd-set-nonblock.Po: No such file or directory Makefile:432: .deps/fdpass.Po: No such file or directory Makefile:433: .deps/file-cache.Po: No such file or directory Makefile:434: .deps/file-dotlock.Po: No such file or directory Makefile:435: .deps/file-lock.Po: No such file or directory Makefile:436: .deps/file-set-size.Po: No such file or directory Makefile:437: .deps/hash.Po: No such file or directory Makefile:438: .deps/hex-binary.Po: No such file or directory Makefile:439: .deps/hex-dec.Po: No such file or directory Makefile:440: .deps/hmac-md5.Po: No such file or directory Makefile:441: .deps/home-expand.Po: No such file or directory Makefile:442: .deps/hostpid.Po: No such file or directory Makefile:443: .deps/imem.Po: No such file or directory Makefile:444: .deps/ioloop-epoll.Po: No such file or directory Makefile:445: .deps/ioloop-kqueue.Po: No such file or directory Makefile:446: .deps/ioloop-notify-dn.Po: No such file or directory Makefile:447: .deps/ioloop-notify-inotify.Po: No such file or directory Makefile:448: .deps/ioloop-notify-kqueue.Po: No such file or directory Makefile:449: .deps/ioloop-notify-none.Po: No such file or directory Makefile:450: .deps/ioloop-poll.Po: No such file or directory Makefile:451: .deps/ioloop-select.Po: No such file or directory Makefile:452: .deps/ioloop.Po: No such file or directory Makefile:453: .deps/iostream.Po: No such file or directory Makefile:454: .deps/istream-data.Po: No such file or directory Makefile:455: .deps/istream-file.Po: No such file or directory Makefile:456: .deps/istream-limit.Po: No such file or directory Makefile:457: .deps/istream-mmap.Po: No such file or directory Makefile:458: .deps/istream-seekable.Po: No such file or directory Makefile:459: .deps/istream.Po: No such file or directory Makefile:460: .deps/lib-signals.Po: No such file or directory Makefile:461: .deps/lib.Po: No such file or directory Makefile:462: .deps/md4.Po: No such file or directory Makefile:463: .deps/md5.Po: No such file or directory Makefile:464: .deps/mempool-alloconly.Po: No such file or directory Makefile:465: .deps/mempool-datastack.Po: No such file or directory Makefile:466: .deps/mempool-system.Po: No such file or directory Makefile:467: .deps/mempool-unsafe-datastack.Po: No such file or directory Makefile:468: .deps/mempool.Po: No such file or directory Makefile:469: .deps/mkdir-parents.Po: No such file or directory Makefile:470: .deps/mmap-anon.Po: No such file or directory Makefile:471: .deps/mmap-util.Po: No such file or directory Makefile:472: .deps/module-dir.Po: No such file or directory Makefile:473: .deps/network.Po: No such file or directory Makefile:474: .deps/ostream-crlf.Po: No such file or directory Makefile:475: .deps/ostream-file.Po: No such file or directory Makefile:476: .deps/ostream.Po: No such file or directory Makefile:477: .deps/primes.Po: No such file or directory Makefile:478: .deps/printf-upper-bound.Po: No such file or directory Makefile:479: .deps/process-title.Po: No such file or directory Makefile:480: .deps/randgen.Po: No such file or directory Makefile:481: .deps/read-full.Po: No such file or directory Makefile:482: .deps/restrict-access.Po: No such file or directory Makefile:483: .deps/restrict-process-size.Po: No such file or directory Makefile:484: .deps/safe-memset.Po: No such file or directory Makefile:485: .deps/safe-mkdir.Po: No such file or directory Makefile:486: .deps/sendfile-util.Po: No such file or directory Makefile:487: .deps/seq-range-array.Po: No such file or directory Makefile:488: .deps/sha1.Po: No such file or directory Makefile:489: .deps/str-sanitize.Po: No such file or directory Makefile:490: .deps/str.Po: No such file or directory Makefile:491: .deps/strescape.Po: No such file or directory Makefile:492: .deps/strfuncs.Po: No such file or directory Makefile:493: .deps/unix-socket-create.Po: No such file or directory Makefile:494: .deps/unlink-directory.Po: No such file or directory Makefile:495: .deps/unlink-lockfiles.Po: No such file or directory Makefile:496: .deps/utc-mktime.Po: No such file or directory Makefile:497: .deps/utc-offset.Po: No such file or directory Makefile:498: .deps/var-expand.Po: No such file or directory Makefile:499: .deps/write-full.Po: No such file or directory make[3]: *** No rule to make target `.deps/write-full.Po'. Stop. make[3]: Leaving directory `/root/dovecot-1.0.alpha5/src/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot-1.0.alpha5/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot-1.0.alpha5' make: *** [all] Error 2 It seems like the code is horribly broken. All of the nightly snapshots except for 20060107 (which won't configure) fail with "main.c:14:25: dict-client.h: No such file or directory" it does this for src/imap/main.c AND src/pop3/main.c . I tried commenting out any lines that had to do with "dict-client.h" "dict_client_register();" and "dict_client_unregister();" inside the two files and it would compile those files but it would fail in src/deliver claiming that it is too old? make[3]: Entering directory `/root/dovecot-1.0.alpha5/src/deliver' ~ deliver.c:4:2: #error This program is somewhat out of date, use dovecot-lda instead make[3]: *** [deliver.o] Error 1 make[3]: Leaving directory `/root/dovecot-1.0.alpha5/src/deliver' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/dovecot-1.0.alpha5/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/dovecot-1.0.alpha5' make: *** [all] Error 2 Harout Hedeshian

3 5

[Dovecot] Documentation updates in Wiki
by Timo Sirainen 08 Jan '06

08 Jan '06

I started writing a new front page for wiki.dovecot.org: http://wiki.dovecot.org/NewIndex This is partially based on the comments in Documentation thread starting from here: http://dovecot.org/list/dovecot/2005-July/008076.html "A simple Dovecot installation" section is pretty much finished from my point of view. I hope it's clear enough for anyone wanting to install a working Dovecot server. Suggestions are welcome of course. You're also welcome to just edit the pages directly. I'll get email notifications of all page changes, so if I see changes that I don't think belong in there, I'll just remove them and maybe move them elsewhere (so don't add too much text without asking :). I'm not sure about what exactly should be visible in the front page. Currently there's probably too much. But I think it's better to show more than too little, so that new people can just look at the page and quickly pick up the interesting keywords without having to click through multiple pages. Maybe most of the sub-sections in "full guide" section could be listed only under those root sections. So that it becomes something like: * Starting guidelines * Authentication configuration * Mail configuration * Namespaces * Shared folders * SSL * POP3 * Dovecot LDA * Full configuration file reference * Examples / Scenarios I'd leave namespaces and shared folders there so that they can be easily found. I'm not sure where to put "full configuration file reference" or what exactly to call it. The same goes for Examples/Scenarios. Tuning should maybe be only part of "full guide". "Generic information about mail servers" is meant for discussion of mail server components, protocols, etc. without being too much Dovecot-specific. It's partially for "mail server newbies", but also would contain some "hard core" information about how things really work (mailbox format and user authentication especially). Anyway, if you have time please start adding the missing pages and writing to them. Even if you only give a FIXME-list that others can then fill out :) My school starts again at monday, and I'll be too busy to do anything else than that and work for the rest of January (after that only finals, yay).

2 1

[Dovecot] fastbind patch -> auth_bind_userdn patch (attached)
by Geff 07 Jan '06

07 Jan '06

Let me know how you like this one. This assumes one config parameter. The non-null of auth_bind_userdn overrides auth_bind = yes. I'm using this patch now on cvs head. Comments are always welcome. Thanks much, Geff

2 4

[Dovecot] Questions regarding quota
by Stian Jordet 07 Jan '06

07 Jan '06

Hi, I have some trouble trying to test the quota plugin. First off all, it says in the wiki: "Dovecot 1.0 supports quota using a quota plugin. It's currently discussed in Dovecot LDA page and it supports only very simple quota calculation which is suitable only for mboxes. Maildir++ quota support will come later." Does that mean that it won't work at all with Maildir++, or just that it's slow? Second; there are two plugins? One in src/plugins/quota and one ine src/plugins/imap-quota. What's the difference? Is one for imap-quota and the other for fs-quota? (I would love that!) But third and most importantly; I can't get it too work. I'm using CVS from tonight (which fixed the missing symbol bug). But neither when I'm using static userdb nor LDAP as explained in the wiki I can't get it to work. I'm not really sure of the getquota syntax, but whatever I try, I get: a OK No quota. So please, enlighten me! :) Best regards, Stian

5 9

Re: [Dovecot] invalid mbox files
by Harout S. Hedeshian 07 Jan '06

07 Jan '06

I am resending this because I have not gotten a response in a few days. Help is appreciated! Timo Sirainen wrote .. > On Fri, 2005-12-30 at 17:50 -0700, Harout S. Hedeshian wrote: > > I recently upgraded from dovecot 0.9x to 1.0.5-Aplha and now when ever > folders are opened (in IMAP), it keeps saying invalid mbox files. It worked > fine in 0.99.x. It is detecting the right mbox files because it lists the > folders and the subscriptions correctly. I am using "default_mail_env > = mbox:~/mail/:INBOX=/var/mail/%u" in the config file, but I get the same > error with "Detect automatically". It generates nothing in the log files > so I am lost!! I tried both outlook and thunderbird but same results. > > Invalid mbox file error comes only if the first line of the mbox file > isn't valid. What does it look like? It should be something like: > > From someone@somewhere Wed Jan 5 09:03:48 2005 > > 0.99.x Dovecot didn't accept broken From-lines either, but it might have > had slightly different logic in checking what's valid and what's not. Here is a sample file generated by postfix. Note: it is NOT censored or edited. What you see is the real thing. >From - Sat, 6 Apr 2002 04:07:18^M Return-Path: <List-owner(a)mail.fuelcellstore.com> Received: from mail.fuelcellstore.com ([207.174.23.2]) by rwcrgwc55.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020406013417.LNRM3313.rwcrgwc55.attbi.com(a)mail.fuelcellstore.com> for <haroutetoot(a)attbi.com>; Sat, 6 Apr 2002 01:34:17 +0000 Received: from saa01.saleebaadams.com.au [203.59.141.98] by mail.revealmail.com with ESMTP (SMTPD32-7.06) id A64E1BA01F8; Fri, 05 Apr 2002 17:50:22 -0700 Received: from saa01.saleebaadams.com.au (10.0.0.13 [10.0.0.13]) by saa01.saleebaadams.com.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 1KDV523W; Sat, 6 Apr 2002 08:45:25 +0800 Received: by saa01.saleebaadams.com.au (Microsoft Exchange Connector for POP3 Mailboxes 4.50.2113) with SMTP (Global POP3 Download) id MSG04062002-084518-2751.MMD@SAA01; Sat, 6 Apr 2002 08:45:18 +0800 Return-Path: <List-owner(a)mail.fuelcellstore.com> Delivered-To: saa(a)iinet.net.au Received: (qmail 28777 invoked by uid 666); 6 Apr 2002 00:24:40 -0000 Delivered-To: saa-saleebaadamscomau-n.juniper(a)saleebaadams.com.au X-Envelope-To: <n.juniper(a)saleebaadams.com.au> Received: (qmail 28767 invoked by uid 666); 6 Apr 2002 00:24:39 -0000 Received: from unknown (HELO mail.fuelcellstore.com) (207.174.23.2) by mail.iinet.net.au with SMTP; 6 Apr 2002 00:24:39 -0000 Received: from mtiwmhc23.worldnet.att.net [204.127.131.48] by mail.revealmail.com with ESMTP (SMTPD32-7.06) id AD4D1690192; Fri, 05 Apr 2002 17:11:57 -0700 Received: from jason ([12.81.167.50]) by mtiwmhc23.worldnet.att.net (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020406001120.RBFM8815.mtiwmhc23.worldnet.att.net@jason>; Sat, 6 Apr 2002 00:11:20 +0000 Reply-To: fuelcell(a)fuelcellstore.com From: "fuelcell" <fuelcell(a)fuelcellstore.com> To: list(a)mail.fuelcellstore.com Subject: FuelCellStore.com Date: Fri, 5 Apr 2002 17:11:08 -0700 Message-ID: <001d01c1dcff$8f6c5fa0$cacbfea9@jason> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal X-Sender: List-owner(a)mail.fuelcellstore.com Precedence: bulk Sender: List-owner(a)mail.fuelcellstore.com Content-transfer-encoding: 8bit X-IMAPbase: 1135543792 1 Status: O X-UID: 1 Content-Length: 150475 X-Keywords: Dear Fuel Cell Enthusiast,^M ^M FuelCellStore.com would like to tell you about several new fuel cell products and our redesigned website. ^M ^M * ^M One of which is the new 500W unit that is available for residential back up power, or remote low power primary needs. These units can be stacked up to 1500W and self-starts upon grid failure ~V provi ding critical power for nominal apparatus and remote applications. You will find a link to this product at www.fuelcellstore.com^M * ^M Bench Top Methanol Reformer capable of generating ultra-pure hydrogen from methanol and water for University and Research Labs. Please reply for more information. ^M * ^M A fuel cell powered remote control car with metal hydride storage. ^M ^M FuelCellStore.com has many new educational products and a new nav bar to help you find the products you are looking for. Please check out our Student and Teacher section at www.fuelcellstore.com/products.htm l^M Please let us know what you think of the new site structure and any feedback would be great. ^M ^M You have received this message because you have contacted fuelcellstore.com in the past and asked to receive FuelCellStore.com news. If you would like to unsubscribe from our mailing please reply to this mes sage with unsubscribe in the subject heading. ^M ^M Sincerely,^M ^M FuelCellStore.com^M PO Box 4038^M Boulder, CO 80306-4038^M Harout Hedeshian harout(a)hedeshian.net 720 - 261 - 3548

3 3

Re: [Dovecot] invalid mbox files
by Harout S. Hedeshian 07 Jan '06

07 Jan '06

Timo Sirainen wrote .. > On Fri, 2006-01-06 at 19:17 -0700, Harout S. Hedeshian wrote: > > Timo Sirainen wrote .. > > > On Fri, 2006-01-06 at 12:11 -0700, Harout S. Hedeshian wrote: > > > > > From someone@somewhere Wed Jan 5 09:03:48 2005 > > > .. > > > > From - Sat, 6 Apr 2002 04:07:18 > > > > > > How have you added the mails to the mailbox? Dovecot can't handle that > > > kind of a timestamp. > > > > Interesting... The dovecot 0.99 I was using was packaged with Mandriva. > Is it possible that they added support for that time stamp themselves? > My mailbox files get generated one of three ways: thunderbird, fetchmail, > and postfix. I used thunderbird to convert my Outlook files to mbox files, > and thats the one that I sent. Here is a sample timestamp from postfix: > > It worked with 0.99 only because Dovecot didn't check errors as well as > 1.0 does. So it just parsed those timestamps as being invalid, and set > the received-time of mails wrong. > > > > I suppose I could add support for it.. > > > > Unless you know of a conversion utility, I think that would be a good > idea. I don't want to edit thousands of emails for multiple users manually > in order to use dovecot. > > Dovecot's current CVS version supports that timestamp format. Okay. Thanks. I will try getting the CVS version. Harout Hedeshian

1 0

[Dovecot] Passwd file location
by Tracy Phillips 07 Jan '06

07 Jan '06

Hi, I am trying to access my passwd file like this: passdb passwd-file { args = /usr/local/etc/vmail/%d/passwd } Is that not possible. I keep getting an error when trying to login. I do not get much in my log files to help me debug it. Thanks, Tracy

2 1

[Dovecot] FETCH FLAGS in response to SORT and SEARCH commands
by Michael Doppler 06 Jan '06

06 Jan '06

Hi, I am getting IMAP FETCH FLAGS in response to SORT and SEARCH commands for my INBOX. See the following transcript between dovecot (marked with S:) and an imap client (marked with C:) for an example SEARCH command. C: A004 UID SEARCH CHARSET ISO-8859-1 ALL TEXT {4} C: test S: + OK S: * SEARCH 5 13 20 21 22 23 24 30 37 39 56 64 77 82 93 94 96 103 109 110 118 135 136 158 160 165 171 174 175 177 180 181 190 198 207 209 210 212 220 221 233 237 242 248 250 253 256 257 261 270 278 281 294 296 301 302 303 304 305 309 310 317 318 320 323 330 331 333 342 343 352 355 356 357 365 387 390 394 407 412 416 426 428 432 437 450 451 454 459 460 465 468 470 477 482 484 488 493 500 522 524 526 529 530 537 541 571 575 580 597 604 666 689 730 738 741 742 743 746 750 751 752 753 754 755 758 759 760 762 763 764 766 767 768 770 772 773 782 788 797 798 829 831 832 835 836 842 854 863 864 865 866 868 869 871 874 880 881 891 943 944 945 954 957 962 963 964 965 968 970 971 973 974 985 986 987 S: * 307 FETCH (FLAGS (\Seen $NotJunk $MDNSent)) S: * 381 FETCH (FLAGS (\Seen $NotJunk $MDNSent)) S: * 971 FETCH (FLAGS (\Seen $NotJunk NonJunk JunkRecorded)) S: * 307 FETCH (FLAGS (\Seen $NotJunk $MDNSent)) S: * 381 FETCH (FLAGS (\Seen $NotJunk $MDNSent)) S: * 971 FETCH (FLAGS (\Seen $NotJunk NonJunk JunkRecorded)) S: * 971 FETCH (FLAGS (\Seen $NotJunk NonJunk JunkRecorded)) S: * 307 FETCH (FLAGS (\Seen $NotJunk $MDNSent)) S: * 381 FETCH (FLAGS (\Seen $NotJunk $MDNSent)) S: * 971 FETCH (FLAGS (\Seen $NotJunk NonJunk JunkRecorded)) S: A004 OK Search completed Mozilla Thunderbird and Apple Mail seem to be able to cope with this, but squirrelmail chokes when it receives those flags. I get them only for my INBOX and not for other folders like sent mail, so the behaivour seems to depend on the content of the folder. It occurrs at least with dovecot 1.0alpha4 and 1.0alpha5 using maildir. I have not tested other versions / mbox format. Is this behaviour expected? regards, Michael

2 4

[Dovecot] Dovecot Version Numbers - Let's drop the Alpha?
by Marc Perkel 04 Jan '06

04 Jan '06

I'd like to make a suggestion. Let's drop the Alpha and come out with an official version 1.0. Here's my reasons. The 0.9x version are obsolete and people should be using the 1.0 Alpha versions which seem to me to do everything the previous versions did and more. It's as full featured and stable as all other IMAP servers and in my opinion is ready to be called 1.0. The "Alpha" label scares people off and with the 0.9x version being obsolete I think it creates confusion for new users. It created confusion for me when I converted to dovecot, and distros are less ,ikely to include versions with the Alpha label. Once you go to 1.0 you can start a 1.1 alpha series and finish it up. I know Timo has high standards but as a marketing issue I think that the Alpha label needs to go to get people to accept and use 1.0 in production. Thoughts? -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

16 18

[Dovecot] problems connecting to the Problems connecting to mysql
by Alfonso Fernández Vázquez 04 Jan '06

04 Jan '06

Hi, I'm trying to setup a mailserver running postfix and dovecot with mysql as database backend. Postfix is already running and delivers mails just fine. Unfortunately, dovecot has great problems connecting to the database (using username + password). Found that two threads about the same issue but none of them solves the problem http://dovecot.org/list/dovecot/2005-April/006770.html http://dovecot.org/list/dovecot/2005-August/008394.html I am using: dovecot-1.0.alpha5 mysql 5.0.17-1 Please, can anyone help? Thanks in advance, Alfonso

5 4

[Dovecot] Status of your Dovecot GSSAPI patch
by Fredrik Tolf 04 Jan '06

04 Jan '06

Hi! I saw your discussion on the Dovecot list back in October about a SASL GSSAPI patch for Dovecot. I'd like to ask what the status is on it. Are you still working on it? Thanks for your attention! Fredrik Tolf

2 2

[Dovecot] Intermittent "Password Mismatch" errors
by dan＠ipws.com 03 Jan '06

03 Jan '06

Hello - I have had a problem the last few days with Dovecot reporting intermittent "Password Mismatch" errors for pretty much every client. Not all the time, maybe 1 out of every 10 connections. I cannot pinpoint where the process may be failing. I am using a MySQL backend to store user information in, and Dovecot queries that database directly. It works fine, but it seems as if Dovecot has a problem connecting to the SQL server for this information, instead of doing something smart, it just reports a password mismatch. I've turned on debugging and verbose logging, but I can't see exactly *why* the process fails on occasion. MySQL is tuned appropriately, and there's no reason why Dovecot cannot connect to the server. I'm wondering if anyone has seen this, and if so, what they've done about it. Because honestly, I'm lost. Thanks -dant

1 0

[Dovecot] very slow imap opens in pine after moving maildirs to new drive
by Dave Lugo 03 Jan '06

03 Jan '06

Hi, I've been running dovecot-0.99.10 for the past several years, with virtually no problems. Lately, I noticed that the filesystem holding my users' imap maildirs was getting close to full. So... last night, I used tar to copy /var/spool/imap to a new drive (9G scsi, reiserfs) that I then mounted under /var/spool/imap (after moving the old dir aside). After the move, what would take pine a handful of seconds, with the load average barely breaking .40, now takes several minutes, with a load average spike to nearly 3. I must admit to being rather puzzled by this, as I would not have expected the move to result in worse performance. Do I need to figure out what the index file names are, and delete those? Any suggestions greatly appreciated - as even closing pine now takes nearly 5 minutes, whereas when dovecot talks to my old imap dir (I've tested this), closing the session takes no more than 10 seconds. server is Mandrake 9.1, 2.4.21-0.13mdkenterprise, P4 2.6GHz, 1G RAM 9G U2W SCSI system disk, 9G U2W SCSI (and big*ss IDE drive for /users). Each of the scsi drives is on its own aha-2940UW controller. Filesystem on old imap location (/var filesystem) is reiserfs, same as that on new dedicated disk. Thanks much, Dave -- -------------------------------------------------------- Dave Lugo dlugo(a)etherboy.com LC Unit #260 TINLC Have you hugged your firewall today? No spam, thanks. -------------------------------------------------------- Are you the police? . . . . No ma'am, we're sysadmins.

3 4

[Dovecot] fast bind patch for ldap passwords
by Geff 03 Jan '06

03 Jan '06

All, I'm not sure if I sent this in yet or not. Basically it works like this: if you set "fast_bind = yes" it overrides auth_bind. And requires that you set userdn. Example config: fast_bind = yes userdn = cn=%u,ou=people,o=dovecot I'm using the patch right now on the cvs head branch. Comments are welcome. Geff

3 3

[Dovecot] another migration problem from courier with Outlook 2003
by Andreas Mimz 02 Jan '06

02 Jan '06

So I'm still trying to figure out a way to migrate from courier-imap to dovecot but I got stuck again... basically all of the clients are working now (more or less) - but when using outlook 2003 I don't see any email! the folders are there - just no emails! I think there's still a namespace problem somehow... I've attached the rawlog .in and .out files... when I select the Spam folder outlook tries to access "Posteingang.Spam" which should be "INBOX.Spam", shouldn't it?? my namespace config: namespace private { separator = . location = maildir:~/Maildir prefix=INBOX. inbox = yes hidden = no } maybe anyone can help me out?! thanks a lot! aexd IDLE DONE tgr8 LIST "" "" qqvt IDLE DONE nlvq LSUB "" "*" wjll STATUS "INBOX.Drafts" (UNSEEN) yhuw STATUS "INBOX.Gesendete Objekte" (UNSEEN) epjg STATUS "INBOX.Junk E-mail" (UNSEEN) r2bz STATUS "INBOX.Sent" (UNSEEN) 16iu STATUS "INBOX.Spam" (UNSEEN) 3vki STATUS "INBOX.Spam.Erkennungsfehler" (UNSEEN) dstc STATUS "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" (UNSEEN) 64bl STATUS "INBOX.Spam.Erkennungsfehler.nicht erkannt" (UNSEEN) gwa0 STATUS "INBOX.Spam.treffer" (UNSEEN) 31sy STATUS "INBOX.Spam.verdacht" (UNSEEN) u9fg STATUS "INBOX.Trash" (UNSEEN) dypb IDLE DONE 4u5q LIST "" "INBOX" x8nb LSUB "" "*" dja3 LIST "" "INBOX" x40b LSUB "" "*" eg5t IDLE DONE mj6l SELECT "Posteingang" uj7v IDLE DONE 7w1o SELECT "Posteingang.Spam" zuyg IDLE DONE xsoy SELECT "Posteingang" kiuz IDLE DONE dx73 LSUB "" "*" 4qnd STATUS "INBOX.Drafts" (UNSEEN) 61vj STATUS "INBOX.Gesendete Objekte" (UNSEEN) jhaw STATUS "INBOX.Junk E-mail" (UNSEEN) x7t3 STATUS "INBOX.Sent" (UNSEEN) gipp STATUS "INBOX.Spam" (UNSEEN) cx56 STATUS "INBOX.Spam.Erkennungsfehler" (UNSEEN) yw81 STATUS "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" (UNSEEN) nx8w STATUS "INBOX.Spam.Erkennungsfehler.nicht erkannt" (UNSEEN) 1nfc STATUS "INBOX.Spam.treffer" (UNSEEN) wf7r STATUS "INBOX.Spam.verdacht" (UNSEEN) 9y3i STATUS "INBOX.Trash" (UNSEEN) al6r IDLE DONE fcd9 LSUB "" "*" dpxa STATUS "INBOX.Drafts" (UNSEEN) 6fsv STATUS "INBOX.Gesendete Objekte" (UNSEEN) 8nyj STATUS "INBOX.Junk E-mail" (UNSEEN) lsnf STATUS "INBOX.Sent" (UNSEEN) gmym STATUS "INBOX.Spam" (UNSEEN) u7nd STATUS "INBOX.Spam.Erkennungsfehler" (UNSEEN) r8zi STATUS "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" (UNSEEN) hrja STATUS "INBOX.Spam.Erkennungsfehler.nicht erkannt" (UNSEEN) 9keb STATUS "INBOX.Spam.treffer" (UNSEEN) iwfc STATUS "INBOX.Spam.verdacht" (UNSEEN) 1pd6 STATUS "INBOX.Trash" (UNSEEN) bhfu IDLE * OK [RAWLOG TIMESTAMP] 2006-01-02 00:01:31 + idling aexd OK Idle completed. tgr8 OK List completed. + idling qqvt OK Idle completed. * LSUB () "." "INBOX.Trash" * LSUB () "." "INBOX.Sent" * LSUB () "." "INBOX.Drafts" * LSUB () "." "INBOX.Spam" * LSUB () "." "INBOX.Gesendete Objekte" * LSUB () "." "INBOX.Junk E-mail" * LSUB () "." "INBOX.Spam.treffer" * LSUB () "." "INBOX.Spam.verdacht" * LSUB () "." "INBOX.Spam.Erkennungsfehler" * LSUB () "." "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" * LSUB () "." "INBOX.Spam.Erkennungsfehler.nicht erkannt" nlvq OK Lsub completed. * STATUS "INBOX.Drafts" (UNSEEN 0) wjll OK Status completed. * STATUS "INBOX.Gesendete Objekte" (UNSEEN 0) yhuw OK Status completed. * STATUS "INBOX.Junk E-mail" (UNSEEN 0) epjg OK Status completed. * STATUS "INBOX.Sent" (UNSEEN 0) r2bz OK Status completed. * STATUS "INBOX.Spam" (UNSEEN 0) 16iu OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler" (UNSEEN 0) 3vki OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" (UNSEEN 0) dstc OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler.nicht erkannt" (UNSEEN 0) 64bl OK Status completed. * STATUS "INBOX.Spam.treffer" (UNSEEN 0) gwa0 OK Status completed. * STATUS "INBOX.Spam.verdacht" (UNSEEN 0) 31sy OK Status completed. * STATUS "INBOX.Trash" (UNSEEN 0) u9fg OK Status completed. + idling dypb OK Idle completed. 4u5q OK List completed. * LSUB () "." "INBOX.Trash" * LSUB () "." "INBOX.Sent" * LSUB () "." "INBOX.Drafts" * LSUB () "." "INBOX.Spam" * LSUB () "." "INBOX.Gesendete Objekte" * LSUB () "." "INBOX.Junk E-mail" * LSUB () "." "INBOX.Spam.treffer" * LSUB () "." "INBOX.Spam.verdacht" * LSUB () "." "INBOX.Spam.Erkennungsfehler" * LSUB () "." "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" * LSUB () "." "INBOX.Spam.Erkennungsfehler.nicht erkannt" x8nb OK Lsub completed. dja3 OK List completed. * LSUB () "." "INBOX.Trash" * LSUB () "." "INBOX.Sent" * LSUB () "." "INBOX.Drafts" * LSUB () "." "INBOX.Spam" * LSUB () "." "INBOX.Gesendete Objekte" * LSUB () "." "INBOX.Junk E-mail" * LSUB () "." "INBOX.Spam.treffer" * LSUB () "." "INBOX.Spam.verdacht" * LSUB () "." "INBOX.Spam.Erkennungsfehler" * LSUB () "." "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" * LSUB () "." "INBOX.Spam.Erkennungsfehler.nicht erkannt" x40b OK Lsub completed. + idling eg5t OK Idle completed. mj6l NO Unknown namespace. + idling uj7v OK Idle completed. 7w1o NO Unknown namespace. + idling zuyg OK Idle completed. xsoy NO Unknown namespace. + idling kiuz OK Idle completed. * LSUB () "." "INBOX.Trash" * LSUB () "." "INBOX.Sent" * LSUB () "." "INBOX.Drafts" * LSUB () "." "INBOX.Spam" * LSUB () "." "INBOX.Gesendete Objekte" * LSUB () "." "INBOX.Junk E-mail" * LSUB () "." "INBOX.Spam.treffer" * LSUB () "." "INBOX.Spam.verdacht" * LSUB () "." "INBOX.Spam.Erkennungsfehler" * LSUB () "." "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" * LSUB () "." "INBOX.Spam.Erkennungsfehler.nicht erkannt" dx73 OK Lsub completed. * STATUS "INBOX.Drafts" (UNSEEN 0) 4qnd OK Status completed. * STATUS "INBOX.Gesendete Objekte" (UNSEEN 0) 61vj OK Status completed. * STATUS "INBOX.Junk E-mail" (UNSEEN 0) jhaw OK Status completed. * STATUS "INBOX.Sent" (UNSEEN 0) x7t3 OK Status completed. * STATUS "INBOX.Spam" (UNSEEN 0) gipp OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler" (UNSEEN 0) cx56 OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" (UNSEEN 0) yw81 OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler.nicht erkannt" (UNSEEN 0) nx8w OK Status completed. * STATUS "INBOX.Spam.treffer" (UNSEEN 0) 1nfc OK Status completed. * STATUS "INBOX.Spam.verdacht" (UNSEEN 0) wf7r OK Status completed. * STATUS "INBOX.Trash" (UNSEEN 0) 9y3i OK Status completed. + idling al6r OK Idle completed. * LSUB () "." "INBOX.Trash" * LSUB () "." "INBOX.Sent" * LSUB () "." "INBOX.Drafts" * LSUB () "." "INBOX.Spam" * LSUB () "." "INBOX.Gesendete Objekte" * LSUB () "." "INBOX.Junk E-mail" * LSUB () "." "INBOX.Spam.treffer" * LSUB () "." "INBOX.Spam.verdacht" * LSUB () "." "INBOX.Spam.Erkennungsfehler" * LSUB () "." "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" * LSUB () "." "INBOX.Spam.Erkennungsfehler.nicht erkannt" fcd9 OK Lsub completed. * STATUS "INBOX.Drafts" (UNSEEN 0) dpxa OK Status completed. * STATUS "INBOX.Gesendete Objekte" (UNSEEN 0) 6fsv OK Status completed. * STATUS "INBOX.Junk E-mail" (UNSEEN 0) 8nyj OK Status completed. * STATUS "INBOX.Sent" (UNSEEN 0) lsnf OK Status completed. * STATUS "INBOX.Spam" (UNSEEN 0) gmym OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler" (UNSEEN 0) u7nd OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler.irrtuemlich Erkannt" (UNSEEN 0) r8zi OK Status completed. * STATUS "INBOX.Spam.Erkennungsfehler.nicht erkannt" (UNSEEN 0) hrja OK Status completed. * STATUS "INBOX.Spam.treffer" (UNSEEN 0) 9keb OK Status completed. * STATUS "INBOX.Spam.verdacht" (UNSEEN 0) iwfc OK Status completed. * STATUS "INBOX.Trash" (UNSEEN 0) 1pd6 OK Status completed. + idling

1 0

[Dovecot] Using dovecot auth with Postfix
by Kim Culhan 01 Jan '06

01 Jan '06

Attempting to setup smtpd auth for Postfix using the Dovecot authorization unix socket. Some info is at: http://www.postfix.org/SASL_README.html To enable operation when Postfix is chrooted, a method from the reference above is to locate the socket at: /var/spool/postfix/private/auth To do this, I have this configuration in dovecot.conf: # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section auth default_with_listener { mechanisms = plain passdb passwd { } userdb pam { } socket listen { master { path = /var/spool/postfix/private/dovecot-auth-master # WARNING: Giving untrusted users access to master socket may be a # security risk, don't give too wide permissions to it! mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = group = } client { path = /var/spool/postfix/private/dovecot-auth-master mode = 0660 } } } With this configuration Dovecot writes this to the log at startup: dovecot: Dec 31 17:04:32 Error: child 3536 (auth) returned error 89 dovecot: Dec 31 17:25:34 Error: Auth process died too early - shutting down dovecot: Dec 31 17:25:34 Error: auth(default_with_listener): Unknown userdb driver 'pam' (typo, or Dovecot was built without support for it? Check with dovecot --build-options) Before modifying the setup for this auth function, pam authentication was working fine. Also, Dovecot will make /auth owned by root which Postfix considers a 'fatal' problem. Should it be setup to run as user Postfix ? Any help here is vy appreciated -kim -- w8hdkim(a)gmail.com

4 4

[Dovecot] LDAP - authentication with bind vs. password attribute read
by Geff 01 Jan '06

01 Jan '06

Any word on this patch? http://www.dovecot.org/list/dovecot/2004-June/003867.html If not, I'll take a stab at it. Geff

2 3