- dovecot - dovecot.org

[Dovecot] imap flags - \* - dovecot 1.1.{8,9}
by Arkadiusz Miskiewicz 27 Jan '09

27 Jan '09

Isn't \* supposed to be (almost always) in flags after "SELECT" command in dovecot imap? Isn't \* meaning is "you can store any new flag" ? 20 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] Flags permitted. so no \* ... [..] 50 store 1 +flags $MDNSent * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent)] Flags permitted. * 1 FETCH (FLAGS ($MDNSent)) 50 OK Store completed. 60 logout * BYE Logging out 60 OK Logout completed. [ new session ...] 20 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent)] Flags permitted. * 4 EXISTS * 2 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1181546666] UIDs valid * OK [UIDNEXT 864597] Predicted next UID 20 OK [READ-WRITE] Select completed. ... but it saved $MDNSent flag, huh -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

2 2

[Dovecot] dotlock timestamp trouble
by Giorgenes Gelatti 27 Jan '09

27 Jan '09

Hi there, I'm getting a lot of this message in production log: Created dotlock file's timestamp is different than current time (1232468644 vs 1232468524): /path/to/dovecot.index.log The IT guy swears the clocks are sincronized. Whe even have made a test in the machine running dovecot, inside the user's mailbox: # > foo; ls -l --time-style=full-iso foo; date -rw-r--r-- 1 root root 0 2009-01-19 17:40:55.000850000 +0000 foo Mon Jan 19 17:40:55 UTC 2009 The timestamps seems to match. I'm using dovecot 1.1.6 over NFS. Any thoughts? Thanks in advance, gpg

2 5

[Dovecot] No Spaces in Directory names
by Matt Rude 27 Jan '09

27 Jan '09

How can I make it so my users can not create folders with spaces in them? Or allow them to create such folders but rewrite them on the hardrive with a "_" or some other symbol. I have looked threw the wiki but couldn't find anything about folder name restrictions or folder name rewriting (rewrite the space to a "_"). Im having problems with some of the expire and compress scripts when it hits these types of folders. Is dovecot able to restrict or rewrite the names of imap folders? dovecot -n # 1.1.9: /usr/local/etc/dovecot.conf # OS: Linux 2.6.27.9-159.fc10.i686 i686 Fedora release 10 (Cambridge) ext3 listen: *:143 ssl_listen: *:993 ssl_cert_file: /etc/postfix/SSL/mail.mattrude.com.cert ssl_key_file: /etc/postfix/SSL/mail.mattrude.com.key login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: postfix mail_location: maildir:/var/spool/virtualmailboxes/%d/%u/imap/:INBOX=/var/spool/virtualmailboxes/%d/%u/ mail_plugins: quota imap_quota zlib auth default: mechanisms: plain login cram-md5 cache_size: 128 cache_ttl: 600 master_user_separator: * passdb: driver: sql args: /etc/dovecot-mysql.conf passdb: driver: sql args: /etc/dovecot-sql-master.conf pass: yes master: yes userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: virtualmail group: virtualmail plugin: sieve: /var/spool/virtualmailboxes/%d/%u/dovecot.sieve sieve_storage: = /var/spool/virtualmailboxes/%d/%u/ quota: maildir quota_rule: *:storage=10M quota_rule2: Trash:storage=20% Thanks -Matt

3 2

Re: [Dovecot] help writeing rule for preventin spam
by Sophia Alikhani 27 Jan '09

27 Jan '09

Hi I installed qmail-jms1-7.07 + domainkey-patch + simscan + clamav+ dovecot-1.1.7+ vpopmail+ spamassassin I also used Bayes + AWL as database connection in local.cf I don't know how can i stop these type of spam at MTA level (qmail) i wrote a rule in .dovecot.sieve if header :contains ["From","To"] ["%u@mydomain] { discard; stop; } In the real i nedd to stop any mail from a virtual user to him/her self. -- with regards Sophia Alikhani WorkPhone: +98-21-8497057 Mobile : +98-912-3361036

3 2

[Dovecot] Dovecot discards mail over quota
by Gary V 27 Jan '09

27 Jan '09

I'm new to Dovecot, using 1.1.8 and I just wanted to verify that what I am observing is the intended behavior. I'm using Maildir++ quota. When a message is delivered to a mailbox that cannot accept the message because it would place them over the quota limit, deliver states to the MTA that the messsage was delivered successfully (example using postfix): Jan 17 12:05:31 msa postfix/pipe[13983]: 088C5B9D47: to=<test(a)example.com>, relay=dovecot, delay=0.72, delays=0.34/0.02/0/0.36, dsn=2.0.0, status=sent (delivered via dovecot service) But in actuality the mail is discarded (dropped). Then a bounce is created stating the mail was rejected: Your message to <test(a)example.com> was automatically rejected: Quota exceeded (mailbox for user is full). Question: is it possible (without changing code) to alter this to where deliver would instead tempfail or something. Somehow it seems wrong to me to tell the MTA that everything is good, and then silently discard messages - regardless of the fact dovecot creates a bounce. This is not necessarily ideal either, but I _am_ wondering if this is configurable or not. deliver(test(a)example.com): 2009-01-17 12:05:31 Info: msgid=<1293474859.20090117120812(a)example.com>: save failed to INBOX: Quota exceeded (mailbox for user is full) deliver(test(a)example.com): 2009-01-17 12:05:31 Info: sieve runtime error: Keep: Generic Error deliver(test(a)example.com): 2009-01-17 12:05:31 Error: sieve_execute_bytecode(/var/sieve/global.sievec) failed deliver(test(a)example.com): 2009-01-17 12:05:31 Info: msgid=<1293474859.20090117120812(a)example.com>: rejected: Quota exceeded (mailbox for user is full) deliver(garyv(a)example.com): 2009-01-17 12:05:31 Info: msgid=<dovecot-1232219131-401523-0@msa>: saved mail to INBOX -- Gary V

