- dovecot - dovecot.org

[Dovecot] dovecot tpop3d UIDL mbox
by antencek＠volja.net 17 Oct '06

17 Oct '06

Hello All! I am new to this list so I hope I'm not in the wrong list with my question. First, I have to say that dovecot is (in my opinion) one of the best POP3/IMAP servers arround. I especialy like its' simplicity (configuration) and powerfullness (speed, auth mechs). In my production environment I would like to cange from tpop3d to dovecot, but I have only one little problem :). This is my situation: pop3 server: tpop3d mail fromat: mbox (/var/mail/username) UIDL: tpop3d UIDL format Since there are users who let mail on server, I need to keep UIDL. The problem is that the patch which gives dovecot the capability to replay with tpop3d UIDL format apparently works only on maildir mailboxes. Is there any resonable solution to my problem? TIA. Regards, Antencek

3 2

[Dovecot] allow_nets and mysql question
by Alex Samorukov 17 Oct '06

17 Oct '06

Hi. I want to use allow_nets in my configuration, but i have some troubles which i cant resolve. To use allow_nets i creates `allow_nets` text field in my mysql users table. My query is: from: dovecot/sql.conf: password_query = SELECT crypt as password, maildir as userdb_mail, 6 AS userdb_uid,6 AS userdb_gid, allow_nets FROM users WHERE id = '%u' from dovecot.conf: auth default { mechanisms = plain passdb sql { args = /usr/local/etc/dovecot/sql.conf } userdb prefetch { } user = root } To check this i added address 193.193.193.100/32 (which is not my address) and tried to connect from localhost (using telnet). And it allow me to connect! May be i did something wrong, but i cant explain this, so i`m asking for your help. Here is debug information: Dovecot v1.0.rc10 starting up auth-worker(default): mysql: Connected to localhost (maildb) auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=10.0.0.1 rip=10.0.0.1 resp=<hidden> auth-worker(default): sql(testuser(a)example.com,10.0.0.1): query: SELECT allow_nets,crypt as password, maildir as userdb_mail, 1005 AS userdb_uid,6 AS userdb_gid FROM users WHERE id = 'testuser(a)example.com' auth-worker(default): auth(testuser(a)example.com,10.0.0.1): allow_nets: Matching for network 193.193.193.100/32 auth-worker(default): passdb(testuser(a)example.com,10.0.0.1): allow_nets check failed: IP not in allowed networks auth(default): client out: OK 1 user=testuser(a)example.com auth(default): master in: REQUEST 1 65787 1 auth(default): master out: USER 1 testuser(a)example.com mail=/usr/local/vdomains/example.com/users/testuser/Maildir/ uid=1005 gid=6 pop3-login: Login: user=<testuser(a)example.com>, method=PLAIN, rip=10.0.0.1, lip=10.0.0.1, secured POP3(testuser(a)example.com): Effective uid=1005, gid=6 POP3(testuser(a)example.com): maildir: data=/usr/local/vdomains/example.com/users/testuser/Maildir/ POP3(testuser(a)example.com): maildir: root=/usr/local/vdomains/example.com/users/testuser/Maildir, index=/usr/local/vdomains/example.com/users/testuser/Maildir, control=, inbox= POP3(testuser(a)example.com): Disconnected: Logged out top=0/0, retr=0/0, del=0/7, size=1362269

2 3

[Dovecot] auth problem
by Lampa 17 Oct '06

17 Oct '06

hello, i new to list but i need little help. I need only imap (later pop3),i have own checkpassword and own user/password database. i'm using last version v1.0.rc10 But i have problem with auth, user is authorized but cannot login, here is log: dovecot: Oct 17 15:00:36 Info: Dovecot v1.0.rc10 starting up dovecot: Oct 17 15:00:40 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=10.0.0.1 rip=10.0.0.13 resp=AG1kdgBza29sYTY2Ng== dovecot: Oct 17 15:00:40 Info: auth(default): checkpassword(lampa,10.0.0.13): Executed: /usr/local/checklocalpwd/checkpassword.pl /usr/local/dovecot/bin/dovecot/checkpassword-reply dovecot: Oct 17 15:00:40 Info: auth(default): checkpassword(lampa,10.0.0.13): Received input: userdb_user=lampa userdb_home=/home/_mail/lampa userdb_uid=65534 userdb_gid=65534 dovecot: Oct 17 15:00:40 Info: auth(default): checkpassword(lampa,10.0.0.13): Received no input dovecot: Oct 17 15:00:40 Info: auth(default): checkpassword(lampa,10.0.0.13): exit_status=0 dovecot: Oct 17 15:00:40 Info: auth(default): client out: OK 1 user=lampa dovecot: Oct 17 15:00:40 Info: auth(default): master in: REQUEST 1 17950 1 dovecot: Oct 17 15:00:40 Info: auth(default): master out: USER 1 lampa user=lampa home=/home/_mail/lampa uid=65534 gid=65534 dovecot: Oct 17 15:00:40 Info: imap-login: Internal login failure: user=<lampa>, method=PLAIN, rip=10.0.0.13, lip=10.0.0.1 dovecot: Oct 17 15:00:40 Error: Logins with UID 65534 (user lampa) not permitted (see first_valid_uid in config file) i think that problem is that uid and gid is set to user nobody instead 508 and 502 (user lampa , end of message is passwd file) uid 65534 is user nobody (used in auth section in conf, if i set it to root everyhting is ok) this is my config: base_dir = /var/run/dovecot/ protocols = imap listen = 10.0.0.1 disable_plaintext_auth = no log_path = /var/log/dovecot/dovecot.log info_log_path = /var/log/dovecot/dovecot.info log_timestamp = "%b %d %H:%M:%S " ssl_disable = yes login_dir = /var/run/dovecot/login login_chroot = yes login_user = dovecot mail_debug = yes mail_log_prefix = "%Us(%u): " verbose_proctitle = yes first_valid_uid = 508 last_valid_uid = 508 first_valid_gid = 502 last_valid_gid = 502 protocol imap { login_executable = /usr/local/dovecot/bin/imap-login mail_executable = /usr/local/dovecot/bin/imap } auth_executable = /usr/local/dovecot/bin/dovecot-auth auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb checkpassword { args = /usr/local/checklocalpwd/checkpassword.pl } userdb prefetch { } user = nobody } in file i must comment out chdir $home (program was unable to chdir) i think due to chroot /usr/local/checklocalpwd/checkpassword.pl: #!/usr/bin/perl use POSIX; use strict qw(vars); my $PASSWD_FILE = "/usr/local/qmail/control/passwd2"; %ENV=(); my($len, $buf); open (USER, "<&=3") || _exit(2); $len = read(USER, $buf, 512); close USER; _exit(2) if $len < 4; my($user, $pass) = split /\x00/, $buf; $user = lc $user; $buf = "\x00" x $len; my $cwd = getcwd; my ($passwd, $uid, $gid, $gcos, $home, $shell) = ""; open F, $PASSWD_FILE || _exit(111); while (<F>) { if (/^$user:/) { ($user, $passwd, $uid, $gid, $gcos, $home, $shell) = split(/:/); } } close F; _exit(2) unless $uid; if (crypt($pass, $passwd) ne $passwd) { _exit(1); } $ENV{USER} = $user; $ENV{UID} = $uid + 0; $ENV{HOME} = $home; $ENV{SHELL} = $shell; _exit(111) unless $ENV{UID}; #chdir $home || _exit(111); $) = $gid; $( = $gid; $> = $uid; $< = $uid; exec @ARGV; _exit(0); here is passwd/user file: lampa:HSExFJNuwlKvk:508:502::/home/_mail/lampa:/bin/false

1 0

Re: [Dovecot] File isn't in mbox format: /home/foo/mail/Trash
by Phil Roffe 17 Oct '06

17 Oct '06

> On Mon, 2006-10-16 at 05:40 -0500, James Lupolt wrote: >> > Hello, >> > >> > I'm seeing the following error on a server: >> > >> > File isn't in mbox format: /home/foo/mail/Trash >> > >> > The Trash file is full of the following at the beginning: >> > >> > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ >> > >> > I've repaired the file several times, but this keeps happening. Would >> > any of you mind offering me some insight into what could be causing this >> > and how to fix it? >> > > This is a known problem with v0.99.x. The mbox code has been rewritten > in 1.0rc versions and it doesn't have this problem, so I'd just suggest > upgrading. We had a problem with this several months ago. The alarming aspect of the corruption is when it occurs at the beginning of an email (i.e. ^@^@^@From:...). Emails can be lost/appended to the bottom of the previous email. I've seen this problem several times on our deployment and tracked it down to what appears to be NFS locking issues. Are you storing mails on an NFS mounted filesystem? If so check the following... http://wiki.dovecot.org/NFS We're running dovecot-1.0 beta5 (admittedly not an rc version but >beta4 which is mentioned in the NFS wiki section) so I'm not sure the mbox rewrite from v0.99.x has fixed the problem. We had several applications accessing the mbox (Dovecot and Pine mainly). Reconfiguring Pine to use IMAP (using Dovecot) rather than write to the mbox directly appears to have fixed the problem and we have had no corruption for several months now. So, my question is am I wrong to assume NFS locking/corruption? Does anyone know if this is really a Dovecot or NFS issue? Phil

3 4

[Dovecot] plugin to delete spam/virus/junk/trash mail after 30 days of life
by Beber 17 Oct '06

17 Oct '06

Hi, Is there a plugin or a way in dovecot to delete any mails older that 30 days in certain maildir ? Just something like find maildir:%h/.Spam maildir:%h/.Virus maildir:%h/.Junk maildir:%h/.Trash -type f -ctime 30 -exec rm {} \; -- Beber -- Email / Jabber (+GMail) : beber(a)meleeweb.net http://www.meleeweb.net

2 4

[Dovecot] 1.0.rc9 released
by Timo Sirainen 17 Oct '06

17 Oct '06

http://dovecot.org/releases/dovecot-1.0.rc9.tar.gz http://dovecot.org/releases/dovecot-1.0.rc9.tar.gz.sig Most importantly this should fix the login process problems that people have been reporting. There were also some bugs in the proxying feature. Also note the 64bit change in dovecot.index.cache files. Unless you delete dovecot.index.cache files manually, you'll these kind of error messages into your logs: Error: Corrupted index cache file ...dovecot.index.cache: registered field date.sent size changed They'll get fixed automatically of course, but it might be a bit annoying to see them. * 64bit systems: dovecot.index.cache file will be rebuilt because some time fields have been changed from 64bit fields to 32bit fields. Now the same cache file can be used in both 32bit and 64bit systems without it being rebuilt. * Added libmysqlclient workaround to conflicting sha1_result symbol, which caused Dovecot to fail logging into MySQL. + dovecot.index.cache file opening is delayed until it's actually needed. This reduces disk accesses a bit with eg. STATUS commands. + auth_cache: Try to handle changing passwords automatically: If password verification fails, but the last one had succeeded, don't use the cache. This works only with plaintext auth. - dovecot.index.cache: We didn't properly detect if some fields were different length than we expected, which caused assert crashes - Lots of fixes to login/master process handling - mbox: Fixed a bug causing "X-IMAPbase uid-last unexpectedly lost in mbox file" errors, and possibly others.

12 19

[Dovecot] Separate auth for pop and imap
by Hr. Daniel Mikkelsen 17 Oct '06

17 Oct '06

Hi. Is it possible to set up separate authentication backends for POP and IMAP for a single Dovecot instance? Or does this require two separate dovecot instances with separate config files? Specifically, I want to have one database query for IMAP and one for POP so that I can let these be separate features that I can flag in a database. -- Daniel Mikkelsen Copyleft Software AS

3 2

[Dovecot] Ignore leave on server
by Hr. Daniel Mikkelsen 17 Oct '06

17 Oct '06

Hi. Is it possible to ignore "leave on server" for POP3 clients? That is, always delete all downloaded mail automatically? -- Daniel Mikkelsen Copyleft Software AS

2 1

[Dovecot] MBox path
by Rick 17 Oct '06

17 Oct '06

Hi, I'm having great difficulty pointing Dovecot to my MBox files. They are all in /var/spool/mail/username as textfiles.. not directories. So my guess was: default_mail_env = /var/spool/mail/%u Since %u is user. If the user is "server" I would expect it to go to /var/spool/mail/server exactly what I want. But it doesn't /var/spool/mail///home/server. If I create the directory home in /var/spool/mail and make a symlink of the username pointing to /var/spool/mail it does work. But that's a very dirty workaround I rather not use, also because we have a lot of users.. a lot of symlinks. If I set default_mail_env = /var/spool/mail, it also searches for /var/spool/mail///home/server. I feel like I've tried everything. What am I doing wrong? I'm using version 1.0.beta8, included in Fedora Core 5. Thanks, Rick

2 1

[Dovecot] Dovecot still failing with RC10...
by Timothy Meader 16 Oct '06

16 Oct '06

Hello, I mentioned back with version RC8 that dovecot was having an issue with the first login working, but all subsequent attempts failing with the error message: "Error: Maximum number of mail processes exceeded" in the dovecot log file. This is with an unchanged working conf file from RC7 (which, aside from comments, nothing has changed config-wise in the conf from version RC7). Now, the max mail processes were already set at 1024 (and I'm the only person using this server while testing), but just for the heck of it, I tried bumping the number up to 4096 and giving it another shot. No such luck. You can login once, but any subsequent attempts come back with the error I mentioned. This is making all versions above RC7 unusable for me unfortunately. I was hoping to get buy-off on switching from QPopper/UWImap to an all Dovecot solution with the pending 1.0 final, but I doubt they'll go for allow and RC being run on the production side. Two notes that might help(?): -I'm running this on Solaris 9, not a Linux box -Dovecot is not running in daemon mode, it's running through xinetd Here are the xinetd.conf sections that are relevant: defaults { #The maximum number of requests a particular service may handle # at once. instances = UNLIMITED # The type of logging. This logs to a file that is specified. # Another option is: SYSLOG syslog_facility [syslog_level] log_type = FILE /var/log/servicelog # What to log when the connection succeeds. # PID logs the pid of the server processing the request. # HOST logs the remote host's ip address. # USERID logs the remote user (using RFC 1413) # EXIT logs the exit status of the server. # DURATION logs the duration of the session. log_on_success = HOST PID DURATION EXIT # What to log when the connection fails. Same options as above log_on_failure = HOST # The maximum number of connections a specific IP address can # have to a specific service. per_source = 50 } service pop3 { socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/dovecot/pop3-login port = 110 flags = REUSE IPv4 rlimit_cpu = 150 instances = 80 cps = 110 10 no_access = xxx.xxx.xxx.xxx log_type = FILE /var/log/POPlog disable = no } service imap { socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/dovecot/imap-login port = 143 flags = REUSE IPv4 rlimit_cpu = 120 only_from = xxx.xxx.xxx.xxx log_type = FILE /var/log/IMAPlog disable = no } Thanks in advance for any help with this. --- Tim Meader CNE ISG Security NetCommerce Corporation Tim.Meader(a)gsfc.nasa.gov (301) 286-8013

2 1