- dovecot - dovecot.org

[Dovecot] Dovecot (IMAP) Hangs sometimes
by Mario Gomide 12 Jan '10

12 Jan '10

Hi there! I'm using Dovecot 1.0.7 in RHEL 5.4 64bits as a IMAP/POP3 server. Dovecot authenticates users against an AD server via kerberos (pam configuration) and clients connect to it via IMAPs and POP3s with SSL. Webmail is in localhost and connects locally also with SSL. All is fine and people use the email server normally and with no problems. But, I have noticed that dovecot hangs sometimes. Usually twice a day somewhere between 09:40 and 10:00 a.m and in the afternoon at about 3:00 p.m. The problem starts when webmail takes long to authenticate and show folders and stuff. After a while it times out and doesn't connect. Then the clients (e.g. outlook, thunderbird) start taking long to connect and then they timeout. Important: Only IMAP connections timeout! POP3 continues ok. This latency keeps on going until dovecot finally hangs (after about 10 to 15 minutes). The problem is solved when I restart/reload dovecot. I'm not sure as to what's going on! I check the log, but it has been hard to pinpoint an exact event or to detect when the problem begins. Any ideas? BTW: what's the real difference between reload and restart? Thanks a lot! Mario

5 13

Re: [Dovecot] Sieve > Pigeonhole > external storage with LDAP or other data source available to dovecot
by Martin F. Foster 12 Jan '10

12 Jan '10

Le 09-Jan-10 20:29, Stephan Bosch a écrit : > > I thought this would be an excellent opportunity to test the new > Pigeonhole plugin support and also to do something interesting with the > namespace functionality of the variables extension. That is why I gave > this a short look, which promptly resulted in a preliminary implementation. > > If you want to play around with it, you can download it from: > > http://hg.rename-it.nl/pigeonhole-sieve-extdata/ > > It will compile and run with both Pigeonhole for Dovecot v1.2 and > Pigeonhole for Dovecot v2.0, but only with the tip Mercurial revisions > (since only those have plugin support). Thanks Stephan, I have the extdata plugin compiled, and am now trying to make a global sieve script to test it. I'm running into problems when using sievec to compile the script - I'm not getting the plugin's variables that are provided in dovecot.conf's plugin {}. I added a few sieve_sys_warning messages to track the calls to sieve_setting_get() <output> /usr/local/bin/sievec -d -P sieve_extdata /usr/local/etc/dovecot/sieve/before.sv Warning: sieve: sieve_setting_get: req: 'sieve_max_script_size' res: '(null)' Warning: sieve: sieve_setting_get: req: 'sieve_max_actions' res: '(null)' Warning: sieve: sieve_setting_get: req: 'sieve_max_redirects' res: '(null)' Warning: sieve: sieve_setting_get: req: 'sieve_subaddress_sep' res: '(null)' Warning: sieve: sieve_setting_get: req: 'recipient_delimiter' res: '(null)' Warning: sieve: sieve_setting_get: req: 'sieve_plugin_dir' res: '(null)' Warning: sieve: sieve_setting_get: req: 'sieve_plugins' res: '(null)' Warning: sieve: sieve_setting_get: req: 'sieve_extdata_dict_uri' res: '(null)' Warning: sieve: extdata: no dict uri specified, extension is unconfigured (sieve_extdata_dict_uri is not set). * Required extensions: 0: vacation (9) 1: variables (17) 2: vnd.dovecot.extdata (29) * Main program (block: 1): 00000000: EXTENSIONS [3]: 00000001: vacation 00000002: variables 00000003: SCOPE [0] (end: 00000008) 00000008: vnd.dovecot.extdata 00000009: VACATION 0000000a: (source line: 3) 0000000d: subject: VAR ${extdata.vacation_subject} 00000023: reason: VAR ${extdata.vacation_message} 00000038: handle: STR[77] "${extdata.vacation_message}${extdata.vacation_subject}<default-from><NO-MIME>" 00000088: [End of code] </output> I'm new to dovecot's internals, it looks like it just needs some environment variables provided, but I'm puzzled as to how this is to be done. I've traced it through sievec.c -> sieve_tool_sieve_env -> sieve_tool_get_setting -> getenv() call. More info: 1. I've traced the process, there's no attempt to open or stat any dovecot.conf 2. using tip dovecot-1.2, dovecot-1.2-sieve, pigeonhole-sieve-extdata. I pulled+updated & rebuilt and confirmed the above behaviour just prior to sending this message. 3. The test scripts run because the test framework uses the test_config mechanism to provide sieve_extdata_dict_uri. Any hints on how to get the dovecot.conf data to sievec? Thanks, -Martin Foster

