- dovecot - dovecot.org

[Dovecot] ssl-parameters.dat ownership problems on MacOS X
by Lars Skovgaard 09 Apr '06

09 Apr '06

Hi all, I've been having some issues with the ssl-parameters.dat file from dovecot 1.0 beta 2 on MacOS X 10.4.6 client. As I understand it, the user/group on the file should be root:wheel, and I have changed ownership accordingly. However, on occation this gets set to root:dovecot by some process I haven't yet identified, which causes the ssl-parameters.dat file to be regenerated once every 10 minutes instead of the default. Does anyone have an idea what is going on, or how I can avoid this? Best, Lars

1 0

[Dovecot] Feature Request: Config Dump
by Charles Marcus 09 Apr '06

09 Apr '06

Hello, One of the less friendly lists I am on is the Postfix list, but one of the features that Postfix has, and the use of which is required when asking for help on their list, is a command called 'postconf', which simply dumps the current configuration parameters into a neat, orderly output that you can then cut-n-paste into an email request for help. The postfix guys won't even try to address a problem without this output (as opposed to snippets from config files), combined with log snippets of the failing behavior (as opposed to bounced message text, or 'it don't work' comments). So, what I'd like to see is something similar - a command that I can issue that will cause Dovecot to dump all of the configuration parameters it is currently using in a neat, orderly arrangement. This would dramatically help individual users in troubleshooting their own problems, as well as help people on this list help others. It would totally eliminate all of the 'what is xys set to' questions back and forth. But I'm more interested in how it will simply help me to see how I have it configured, and allow me to easily spot conflicting or misconfigured parameters. -- Best regards, Charles

4 5

[Dovecot] dovecot NTLM authentication
by Lior Okman 09 Apr '06

09 Apr '06

Hi, I'm trying to configure DoveCot to allow NTLM authentication. I've successfully authenticated with Outlook 2003 against Dovecot when the passdb backend used to store the password is a passwd-file. It doesn't matter if the passwd-file contains plain or NTLM encrypted passwords. When I compare the NTLM hash provided by the dovecotpw utility to the one I have in my SAMBA ldap, it appears to be exactly the same. When I use the LDAP passdb backend, I can see in the log file that dovecot has received the correct NTLM hash value, but outlook fails to authenticate successfully. I'm using the debianized dovecot version v1.0.beta2. I can post my dovecot-ldap.conf file, if it will help. Can anybody help me configure my dovecot to allow Outlook to perform NTLM authentication when the password database is in LDAP? Thanks, Lior Okman

3 8

[Dovecot] fcntl error
by Doug Dalton 09 Apr '06

09 Apr '06

Error: imap(user): fcntl() failed with mbox file /var/mail/user: Resource temporarily unavailable The user is using Outlook, I am not sure what the issue is, I am running Freebsd 6.0 and Dovecot 1.0.3 The user report that the gets about 60 of his inbox then I see this error in my error log. He is only running one instance of outlook Doug

2 1

[Dovecot] Digest-MD5 authentication problems
by Trev Peterson 09 Apr '06

09 Apr '06

Hello, I have dovecot setup to pull passwords stored in plain from a database. My allowed authentication mechanisms are cram-md5 and digest-md5. Cram works but digest fails on my evolution client with and authentication failed. The server is running dovecot 0.99.14-1 on debian sarge. The user logging in is test(a)advanced-reality.com. Some potentially relevant portions of dovecot.conf are: auth_mechanisms = digest-md5 cram-md5 auth_default_realm = auth_user = dovecot-auth >From the logs with auth_verbose = yes and auth_debug = yes in dovecot.conf: Mar 16 08:12:51 localhost dovecot-auth: PGSQL: Performing query: SELECT password FROM mailbox WHERE username = 'test' AND domain = 'advanced-reality.com' AND active IS TRUE Mar 16 08:12:51 localhost dovecot-auth: digest-md5(test(a)advanced-reality.com): password mismatch Mar 16 08:12:51 localhost pop3-login: Aborted login [64.81.224.97] Some preliminary searching led me to this: http://www.dovecot.org/list/dovecot/2003-November/002598.html Is there a problem with digest-md5 in this version of dovecot? Any pointers on how to troubleshoot this further? Any additional help is appreciated. Let me know if additional information is needed. Thanks -- Trev Peterson <trev(a)advanced-reality.com> Advanced Reality

