- dovecot - dovecot.org

[Dovecot] Exim Dovecot Authentication Problem
by Marc Perkel 21 Jan '08

21 Jan '08

Having a hard time figuring out something that is supposed to be easy. Tryiong to configure Dovecot so that it provides authentication to Exim for outgoing smtp. Tried different things and getting authentication socket protocol error dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous 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 # # 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 passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/exim/control/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/exim/control/vmail/passwd.%d } # 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 # Number of authentication processes to create count = 10 } # 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-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } passdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/shadow.%d } userdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/passwd.%d } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } } } auth external { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } passdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/shadow.%d } userdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/passwd.%d } socket listen { client { path = /var/run/dovecot/auth-client mode = 0666 } } }

3 6

Re: [Dovecot] v1.1.beta14 released (Compile Error)
by Jerry Yeager 21 Jan '08

21 Jan '08

On Jan 20, 2008, at 12:15 PM, dovecot-request(a)dovecot.org wrote: > > Message: 5 > Date: Sun, 20 Jan 2008 15:48:09 +0200 > From: Timo Sirainen <tss(a)iki.fi> > Subject: [Dovecot] v1.1.beta14 released > To: dovecot(a)dovecot.org > Message-ID: <1200836889.12450.99.camel@hurina> > Content-Type: text/plain; charset="us-ascii" > > http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta14.tar.gz > http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta14.tar.gz.sig > > (stuff cut out) The new beta does not compile under OS X 10.5.1 It configures as usual, but then running the 'make' command gets to the point: mkdir .libs gcc -std=gnu99 (followed by the normal list of things it is going to build ) ending with ../lib/liblib.a /usr/local/lib/libiconv.dylib Undefined symbols: "_posix_fallocate", referenced from: _file_set_size in liblib.a(file-set-size.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[3]: *** [imap] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 ??? Jerry > > ------------------------------ > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > End of dovecot Digest, Vol 57, Issue 60 > ***************************************

5 5

[Dovecot] Squirrel Mail (unknown date) in subject and zero size of messages shown
by Niki Spassov 21 Jan '08

21 Jan '08

Hello, I'm having the following problems with a Squirrelmail and Dovecot. with option SERVER SIDE SORTING in Squirrel, only the first page with e-mails is shown in user's inbox, the mails in all the next pages are listed with subject: "(unknown date)" and size 0. The other similar problem, independent from that option (SERVER SIDE SORTING) is: when THREAD VIEW is chosen, we have the same behavior, normal first page and damaged all the others. with option SERVER SIDE SORTING = FASE, and UNTHREADED, everything is OK Has anyone seen this behavior, any help will be greatly appreciated. Thank you in advance :) P.S. Squirrel's version is 1.4.7 and Dovecot is 1.0-stable

2 2

Re: [Dovecot] Time just moved backwards error even with ntpd
by Alexander Moisseev 21 Jan '08

21 Jan '08

On some FreeBSD 6.2 systems I was solved this problem just by adding to crontab: @hourly /sbin/sysctl `/sbin/sysctl -e machdep.adjkerntz` >/dev/null 2>&1 For some explanation, see: http://lists.freebsd.org/pipermail/freebsd-hackers/2005-August/013383.html Quote follows: ... It seems that CMOS clock is updated using resettodr(9) function. There seem to be only a few occasions when this function is called: 1. clock_settime(ClOCK_REALTIME) // through kern_time.c:settime() 2. settimeofday() // through kern_time.c:settime() 3. machdep.adjkerntz sysctl is set I believe that ntpd calls *settime-family* functions *only* if time offset is *larger* than *128ms* (or maybe I am thinking about ntpdate), but normally it uses ntp_adjtime() to adjust time keeping. Obviosuly, a system running ntpd with good enough hardware clock and good enough connection to good enough ntp server(s) would use the latter method all of the time after some initial stabilization period. But it seems that time changes are *never propagated to CMOS* in this case, ... Alexander

1 0

[Dovecot] Using deliver from Getmail?
by Andreas Ntaflos 21 Jan '08

21 Jan '08

Hello list, a quick question: can I use Dovecot's LDA "deliver" as a destination in Getmail? I.e.: [destination] type = MDA_external path = /usr/local/libexec/dovecot/deliver arguments = ("-d", "username",) Or is deliver not supposed to be called this way? What I'd like to do is use deliver in the same way I would have used procmail ages ago. Getmail retrieves the mail messages, filters them according to the filter sections set up and then puts them in the final destination as noted above. Of course I would like to have deliver honour my .dovecot.sieve sieve script. My first tries have not been very successful, all messages retrieved in this way are put in the top level INBOX, not being sieved. I also got this error message, but I am not sure how it is related: Jan 14 16:08:04 localhost deliver(username): net_connect(/usr/local/var/run/dovecot/auth-master) failed: Permission denied Does my user need any special permissions to use the LDA? TIA! Andreas P.S.: Using Dovecot 1.0.5 with the Sieve plugin. I can post the output of dovecot -n but I don't think it's necessary? -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

4 9

[Dovecot] v1.1.beta14 released
by Timo Sirainen 20 Jan '08