2 3

Re: [Dovecot] Moving
by Stewart Dean 11 Jan '10

11 Jan '10

My apologies for posting this to the list; I meant to send it Timo only.... > Now that you're back in your native land. ..... > If and only if you're interested, I'D be interested in hearing what > you thought of America -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] Same filenames on different servers?
by Alexander Chekalin 11 Jan '10

11 Jan '10

Hi, I'm really fuzzy about some problem on how Dovecot used to name files to store messages in Maildir. I have two identical servers (let's call them "First" and "Second"), and have Dovecot and Exim set up on both of them (Maildirs are used to store messages and boxes). First server is the server to be used by people around, and the Second server is backup one, the only thing it can do while the First is alive is to get (via rsync) First's mail spool. I set up rsync to run every 5 minutes, and that's quite well sync spools from First to Second. So if something wrong happens to First server we simple disconnect it from the network and put Second server in place of First. The problem is that files in Maildirs on First server are named like that: 1262610335.H798006P5447.first.domain.my,S=1962:2, 1262610402.H529761P5596.first.domain.my,S=2975:2, 1262610410.H787724P5657.first.domain.my,S=75691:2, ... and the files on Second server should be named like 1262610335.H798006P5447.second.domain.my,S=1962:2, 1262610402.H529761P5596.second.domain.my,S=2975:2, 1262610410.H787724P5657.second.domain.my,S=75691:2, ... As soon as I enter the Second's mailbox with IMAP client Dovecot used to rename files the way they should be. If after that I rsync spools I'll end up with double sized spool as there'll be both First and Second files: 1262610335.H798006P5447.first.domain.my,S=1962:2, 1262610335.H798006P5447.second.domain.my,S=1962:2, 1262610402.H529761P5596.first.domain.my,S=2975:2, 1262610402.H529761P5596.second.domain.my,S=2975:2, ... Long description for simple problem, yes :) I also tried to set: maildir_copy_preserve_filename = yes but still no luck. My setup is FreeBSD 7.2 with all versions in 1.1.x and 1.2.x branches (now it is 1.2.8). Thank you in advance for you advice, yours, Alexander

8 19

[Dovecot] sieve 0.1.14: vacation encodes Subject twice
by Roland Rosenfeld 11 Jan '10

11 Jan '10

Hi! I noticed the following problem in dovecot-1.2-sieve-0.1.14: The following vacation causes trouble with the Subject line: if not exists ["List-Id", "List-Post"] { vacation :days 7 :addresses ["test(a)netcologne.de"] :subject "=?utf-8?b?w4TDlsOc?= sadasd" "Bin gerade nicht hier."; } As you can see, the Subject is already MIME encoded according to RFC2047. Starting with sieve 0.1.14 the subject is now encoded by sieve again, so I get the following in my vacation mail: Subject: =?utf-8?q?=3D=3Futf-8=3Fb=3Fw4TDlsOc=3F=3D?= sadasd As you can see, the RFC2047 encoding is RFC2047 encoded, which results in an unreadable subject. According to RFC5230 section 4.3 this shouldn't happen: The ":subject" parameter specifies a subject line to attach to any vacation response that is generated. UTF-8 characters can be used in the string argument; implementations MUST convert the string to [RFC2047] encoded words if and only if non-ASCII characters are present. Implementations MUST generate an appropriate default subject line as specified below if no :subject parameter is specified. If I understand this right, sieve should do the RFC2047 encoding only if the string is non-ASCII. But the RFC2047 encoded string is already ASCII, so it should not be encoded a second time. I just compared this with sieve 0.1.13, which behaves different: It does not encode the Subject header at all. As long as the managesieve client (in our situation Horde/IMP) encodes the subject, everything works correct, while we run into trouble with 0.1.14. I think that there needs to some mechanism in sieve that checks whether the subject contains non-ASCII and does the encoding only in this case. I just checked out, that 0.1.14 does not encode a non RFC2047 encoded 7bit subject, while a 7bit subject starting with =?utf-8?... is encoded twice. Tschoeeee Roland -- Roland Rosenfeld - Content Delivery - NED - Technik NetCologne Gesellschaft für Telekommunikation mbH - HRB 25580, AG Köln Am Coloneum 9 50829 Köln Tel.: +49-221-2222-373 Fax: +49-221-2222-7373 Geschäftsführer: Werner Hanf, Karl-Heinz Zankel

