- dovecot - dovecot.org

[Dovecot] Dovecot as LDA
by Gerard Seibert 03 Oct '06

03 Oct '06

FreeBSD 6.1-RELEASE-p8 postfix-current-2.4.20060903,3 dovecot-1.0.r7 I am experiencing a problem with dovecot as an LDA. It will not deliver mail unless the mail directory is chmod'd to 1777. Below is an example of the log file output. The dovecot.log file had over a hundred entries similar to this: deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1123.cd38cd4d82e1368f) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied Obviously the /var/log/maillog had similar fail warnings. By changing the permission to 1777 on the /var/mail directory and running postsuper -r ALL, I was able to get the mail delivered. What I am trying to determine is if I really should have those settings on the directory, or if I have something configured wrong in either postfix or dovecot. Postfix will deliver mail without any problem so I think it has to do with dovecot although I am not sure what. -- Gerard

3 4

[Dovecot] Quota with quota dict and peruser quota, dovecot LDA needed?
by Peter Veerman 02 Oct '06

02 Oct '06

Hi, This mail sources from the thread with this topic title: Re: [Dovecot] [SOLVED] quota with: postfixadmin, postfix, mysql & dovecot As this title does no longer cover the topic i decided to start a new thread. I have set up quota:dict with the proxy::quotadict option and i'm not using dovecot LDA. My quota table is filled with records like username: pveerman(a)nemo.kabelfoon.net path: 0 current: 0 and the personal max-quota reported by the client is okay, but the current-quota is 0. What am I doing wrong here? Peter

1 1

[Dovecot] Dovecot accepts squirrelmail, rejects fetchmail
by M. Fioretti 01 Oct '06

01 Oct '06

Hello, this is a follow-up to the thread "Fetchmail can't talk to dovecot" http://www.dovecot.org/list/dovecot/2006-September/016477.html Increasing the log level I get this in the log filed: Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAPsecured +lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE resp=LONG_STRING_HERE VDBB Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL 1 user=user_name Sep 30 15:05:07 fm dovecot: imap-login: Aborted login: user=<user_name>, method=PLAIN, rip=::ffff:CLIENT_IP_HERE, +lip=::ffff:SERVER_IP_HERE, TLS Remember that when the same user name and password come from Squirrelmail on the same host where dovecot runs, everything works. Why does it fail with fetchmail? what does that message "unknown user" exactly mean? Thank you in advance for any help, Marco

3 3

[Dovecot] [SOLVED] quota with: postfixadmin, postfix, mysql & dovecot
by Peter Veerman 01 Oct '06

01 Oct '06

Hi, I'm quite new to dovecot but already quite satisfied. Your documentation in the wiki is great but on quota + mysql it is not very clear. Because of the previously mentioned I have got the following note to make which you will hopefully use to adjust your wiki documentation on per-user-quota + mysql. I've searched your mail archive as good as possible and found no messages on this. If already messages have been exactly on this topic I want to apologize for sending this one. The notes I want to make is about this page: http://wiki.dovecot.org/Quota I'm using postfix + postfixadmin & mysql and dovecot (previously I used courier-imap instead of dovecot). The problems I ran in to was with setting up the per-user quota, as the explanation at the wiki is quite vague. For instance, the dict plugin is used to keep the quota counters in the mysql backend but only one single line shows how to set-up a per user quota. Setting up a per user quota where the max-quota is stored in mysql should be made making use of this setting: ========== user_query = SELECT home, uid, gid, 'dirsize:storage=' || quota_bytes AS quota FROM users WHERE userid = '%u' ========== nowhere is mentioned that this should also! be set: =========== protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota } =========== the second point I want to make is that the mysqlquery is incorrect as || does not do the job of joining the two strings. Secondly is dovecot making use of kilobytes instead of bytes like postfix (and postfixadmin) does. For this I have found the following solution: ========== user_query = SELECT maildir, 125 AS uid, 125 AS gid,\ CONCAT('dirsize:storage=', ROUND( mailbox.quota / 1024 ) ) AS quota \ FROM mailbox WHERE username = '%u' AND active = '1' ========== Here I select the quota field from the mailbox table. This is then divided by 1024 (1Kbyte) and ROUNDED off in order to get rid of the .00 that results from this division. Greetz, Peter Veerman pveerman NO-SPAM at NO-SPAM hackwerk DOT net

6 7

[Dovecot] fetchmail can't talk to dovecot
by M. Fioretti 30 Sep '06

30 Sep '06

Hello, I have dovecot q1.0-0_22.rc7 up and running on a server: I can read email from squirrelmail just fine. When I try to download email with fetchmail, however, I get the result below. Why is that happening? In dovecot.conf I have: protocols = imap imaps pop3, so why should pop3 or imap fail? Where should I look? (I'll fix the certificates problem after I've managed to get in successfully with plain imap or pop3) Thanks, Marco fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:17 AM CEST: poll started fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< STLS fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now. fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: Server CommonName mismatch: localhost.localdomain != my.server fetchmail: my.server key fingerprint: ... fetchmail: Server certificate verification error: self signed certificate fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> USER user_name fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. fetchmail: Authorization failure on user_name(a)my.server fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:21 AM CEST: poll completed fetchmail: Query status=3 (AUTHFAIL) fetchmail: Writing fetchids file. fetchmail: normal termination, status 3 fetchmail: Writing fetchids file. if I try with IMAP the part after the certificate verification error is: fetchmail: IMAP> A0003 CAPABILITY fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5 fetchmail: IMAP< A0003 OK Capability completed. fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: IMAP> A0004 LOGIN "user_name" * fetchmail: IMAP< A0004 NO Authentication failed. fetchmail: IMAP> A0005 * fetchmail: Authorization failure on user_name(a)my.server fetchmail: IMAP> A0006 LOGOUT fetchmail: IMAP< A0005 BAD Error in IMAP command received by server. fetchmail: IMAP< * BYE Logging out and I don't see any error message related to this in the server log.

