Re: [Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
hi, Am Mittwoch, den 29.09.2010, 12:25 -0400 schrieb Charles Marcus: > On 2010-09-29 10:26 AM, Denny Schierz wrote: > > # grep conn=1103 local4.log > > > > http://pastebin.com/a1h1YE8P > > Same for this... Sorry, I do this for longer output because 79 chars are to short do display it in a readable way. but, thanks for reading :-) cu denny signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
hi, Am Mittwoch, den 29.09.2010, 18:45 +0100 schrieb Timo Sirainen: > > You've configured LDAP server to have a really small connection idle > timeout? maybe, i found the solution, by my self. I had the same idea, that the timeout from slapd was to short (30 seconds) and I configured slapd now up to 60 seconds. No messages any more :-) Thanks for your help :-) cu denny signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [Dovecot] Fwd: NFS question
On Wed, 29 Sep 2010, Charles Marcus wrote: On 2010-09-29 1:27 AM, Nick Edwards wrote: I do not wish responses from those who are not developers of dovecot, Silly... Then you should have spent the few seconds required to browse the PUBLIC list archives for Timo's current email address - then I wouldn't have even seen this message and you wouldn't be getting this response. Additionally, I don't think this is something the developer needs to address privately. There's also a whole thread about this, and this reply totally cleared up the issue for me: http://www.mail-archive.com/dovecot@dovecot.org/msg31713.html Charles many I have since had discussions with on another list and spam binned (abusive souls like charlie marcus) If you consider simply correcting your misunderstanding of how dovecot works as 'abusive', then, yeah, I guess I'm guilty as charged. but I likely was mailing a old address he doesn't read Like I said - took me all of 10 seconds to determine his current email address from his most recent posting to this list (he posts daily). -- Best regards, Charles
Re: [Dovecot] Possible bug with proxy in 2.0.4
On 29.9.2010, at 23.03, Ed W wrote: > Specifically I cloned my 1.2 virtual machine, upgraded the clone to 2.0.4 and > tested it by trying to login using CRAM-MD5. I get the errors: > > Sep 29 22:50:30 mail_test dovecot: imap-login: Error: proxy: password not > given: user=, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, > mpid=0, TLS CRAM-MD5 doesn't work directly with proxying. It can't work, by CRAM-MD5 design. The only way to make it work is if your passdb lookup returns a password, either the user's actual password in plaintext or some master password, that the backends accepts with plaintext authentication. > I then change the configuration so that the 2.0.4 machine proxies the > connection back to the 1.2 machine (again) and try to login to the 2.0.4 > machine and get the same errors as above. Seems like the error is only when > proxying (needless to say, the old 1.2 machine works fine with CRAM and > that's how it's normally accessed, so also does the 2.0.4 machine, it's only > proxying one to the other which isn't apparently working?) If it worked with v1.2, it either wasn't proxying or it was doing something like I mentioned above.
[Dovecot] Possible bug with proxy in 2.0.4
Hi, I *think* there might be an auth/proxy bug in 2.0.4 Specifically I cloned my 1.2 virtual machine, upgraded the clone to 2.0.4 and tested it by trying to login using CRAM-MD5. I get the errors: Sep 29 22:50:23 mail_test dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, mpid=0, TLS Sep 29 22:50:30 mail_test dovecot: auth: mysql: Connected to mysql-local (postfix) Sep 29 22:50:30 mail_test dovecot: imap-login: Error: proxy: password not given: user=, method=CRAM-MD5, rip=x.x.x.x, lip=x.x.x.x, mpid=0, TLS Interestingly the config here (accidently as it happens) causes the connection to use the dovecot "proxy" feature back to the original 1.2 machine. I updated my config so that everything stays on the 2.0.4 machine and authentication proceeds normally, messages about generating MD5 hash from the DB, etc, logged in ok. I then change the configuration so that the 2.0.4 machine proxies the connection back to the 1.2 machine (again) and try to login to the 2.0.4 machine and get the same errors as above. Seems like the error is only when proxying (needless to say, the old 1.2 machine works fine with CRAM and that's how it's normally accessed, so also does the 2.0.4 machine, it's only proxying one to the other which isn't apparently working?) It's late and so I haven't managed to probe the 1.2 machine too much, but initially looking at the log files I don't see any evidence of the 2.0.4 machine actually contacting it? Does this make sense? Thanks Ed W
Re: [Dovecot] Fwd: NFS question
On Wed, 2010-09-29 at 15:27 +1000, Nick Edwards wrote: > To: t...@iki.fi This has never been my email address. I don't know who it goes to. > After reading the archives recently on a few threads about NFS I have > concerns You've read http://dovecot.org/list/dovecot/2010-August/052188.html thread? > over our plans to move from cyrus to dovecot, we initially discounted > dovecot as > a choice over it, but since dovecot and sieve go well together, I am just > re-capping > everything before we approve move to courier or back to dovecot, having re > read > those threads over a couple of times, am I right in assuming that this > caching > problem, is really only a problem if using imap and the chances of it being > an > issue with pop3 is very rare? With POP3-only users it should be rare. But if they're using webmail also that adds IMAP there which makes it less safe. Also with POP3 you might want to disable indexes anyway and use filename as POP3 UIDL and then corruption wouldn't matter at all (dovecot-uidlist file updates are actually pretty pointless then). > Also, will this be more of a problem if we use dovecot v1.2 or v2.0 ? They work identically. Although today I made performance improvements to POP3, and I'll probably still make some more. Anyway, I can't give you any guarantees. I only know that it's not 100% safe, but some people with POP3-only/mostly setups have been happy enough anyway.
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
Timo, > -Original Message- > From: Timo Sirainen [mailto:t...@iki.fi] > > The whole userdb. Director doesn't do userdb lookups at all. (Also if > there is no userdb defined, Dovecot actually creates a default static > userdb with empty args.) Awesome, good to know. -Brad
Re: [Dovecot] Doveadm expunge purge optimize
On Wed, 2010-09-29 at 12:51 -0300, Thiago Henrique wrote: > 01 22 * * * root nice -n 19 /usr/bin/doveadm expunge -A mailbox SPAM > BEFORE 60d > 01 00 * * * root nice -n 19 /usr/bin/doveadm purge -A > > Each doveadm command walks through the whole file system. Is there a way > to run the two operations into a single walk? Does anyone have a > suggestion that helps optimize this? Currently there's no way to run multiple commands in one run. I was thinking about that though.. Maybe it could be something like: doveadm -A <
Re: [Dovecot] Problem with dovecot/deliver and SSL in 2.0.4
On Wed, 2010-09-29 at 21:39 +0200, Rainer Ophoven wrote: > c/dovecot/deliver". Command output: doveconf: Fatal: Error in > configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_key > not set ) This happens somewhat randomly depending on what order "find" command finds some files when running configure. http://hg.dovecot.org/dovecot-2.0/rev/65855df71cf4 fixes this.
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
On Wed, 2010-09-29 at 14:11 -0700, Brad Davidson wrote:
> > -Original Message-
> > From: Timo Sirainen [mailto:t...@iki.fi]
> >
> > On Wed, 2010-09-29 at 11:46 -0700, Brad Davidson wrote:
> >
> > > userdb {
> > > driver = static
> > > args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty
> > > }
> >
> > This shouldn't be necessary.
> >
>
> Which bit? The args, or the whole userdb? What happens if I don't have a
> userdb at all? The mailservers use PAM, but I wasn't sure what to use on the
> Director proxies.
The whole userdb. Director doesn't do userdb lookups at all. (Also if
there is no userdb defined, Dovecot actually creates a default static
userdb with empty args.)
Re: [Dovecot] Problem with dovecot-acl
On Wed, 2010-09-29 at 23:26 +0400, dss wrote: > I have a problem with dovecot-acl. Some of our users need to use the > same Mailbox with all folders: Inbox (with subfolders), Outbox, Send > and Deleted, (some users need in full righs, some - readonly) so I > choosed Symlinking mailboxes and tried to use dovecot-acl file. This is only a problem with symlinked mailboxes, because Dovecot thinks you own the mailbox and uses "allow everything" as the default ACL. > cat dovecot-acl: > user=t1 lrwsti > user=operolegs lrwsti > user=operantona lrwsti > user=operdss lr > > User operdss have lrwsti rights in this shared mailbox unstead of lr! But if > I comment out other users in the dovecot-acl: > > #user=t1 lrwsti > #user=operolegs lrwsti > #user=operantona lrwsti > user=operdss lr I'll try to get this fixed properly tomorrow, but for now you can work around it by first removing all rights from owner: owner user=t1 ... user=...
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
> -Original Message-
> From: Timo Sirainen [mailto:t...@iki.fi]
>
> On Wed, 2010-09-29 at 11:46 -0700, Brad Davidson wrote:
>
> > userdb {
> > driver = static
> > args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty
> > }
>
> This shouldn't be necessary.
>
Which bit? The args, or the whole userdb? What happens if I don't have a userdb
at all? The mailservers use PAM, but I wasn't sure what to use on the Director
proxies.
-Brad
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
Thanks again! Everything working properly with proxy and director now once I moved passdb out of 10-director.conf and into auth-static.conf.ext (and switched to it in 10-auth.conf) Timo was correct, userdb wasn't needed. poolmon is working great as well!
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
On Wed, 2010-09-29 at 11:46 -0700, Brad Davidson wrote:
> userdb {
> driver = static
> args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty
> }
This shouldn't be necessary.
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
Edward,
> -Original Message-
>
> Adding this to my 10-director.conf fixed it
>
> passdb {
> driver = static
> args = nopassword=y proxy=y
> }
> userdb {
> driver = static
> args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty
> }
>
> Do I still need "someAttribute=proxy" in pass_attrs?
I believe that having it in the static passdb is sufficient.
>
> If I want to use proxy_maybe, is the LDAP value changed from "proxy"
to
> "proxy_maybe" or in pass_attrs "someAttribute=proxy_maybe"?
The Director does not support proxy_maybe. When using it, all logins are
proxied.
Additionally, you can get rid of any other passdb/userdb sections you've
got on the Directors; the LDAP directory should not be queried at all
since the Director can just proxy everything through to the backends and
let them figure out whether or not the user/pass are valid.
> I'll take a look at poolmon for node failures.
Let me know how it works for you, or if there are any enhancements you'd
find useful.
-Brad
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
Thanks Brad!
Adding this to my 10-director.conf fixed it
passdb {
driver = static
args = nopassword=y proxy=y
}
userdb {
driver = static
args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty
}
Do I still need "someAttribute=proxy" in pass_attrs?
If I want to use proxy_maybe, is the LDAP value changed from "proxy" to
"proxy_maybe" or in pass_attrs "someAttribute=proxy_maybe"?
I'll take a look at poolmon for node failures.
[Dovecot] Problem with dovecot/deliver and SSL in 2.0.4
I'm facing a problem with dovecot/deliver and SSL in 2.0.4 which did not
occur in earlier releases:
I get this error message:
postfix/local[18259]: 687CE86514: to=,
relay=local, delay=0.08, delays=0.02/0/0/0.06, dsn=5.3.0, status=bounced
(Command died with status 89: "/usr/libexe
c/dovecot/deliver". Command output: doveconf: Fatal: Error in
configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_key
not set )
My System is:
Linux mylfs 2.6.27.53 #1 Mon Aug 30 14:28:06 CEST 2010 i686 pentium3
i386 GNU/Linux
and dovecot -n reads like this:
# 2.0.3: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.27.53 i686
auth_mechanisms = plain login digest-md5 cram-md5
disable_plaintext_auth = no
mail_location = maildir:~/Maildir
passdb {
args = dovecot
driver = pam
}
passdb {
args = /etc/mail/dovecot/dovecot-cram-md5.pwd
driver = passwd-file
}
service auth {
user = root
}
service imap-login {
inet_listener imap {
address = *
}
inet_listener imaps {
address = *
}
}
service pop3-login {
inet_listener pop3 {
address = 192.168.1.2
}
inet_listener pop3s {
address = 192.168.1.2
}
}
ssl_cert = <>
[Dovecot] Problem with dovecot-acl
I have a problem with dovecot-acl. Some of our users need to use the same Mailbox with all folders: Inbox (with subfolders), Outbox, Send and Deleted, (some users need in full righs, some - readonly) so I choosed Symlinking mailboxes and tried to use dovecot-acl file. cat dovecot-acl: user=t1 lrwsti user=operolegs lrwsti user=operantona lrwsti user=operdss lr User operdss have lrwsti rights in this shared mailbox unstead of lr! But if I comment out other users in the dovecot-acl: #user=t1 lrwsti #user=operolegs lrwsti #user=operantona lrwsti user=operdss lr User operdss have lr rights. Whats wrong? It seems, that dovecot-acl is working only for one user. How can I fix it? === Here is my configs. imap:~# dovecot -n # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.6 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_plugins: acl imap_acl auth default: passdb: driver: pam userdb: driver: passwd plugin: acl: vfile imap:~# ls -l /home/t1/Maildir lrwxrwxrwx 1 root root 21 2010-09-22 16:03 /home/t1/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operolegs/Maildir lrwxrwxrwx 1 root root 21 2010-09-23 16:00 /home/operolegs/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operantona/Maildir lrwxrwxrwx 1 root root 21 2010-09-23 16:00 /home/operantona/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operdss/Maildir lrwxrwxrwx 1 root root 16 2010-09-28 16:32 /home/operdss/Maildir -> /home/t1/Maildir --- imap:/home/t1/Maildir# ls -l total 112 drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 cur -rw-rw 1 t1 mshare99 2010-09-29 15:56 dovecot-acl -rw-rw 1 operdssmshare 312 2010-09-29 16:43 dovecot-acl-list -rw-rw 1 operolegs mshare 1144 2010-09-24 12:16 dovecot.index -rw-rw 1 t1 mshare 41984 2010-09-28 16:39 dovecot.index.cache -rw-rw 1 t1 mshare 25068 2010-09-28 16:38 dovecot.index.log -rw-rw 1 operantona mshare17 2010-09-23 16:41 dovecot-keywords -rw-rw 1 operantona mshare 1941 2010-09-27 10:46 dovecot-uidlist -rw-rw 1 t1 mshare 8 2010-09-29 16:43 dovecot-uidvalidity -rw-rw 1 t1 mshare 0 2010-09-22 10:54 dovecot-uidvalidity.4c99a82f drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 new -rw-rw 1 operdssmshare 327 2010-09-29 16:43 subscriptions drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 tmp - imap:/home/t1/Maildir# dpkg --list|grep dovecot ii dovecot-common 1:1.2.13-1~bpo50+1 secure mail server that supports mbox and maildir mailboxes ii dovecot-imapd1:1.2.13-1~bpo50+1 secure IMAP server that supports mbox and maildir mailboxes dovecot packages - from backports --- Linux: Debian Lenny up2date
Re: [Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Directorinstead of LDAP?
Edward,
> -Original Message-
> So far all examples I've seen on the dovecot
> site require the proxy to know the exact mail server to pass the user
to by
> way of an LDAP lookup.
>
> Does anyone know of a way to have Dovecot Proxy pick a server from
> Directors
> status list instead of looking it up from LDAP?
Automatically setting the proxy destination is actually the core
function of the Director. It maintains an internal list of available
backend servers, and uses a hash algorithm to balance logins across
them. All you need to do to enable this is:
director_servers =
director_mail_servers =
service director {
unix_listener login/director {
mode = 0666
}
fifo_listener login/proxy-notify {
mode = 0666
}
}
passdb {
driver = static
args = nopassword=y proxy=y
}
userdb {
driver = static
args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty
}
service imap-login {
executable = imap-login director
}
service pop3-login {
executable = pop3-login director
}
This tells the login processes to talk to the Director, and the static
passdb/userdb tells the Director to proxy all connections and let the
backend node handle authentication.
Note that this won't work if specific users need to be on specific
servers - the Director makes sure that all of a user's sessions end up
the same host, but it does not care which host it is.
> Also, how does Director discover that an IMAP server is up or down so
that
> it can adjust in the case of a server failure? Is this something that
> Director does automatically or do we need to manually change the mail
> servers vhost count in case of an IMAP node failure?
It does not handle failure on its own. Several of us are using this to
detect and react to node failures:
http://github.com/brandond/poolmon
-Brad
Re: [Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
On Wed, 2010-09-29 at 16:09 +0200, Denny Schierz wrote: > Sep 29 15:33:43 auth(default): Error: LDAP: Connection lost to LDAP > server, reconnecting > Sep 29 15:34:15 auth(default): Error: LDAP: Connection lost to LDAP > server, reconnecting You've configured LDAP server to have a really small connection idle timeout? > hosts = ldap ldap2 > > ps. when does dovecot switches to ldap2? Dovecot doesn't switch. OpenLDAP library switches. I don't know what its internal log is. My guess is it first always connects to ldap, and if that fails then it connects to ldap2 (and never switches back, until connection is lost).
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
Hello again,
I've added the -d and -f flags to the command line and this time I got a
trace.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p
example-message.eml -f u...@domain.com -d u...@domain.com
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols foun.
Program received signal SIGSEGV, Segmentation fault.
0x000800e70140 in seff_flags_merge () from
/usr/lib/dovecot/libdovecot-sieve.so.0
(gdb) bt full
#0 0x000800e70140 in seff_flags_merge () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
Does the attached patch fix it perhaps?
Regards,
Stepha.
diff -r 5cb795d0d1de src/lib-sieve/plugins/imap4flags/tag-flags.c
--- a/src/lib-sieve/plugins/imap4flags/tag-flags.c Tue Sep 28 22:50:04
2010 +0200
+++ b/src/lib-sieve/plugins/imap4flags/tag-flags.c Wed Sep 29 19:09:06
2010 +0200
@@ -340,7 +340,8 @@
const struct sieve_side_effect *new_seffect,
void **old_context)
{
- *old_context = new_seffect->context;
+ if ( new_seffect != NULL )
+ *old_context = new_seffect->context;
return 1;
}
Re: [Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
On 2010-09-29 10:26 AM, Denny Schierz wrote: > # grep conn=1103 local4.log > > http://pastebin.com/a1h1YE8P Same for this... -- Best regards, Charles
Re: [Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
On 2010-09-29 10:09 AM, Denny Schierz wrote: > My DoveCot Config: > > http://pastebin.com/W7zHf4fT Please don't do this (it makes it harder to help you) - just paste the output in the email body... -- Best regards, Charles
[Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Director instead of LDAP?
We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP lookup. Does anyone know of a way to have Dovecot Proxy pick a server from Directors status list instead of looking it up from LDAP? Also, how does Director discover that an IMAP server is up or down so that it can adjust in the case of a server failure? Is this something that Director does automatically or do we need to manually change the mail servers vhost count in case of an IMAP node failure? Thanks
[Dovecot] Doveadm expunge purge optimize
Hello,
I'm testing Dovecot 2.0.3.
I plan to use Dovecot with 10 thousands domains per server (~50
thousands accounts).
I use 'mdbox' as mailbox format. So, I have two cron jobs before backup:
01 22 * * * root nice -n 19 /usr/bin/doveadm expunge -A mailbox SPAM
BEFORE 60d
01 00 * * * root nice -n 19 /usr/bin/doveadm purge -A
01 02 * * * root nice -n 19 My_Backup_aplication
Each doveadm command walks through the whole file system. Is there a way
to run the two operations into a single walk? Does anyone have a
suggestion that helps optimize this?
Thank you in advance.
Best Regards
My confs :
r...@server:# dovecot -n
# 2.0.3 (02a9cf90ad02): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-24-server x86_64 Ubuntu 10.04.1 LTS
auth_cache_negative_ttl = 3600 s
auth_cache_size = 33554432
auth_master_user_separator = *
auth_mechanisms = plain login
auth_username_chars =
abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz01234567890...@=
auth_worker_max_count = 10
disable_plaintext_auth = no
listen = server.com
login_greeting = Dovecot server !
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 = server.com
port = 143
}
}
service imap {
process_limit = 1024
process_min_avail = 10
}
service lmtp {
inet_listener {
address = server.com
port = 2003
}
process_limit = 256
process_min_avail = 10
}
service managesieve-login {
inet_listener sieve {
address = server.com
port = 4190
}
inet_listener sieve_deprecated {
address = server.com
port = 2000
}
}
service managesieve {
process_limit = 20
process_min_avail = 10
}
service pop3-login {
inet_listener pop3 {
address = server.com
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 = 10
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 = Dovecot ManageSieve Pigeonhole
server
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
}
r...@server:#
--
[]'s
Thiago Henrique
Network Administration
Digirati Networks
K8 Networks
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
On 29/09/2010 16:40, Stephan Bosch wrote:
> Op 29-9-2010 17:35, Stephan Bosch schreef:
>> Op 29-9-2010 17:33, interfaSys sàrl schreef:
>>> (gdb) bt full
>>> #0 0x000800e70140 in seff_flags_merge () from
>>
>> According to this, you have a require "imap4flags"; somewhere on top
>> of your Sieve script right?
>
Nope, only fileinto, but the sieve_before script does.
***
require "fileinto";
if true {
redirect "ofu...@gmail.com";
}
if true {
keep;
stop;
}
***
> Also, it's apparently running in multiscript context:
>> #21 0x000800e6a8f5 in sieve_multiscript_run () from
>> /usr/lib/dovecot/libdovecot-sieve.so.0
>
Indeed
> Could you send me (not the list necessarily) full versions of all
> involved scripts (including those executed from
> sieve_before/sieve_after) and the output of dovecot -n?
>
There is just one.
**
require ["fileinto","imap4flags"];
if allof(header :contains "X-DSPAM-Result" "Spam",
not header :contains "X-DSPAM-Reclassified" "Innocent") {
setflag "\\Seen";
fileinto "INBOX/spam";
stop;
}
keep;
**
I'll send doveconf -n separately
> Regards,
>
> Stephan.
>
>
Cheers,
Olivier
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
Op 29-9-2010 17:35, Stephan Bosch schreef: Op 29-9-2010 17:33, interfaSys sàrl schreef: (gdb) bt full #0 0x000800e70140 in seff_flags_merge () from According to this, you have a require "imap4flags"; somewhere on top of your Sieve script right? Also, it's apparently running in multiscript context: #21 0x000800e6a8f5 in sieve_multiscript_run () from /usr/lib/dovecot/libdovecot-sieve.so.0 Could you send me (not the list necessarily) full versions of all involved scripts (including those executed from sieve_before/sieve_after) and the output of dovecot -n? Regards, Stephan.
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
Op 29-9-2010 17:33, interfaSys sàrl schreef: Hello again, I've added the -d and -f flags to the command line and this time I got a trace. (gdb) r Starting program: /usr/libexec/dovecot/dovecot-lda -p example-message.eml -f u...@domain.com -d u...@domain.com (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols foun. Program received signal SIGSEGV, Segmentation fault. 0x000800e70140 in seff_flags_merge () from /usr/lib/dovecot/libdovecot-sieve.so.0 (gdb) bt full #0 0x000800e70140 in seff_flags_merge () from According to this, you have a require "imap4flags"; somewhere on top of your Sieve script right? Regards, Stephan.
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
Hello again,
I've added the -d and -f flags to the command line and this time I got a
trace.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p
example-message.eml -f u...@domain.com -d u...@domain.com
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols foun.
Program received signal SIGSEGV, Segmentation fault.
0x000800e70140 in seff_flags_merge () from
/usr/lib/dovecot/libdovecot-sieve.so.0
(gdb) bt full
#0 0x000800e70140 in seff_flags_merge () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#1 0x000800e58d61 in sieve_result_side_effects_merge.clone.0 ()
from /usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#2 0x000800abf0b0 in ?? ()
No symbol table info available.
#3 0x000800abc040 in ?? ()
No symbol table info available.
#4 0x000800abf0f8 in ?? ()
No symbol table info available.
#5 0x000800ea08e0 in sieve_side_effect_operand_class () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#6 0x000800abc388 in ?? ()
No symbol table info available.
#7 0x000800abc040 in ?? ()
No symbol table info available.
#8 0x000800abc388 in ?? ()
No symbol table info available.
#9 0x7fffe180 in ?? ()
No symbol table info available.
#10 0x000800abf078 in ?? ()
No symbol table info available.
#11 0x000800e58f71 in _sieve_result_add_action () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#12 0x000800e59415 in sieve_result_add_keep () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#13 0x000800e670f3 in cmd_keep_operation_execute () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#14 0x00080005 in ?? ()
No symbol table info available.
#15 0x in ?? ()
No symbol table info available.
#16 0x00080001 in ?? ()
No symbol table info available.
#17 0x000800abf0b0 in ?? ()
No symbol table info available.
#18 0x000800abf040 in ?? ()
No symbol table info available.
#19 0x000800e5542b in sieve_interpreter_continue () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#20 0x000800e555bb in sieve_interpreter_run () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#21 0x000800e6a8f5 in sieve_multiscript_run () from
/usr/lib/dovecot/libdovecot-sieve.so.0
No symbol table info available.
#22 0x in ?? ()
No symbol table info available.
#23 0x000800abf040 in ?? ()
No symbol table info available.
#24 0x0001 in ?? ()
No symbol table info available.
#25 0x0001 in ?? ()
No symbol table info available.
#26 0x0001 in ?? ()
No symbol table info available.
#27 0x000800a06248 in ?? ()
No symbol table info available.
#28 0x0008 in ?? ()
No symbol table info available.
#29 0x000800a23e40 in ?? ()
No symbol table info available.
#30 0x0001 in ?? ()
No symbol table info available.
#31 0x000800515bfb in lda_sieve_deliver_mail () from
/usr/lib/dovecot/lib90_sieve_plugin.so
Cheers,
Olivier
On 29/09/2010 15:01, Stephan Bosch wrote:
> Op 29-9-2010 14:42, interfaSys sàrl schreef:
>> Hello,
>>
>> One account couldn't get emails all the sudden.
>> dovecot-lda was crashing with "signal 11 (segmentation fault)".
>> There was absolutely nothing in the dovecot logs, even with
>> mail_debug=yes.
>>
>> I found out that it was because of the following lines in a sieve script
>> that were generated by a script generator (Ingo).
>>
>> if true {
>> keep;
>> stop;
>> }
>>
>> I'm using the latest revision of pigeonhole with Dovecot 2.0.4.
>
> Hmm. I cannot reproduce this.
>
> You should:
>
> 1) send your dovecot -n output.
>
> 2) If you can easily reproduce it: produce a backtrace of the problem
> using gdb:
>
> You can for instance run dovecot-lda manually as follows: gdb --args
> /usr/lib/dovecot-lda -p example-message.eml
>
> And then:
>
> - issue 'r' command
> - (hopefully) see it crash with sigsegfault
> - issue 'bt full' command and report the output back here
> - also include a copy of the full Sieve script that you are using and
> the example message.
>
> You can also use core dumps if the problem is more transient:
> http://www.dovecot.org/bugreport.html
>
> Regards,
>
> Stephan.
>
>
>
>
>
>
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
Hello,
I tried to do a trace but it didn't seem to work.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p example-message.eml
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols founn
Program exited with code 0100.
Nothing gets delivered.
Cheers,
Olivier
On 29/09/2010 15:01, Stephan Bosch wrote:
> Op 29-9-2010 14:42, interfaSys sàrl schreef:
>> Hello,
>>
>> One account couldn't get emails all the sudden.
>> dovecot-lda was crashing with "signal 11 (segmentation fault)".
>> There was absolutely nothing in the dovecot logs, even with
>> mail_debug=yes.
>>
>> I found out that it was because of the following lines in a sieve script
>> that were generated by a script generator (Ingo).
>>
>> if true {
>> keep;
>> stop;
>> }
>>
>> I'm using the latest revision of pigeonhole with Dovecot 2.0.4.
>
> Hmm. I cannot reproduce this.
>
> You should:
>
> 1) send your dovecot -n output.
>
> 2) If you can easily reproduce it: produce a backtrace of the problem
> using gdb:
>
> You can for instance run dovecot-lda manually as follows: gdb --args
> /usr/lib/dovecot-lda -p example-message.eml
>
> And then:
>
> - issue 'r' command
> - (hopefully) see it crash with sigsegfault
> - issue 'bt full' command and report the output back here
> - also include a copy of the full Sieve script that you are using and
> the example message.
>
> You can also use core dumps if the problem is more transient:
> http://www.dovecot.org/bugreport.html
>
> Regards,
>
> Stephan.
>
>
>
>
>
>
[Dovecot] SASL auth and proxy
Hello, I'm finding a way to have a pool of smtp-auth servers in front of my actuals servers to permit relay to our customers. Now users sends emails connecting to the right IP via mail.domain.tld, with authentication. Every server has it's own user database in mysql. I'd like to have a pool of server (with round robin, ideally with postfix + sasl + dovecot) that authenticate the users with the actuals servers and then pointing mail.domain.tld to this pool and not to one server. My trouble is how to authenticate users. Can I use: http://wiki.dovecot.org/Authentication/MultipleDatabases to tell Dovecot to authenticate with every MySQL database on the servers "behind"? If yes, is there a better way to do this considering I'm already using some proxy machines (dovecot) for pop3/imap and so I already have a db with domain.tld -> IP of the server? I also have some machine without a MySQL DB for users (vpopmail + cdb), so the option with MultipleDatabases will be good only for some machines. Something similar to the proxy mechanism that I already use for pop3/imsp will be good: the proxy connect to the machine behind that do the authentication, I only need a table with domain -> server IP (that I already have). Thanks for any advice.
[Dovecot] Error on mailbox file
Hi! I'm running Postfix 2.2.9 as MTA. I have several mail clients , such as Outlook 2000/xp/2007. The clients comunicate to the MTA using pop3/smtp protocols. I have also installed Webmail Squirrel for the internet users. Squirrel needs an Imap server, so i have utilized Dovecot 1.2.6. To authenticate users , i use pam_winbbind to validate users to my NT domain. Here is my problem : Today i checked my /var/log/mail log and this took my attention : Sep 29 08:25:07 host1 dovecot: imap-login: Login: user=, method=PLAIN, rip=172.20.22.12, lip=172.20.22.14 Sep 29 08:25:07 host1 dovecot: IMAP(user): mail_location: mbox: mkdir(/home/NT-DOMAIN/user/mail) failed: Permission denied (euid=10188(user) egid=10001(domain users) missing +w perm: /home) Sep 29 08:25:07 host1 dovecot: IMAP(user): Fatal: Namespace initialization failed Here , i assume the user put his user name in CAPS (USER), and that i generating an error. Then Dovecot tries to create the directory /home/NT-DOMAIN/user/mail. In my dovecot.conf file , i have : mail_location = mbox:~/mail:INBOX=/var/mail/%u Now , the log continues : Sep 29 08:25:18 host1 dovecot: imap-login: Login: user=, method=PLAIN, rip=172.20.22.12, lip=172.20.22.14 Sep 29 08:25:18 host1 dovecot: IMAP(user): mail_location: mbox: mkdir(/home/NT-DOMAIN/user/mail) failed: Permission denied (euid=10188(user) egid=10001(domain users) missing +w perm: /home) Sep 29 08:25:18 host1 dovecot: IMAP(user): Fatal: Namespace initialization failed Here the user re-enters the user, now correctly, but the problem persists . Finally , a could see this new log entry : Sep 29 10:50:43 host1 postfix/local[19663]: 50B98441E0: to=, orig_to=, relay=local, delay=0, status=bounced (cannot access mailbox /var/mail/user for user user. cannot open file: Permission denied) Here some user tries to send an email to this user , and a permission denied error occurs. Watching the permissions on the file : -rw--- 1 user users 1499655 2010-09-29 02:18 /var/mail/user Maybe some Dovecot process is blocking the file access ? List of Dovecot process: ps ax | grep dovecot 25997 ? Ss 0:07 /usr/sbin/dovecot 15399 ? S 0:02 dovecot-auth 20614 ? S 0:00 dovecot-auth -w How can i fix this issue? Thank you very much ! Augusto
Re: [Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
hi, I enabled a bit more logging and it seems, that "auth" try to connect without anything: # grep conn=1103 local4.log http://pastebin.com/a1h1YE8P cu denny signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
OK, I'll give the trace a try. Thanks for the instructions.
In the meantime, here is more info.
The sieve script does a redirect and a local save. It works fine if only
the redirect is in place.
if true {
redirect "some.em...@domain.com";
}
if true {
keep;
stop;
}
I'm using mdbox as storage.
Cheers,
Olivier
On 29/09/2010 15:01, Stephan Bosch wrote:
> Op 29-9-2010 14:42, interfaSys sàrl schreef:
>> Hello,
>>
>> One account couldn't get emails all the sudden.
>> dovecot-lda was crashing with "signal 11 (segmentation fault)".
>> There was absolutely nothing in the dovecot logs, even with
>> mail_debug=yes.
>>
>> I found out that it was because of the following lines in a sieve script
>> that were generated by a script generator (Ingo).
>>
>> if true {
>> keep;
>> stop;
>> }
>>
>> I'm using the latest revision of pigeonhole with Dovecot 2.0.4.
>
> Hmm. I cannot reproduce this.
>
> You should:
>
> 1) send your dovecot -n output.
>
> 2) If you can easily reproduce it: produce a backtrace of the problem
> using gdb:
>
> You can for instance run dovecot-lda manually as follows: gdb --args
> /usr/lib/dovecot-lda -p example-message.eml
>
> And then:
>
> - issue 'r' command
> - (hopefully) see it crash with sigsegfault
> - issue 'bt full' command and report the output back here
> - also include a copy of the full Sieve script that you are using and
> the example message.
>
> You can also use core dumps if the problem is more transient:
> http://www.dovecot.org/bugreport.html
>
> Regards,
>
> Stephan.
>
>
>
>
>
>
[Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
hi, I see in dovecots logfile some error messages: Sep 29 15:33:43 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:34:15 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:34:50 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:35:22 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:36:01 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:36:37 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:37:16 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:37:52 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:38:24 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting I don't know, what could be the problem. I upgraded Dovecot from 1.2.13 to 1.2.14 to solving the problem, but ... no success. Our LDAP Server is 2.4.23 and works for our network without any problems. If I try to use ldapsearch from the Dovecot host, while I see the messages, ldapsearch works withouch any timeout. I enabled caching for auth too, but the problem still exists. My DoveCot Config: http://pastebin.com/W7zHf4fT the LDAP part: hosts = ldap ldap2 auth_bind = yes ldap_version = 3 base = cn=accounts, dc=foo user_attrs = postalAddress=domain, homeDirectory=/imap/spool/%d/%1n/%n, myMailQuota=quota_rule=*:storage=%$M user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_attrs = postalAddress=domain, uid=user, userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = MD5 any suggestions? cu denny ps. when does dovecot switches to ldap2? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [Dovecot] dovecot-lda segfaults with some sieve scripts
Op 29-9-2010 14:42, interfaSys sàrl schreef:
Hello,
One account couldn't get emails all the sudden.
dovecot-lda was crashing with "signal 11 (segmentation fault)".
There was absolutely nothing in the dovecot logs, even with mail_debug=yes.
I found out that it was because of the following lines in a sieve script
that were generated by a script generator (Ingo).
if true {
keep;
stop;
}
I'm using the latest revision of pigeonhole with Dovecot 2.0.4.
Hmm. I cannot reproduce this.
You should:
1) send your dovecot -n output.
2) If you can easily reproduce it: produce a backtrace of the problem
using gdb:
You can for instance run dovecot-lda manually as follows: gdb --args
/usr/lib/dovecot-lda -p example-message.eml
And then:
- issue 'r' command
- (hopefully) see it crash with sigsegfault
- issue 'bt full' command and report the output back here
- also include a copy of the full Sieve script that you are using and
the example message.
You can also use core dumps if the problem is more transient:
http://www.dovecot.org/bugreport.html
Regards,
Stephan.
Re: [Dovecot] problems and dovecot & manegesieve
On Wed, 2010-09-29 at 13:53 +0100, Jose Luis Faria wrote: > > Add "sieve" to protocols setting. > > I did this add yesterday but it still not working. Show your full doveconf -n output then.
[Dovecot] LMTP don't accept jobs for system users
Hi, I'm trying to configure Dovecot 2.0.1 to deliver email to users in
/etc/passwd using the Dovecot LMTP service. So far, I can
sucessufully do POP3 for system users, but when Postfix tries to deliver
email to the Dovecot LMTP service the LMTP reject the job with:
"User doesn't exist a...@centos54.mydomain.com"
Any suggestions?
The user 'ale' is a valid user:
# grep ale /etc/passwd
ale:x:500:500:Alex:/home/ale:/sbin/nologin
This is the dovecot -n output:
# 2.0.1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-164.el5xen i686 CentOS release 5.4 (Final)
disable_plaintext_auth = no
mail_location = maildir:~/Maildir
mail_privileged_group = mail
mbox_write_locks = fcntl
passdb {
args = session=yes failure_show_msg=yes dovecot
driver = pam
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1
port = 10050
}
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert =
Re: [Dovecot] problems and dovecot & manegesieve
Hello, Em 28-09-2010 18:10, Timo Sirainen escreveu: On Tue, 2010-09-28 at 16:19 +0100, Jose Luis Faria wrote: Hello, my server is working with dovecot-2.0.2+dovecot-2.0-pigeonhole-0.2.0. but if activate managesieve, is not listening in 4190! Add "sieve" to protocols setting. I did this add yesterday but it still not working. -- :) cumprimentos -- José Luís Faria Network Eng./Administrador de Sistemas Departamento de Informática Universidade do Minho Braga, Portugal smime.p7s Description: S/MIME Cryptographic Signature
[Dovecot] dovecot-lda segfaults with some sieve scripts
Hello,
One account couldn't get emails all the sudden.
dovecot-lda was crashing with "signal 11 (segmentation fault)".
There was absolutely nothing in the dovecot logs, even with mail_debug=yes.
I found out that it was because of the following lines in a sieve script
that were generated by a script generator (Ingo).
if true {
keep;
stop;
}
I'm using the latest revision of pigeonhole with Dovecot 2.0.4.
Cheers,
Olivier
Re: [Dovecot] Fwd: NFS question
On 2010-09-29 1:27 AM, Nick Edwards wrote: > I do not wish responses from those who are not developers of dovecot, Then you should have spent the few seconds required to browse the PUBLIC list archives for Timo's current email address - then I wouldn't have even seen this message and you wouldn't be getting this response. > many I have since had discussions with on another list and spam > binned (abusive souls like charlie marcus) If you consider simply correcting your misunderstanding of how dovecot works as 'abusive', then, yeah, I guess I'm guilty as charged. > but I likely was mailing a old address he doesn't read Like I said - took me all of 10 seconds to determine his current email address from his most recent posting to this list (he posts daily). -- Best regards, Charles
[Dovecot] Fwd: NFS question
Resent to list, since my previous direct emails to Timo have gone unanswered
I am NOT a member of this list so Timo please reply direct
I do not wish responses from those who are not developers of dovecot, many I
have since had discussions with on another list and spam binned (abusive
souls like charlie marcus) some for trolling, I seek a definitive answer and
there is only one man who can give this, but I likely was mailing a old
address he doesn't read
-- Forwarded message --
From: Nick Edwards
Date: Fri, Sep 24, 2010 at 6:15 PM
Subject: NFS question
To: t...@iki.fi
After reading the archives recently on a few threads about NFS I have
concerns
over our plans to move from cyrus to dovecot, we initially discounted
dovecot as
a choice over it, but since dovecot and sieve go well together, I am just
re-capping
everything before we approve move to courier or back to dovecot, having re
read
those threads over a couple of times, am I right in assuming that this
caching
problem, is really only a problem if using imap and the chances of it being
an
issue with pop3 is very rare?
If this is the case, then we certainly would approve move to dovecot.
I note some people who have apparently much larger systems than us, say
that
they have seen no problems but others say they may have had just not
noticed.
So, if smtp3 delivers to storage MailDir and pop3-1 connects to get mail -
at the same time: no problem just wont see that message until next refresh
at the same time: will see message
if smtp3 and smtp1 deliver at same time there lies the corruption issue?
If so, it will be reindexed at next delivery or pop3?
Just trying to understand where it will be a problem, we will use postfix
setting of virtual_transport = dovecot and
dovecot_destination_recipient_limit = 1
We dont allow multiple logins either, we have only intention for one imap
server, to compliment our two pop3's and 4 smtp's.
We intend to use -
pop3_lock_session=yes
maildir_very_dirty_syncs=yes
auth_verbose = yes
auth_cache_size = 512
auth_cache_ttl = 3600
auth_cache_negative_ttl = 0
mail_location = maildir:/var/vmail/%1d/%d/%n/Maildir
mmap_disable = yes
mail_nfs_storage = yes
mail_nfs_index = yes
protocol lda {
mail_plugins = quota cmusieve
quota_full_tempfail = yes
auth_socket_path = /var/run/dovecot/auth-master
}
Also, will this be more of a problem if we use dovecot v1.2 or v2.0 ?
(only examples of configs we have for our move is for v1.2 at present for
debian)
Hope you do not mind me asking this in private, but given how those threads
ended up in personal attacks, I would rather not reignite any fires.
Nick
Re: [Dovecot] LMTP proxy too many DATA output timeout (perhaps)
Hi Timo,
sorry for late answer, but I'm trying to look deeper at problem.
Stracing both director and real lmtp server, I've noticed that both of
them seem to be stuck waiting for input on socket fd.
Director's lmtp seem to be waiting some input from real server, but mail
message is not yet sent completely and there no real reason to wait for it.
I hope this help.
Luca
Director lmtp's strace (fd 11 is socket from postfix server, fd 13 is
socket to dovecot real server):
--
08:33:04.418921 read(13, "250-xxxi"..., 970) = 104
08:33:04.418978 write(13, "RCPT TO:\r\n", 28) = 28
08:33:04.419034 read(13, 0x815aa06, 866) = -1 EAGAIN (Resource
temporarily unavailable)
08:33:04.419076 gettimeofday({1285741984, 419092}, NULL) = 0
08:33:04.419120 epoll_wait(10, {{EPOLLIN, {u32=134706928,
u64=134706928}}}, 103, 964) = 1
08:33:04.447847 gettimeofday({1285741984, 447864}, NULL) = 0
08:33:04.447892 read(13, "250 2.1.5 OK\r\n", 866) = 14
08:33:04.447941 write(13, "DATA\r\n", 6) = 6
08:33:04.447991 read(13, 0x815aa14, 852) = -1 EAGAIN (Resource
temporarily unavailable)
08:33:04.448033 gettimeofday({1285741984, 448049}, NULL) = 0
08:33:04.448077 epoll_wait(10, {{EPOLLIN, {u32=134706928,
u64=134706928}}}, 103, 935) = 1
08:33:04.449844 gettimeofday({1285741984, 449860}, NULL) = 0
08:33:04.449888 read(13, "354 OK\r\n", 852) = 8
08:33:04.449952 setsockopt(13, SOL_TCP, TCP_CORK, [1], 4) = 0
08:33:04.449995 write(13, "Return-Path: 4286
08:33:04.450097 read(11, "olid #CC; border-bottom: 0; "..., 4096) = 4096
08:33:04.450155 write(13, "rce=3Dviadeomail-IT&utm_medi"..., 4096) =
4096
08:33:04.450218 gettimeofday({1285741984, 450234}, NULL) = 0
08:33:04.450294 read(11, "vertical-ali=\r\ngn: middle; font-"..., 4096)
= 4096
08:33:04.450351 write(13, "ize:15px;color:#66;padding:0"..., 4096) =
4096
08:33:04.450406 gettimeofday({1285741984, 450423}, NULL) = 0
08:33:04.450481 read(11, "/a>08:33:04.450537 write(13, "olor: #fff; color: #006DA4;\" hei"..., 4096)
= 2002
08:33:04.450589 gettimeofday({1285741984, 450606}, NULL) = 0
08:33:04.450662 write(13, ";color:#ec9516;p=\r\nadding:0px 8p"..., 4932)
= -1 EAGAIN (Resource temporarily unavailable)
08:33:04.450715 gettimeofday({1285741984, 450732}, NULL) = 0
08:33:04.450759 write(13, ";color:#ec9516;p=\r\nadding:0px 8p"..., 4932)
= -1 EAGAIN (Resource temporarily unavailable)
08:33:04.450854 gettimeofday({1285741984, 450870}, NULL) = 0
08:33:04.450899 read(11, "e; qui=\r\n.. Leggendo molti profi"..., 4096)
= 4096
08:33:04.450972 write(13, ";color:#ec9516;p=\r\nadding:0px 8p"..., 4932)
= 4932
08:33:04.451038 write(13, " Mi sono avvicinata al web p"..., 4099) =
3756
08:33:04.451091 gettimeofday({1285741984, 451107}, NULL) = 0
08:33:04.451145 read(11, " 10px 1px 0px;\" valign=3D\"top\">c"..., 4096)
= 4096
08:33:04.451232 writev(13, [{"amp/bg-box-title.gif); backgroun"...,
4436}, {"cellpadding=3D\"0\" border=3D\"0\" w"..., 1160}], 2) = -1
EAGAIN (Resource temporarily unavailable)
08:33:04.451302 gettimeofday({1285741984, 451319}, NULL) = 0
08:33:04.451347 read(11, "=\r\ni e bar - Annuario Qualit&agr"..., 4096)
= 4096
08:33:04.451429 writev(13, [{"amp/bg-box-title.gif); backgroun"...,
4436}, {"cellpadding=3D\"0\" border=3D\"0\" w"..., 3033}], 2) = -1
EAGAIN (Resource temporarily unavailable)
08:33:04.451498 gettimeofday({1285741984, 451515}, NULL) = 0
08:33:04.451543 writev(13, [{"amp/bg-box-title.gif); backgroun"...,
4436}, {"cellpadding=3D\"0\" border=3D\"0\" w"..., 3033}], 2) = -1
EAGAIN (Resource temporarily unavailable)
08:33:04.451612 gettimeofday({1285741984, 451629}, NULL) = 0
08:33:04.451656 read(11, "or:#66;padding:1px 10px 1px "..., 4096) = 3242
08:33:04.451723 writev(13, [{"amp/bg-box-title.gif); backgroun"...,
4436}, {"cellpadding=3D\"0\" border=3D\"0\" w"..., 3033}], 2) = -1
EAGAIN (Resource temporarily unavailable)
08:33:04.451792 gettimeofday({1285741984, 451858}, NULL) = 0
08:33:04.451887 gettimeofday({1285741984, 451904}, NULL) = 0
08:33:04.451931 writev(13, [{"amp/bg-box-title.gif); backgroun"...,
4436}, {"cellpadding=3D\"0\" border=3D\"0\" w"..., 3033}], 2) = 7469
08:33:04.452016 setsockopt(13, SOL_TCP, TCP_CORK, [0], 4) = 0
08:33:04.452060 read(13, 0x815aa1c, 844) = -1 EAGAIN (Resource
temporarily unavailable)
... and after 60secs timeout...
08:34:04.460271 setsockopt(11, SOL_TCP, TCP_CORK, [1], 4) = 0
08:34:04.460327 write(11, "451 4.4.0 Remote server not answ"..., 61) = 61
08:34:04.460391 setsockopt(11, SOL_TCP, TCP_CORK, [0], 4) = 0
08:34:04.460443 epoll_ctl(10, EPOLL_CTL_DEL, 13, {0, {u32=134706928,
u64=134706928}}) = 0
08:34:04.460511 close(13) = 0
08:34:04.460662 read(11, "adding:1px 10px 1px 10px;font-we"..., 854) = 854
08:34:04.460722 gettimeofday({1285742044, 460739}, NULL) = 0
08:34:04.460766 read(11, "2px;\" align=3D\"right\">= 4096
08:34:04.460845 gettimeofday({1285742044, 460861}, NULL) = 0
08:34:04.460888 read(11, "
