- dovecot - dovecot.org

[Dovecot] Postfix Virtual Users and Directory Permissions
by Michael Starks 18 Jul '06

18 Jul '06

I have followed the instruction here: http://www.postfix.org/VIRTUAL_README.html#virtual_mailbox There are five virtual domains configured and each directory containing each domain is owned by one UID/UID with permissions of 700. I can send mail to each domain and it is stored in the appropriate Maildir under the correct directory. The system is OpenBSD 3.8 STABLE. So far, so good. Now comes Dovecot. What I would like to do is to have one set of credentials for 4 of the domains, and another for the remaining. I would also like to *not* use a database backend for authentication at this time and would prefer to stick with standard UNIX /etc/passwd and /etc/shadow. Considering the directories are all owned by one user, does Dovecot need to be configured to use the same user as auth_userdb = static? That would make sense. What I'm not clear on is how Dovecot would know which domains are associated with which user, and does the user need permissions to those directories or is that handled by impersonation? Thanks in advance.

2 1

[Dovecot] access to root mail through Dovecot on VPS
by surabaja＠gmail.com 18 Jul '06

18 Jul '06

Hello, I just installed dovecot and postfix on a Fedora Core VPS. The VPS will not allow me to ssh directly as user "root" i.e.: I must first login as a non-root user and then "su" into root. My question is: is there a way to read my root mail through Dovecot ? How should I setup the Thunderbird account ? Thank you... SJ

3 2

[Dovecot] bug in 1.0RC2?
by Renaud Allard 17 Jul '06

17 Jul '06

Hello, I have a small problem with dovecot 1.0RC2. This didn't happen with former versions. There are imap processes that are left open a long while after the client disconnected. I am running dovecot on OpenBSD 3.8. Below is the output of a process list. As you can see, there are many imap processes for the same login running. simon 11593 0.0 0.1 924 1140 ?? I 12:21PM 0:00.48 imap [simon 24.43.241.184] juha 1376 0.0 0.2 1936 2212 ?? I 12:25PM 0:01.36 imap [juha 203.114.146.110] n 26989 0.0 0.1 1060 1292 ?? I 2:18PM 0:00.47 imap [n 85.201.63.39] n 30256 0.0 0.5 5124 5300 ?? I 3:34PM 23:29.59 imap [n 85.201.63.39] n 27695 0.0 0.1 1020 1284 ?? I 3:39PM 0:00.26 imap [n 85.201.63.39] n 24109 0.0 0.1 960 1328 ?? I 3:57PM 0:00.18 imap [n 85.201.63.39] n 20018 0.0 0.1 948 1288 ?? I 4:00PM 0:00.28 imap [n 85.201.63.39] n 12715 0.0 0.1 900 1240 ?? I 4:09PM 0:00.25 imap [n 85.201.63.39] n 3466 0.0 0.1 1116 1280 ?? I 4:27PM 0:00.43 imap [n 85.201.63.39] simon 16654 0.0 0.1 864 1268 ?? I 4:31PM 0:00.14 imap [simon 24.43.241.184] simon 12460 0.0 0.1 980 1256 ?? I 5:02PM 0:00.11 imap [simon 24.43.241.184] simon 31713 0.0 0.1 940 1280 ?? I 5:11PM 0:00.17 imap [simon 24.43.241.184] simon 14593 0.0 0.1 1004 1212 ?? I 6:18PM 0:00.56 imap [simon 24.43.241.184] n 15645 0.0 0.5 4984 5336 ?? I 6:19PM 0:37.77 imap [n 85.201.63.39] simon 10532 0.0 0.1 1220 1480 ?? I 6:21PM 0:01.28 imap [simon 24.43.241.184] n 13642 0.0 0.1 1088 1268 ?? I 7:32PM 0:00.32 imap [n 85.201.63.39] juha 20201 0.0 0.2 1736 2160 ?? I 10:45PM 0:00.82 imap [juha 203.114.146.110] simon 30389 0.0 0.1 952 1276 ?? I 11:11PM 0:00.68 imap [simon 24.43.241.184] juha 26802 0.0 0.2 1948 2172 ?? S 2:45AM 0:00.98 imap [juha 203.114.146.110] simon 26946 0.0 0.1 884 1232 ?? I 5:21AM 0:00.09 imap [simon 24.43.241.184] simon 21744 0.0 0.1 948 1244 ?? I 5:22AM 0:00.06 imap [simon 24.43.241.184] simon 17271 0.0 0.1 868 1272 ?? I 5:24AM 0:59.36 imap [simon 24.43.241.184] simon 641 0.0 0.1 952 1228 ?? I 5:31AM 0:00.14 imap [simon 24.43.241.184] simon 23690 0.0 0.1 812 1152 ?? I 5:32AM 0:00.04 imap [simon 24.43.241.184] simon 25444 0.0 0.1 1024 1228 ?? I 5:37AM 0:36.67 imap [simon 24.43.241.184] simon 6198 0.0 0.1 1000 1228 ?? I 5:54AM 0:00.14 imap [simon 24.43.241.184] simon 9066 0.0 0.1 1040 1244 ?? I 6:01AM 0:28.46 imap [simon 24.43.241.184] simon 15098 0.0 0.1 908 1120 ?? I 6:01AM 0:00.12 imap [simon 24.43.241.184] simon 15905 0.0 0.1 992 1232 ?? I 6:13AM 0:39.33 imap [simon 24.43.241.184] simon 26291 0.0 0.1 848 1264 ?? I 6:13AM 0:00.10 imap [simon 24.43.241.184] simon 20385 0.0 0.1 1004 1216 ?? I 6:14AM 0:00.23 imap [simon 24.43.241.184] simon 21078 0.0 0.1 876 1224 ?? I 6:15AM 0:39.01 imap [simon 24.43.241.184] simon 17733 0.0 0.1 828 1196 ?? I 6:21AM 0:30.02 imap [simon 24.43.241.184] simon 22327 0.0 0.1 1192 1408 ?? I 6:24AM 16:20.01 imap [simon 24.43.241.184] simon 20571 0.0 0.1 808 1196 ?? I 6:28AM 0:00.25 imap [simon 24.43.241.184] simon 15751 0.0 0.1 804 1132 ?? I 6:31AM 0:00.12 imap [simon 24.43.241.184] simon 28495 0.0 0.1 904 1108 ?? S 6:51AM 0:00.20 imap [simon 24.43.241.184] n 24886 0.0 0.1 892 1192 ?? S 8:39AM 0:00.04 imap [n 85.201.63.39] n 7397 0.0 0.1 1004 1052 ?? S 8:43AM 0:00.02 imap [n 85.201.63.39] n 9757 0.0 0.1 900 1288 ?? S 8:44AM 0:00.13 imap [n 85.201.63.39] n 6788 0.0 0.1 928 1196 ?? S 8:53AM 0:00.01 imap [n 85.201.63.39]

