- dovecot - dovecot.org

[Dovecot] Strange behaivour with extended characters
by Armando Soto Baeza 20 Apr '09

20 Apr '09

Hi there. I am using dovecot in almost all the mail servers I configure, but I have not noticed some problems till now, when I configured a server for a japanese language based customer. Now I know, the problem is not about this customer, but it seems to be a constant in all my servers (for some reason we did not noticed that before). The situation is like this. When receving mail with extended (not only japanese) characters in the subject, Outlook Express does not recognize them. Most of our users do not use OE, but most of the japanese do. This is not all. When extended chars are also in the body, they look well when the maqil still arrives, but if forwarded to another account, or when mail is an answer to another, extended characters are not well displayed. In some tests we have done, I found more or less the same is happening when using squirrelmail. The funny thing is that the problem dos not appear when using Evolution or Outlook (the MS Office component). I move some pamrs in dovecot.conf and get some results (before moving them, the problem extended to attachements), but still remains as described. Somebody has seen such a behaivour and solved it? I was thinking to change dovecot for another agent, but will be happier using dovecot. Any suggestion? Thanks in advice.

2 1

[Dovecot] [SIEVE: Redirect] Double ">" in forwarded envelop sender address => Gmail syntax error
by Toorop 20 Apr '09

20 Apr '09