2 1

[Dovecot] TCP wrappers patch
by Timo Sirainen 09 Apr '06

09 Apr '06

I finally started looking into how to use libwrap, and even got the code working: http://dovecot.org/patches/1.0/tcp-wrappers.patch However once everything was done, I realized it can't work that way because login processes are normally chrooted. So if you want TCP wrappers and don't care that much about the security given by chrooting, you could disable it and use the above patch. Alternatively you could just make sure that the hosts.allow/deny files are always copied inside the chroot. I think I'll just forget about TCP wrappers for now, and implement it in Dovecot 2.0 as some separate non-chrooted process.

1 0

[Dovecot] How to achieve: Automove of mails
by Daniel Watts 09 Apr '06

09 Apr '06

Dear All, I was wondering if this is possible: I am using namespaces to support my environment which has legacy mboxes and new maildirs. In it looks like: namespace private { separator = / inbox = yes prefix = location = maildir:/home/virtual/%d/home/%n/Maildir/ } namespace private { separator = / prefix = mail2/ inbox = yes hidden = yes location = mbox:/home/virtual/%d/home/var/spool/mail/%n:INBOX=/home/virtual/%d/var/spool/mail/%n } This basically means that there is a hidden inbox "mail2/INBOX" that the user cannot see but which can referenced and accessed. What I would like is for Dovecot to automatically move all mail (actually only as much as possible within quota limits) in "mail2/INBOX" into "/INBOX" whenever INBOX is checked/expunged. An alternative acceptable solution is to have something that moves mail once it has read. I would then symlink mail2/INBOX as a "New mail" folder. Once user's read their mail it is moved to the standard /INBOX folder. Are either of the above possible natively or do I need to look at something like plugins? Incidently where is the documentation guiding plugin development? I've looked at the website but can't find anything either by browsing or searching. Many thanks, Daniel

2 1

Re: [Dovecot] Quick question. Thunderbird/Outlook = no love.
by Charlie Davis 09 Apr '06

09 Apr '06

1.0 Beta 3. Plain authentication works. But not TLS. I don't see anything in the configuration file that seems obvious to deny TLS authentication. -Charlie ----- On Friday, March 31, 2006 javert42(a)cs.byu.edu wrote: > Charlie Davis wrote: >> Are there any how-tos or documentation on getting dovecot to be > thunderbird/outlook friendly? >> >> Thunderbird can connect about 20% of the time, the other 80% of the time, I > Get the error: >> >> "You may need to connect via SSL or TLS. Please check the account settings > for your mail server." >> >> I have my thunderbird setup to do TLS. I've put it on the TLS if available > as well, still no love. >> >> Dovecot logfile contains: >> >> dovecot: Mar 31 17:25:19 Info: imap-login: Aborted login: rip=10.0.0.4, > lip=10.0.0.208, TLS >> dovecot: Mar 31 17:25:24 Info: imap-login: Aborted login: rip=10.0.0.4, > lip=10.0.0.208, TLS >> >> Nothing else. >> >> Thanks in advance! >> >> -Charlie >> >> >> > I've got beta2 running on an RHEL4 box, and I've had no problems with > Thunderbird (with people running anywhere from 0.7 to 1.5). Which > version of dovecot are you running? > > -- > Topher Fischer > GnuPG Fingerprint: 3597 1B8D C7A5 C5AF 2E19 EFF5 2FC3 BE99 D123 6674 > javert42(a)cs.byu.edu

5 8

[Dovecot] LDAP and prefetch
by Jorgen Lundman 09 Apr '06

09 Apr '06