4 7

[Dovecot] pop3 auth problem solved!
by Bruce Lane 16 Jul '06

16 Jul '06

Fellow techies, OK... This is going to go down as one of those "D'Oh!" moments in the world of computers. Boy, do I feel dumb... In short: I found the problem. One miserable little line in 'dovecot.conf' called 'auth_default_realm =.' I had this set to 'bluefeathertech.com,' thinking it was necessary to do so. I was wrong, at least for my environment, and the stupid clues were right in front of me in the logfile all the time! For the benefit of others who may run into this: Setting a domain name in this entry causes that domain name to be automatically appended to usernames when they log in. No wonder nothing ever matched in /etc/passwd! My deepest thanks to Frank Cusack for giving me the idea. Something he said in his post, in response to my initial one, got me thinking about things getting appended to the user name, and the rest is history. pop3 and pop3s both work just fine now, thanks. ;-) Keep the peace(es). -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"

1 0

[Dovecot] pop3 authentication problems: Still got 'em...
by Bruce Lane 16 Jul '06

16 Jul '06

Fellow users, This is just a heads-up to let the list know that I'm still unable to get ANY sort of pop3 or pop3s authentication to work with Dovecot. Just as a sanity check, I set up an entirely separate system, running FreeBSD 6.1 production, postfix 2.3, and Dovecot 1.0rc2, as a testbed. I got the exact same problem that I had with the NetBSD 3.0 production server, specifically that Dovecot refuses to authenticate a user with either basic pop3 or pop3s. The way I see it, I may as well try to get basic pop3 working first. If it doesn't, pop3s will never work. This first quote is taken from the mail client (Pegasus) trying to establish a regular, unencrypted pop3 session. -=-=-=-=-=-=- [*] Connection established to 192.168.42.80 >> 0058 +OK AVG POP3 Proxy Server 7.1.368/7.1.394 [268.10.1/389] << 0013 USER kyrrin >> 0005 +OK << 0016 PASS XXXXXXXXX >> 0029 -ERR Authentication failed. -=-=-=-=-=-=-=- As you can see, the user ID of 'kyrrin' is getting passed as just that, and Dovecot at least seems to recognize it. I say this as a prefix to the next log clip, which will be the corresponding entry from /var/log/maillog, in which the user name is being presented (for whatever reason) in FQDN format. Note that pam was added just as an experiment. It failed too, despite the presence of a 'dovecot' file, containing the following, in /etc/pam.d -=-=-=-=-=-=-=- pioneer# cat /etc/pam.d/dovecot auth required pam_unix.so nullok account required pam_unix.so pioneer# -=-==-=-=-=-=- This would be the /var/log/maillog entry corresponding to the above-referenced Pegasus session. -=-=-=-=-=-=-=- Jul 16 11:24:38 pioneer dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=192.168.42.80rip=192.168.42.40 resp=AGt5cnJpbgBocDIxZHZlbTc= Jul 16 11:24:38 pioneer dovecot: auth(default): pam(kyrrin(a)bluefeathertech.com,192.168.42.40): pam_authenticate() failed: authentication error Jul 16 11:24:38 pioneer dovecot: auth(default): cache(kyrrin(a)bluefeathertech.com,192.168.42.40): User unknown Jul 16 11:24:40 pioneer dovecot: auth(default): client out: FAIL 1 user=kyrrin(a)bluefeathertech.com Jul 16 11:24:49 pioneer dovecot: pop3-login: Aborted login: user=<kyrrin(a)bluefeathertech.com>, method=PLAIN, rip=192.168.42.40, lip=192.168.42.80 -=-=-=-=-=-=-=- This next bit is the auth default section of my dovecot.conf file. Other sections, or the entire file, can be posted upon request. -=-=-=-=-=-=-=- auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain login passdb pam { } passdb passwd { } userdb passwd { } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } -=-=-=-=-=-=-=-=-=-=- I've posted a similar note to bsdforums, in the hope that someone there is (successfully) using Dovecot with pop3 and pop3s. Thanks in advance for any assistance. I'm really starting to get seriously upset about this, enough to give thought to qpopper over Dovecot. -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"