20 Jan '08

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta14.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta14.tar.gz.sig School has started since beta13 release and I've been a bit busy with it and trying to get my sleeping times fixed (0-2h sleep doesn't seem to be enough). My interest in algorithms has also grown a bit recently. I'm thinking about majoring in CS / algorithmics (as well as biochemistry / possibly bioinformatics). This should only be good for Dovecot's performance in future. :) Pretty much the same things are in TODO for v1.1.rc1 as there were in beta13. But there are quite a lot of other changes: - Added proxy_maybe setting. If the returned IP/port/user points to ourself, log in normally. Otherwise proxy to the IP. - Added quota_exceeded_message setting for quota plugin. Add it to plugin {} for global, or protocol lda {} for deliver-only. - mysql: default_file and default_group settings (by Luca Longinotti) - Timeout handling rewritten using a priority queue (heap). Dovecot should now be able to handle lots of timeouts quite fast. - Using the new timeout changes several places in code have been changed from iterate-through-objects-in-one-timeout to timeout-per-object. This means that there are no longer timeouts triggering every couple of seconds for no reason. dovecot master and dovecot-auth processes haven't been changed yet. - deliver without -d parameter: if $USER and $HOME exists, don't do getpwuid() lookup. - Maildir locking fix - Index file performance fixes - Don't allow RENAME box box/child. It breaks some clients (which do it themselves..) and there's really no reason to allow it. - Quota warnings were broken - Maildir quota didn't use limits from maildirsize if no quota rules were specified I'm also thinking about getting rid of the "time moved backwards" error and change it to a warning. First I'd just need to fix the timeout handling code to handle time jumps and then verify that all timestamp comparisons can handle it correctly. Also besides warning about "time moved backwards" it should warn about "time moved forwards a lot" where "lot" is probably something like a minute. That could cause problems with dotlocks just the same as time moving backwards.

2 1

[Dovecot] [Sieve] Sendmail problem
by Roger 20 Jan '08

20 Jan '08

Hi All, it's my first post in this list. I'm running dovecot 1.0.rc15 on my Debian Etch box. It's working very well but I faced a problem with Vacation using Sieve. :-( In fact, after well configuring the system I dont't receive the vacation message, and in the log I found: deliver(my(a)address.test): "2008-01-19 12:05:32 "Info: cmusieve: Using sieve path: /home/path/to/my/homedir/.dovecot.sieve deliver(my(a)address.test): "2008-01-19 12:05:32 "Error: Sendmail process terminated abnormally, exit status 75 deliver(my(a)address.test): "2008-01-19 12:05:32 "Info: sieve runtim error: Vacation: Error sending mail. Any idea about the reason this happen and how to solve? Thank a lot for your help Roger

2 1

[Dovecot] Error with 1.1 Beta
by Jeff Grossman 20 Jan '08

20 Jan '08

I am running the latest version of the 1.1 beta and just got the following error: Jan 17 06:20:13 apple dovecot: IMAP(jeff): rename(/home/jeff/Maildir/.Sent Items/dovecot.index.cache.lock, /home/jeff/Maildir/.Sent Items/dovecot.index.cache) failed: No such file or directory Jan 17 06:20:13 apple dovecot: IMAP(jeff): file_dotlock_replace() failed with index cache file /home/jeff/Maildir/.Sent Items/dovecot.index.cache: No such file or directory Is it something I should be concerned about? I had just sent an e-mail about 30 seconds before that one which did not give the error. I will see if I get the error again when I send this one. Jeff

2 2

[Dovecot] Master vs Client socket?
by Marc Perkel 20 Jan '08

20 Jan '08

I'm somewhat confused. I need to use a master socket for the dovecot lda but I also need to have a client socket for authenticating through Exim for outgoing smtp. The auth section doesn't allow for two sockets. How do I do this? Thanks in advance.

2 1

[Dovecot] "Connection queue full" errors
by Jackie Hunt 20 Jan '08

20 Jan '08

Hi all, Our Dovecot server became non-responsive today and had to be restarted. We had approximately 1200 imap sessions running, and when I looked at the log, I found the following errors: Jan 16 10:02:01 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=75.166.40.150, lip=129.82.103.75, TLS handshake Jan 16 10:02:01 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=75.166.40.150, lip=129.82.103.75, TLS handshake Jan 16 10:02:12 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=75.166.40.150, lip=129.82.103.75, TLS handshake Jan 16 10:02:26 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=67.162.151.85, lip=129.82.103.75, TLS handshake Jan 16 10:02:26 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=129.82.100.135, lip=129.82.103.75 Jan 16 10:02:26 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=71.196.217.203, lip=129.82.103.75 Jan 16 10:02:26 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=129.82.100.135, lip=129.82.103.75 Jan 16 10:02:26 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=129.82.100.135, lip=129.82.103.75 Jan 16 10:02:26 lamar dovecot: imap-login: Disconnected: Connection queue full: rip=129.82.218.58, lip=129.82.103.75 ... We are running v1.0.10 on AIX. Here's the relevant configuration from dovecot.conf: # Set max. process size in megabytes. #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)? login_process_per_connection = no # Number of login processes to keep for listening new connections. #login_processes_count = 3 # Maximum number of login processes to create. #login_max_processes_count = 128 # Maximum number of connections allowed per each login process. #login_max_connections = 256 We are running in the high-performance mode, where each login process can handle a number of connections. As I understand it that means we have login_max_connections * login_max_processes_count available possible logins at a given time. That's 32K with our configuration. That seems like a very high limit. Is that what these errors are indicating? Thanks for any insight on this, Jackie --- Jackie Hunt ACNS Voice: (970) 663-3789 Colorado State University FAX: (970) 491-1958 Fort Collins, CO 80523 Email: jackie.hunt(a)colostate.edu

2 1