Re: [Dovecot] Error or bug?
Robby Gunawan wrote on 10/21/2010: Dear all, Please help me, I just change from vm-pop3d to dovecot, installed from rpm that provided by dovecot.org, I got this error for random email user Command died with signal 11: /usr/libexec/dovecot/deliver maybe this patch helps? http://hg.dovecot.org/dovecot-2.0/rev/e2f9baa436f2 -- Daniel
[Dovecot] 2.0.5 Error: Timeout waiting for handshake from auth server.
Hello, Upgraded from 1.2.x to 2.0.5, converted configuration as described in http://wiki2.dovecot.org/Upgrading/2.0 and now I'm unable to log in to imap server. Dovecot error.log shows: Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13338, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13364, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13337, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13350, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13335, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13360, input bytes=0 I'm using pam with winbind for authentication. /etc/pam.d/dovecot contains: authrequired pam_winbind.so account sufficient pam_winbind.so And it used to work perfectly with 1.1 and 1.2 series of dovecot. What could be the problem with 2.0.5? -- Veiko
Re: [Dovecot] anti-spam+anti-malware suggestions
Jose Luis Faria put forth on 10/20/2010 11:20 AM: Hello people, I am using now qmail in cluster with LDAP + Interscan Messaging Security Suite from Trendmicro. I need to develop a new solution with: - postfix - dovecot - anti-spam - anti-malware. I am thankful any help or suggestion for anti-spam and anti-malware. Thanks in advance! This will kill a huge amount of bot spam without dnsbl queries or greylisting, both of which can be resource hogs and add serious latency: http://www.hardwarefreak.com/fqrdns.pcre Use the everything under smtpd_recipient_restrictions style of Postfix main.cf: /etc/postfix/main.cf smtpd_recipient_restrictions permit_mynetworks permit_sasl_authenticated reject_unauth_destination ... ... check_client_access pcre:/etc/postfix/fqrdns.pcre ... ... Ask for assistance on the Postfix users list: postfix-us...@postfix.org You'll get more expert advice than you will know what to do with. ;) -- Stan
Re: [Dovecot] anti-spam+anti-malware suggestions
Denny Lin wrote on 10/20/2010: Currently, I am using a setup with Postfix + Dovecot as well. We're using these DNSBL blacklists: zen.spamhaus.org b.barracudacentral.org cbl.abuseat.org bl.spamcop.net dnsbl.njabl.org info: it's not needed to use cbl.abuseat.org AND zen.spamhaus.org because the data from cbl is included in zen. Link: http://cbl.abuseat.org/faq.html -- Daniel
Re: [Dovecot] anti-spam+anti-malware suggestions
Jose Luis Faria wrote on 10/20/2010: Hello people, I am using now qmail in cluster with LDAP + Interscan Messaging Security Suite from Trendmicro. I need to develop a new solution with: - postfix - dovecot - anti-spam - anti-malware. I am thankful any help or suggestion for anti-spam and anti-malware. you can use several blacklists or header/body checks to block spam or malware to save your ressources. Another useful feature is the upcoming Postfix server postscreen - this feature will be available in Postfix 2.8. Info: http://www.postfix.org/POSTSCREEN_README.html Some header checks and maybe zen.spamhaus.org should block 85-95% of spam. All other messages can be scanned with spamassassin/amavisd/clamav or other commercial products. To block malware you could also look at: http://www.malwarepatrol.net/ Start with some good Postfix restrictions and then you can extend your setup with other filters/blacklists... -- Daniel
Re: [Dovecot] Error or bug?
Robby Gunawan wrote on 10/21/2010: how do I install / update to my system? Normally you should patch the file(s) in the source package. You can compile Dovecot from the official sources (apply the patch before), download/install Dovecot from Mercurial (hg.dovecot.org) or open a bugreport for the package maintainer so that the bug can be fixed for your distribution. -- Daniel
Re: [Dovecot] minimize mbox mdbox fragmentation
On Oct 20, 2010, at 10:14 PM, Timo Sirainen wrote: On 21.10.2010, at 3.12, Denny Lin wrote: On Wed, Oct 20, 2010 at 06:45:17PM +0100, Timo Sirainen wrote: On Wed, 2010-10-20 at 13:32 -0400, Charles Marcus wrote: On 2010-10-20 12:53 PM, Timo Sirainen wrote: Oh, interesting. I didn't know that was possible. And even better: Linux has fallocate() that can do it for other filesystems than just XFS. Or looks like it's only XFS and ext4 (ext3 doesn't support it). How about reiserfs (3, not 4)? Doesn't support. Is it possible with UFS and ZFS? Linux doesn't support either and my googling didn't find any FreeBSD or Solaris interface for this feature, so I don't know. AIX supports posix_fallocate but only for JFS2. For GPFS(what we use), the function is gpfs_prealloc. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] minimize mbox mdbox fragmentation
On 20/10/2010 18:32, Charles Marcus wrote: On 2010-10-20 12:53 PM, Timo Sirainen wrote: Oh, interesting. I didn't know that was possible. And even better: Linux has fallocate() that can do it for other filesystems than just XFS. Or looks like it's only XFS and ext4 (ext3 doesn't support it). How about reiserfs (3, not 4)? Though in the case of the small number of large files (i.e. the opposite of ReiserFS's strength), which you would get with mbox and mdbox, one would have to ask what upside ReiserFS would bring to the party which would outweigh the downside that Namesys is kaput and Hans Reiser is currently serving 15 years to life for second degree murder in a California State Prison... Bill
[Dovecot] Segfault in libdovecot-sieve
Hello, I've been getting these messages in dmesg: [1663649.206652] lmtp[4961]: segfault at 18 ip 7fb5b6aab1f0 sp7fff7e3b5468 error 4 innbsp;libdovecot-sieve.so.0.0.0[7fb5b6a6d000 +66000] Dovecot's version is 2.0.3. Is this known? What other kind of information could be useful to help find this issue? Thanks,Andre
Re: [Dovecot] Segfault in libdovecot-sieve
Op 21-10-2010 14:29, an...@digirati.com.br schreef: Hello, I've been getting these messages in dmesg: [1663649.206652] lmtp[4961]: segfault at 18 ip 7fb5b6aab1f0 sp7fff7e3b5468 error 4 innbsp;libdovecot-sieve.so.0.0.0[7fb5b6a6d000 +66000] Dovecot's version is 2.0.3. Is this known? What other kind of information could be useful to help find this issue? Thanks,Andre 1) Your config: Output from: dovecot -n What version/revision of Pigeonhole you installed. 2) Gdb backtrace: http://www.dovecot.org/bugreport.html Try to obtain core dumps when it is hard to reproduce. 3) Examples of scripts and messages that cause the problem (assuming it is reproducible). Regards, Stephan
Re: [Dovecot] minimize mbox mdbox fragmentation
On 2010-10-21 6:58 AM, William Blunn wrote: Though in the case of the small number of large files (i.e. the opposite of ReiserFS's strength), which you would get with mbox and mdbox, Good point... one would have to ask what upside ReiserFS would bring to the party which would outweigh the downside that Namesys is kaput and Hans Reiser is currently serving 15 years to life for second degree murder in a California State Prison... Please don't politicize the issue. Reiserfs is not 'kaput', it is still being maintained in the linux kernel (both v3 and work is ongoing for v4), and will be for the foreseeable future. -- Best regards, Charles
Re: [Dovecot] anti-spam+anti-malware suggestions
On 2010-10-20 10:18 PM, Denny Lin wrote: Postfix's address verification is also quite useful for popular domains like gmail.com, hotmail.com, yahoo.com, etc. If you mean you are using *sender* address verification on these domains, you will eventually get blacklisted by them if your system has much traffic from them. Most Mail Admins consider blanket SAV as an abuse of their systems. SAV (sender address verification) should be used sparingly, and only with domains/systems that are ok with you using it. -- Best regards, Charles
Re: [Dovecot] anti-spam+anti-malware suggestions
Does someone run dspam or just me?? I like very much this antispam solution. On 10/21/10, Charles Marcus cmar...@media-brokers.com wrote: On 2010-10-20 10:18 PM, Denny Lin wrote: Postfix's address verification is also quite useful for popular domains like gmail.com, hotmail.com, yahoo.com, etc. If you mean you are using *sender* address verification on these domains, you will eventually get blacklisted by them if your system has much traffic from them. Most Mail Admins consider blanket SAV as an abuse of their systems. SAV (sender address verification) should be used sparingly, and only with domains/systems that are ok with you using it. -- Best regards, Charles -- Sent from my mobile device
Re: [Dovecot] anti-spam+anti-malware suggestions
On Thu, Oct 21, 2010 at 09:26:46AM -0400, Charles Marcus wrote: On 2010-10-20 10:18 PM, Denny Lin wrote: Postfix's address verification is also quite useful for popular domains like gmail.com, hotmail.com, yahoo.com, etc. If you mean you are using *sender* address verification on these domains, you will eventually get blacklisted by them if your system has much traffic from them. Most Mail Admins consider blanket SAV as an abuse of their systems. SAV (sender address verification) should be used sparingly, and only with domains/systems that are ok with you using it. Oh yeah, I forgot to mention that. A better solution would be to check the rDNS or SPF record and do sender verification if it doesn't match. -- Denny Lin
Re: [Dovecot] Segfault in libdovecot-sieve
Em 21/10/2010, Stephan Bosch lt;step...@rename-it.nlgt; escreveu:
gt; nbsp; Output from: dovecot -n
# 2.0.3 (02a9cf90ad02): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-25-server x86_64 Ubuntu 10.04.1 LTSnbsp;
auth_master_user_separator = *
auth_mechanisms = plain login
auth_username_chars =
abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz01234567890...@=
auth_worker_max_count = 10
disable_plaintext_auth = no
listen = lmtp1.f1.k8.com.br, lmtp1.prv.f1.k8.com.br
login_greeting = K8 IMAP/POP3 server
mail_debug = yes
mail_gid = dovemail
mail_plugins = $mail_plugins quota
mail_uid = dovemail
managesieve_sieve_capability = fileinto reject envelope vacation subaddress
comparator-i;ascii-numeric relational regex imap4flags copy include imapflags
notify
mmap_disable = yes
passdb {
nbsp;nbsp;args = /etc/dovecot/dovecot-sql.conf.ext
nbsp;nbsp;driver = sql
}
passdb {
nbsp;nbsp;args = /etc/dovecot/dovecot-sql-master.conf.ext
nbsp;nbsp;driver = sql
nbsp;nbsp;master = yes
nbsp;nbsp;pass = yes
}
plugin {
nbsp;nbsp;autocreate = SPAM
nbsp;nbsp;autosubscribe = SPAM
nbsp;nbsp;quota = dict:User
quota::file:/var/lib/imap/user/%2.256RHn/%n/dovecot-quota
nbsp;nbsp;quota_rule = *:storage=1GB
nbsp;nbsp;sieve = /var/lib/imap/sieve/%2.256RHn/%n/phpscript.script
nbsp;nbsp;sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n
nbsp;nbsp;sieve_extensions = comparator-i;ascii-numeric copy envelope
fileinto imapflags include notify regex reject relational subaddress vacation
nbsp;nbsp;sieve_max_script_size = 512KB
nbsp;nbsp;sieve_quota_max_scripts = 2
}
protocols = imap pop3 lmtp sieve
service auth-worker {
nbsp;nbsp;user = $default_internal_user
}
service auth {
nbsp;nbsp;process_limit = 1
nbsp;nbsp;process_min_avail = 1
}
service imap-login {
nbsp;nbsp;inet_listener imap {
nbsp;nbsp; nbsp;address = lmtp1.f1.k8.com.br, box5.f1.k8.com.br
nbsp;nbsp; nbsp;port = 143
nbsp;nbsp;}
}
service imap {
nbsp;nbsp;process_limit = 1024
nbsp;nbsp;process_min_avail = 10
}
service lmtp {
nbsp;nbsp;inet_listener {
nbsp;nbsp; nbsp;address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
nbsp;nbsp; nbsp;port = 2003
nbsp;nbsp;}
nbsp;nbsp;process_limit = 256
nbsp;nbsp;process_min_avail = 10
}
service managesieve-login {
nbsp;nbsp;inet_listener sieve {
nbsp;nbsp; nbsp;address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
nbsp;nbsp; nbsp;port = 4190
nbsp;nbsp;}
nbsp;nbsp;inet_listener sieve_deprecated {
nbsp;nbsp; nbsp;address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
nbsp;nbsp; nbsp;port = 2000
nbsp;nbsp;}
}
service managesieve {
nbsp;nbsp;process_limit = 20
nbsp;nbsp;process_min_avail = 10
}
service pop3-login {
nbsp;nbsp;inet_listener pop3 {
nbsp;nbsp; nbsp;address = lmtp1.f1.k8.com.br, box5.f1.k8.com.br
nbsp;nbsp; nbsp;port = 110
nbsp;nbsp;}
}
service pop3 {
nbsp;nbsp;process_limit = 256
nbsp;nbsp;process_min_avail = 10
}
ssl = no
userdb {
nbsp;nbsp;driver = prefetch
}
userdb {
nbsp;nbsp;args = /etc/dovecot/dovecot-sql.conf.ext
nbsp;nbsp;driver = sql
}
verbose_proctitle = yes
protocol imap {
nbsp;nbsp;imap_idle_notify_interval = 120 s
nbsp;nbsp;imap_max_line_length = 65536
nbsp;nbsp;mail_max_userip_connections = 50
nbsp;nbsp;mail_plugins = $mail_plugins quota imap_quota autocreate
}
protocol lmtp {
nbsp;nbsp;mail_plugins = $mail_plugins sieve quota autocreate
}
protocol sieve {
nbsp;nbsp;mail_plugins = $mail_plugins sieve
nbsp;nbsp;managesieve_implementation_string = K8 ManageSieve
nbsp;nbsp;managesieve_logout_format = bytes=%i/%o
nbsp;nbsp;managesieve_max_line_length = 65536
nbsp;nbsp;managesieve_sieve_capability = comparator-i;ascii-numeric copy
envelope fileinto imapflags include notify regex reject relational subaddress vacation
}
protocol pop3 {
nbsp;nbsp;mail_plugins = $mail_plugins quota autocreate
}
gt; nbsp; What version/revision of Pigeonhole you installed.
I'm using recompiled debian packages from http://xi.rename-it.nl/debian/ which
already come with pigeonhole. The last changelog entry is fromnbsp;2010-08-14.
gt; 2) Gdb backtrace:
gt;nbsp;
gt; http://www.dovecot.org/bugreport.html
gt;nbsp;
gt; Try to obtain core dumps when it is hard to reproduce.
gt;nbsp;
gt; 3) Examples of scripts and messages that cause the problem (assuming
itnbsp;
gt; is reproducible).
I'll work on these. The server is hosting a few thousand accounts, so it's hard
to identify specific scripts.
Thanks,Andre
Re: [Dovecot] anti-spam+anti-malware suggestions
On Thu, 21 Oct 2010 11:37:40 -0200, Fabricio Archanjo farcha...@gmail.com wrote: Does someone run dspam or just me?? I like very much this antispam solution. I use dspam + sqlgrey + policyd-weight to prevent spam. 60% rejects are invalid recipient drop 30% nonreturning from sqlgrey 10% goes to dspam with autolearning. -- Pozdrawiam Paweł Madej
Re: [Dovecot] anti-spam+anti-malware suggestions
On 2010-10-21 9:37 AM, Fabricio Archanjo wrote: Does someone run dspam or just me?? I like very much this antispam solution. I *much* prefer ASSP myself... Vastly easier to install/configure than dspam, and more effective too imnsho, *especially out of the box, but even also after dspam is properly trained... -- Best regards, Charles
Re: [Dovecot] anti-spam+anti-malware suggestions
On Thu, 21 Oct 2010 21:52:38 +0800 Denny Lin dennyli...@hs.ntnu.edu.tw articulated: Oh yeah, I forgot to mention that. A better solution would be to check the rDNS or SPF record and do sender verification if it doesn't match. Actually, SPF has been going out of vogue for awhile now and sensible mail admins do not make accept/deny decisions entirely on pass/fail of SPF tests. Many SAs are finding it causes more problems than it solves. When added to the fact that its use is by no means universal, its continued use is seriously in doubt. In other words, Use at your own risk. There are, as has been pointed out, better methods available. -- Jerry ✌ dovecot.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ The reason we start a war is to fight a war, win a war, thereby causing no more war. George W. Bush October 3, 2000 Boston, Massachusetts. First Presidential Debate
Re: [Dovecot] anti-spam+anti-malware suggestions
On Thu, Oct 21, 2010 at 10:18:46AM -0400, Jerry wrote: On Thu, 21 Oct 2010 21:52:38 +0800 Denny Lin dennyli...@hs.ntnu.edu.tw articulated: Oh yeah, I forgot to mention that. A better solution would be to check the rDNS or SPF record and do sender verification if it doesn't match. Actually, SPF has been going out of vogue for awhile now and sensible mail admins do not make accept/deny decisions entirely on pass/fail of SPF tests. Many SAs are finding it causes more problems than it solves. When added to the fact that its use is by no means universal, its continued use is seriously in doubt. In other words, Use at your own risk. There are, as has been pointed out, better methods available. True, that's why I only use it to verify whether sender verification should be done (at least it can tell me if the mail was sent from Gmail servers, etc.). -- Denny Lin
[Dovecot] allow_nets and local sockets
Hello, i am running dovevot 2.0.5 using ldap authentication with the allow_nets paramter to limit access to some local networks. The problem is, when i want to use the local lmtp socket from postfix *virtual_transport = lmtp:unix:private/dovecot-lmtp * i get the follwing error: *Oct 21 15:48:03 auth: Info: passdb(username): allow_nets check failed: Remote IP not known *When using the TCP socket with postfix *virtual_transport = lmtp:localhost:30025 *it is working. (i have 127.0.0.0/8 in the allow_nets list) Is there a way, other than using two different config sets to get this working together ? Something like disabling the address lookup on local passdb sockets ? Regards, Oliver
Re: [Dovecot] minimize mbox mdbox fragmentation
On 21/10/2010 14:25, Charles Marcus wrote: Reiserfs is not 'kaput', it is still being maintained in the linux kernel (both v3 and work is ongoing for v4), and will be for the foreseeable future. For the benefit of anyone reading this and wondering Well is it kaput or not?: Charles and I are both right. I said that *Namesys* was kaput. Namesys was the company which developed ReiserFS. Charles stated correctly (but perhaps confusingly when done as a reply to my comment) that *ReiserFS* is not kaput. We were talking about two different things. The company is dead, but the software (being open source) lives on. Bill
Re: [Dovecot] minimize mbox mdbox fragmentation
On Wed, 2010-10-20 at 23:50 -0500, Stan Hoeppner wrote: Oh, interesting. I didn't know that was possible. And even better: Linux has fallocate() that can do it for other filesystems than just XFS. Or looks like it's only XFS and ext4 (ext3 doesn't support it). I don't know if other OSes support this. There exists posix_fallocate() which would widen the platforms that would support this Timo. I know about posix_fallocate(), but that does a different thing. It would work only when this works: Maybe in future I could make mdbox support writing to files whose size has been preallocated by actually writing NUL bytes, but that requires some extra code. You may also want to look at posix_fadvise() as well (if you're not using it already) which might increase Dovecot's overall disk performance a bit. I once wrote a patch for that and asked if anyone could confirm if it made things worse or better, but no one ever did. http://dovecot.org/list/dovecot/2007-November/026819.html NOTE: I don't believe fallocate() in either posix or linux only form will actually accomplish decreased m[d]box file fragmentation. I don't believe it actually increases the file size on disk, i.e. physically allocating additional free extents tailing the end of the file. fallocate() is _speculative_ preallocation, which isn't what you want. Why do you believe that? The man pages and everything tell me that it's about physical preallocation: fallocate is used to preallocate blocks to a file. For filesystems which support the fallocate system call, this is done quickly by allo‐ cating blocks and marking them as uninitialized, requiring no IO to the data blocks. This is much faster than creating a file by filling it with zeros. Also du shows that the file's size is actually the preallocated size. That's how I checked which filesystems supported it. And I think Linux fallocate() with XFS internally does exactly what XFS_IOC_RESVSP does, which your quoted mail mentioned being about physical preallocation. I don't know if it changes anything in the sequence above, but Dovecot uses mmap i/o. mmap is used only for index files, not for mdbox files. It would be beneficial I think if you'd sub to the xfs list Timo and pick some brains. Maybe, but there is still so much other stuff to do, like bug fixing. :)
Re: [Dovecot] allow_nets and local sockets
On Thu, 2010-10-21 at 16:37 +0200, Oliver Eales wrote:
*virtual_transport = lmtp:unix:private/dovecot-lmtp *
LMTP does a userdb lookup normally.
*Oct 21 15:48:03 auth: Info: passdb(username): allow_nets check failed:
Remote IP not known
So this shouldn't be happening. Are you using userdb static, and Dovecot
is doing a passdb lookup because of it? Could you replace it with userdb
lookup for lmtp-only?
protocol lmtp {
userdb {
driver = ldap
args = dovecot-ldap.conf
}
}
[Dovecot] bug with null pointer
Hi, we found a serious bug while testing our migration scripts. in Solaris (or other system 5) the user variable is not always set. Dsync is not very happy about that and crashes with an segmentation fault. After hours of debugging and TWOE simple lines # USER=$LOGNAME # export USER the problem was solved! The null pointer was found - so i will go home now an drink a bottle of Erdinger... hope this hint helps for development - and we hope that we don't find more of these bugs :) bye Tobi -- Dr. Nagler Company GmbH Hauptstraße 9 92253 Schnaittenbach Tel : 09622-7197-38 Fax : 09622-7197-50 Web : http://www.nagler-company.com E-Mail : tobias.dauc...@nagler-company.com Hauptsitz: Schnaittenbach Handelregister: Amberg HRB 4653 Gerichtsstand: Amberg Steuernummer: 201/118/51825 USt.-ID-Nummer: DE 273143997 Geschäftsführer:Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze
Re: [Dovecot] bug with null pointer
On Thu, 2010-10-21 at 17:08 +0200, Tobias Daucher wrote: we found a serious bug while testing our migration scripts. in Solaris (or other system 5) the user variable is not always set. Dsync is not very happy about that and crashes with an segmentation fault. Thanks, fixed: http://hg.dovecot.org/dovecot-2.0/rev/760d84e274ad
Re: [Dovecot] minimize mbox mdbox fragmentation
On 2010-10-21 10:40 AM, William Blunn wrote: On 21/10/2010 14:25, Charles Marcus wrote: Reiserfs is not 'kaput', it is still being maintained in the linux kernel (both v3 and work is ongoing for v4), and will be for the foreseeable future. For the benefit of anyone reading this and wondering Well is it kaput or not?: Charles and I are both right. I said that *Namesys* was kaput. Namesys was the company which developed ReiserFS. Charles stated correctly (but perhaps confusingly when done as a reply to my comment) that *ReiserFS* is not kaput. We were talking about two different things. The company is dead, but the software (being open source) lives on. That was my point... the way it was worded your comment could be interpreted as the same as reiserfs being kaput. I merely pointed out that the original programmers company/website of an open-source project whose code is and has been included in the mainline kernel for a very long time being kaput is far far from the same as the filesystem itself being kaput - which was the last part of your comment. -- Best regards, Charles
Re: [Dovecot] Segfault in libdovecot-sieve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 21.10.2010 16:13, an...@digirati.com.br a écrit :
Em 21/10/2010, Stephan Bosch lt;step...@rename-it.nlgt; escreveu:
gt; nbsp; Output from: dovecot -n
# 2.0.3 (02a9cf90ad02): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-25-server x86_64 Ubuntu 10.04.1 LTSnbsp;
auth_master_user_separator = *
auth_mechanisms = plain login
auth_username_chars =
abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz01234567890...@=
auth_worker_max_count = 10
disable_plaintext_auth = no
listen = lmtp1.f1.k8.com.br, lmtp1.prv.f1.k8.com.br
login_greeting = K8 IMAP/POP3 server
mail_debug = yes
mail_gid = dovemail
mail_plugins = $mail_plugins quota
mail_uid = dovemail
managesieve_sieve_capability = fileinto reject envelope vacation
subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include imapflags notify
mmap_disable = yes
passdb {
nbsp;nbsp;args = /etc/dovecot/dovecot-sql.conf.ext
nbsp;nbsp;driver = sql
}
passdb {
nbsp;nbsp;args = /etc/dovecot/dovecot-sql-master.conf.ext
nbsp;nbsp;driver = sql
nbsp;nbsp;master = yes
nbsp;nbsp;pass = yes
}
plugin {
nbsp;nbsp;autocreate = SPAM
nbsp;nbsp;autosubscribe = SPAM
nbsp;nbsp;quota = dict:User
quota::file:/var/lib/imap/user/%2.256RHn/%n/dovecot-quota
nbsp;nbsp;quota_rule = *:storage=1GB
nbsp;nbsp;sieve = /var/lib/imap/sieve/%2.256RHn/%n/phpscript.script
nbsp;nbsp;sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n
nbsp;nbsp;sieve_extensions = comparator-i;ascii-numeric copy envelope
fileinto imapflags include notify regex reject relational subaddress
vacation
nbsp;nbsp;sieve_max_script_size = 512KB
nbsp;nbsp;sieve_quota_max_scripts = 2
}
protocols = imap pop3 lmtp sieve
service auth-worker {
nbsp;nbsp;user = $default_internal_user
}
service auth {
nbsp;nbsp;process_limit = 1
nbsp;nbsp;process_min_avail = 1
}
service imap-login {
nbsp;nbsp;inet_listener imap {
nbsp;nbsp; nbsp;address = lmtp1.f1.k8.com.br, box5.f1.k8.com.br
nbsp;nbsp; nbsp;port = 143
nbsp;nbsp;}
}
service imap {
nbsp;nbsp;process_limit = 1024
nbsp;nbsp;process_min_avail = 10
}
service lmtp {
nbsp;nbsp;inet_listener {
nbsp;nbsp; nbsp;address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
nbsp;nbsp; nbsp;port = 2003
nbsp;nbsp;}
nbsp;nbsp;process_limit = 256
nbsp;nbsp;process_min_avail = 10
}
service managesieve-login {
nbsp;nbsp;inet_listener sieve {
nbsp;nbsp; nbsp;address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
nbsp;nbsp; nbsp;port = 4190
nbsp;nbsp;}
nbsp;nbsp;inet_listener sieve_deprecated {
nbsp;nbsp; nbsp;address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
nbsp;nbsp; nbsp;port = 2000
nbsp;nbsp;}
}
service managesieve {
nbsp;nbsp;process_limit = 20
nbsp;nbsp;process_min_avail = 10
}
service pop3-login {
nbsp;nbsp;inet_listener pop3 {
nbsp;nbsp; nbsp;address = lmtp1.f1.k8.com.br, box5.f1.k8.com.br
nbsp;nbsp; nbsp;port = 110
nbsp;nbsp;}
}
service pop3 {
nbsp;nbsp;process_limit = 256
nbsp;nbsp;process_min_avail = 10
}
ssl = no
userdb {
nbsp;nbsp;driver = prefetch
}
userdb {
nbsp;nbsp;args = /etc/dovecot/dovecot-sql.conf.ext
nbsp;nbsp;driver = sql
}
verbose_proctitle = yes
protocol imap {
nbsp;nbsp;imap_idle_notify_interval = 120 s
nbsp;nbsp;imap_max_line_length = 65536
nbsp;nbsp;mail_max_userip_connections = 50
nbsp;nbsp;mail_plugins = $mail_plugins quota imap_quota autocreate
}
protocol lmtp {
nbsp;nbsp;mail_plugins = $mail_plugins sieve quota autocreate
}
protocol sieve {
nbsp;nbsp;mail_plugins = $mail_plugins sieve
nbsp;nbsp;managesieve_implementation_string = K8 ManageSieve
nbsp;nbsp;managesieve_logout_format = bytes=%i/%o
nbsp;nbsp;managesieve_max_line_length = 65536
nbsp;nbsp;managesieve_sieve_capability = comparator-i;ascii-numeric
copy envelope fileinto imapflags include notify regex reject relational
subaddress vacation
}
protocol pop3 {
nbsp;nbsp;mail_plugins = $mail_plugins quota autocreate
}
gt; nbsp; What version/revision of Pigeonhole you installed.
I'm using recompiled debian packages from http://xi.rename-it.nl/debian/
which already come with pigeonhole. The last changelog entry is
fromnbsp;2010-08-14.
gt; 2) Gdb backtrace:
gt;nbsp;
gt; http://www.dovecot.org/bugreport.html
gt;nbsp;
gt; Try to obtain core dumps when it is hard to reproduce.
gt;nbsp;
gt; 3) Examples of scripts and messages that cause the problem
(assuming itnbsp;
gt; is reproducible).
I'll work on these. The server is hosting a few thousand accounts, so
it's hard to identify specific scripts.
Thanks,Andre
try to correct dovecot -n try to remove nbsp;
- --
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x092164A7
gpg --keyserver pgp.mit.edu --recv-key 092164A7
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iD8DBQFMwF84tXI/OwkhZKcRAvUvAJ4112rhEvFGS5oD0R1Kl/Ao2IzhmACfcqjO
D5T49LzAlp63IF4mJpPRvio=
=Ntb+
-END PGP SIGNATURE-
Re: [Dovecot] 2.0.5 Error: Timeout waiting for handshake from auth server.
On Thu, 2010-10-21 at 10:57 +0300, Veiko Kukk wrote: Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13338, input bytes=0 auth process is hanging or imap-login is connecting to wrong server. First try deleting everything from Dovecot's base_dir (/var/run/dovecot/ or something). If that doesn't help, show your doveconf -n output. Also once started, show ps aux|grep dovecot output and strace -tt -p `pidof auth` output for a few seconds.
Re: [Dovecot] Question about Client Certificates
On Mon, 2010-10-18 at 23:17 +0100, William Gallafent wrote: In other words, I want ssl_require_client_cert = yes for remote connections (on port 993), but ssl_require_client_cert = no for local connections using non-tls imap on port 143. Is this possible? With v2.0, yes. With v1.2 .. I guess not unless you run two Dovecot instances with two different config files.
Re: [Dovecot] delivering mail to public mbox with permission 660?
On Tue, 2010-10-19 at 14:30 -0700, RParr wrote: I am running Ubuntu 10.04 packages postfix 2.7.0-1, dovecot-common, dovecot-imapd, dovecot-pop3d, and dovecot-postfix (all version 1.2.9-1ubuntu6.1). .. My understanding, from the Dovecot wiki and other docs/postings is that the folders should be 660 given the /var/mail permssions of rwxrwsrwt and ~/mail permssions of rwxrws--- Yep. Looks like it's broken in v1.2 for mbox. It works in v2.0 though. I could maybe write a patch for v1.2, but you'd need to compile Dovecot anyway.
Re: [Dovecot] Correct permissions for base_dir??
On Thu, 2010-10-21 at 19:42 +0300, Odhiambo Washington wrote:
Oct 21 16:33:18 lda: Error: userdb lookup:
connect(/opt/dovecot2/var/run/auth-userdb) failed: Permission denied
(euid=26(mailnull) egid=26(mailnull) missing +r perm:
/opt/dovecot2/var/run/auth-userdb, euid is not dir owner)
It's not complaining about base_dir's permissions, but auth-userdb
socket's permissions. See:
service auth {
# auth_socket_path points to this userdb socket by default. It's typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Its default
# permissions make it readable only by root, but you may need to relax these
# permissions. Users that have access to this socket are able to get a list
# of all usernames and get results of everyone's userdb lookups.
unix_listener auth-userdb {
#mode = 0600
#user =
#group =
}
Maybe you want to set user = vmail or something.
Re: [Dovecot] Segfault in libdovecot-sieve
On Thu, 21 Oct 2010 18:20:51 +0200 fake...@fakessh.eu articulated: it is the webmail problem or postfix problem Or something else; or not! -- Jerry ✌ dovecot.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? TOPIC: Posting Etiquette
Re: [Dovecot] Correct permissions for base_dir??
On Thu, Oct 21, 2010 at 7:48 PM, Timo Sirainen t...@iki.fi wrote:
On Thu, 2010-10-21 at 19:42 +0300, Odhiambo Washington wrote:
Oct 21 16:33:18 lda: Error: userdb lookup:
connect(/opt/dovecot2/var/run/auth-userdb) failed: Permission denied
(euid=26(mailnull) egid=26(mailnull) missing +r perm:
/opt/dovecot2/var/run/auth-userdb, euid is not dir owner)
It's not complaining about base_dir's permissions, but auth-userdb
socket's permissions. See:
service auth {
# auth_socket_path points to this userdb socket by default. It's typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Its default
# permissions make it readable only by root, but you may need to relax
these
# permissions. Users that have access to this socket are able to get a
list
# of all usernames and get results of everyone's userdb lookups.
unix_listener auth-userdb {
#mode = 0600
#user =
#group =
}
Maybe you want to set user = vmail or something.
Thanks Timo!
Problem solved.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Damn!!
Re: [Dovecot] anti-spam+anti-malware suggestions
On 10/21/2010 07:37 AM, Fabricio Archanjo wrote: Does someone run dspam or just me?? I like very much this antispam solution. I use it with Eugene's port/fork of dovecot-antispam to dovecot 2.0. I use it with amavisd. I use postfix in the mix. On machines where people don't care about dangerous file extensions and rewrapping virus containing emails instead of just erasing them, I will use clamav-milter. I find it works VERY well. Trever -- Yesterday is gone. Tomorrow is too far for me. Today is what I have, and what I fight for. -- Unknown signature.asc Description: OpenPGP digital signature
[Dovecot] v2.0.6 released
http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0. + dbox: Added support for saving mail attachments to external files, with also support for single instance storage. This feature hasn't had much testing yet, so be careful with it. + doveadm: Added import command for importing mails from other storages. + Reduced NFS I/O operations for index file accesses + dbox, Maildir: When copying messages, copy also already cached fields from dovecot.index.cache + mdbox: Added mdbox_preallocate_space setting (Linux+ext3/XFS only) - Maildir: LDA/LMTP assert-crashed sometimes when saving a mail. - Fixed leaking fds when writing to dovecot.mailbox.log. - Fixed rare dovecot.index.cache corruption - IMAP: SEARCH YOUNGER/OLDER wasn't working correctly
Re: [Dovecot] minimize mbox mdbox fragmentation
Timo Sirainen put forth on 10/21/2010 9:52 AM: On Wed, 2010-10-20 at 23:50 -0500, Stan Hoeppner wrote: Oh, interesting. I didn't know that was possible. And even better: Linux has fallocate() that can do it for other filesystems than just XFS. Or looks like it's only XFS and ext4 (ext3 doesn't support it). I don't know if other OSes support this. There exists posix_fallocate() which would widen the platforms that would support this Timo. I know about posix_fallocate(), but that does a different thing. It would work only when this works: Ahh, ok, didn't realize that it was different than the Linux specific call. Maybe in future I could make mdbox support writing to files whose size has been preallocated by actually writing NUL bytes, but that requires some extra code. You may also want to look at posix_fadvise() as well (if you're not using it already) which might increase Dovecot's overall disk performance a bit. I once wrote a patch for that and asked if anyone could confirm if it made things worse or better, but no one ever did. http://dovecot.org/list/dovecot/2007-November/026819.html I wasn't aware of this. I don't really have the resources, skill set, or time to test patches, or I'd do so. :( NOTE: I don't believe fallocate() in either posix or linux only form will actually accomplish decreased m[d]box file fragmentation. I don't believe it actually increases the file size on disk, i.e. physically allocating additional free extents tailing the end of the file. fallocate() is _speculative_ preallocation, which isn't what you want. Why do you believe that? The man pages and everything tell me that it's about physical preallocation: fallocate is used to preallocate blocks to a file. For filesystems which support the fallocate system call, this is done quickly by allo‐ cating blocks and marking them as uninitialized, requiring no IO to the data blocks. This is much faster than creating a file by filling it with zeros. Also du shows that the file's size is actually the preallocated size. That's how I checked which filesystems supported it. And I think Linux fallocate() with XFS internally does exactly what XFS_IOC_RESVSP does, which your quoted mail mentioned being about physical preallocation. Well that's cool then. I don't know if it changes anything in the sequence above, but Dovecot uses mmap i/o. mmap is used only for index files, not for mdbox files. Ahh, that's really good to know. IIRC the comments for enabling mmap in dovecot.conf don't state this. I thus assumed enabling mmap was for all files. It would be beneficial I think if you'd sub to the xfs list Timo and pick some brains. Maybe, but there is still so much other stuff to do, like bug fixing. :) Looks like you've got a handle on it. Like I said, I know just enough about this stuff to make me dangerous. ;) -- Stan
Re: [Dovecot] anti-spam+anti-malware suggestions
Stan Hoeppner s...@hardwarefreak.com wrote on 21.10.2010 10:29:50: This will kill a huge amount of bot spam without dnsbl queries or greylisting, both of which can be resource hogs and add serious latency: http://www.hardwarefreak.com/fqrdns.pcre Stan, nice one. I'm wondering from where did you compile this one? Regards, Miha -- It's time to get rid of your current e-mail client ... ... and start using si.Mail. It's small free. ( http://www.simail.si/ )
Re: [Dovecot] Segfault in libdovecot-sieve
This shows up in the mail error when the sieve error happens. It seems
the sieve error is a side-effect of something else:
Oct 21 17:58:11 box6 dovecot: lmtp(10424,
catia.comercial=industriacarvalho.com...@lmtp1.prv.f1.k8.com.br): Error:
lstat((null)) failed: Bad address
Oct 21 17:58:11 box6 dovecot: lmtp(10424,
catia.comercial=industriacarvalho.com...@lmtp1.prv.f1.k8.com.br): Error:
file_dotlock_create((null)) failed: Bad address
Oct 21 17:58:11 box6 dovecot: lmtp(10424,
catia.comercial=industriacarvalho.com...@lmtp1.prv.f1.k8.com.br): Error:
open((null)) failed: Bad address
Oct 21 18:05:25 box6 dovecot: master: Error: service(lmtp): child 10424
killed with signal 11 (core dumps disabled)
Best regards,
Andre
On Thu, 2010-10-21 at 14:13 -0400, Andre wrote:
Sigh. The webmail broke the configuration output. Here's it again.
# 2.0.3 (02a9cf90ad02): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-25-server x86_64 Ubuntu 10.04.1 LTS
auth_master_user_separator = *
auth_mechanisms = plain login
auth_username_chars =
abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz01234567890...@=
auth_worker_max_count = 10
disable_plaintext_auth = no
listen = lmtp1.f1.k8.com.br, lmtp1.prv.f1.k8.com.br
login_greeting = K8 IMAP/POP3 server
mail_debug = yes
mail_gid = dovemail
mail_plugins = $mail_plugins quota
mail_uid = dovemail
managesieve_sieve_capability = fileinto reject envelope vacation
subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include imapflags notify
mmap_disable = yes
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
passdb {
args = /etc/dovecot/dovecot-sql-master.conf.ext
driver = sql
master = yes
pass = yes
}
plugin {
autocreate = SPAM
autosubscribe = SPAM
quota = dict:User quota::file:/var/lib/imap/user/%2.256RHn/%
n/dovecot-quota
quota_rule = *:storage=1GB
sieve = /var/lib/imap/sieve/%2.256RHn/%n/phpscript.script
sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n
sieve_extensions = comparator-i;ascii-numeric copy envelope fileinto
imapflags include notify regex reject relational subaddress vacation
sieve_max_script_size = 512KB
sieve_quota_max_scripts = 2
}
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
process_limit = 1
process_min_avail = 1
}
service imap-login {
inet_listener imap {
address = lmtp1.f1.k8.com.br, box5.f1.k8.com.br
port = 143
}
}
service imap {
process_limit = 1024
process_min_avail = 10
}
service lmtp {
inet_listener {
address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
port = 2003
}
process_limit = 256
process_min_avail = 10
}
service managesieve-login {
inet_listener sieve {
address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
port = 4190
}
inet_listener sieve_deprecated {
address = lmtp1.prv.f1.k8.com.br, box5.prv.f1.k8.com.br
port = 2000
}
}
service managesieve {
process_limit = 20
process_min_avail = 10
}
service pop3-login {
inet_listener pop3 {
address = lmtp1.f1.k8.com.br, box5.f1.k8.com.br
port = 110
}
}
service pop3 {
process_limit = 256
process_min_avail = 10
}
ssl = no
userdb {
driver = prefetch
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
verbose_proctitle = yes
protocol imap {
imap_idle_notify_interval = 120 s
imap_max_line_length = 65536
mail_max_userip_connections = 50
mail_plugins = $mail_plugins quota imap_quota autocreate
}
protocol lmtp {
mail_plugins = $mail_plugins sieve quota autocreate
}
protocol sieve {
mail_plugins = $mail_plugins sieve
managesieve_implementation_string = K8 ManageSieve
managesieve_logout_format = bytes=%i/%o
managesieve_max_line_length = 65536
managesieve_sieve_capability = comparator-i;ascii-numeric copy
envelope fileinto imapflags include notify regex reject relational
subaddress vacation
}
protocol pop3 {
mail_plugins = $mail_plugins quota autocreate
}
Re: [Dovecot] v2.0.6 released
On Thu, Oct 21, 2010 at 9:14 PM, Timo Sirainen t...@iki.fi wrote: http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0. + dbox: Added support for saving mail attachments to external files, with also support for single instance storage. This feature hasn't had much testing yet, so be careful with it. + doveadm: Added import command for importing mails from other storages. + Reduced NFS I/O operations for index file accesses + dbox, Maildir: When copying messages, copy also already cached fields from dovecot.index.cache + mdbox: Added mdbox_preallocate_space setting (Linux+ext3/XFS only) - Maildir: LDA/LMTP assert-crashed sometimes when saving a mail. - Fixed leaking fds when writing to dovecot.mailbox.log. - Fixed rare dovecot.index.cache corruption - IMAP: SEARCH YOUNGER/OLDER wasn't working correctly And I am the 2nd person ever to run dovecot-2.0.6 after Timo!! Running on my brand new PC-BSD-8.1 amd64 server after a successful compile with mbdox. PS: Timo, in the options shown when one runs the configure script, should the dbox option be removed? [r...@gw] ~wash/Tools/Dovecot/dovecot-2.0/dovecot-2.0.6# ./configure --help | grep dbox (maildir mbox dbox mdbox cydir) For the fun of it, i used --with-storages=maildir mbox dbox mdbox cydir (not intending to use all, but just to see) and this led `make` to fail with something about dbox, so I simply removed it and got a successful compile. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!!
Re: [Dovecot] v2.0.6 released
On 2010-10-21 4:52 PM, Odhiambo Washington wrote: For the fun of it, i used --with-storages=maildir mbox dbox mdbox cydir (not intending to use all, but just to see) and this led `make` to fail with something about dbox, so I simply removed it and got a successful compile. Its not dbox any more, its sdbox (for single dbox) and mdbox (for multi-dbox)... So if you wanted to compile with support for all, try adding sdbox to the rest and you should be good to go... -- Best regards, Charles
Re: [Dovecot] v2.0.6 released
On 21.10.2010, at 21.52, Odhiambo Washington wrote: PS: Timo, in the options shown when one runs the configure script, should the dbox option be removed? [r...@gw] ~wash/Tools/Dovecot/dovecot-2.0/dovecot-2.0.6# ./configure --help | grep dbox (maildir mbox dbox mdbox cydir) Yeah, it should have been sdbox. Fixed now in hg. For the fun of it, i used --with-storages=maildir mbox dbox mdbox cydir (not intending to use all, but just to see) and this led `make` to fail with something about dbox, so I simply removed it and got a successful compile. Hmm. I think it still should have worked.. Well, not sure.
Re: [Dovecot] Segfault in libdovecot-sieve
On 21.10.2010, at 23.14, Andre wrote: This shows up in the mail error when the sieve error happens. It seems the sieve error is a side-effect of something else: Oct 21 17:58:11 box6 dovecot: lmtp(10424, catia.comercial=industriacarvalho.com...@lmtp1.prv.f1.k8.com.br): Error: lstat((null)) failed: Bad address This reminds me of a problem with missing home directory. That crash is fixed in v2.0.6, but you should have a home directory set so that reject/vacation messages won't be duplicated. http://wiki2.dovecot.org/VirtualUsers/Home
Re: [Dovecot] Segfault in libdovecot-sieve
On Thu, 2010-10-21 at 22:13 +0100, Timo Sirainen wrote: This reminds me of a problem with missing home directory. That crash is fixed in v2.0.6, but you should have a home directory set so that reject/vacation messages won't be duplicated. http://wiki2.dovecot.org/VirtualUsers/Home Given my mail directory is in the format mdbox:/var/spool/imap/$hash/$username is it safe to set the home directory to, say, /var/spool/imap/$hash/$username/home ? I assume it is, since the mailboxes are in the 'mailboxes' directory and thus the conflicts mentioned in the wiki can't happen, right? Best, Andre
Re: [Dovecot] minimize mbox mdbox fragmentation
On 20.10.2010, at 17.53, Timo Sirainen wrote: What you want is _physical_ preallocation, not speculative preallocation. i.e. look up XFS_IOC_RESVSP or FIEMAP so your application does _permanent_ preallocate past EOF. Oh, interesting. I didn't know that was possible. And even better: Linux has fallocate() that can do it for other filesystems than just XFS. Or looks like it's only XFS and ext4 (ext3 doesn't support it). I don't know if other OSes support this. Maybe in future I could make mdbox support writing to files whose size has been preallocated by actually writing NUL bytes, but that requires some extra code. Looks like OS X has fcntl(F_PREALLOCATE), although it doesn't seem to produce any visible results, other than giving ENOSPC error if I give too large of a size (100 MB or so). Disk usage doesn't shrink though, so maybe it's more of a hint?.. Mike, do you think this code is actually working/useful with OSX? :)
Re: [Dovecot] minimize mbox mdbox fragmentation
On 21.10.2010, at 22.58, Timo Sirainen wrote: Looks like OS X has fcntl(F_PREALLOCATE), although it doesn't seem to produce any visible results, other than giving ENOSPC error if I give too large of a size (100 MB or so). Disk usage doesn't shrink though, so maybe it's more of a hint?.. Mike, do you think this code is actually working/useful with OSX? :) Oh, forgot to give the link: http://hg.dovecot.org/dovecot-2.0/rev/f6e45e83796b (plus http://hg.dovecot.org/dovecot-2.0/rev/aaca506ea33b)
Re: [Dovecot] Segfault in libdovecot-sieve
On 22.10.2010, at 0.53, Andre wrote: is it safe to set the home directory to, say, /var/spool/imap/$hash/$username/home ? I assume it is, since the mailboxes are in the 'mailboxes' directory and thus the conflicts mentioned in the wiki can't happen, right? So you're using dbox? Yeah, you can set home like that then. Although with dbox because of the mailboxes/ directory it's actually not bad to set home = mail dir.
Re: [Dovecot] 2.0.5 Error: Timeout waiting for handshake from auth server.
check your mail log, if you get this: Authentication service cannot retrieve authentication info then it could be related to this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566844 if you do have that issue let me know, and I'll look up our notes to post a work around. On Thu, Oct 21, 2010 at 3:57 AM, Veiko Kukk veiko.k...@ekp.ee wrote: Hello, Upgraded from 1.2.x to 2.0.5, converted configuration as described in http://wiki2.dovecot.org/Upgrading/2.0 and now I'm unable to log in to imap server. Dovecot error.log shows: Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13338, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13364, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13337, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13350, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13335, input bytes=0 Oct 21 09:52:48 imap-login: Error: Timeout waiting for handshake from auth server. my pid=13360, input bytes=0 I'm using pam with winbind for authentication. /etc/pam.d/dovecot contains: auth required pam_winbind.so account sufficient pam_winbind.so And it used to work perfectly with 1.1 and 1.2 series of dovecot. What could be the problem with 2.0.5? -- Veiko
Re: [Dovecot] Segfault in libdovecot-sieve
On Thu, 2010-10-21 at 23:01 +0100, Timo Sirainen wrote: So you're using dbox? Yeah, you can set home like that then. Although with dbox because of the mailboxes/ directory it's actually not bad to set home = mail dir. Yeah, I'm using mdbox. I'll set home = mail dir then and upgrade to 2.0.6 to see if the problem goes away. Thanks Andre
Re: [Dovecot] maildir-dbox hybrid
Timo Sirainen wrote: Yeah. Not very nice either. Here's a 3rd option: Apply the attached patch to v1.2 and then open all users' all mailboxes (write a script or something). It should convert all maildir files to dbox files. Try with one account first to make sure it works. :) Hi Timo, list, your 3rd option sounded best, but I got some problems and had to revert to my backup: I patched Dovecot 1.2.15 with your diff (and with debian patches). I then accessed all mailboxes. For some it went OK, but for some I now only see old mail and am missing the newest ones starting from some time in February (I probably did a dovecot upgrade then). What I got is thousands of these: Oct 21 21:29:30 atrus dovecot: IMAP(roland): /var/spool/dovecot/mail/roland/dbox/mailboxes/INBOX/dbox-Mails/u.8922 corrupted: Invalid dbox version ...and some occasional these: Oct 21 21:32:59 atrus dovecot: IMAP(roland): Panic: file mail-index-transaction.c: line 1273 (mail_index_update_ext): assertion failed: (seq 0 (seq = mail_index_view_get_messages_count(t-view) || seq = t-last_new_seq)) Oct 21 21:32:59 atrus dovecot: IMAP(roland): Raw backtrace: imap [0x4a6e32] - imap [0x4a6eb3] - imap [0x4a6596] - imap(mail_index_update_ext+0x15d) [0x47d7bd] - imap(dbox_sync_index_rebuild+0x1da) [0x43c87a] - imap(dbox_sync_begin+0x481) [0x43ae01] - imap(dbox_sync+0x18) [0x43b198] - imap(dbox_storage_sync_init+0x36) [0x43b206] - imap(mailbox_sync+0x30) [0x46d380] - imap(cmd_select_full+0x37c) [0x42129c] - imap [0x423adc] - imap [0x423b8d] - imap(client_handle_input+0x45) [0x423d05] - imap(client_input+0x5f) [0x42469f] - imap(io_loop_handler_run+0xcb) [0x4aefeb] - imap(io_loop_run+0x18) [0x4ae468] - imap(main+0x537) [0x42c727] - /lib/libc.so.6(__libc_start_main+0xe6) [0x7fe1edc081a6] - imap [0x41c689] Oct 21 21:32:59 atrus dovecot: dovecot: child 2920 (imap) killed with signal 6 (core dumps disabled) ...where the last one is not always there. Was there a dbox format change? Best regards, Roland.
[Dovecot] Problems converting to maildir with dsync in 2.0.6
I'm trying to convert from an old Dovecot (1.0.15) and mbox to a new
Dovecot and maildir. I'm running into several problems with dsync which
are causing my mboxes not to convert.
If I use LAYOUT=fs (as I'd prefer) I get an error because I have a
mailbox called subscriptions, and none of my messages convert. Is
there a way to get dovecot to put its own metadata in dotfiles instead?
(I guess I can rename my mailbox too :-)
% dsync mirror mbox:~/Mail
dsync(nriley): Error: read() failed with subscription file
/home/nriley/Maildir/subscriptions: Is a directory
dsync(nriley): Error: Can't update subscription +/INBOX: Internal error
occurred. Refer to server log for more information. [2010-10-21 20:17:55]
[...]
Also, what server log is it referring to above?
So I tried without LAYOUT=fs, and dsync successfully converts some
mailboxes, then crashes:
% dsync mirror mbox:~/Mail
dsync(nriley): Error: Maildir: 6ef533cd4cdb1fd454b0226bfc851bb3:2,
changed UID 1846529 - 1846531
dsync(nriley): Panic: file maildir-save.c: line 892
(maildir_save_sync_uidlist): assertion failed: (ret 0)
dsync(nriley): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0
[0xb7ea21f1] -
/usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x47)
[0xb7ea2317] - /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0xb7ea2544]
-
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_transaction_save_commit_
pre+0x858) [0xb7f2ab58] - /usr/lib/dovecot/libdovecot-storage.so.0
[0xb7f2501f] -
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_fu
ll+0x85) [0xb7f67eb5] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_transaction_commit+0x94)
[0xb7f24c14] -
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_c
hanges+0x42) [0xb7efeaa2] - /usr/bin/dsync [0x8056ed2] -
/usr/bin/dsync [0x80570f0] -
/usr/bin/dsync(dsync_worker_select_mailbox+0x2e) [0x8055b2e] -
/usr/bin/dsync [0x80507e6] - /usr/bin/dsync [0x8050a3b] -
/usr/bin/dsync(dsync_brain_msg_sync_new_msgs+0x12) [0x8050c12] -
/usr/bin/dsync(dsync_brain_msg_sync_more+0x2e1) [0x8050261] -
/usr/bin/dsync(dsync_brain_sync+0x309) [0x804e949] - /usr/bin/dsync
[0x804f953] - /usr/bin/dsync(dsync_brain_sync+0x72e) [0x804ed6e] -
/usr/bin/dsync [0x804f7d0] - /usr/bin/dsync(dsync_brain_sync+0x55d)
[0x804eb9d] - /usr/bin/dsync(dsync_brain_sync_all+0x18) [0x804f668] -
/usr/bin/dsync(main+0x5a1) [0x804da51] -
/lib/libc.so.6(__libc_start_main+0xe5) [0xb7d29455] - /usr/bin/dsync
[0x804d2e1]
[1]30528 abort dsync mirror mbox:~/Mail
I tried running it in GDB but that crashed GDB, so hopefully the above
info is OK...
% gdb --args dsync mirror mbox:~/Mail
(gdb) run
Starting program: /usr/bin/dsync mirror mbox:\~/Mail
[Thread debugging using libthread_db enabled]
[New process 30652]
Executing new program: /usr/bin/doveconf
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
[New process 30652]
[Thread debugging using libthread_db enabled]
[1]30651 segmentation fault gdb -q --args dsync mirror mbox:~/Mail
I'm using the Debian packages from rename-it.nl. Here is doveconf -n
output:
# 2.0.6 (aaca506ea33b): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18.8-linode22 i686 Debian 5.0.6
mail_location = maildir:~/Maildir:INBOX=~/Maildir/INBOX
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date
namespace {
inbox = yes
location =
prefix =
separator = /
}
passdb {
driver = pam
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap
ssl = required
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
driver = passwd
}
--
Nicholas Riley njri...@illinois.edu
Re: [Dovecot] Problems converting to maildir with dsync in 2.0.6
In article njriley-5cb377.20303521102...@news.gmane.org, Nicholas Riley njri...@illinois.edu wrote: I'm trying to convert from an old Dovecot (1.0.15) and mbox to a new Dovecot and maildir. I'm running into several problems with dsync which are causing my mboxes not to convert. If I use LAYOUT=fs (as I'd prefer) I get an error because I have a mailbox called subscriptions, and none of my messages convert. Is there a way to get dovecot to put its own metadata in dotfiles instead? (I guess I can rename my mailbox too :-) OK, I found in the source code that I can use SUBSCRIPTIONS=... to fix this, although oddly enough I don't see a file being created now. (This might be documented in http://wiki2.dovecot.org/MailLocation or http://wiki2.dovecot.org/MailLocation/Maildir...) So now I get the same crash as before with LAYOUT=fs, and my mail_location: mail_location = maildir:~/Maildir:INBOX=~/Maildir/INBOX:LAYOUT=fs:CONTROL=~/Maildir/.dove cot:SUBSCRIPTIONS=~/Maildir/.subscriptions -- Nicholas Riley njri...@illinois.edu