2 3

Re: [Dovecot] SSL errors
by Bill Boebel 29 Sep '06

29 Sep '06

On Fri, September 29, 2006 11:47 am, Charles Marcus <CMarcus(a)Media-Brokers.com> said: > Bill Boebel wrote: >> I have a Dovecot server set up as a proxy and getting a ton of these >> errors, but I'm not sure where to begin troubleshooting it. I'm >> hearing frequently that Outlook users who use IMAP with SSL are >> getting disconnected often as a result. Any suggestions?... > > Need more details... Dovecot version? Platform? > Sorry... Red Hat ES4 (2.6.9-42.0.2.EL), latest dovecot CVS 20060926. login_process_per_connection = no login_processes_count = 3 login_max_processes_count = 10 login_max_connections = 4000 login_process_size = 64 Also added this to the dovecot init script to allocate more file descriptors to dovecot: start() { echo -n $"Starting $prog: " + ulimit -n 16384 daemon /usr/sbin/dovecot Also, seeing this error occasionally... Sep 29 11:34:15 director4 dovecot: imap-login: SSL_write() syscall failed: Bad file descriptor [166.137.221.91] Maybe nothing to worry about now that I have increased "login_process_size". Checking with customers to see if the Outlook IMAP SSL disconnects are still frequently occurring. Thanks, Bill

1 0

[Dovecot] SSL errors
by Bill Boebel 29 Sep '06

29 Sep '06

I have a Dovecot server set up as a proxy and getting a ton of these errors, but I'm not sure where to begin troubleshooting it. I'm hearing frequently that Outlook users who use IMAP with SSL are getting disconnected often as a result. Any suggestions?... Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [64.81.197.28] Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() syscall failed: EOF [24.236.204.154] Bill

2 1

Re: [Dovecot] SSL errors
by Bill Boebel 29 Sep '06

29 Sep '06

On Fri, September 29, 2006 11:23 am, Bill Boebel <bill(a)webmail.us> said: > I have a Dovecot server set up as a proxy and getting a ton of these errors, but > I'm not sure where to begin troubleshooting it. I'm hearing frequently that > Outlook users who use IMAP with SSL are getting disconnected often as a result. > Any suggestions?... > > Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() failed: > error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [64.81.197.28] > > Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() syscall failed: EOF > [24.236.204.154] > Actually, I found in the archives that I should increase login_process_size if I'm not running with login_process_per_connection. I have done this and that seems to have taken care of the malloc failure. However I am still getting a ton of these every few seconds: Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [70.171.61.190] Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [24.236.204.154] Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [70.171.61.190] Sep 29 11:30:08 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [65.242.19.3]

2 1

[Dovecot] Passdb passwd on FreeBSD
by Jim Flowers 29 Sep '06

29 Sep '06

I am trying to use dovecot for both virtual and local pop3 mailboxes. When I try to access a local account, I get an "unknown user" reject from 'passdb sql', as expected. However, I also get a reject from 'passdb pam' with the message: dovecot: auth(default_with_listener): pam(username(a)domain.tld,###.###.###.###): pam_authenticate() failed: authentication error. Is this because it is trying to authenticate username(a)domain.tld instead of just username? What can I do about it? Although I have a block for 'passdb passwd' following the 'passdb pam' block, there is nothing in the log. Why is this, I wonder? Any help to point me in the right direction will be appreciated. Thanks. -- Jim Flowers <jflowers(a)ezo.net> -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

[Dovecot] Quota plugin rewrite
by Timo Sirainen 28 Sep '06

28 Sep '06

Backported from CVS HEAD to branch_1_0. You can get it as a patch from http://dovecot.org/patches/1.0/quota-rewrite.diff New features include support for multiple quota roots, so you could have eg. per-user quota and a larger domain quota (although no backend actually supports this yet..). The more important feature is that you can configure specific mailboxes to have a bit more space available for them, such as Trash or Spam. The configuration has also changed. Normally you'd use something like this: quota = maildir # 1GB quota in general quota_rule = *:storage=1048576 # Trash mailbox gets 100MB more (so max. 1,1GB) quota_rule2 = Trash:storage=102400 # Spam mailbox gets also +100MB (still maxes at 1,1GB, not 1,2GB) quota_rule3 = Spam:storage=102400 You can place all the above into plugin { .. } section in dovecot.conf. In userdb if users have different quotas you'd then need to override only quota_rule (not quota, quota_rule2 and quota_rule3). I tested quickly that this seemed to work as described above. Please test and report. :)

2 6