Hi, Plateform: gentoo + qmail My deliver line is in a .qmail-USER file: |/var/qmail/bin/preline /usr/libexec/dovecot/deliver -f ${SENDER:-<>} -d user(a)domain.tld I notice that sieve implementation in Dovecot use double ">" for the envelop sender when there is a redirect command in sieve script. (i've tried preline -f, without -f ${SENDER:-<>},... but nothing change for the the envelop sender syntax, alway the double ">") And that fact breaks forwardin to Gmail. Gmail reply that there is a syntax error probably due to the double "<<" (<<address>> and not <address>) as we can see in the log behind: Dovecot logs: deliver(stephane@XXXX): Apr 20 16:06:44 Info: Sending a forward to <XXXX(a)gmail.com> with return path <<stephane@XXXXXX>> deliver(stephane@XXXXX: Apr 20 16:06:44 Info: msgid=<49EC816D.9090403(a)XXXXX.com>: forwarded to <XXXXX(a)gmail.com> qmail-send logs: 2009-04-20 16:06:44.877793500 info msg 14815541: bytes 1290 from <<stephane(a)XXXXX.com>> qp 17780 uid 89 2009-04-20 16:06:44.892303500 starting delivery 6356: msg 14815541 to remote XXXXX(a)gmail.com 2009-04-20 16:06:44.982424500 delivery 6356: failure: Connected_to_209.85.219.1_but_sender_was_rejected./Remote_host_said:_555_5.5.2_Syntax_error._1si7169155ewy.101/ 2009-04-20 16:06:44.982502500 status: local 0/10 remote 0/80 Is there something to do to fix that probleme ? Thanks. -- Toorop <O> http://www.flickr.com/photos/toorop/

3 3

[Dovecot] 0 mails available even if mails in mailbox
by Raphael Thoma 20 Apr '09

20 Apr '09

Hello We are currently facing the problem, that dovecot doesn't return any messages (Pop3: +OK 0 messages) even if there are messages in the cur and new directory (maildir format). The logfile does not contain any information other than login/logout. After I deleted the dovecot.index file, all messages are available and everything works as expected. According to the wiki page [1] the main index file should be synchronized when the cur and new timestamps changed. I suppose this synchronization doesn't work correctly because the problem still existed after I changed the timestamps manually. Dovecot version: 10.0.14 Operating System: FreeBSD 7.0-RELEASE-p1 CPU Arch: amd64 Filesystem: NFS Clients: The problem exists on Pop3 and IMAP. It doesn't matter which client. I could reproduce the problem on outlook, thunderbird and even on telnet. Reproduced: +OK Dovecot ready. user user(a)domain.com +OK pass password +OK Logged in. list +OK 0 messages: After deleting dovecot.index: +OK Dovecot ready. user user(a)domain.com +OK pass password +OK Logged in. list +OK 20 messages: It seems to be a problem with the index-file from dovecot which doesn't seem to be synchronized. What could be the reason for this behaviour? How can we fix this issue for all customers? Kind regards Raphael Thoma [1] http://wiki.dovecot.org/IndexFiles

3 5

[Dovecot] Quota not being dispayed correctly in 1.2rc2 (with proof)
by Ralf Hildebrandt 20 Apr '09

20 Apr '09

User reports: 0% of 640MB -- which cannot be true. I logged in as masteruser and was able to confirm this. I'm getting "0.0% von 640.0MB" == "0.0% of 640.0MB" His maildirsize file is attached. His mailbox is nearly full. Manual login: # telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. . LOGIN user*masteruser topsecretpassword . OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA] Logged in . SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 3261 EXISTS * 0 RECENT * OK [UIDVALIDITY 1179137269] UIDs valid * OK [UIDNEXT 8900] Predicted next UID * OK [HIGHESTMODSEQ 1] . OK [READ-WRITE] Select completed. . GETQUOTA "" * QUOTA "" (STORAGE 0 655360) . OK Getquota completed. WTF? -- Ralf Hildebrandt Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.computerbeschimpfung.de If you spend more on coffee than on IT security, then you will be hacked -- what's more, you deserve to be hacked.

3 5

[Dovecot] dovecot deliver with sieve: Corrupted index cache file (in-memory index).cache: Broken fields for mail UID
by Mathias Gug 19 Apr '09

19 Apr '09

Hi, Running dovecot deliver 1.1.11 with a sieve script (dovecot-sieve 1.1.6 + changeset b9567e94b897) the following messages started to show up in the mail logs for some (spam) messages: deliver(mathiaz): Apr 18 19:03:06 Error: Corrupted index cache file (in-memory index).cache: Broken fields for mail UID 1 deliver(mathiaz): Apr 18 19:03:06 Error: Couldn't fix broken header unfolding deliver(mathiaz): Apr 18 19:03:06 Info: msgid=<01c9548a$f1666dfe$6c822ecf@pillarsx6>: saved mail to INBOX How serious are these? Without changeset b9567e94b897 applied deliver would actually crash and the message would be lost. More information can be found in the Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/264306 -- Mathias Gug Ubuntu Developer http://www.ubuntu.com

1 0

[Dovecot] Suggestion: deliver should honor mail_log_prefix
by Mike Abbott 19 Apr '09

19 Apr '09

I can set the log prefix for imap/pop3 processes using mail_log_prefix but the log prefix for deliver is hard-coded. (I'm using 1.1.13.) Deliver should either honor mail_log_prefix or have its own setting (deliver_log_prefix?). What do you think?

2 1

[Dovecot] Released Sieve v0.1.5 and ManageSieve v0.11.4 for Dovecot v1.2.rc3 and ManageSieve v0.10.6 for Dovecot v1.1.14
by Stephan Bosch 18 Apr '09

18 Apr '09

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve include extension to the latest draft. This means that the import and export commands are replaced by a new command called global. The import and export commands are now DEPRICATED and are mere aliases for the global command. The new specification also adds the :once modifier to the include command. The also newly specified global.* variable namespace is not implemented yet as support for variable namespaces is currently missing. * Did a major rework of the multiscript support for better error handling and made sure that persistent global scripts (sieve_before/sieve_after) are always executed, even when the user does not have a script of his own and a global default is missing. + Provided basic support for the environment extension. Currenly, the name, version and host items are useful. Others are pending. + Improved error message that is presented when an unknown Sieve extension is provided as argument to the require command. It now notifies the user that Sieve core commands do not need to be specified in require. - Fixed bug in includes at levels deeper than one. - Fixed bug in address matching that was caused by the failure to handle group specifications. In Dovecot, these are marked by address items with NULL elements, which causes a segfault if not considered. The group 'undisclosed-recipients:;' in particular triggered this bug. Bug reported by Bernhard Schmidt. Changelog ManageSieve v0.11.4 (Dovecot v1.2.rc3): * Adjusted to changes in the Dovecot signal handler API. Changelog ManageSieve v0.10.6 (Dovecot v1.1.14): - Fixed small problems in the login proxy support. -- The releases are available as follows: Sieve for Dovecot 1.2: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.5.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.5.tar.gz.sig ManageSieve for Dovecot v1.2 (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.4.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.4.tar.gz.s… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.rc3-managesieve-0.11.4.diff… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.rc3-managesieve-0.11.4.diff… ManageSieve + patch for Dovecot v1.1 (package + patch): http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.6.tar.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1-managesieve-0.10.6.tar.gz.s… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.14-managesieve-0.10.6.diff.… http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.14-managesieve-0.10.6.diff.… -- 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

1 0

[Dovecot] Mail replication
by Renaud Allard 18 Apr '09

18 Apr '09

Hello, I am running an asynchronously replicated mail setup. 2 servers are each running an smtp server which uses dovecot as the LDA. I am using unison to replicate mail files between servers. Before, I was using Maildir format and after reading so much good papers about the very good performance of dbox format, I decided to switch to dbox. However, I now have a very annoying problem, as mails are created with names like u.1234 and numbers are following each others. So, if there is for example a mail stored as u.1001 on both servers, and now 2 mails arrive at about the same time, 1 on each server. Then, they will both be created as u.1002, that means unison will encounter a conflict as both files are different. So my question would be, is there a way to tell the servers to increment by 2 instead of 1 and have each an offset (like you can do with mysql with auto incrementing tables for example)? That way, with former example, one mail would be stored as u.1002 and the other as u.1003. Thanks

2 3

[Dovecot] Logging to see exactly all IMAP commands?
by Johan Persson 18 Apr '09

18 Apr '09

I was wondering if there is some additional logging that can be enabled to make it possible to have Dovecot print all actual IMAP commands it receives in a conversation? /Johan

2 2

[Dovecot] Feature Request: Control over IMP IDLE 'OK Still Here' message timings
by Robert Goldsmith 18 Apr '09

18 Apr '09

Hi all, I would like to make a feature request regarding IMAP Idle support. Currently when a client triggers Idle support, Dovecot then sends 'OK Still Here' messages every 2 minutes. This is apparently to prevent NAT systems killing the tcp connection and disconnecting the client. However, while this may be fine for desktop clients, this rapidly drains the battery life of mobile clients such as phones. Unfortunately, the timing control on this behaviour is a c define at the top of cmd-idle.c and is only adjustable at compile-time. I have experimented with this define and find a timeout of 20 minutes between 'OK' messages is perfectly adequate for my system setup and results in a significant battery saving for my Nokia 6120c (increasing from ~ 6 hours to ~ 55 hours from full charge to low battery warning). Therefore, can you please make the timeout changeable from the config file, even if it defaults to the current 2min timing, so admins supporting mobile users can balance battery life with a need to prevent killed tcp connections. Thanks Robert Goldsmith --- GnuPG public key: http://www.Far-Blue.co.uk

3 2