[Dovecot] fetch bodystructure filename problem rfc2231
Hi,
I have a problem with the filename of attachments in some clients.
# dovecot 1.2.(5|7)
* 3 FETCH (BODYSTRUCTURE ((text plain (charset us-ascii) NIL NIL 7bit
13 1 NIL NIL NIL NIL)(text plain (charset UTF-8 name
ISO-8859-1''testanh%E4ng.txt) NIL NIL 8bit 27 1 NIL (attachment
(filename ISO-8859-1''testanh%E4ng.txt)) NIL NIL) mixed (boundary
=-+zw7hjwJmiqfzphlbHnu) NIL NIL NIL))
- wrong filename in client: ISO-8859-1''testanh%E4ng.txt
# cyrus
* 808 FETCH (BODYSTRUCTURE ((TEXT PLAIN NIL NIL NIL 7BIT 13 1 NIL NIL
NIL)(TEXT PLAIN (NAME* {28}
ISO-8859-1''testanh%E4ng.txt CHARSET UTF-8) NIL NIL 8BIT 27 1 NIL
(ATTACHMENT (FILENAME* {28}
ISO-8859-1''testanh%E4ng.txt)) NIL) MIXED (BOUNDARY
=-+zw7hjwJmiqfzphlbHnu) NIL NIL))
- correct filename in client: testanhäng.txt
I think name should be name* (rfc 2231?)
What can I do?
Test mail:
--
Subject: test
From: ...
To: ...
Content-Type: multipart/mixed; boundary==-+zw7hjwJmiqfzphlbHnu
Date: Fri, 06 Nov 2009 09:48:26 +
Message-Id: 1257500906.7739.0.ca...@localhost
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
X-CheckCompat: OK
--=-+zw7hjwJmiqfzphlbHnu
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
inhalt mail
--=-+zw7hjwJmiqfzphlbHnu
Content-Disposition: attachment; filename*=ISO-8859-1''testanh%E4ng.txt
Content-Type: text/plain; name*=ISO-8859-1''testanh%E4ng.txt; charset=UTF-8
Content-Transfer-Encoding: 8bit
inhalt.. auch mit umlaüt
--=-+zw7hjwJmiqfzphlbHnu--
--
--
DSL-Preisknaller: DSL Komplettpakete von GMX schon für
16,99 Euro mtl.!* Hier klicken: http://portal.gmx.net/de/go/dsl02
Re: [Dovecot] dovecot-2.0.alpha2 doesn't compile on Mac OS X
Le 10 nov. 2009 à 23:44, Timo Sirainen a écrit : On Tue, 2009-11-10 at 22:56 +0100, Axel Luttgens wrote: Although fdatasync() seems to have gone missing from .h files, but still exists in libc. I guess that's intentional? Hello Timo, Did Mike reply about that one? No. I'm also not sure what to do about it. I fear that fdatasync() is currently some kind of a ghost on Mac OS X; I've asked on the darwin-dev list, should someone have definitive information. I guess I could just try if compiler=gcc and compiling it fails with $CC -Wall -Werror and in that case fallback to fsync.. Kind of ugly. On the other hand, autoconf et alii may come with their uglinesses as well. ;-) Here, AC_SEARCH_LIBS seems to fall in the trap by defining a prototype for an existing yet very ambiguous symbol. Looks like that AC_TRY_COMPILE could avoid the problem in that precise case. Now, my knowledge about those matters nearing zero, I'm really *unable* to tell whether the latter would be safer under any circumstances... HTH, Axel
[Dovecot] Deliver and file system quota
Hi, what is the quota plugin for deliver supposed to do when using fs quota? With IMAP, and not using noenforcing, a user that is over Soft limit can't copy mails. With deliver, the mail is delivered normally. When hard limit is exceeded, there is an error rejected: Not enough disk space, just like when I don't use the plugin in lda. Even the lda setting quota_full_tempfail = yes works without the plugin configured in lda section. So is there any effect of the quota plugin in lda with file system quota? Thanks Rainer
Re: [Dovecot] sieve files wont get parsed/compiled using cmusieve
Hello, i have mail_debug turned on, and of course i've got a lot more messages in the log, but nothing which mentions sieve or an error. Timo: in the protocol lda section i've got mail_plugins = cmusieve so it should be active. please see my original message from the 7th of November. Here is the complete output in my log concerning dovecot and one message which should have been placed in a subdir of inbox by a sieve rule: Nov 12 17:31:00 mail dovecot: auth(default): master in: user#0111#011mor...@krinke.biz#011service=deliver Nov 12 17:31:00 mail dovecot: auth-worker(default): sql(mor...@krinke.biz): SELECT '/var/vmail/krinke.biz/moritz' as home, 'maildir:/var/vmail/krinke.biz/moritz' as mail, 150 AS uid, 8 AS gid FROM mailbox WHERE username = 'mor...@krinke.biz' AND active = '1' Nov 12 17:31:00 mail dovecot: auth(default): master out: user#0111#011mor...@krinke.biz#011home=/var/vmail/krinke.biz/moritz#011mail=maildir:/var/vmail/krinke.biz/moritz#011uid=150#011gid=8 Nov 12 17:31:00 mail deliver(mor...@krinke.biz): auth input: home=/var/vmail/krinke.biz/moritz Nov 12 17:31:00 mail deliver(mor...@krinke.biz): auth input: mail=maildir:/var/vmail/krinke.biz/moritz Nov 12 17:31:00 mail deliver(mor...@krinke.biz): auth input: uid=150 Nov 12 17:31:00 mail deliver(mor...@krinke.biz): auth input: gid=8 Nov 12 17:31:00 mail deliver(mor...@krinke.biz): maildir: data=/var/vmail/krinke.biz/moritz Nov 12 17:31:00 mail deliver(mor...@krinke.biz): maildir++: root=/var/vmail/krinke.biz/moritz, index=, control=, inbox=/var/vmail/krinke.biz/moritz Nov 12 17:31:00 mail deliver(mor...@krinke.biz): msgid=2f91b0bb-6356-44fb-9518-23c65b9bb...@gmx.net: saved mail to INBOX Nov 12 17:31:00 mail postfix/pipe[14791]: BD93D29F6A: to=mor...@krinke.biz, relay=dovecot, delay=0.06, delays=0.02/0.02/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) Nov 12 17:31:00 mail postfix/qmgr[14053]: BD93D29F6A: removed Thanks, Moritz Am 11.11.2009 um 10:10 schrieb Steffen Kaiser: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 10 Nov 2009, Moritz Krinke wrote: Any more ideas? ;-) turn on mail_debug Nov 10 19:46:33 mail deliver(mor...@krinke.biz): maildir++: root=/var/vmail/krinke.biz/moritz, index=, control=, inbox=/var/vmail/krinke.biz/moritz Nov 10 19:46:33 mail deliver(mor...@krinke.biz): msgid=d03a5a670911101046y51cf5347m2c79a1642e726...@mail.gmail.com: saved mail to INBOX You should have some more lines in the log. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSvp/eXWSIuGy1ktrAQLtrAgAwY7ryyDz/Tw8CM4Wi0hecZGqxG/RSpkO 4/1dUiQZCYH7yx0h2Es31KQ824scH304fe/YHQupuX+MqOn6ndPgFu/qB3+JaIC4 +iFKEwiFnPGBlIuPyrbOycp8/vyKNRiy5qoL2d1LTDLyULESUuO9iaZA9HpjDg1D fbJyBqpqCIS/sF/eMRwUrVNPQWBaXd/Uenc7PK8sIE9iOCBi0k4SYAV3ZJIzY4ZF dkKqbARAxdKCptN55T+TO1d1kJqO7rCaThzjZmb9CIheRyBktONiV9EujxgwzI56 hSeqKfP/vZ5kyuwoL8aNhCl2U1VYluSWT9M+ylMEokwlRqC0enzquw== =ZjDN -END PGP SIGNATURE-
Re: [Dovecot] Postfix and Dovecot SASL
The problem is solved it was as something easy I missed. Because of the line: smtpd_tls_auth_only = yes the sasl isn't working on plain logins, so using a telnet session to port 25, doesn't allow you to use the smtp authenticate. Uncommenting this (or changing yes to no) will make the plain login work for sasl. Thanks for the help! - Rene
Re: [Dovecot] UTF-8 mailbox names in filesystem
On 10-Nov-09, at 9:02 AM, Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 10 Nov 2009, Laurent Blume wrote: I would personally find it useful. I use accented and Chinese characters, and I, too. Same here. I've worked in environments where they were common as well. Having a common name between MUA and FS would certainly be nice. It would be nicer for some scripts and plugins as well. Will there be an API to match folder names, upper and lower case etc.pp.? As for the risks, maybe some Unicode ranges could be restricted to avoid control characters and such? Or limit the use to given subsets? UTF8 does use octets = 0x80, every system should be 8bit clean nowadays. I had some worries rather than risk. Some MUA may convert before passing the name, and it results in no match... but maybe Timo thought about this already :) Other than looking weird to sys admin whose non foreign speaker, especially in bidirectional presentation, in file system, there should be no issue. best, Joseph regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSvlyg3WSIuGy1ktrAQLsLgf9HVO/E7jwHl8Vgug6esIVK6Icurez7EV5 tvPxtobDSwBDq+ZP8BC6Kdw1uzmRNH60xs/KnaKgscv3vHyOYoiPlRLzYJmNriVt Msct59wPsKwEYACXm1P9iVCMOX0TYLiXliC+LCfOpOL0BqxDBolULuqKw9X2OF9t 71L+WL79KOxgYD2EwUGD9yYoEOo3uixd3AQdsADYfhFqbO9JwsPvuACXmmgAEL0A L3cPGpAp7YeAeAS6DQNCn5d1r1jGRaK47dipHmNSU6U5F3YW40DCl+JUS50AT3no bxrxrNbvXUGFGyHli54RaQS3svArJyXOii9ro9rtqngrnF3xaqunuA== =0IFT -END PGP SIGNATURE-
[Dovecot] Sieve and ACL problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've come across a problem that I can't figure out. I'm using Dovecot
1.2.6 and Sieve 0.1.13.
I'm using the following sieve script to sort my incoming mail.
require [fileinto, envelope];
if envelope :all :is from sopp...@newport.th.gov.bc.ca {
fileinto Public/Weather;
} elsif envelope :all :is from apa...@ldmltd.ca {
fileinto hwcr;
} elsif envelope :all :is from weatherdir...@pelmorex.ca {
fileinto Public/Weather;
} elsif envelope :all :is from drive...@gems2.gov.bc.ca {
fileinto Public/Weather;
} elsif header :contains List-Id Dovecot Mailing List {
fileinto Dovecot;
} else {
keep;
}
It works for saving to my private email folders, but I get a permission
denied error when trying to save to a public folder.
maillog - showing error
Nov 12 12:26:57 app postfix/qmgr[19314]: B36E77800088:
from=weatherdir...@pelmorex.ca, size=35572, nrcpt=1 (queue active)
Nov 12 12:26:57 app dovecot: deliver(gfi...@app.ldmltd.ca): sieve:
msgid=3708845-2200911412202651...@pelmorex.ca: failed to store into
mailbox 'Public/Weather': Permission denied
Nov 12 12:26:57 app dovecot: deliver(gfi...@app.ldmltd.ca): sieve:
msgid=3708845-2200911412202651...@pelmorex.ca: stored mail into
mailbox 'INBOX'
Nov 12 12:26:57 app dovecot: deliver(gfi...@app.ldmltd.ca): sieve:
execution of script /srv/dovecot/gfinch/.dovecot.sieve failed, but
implicit keep was successful
Nov 12 12:26:57 app postfix/pipe[15363]: B36E77800088:
to=gfi...@app.ldmltd.ca, relay=dovecot, delay=0.66,
delays=0.62/0/0/0.05, dsn=2.0.0, status=sent (delivered via dovecot service)
Nov 12 12:26:57 app postfix/qmgr[19314]: B36E77800088: removed
Nov 12 12:26:57 app postfix/smtpd[15365]: disconnect from
mail127c0.megamailservers.com[69.49.121.237]
maillog - showing working
Nov 12 09:44:42 app postfix/smtpd[13094]: connect from
dovecot.org[82.118.211.50]
Nov 12 09:44:42 app postfix/smtpd[13094]: E08BC7800085:
client=dovecot.org[82.118.211.50]
Nov 12 09:44:43 app postfix/cleanup[13097]: E08BC7800085:
message-id=1258047854.3022.401.ca...@timo-desktop
Nov 12 09:44:43 app postfix/qmgr[19314]: E08BC7800085:
from=dovecot-bounces+gfinch=app.ldmltd...@dovecot.org, size=2518,
nrcpt=1 (queue active)
Nov 12 09:44:43 app postfix/smtpd[13094]: disconnect from
dovecot.org[82.118.211.50]
Nov 12 09:44:43 app dovecot: deliver(gfi...@app.ldmltd.ca): sieve:
msgid=1258047854.3022.401.ca...@timo-desktop: stored mail into mailbox
'Dovecot'
Nov 12 09:44:43 app postfix/pipe[13099]: E08BC7800085:
to=gfi...@app.ldmltd.ca, relay=dovecot, delay=0.32,
delays=0.27/0.01/0/0.05, dsn=2.0.0, status=sent (delivered via dovecot
service)
Nov 12 09:44:43 app postfix/qmgr[19314]: E08BC7800085: removed
As for the permissions, I can save messages to the public folder with
no problems from my email client over IMAP, so I'm assuming the acl file
is correct.
dovecot-acl for Public/Weather
authenticated lrs
user=gfinch lrwstipekxa
# 1.2.6: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.23.1-smp-LDM i686 Slackware 12.0.0
base_dir: /var/run/dovecot/
protocols: imap imaps managesieve
ssl_ca_file: /etc/dovecot/ca.pem
ssl_cert_file: /etc/dovecot/dovecot1.crt
ssl_key_file: /etc/dovecot/dovecot1.key
login_dir: /var/run/dovecot//login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login
verbose_proctitle: yes
first_valid_gid: 500
mail_uid: 500
mail_gid: 500
mail_location: maildir:~/Maildir:LAYOUT=fs
fsync_disable: yes
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve
mail_plugins(default): acl imap_acl
mail_plugins(imap): acl imap_acl
mail_plugins(managesieve):
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve
imap_idle_notify_interval(default): 1200
imap_idle_notify_interval(imap): 1200
imap_idle_notify_interval(managesieve): 120
namespace:
type: private
inbox: yes
list: yes
subscriptions: yes
namespace:
type: shared
separator: /
prefix: Shared/%%u/
location: maildir:%%h/Maildir:LAYOUT=fs:INDEX=~/shared/%%u
list: children
namespace:
type: public
separator: /
prefix: Public/
location: maildir:/srv/dovecot/public:LAYOUT=fs:INDEX=~/public
list: children
lda:
postmaster_address: postmas...@ldmltd.ca
mail_plugins: acl sieve
fsync_disable: no
auth default:
mechanisms: plain login digest-md5 cram-md5
passdb:
driver: passwd-file
args: username_format=%Ln /etc/dovecot/passwd
userdb:
driver: static
args: uid=500 gid=500 home=/srv/dovecot/%Ln
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 432
user: postfix
group: postfix
master:
path:
Re: [Dovecot] sieve files wont get parsed/compiled using cmusieve
On Thu, 2009-11-12 at 17:49 +0100, Moritz Krinke wrote: Timo: in the protocol lda section i've got mail_plugins = cmusieve so it should be active. please see my original message from the 7th of November. Here is the complete output in my log concerning dovecot and one message which should have been placed in a subdir of inbox by a sieve rule: Your log doesn't show this message: Loading modules from directory: That means deliver thinks mail_plugins setting is empty. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Deliver and file system quota
On Thu, 2009-11-12 at 12:22 +0100, Rainer Frey wrote: Hi, what is the quota plugin for deliver supposed to do when using fs quota? The same as with IMAP APPEND command (it uses the exact same code). So is there any effect of the quota plugin in lda with file system quota? If you don't see any difference, there's some configuration problem that causes quota plugin to be disabled with deliver. mail_debug=yes could be helpful in debugging. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Sieve and ACL problem
On Thu, 2009-11-12 at 14:29 -0800, Gregory Finch wrote: Nov 12 12:26:57 app dovecot: deliver(gfi...@app.ldmltd.ca): sieve: msgid=3708845-2200911412202651...@pelmorex.ca: failed to store into mailbox 'Public/Weather': Permission denied .. dovecot-acl for Public/Weather authenticated lrs user=gfinch lrwstipekxa deliver sees username as gfi...@app.ldmltd.ca, not gfinch. Maybe change deliver to be called as: deliver -d gfinch -a gfi...@app.ldmltd.ca signature.asc Description: This is a digitally signed message part
Re: [Dovecot] read/connect anvil-auth-penalty failed: EOF/Connection refused
On Thu, 2009-11-12 at 03:26 +0100, Pascal Volk wrote: Nov 12 03:17:00 master: Warning: Killed with signal 15 (by pid=31656 uid=0 code=kill) Nov 12 03:17:00 auth: Error: read(anvil-auth-penalty) failed: EOF Nov 12 03:17:00 auth: Error: net_connect_unix(anvil-auth-penalty) failed: Connection refused Nov 12 03:17:00 auth: Error: read(anvil-auth-penalty) failed: EOF Nov 12 03:17:00 auth: Error: net_connect_unix(anvil-auth-penalty) failed: Connection refused http://hg.dovecot.org/dovecot-2.0/rev/506fba223006 should fix it. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 2009-11-12 at 15:42 -0800, Jordan Tardif wrote: Is there a way to disable this feature? Seems to be causing more harm then good right now. Without getting into too much details it is fixing the duplcates but it does not remove the old file, and the new file it creates is not marked as read like the old one was. I understand that this problem can be created by multiple rsyncs and files changing in between, but is there any way that I can just turn this feature off all together? I do not see anything in the wiki regrading settings to disable. There's no way to disable it, because it shouldn't be happening in the first place. If your rsyncs are causing it, maybe you should be using e.g. maildirlock utility to make sure Dovecot's not changing the maildir while rsync is writing. Or you could of course always just comment out that code. Heres a litle bit of background on what we are doing and maybe if you have time you can let me know what you think the best way of doing this would be. When we move users to dovecot servers, we first create a new user on the destination machine, then do a rsync from the old user (that contains all the courier* files) to the new one, and then run the migration script found in the dovecot wiki to convert the courier* files to dovecot*. 6 Hours later we rsync from the old user to the new one again to make sure that any emails that have been delived to the old user while dns updates make it to the new users account. Then we run the migration script again with --overwrite so it creates the new courier* files. Would you also reccomend removing any dovecot.index.cache files at this time as well? Can you think of another way to do this move so that dovecot would not have this problem with duplicates? -- Jordan Tardif DreamHost
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 2009-11-12 at 16:04 -0800, Jordan Tardif wrote: Heres a litle bit of background on what we are doing and maybe if you have time you can let me know what you think the best way of doing this would be. When we move users to dovecot servers, we first create a new user on the destination machine, then do a rsync from the old user (that contains all the courier* files) to the new one, and then run the migration script found in the dovecot wiki to convert the courier* files to dovecot*. 6 Hours later we rsync from the old user to the new one again to make sure that any emails that have been delived to the old user while dns updates make it to the new users account. Then we run the migration script again with --overwrite so it creates the new courier* files. Would you also reccomend removing any dovecot.index.cache files at this time as well? Can you think of another way to do this move so that dovecot would not have this problem with duplicates? When do the imap/pop3 sessions actually start using the new machine? Does that depend on DNS also? Running migration script multiple times isn't a good idea. It can change IMAP UIDs and cause trouble with clients that use a local cache. It could even lose messages since client doesn't realize that there's a new message with an existing one's UID.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 2009-11-12 at 16:04 -0800, Jordan Tardif wrote: Heres a litle bit of background on what we are doing and maybe if you have time you can let me know what you think the best way of doing this would be. When we move users to dovecot servers, we first create a new user on the destination machine, then do a rsync from the old user (that contains all the courier* files) to the new one, and then run the migration script found in the dovecot wiki to convert the courier* files to dovecot*. 6 Hours later we rsync from the old user to the new one again to make sure that any emails that have been delived to the old user while dns updates make it to the new users account. Then we run the migration script again with --overwrite so it creates the new courier* files. Would you also reccomend removing any dovecot.index.cache files at this time as well? Can you think of another way to do this move so that dovecot would not have this problem with duplicates? When do the imap/pop3 sessions actually start using the new machine? Does that depend on DNS also? Running migration script multiple times isn't a good idea. It can change IMAP UIDs and cause trouble with clients that use a local cache. It could even lose messages since client doesn't realize that there's a new message with an existing one's UID.. Yes that depends on DNS updating. So is there not way to avoid this Duplication problem if you need to do an rsync 2x? -- Jordan Tardif DreamHost
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 2009-11-12 at 16:12 -0800, Jordan Tardif wrote: Yes that depends on DNS updating. So is there not way to avoid this Duplication problem if you need to do an rsync 2x? Not really. The move should preferably be atomic.. With Dovecot v2.0 there's dsync utility, which would pretty much do what you want. But that doesn't really help you yet. I guess the easiest solution would be to: 1) Remove the duplicate detection/fixing code from Dovecot code. 2) Create a script that resolves duplicates by deleting one of them. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Sieve and ACL problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Sirainen wrote:
On Thu, 2009-11-12 at 14:29 -0800, Gregory Finch wrote:
Nov 12 12:26:57 app dovecot: deliver(gfi...@app.ldmltd.ca): sieve:
msgid=3708845-2200911412202651...@pelmorex.ca: failed to store into
mailbox 'Public/Weather': Permission denied
..
dovecot-acl for Public/Weather
authenticated lrs
user=gfinch lrwstipekxa
deliver sees username as gfi...@app.ldmltd.ca, not gfinch. Maybe change
deliver to be called as:
deliver -d gfinch -a gfi...@app.ldmltd.ca
That solved my problem entirely.. changing the dovecot line in my
postfix/master.cf from -d ${recipient} to the following makes
everything work as expected, including using the right acl files when
using sieve to redirect to a public folder:
dovecot unix- n n - - pipe
flags=DR user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f
${sender} -d ${user} -a ${recipient} -n -m ${extension}
Thank you,
- -Greg
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkr8oKYACgkQeflWWP27iA/ZHQCg1ozpUBBn0mbNetBsjv5aUjvG
eX8AnRRfrg+bIS6ddcyNMbLJee92Whg1
=Rjk/
-END PGP SIGNATURE-
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 2009-11-12 at 15:42 -0800, Jordan Tardif wrote: Is there a way to disable this feature? Seems to be causing more harm then good right now. Without getting into too much details it is fixing the duplcates but it does not remove the old file, and the new file it creates is not marked as read like the old one was. I understand that this problem can be created by multiple rsyncs and files changing in between, but is there any way that I can just turn this feature off all together? I do not see anything in the wiki regrading settings to disable. There's no way to disable it, because it shouldn't be happening in the first place. If your rsyncs are causing it, maybe you should be using e.g. maildirlock utility to make sure Dovecot's not changing the maildir while rsync is writing. Or you could of course always just comment out that code. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 12 Nov 2009, Timo Sirainen wrote: On Thu, 2009-11-12 at 16:12 -0800, Jordan Tardif wrote: Yes that depends on DNS updating. So is there not way to avoid this Duplication problem if you need to do an rsync 2x? Not really. The move should preferably be atomic.. With Dovecot v2.0 there's dsync utility, which would pretty much do what you want. But that doesn't really help you yet. I guess the easiest solution would be to: 1) Remove the duplicate detection/fixing code from Dovecot code. 2) Create a script that resolves duplicates by deleting one of them. So if I do #1 , do you see this causing any other problems with dovecot? -- Jordan Tardif DreamHost
Re: [Dovecot] Turning off Fixed Duplicates feature
On Thu, 2009-11-12 at 16:22 -0800, Jordan Tardif wrote:
I guess the easiest solution would be to:
1) Remove the duplicate detection/fixing code from Dovecot code.
2) Create a script that resolves duplicates by deleting one of them.
So if I do #1 , do you see this causing any other problems with dovecot?
I actually meant that you should do both. But no, 1) shouldn't cause
problems.
Or actually looking at the code, it already tries to detect duplicate
hard links and unlinks one of them. You could change the code from:
if (st1.st_ino == st2.st_ino
CMP_DEV_T(st1.st_dev, st2.st_dev)) {
/* Files are the same. this means either a race condition
between stat() calls, or that the files were link()ed. */
if (st1.st_nlink 1 st2.st_nlink == st1.st_nlink
st1.st_ctime == st2.st_ctime
st1.st_ctime ioloop_time - DUPE_LINKS_DELETE_SECS) {
to just something like:
if (st1.st_size == st2.st_size) {
and then some day when your migrations are done switch it back.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Turning off Fixed Duplicates feature
I actually meant that you should do both. But no, 1) shouldn't cause
problems.
Or actually looking at the code, it already tries to detect duplicate
hard links and unlinks one of them. You could change the code from:
if (st1.st_ino == st2.st_ino
CMP_DEV_T(st1.st_dev, st2.st_dev)) {
/* Files are the same. this means either a race condition
between stat() calls, or that the files were link()ed. */
if (st1.st_nlink 1 st2.st_nlink == st1.st_nlink
st1.st_ctime == st2.st_ctime
st1.st_ctime ioloop_time - DUPE_LINKS_DELETE_SECS) {
to just something like:
if (st1.st_size == st2.st_size) {
and then some day when your migrations are done switch it back.
This looks like it has done the trick! Thank you very much! Looking
forward to dovecot 2.0
--
Jordan Tardif
DreamHost