SunOS pop01.unix 5.10 Generic_118844-26 i86pc i386 i86pc dovecot-1.0.beta3 It is most likely something I am doing wrong, but could someone take a look at why I can not get LDAP prefetch to work? If I define things like this: dovecot.conf: ---------------------------------------------- passdb ldap { args = /usr/local/etc/dovecot-ldap.conf } userdb ldap { args = /usr/local/etc/dovecot-ldap.conf } ---------------------------------------------- dovecot-ldap.conf: ---------------------------------------------- base = uid=%n, o=%d, ou=mail, dc=example, dc=com user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(mail=%u)) pass_attrs = mail=user,userPassword=password,homeDirectory=userdb_home,uidNumber =userdb_uid,gidNumber=userdb_gid pass_filter = (&(objectClass=posixAccount)(mail=%u)) ---------------------------------------------- This works correctly. Queries LDAP twice, but retrieves home, uid, gid and mail correctly. Authenticates well. If I replace the userdb line in dovecot.conf with: ---------------------------------------------- userdb prefetch { } ---------------------------------------------- It does no longer work. The passdb query is still correct, and it is followed by a second "empty" ldap query (as seen from snoop) with the following errors: Mar 20 15:58:06 pop01.unix dovecot: [ID 474965 mail.info] Dovecot v1.0.beta3 starting up Mar 20 15:58:14 pop01.unix dovecot: [ID 107833 mail.error] auth(default): prefetch(fred(a)uranus.com,172.20.12.12): userdb_uid not returned Mar 20 15:58:14 pop01.unix dovecot: [ID 107833 mail.error] auth(default): prefetch(fred(a)uranus.com,172.20.12.12): userdb_gid not returned Mar 20 15:58:14 pop01.unix dovecot: [ID 107833 mail.error] auth(default): userdb(fred(a)uranus.com,172.20.12.12): user not found from userdb Mar 20 15:58:14 pop01.unix dovecot: [ID 107833 mail.info] pop3-login: Internal login failure: user=<fred(a)uranus.com>, method=PLAIN, rip=172.20.12.12, lip=172.20.12.8 Snoop of failing lookup: LDAP: Operation *[APPL 3: Search Request] LDAP: [Base Object] LDAP: uid=fred, o=uranus.com, ou=mail, LDAP: dc=example, dc=com [snip] LDAP: And *[0] LDAP: Equality Match *[3] LDAP: [Attr Descr] LDAP: objectClass LDAP: [Value] LDAP: posixAccount LDAP: *[3] LDAP: [OctetString] LDAP: mail LDAP: [OctetString] LDAP: fred(a)uranus.com LDAP: *[Sequence] LDAP: [OctetString] LDAP: mail LDAP: [OctetString] LDAP: userPassword LDAP: [OctetString] LDAP: homeDirectory LDAP: [OctetString] LDAP: uidNumber LDAP: [OctetString] LDAP: gidNumber [snip] LDAP: Operation *[APPL 4: Search ResEntry] LDAP: [Object Name] LDAP: uid=fred,o=uranus.com,ou=mail,dc LDAP: =example,dc=com LDAP: *[Partial Attributes] LDAP: *[Attribute] LDAP: [Type] LDAP: uidNumber LDAP: *[Vals] LDAP: [Value] LDAP: 105 LDAP: *[Attribute] LDAP: [Type] LDAP: gidNumber LDAP: *[Vals] LDAP: [Value] LDAP: 200 LDAP: *[Attribute] LDAP: [Type] LDAP: homeDirectory LDAP: *[Vals] LDAP: [Value] LDAP: /export/nfs/mail/com/s/u/ur LDAP: anus/fred/ LDAP: *[Attribute] LDAP: [Type] LDAP: userPassword LDAP: *[Vals] LDAP: [Value] LDAP: {crypt}QAa3SPeYrDARs (its "test", no leak fun here) LDAP: *[Attribute] LDAP: [Type] LDAP: mail LDAP: *[Vals] LDAP: [Value] LDAP: fred(a)uranus.com [snip] TCP: Destination port = 389 (LDAP) LDAP: ----- LDAP: ----- LDAP: LDAP: "" LDAP: TCP: Destination port = 389 (LDAP) LDAP: ----- LDAP: ----- LDAP: LDAP: "" LDAP: Please advice! Lund -- Jorgen Lundman | <lundman(a)lundman.net> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home)

3 3

[Dovecot] POP (dot) locks
by Christian Balzer 09 Apr '06

09 Apr '06

Hello, just to soothe my paranoia from many years of qpopper usage, which enforces solitary access to a POP mailbox. Only one login per user is possible at the same time and if a session terminates w/o qpopper being properly notified it will remain locked for some time, 30 minutes by default. With dovecot (0.99.10.4) one can login multiple times (using POP, with IMAP of course this comes as no surprise :) and thus I presume this bit from the configuration: --- # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no --- means that if the only other reading accesses to a (mbox style in this case here) mailbox are via other dovecot processes everything will be fine? Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

5 10