12 29

[Dovecot] behavior of dovecot with Openldap
by Masaharu Kawada 27 Jan '09

27 Jan '09

Dear team, I'm sorry if this is a stupid question, but I'd like to know the behavior of dovecot in a particular stuation. My questions are as follows. In /etc/dovecot-ldap.conf, 'hosts=' field is the one which can be used to specify availabled ldap server to access from the clients to authorize. And also sevral ldap servers can be specified in 'hosts =' field as shown like below. hosts = ldap-server1.example.com ldap-server2.example.com ※both server have the same configuration and available to replication ldap-server1(master) to ldap-server2(slave). If this is right, how does dovecot know which ldap server is currently used? and if the master dies, how does dovecot know and switch to slave one? In addition, which one is the exact behavior of dovecot in case master server dies? 1. only swithcing to the slave server 2. switching to the slave server, and once the master server is reactive then switch back to the master server automatically OS：RHEL4 U3 kernel 2.6.9-34.ELsmp openldap-2.2.13-12.el4 Thanks in advance, Masaharu Kawada ------------------- Masaharu Kawada Associate Global Support Engineer Red Hat K K Ebisu Neonato 8F 1-18 Ebisu 4-chome, Shibuya-ku Tokyo 150-0013, Japan Direct: +81-3-5798-8482

5 11

[Dovecot] FOLDER INTERNAL DATA (uw pine header)
by Charles Gregory 26 Jan '09

26 Jan '09

Hello! I run Dovecot on CentOS 4 (dovecot-1.1.4-0_81.el4), and I *also* run the "Alpine" mail system that comes with that OS. Alpine still writes out the 'FOLDER INTERNAL DATA' pseudo-message at the beginning of each user's mbox, but dovecot does not. I make use of that record as a simle/quick way to verify when a user actually last read their e-mail (for administrative purposes, identifying stale/unused accounts), so is there any way to configure/command dovecot to write (or update) these hidden messages? (Note: I tried looking in the archives, but most references seemed to be about this message being a 'side effect' of transferring *from* UW IMAP, and how to get 'rid' of it. Not what I need. :) Apologies if this was covered before in a different thread.) - Charles

2 6

[Dovecot] uint_cmp bug
by Mike Abbott 26 Jan '09

26 Jan '09

In reviewing the differences between 1.1.8 and 1.1.9 I saw a probable bug in the new function uint_cmp() in src/lib-storage/index/maildir/ maildir-sync-index.c: if (*i1 < *i2) return -1; else if (*i1 > *i2) return -1; else return 0; The second case should return 1 not -1.

2 1

[Dovecot] Released ManageSieve v0.10.5 for Dovecot v1.1.9
by Stephan Bosch 26 Jan '09

26 Jan '09

Hello Dovecot users, Because there was a crash bug in the ManageSieve v0.10.4 login daemon, I made a new release of the ManageSieve service for Dovecot v1.1. This release includes two other small fixes as well. Changelog v0.10.5: - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed maximum permissions for uploaded scripts; was 0777. This was shielded however by the default umask (not documented to be configurable), so the actual permissions would never have been 0777. - Fixed handling of ~/ in use of mail-data for script location The following files are released: ManageSieve package: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.5.tar.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.5.tar.gz.s… ManageSieve patch: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.9-managesieve-0.10.5.diff.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.9-managesieve-0.10.5.diff.g… Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

1 0

Re: [Dovecot] troubles with 1.1.8 and squirrelmail over HTTPS
by Frank Bonnet 26 Jan '09

26 Jan '09

Hello Jack Setting up imapproxy on a third machine greatly improve performances on my mailhub which doesn't refuse connexions anymore. Thanks a lot for your help ! Frank Jack Stewart wrote: > > > Frank Bonnet wrote: >> Timo Sirainen wrote: >>> On Thu, 2009-01-15 at 16:25 +0100, Frank Bonnet wrote: >>>> I had to increase the max_mail_processes to 8192 >>>> to have a functionnal IMAP server with normal clients AND >>>> squirrelmail clients >>>> >>>> 8192 sounds enormous to me , any infos welcome ! >>> >>> How many imap processes have you running typically? >>> >> > > Hi, > > I don't know if this will help or not - I'm taking my comments offline > because it isn't clear if they are related to your core problem. Also, > they seem to be specific to high usage servers/people. > > We're not 1.1.8 yet but I've spent a reasonable amount of time tweaking > the Linux side. > > We run at about ~1300 processes per server. > > Squirrelmail does a login/logout on every single page that is clicked. > So I've found that running an imap proxy (such as the one at > imapproxy.org really helps). It creates some additional connections but > they get re-used pretty frequently. > > If 1.1.8 isn't logging out quickly, or not cleanly shutting down the > connection, or something similar, that could explain additional > connections. What does netstat -an show? On some O/S's the process will > disappear from ps but not be fully released until the socket/connection > disappears (in this case tcp). If you have a bunch of WAIT/FIN_WAIT's > something like this seems pretty likely. > > I've found that going through localhost allows you to bypass TLS while > still enforcing TLS for non-localhost connections. It's pretty nice for > overhead/connect speed. Also, an imap proxy may need a non-encrypted > connection. > > Besides the dovecot max_ ... settings, in our system you need to tweak > limits.conf and bump up the limits via the ulimit command in the dovecot > init script. Open file descriptors and process limits seem to be the > main settings. > > After this, you get into kernel tuning such as inotify settings. > > Let me know if you have any questions. If some of this helps, we might > want to feed it back into the list. > > ---Jack > >

1 0