3 4

[Dovecot] auth with kerberos
by Renaud Allard 16 Jul '06

16 Jul '06

Hello, I am running dovecot 1.0RC2 and I'd like to know if there is a way to make dovecot provide PLAIN, LOGIN, CRAM-MD5, NTLM authentications from a kerberos database. GSSAPI works great, but I currently have to have two password databases, one for GSSAPI and one for all the others. What I'd like is to have only one password database (namely kerberos). I know that cyrus-sasl (which most of you don't like I think ;)) can provide such authentications, but I haven't found the way to configure dovecot to do the same. Any input welcome.

2 2

Re: [Dovecot] TLS Issues - Plain Text login?
by Timothy White 15 Jul '06

15 Jul '06

Thanks Marcus and Thomas. I should have checked it in another client ;-) Tim -- Linux Counter user #273956 Don't email joeblogs(a)scouts.org.au

1 0

Re: [Dovecot] Deliever in RC2 incorretly outputs "saved mail to INBOX"
by Alex Pimperton 14 Jul '06

14 Jul '06

Hi All, I've recently upgraded to RC2 (debian package) and now I get the following message in syslog all the time: Jul 14 15:51:04 server01 deliver(alex): saved mail to INBOX This seems to happen for every mail, despite some being filtered into different folders. It goes like this: Mail arrives from Ubuntu mailing list: Jul 14 15:53:49 server01 postfix/qmgr[19023]: D51A95C023: from=<ubuntu-users-bounces(a)lists.ubuntu.com>, size=4319, nrcpt=1 (queue active) I get this message: Jul 14 15:53:51 server01 deliver(alex): saved mail to INBOX Postfix sends to deliver: Jul 14 15:53:51 server01 postfix/local[29843]: D51A95C023: to=<alex(a)placet.co.uk>, relay=local, delay=29, status=sent (delivered to command: /usr/lib/dovecot/deliver) ...and a few seconds later it shows up in my Ubuntu-Users folder, exactly where my sieve rule sends it. Is this a bug? Alex -- This message has been scanned for viruses and dangerous content by the MailScanner at Placet.co.uk, and is believed to be clean.

1 0

[Dovecot] Backing up mail
by Davide Bolcioni 14 Jul '06

14 Jul '06

Greetings, in backing up mail stored according to default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u is it safe *not* to backup the .imap subdirectory ? I am currently using dovecot-0.99.13-3.FC3. When restoring, I guess the safe option would be to zap the contents of .imap so that it gets rebuilt, correct ? Thank you for your consideration, Davide Bolcioni -- Paranoia is a survival asset.

1 0

[Dovecot] TLS Issues - Plain Text login?
by Timothy White 14 Jul '06

14 Jul '06

I'm trying to setup IMAP, so that it works via secure connections. I have it working fine over SSL, now I wish to get TLS to work. I have set imap and imaps to both listen on *, and have disable_plaintext_auth = yes, which according to the docs, Disable LOGIN command and all other plaintext authentications unless SSL/TLS is used (LOGINDISABLED capability). So the problem is now, that TLS doesn't work. Trying it with thunderbird, I get a message about login being disabled, and to check my settings and such. The port is correct (imap, not imaps), and I have it to always use TLS. I see the following in my logs Jul 14 16:35:46 mafeking dovecot: imap-login: Aborted login: rip=58.7.136.163, lip=203.30.47.34, TLS Any ideas? To me it appears to be using TLS, so why doesn't thunderbird work? Is it the LOGINDISABLED capa keyword? Is it dovecot telling Thunderbird the wrong capa when using TLS? It all works fine with SSL, and the port (in thunderbird) set to the imaps port. The logs show lines like below when using SSL. Jul 14 16:36:32 mafeking dovecot: imap-login: Login: user=<joeblogs>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Any ideas? Or should I just force SSL? Thanks Tim (using RC2) -- Linux Counter user #273956 Don't email joeblogs(a)scouts.org.au

3 2