4 6

[Dovecot] dovecot cannot access a specific folder
by Spyros Tsiolis 11 Jan '10

11 Jan '10

Hello list, Has someone stumbled upon this before ? -- Jan 09 11:25:01 IMAP(postmaster(a)webmail.domain.gr): Error: stat(/var/MailRoot/domains/webmail.domain.gr/postmaster/Maildir/tmp) failed: Permission denied (euid=501(vmail) egid=502(vmail) missing +x perm: /var/MailRoot) -- "/var/MailRoot" is the root path/folder for XMail. An smtp/pop3 server. Should I go ahead and chmod the folder or should I try to find a more delicate solution to this ? Any help would be greatly appreciated, Regards, spyros

2 1

[Dovecot] How to create UTF encoded folders?
by Kārlis Repsons 11 Jan '10

11 Jan '10

Hey, as I understand from post [1], system folders with UTF-8 chars in their names will only be available for use with Dovecot2 and I certainly look forward to that, but somehow I was short of info about the current use of UTF characters like ā, Ž etc. Should I just omit thinking about modified-UTF-7, avoid those characters for the time being and then with Dovecot2 create UTF-8 encoded folders with MUA and also on fs? Or there is something to know anyway? Please suggest as it would be a pity not to create folders with utf symbols... [1] http://www.mail-archive.com/dovecot@dovecot.org/msg23576.html

2 1

[Dovecot] "leave mail on server" workaround
by Kirill Miazine 11 Jan '10

11 Jan '10

Hello, POP users often keep fetched mail on server, by checking for "leave mail on server" or similar option in their client. What would be the best way to disallow them using such approach. That is, what is the best way to force deletion of messages that have been RETRieved in a POP session at the end of that POP session? RETRieved messages will be marked as \Seen, but since users might also use an IMAP client (e.g. webmail), it'll be dangerous to simply delete all \Seen messages in user's mailbox. I'm all open for suggestions. -- -- Kirill Miazine <km(a)krot.org>

5 9

[Dovecot] how to use dsync?
by joakim＠verona.se 10 Jan '10

10 Jan '10

I would like to try dsync but dont quite understand the usage string. Can anyone offer an example? -- Joakim Verona

2 1

[Dovecot] How to tell dovecot to use a specific MTA
by Spyros Tsiolis 10 Jan '10

10 Jan '10

Hello again people, OK. I checked a lot of HOWTOs and documents. One specific document describes how one can make dovecot "talk" to postfix. The procedure is pretty straightforward (taken from the document) : -- . Configuring Postfix and Dovecot Turn off sendmail: service sendmail stop chkconfig sendmail off system-switch-mail (select postfix) -- This is for CentOS systems. My question is pretty simple. How exactly does someone tell dovecot (or the CentOS system) that the MTA used is not a pre-packaged postfix MTA but (in my case as you have pretty much discovered by now) XMail compiled from source (no pre-packaged version AFAIK for CentOS; but even if existed, I would still build it on my own) ? Any help would be appreciated, Regards, spyros

2 1