Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2019-04-19 15:26, Aki Tuomi via dovecot wrote: Unfortunately we have quite long list of things to do, so sometimes even trivial things can take a long time. Not to hijack the thread, but perhaps you could elaborate on what has changed within Dovecot? Timo seems to be put in the background, releases are less frequent and with less changes/additions. The days of "Oh, great idea - I added that, see this commit" seem gone. Is this because OX acquired Dovecot, so priorities have changed? Or what is going on? Mostly just curious. -- Tom
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
Unfortunately we have quite long list of things to do, so sometimes even trivial things can take a long time. Aki On 18 April 2019 16:53 Tanstaafl via dovecot < dovecot@dovecot.org> wrote: Sadly, I guess not... I'm not sure what to make of this, seeing as both Wietse and Timo said it was almost a trivial thing to fix. On Fri Apr 12 2019 12:17:22 GMT-0400 (Eastern Standard Time), Tanstaafl via dovecot < dovecot@dovecot.org> wrote: I'm resurrecting this again because I'm getting pretty close to possibly being ready to install a brand new dovecot server (finally), but I still need for dovecots LMTP to add the x-original-to header. So... was this completed quietly, or is support for it still not there? Thanks, Charles --- Aki Tuomi
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
Sadly, I guess not... I'm not sure what to make of this, seeing as both Wietse and Timo said it was almost a trivial thing to fix. On Fri Apr 12 2019 12:17:22 GMT-0400 (Eastern Standard Time), Tanstaafl via dovecot wrote: > I'm resurrecting this again because I'm getting pretty close to possibly > being ready to install a brand new dovecot server (finally), but I still > need for dovecots LMTP to add the x-original-to header. > > So... was this completed quietly, or is support for it still not there? > > Thanks, > > Charles
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
I'm resurrecting this again because I'm getting pretty close to possibly being ready to install a brand new dovecot server (finally), but I still need for dovecots LMTP to add the x-original-to header. So... was this completed quietly, or is support for it still not there? Thanks, Charles On Tue Apr 28 2015 15:27:07 GMT-0400 (Eastern Standard Time), Charles Marcus wrote: > On 4/28/2015 1:40 PM, Tobias Franzén wrote: >> On 2014-01-08 14:32, Charles Marcus wrote: >>> On 2012-04-09 8:53 AM, Timo Sirainen wrote: On 9.4.2012, at 15.50, Charles Marcus wrote: >> LMTP adds a new Delivered-To: header when there is >> a single RCPT TO. You can force a single RCPT TO from Postfix side by >> setting lmtp_destination_recipient_limit=1. LMTP doesn't >> add/remove/change X-Original-To: header. > Ok, thanks Timo... but... > > Are you saying that this 'Delivered-To:' header can somehow be > leveraged to provide the same info as the x-original-to header? I guess X-Original-To is the same address as what Postfix sees as the original RCPT TO address before alias expansion and such? In that case, see my today's mail in Postfix list.. >>> Hi Timo, >>> >>> I just tried to find your email from that day, but don't see it in the >>> archives... >>> >>> Was this ever resolved (getting x-original-to support in LMTP, like it >>> is for the LDA)? >>> >>> If not, since it seemed like it wasn't going to be much work, any >>> chance you can revisit it soon? >> Hello, >> >> I have tried to keep tabs on the various discussions going on related to >> the X-Original-To header when using Dovecot LMTP. Until now I have not >> needed a solution, but I am now finally about to migrate my old server. >> >> Old setup: Postfix + SpamAssassin (after-queue content filter via pipe) >> + virtual transport, and Courier-IMAP. >> New setup: Postfix + amavisd-new (after-queue content filter via smtp, >> with ClamAV and SpamAssassin) + Dovecot LMTP, and Dovecot for IMAP. >> >> Charles, have you found a way that works for you? > > No, and I simply haven't switched to LMTP yet, for this and one other > reason (political, not technical)... > > As for the rest below... wow... all I can say is, it sure would be nice > if Timo/Wietse could just add the few lines of code that Timo said would > be needed to properly support it natively. > >> I was experimenting some with my test server and came up with a way that >> utilizes some additional internal smtp content filter forwarding, which >> produces some overhead. It should be light compared with the load from >> ClamAV and SpamAssassin, however. >> >> I'm not yet sure how amavisd-new funneling would handle multiple local >> recipients with different settings without passing the mail through >> multiple time, at least once per local user, let alone without first >> performing address mapping in postfix (for alias expansion). I have >> configured per-user SpamAssassin bayes filtering, and may introduce a >> whitelist based on address book entries (Roundcube.) >> >> >> This solution I'm currently testing will pass each message through >> amavisd-new one time each per local and remote recipient, and will only >> add the X-Original-To header to the specific local recipient each >> envelope is intended for. No external users will receive the header, and >> no local user will see which other local users (e.g. via BCC) have >> potentially received the same message. >> >> Flow: >> all mail in (both external and tls-authenticated internal) -> smtp (1) >> -> smtp-split (2) -> smtp-to-me (3a) | smtp-to-external (3b) -> >> smtp-amavis (4) -> dovecot-lmtp (5) >> >> 1) I rely on default_destination_recipient_limit=1 in main.cf to split >> each incoming mail into one stream per recipient. >> 2) smtp-split will receive one stream per recipient. Default >> content_filter=smtp-to-me, followed by option >> "smtpd_recipient_restrictions=permit_auth_destination,check_recipient_access,pcre:/usr/local/etc/postfix/filter-to-external.pcre,permit_mynetworks,reject" >> >> means I stop processing restrictions if my server is the destination. If >> my server is not the destination, the FILTER in check_recipient_access >> will override the preceding smtp-to-me filter. >> >> Both 1) and 2) smtpd instances include option >> receive_override_options=no_address_mappings, to wait with mapping to >> internal recipient until we can add X-Original-To header for my server's >> users only. >> >> 3a) For mail to my server, smtp-to-me will add X-Original-To using a >> pcre script, in a similar fashion to step 2's filter. This step also >> expands the address mapping (by not specifying any >> receive_override_options). >>-o >> smtpd_recipient_restrictions=check_recipient_access,pcre:/usr/local/etc/postfix/recipient_access_x-orig.pcre,permit_mynetworks,reject >> >> 3b) For mail leaving my server, smtp-to-external will not add any >> processing besides
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2014-01-08 14:32, Charles Marcus wrote: On 2012-04-09 8:53 AM, Timo Sirainen t...@iki.fi wrote: On 9.4.2012, at 15.50, Charles Marcus wrote: LMTP adds a new Delivered-To:rcpt-to@address header when there is a single RCPT TO. You can force a single RCPT TO from Postfix side by setting lmtp_destination_recipient_limit=1. LMTP doesn't add/remove/change X-Original-To: header. Ok, thanks Timo... but... Are you saying that this 'Delivered-To:' header can somehow be leveraged to provide the same info as the x-original-to header? I guess X-Original-To is the same address as what Postfix sees as the original RCPT TO address before alias expansion and such? In that case, see my today's mail in Postfix list.. Hi Timo, I just tried to find your email from that day, but don't see it in the archives... Was this ever resolved (getting x-original-to support in LMTP, like it is for the LDA)? If not, since it seemed like it wasn't going to be much work, any chance you can revisit it soon? Thanks, Hello, I have tried to keep tabs on the various discussions going on related to the X-Original-To header when using Dovecot LMTP. Until now I have not needed a solution, but I am now finally about to migrate my old server. Old setup: Postfix + SpamAssassin (after-queue content filter via pipe) + virtual transport, and Courier-IMAP. New setup: Postfix + amavisd-new (after-queue content filter via smtp, with ClamAV and SpamAssassin) + Dovecot LMTP, and Dovecot for IMAP. Charles, have you found a way that works for you? I was experimenting some with my test server and came up with a way that utilizes some additional internal smtp content filter forwarding, which produces some overhead. It should be light compared with the load from ClamAV and SpamAssassin, however. I'm not yet sure how amavisd-new funneling would handle multiple local recipients with different settings without passing the mail through multiple time, at least once per local user, let alone without first performing address mapping in postfix (for alias expansion). I have configured per-user SpamAssassin bayes filtering, and may introduce a whitelist based on address book entries (Roundcube.) This solution I'm currently testing will pass each message through amavisd-new one time each per local and remote recipient, and will only add the X-Original-To header to the specific local recipient each envelope is intended for. No external users will receive the header, and no local user will see which other local users (e.g. via BCC) have potentially received the same message. Flow: all mail in (both external and tls-authenticated internal) - smtp (1) - smtp-split (2) - smtp-to-me (3a) | smtp-to-external (3b) - smtp-amavis (4) - dovecot-lmtp (5) 1) I rely on default_destination_recipient_limit=1 in main.cf to split each incoming mail into one stream per recipient. 2) smtp-split will receive one stream per recipient. Default content_filter=smtp-to-me, followed by option smtpd_recipient_restrictions=permit_auth_destination,check_recipient_access,pcre:/usr/local/etc/postfix/filter-to-external.pcre,permit_mynetworks,reject means I stop processing restrictions if my server is the destination. If my server is not the destination, the FILTER in check_recipient_access will override the preceding smtp-to-me filter. Both 1) and 2) smtpd instances include option receive_override_options=no_address_mappings, to wait with mapping to internal recipient until we can add X-Original-To header for my server's users only. 3a) For mail to my server, smtp-to-me will add X-Original-To using a pcre script, in a similar fashion to step 2's filter. This step also expands the address mapping (by not specifying any receive_override_options). -o smtpd_recipient_restrictions=check_recipient_access,pcre:/usr/local/etc/postfix/recipient_access_x-orig.pcre,permit_mynetworks,reject 3b) For mail leaving my server, smtp-to-external will not add any processing besides implied expanding of the address mapping. 4) Mail is funneled through amavisd-new, once per final recipient. Mails leaving the server (sent from smtp-to-external) will be scanned by ClamV only. Mails with my server as the destination (sent from smtp-to-me) will go through ClamV, and SpamAssassin (together with per-user bayes filtering). 5) Nothing special is done here. The final destination address is sent to LMTP for delivery. Contents of /usr/local/etc/postfix/recipient_access_x-orig.pcre: /(.+)/prepend X-Original-To: $1 Contents of /usr/local/etc/postfix/filter-to-external.pcre: /^/FILTER smtp-to-external:[127.0.0.1]:port Room for improvement: Postfix seem to know the orig_to even after processing in amavisd-new, however I have yet to find a way to use this option. I can move the amavisd-new filter to before the X-Original-To header addition, however for amavisd-new to utilize per-user bayes, I currently need to do the address
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 4/28/2015 1:40 PM, Tobias Franzén lists.zx...@otaking.se wrote: On 2014-01-08 14:32, Charles Marcus wrote: On 2012-04-09 8:53 AM, Timo Sirainen t...@iki.fi wrote: On 9.4.2012, at 15.50, Charles Marcus wrote: LMTP adds a new Delivered-To:rcpt-to@address header when there is a single RCPT TO. You can force a single RCPT TO from Postfix side by setting lmtp_destination_recipient_limit=1. LMTP doesn't add/remove/change X-Original-To: header. Ok, thanks Timo... but... Are you saying that this 'Delivered-To:' header can somehow be leveraged to provide the same info as the x-original-to header? I guess X-Original-To is the same address as what Postfix sees as the original RCPT TO address before alias expansion and such? In that case, see my today's mail in Postfix list.. Hi Timo, I just tried to find your email from that day, but don't see it in the archives... Was this ever resolved (getting x-original-to support in LMTP, like it is for the LDA)? If not, since it seemed like it wasn't going to be much work, any chance you can revisit it soon? Hello, I have tried to keep tabs on the various discussions going on related to the X-Original-To header when using Dovecot LMTP. Until now I have not needed a solution, but I am now finally about to migrate my old server. Old setup: Postfix + SpamAssassin (after-queue content filter via pipe) + virtual transport, and Courier-IMAP. New setup: Postfix + amavisd-new (after-queue content filter via smtp, with ClamAV and SpamAssassin) + Dovecot LMTP, and Dovecot for IMAP. Charles, have you found a way that works for you? No, and I simply haven't switched to LMTP yet, for this and one other reason (political, not technical)... As for the rest below... wow... all I can say is, it sure would be nice if Timo/Wietse could just add the few lines of code that Timo said would be needed to properly support it natively. I was experimenting some with my test server and came up with a way that utilizes some additional internal smtp content filter forwarding, which produces some overhead. It should be light compared with the load from ClamAV and SpamAssassin, however. I'm not yet sure how amavisd-new funneling would handle multiple local recipients with different settings without passing the mail through multiple time, at least once per local user, let alone without first performing address mapping in postfix (for alias expansion). I have configured per-user SpamAssassin bayes filtering, and may introduce a whitelist based on address book entries (Roundcube.) This solution I'm currently testing will pass each message through amavisd-new one time each per local and remote recipient, and will only add the X-Original-To header to the specific local recipient each envelope is intended for. No external users will receive the header, and no local user will see which other local users (e.g. via BCC) have potentially received the same message. Flow: all mail in (both external and tls-authenticated internal) - smtp (1) - smtp-split (2) - smtp-to-me (3a) | smtp-to-external (3b) - smtp-amavis (4) - dovecot-lmtp (5) 1) I rely on default_destination_recipient_limit=1 in main.cf to split each incoming mail into one stream per recipient. 2) smtp-split will receive one stream per recipient. Default content_filter=smtp-to-me, followed by option smtpd_recipient_restrictions=permit_auth_destination,check_recipient_access,pcre:/usr/local/etc/postfix/filter-to-external.pcre,permit_mynetworks,reject means I stop processing restrictions if my server is the destination. If my server is not the destination, the FILTER in check_recipient_access will override the preceding smtp-to-me filter. Both 1) and 2) smtpd instances include option receive_override_options=no_address_mappings, to wait with mapping to internal recipient until we can add X-Original-To header for my server's users only. 3a) For mail to my server, smtp-to-me will add X-Original-To using a pcre script, in a similar fashion to step 2's filter. This step also expands the address mapping (by not specifying any receive_override_options). -o smtpd_recipient_restrictions=check_recipient_access,pcre:/usr/local/etc/postfix/recipient_access_x-orig.pcre,permit_mynetworks,reject 3b) For mail leaving my server, smtp-to-external will not add any processing besides implied expanding of the address mapping. 4) Mail is funneled through amavisd-new, once per final recipient. Mails leaving the server (sent from smtp-to-external) will be scanned by ClamV only. Mails with my server as the destination (sent from smtp-to-me) will go through ClamV, and SpamAssassin (together with per-user bayes filtering). 5) Nothing special is done here. The final destination address is sent to LMTP for delivery. Contents of /usr/local/etc/postfix/recipient_access_x-orig.pcre: /(.+)/prepend X-Original-To: $1 Contents of
Re: [Dovecot] dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database
Hello,
some config-trys later:
I have to set allow_all_users=yes in the userdb with driver=static:
|userdb {
args = home=/var/mail/%u uid=Debian-exim
gid=Debian-exim|||allow_all_users=yes|
driver = static
}|
Have a good time
Christian
||
Am 31.05.2014 17:04, schrieb Christian Hoffmann:
Hello everyone,
I have a small problem with dovecot installed on ubuntu-13.10. I use
dovcot as LDA with a LDAP-passdb and a pam-passdb. The userdb is
static. A mail to LDAP-user 'foo' is delivered with the error-message
dovecot: lda(foo): Error: User foo doesn't have home dir set,
disabling duplicate database
A mail to the pam-user 'bar' will deliverd without this error. But
both users should work with the static-userdb. Where is my mistake?
Greetings
Christian
dovecot --version
2.1.7
my dovecot.conf
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.11.0-22-generic i686 Ubuntu 13.10 ext4
disable_plaintext_auth = no
first_valid_uid = 107
last_valid_uid = 109
listen = *
log_timestamp = %Y-%m-%d %H:%M:%S
mail_home = /var/mail/%u
mail_location = maildir:/var/mail/%u/Maildir
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 ihave
passdb {
args = /etc/dovecot/dovecot-ldap.conf
driver = ldap
}
passdb {
driver = pam
}
plugin {
sieve = /var/mail/%u/dovecot.sieve
sieve_before = /etc/dovecot/sieve.global/spamfilter.sieve
}
protocols = imap pop3 sieve
service auth {
user = root
}
service managesieve-login {
inet_listener sieve {
port = 2000
}
}
ssl_cert = /etc/exim4/exim.crt
ssl_key = /etc/exim4/exim.key
syslog_facility = local0
userdb {
args = home=/var/mail/%u uid=Debian-exim gid=Debian-exim
driver = static
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
}
protocol lda {
auth_socket_path = /var/run/dovecot/auth-master
hostname = ods2.schule.de
mail_plugins = sieve
postmaster_address = postmaster
sendmail_path = /usr/sbin/sendmail
}
## my dovecot-ldap.conf
uris = ldaps://my.ldap.host.edu
dn = chief
dnpass = secret
auth_bind = yes
ldap_version = 3
base = ou=Personen,DC=my,DC=ldap,DC=host,DC=eu
scope = subtree
pass_filter =
((objectClass=user)(cn=%u)(memberOf:1.2.840.113556.1.4.1941:=cn=Mail,ou=Gruppen,DC=my,DC=ldap,DC=host,DC=eu))
[Dovecot] dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database
Hello everyone,
I have a small problem with dovecot installed on ubuntu-13.10. I use
dovcot as LDA with a LDAP-passdb and a pam-passdb. The userdb is static.
A mail to LDAP-user 'foo' is delivered with the error-message
dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling
duplicate database
A mail to the pam-user 'bar' will deliverd without this error. But both
users should work with the static-userdb. Where is my mistake?
Greetings
Christian
dovecot --version
2.1.7
my dovecot.conf
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.11.0-22-generic i686 Ubuntu 13.10 ext4
disable_plaintext_auth = no
first_valid_uid = 107
last_valid_uid = 109
listen = *
log_timestamp = %Y-%m-%d %H:%M:%S
mail_home = /var/mail/%u
mail_location = maildir:/var/mail/%u/Maildir
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 ihave
passdb {
args = /etc/dovecot/dovecot-ldap.conf
driver = ldap
}
passdb {
driver = pam
}
plugin {
sieve = /var/mail/%u/dovecot.sieve
sieve_before = /etc/dovecot/sieve.global/spamfilter.sieve
}
protocols = imap pop3 sieve
service auth {
user = root
}
service managesieve-login {
inet_listener sieve {
port = 2000
}
}
ssl_cert = /etc/exim4/exim.crt
ssl_key = /etc/exim4/exim.key
syslog_facility = local0
userdb {
args = home=/var/mail/%u uid=Debian-exim gid=Debian-exim
driver = static
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
}
protocol lda {
auth_socket_path = /var/run/dovecot/auth-master
hostname = ods2.schule.de
mail_plugins = sieve
postmaster_address = postmaster
sendmail_path = /usr/sbin/sendmail
}
## my dovecot-ldap.conf
uris = ldaps://my.ldap.host.edu
dn = chief
dnpass = secret
auth_bind = yes
ldap_version = 3
base = ou=Personen,DC=my,DC=ldap,DC=host,DC=eu
scope = subtree
pass_filter =
((objectClass=user)(cn=%u)(memberOf:1.2.840.113556.1.4.1941:=cn=Mail,ou=Gruppen,DC=my,DC=ldap,DC=host,DC=eu))
Re: [Dovecot] dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database
On 05/31/2014 03:04 PM Christian Hoffmann wrote: Hello everyone, I have a small problem with dovecot installed on ubuntu-13.10. I use dovcot as LDA with a LDAP-passdb and a pam-passdb. The userdb is static. A mail to LDAP-user 'foo' is delivered with the error-message dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database Your LDAP based userdb doesn't return the home directory for user foo. The LDAP lookup should return the home directory. See http://wiki2.dovecot.org/UserDatabase And even for virtual users you should have a home directory for each virtual user. See http://wiki2.dovecot.org/VirtualUsers/Home A mail to the pam-user 'bar' will deliverd without this error. But both users should work with the static-userdb. Where is my mistake? Because the userdb returns the home directory of the system user bar. Regards, Pascal -- The trapper recommends today: c01dcofe.1415...@localdomain.org
Re: [Dovecot] dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database
Hello Pascal, but I didn't configure a userdb with driver=ldap. There is only one userdb with driver=static and I assumed, that every user gets the same uid, gid and a valid home directory. Are there some circumstances, that different passdb-drivers treated in special relation to userdb-drivers? Like, one have to configure a userdb-driver=ldap if one uses a passdb-driver=ldap. But the passdb-driver=pam looks into userdb-driver=static. That is the part, I do not understand. Greetings Christian Am 31.05.2014 19:12, schrieb Pascal Volk: On 05/31/2014 03:04 PM Christian Hoffmann wrote: Hello everyone, I have a small problem with dovecot installed on ubuntu-13.10. I use dovcot as LDA with a LDAP-passdb and a pam-passdb. The userdb is static. A mail to LDAP-user 'foo' is delivered with the error-message dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database Your LDAP based userdb doesn't return the home directory for user foo. The LDAP lookup should return the home directory. See http://wiki2.dovecot.org/UserDatabase And even for virtual users you should have a home directory for each virtual user. See http://wiki2.dovecot.org/VirtualUsers/Home A mail to the pam-user 'bar' will deliverd without this error. But both users should work with the static-userdb. Where is my mistake? Because the userdb returns the home directory of the system user bar. Regards, Pascal
Re: [Dovecot] dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database
On 05/31/2014 05:35 PM Christian Hoffmann wrote: Hello Pascal, but I didn't configure a userdb with driver=ldap. There is only one userdb with driver=static and I assumed, that every user gets the same uid, gid and a valid home directory. Are there some circumstances, that different passdb-drivers treated in special relation to userdb-drivers? Like, one have to configure a userdb-driver=ldap if one uses a passdb-driver=ldap. But the passdb-driver=pam looks into userdb-driver=static. That is the part, I do not understand. [*ToFu*] What is the output of commands `doveadm user -f home foo` and `doveadm user -f home bar`? Regards, Pascal -- The trapper recommends today: c01dcofe.1415...@localdomain.org
Re: [Dovecot] dovecot: lda(foo): Error: User foo doesn't have home dir set, disabling duplicate database
Am 31.05.2014 19:50, schrieb Pascal Volk: On 05/31/2014 05:35 PM Christian Hoffmann wrote: Hello Pascal, but I didn't configure a userdb with driver=ldap. There is only one userdb with driver=static and I assumed, that every user gets the same uid, gid and a valid home directory. Are there some circumstances, that different passdb-drivers treated in special relation to userdb-drivers? Like, one have to configure a userdb-driver=ldap if one uses a passdb-driver=ldap. But the passdb-driver=pam looks into userdb-driver=static. That is the part, I do not understand. [*ToFu*] What is the output of commands `doveadm user -f home foo` and `doveadm user -f home bar`? Regards, Pascal Here it is: root@ods2:~# doveadm user -f home foo doveadm(root): Error: user foo: Auth USER lookup failed doveadm(root): Error: userdb lookup failed for foo root@ods2:~# doveadm user -f home bar doveadm(root): Error: user bar: Auth USER lookup failed doveadm(root): Error: userdb lookup failed for bar Greetings Christian
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2012-04-09 8:53 AM, Timo Sirainen t...@iki.fi wrote: On 9.4.2012, at 15.50, Charles Marcus wrote: LMTP adds a new Delivered-To:rcpt-to@address header when there is a single RCPT TO. You can force a single RCPT TO from Postfix side by setting lmtp_destination_recipient_limit=1. LMTP doesn't add/remove/change X-Original-To: header. Ok, thanks Timo... but... Are you saying that this 'Delivered-To:' header can somehow be leveraged to provide the same info as the x-original-to header? I guess X-Original-To is the same address as what Postfix sees as the original RCPT TO address before alias expansion and such? In that case, see my today's mail in Postfix list.. Hi Timo, I just tried to find your email from that day, but don't see it in the archives... Was this ever resolved (getting x-original-to support in LMTP, like it is for the LDA)? If not, since it seemed like it wasn't going to be much work, any chance you can revisit it soon? Thanks, -- Best regards, Charles
Re: [Dovecot] Dovecot LDA
On 23 Aug 2013, at 18:19 , Pascal Volk user+dove...@localhost.localdomain.org wrote: On 08/24/2013 02:12 AM LuKreme wrote: OK, I did read http://wiki2.dovecot.org/LDA but it doesn't answer the question I have since it doesn't tell me what I can do with -o, exactly. -o is used to override settings, as documented in dovecot-lda(1)/http://wiki2.dovecot.org/Tools/DovecotLDA What I would like to do is be able to call dovecot-lda and pass along '\\Seen', is that possible? That requires Sieve, see http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#line-59 for an example. So would I be able to call dovecot-lda with the name of the sieve file I want (one which just applies \\Seen to the message in question). Could I also pass the name of the maildir I wanted the message in? Basically, I do all my sorting in procmail, but the method for marking messages in procmail as seen is... well, it's a kludge. It it is possible for me to do something like |dovecot-lda -o mail_location=/path/to/my/Maildir/.listname -o sieve=/path/to/markread.sieve that would be great. This page http://wiki.dovecot.org/LDA/Sieve/Dovecot does not have a s.x equivalent, so I am guessing nothing has changed. That says that I have to use dovecot-lda as my LDA in order to invoke sieve, could I just add mail_plugins=sieve to that dovecot-lda line above? -- I WILL NOT BARF UNLESS I'M SICK Bart chalkboard Ep. 8F15
[Dovecot] Dovecot LDA
OK, I did read http://wiki2.dovecot.org/LDA but it doesn't answer the question I have since it doesn't tell me what I can do with -o, exactly. What I would like to do is be able to call dovecot-lda and pass along '\\Seen', is that possible? -- Up the airy mountains, down the rushy glen... From ghosties and bogles and long-leggity beasties... My mother said I never should... We dare not go a-hunting for fear... And things that go bump... Play with the fairies in the wood... --Lords and Ladies
Re: [Dovecot] Dovecot LDA
On 08/24/2013 02:12 AM LuKreme wrote: OK, I did read http://wiki2.dovecot.org/LDA but it doesn't answer the question I have since it doesn't tell me what I can do with -o, exactly. -o is used to override settings, as documented in dovecot-lda(1)/http://wiki2.dovecot.org/Tools/DovecotLDA What I would like to do is be able to call dovecot-lda and pass along '\\Seen', is that possible? That requires Sieve, see http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#line-59 for an example. Regards, Pascal -- The trapper recommends today: cafebabe.1323...@localdomain.org
Re: [Dovecot] execvp /usr/local/libexec/dovecot/dovecot-lda: Permission denied
Hi,
Can you help me?
Because my config in master.cf is:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d
${user}@${nexthop}
But now I have this problem in my postfix, logs:
fatal destination user parameter (-d user) not given
It´s funny because, this problem occur only in my domain, no to external
domains.
Before I was with this problem with permissions, I solved, but now happen
this.
Thanks.
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/execvp-usr-local-libexec-dovecot-dovecot-lda-Permission-denied-tp9592p43797.html
Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] execvp /usr/local/libexec/dovecot/dovecot-lda: Permission denied
Hi Edward Carraro, I see you got your goal. So I have same trouble and don´t solved. I used the three scenarios you used. based in http://wiki.dovecot.org/LDA/%VirtualUsers And tried using the lmtp, but too don´t worked to delivery mail, I use dovecot-lda to sieve plugin work. Please help me. See the logs: mail postfix/local[14324]: 45FCB12E89: to=te...@foobar.br, relay=local, delay=1785, delays=1785/0.05/0/0.12, dsn=4.3.0, status=deferred (temporary failure. Command output: local: fatal: execvp /usr/libexec/dovecot/deliver: Permission denied) Thanks. -- View this message in context: http://dovecot.2317879.n4.nabble.com/execvp-usr-local-libexec-dovecot-dovecot-lda-Permission-denied-tp9592p43756.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] execvp /usr/local/libexec/dovecot/dovecot-lda: Permission denied
Le 7 août 2013 à 16:32, will moura a écrit : Hi Edward Carraro, I see you got your goal. So I have same trouble and don´t solved. I used the three scenarios you used. based in http://wiki.dovecot.org/LDA/%VirtualUsers And tried using the lmtp, but too don´t worked to delivery mail, I use dovecot-lda to sieve plugin work. Please help me. See the logs: mail postfix/local[14324]: 45FCB12E89: to=te...@foobar.br, relay=local, delay=1785, delays=1785/0.05/0/0.12, dsn=4.3.0, status=deferred (temporary failure. Command output: local: fatal: execvp /usr/libexec/dovecot/deliver: Permission denied) Thanks. Hello Will, Are you cross-posting without knowing it? As far as I'm concerned, I'm unable to find any previous related email on this list; and the above sure is insufficient for anyone on this list to be of some help... Could you re-state your trouble for the sake of all of us? :-) Axel
Re: [Dovecot] dovecot-lda not logging if dovecot runs under daemontools
On Fri Jul 26 12:49:08 2013, Roberto Puzzanghera wrote: I have dovecot running under daemontools and I can't see dovecot-lda in action when I read the logs. I've set the logs to /dev/stderr because daemontools redirects /dev/stderr to /var/log/dovecot/current. Dovecot-lda runs under qmail, so you'll find the output in qmail's logs. If you run, say, doveadm manually, the output will be on your terminal. Yours Jost Krieger -- | jost.krieger+...@ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machineat RUB Comp. Center | | Sincere words are not sweet, sweet words are not sincere.| | Lao Tse, Tao Te King 81 |
Re: [Dovecot] dovecot-lda not logging if dovecot runs under daemontools
On Fri Jul 26 14:51:30 2013, Roberto Puzzanghera wrote: Hi Jost, thanks for your reply. Il 26.07.2013 13:11 Jost Krieger ha scritto: Dovecot-lda runs under qmail, so you'll find the output in qmail's logs. If you run, say, doveadm manually, the output will be on your terminal. I didn't explain myself very well. The qmail's log /var/log/dovecot/current doesn't show the lda output as expected. I That's dovecot's log, not qmail's. see onlythe output of imap and pop3. Anyway, running dovecot manually or as daemon in the normal way (without daemontools) show the lda output in the log. You are logging to stderr, in the delivery case that means qmail-local's output. This is somewhere in a place like /var/qmal/logs/qmail/current and looks similar to @400051f793e218f78c54 delivery 847552: success: lda():_Info:_msgid=20130730102215.ecb4880...@carlos.noc.ruhr-uni-bochum.de:_saved_mail_to_NOC-Order/did_0+0+1/ Yours Jost Krieger -- | jost.krieger+...@ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machineat RUB Comp. Center | | Sincere words are not sweet, sweet words are not sincere.| | Lao Tse, Tao Te King 81 |
Re: [Dovecot] dovecot-lda not logging if dovecot runs under daemontools
Thank you, Jost. The lda output is actually logged on qmail-send's log regards, Roberto Puzzanghera Il 30.07.2013 12:35 Jost Krieger ha scritto: On Fri Jul 26 14:51:30 2013, Roberto Puzzanghera wrote: Hi Jost, thanks for your reply. Il 26.07.2013 13:11 Jost Krieger ha scritto: Dovecot-lda runs under qmail, so you'll find the output in qmail's logs. If you run, say, doveadm manually, the output will be on your terminal. I didn't explain myself very well. The qmail's log /var/log/dovecot/current doesn't show the lda output as expected. I That's dovecot's log, not qmail's. see onlythe output of imap and pop3. Anyway, running dovecot manually or as daemon in the normal way (without daemontools) show the lda output in the log. You are logging to stderr, in the delivery case that means qmail-local's output. This is somewhere in a place like /var/qmal/logs/qmail/current and looks similar to @400051f793e218f78c54 delivery 847552: success: lda():_Info:_msgid=20130730102215.ecb4880...@carlos.noc.ruhr-uni-bochum.de:_saved_mail_to_NOC-Order/did_0+0+1/ Yours Jost Krieger
[Dovecot] dovecot-lda not logging if dovecot runs under daemontools
Hello all,
I have dovecot running under daemontools and I can't see dovecot-lda in
action when I read the logs. I've set the logs to /dev/stderr because
daemontools redirects /dev/stderr to /var/log/dovecot/current.
The dovecot server works fine and I know that dovecot-lda is actually
doing the delivery, because the sieve facility is working as well. I can
get lda log working -but only on syslog- if I override the log_path in
this way:
protocol lda {
mail_plugins = $mail_plugins sieve
log_path =
}
I'm calling dovecot-lda in the usual qmail way. This is my
.qmail-default:
|/var/qmail/bin/preline -f /usr/libexec/dovecot/deliver -d $EXT@$USER
As running dovecot under daemontools seems to be a common practice among
qmail users, could any of you give me an hint on how dovecot should be
configured to achieve the purpose?
Thanks in advance.
My doveconf follows
Roberto Puzzanghera
# dovecof -n
# 2.2.4: /etc/dovecot/dovecot/dovecot.conf
# OS: Linux 3.2.29-smp i686 Slackware 14.0
auth_default_realm = mydomain.net
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
auth_verbose = yes
default_login_user = vpopmail
disable_plaintext_auth = no
first_valid_gid = 89
first_valid_uid = 89
last_valid_gid = 89
last_valid_uid = 89
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
log_path = /dev/stderr
mail_access_groups = 89
mail_debug = yes
mail_gid = 89
mail_location = maildir:%h/Maildir
mail_plugins = quota mail_log notify
mail_privileged_group = 89
mail_uid = 89
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 ihave spamtest spamtestplus
namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot/conf.d/dovecot-sql.conf.ext
driver = sql
}
plugin {
autocreate = Sent
autocreate2 = Drafts
autocreate3 = Junk
autocreate4 = Trash
autosubscribe = Sent
autosubscribe2 = Drafts
autosubscribe3 = Junk
autosubscribe4 = Trash
mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
mail_log_fields = uid box msgid size
quota = maildir:User quota
sieve = ~/sieve/dovecot.sieve
sieve_before = /etc/dovecot/sieve/
sieve_dir = ~/sieve
sieve_extensions = +spamtest +spamtestplus +relational
+comparator-i;ascii-numeric
}
postmaster_address = postmaster@%d
protocols = imap pop3 sieve
sendmail_path = /var/qmail/bin/sendmail
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener auth-userdb {
group = vchkpw
mode = 0600
user = vpopmail
}
user = $default_internal_user
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
service_count = 1
vsz_limit = 64 M
}
ssl_cert = /etc/dovecot/ssl/certs/dovecot.pem
ssl_key = /etc/dovecot/ssl/private/dovecot.pem
userdb {
args = /etc/dovecot/dovecot/conf.d/dovecot-sql.conf.ext
driver = sql
}
verbose_ssl = yes
protocol lda {
mail_plugins = quota mail_log notify sieve
}
protocol imap {
mail_plugins = quota mail_log notify imap_quota
}
protocol pop3 {
mail_plugins = quota mail_log notify
}
[Dovecot] dovecot-lda - dovecot: quota-warning: Error: lda: Fatal: Unknown argument
Hi, everyone, I'm attempting to configure automated quota warnings for users and have hit a snag. The script I'm using is as follows: - #!/bin/sh PERCENT=$1 MAILBOX=$2 DOMAIN=$3 cat EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o plugin/quota=dict:user::file:/var/vmail/%d/%n/.quotausage From: postmaster@$DOMAIN Subject: Email quota warning - mailbox over $PERCENT% full [...] - When the script is triggered, here's what appears in the log: - Jun 24 11:16:53 host dovecot: quota-warning: Error: lda: Fatal: Unknown argument: plugin/quota=dict:user::noenforcing:file:/var/vmail/%d/%n/.quotausage Jun 24 11:16:53 host dovecot: master: Error: service(quota-warning): child 22415 returned error 64 - If I paste the same on the command line, the message is delivered, as expected: /usr/lib/dovecot/dovecot-lda -d u...@example.com -o plugin/quota=dict:user::noenforcing:file:/var/vmail/%d/%n/.quotausage -p /tmp/test.txt The problem seems to be that the -o switch isn't being interpreted correctly when dovecot-lda is called from within the script. -o is the correct switch, yes? From the manual at http://wiki2.dovecot.org/LDA : -o name=value: Override a setting from dovecot.conf. You can give this parameter multiple times. What am I missing here? Is some shell script escaping or similar required? Thanks for any tips! -Ben
Re: [Dovecot] dovecot-lda - dovecot: quota-warning: Error: lda: Fatal: Unknown argument
On 6/24/2013 11:59 AM, Ben Johnson wrote: Hi, everyone, I'm attempting to configure automated quota warnings for users and have hit a snag. The script I'm using is as follows: - #!/bin/sh PERCENT=$1 MAILBOX=$2 DOMAIN=$3 cat EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o plugin/quota=dict:user::file:/var/vmail/%d/%n/.quotausage From: postmaster@$DOMAIN Subject: Email quota warning - mailbox over $PERCENT% full [...] - When the script is triggered, here's what appears in the log: - Jun 24 11:16:53 host dovecot: quota-warning: Error: lda: Fatal: Unknown argument: plugin/quota=dict:user::noenforcing:file:/var/vmail/%d/%n/.quotausage Jun 24 11:16:53 host dovecot: master: Error: service(quota-warning): child 22415 returned error 64 - If I paste the same on the command line, the message is delivered, as expected: /usr/lib/dovecot/dovecot-lda -d u...@example.com -o plugin/quota=dict:user::noenforcing:file:/var/vmail/%d/%n/.quotausage -p /tmp/test.txt The problem seems to be that the -o switch isn't being interpreted correctly when dovecot-lda is called from within the script. -o is the correct switch, yes? From the manual at http://wiki2.dovecot.org/LDA : -o name=value: Override a setting from dovecot.conf. You can give this parameter multiple times. What am I missing here? Is some shell script escaping or similar required? Thanks for any tips! -Ben I figured it out; I had copy/pasted part of the line cat EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o \ plugin/quota=dict:user::file:/var/vmail/%d/%n/.quotausage from the documentation example and in so doing I neglected to use the correct variable name for the user/mailbox. In the documentation example, the variable is $USER, whereas I had named it $MAILBOX. This was causing the mailbox/user to be evaluated as an empty string (or null). Everything works as expected using the correct variable name. Oops! -Ben
Re: [Dovecot] Dovecot LDA LDAP lookups on samba4 server ends very often in timeouts (Christian Wiese)
Dear Christian thank you very much - you got it at the very first shot: modified /etc/ openldap/ldap.conf adding REFERRALS off en everything works without issues now many thanks Marco Carcano
[Dovecot] Dovecot LDA LDAP lookups on samba4 server ends very often in timeouts
I hope that someone will be so kind to help me into solving this really strange thing (don't know if it is a bug or not) I have a samba4 server and want to use postfix+dovecot - dovecot version is 2.0.11 as for the postfix side everything is OK (all the LDAP lookups works without any error, tested also manually with postmap -q) the real pain is with dovecot deliver: it seems that sometimes lda tries to lookup to the LDPA (samba 4) server, got a reply, an then report(after 2 minutes) a lookup timeout error the really strange thing is that (very seldom) lda works, but most of the times I got the timeout error. The strange thing is that if I use ldapsearch I never got timeout neither late replies, and even postfix performs its lookups without any issue it seems something related to lda itself (I do not know if I have a wrong configuration, but I think this is not a configuration issue, otherwise it should not work at all) here are the information logged when it does not work - after this log you will find the one when I got the failure (if needed I can provide a .pcap file too) (trailing and leading spaces of AT charcater has been added by me) ## FAULTY DELIVER LOG # Feb 20 12:20:50 sng02 postfix/smtpd[8928]: connect from localhost[127.0.0.1] Feb 20 12:21:14 sng02 postfix/smtpd[8928]: A38D4407F5: client=localhost[127.0.0.1] Feb 20 12:21:20 sng02 postfix/cleanup[8891]: A38D4407F5: warning: header Subject: prova from localhost[127.0.0.1]; from=marco @ senderdomain.tld to=mac @ mydomain.com proto=SMTP helo=senderdomain.tld Feb 20 12:21:20 sng02 postfix/cleanup[8891]: A38D4407F5: message-id=20130220112114.A38D4407F5 @ srv01.mydomain.local Feb 20 12:21:20 sng02 postfix/qmgr[8889]: A38D4407F5: from=marco @ senderdomain.tld, size=371, nrcpt=1 (queue active) Feb 20 12:21:20 sng02 dovecot: lda: Debug: Loading modules from directory: /usr/lib64/dovecot Feb 20 12:21:20 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Feb 20 12:21:20 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib20_expire_plugin.so Feb 20 12:21:20 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_bind Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_simple_bind Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_sasl_bind Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_send_initial_request Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_new_connection 1 1 0 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_int_open_connection Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_connect_to_host: TCP localhost:389 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_new_socket: 16 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_prepare_socket: 16 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_connect_to_host: Trying ::1 389 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_pvt_connect: fd: 16 tm: -1 async: 0 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_open_defconn: successful Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_send_server_request Feb 20 12:21:20 sng02 dovecot: auth: Debug: master in: USER#0111#011marco.carcano#011service=lda Feb 20 12:21:20 sng02 dovecot: auth: Debug: password(marco.carcano): passdb doesn't support credential lookups Feb 20 12:21:20 sng02 dovecot: auth: Error: static(marco.carcano): passdb doesn't support lookups, can't verify user's existence Feb 20 12:21:20 sng02 dovecot: auth: Debug: ldap(marco.carcano): user search: base=DC=mydomain,DC=local scope=subtree filter=(sAMAccountname=marco.carcano) fields=Mailbox,dovecotMailQuota Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_result ld 0x6cba60 msgid -1 Feb 20 12:21:20 sng02 dovecot: auth: Error: wait4msg ld 0x6cba60 msgid -1 (timeout 0 usec) Feb 20 12:21:20 sng02 dovecot: auth: Error: wait4msg continue ld 0x6cba60 msgid -1 all 0 Feb 20 12:21:20 sng02 dovecot: auth: Error: ** ld 0x6cba60 Connections: Feb 20 12:21:20 sng02 dovecot: auth: Error: * host: localhost port: 389 (default) Feb 20 12:21:20 sng02 dovecot: auth: Error: refcnt: 2 status: Connected Feb 20 12:21:20 sng02 dovecot: auth: Error: last used: Wed Feb 20 12:21:20 2013 Feb 20 12:21:20 sng02 dovecot: auth: Error: Feb 20 12:21:20 sng02 dovecot:
Re: [Dovecot] Dovecot LDA LDAP lookups on samba4 server ends very often in timeouts
just to complete the informations of this thread, here is the log of a mail delivered succesfully (trailing and leading spaces of AT charcater has been added by me) ## MAIL SUCCEFFULLY DELIVERED LOG # Feb 19 17:41:01 sng02 postfix/smtpd[4006]: connect from localhost[127.0.0.1] Feb 19 17:41:28 sng02 postfix/smtpd[4006]: 95659407F5: client=localhost[127.0.0.1] Feb 19 17:41:36 sng02 postfix/cleanup[4011]: 95659407F5: warning: header Subject: prova from localhost[127.0.0.1]; from=marco @ senderdomain.tld to=mac @ mydomain.com proto=SMTP helo=senderdomain.tld Feb 19 17:41:36 sng02 postfix/cleanup[4011]: 95659407F5: message-id=20130219164128.95659407F5 @ srv01.mydomain.local Feb 19 17:41:36 sng02 postfix/qmgr[3992]: 95659407F5: from=marco @ senderdomain.tld, size=371, nrcpt=1 (queue active) Feb 19 17:41:36 sng02 dovecot: lda: Debug: Loading modules from directory: /usr/lib64/dovecot Feb 19 17:41:36 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Feb 19 17:41:36 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib20_expire_plugin.so Feb 19 17:41:36 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Feb 19 17:41:36 sng02 dovecot: auth: Debug: master in: USER#0111#011marco.carcano#011service=lda Feb 19 17:41:36 sng02 dovecot: auth: Debug: password(marco.carcano): passdb doesn't support credential lookups Feb 19 17:41:36 sng02 dovecot: auth: Error: static(marco.carcano): passdb doesn't support lookups, can't verify user's existence Feb 19 17:41:36 sng02 dovecot: auth: Debug: ldap(marco.carcano): user search: base=DC=mydomain,DC=local scope=subtree filter=(sAMAccountname=marco.carcano) fields=Mailbox,dovecotMailQuota Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap(marco.carcano): Connection appears to be hanging, reconnecting Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_unbind Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_free_request (origid 2, msgid 3) Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_free_request (origid 2, msgid 2) Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_free_connection 1 1 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_send_unbind Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_free_connection: actually freed Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_free_connection 1 1 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_send_unbind Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_free_connection: actually freed Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_create Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_bind Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_simple_bind Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_sasl_bind Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_send_initial_request Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_new_connection 1 1 0 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_int_open_connection Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_connect_to_host: TCP localhost:389 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_new_socket: 16 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_prepare_socket: 16 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_connect_to_host: Trying ::1 389 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_pvt_connect: fd: 16 tm: -1 async: 0 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_open_defconn: successful Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_send_server_request Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_result ld 0x666a60 msgid -1 Feb 19 17:41:36 sng02 dovecot: auth: Error: wait4msg ld 0x666a60 msgid -1 (timeout 0 usec) Feb 19 17:41:36 sng02 dovecot: auth: Error: wait4msg continue ld 0x666a60 msgid -1 all 0 Feb 19 17:41:36 sng02 dovecot: auth: Error: ** ld 0x666a60 Connections: Feb 19 17:41:36 sng02 dovecot: auth: Error: * host: localhost port: 389 (default) Feb 19 17:41:36 sng02 dovecot: auth: Error: refcnt: 2 status: Connected Feb 19 17:41:36 sng02 dovecot: auth: Error: last used: Tue Feb 19 17:41:36 2013 Feb 19 17:41:36 sng02 dovecot: auth: Error: Feb 19 17:41:36 sng02 dovecot: auth: Error: Feb 19 17:41:36 sng02 dovecot: auth: Error: ** ld 0x666a60 Outstanding Requests: Feb 19 17:41:36 sng02 dovecot: auth: Error: * msgid 1, origid 1, status InProgress Feb 19 17:41:36 sng02 dovecot: auth: Error:outstanding referrals 0, parent count 0 Feb 19 17:41:36 sng02 dovecot: auth: Error: ld 0x666a60 request count 1 (abandoned 0) Feb 19 17:41:36 sng02 dovecot: auth: Error: ** ld 0x666a60 Response Queue: Feb 19 17:41:36 sng02 dovecot: auth: Error:Empty Feb 19 17:41:36 sng02 dovecot: auth: Error: ld 0x666a60 response count 0 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_chkResponseList ld 0x666a60 msgid -1 all 0 Feb 19 17:41:36 sng02 dovecot: auth: Error: ldap_chkResponseList returns ld 0x666a60 NULL Feb 19 17:41:36 sng02 dovecot: auth: Error:
Re: [Dovecot] Dovecot LDA LDAP lookups on samba4 server ends very often in timeouts
Hi Marco, try to check if LDAP REFERRALS are enabled. I had a similar issue some time ago when trying to authenticate against an AD, which didn't worked (long timeouts) as long as I switched off REFERRALS in the systems ldap.conf. (more info you might get by 'man ldap.conf') Cheers, Chris Am Wed, 20 Feb 2013 13:25:39 +0100 schrieb ma...@carcano.ch: I hope that someone will be so kind to help me into solving this really strange thing (don't know if it is a bug or not) I have a samba4 server and want to use postfix+dovecot - dovecot version is 2.0.11 as for the postfix side everything is OK (all the LDAP lookups works without any error, tested also manually with postmap -q) the real pain is with dovecot deliver: it seems that sometimes lda tries to lookup to the LDPA (samba 4) server, got a reply, an then report(after 2 minutes) a lookup timeout error the really strange thing is that (very seldom) lda works, but most of the times I got the timeout error. The strange thing is that if I use ldapsearch I never got timeout neither late replies, and even postfix performs its lookups without any issue it seems something related to lda itself (I do not know if I have a wrong configuration, but I think this is not a configuration issue, otherwise it should not work at all) here are the information logged when it does not work - after this log you will find the one when I got the failure (if needed I can provide a .pcap file too) (trailing and leading spaces of AT charcater has been added by me) ## FAULTY DELIVER LOG # Feb 20 12:20:50 sng02 postfix/smtpd[8928]: connect from localhost[127.0.0.1] Feb 20 12:21:14 sng02 postfix/smtpd[8928]: A38D4407F5: client=localhost[127.0.0.1] Feb 20 12:21:20 sng02 postfix/cleanup[8891]: A38D4407F5: warning: header Subject: prova from localhost[127.0.0.1]; from=marco @ senderdomain.tld to=mac @ mydomain.com proto=SMTP helo=senderdomain.tld Feb 20 12:21:20 sng02 postfix/cleanup[8891]: A38D4407F5: message-id=20130220112114.A38D4407F5 @ srv01.mydomain.local Feb 20 12:21:20 sng02 postfix/qmgr[8889]: A38D4407F5: from=marco @ senderdomain.tld, size=371, nrcpt=1 (queue active) Feb 20 12:21:20 sng02 dovecot: lda: Debug: Loading modules from directory: /usr/lib64/dovecot Feb 20 12:21:20 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Feb 20 12:21:20 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib20_expire_plugin.so Feb 20 12:21:20 sng02 dovecot: lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Feb 20 12:21:20 sng02 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_bind Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_simple_bind Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_sasl_bind Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_send_initial_request Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_new_connection 1 1 0 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_int_open_connection Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_connect_to_host: TCP localhost:389 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_new_socket: 16 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_prepare_socket: 16 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_connect_to_host: Trying ::1 389 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_pvt_connect: fd: 16 tm: -1 async: 0 Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_open_defconn: successful Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_send_server_request Feb 20 12:21:20 sng02 dovecot: auth: Debug: master in: USER#0111#011marco.carcano#011service=lda Feb 20 12:21:20 sng02 dovecot: auth: Debug: password(marco.carcano): passdb doesn't support credential lookups Feb 20 12:21:20 sng02 dovecot: auth: Error: static(marco.carcano): passdb doesn't support lookups, can't verify user's existence Feb 20 12:21:20 sng02 dovecot: auth: Debug: ldap(marco.carcano): user search: base=DC=mydomain,DC=local scope=subtree filter=(sAMAccountname=marco.carcano) fields=Mailbox,dovecotMailQuota Feb 20 12:21:20 sng02 dovecot: auth: Error: ldap_result ld 0x6cba60 msgid -1 Feb 20 12:21:20 sng02 dovecot: auth: Error: wait4msg ld 0x6cba60 msgid -1 (timeout 0 usec) Feb 20 12:21:20 sng02 dovecot: auth: Error:
Re: [Dovecot] dovecot-lda (2.1.12) segfaults
Timo Sirainen writes:
Can you still reproduce this in any way?
Yes, I have 6 sets of user INBOX index caches that will crash dovecot-lda.
The actual content of the INBOX is irrelevant (crash probably happens
before INBOX is opened).
I found two bugs, would be nice to know if they solve it:
http://hg.dovecot.org/dovecot-2.1/rev/2f848393f78e
http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9
No, these patch don't help. It crashes in the same place with the
same value of field_hdr. Here's the full backtrace:
#0 0xff2a0474 in mail_cache_header_fields_read (cache=0x5c250) at
mail-cache-fields.c:325
field_hdr = (const struct mail_cache_header_fields *) 0x20
field = {name = 0x402 Address 0x402 out of bounds, idx = 4282351288,
type = MAIL_CACHE_FIELD_VARIABLE_SIZE, field_size = 4282335628,
decision = MAIL_CACHE_DECISION_TEMP, last_used = -14558816}
last_used = (const uint32_t *) 0x64584
sizes = (const uint32_t *) 0xc
types = (const uint8_t *) 0x64888
decisions = (const uint8_t *) 0x64900
p = 0x24a38 ?\035\212@
names = 0x0
end = 0x64a50
orig_key = (void *) 0xffbfee38
orig_value = (void *) 0x64550
fidx = 411784
new_fields_count = 4280126016
dec = MAIL_CACHE_DECISION_NO
max_drop_time = 376804
offset = 32
i = 4282348464
#1 0xff29e8cc in mail_cache_compress_locked (cache=0x5c250, trans=0x645e0,
unlock=0xffbfeeef)
at mail-cache-compress.c:361
dotlock = (struct dotlock *) 0x2ea00
st = {st_dev = 235718347, st_pad1 = {874, 0, 0}, st_ino = 0, st_mode =
0, st_nlink = 0,
st_uid = 0, st_gid = 0, st_rdev = 3720, st_pad2 = {0, 0}, st_size = 3720,
st_atim = {
tv_sec = 410816, tv_nsec = -12631336}, st_mtim = {tv_sec = 514, tv_nsec =
-12631336},
st_ctim = {tv_sec = 65536, tv_nsec = 0}, st_blksize = 0, st_blocks =
1621028016851520,
st_fstype = \000\000\000\004\000\000\000\003\212\000\000\000\000\005?P,
st_pad4 = {-4198784,
-14028952, 39394339, 377424, 0, 16777216, 3, 4}}
old_mask = 4282348464
file_seq = 4
old_offset = 4290768372
ext_offsets = {arr = {buffer = 0xffbfee10, element_size = 4280930288},
v = 0xffbfee10,
v_modifiable = 0xffbfee10}
offsets = (const uint32_t *) 0x0
data = (const void *) 0xff3f4380
i = 0
count = 1
fd = 0
ret = 377424
#2 0xff29efe0 in mail_cache_compress (cache=0x5c250, trans=0x645e0) at
mail-cache-compress.c:489
unlock = false
ret = 411764
__FUNCTION__ = mail_cache_compress
#3 0xff2a3e28 in mail_cache_transaction_compress (ctx=0x5e3b8) at
mail-cache-transaction.c:180
cache = (struct mail_cache *) 0x5c250
view = (struct mail_index_view *) 0x644c0
trans = (struct mail_index_transaction *) 0x645e0
ret = 2424
#4 0xff2a40b8 in mail_cache_transaction_open_if_needed (ctx=0x5e3b8)
at mail-cache-transaction.c:241
cache = (struct mail_cache *) 0x5c250
ext = (const struct mail_index_ext *) 0x1e
idx = 154968
i = 1
__FUNCTION__ = mail_cache_transaction_open_if_needed
#5 0xff2a6e94 in mail_cache_field_want_add (ctx=0x5e3b8, seq=1, field_idx=12)
at mail-cache-transaction.c:1048
decision = 153968
#6 0xff27e8e8 in index_mail_parse_header_register_all_wanted (mail=0x5efa8)
at index-mail-headers.c:175
_mail = (struct mail *) 0x5efa8
all_cache_fields = (const struct mail_cache_field *) 0x25970
i = 12
count = 26
#7 0xff27ec90 in index_mail_parse_header_init (mail=0x5efa8, headers=0x0)
at index-mail-headers.c:230
_data_stack_cur_id = 2
data = (struct index_mail_data *) 0x5f058
match = (const uint8_t *) 0x641a0
i = 0
field_idx = 4290769328
match_count = 2155905152
__FUNCTION__ = index_mail_parse_header_init
#8 0xff27f5c8 in index_mail_cache_parse_init (_mail=0x5efa8, input=0x64058)
at index-mail-headers.c:376
mail = (struct index_mail *) 0x5efa8
input2 = (struct istream *) 0x641a0
__FUNCTION__ = index_mail_cache_parse_init
#9 0xff2299cc in mbox_save_get_input_stream (ctx=0x5e6e0, input=0x637c8) at
mbox-save.c:411
filter = (struct istream *) 0x0
ret = (struct istream *) 0x5edd0
cache_input = (struct istream *) 0x25990
streams = {0x20202020, 0x2e938, 0xa202020}
#10 0xff22a084 in mbox_save_begin (_ctx=0x5e6e0, input=0x637c8) at
mbox-save.c:520
ctx = (struct mbox_save_context *) 0x5e6e0
t = (struct mbox_transaction_context *) 0x5de88
save_flags = MAIL_RECENT
offset = 0
__FUNCTION__ = mbox_save_begin
#11 0xff24e9c0 in mailbox_save_begin (ctx=0xffbff514, input=0x637c8) at
mail-storage.c:1652
box = (struct mailbox *) 0x594e8
ret = 0
#12 0xff23f138 in mail_storage_try_copy (_ctx=0xffbff514, mail=0x54cd8) at
mail-copy.c:68
Re: [Dovecot] dovecot-lda (2.1.12) segfaults
On 19.12.2012, at 12.47, Joseph Tam jtam.h...@gmail.com wrote: Can you still reproduce this in any way? Yes, I have 6 sets of user INBOX index caches that will crash dovecot-lda. The actual content of the INBOX is irrelevant (crash probably happens before INBOX is opened). Could you send me those files? Would be the easiest and quickest way to get it fixed :)
Re: [Dovecot] dovecot-lda (2.1.12) segfaults
On 19.12.2012, at 12.59, Timo Sirainen t...@iki.fi wrote: On 19.12.2012, at 12.47, Joseph Tam jtam.h...@gmail.com wrote: Can you still reproduce this in any way? Yes, I have 6 sets of user INBOX index caches that will crash dovecot-lda. The actual content of the INBOX is irrelevant (crash probably happens before INBOX is opened). Could you send me those files? Would be the easiest and quickest way to get it fixed :) Okay, fixed: http://hg.dovecot.org/dovecot-2.1/rev/32ce915e046a
Re: [Dovecot] dovecot-lda (2.1.12) segfaults
Timo Sirainen writes: Date: Wed, 19 Dec 2012 12:59:54 +0200 Could you send me those files? Would be the easiest and quickest way to get it fixed :) Date: Wed, 19 Dec 2012 15:02:25 +0200 Okay, fixed: http://hg.dovecot.org/dovecot-2.1/rev/32ce915e046a Yes it is does, and it stops crashing for the other 5 sets of indices. A 2-hour turnaround, of which an hour was spent packing up the index files. Amazing. Thanks. Joseph Tam jtam.h...@gmail.com
Re: [Dovecot] dovecot-lda (2.1.12) segfaults
On Thu, 2012-12-13 at 03:56 -0800, Joseph Tam wrote: We uograded our dovecot from version 2.1.10 - 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index. Reindexing with doveadm index does not fix anything. I've installed a test version with one user's problematic INBOX cache indices and ran gdb dovecot-lda (gdb) run -t testuser /dev/null and it crashes with the following backtrace Program received signal SIGSEGV, Segmentation fault. 0xff2a0440 in mail_cache_header_fields_read (cache=0x5c120) at mail-cache-fields.c:323 323 if (field_hdr-size sizeof(*field_hdr) + .. (gdb) p field_hdr $1 = (const struct mail_cache_header_fields *) 0x20 So mail_cache_map() returned a broken pointer.. Is this enough debug info to work your magic, Timo? I can supply the cache data if you neded it. It's compiled on a Solaris10. Can you still reproduce this in any way? I found two bugs, would be nice to know if they solve it: http://hg.dovecot.org/dovecot-2.1/rev/2f848393f78e http://hg.dovecot.org/dovecot-2.1/rev/bded819417d9
[Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information.
I ran dovecot -a and the blizzard of data seemed ok to my limited knowledge. Is there another log I should look into to trace this error down? Dovecot and system info: thufir@dur:~$ thufir@dur:~$ dovecot --version 2.0.19 thufir@dur:~$ thufir@dur:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS thufir@dur:~$ testing postfix dovecot (http://packages.ubuntu.com/precise/dovecot-postfix): root@dur:/etc/postfix# root@dur:/etc/postfix# telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 dur.bounceme.net ESMTP Postfix (Ubuntu) helo me 250 dur.bounceme.net mail from:f...@bar.com 250 2.1.0 Ok rcpt to:r...@dur.bounceme.net 250 2.1.5 Ok data 354 End data with CRLF.CRLF subject:ping 3 blah blah . 250 2.0.0 Ok: queued as 35EC92A0D72 quit 221 2.0.0 Bye Connection closed by foreign host. root@dur:/etc/postfix# root@dur:/etc/postfix# tail /var/log/mail.log Nov 16 12:30:07 dur postfix/smtpd[4113]: connect from localhost[127.0.0.1] Nov 16 12:30:40 dur postfix/smtpd[4113]: 35EC92A0D72: client=localhost[127.0.0.1] Nov 16 12:30:52 dur postfix/cleanup[4133]: 35EC92A0D72: message-id=20121116203040.35ec92a0...@dur.bounceme.net Nov 16 12:30:52 dur postfix/qmgr[1681]: 35EC92A0D72: from=f...@bar.com, size=321, nrcpt=1 (queue active) Nov 16 12:30:52 dur dovecot: lda(root): Error: chdir(/root/) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root, dir owned by 0:0 mode=0700) Nov 16 12:30:52 dur dovecot: lda(root): Error: chdir(/root) failed: Permission denied Nov 16 12:30:52 dur dovecot: lda(root): Error: user root: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/root/Maildir) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root, dir owned by 0:0 mode=0700) Nov 16 12:30:52 dur dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information. Nov 16 12:30:52 dur postfix/local[4134]: 35EC92A0D72: to=r...@dur.bounceme.net, relay=local, delay=25, delays=25/0.02/0/0.12, dsn=4.3.0, status=deferred (temporary failure) Nov 16 12:30:56 dur postfix/smtpd[4113]: disconnect from localhost[127.0.0.1] root@dur:/etc/postfix# thanks, Thufir
Re: [Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information.
On Fri, Nov 16, 2012 at 12:47:52PM -0800, Thufir wrote: I ran dovecot -a and the blizzard of data seemed ok to my limited knowledge. Is there another log I should look into to trace this error down? It's actually a Postfix problem. Postfix is invoking your Dovecot LDA with wrong permissions. Dovecot and system info: thufir@dur:~$ thufir@dur:~$ dovecot --version 2.0.19 thufir@dur:~$ thufir@dur:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS thufir@dur:~$ testing postfix dovecot (http://packages.ubuntu.com/precise/dovecot-postfix): root@dur:/etc/postfix# root@dur:/etc/postfix# telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 dur.bounceme.net ESMTP Postfix (Ubuntu) helo me 250 dur.bounceme.net mail from:f...@bar.com Angle brackets are required on envelope addresses (and I bet you don't own bar.com): MAIL FROM:f...@example.com 250 2.1.0 Ok rcpt to:r...@dur.bounceme.net RCPT TO:r...@dur.bounceme.net 250 2.1.5 Ok data 354 End data with CRLF.CRLF subject:ping 3 blah blah . A header must have a space after the colon. Header and body are separated by a blank line. See RFC 5322. 250 2.0.0 Ok: queued as 35EC92A0D72 quit 221 2.0.0 Bye Connection closed by foreign host. root@dur:/etc/postfix# root@dur:/etc/postfix# tail /var/log/mail.log Nov 16 12:30:07 dur postfix/smtpd[4113]: connect from localhost[127.0.0.1] Nov 16 12:30:40 dur postfix/smtpd[4113]: 35EC92A0D72: client=localhost[127.0.0.1] Nov 16 12:30:52 dur postfix/cleanup[4133]: 35EC92A0D72: message-id=20121116203040.35ec92a0...@dur.bounceme.net Nov 16 12:30:52 dur postfix/qmgr[1681]: 35EC92A0D72: from=f...@bar.com, size=321, nrcpt=1 (queue active) Nov 16 12:30:52 dur dovecot: lda(root): Error: chdir(/root/) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root, dir owned by 0:0 mode=0700) The fix to this is simply not to deliver mail to root. You should have aliased root to a mortal user. Postfix will not invoke a mailbox_command as root. In broader terms, you should only use root for actual system administration, and not for user tasks such as reading and sending mail. See and edit /etc/aliases, then run newaliases. Example: root: thufir http://www.postfix.org/postconf.5.html#default_privs http://www.postfix.org/postconf.5.html#mailbox_command http://www.postfix.org/local.8.html http://www.postfix.org/aliases.5.html After you have done this, requeue the message: # postsuper -r 35EC92A0D72 (or just delete it, s/-r/-d/, and try another test.) http://www.postfix.org/postsuper.1.html Nov 16 12:30:52 dur dovecot: lda(root): Error: chdir(/root) failed: Permission denied Nov 16 12:30:52 dur dovecot: lda(root): Error: user root: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/root/Maildir) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root, dir owned by 0:0 mode=0700) Nov 16 12:30:52 dur dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information. Nov 16 12:30:52 dur postfix/local[4134]: 35EC92A0D72: to=r...@dur.bounceme.net, relay=local, delay=25, delays=25/0.02/0/0.12, dsn=4.3.0, status=deferred (temporary failure) Nov 16 12:30:56 dur postfix/smtpd[4113]: disconnect from localhost[127.0.0.1] root@dur:/etc/postfix# -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Re: [Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information.
At 12PM -0800 on 16/11/12 you (Thufir) wrote: I ran dovecot -a and the blizzard of data seemed ok to my limited knowledge. Is there another log I should look into to trace this error down? snip Nov 16 12:30:52 dur dovecot: lda(root): Error: chdir(/root/) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root, dir owned by 0:0 mode=0700) Nov 16 12:30:52 dur dovecot: lda(root): Error: chdir(/root) failed: Permission denied Nov 16 12:30:52 dur dovecot: lda(root): Error: user root: Initialization failed: Initializing mail storage from mail_location setting failed: stat(/root/Maildir) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root, dir owned by 0:0 mode=0700) Nov 16 12:30:52 dur dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information. You should not be attempting to deliver mail to root directly. Instead you should forward root's mail to a real user with /etc/aliases; postfix's local(8) will not allow you to deliver mail as root. Ben
Re: [Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to server log for more information.
On Fri, Nov 16, 2012 at 10:15:24PM +, Ben Morrow wrote: postfix's local(8) will not allow you to deliver mail as root. Strictly speaking it will deliver to/as root, but not if invoking commands, which is what the OP was doing. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Re: [Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to
On Fri, 16 Nov 2012 16:09:54 -0600, /dev/rob0 wrote:
The fix to this is simply not to deliver mail to root. You should have
aliased root to a mortal user. Postfix will not invoke a mailbox_command
as root.
In broader terms, you should only use root for actual system
administration, and not for user tasks such as reading and sending mail.
See and edit /etc/aliases, then run newaliases. Example:
root: thufir
http://www.postfix.org/postconf.5.html#default_privs
http://www.postfix.org/postconf.5.html#mailbox_command
http://www.postfix.org/local.8.html
http://www.postfix.org/aliases.5.html
After you have done this, requeue the message:
# postsuper -r 35EC92A0D72
(or just delete it, s/-r/-d/, and try another test.)
http://www.postfix.org/postsuper.1.html
Ah, thank you. Not dovecot at all, makes sense. I was sending to root
because of a problem with keychain preventing usage of the mail
command for users:
http://ubuntuforums.org/showthread.php?t=2065461
Anyhow, that's fixed so that I can now use the mail command as a
mortal, as you put it. I think I'm on my way, and that this is a
postfix and not dovecot problem. The mail doesn't arrive, but the log
shows as delivered (I think) and then removed for some reason:
thufir@dur:~$
thufir@dur:~$
thufir@dur:~$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 dur.bounceme.net ESMTP Postfix (Ubuntu)
HELO me
250 dur.bounceme.net
mail from:thu...@example.com
250 2.1.0 Ok
rcpt to:thufir@localhost
250 2.1.5 Ok
data
354 End data with CRLF.CRLF
subject: never arrives
postfix problem?
.
250 2.0.0 Ok: queued as 3C8392A0007
quit
221 2.0.0 Bye
Connection closed by foreign host.
thufir@dur:~$
thufir@dur:~$ mail
No mail for thufir
thufir@dur:~$
thufir@dur:~$
thufir@dur:~$ tail /var/log/mail.log
Nov 16 17:19:04 dur postfix/smtpd[2975]: connect from localhost[127.0.0.1]
Nov 16 17:19:32 dur postfix/smtpd[2975]: disconnect from localhost
[127.0.0.1]
Nov 16 17:19:36 dur postfix/smtpd[2975]: connect from localhost[127.0.0.1]
Nov 16 17:20:06 dur postfix/smtpd[2975]: 3C8392A0007: client=localhost
[127.0.0.1]
Nov 16 17:20:48 dur postfix/cleanup[2985]: 3C8392A0007: message-
id=20121117012006.3c8392a0...@dur.bounceme.net
Nov 16 17:20:48 dur postfix/qmgr[1521]: 3C8392A0007:
from=thu...@example.com, size=336, nrcpt=1 (queue active)
Nov 16 17:20:48 dur dovecot: lda(thufir):
msgid=20121117012006.3c8392a0...@dur.bounceme.net: saved mail to INBOX
Nov 16 17:20:48 dur postfix/local[2988]: 3C8392A0007:
to=thufir@localhost, relay=local, delay=55, delays=55/0.02/0/0.17,
dsn=2.0.0, status=sent (delivered to command: /usr/lib/dovecot/deliver -
c /etc/dovecot/conf.d/01-mail-stack-delivery.conf -m ${EXTENSION})
Nov 16 17:20:48 dur postfix/qmgr[1521]: 3C8392A0007: removed
Nov 16 17:20:54 dur postfix/smtpd[2975]: disconnect from localhost
[127.0.0.1]
thufir@dur:~$
thanks,
Thufir
Re: [Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to
On Fri, Nov 16, 2012 at 05:32:16PM -0800, Thufir wrote:
On Fri, 16 Nov 2012 16:09:54 -0600, /dev/rob0 wrote:
The fix to this is simply not to deliver mail to root. You
should have aliased root to a mortal user. Postfix will not
invoke a mailbox_command as root.
Ah, thank you. Not dovecot at all, makes sense. I was sending
to root because of a problem with keychain preventing usage of
the mail command for users:
http://ubuntuforums.org/showthread.php?t=2065461
Anyhow, that's fixed so that I can now use the mail command as a
mortal, as you put it. I think I'm on my way, and that this is a
postfix and not dovecot problem. The mail doesn't arrive, but the
log shows as delivered (I think) and then removed for some reason:
It was delivered and removed from the queue.
thufir@dur:~$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 dur.bounceme.net ESMTP Postfix (Ubuntu)
HELO me
250 dur.bounceme.net
mail from:thu...@example.com
250 2.1.0 Ok
rcpt to:thufir@localhost
250 2.1.5 Ok
data
354 End data with CRLF.CRLF
subject: never arrives
postfix problem?
.
250 2.0.0 Ok: queued as 3C8392A0007
quit
221 2.0.0 Bye
Connection closed by foreign host.
thufir@dur:~$
thufir@dur:~$ mail
No mail for thufir
Your mail(1) MUA is not configured (or unable) to look in the place
where the mail was, in fact, delivered.
thufir@dur:~$ tail /var/log/mail.log
Nov 16 17:19:04 dur postfix/smtpd[2975]: connect from localhost[127.0.0.1]
Nov 16 17:19:32 dur postfix/smtpd[2975]: disconnect from localhost
[127.0.0.1]
Nov 16 17:19:36 dur postfix/smtpd[2975]: connect from localhost[127.0.0.1]
Nov 16 17:20:06 dur postfix/smtpd[2975]: 3C8392A0007: client=localhost
[127.0.0.1]
Nov 16 17:20:48 dur postfix/cleanup[2985]: 3C8392A0007: message-
id=20121117012006.3c8392a0...@dur.bounceme.net
Nov 16 17:20:48 dur postfix/qmgr[1521]: 3C8392A0007:
from=thu...@example.com, size=336, nrcpt=1 (queue active)
Nov 16 17:20:48 dur dovecot: lda(thufir):
msgid=20121117012006.3c8392a0...@dur.bounceme.net: saved mail to INBOX
Dovecot says it delivered it ...
Nov 16 17:20:48 dur postfix/local[2988]: 3C8392A0007:
to=thufir@localhost, relay=local, delay=55, delays=55/0.02/0/0.17,
dsn=2.0.0, status=sent (delivered to command: /usr/lib/dovecot/deliver -
c /etc/dovecot/conf.d/01-mail-stack-delivery.conf -m ${EXTENSION})
Nov 16 17:20:48 dur postfix/qmgr[1521]: 3C8392A0007: removed
... and duly reported this success to Postfix, which deleted it from
the queue as a result.
Nov 16 17:20:54 dur postfix/smtpd[2975]: disconnect from localhost
[127.0.0.1]
Judging from your previous post where deliver tried to write to
/root/Maildir/, I suppose your mail will be found in
~thufir/Maildir/new/ .
Now Postfix is fine, Dovecot seems to be fine also. Your remaining
issue is with mail. If it's old BSD mailx, that is not very
configurable. Consider other choices, such as mutt, alpine, or
Heirloom mailx.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Re: [Dovecot] dovecot: lda(root): Fatal: Invalid user settings. Refer to
On Fri, 16 Nov 2012 19:58:55 -0600, /dev/rob0 wrote: Judging from your previous post where deliver tried to write to /root/Maildir/, I suppose your mail will be found in ~thufir/Maildir/new/ . Now Postfix is fine, Dovecot seems to be fine also. Your remaining issue is with mail. If it's old BSD mailx, that is not very configurable. Consider other choices, such as mutt, alpine, or Heirloom mailx. Thanks, it's right there: thufir@dur:~$ thufir@dur:~$ ll Maildir/new/ total 20 drwx-- 2 thufir thufir 4096 Nov 16 18:56 ./ drwx-- 5 thufir thufir 4096 Nov 16 18:56 ../ -rw--- 1 thufir thufir 410 Nov 16 11:57 1353095866.M305477P3932.dur,S=410,W=422 -rw--- 1 thufir thufir 424 Nov 16 17:20 1353115248.M841336P2990.dur,S=424,W=436 -rw--- 1 thufir thufir 445 Nov 16 18:56 1353121003.M187706P3838.dur,S=445,W=457 thufir@dur:~$ thufir@dur:~$ nl Maildir/new/1353121003.M187706P3838.dur\,S\=445\,W\=457 1 Return-Path: thu...@example.net 2 X-Original-To: thufir@localhost 3 Delivered-To: thufir@localhost 4 Received: from me (localhost [127.0.0.1]) 5 by dur.bounceme.net (Postfix) with SMTP id 43D6F2A07C1 6 for thufir@localhost; Fri, 16 Nov 2012 18:55:55 -0800 (PST) 7 subject: to evolution mail 8 Message-Id: 20121117025613.43d6f2a0...@dur.bounceme.net 9 Date: Fri, 16 Nov 2012 18:55:55 -0800 (PST) 10 From: thu...@example.net 11 we'll see if this goes through. thufir@dur:~$ and it even looks like Evolution's supported :) thanks again for the help with what turned not to be dovecot at all. -Thufir
Re: [Dovecot] dovecot-lda not correct folder
On 30.10.2012, at 7.33, tony.blue.mailingl...@gmx.de wrote: ZUSATZORDNER=$DELIVERMAIL -e -d $LOGNAME -m .optionalfolder ... dovecot-lda puts the mails for the optionalfolder always in the .cur (INBOX). What´s the correct dovecot-lda parameter to put the mails in the optionalfolder? -m optionalfolder, without the dot. Also you may need to set lda_mailbox_autocreate=yes if it doesn't already exist.
Re: [Dovecot] dovecot-lda not correct folder
Am 07.11.2012 16:23, schrieb Timo Sirainen: On 30.10.2012, at 7.33, tony.blue.mailingl...@gmx.de wrote: -m optionalfolder, without the dot. Also you may need to set lda_mailbox_autocreate=yes if it doesn't already exist. Thanks Timo, that was the solution of my problem.
Re: [Dovecot] dovecot lda - Permission denied
On 26.10.2012, at 14.44, tony.blue.mailingl...@gmx.de wrote: Oct 25 23:37:13 gustav dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=501(andy) egid=100(users) missing +w perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) ... Oct 25 23:37:14 gustav dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=500(tony) egid=100(users) missing +w perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) ... Dovecot is installed as !include auth-passwdfile.conf.ext. For all users there is a entry in der /etc/dovecot/users. Usaly the user rights are set to 600. I tryed 755, but I get the same errormessage. 0755 is basically the same as 0600 for sockets, since you disabled writes for others. Use 0777 to give everyone permissions.
[Dovecot] dovecot-lda not correct folder
Hello, i use dovecot with maildir. The maildir-folder looks like this: vmail/mail/user1/cur vmail/mail/user1/.Sent vmail/mail/user1/.optionalfolder Procmail should put some definded mails in the optionalfolder My uses configuration does not do this: ... DELIVERMAIL=/usr/lib/dovecot/dovecot-lda IMAP=$DELIVERMAIL -e -d $LOGNAME -m INBOX ZUSATZORDNER=$DELIVERMAIL -e -d $LOGNAME -m .optionalfolder ... dovecot-lda puts the mails for the optionalfolder always in the .cur (INBOX). What´s the correct dovecot-lda parameter to put the mails in the optionalfolder? Thank you! Tony
[Dovecot] dovecot-lda delivery to Maildir/cur as 'seen'?
Hi I've added a server-side feature where authenticated customers sending through our SMTP server have their outbound mail copied to their Sent folder (like Gmail does). The delivery script called by qmail calls dovecot-lda to deliver it to the user's Sent folder. The problem now, is that the Sent folder shows the mail as unread, which MUAs flag (and notify, in the case of some). I've searched the docs and mailing list, but can't find an option to tell dovecot-lda to mark the mail being delivered, as seen/read. If I've missed something, please let me know. If not, then I think it might be a good idea to add a feature to dovecot-lda permitting one to specify delivery to the ./cur subfolder of a Maildir, instead of ./new. Thanks
[Dovecot] dovecot lda - Permission denied
Hallo,
please excuse my bad english. But I am not a native speaker.
I changed my cyrus to dovecot (alltogehter: fetchmail - procmail - exim4 -
dovecot).
But I get (I think from /usr/lib/dovecot/deliver) the following error-message
in my syslog:
...
Oct 25 23:37:13 gustav dovecot: lda: Error: userdb lookup:
connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=501(andy)
egid=100(users) missing +w perm: /var/run/dovecot/auth-userdb, dir owned by 0:0
mode=0755)
...
Oct 25 23:37:14 gustav dovecot: lda: Error: userdb lookup:
connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=500(tony)
egid=100(users) missing +w perm: /var/run/dovecot/auth-userdb, dir owned by 0:0
mode=0755)
...
Dovecot is installed as !include auth-passwdfile.conf.ext. For all users there
is a entry in der /etc/dovecot/users.
Usaly the user rights are set to 600. I tryed 755, but I get the same
errormessage.
...
service auth {
unix_listener auth-userdb {
mode = 0755
user = mailstore
group = mailstore
}
...
If I try ls /var/run/dovecot/auth-userdb -la - i get:
srwxr-xr-x 1 mailstore mailstore 0 Okt 25 23:36 /var/run/dovecot/auth-userdb
How can I solve this problem?
Tony
Re: [Dovecot] dovecot-lda delivery to Maildir/cur as 'seen'?
On Fri, Oct 26, 2012 at 01:27:00PM +0200, Dale Gallagher wrote: Hi [..] The problem now, is that the Sent folder shows the mail as unread, which MUAs flag (and notify, in the case of some). I've searched the Use Sieve [1] with Imap4flags (RFC 5232) to mark the email as read. Dennis [1] http://wiki2.dovecot.org/Pigeonhole/Sieve [..]
Re: [Dovecot] Dovecot LDA message save logging
Il 22/10/2012 01:08, Dominic Malolepszy ha scritto: Hi, Is there any option in Dovecot that enables logging the full path of where a message is saved in the backend? Dominic With mail_debug=yes you can see it. -- Alessio Cecchi is: @ ILS - http://www.linux.it/~alessice/ on LinkedIn - http://www.linkedin.com/in/alessice Assistenza Sistemi GNU/Linux - http://www.cecchi.biz/ @ PLUG - ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
Re: [Dovecot] dovecot-lda setting quota rules
it works great. thank You again Regards, Michal Grzedzicki 2012/8/3, Timo Sirainen t...@iki.fi: On 3.8.2012, at 2.13, Lazy wrote: dovecot-lda -o plugin/quota_rule=*:storage=1G thank You ! This is simple and elegant. Sill I need this to be taken from environment, I produced a simple patch adding one '-o' from an environment variable. You can also set environment: PLUGIN/QUOTA_RULE=*:storage=1G and then use dovecot-lda -k parameter. And if even that doesn't work, you could simply create a wrapper script. If You consider this useful I can try and make it more generic, enable multiple option overriding. You can also give -o parameter multiple times.
Re: [Dovecot] dovecot-lda setting quota rules
2012/7/31 Timo Sirainen t...@iki.fi: On 18.7.2012, at 4.33, Lazy wrote: I wan't it to stay that way. The problem is that it dosn't update the quota rules in Maildir when quota is changed in userdb. I have the rules avaiable in qmail-lda's environment, but I need an idea on how to feed the quota rule string to quota plugin without doing userdb lookup. What whould be the best way to do this, maybe in plugins/quota/quota.c:quota_root_add_rules() ? dovecot-lda -o plugin/quota_rule=*:storage=1G thank You ! This is simple and elegant. Sill I need this to be taken from environment, I produced a simple patch adding one '-o' from an environment variable. If You consider this useful I can try and make it more generic, enable multiple option overriding. Regards, Michal Grzedzicki
Re: [Dovecot] dovecot-lda setting quota rules
On 3.8.2012, at 2.13, Lazy wrote: dovecot-lda -o plugin/quota_rule=*:storage=1G thank You ! This is simple and elegant. Sill I need this to be taken from environment, I produced a simple patch adding one '-o' from an environment variable. You can also set environment: PLUGIN/QUOTA_RULE=*:storage=1G and then use dovecot-lda -k parameter. And if even that doesn't work, you could simply create a wrapper script. If You consider this useful I can try and make it more generic, enable multiple option overriding. You can also give -o parameter multiple times.
Re: [Dovecot] dovecot-lda setting quota rules
On 18.7.2012, at 4.33, Lazy wrote: I wan't it to stay that way. The problem is that it dosn't update the quota rules in Maildir when quota is changed in userdb. I have the rules avaiable in qmail-lda's environment, but I need an idea on how to feed the quota rule string to quota plugin without doing userdb lookup. What whould be the best way to do this, maybe in plugins/quota/quota.c:quota_root_add_rules() ? dovecot-lda -o plugin/quota_rule=*:storage=1G
[Dovecot] dovecot-lda setting quota rules
Hi, in my setup dovecot-lda reads user and home from environment, and dosn't perform userdb lookup Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: Effective uid=300, gid=300, home=/vmail/la/lazytest_test Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: Quota root: name=User quota backend=maildir args= Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: Quota warning: bytes=0 (95%) messages=0 reverse=no command=quota-warning 95 lazytest_test Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: Quota warning: bytes=0 (80%) messages=0 reverse=no command=quota-warning 80 lazytest_test Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes l ocation=maildir:~/Maildir:INDEX=/var/dovecot_indexes/vmail/la/lazytest_test Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: maildir++: root=/vmail/la/lazytest_test/Maildir, index=/var/dovecot_indexes/vmail/la/lazytest_tes t, control=, inbox=/vmail/la/lazytest_test/Maildir, alt= Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: userdb lookup skipped, username taken from USER environment Jul 18 03:09:47 thebe2 dovecot: lda(lazytest_test): Debug: Quota root: name=User quota backend=maildir args= I wan't it to stay that way. The problem is that it dosn't update the quota rules in Maildir when quota is changed in userdb. I have the rules avaiable in qmail-lda's environment, but I need an idea on how to feed the quota rule string to quota plugin without doing userdb lookup. What whould be the best way to do this, maybe in plugins/quota/quota.c:quota_root_add_rules() ? Regards, Michal Grzedzicki
Re: [Dovecot] Dovecot LDA, Offlineimap and Sieve
On 6/22/2012 1:28 AM, Johnny wrote: Hi, I am trying to st up Offlineimap to use Dovecots LDA to be able to use Sieve for mail filtering, but am not sure how to get this working. I think the right way would be to use 'preauthtunnel' in .offlineimaprc and try the setup below, which doesn't work. [...] Has anyone got any tips on how to get offlineimap to send mail to Dovecot in a way that Siev3e can be used? Could you show your dovecot config (dovecot -n output) here? I'm wondering whether you have enabled the Sieve plugin for LDA. Regards, Stephan.
Re: [Dovecot] Dovecot LDA, Offlineimap and Sieve
Hi Stephan,
Stephan Bosch step...@rename-it.nl writes:
On 6/22/2012 1:28 AM, Johnny wrote:
Hi,
I am trying to st up Offlineimap to use Dovecots LDA to be able to use
Sieve for mail filtering, but am not sure how to get this working. I
think the right way would be to use 'preauthtunnel' in .offlineimaprc
and try the setup below, which doesn't work.
[...]
Has anyone got any tips on how to get offlineimap to send mail to
Dovecot in a way that Siev3e can be used?
Could you show your dovecot config (dovecot -n output) here? I'm
wondering whether you have enabled the Sieve plugin for LDA.
I haven't set up Sieve yet, as I haven't been able to figure out how to
use the Dovecot LDA. Or is this not required to run Sieve?
Here's my config:
,
| mbox_write_locks = fcntl|
| namespace inbox { |
| hidden = no |
| inbox = yes |
| list = yes |
| location = |
| mailbox Drafts {|
| special_use = \Drafts |
| } |
| mailbox Junk { |
| special_use = \Junk |
| } |
| mailbox Sent { |
| special_use = \Sent |
| } |
| mailbox Sent Messages { |
| special_use = \Sent |
| } |
| mailbox Trash { |
| special_use = \Trash|
| } |
| prefix =|
| separator = . |
| subscriptions = yes |
| type = private |
| } |
| passdb {|
| args = scheme=MD5 username_format=%u /etc/dovecot/users |
| driver = passwd-file|
| } |
| protocols = imap|
| service auth { |
| unix_listener auth-userdb { |
| mode = 0666 |
| } |
| } |
| ssl = required |
| ssl_cert = /etc/pki/dovecot/certs/dovecot.pem |
| ssl_key = /etc/pki/dovecot/private/dovecot.pem |
| userdb {|
| args = username_format=%u /etc/dovecot/users|
| driver = passwd-file|
| } |
`
--
Johnny
[Dovecot] Dovecot LDA, Offlineimap and Sieve
Hi, I am trying to st up Offlineimap to use Dovecots LDA to be able to use Sieve for mail filtering, but am not sure how to get this working. I think the right way would be to use 'preauthtunnel' in .offlineimaprc and try the setup below, which doesn't work. ,.offlineimaprc | [Repository LocalRepository] | type = IMAP | preauthtunnel = ssh -q localhost '/usr/libexec/dovecot/deliver -d myloginid' ` If I go via the network card, the snch is fine, but Sieve can't be used? , | [Repository LocalRepository] | type = IMAP | preauthtunnel = MAIL=maildir:$HOME/Maildir/myMailDir /usr/libexec/dovecot/deliver -d mylogonid | remotehost = localhost | port = 143 | remoteuser = mylogonid | remotepass = mypassword ` Has anyone got any tips on how to get offlineimap to send mail to Dovecot in a way that Siev3e can be used? thanks! -- Johnny
[Dovecot] Dovecot-lda - 100% cpu
Hello, On my MTA server where I have installed postfix+mysql+dovecot(2.0.19), when server receives e.g 1000 e-mails and postfix start 10 threads dovecot-lda then my load is growing up. Disk for e-mails is connected through with iSCSI protocol. Any idea why this is happening?
Re: [Dovecot] dovecot LDA error
Hi Timo Sirainen, It’s working with me fine. With no problem. After I configured my MTA (sendmail) to run dovecot-lda as root with chmod 4750 /local/user/libexce/dovecot/dovecot-lda. And create group called secmail. I had to change dovecot-lda group to secmail. And then added mail to secmail group. It works with me. Before when I changed dovecot-lda group direct to mail doesn’t work. But it should to work.!!! I think that was the error. Later after creating separate group and adding mail to it, it’s working fine.. Any idea here… why doesn’t work if I changed dovecot-lda direct to mail group instead of creating new group and adding mail to it???. Hadi- From: t...@iki.fi Date: Thu, 26 Apr 2012 00:29:51 +0300 To: almarzuki2...@hotmail.com CC: dovecot@dovecot.org Subject: Re: [Dovecot] dovecot LDA error On 24.4.2012, at 20.41, Hadi Salem wrote: Apr 24 20:25:46 lda(ja...@example.com): Fatal: setgid(5000(vmail) from userdb lo okup) failed with euid=8(mail), gid=12(mail), egid=12(mail): Operation not permi tted (This binary should probably be called with process group set to 5000(vmail ) instead of 12(mail)) Configure your MTA to run dovecot-lda as vmail instead of as mail.
[Dovecot] dovecot-lda error
Hi,
im getting the fallowing error. from dovecot-lda log
Apr 25 17:30:41 lda(ja...@example.com): Fatal: setgid(5003(vmail) from
userdb lookup) failed with euid=8(mail), gid=12(mail), egid=12(mail):
Operation not permitted (This binary should probably be called with
process group set to 5003(vmail) instead of 12(mail))
this error occur if im using different uid and gid part from mail uid..
ja...@example.com:{PLAIN}123:5003:5003::/var/vmail/example.com/jamal/::userdb_mail=maildir:~/Maildir
but if i use mail uid it work fine..
ja...@example.com:{PLAIN}123:8:12::/var/vmail/example.com/jamal/::userdb_mail=maildir:~/Maildir
i tried using multiple uids as mention in wiki2.dovecot.org/LDA bye setting up
setuid-root for dovecot-lda but im getting on-there error from sendmail :-
Apr 25 17:30:41 host1 sendmail[31024]: q3PEUen2031022: to=ja...@example.com,
delay=00:00:00, xdelay=00:00:00, mailer=dovecot, pri=120359, relay=dovecot,
dsn=4.0.0, stat=Deferred: dovecot mailer
(/usr/local/libexec/dovecot/dovecot-lda) exited with EX_TEMPFAIL
im using sendmail.
[root@host1 conf.d]# doveconf -n
# 2.0.20: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-164.el5 x86_64 CentOS release 5.4 (Final)
auth_debug = yes
auth_debug_passwords = yes
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot.log
disable_plaintext_auth = no
first_valid_gid = 12
first_valid_uid = 8
hostname = host1.bigmama.com
info_log_path = /var/log/dovecot.log
last_valid_gid = 5
last_valid_uid = 5
log_path = /var/log/dovecot.log
mail_debug = yes
mail_gid = mail
mail_location = maildir:~/Maildir
mail_uid = mail
passdb {
args = scheme=PLAIN username_format=%u /etc/dovecot/users
driver = passwd-file
}
postmaster_address = r...@host1.bigmama.com
service auth {
unix_listener auth-userdb {
group = mail
mode = 0666
user = mail
}
}
ssl = no
userdb {
args = username_format=%u /etc/dovecot/users
driver = passwd-file
}
protocol lda {
info_log_path = /var/log/dovecot-lda.log
log_path = /var/log/dovecot-lda-errors.log
}
Re: [Dovecot] dovecot LDA error
On 24.4.2012, at 20.41, Hadi Salem wrote: Apr 24 20:25:46 lda(ja...@example.com): Fatal: setgid(5000(vmail) from userdb lo okup) failed with euid=8(mail), gid=12(mail), egid=12(mail): Operation not permi tted (This binary should probably be called with process group set to 5000(vmail ) instead of 12(mail)) Configure your MTA to run dovecot-lda as vmail instead of as mail.
Re: [Dovecot] dovecot-lda error
On 25.4.2012, at 17.52, Hadi Salem wrote:
i tried using multiple uids as mention in wiki2.dovecot.org/LDA bye setting
up setuid-root for dovecot-lda but im getting on-there error from sendmail :-
Apr 25 17:30:41 host1 sendmail[31024]: q3PEUen2031022:
to=ja...@example.com, delay=00:00:00, xdelay=00:00:00, mailer=dovecot,
pri=120359, relay=dovecot, dsn=4.0.0, stat=Deferred: dovecot mailer
(/usr/local/libexec/dovecot/dovecot-lda) exited with EX_TEMPFAIL
What do the Dovecot logs say about this?
protocol lda {
info_log_path = /var/log/dovecot-lda.log
log_path = /var/log/dovecot-lda-errors.log
}
If there is nothing in dovecot-lda-errors.log, make sure dovecot-lda has
permissions to write there (e.g. temporarily make it world-writable).
Re: [Dovecot] dovecot LDA with sendmail
Timo, in response to Hadi, wrote: Apr 24 20:25:46 lda(ja...@example.com): Fatal: setgid(5000(vmail) from userdb lo okup) failed with euid=8(mail), gid=12(mail), egid=12(mail): Operation not permi tted (This binary should probably be called with process group set to 5000(vmail ) instead of 12(mail)) Configure your MTA to run dovecot-lda as vmail instead of as mail. Yeah, what he said. Someone helpfully added documentation on how to do this at the end of Dovecot1's wiki (http://wiki.dovecot.org/LDA/Sendmail), which probably should be copied to Dovecot 2's wiki. So that's what I did. Joseph Tam jtam.h...@gmail.com
[Dovecot] dovecot LDA error
Hi,
My dovecot version is ,
# 2.0.20: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-164.el5 x86_64 CentOS release 5.4 (Final)
auth_debug = yes
auth_debug_passwords = yes
auth_verbose = yes
auth_verbose_passwords = plain
debug_log_path = /var/log/dovecot.log
disable_plaintext_auth = no
hostname = host1.bigmama.com
info_log_path = /var/log/dovecot.log
log_path = /var/log/dovecot.log
mail_debug = yes
mail_location = maildir:~/Maildir
passdb {
args = scheme=PLAIN
username_format=%u /etc/dovecot/users
driver = passwd-file
}
postmaster_address = r...@host1.bigmama.com
service auth {
unix_listener
auth-userdb {
group = mail
mode = 0660
user = mail
}
}
ssl = no
userdb {
args =
username_format=%u /etc/dovecot/users
driver = passwd-file
}
protocol lda {
info_log_path =
/var/log/dovecot-lda.log
log_path =
/var/log/dovecot-lda-errors.log
}
Im getting error from dovecot LDA logs log_path =
/var/log/dovecot-lda-errors.log
Apr 24 20:25:46 lda(ja...@example.com): Fatal:
setgid(5000(vmail) from userdb lo
okup) failed with
euid=8(mail), gid=12(mail), egid=12(mail): Operation not permi
tted (This binary should probably be called with process group set to
5000(vmail
) instead of 12(mail))
My usersdb config
ja...@example.com:{PLAIN}123:5000:5000::/var/vmail/example.com/jamal/
user 5000 system user as vmail
Permissions for the /var/vmail directory as follow
drwxr-xr-x 3 vmail vmail 4096 Apr 24 20:18 /var/vmail/
drwx-- 3 vmail vmail 4096 Apr 24 20:18
/var/vmail/example.com/
drwx-- 3 vmail vmail 4096 Apr 24 20:18
/var/vmail/example.com/jamal/
drwx-- 5 vmail vmail 4096 Apr 24 20:20
/var/vmail/example.com/jamal/Maildir/
Re: [Dovecot] dovecot LDA with sendmail
Hi,
i installed new version 2.0.20. but its the same problem
# 2.0.20: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-164.el5 x86_64 CentOS release 5.4 (Final)
auth_debug = yes
auth_debug_passwords = yes
auth_verbose = yes
debug_log_path = /var/log/dovecot.log
default_login_user = vmail
disable_plaintext_auth = no
hostname = host1.bigmama.com
info_log_path = /var/log/dovecot.log
log_path = /var/log/dovecot.log
mail_debug = yes
mail_location = maildir:~/Maildir
mail_privileged_group = vmail
passdb {
args = scheme=PLAIN username_format=%u /etc/dovecot/users
driver = passwd-file
}
postmaster_address = r...@host1.bigmama.com
service auth {
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
}
ssl = no
userdb {
args = username_format=%u /etc/dovecot/users
driver = passwd-file
}
Apr 21 17:47:16 host1 sendmail[32561]: q3LElF79032559: to=ja...@example.com,
ctladdr=r...@host1.bigmama.com (0/0), delay=00:00:00, xdelay=00:00:00,
mailer=dovecot, pri=120292, relay=dovecot, dsn=4.0.0, stat=Deferred: dovecot
mailer (/usr/local/libexec/dovecot/dovecot-lda) exited with EX_TEMPFAIL
Date: Fri, 20 Apr 2012 07:07:57 -0400
From: cmar...@media-brokers.com
To: dovecot@dovecot.org
Subject: Re: [Dovecot] dovecot LDA with sendmail
On 2012-04-19 9:45 PM, Joseph Tam jtam.h...@gmail.com wrote:
Hadi Salem almarzuki2...@hotmail.com writes:
Im configuring sendmail with dovecot for virtual users using
password file and file for user name. on centos.
dovecot-1.0.7-7.el5
Maybe I can beat Charles Marcus to the punch and recommend you upgrade
to the latest version, otherwise you'll run into bugs that have already
been fixed.
Lol... I stopped reading at '...sendmail with dovecot...', otherwise I'd
have beat you to it... ;)
--
Best regards,
Charles
Re: [Dovecot] dovecot LDA with sendmail
i installed new version 2.0.20. but its the same problem args = username_format=%u /etc/dovecot/users ... Apr 21 17:47:16 host1 sendmail[32561]: q3LElF79032559: to=ja...@example.com, ctladdr=r...@host1.bigmama.com (0/0), delay=00:00:00, xdelay=00:00:00, mailer=dovecot, pri=120292, relay=dovecot, dsn=4.0.0, stat=Deferred: dovecot mailer (/usr/local/libexec/dovecot/dovecot-lda) exited with EX_TEMPFAIL Any logs for dovecot? Same sendmail configs as before or did you try the extra flag I suggested? Joseph Tam jtam.h...@gmail.com
Re: [Dovecot] dovecot LDA with sendmail
On 2012-04-19 9:45 PM, Joseph Tam jtam.h...@gmail.com wrote: Hadi Salem almarzuki2...@hotmail.com writes: Im configuring sendmail with dovecot for virtual users using password file and file for user name. on centos. dovecot-1.0.7-7.el5 Maybe I can beat Charles Marcus to the punch and recommend you upgrade to the latest version, otherwise you'll run into bugs that have already been fixed. Lol... I stopped reading at '...sendmail with dovecot...', otherwise I'd have beat you to it... ;) -- Best regards, Charles
[Dovecot] dovecot LDA with sendmail
Hi, Im configuring sendmail with dovecot for virtual users using password file and file for user name. on centos. dovecot-1.0.7-7.el5 sendmail-8.13.8-2.el5 dovecot –n # 1.0.7: /etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login default_mail_env: maildir:/home/vmail/%d/%n mail_location: maildir:/home/vmail/%d/%n mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/users socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: root group: root I have also added dovecot LDA for sendmail /usr/share/sendmail-cf/mailer/dovecot.m4 ##*## ### DOVECOT Mailer specification ### ##*## Mdovecot, P=/usr/libexec/dovecot/deliver, F=DFMPhnu9,S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP,T=DNS/RFC822/X-Unix,A=/usr/libexec/dovecot/deliver -d $u And also [root@host1 mail]# cat /etc/mail/mailertable example.com dovecot:dovecot however when im sending email to the virtual user im getting this error, Apr 19 20:52:13 host1 sendmail[22311]: q3JHqDAR022309: to=ja...@example.com, ctladdr=r...@host1.bigmama.com (0/0), delay=00:00:00, xdelay=00:00:00, mailer=dovecot, pri=120292, relay=dovecot, dsn=4.0.0, stat=Deferred: dovecot mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL Dovecot LDA can’t deliver the mail to the user!!!
Re: [Dovecot] dovecot LDA with sendmail
Hadi Salem almarzuki2...@hotmail.com writes: Im configuring sendmail with dovecot for virtual users using password file and file for user name. on centos. dovecot-1.0.7-7.el5 Maybe I can beat Charles Marcus to the punch and recommend you upgrade to the latest version, otherwise you'll run into bugs that have already been fixed. Mdovecot, P=/usr/libexec/dovecot/deliver, F=DFMPhnu9,S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP,T=DNS/RFC822/X-Unix,A=/usr/libexec/dovecot/deliver -d $u ... Apr 19 20:52:13 host1 sendmail[22311]: q3JHqDAR022309: to=ja...@example.com, ctladdr=r...@host1.bigmama.com (0/0), delay=00:00:00, xdelay=00:00:00, mailer=dovecot, pri=120292, relay=dovecot, dsn=4.0.0, stat=Deferred: dovecot mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL Is there any logs from deliver? If not, look at this page to configure logging http://wiki.dovecot.org/LDA That's your best chance at finding out the problem. I don't have virtual users, so I can't venture to say whether this is part of the problem. I know I had to fiddle with the mailer flags (you have DFMPhnu9) to get my setup working, but I don't remember what I did or why. Try adding the S flag and see if that helps. Joseph Tam jtam.h...@gmail.com
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 5.4.2012, at 15.59, Charles Marcus wrote: Does anyone know if the use of LMTP (or even the dovecot LDA) still loses the x-original-to header that the postfix vda adds and that I rely heavily on (since I use a lot of aliases), and if it does, is there any solution to get the original recipient added back in before final delivery? LMTP adds a new Delivered-To: rcpt-to@address header when there is a single RCPT TO. You can force a single RCPT TO from Postfix side by setting lmtp_destination_recipient_limit=1. LMTP doesn't add/remove/change X-Original-To: header.
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2012-04-09 3:33 AM, Timo Sirainen t...@iki.fi wrote: On 5.4.2012, at 15.59, Charles Marcus wrote: Does anyone know if the use of LMTP (or even the dovecot LDA) still loses the x-original-to header that the postfix vda adds and that I rely heavily on (since I use a lot of aliases), and if it does, is there any solution to get the original recipient added back in before final delivery? LMTP adds a new Delivered-To:rcpt-to@address header when there is a single RCPT TO. You can force a single RCPT TO from Postfix side by setting lmtp_destination_recipient_limit=1. LMTP doesn't add/remove/change X-Original-To: header. Ok, thanks Timo... but... Are you saying that this 'Delivered-To:' header can somehow be leveraged to provide the same info as the x-original-to header? If not, since it was the postfix virtual delivery agent that added the x-original-to, and since using lmtp means I would not be using the postfix vda, is the appropriate place to add this header in dovecot's lmtp implementation (and if so, how hard would it be)? Or would this need to be done somehow on the postfix side (if so, I'll go ask on the postfix list)? Sorry for my ignorance - but as I said, I rely on this header (I use a ton of aliases, and without it I can't see the original (alias) recipient), so I need to determine if I'm going to be able to use lmtp or not (obviously, I would much prefer to do so)... Thanks again Timo... -- Best regards, Charles
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 9.4.2012, at 15.50, Charles Marcus wrote: LMTP adds a new Delivered-To:rcpt-to@address header when there is a single RCPT TO. You can force a single RCPT TO from Postfix side by setting lmtp_destination_recipient_limit=1. LMTP doesn't add/remove/change X-Original-To: header. Ok, thanks Timo... but... Are you saying that this 'Delivered-To:' header can somehow be leveraged to provide the same info as the x-original-to header? I guess X-Original-To is the same address as what Postfix sees as the original RCPT TO address before alias expansion and such? In that case, see my today's mail in Postfix list..
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2012-04-09 8:53 AM, Timo Sirainen t...@iki.fi wrote: I guess X-Original-To is the same address as what Postfix sees as the original RCPT TO address before alias expansion and such? In that case, see my today's mail in Postfix list. Yep... and hoping that you and Wietse can work out some way to support it... Thanks for participating in the discussion over there... :) -- Best regards, Charles
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On Sat, 7 Apr 2012 14:30:38 -0400, Jerry wrote: On Sat, 07 Apr 2012 11:06:48 -0700 Daniel L. Miller articulated: Unfortunately, the docs for the ltmp agent http://www.postfix.org/lmtp.8.html [1] don't say anything about adding these headers. I tried asking on the Postfix list - didn't get much of an answer. I may be wrong; however, from what I have been able to understand in regards to the Postfix documentation, if it does not explicitly claim to have a feature, then that feature is not available. In other words, if it doesn't state it can do it, it can't. As I just stated on that list - even though a given feature may be documented, the possible uses of that feature may not be immediately apparent. And while the Postfix lda virtual transports have the flag parameters, and the lmtp transport does not - the lmtp transport DOES have a whole slew of other parameters not available in the lda. So I was simply inquiring if there was a way to achieve my goal - given that my understanding of smtp handling in general, and Postfix in particular, are extremely limited. For some reason, I seem to irritate people with my polite questions - while others who are (in my opinion) downright rude and aggressive get assistance and acceptance. Maybe I need to start being more of a jerk on purpose... -- Daniel Links: -- [1] http://www.postfix.org/lmtp.8.html
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 4/6/2012 1:00 PM, Charles Marcus wrote: On 2012-04-06 2:53 PM, Daniel L. Miller dmil...@amfes.com wrote: I'm currently using Postfix 2.7, Dovecot 2.1, and the Dovecot LDA. I have a pure virtual user environment stored in LDAP. My messages include X-Original-To and Delivered-To headers. Well that is great news... at least I'll be able to use the LDA, if not LMTP... Thanks! :) I had difficulty getting the LMTP transport to work previously - I may revisit that. If you do, by all means reply back on whether or not the headers are still there... Thanks again, From the documentation... http://www.postfix.org/virtual.8.html The*virtual*(8) http://www.postfix.org/virtual.8.html delivery agent prepends a *From* /sender/ /time/*_*/stamp/ envelope header to each message, prepends a *Delivered-To:* message header with the envelope recipient address, prepends an*X-Original-To:* header with the recip- ient address as given to Postfix, prepends a*Return-Path:* message header with the envelope sender address, prepends a character to lines beginning with *From* , and appends an empty line. Using the Postfix pipe agent, which is what is used with the Dovecot LDA, http://www.postfix.org/pipe.8.html *flags=BDFORXhqu.* (optional) Optional message processing flags. By default, a message is copied unchanged. *B* Append a blank line at the end of each mes- sage. This is required by some mail user agents that recognize *From* lines only when preceded by a blank line. *D* Prepend a *Delivered-To:* /recipient/ message header with the envelope recipient address. Note: for this to work, the/transport/*_desti-* *nation_recipient_limit* must be 1 (see SIN- GLE-RECIPIENT DELIVERY above for details). The*D* flag also enforces loop detection (Postfix 2.5 and later): if a message already contains a*Delivered-To:* header with the same recipient address, then the message is returned as undeliverable. The address comparison is case insensitive. This feature is available as of Postfix 2.0. *F* Prepend a *From* /sender time/*_*/stamp/ envelope header to the message content. This is expected by, for example,*UUCP* software. *O* Prepend an *X-Original-To:* /recipient/ mes- sage header with the recipient address as given to Postfix. Note: for this to work, the*/transport/_destination_recipient_limit http://www.postfix.org/postconf.5.html#transport_destination_recipient_limit* must be 1 (see SINGLE-RECIPIENT DELIVERY above for details). Unfortunately, the docs for the ltmp agent http://www.postfix.org/lmtp.8.html don't say anything about adding these headers. I tried asking on the Postfix list - didn't get much of an answer. -- Daniel
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On Sat, 07 Apr 2012 11:06:48 -0700 Daniel L. Miller articulated: Unfortunately, the docs for the ltmp agent http://www.postfix.org/lmtp.8.html don't say anything about adding these headers. I tried asking on the Postfix list - didn't get much of an answer. I may be wrong; however, from what I have been able to understand in regards to the Postfix documentation, if it does not explicitly claim to have a feature, then that feature is not available. In other words, if it doesn't state it can do it, it can't. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 4/5/2012 5:59 AM, Charles Marcus wrote: On 2012-04-05 4:18 AM, Thomas Leuxner t...@leuxner.net wrote: Also with 2.x you may want to use LMTP rather than the LDA Piping. http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I am preparing to convert my main client's postfix_courier-imap setup to dovecot 2.1, which currently just uses the postfix virtual delivery agent... Does anyone know if the use of LMTP (or even the dovecot LDA) still loses the x-original-to header that the postfix vda adds and that I rely heavily on (since I use a lot of aliases), and if it does, is there any solution to get the original recipient added back in before final delivery? Everything I'm reading says that LMTP is better, but I really do need this header (or one like it) to be there so I know who the original recipient was (for filtering and other purposes). I'm currently using Postfix 2.7, Dovecot 2.1, and the Dovecot LDA. I have a pure virtual user environment stored in LDAP. My messages include X-Original-To and Delivered-To headers. I had difficulty getting the LMTP transport to work previously - I may revisit that. -- Daniel
Re: [Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2012-04-06 2:53 PM, Daniel L. Miller dmil...@amfes.com wrote: I'm currently using Postfix 2.7, Dovecot 2.1, and the Dovecot LDA. I have a pure virtual user environment stored in LDAP. My messages include X-Original-To and Delivered-To headers. Well that is great news... at least I'll be able to use the LDA, if not LMTP... Thanks! :) I had difficulty getting the LMTP transport to work previously - I may revisit that. If you do, by all means reply back on whether or not the headers are still there... Thanks again, -- Best regards, Charles
[Dovecot] Dovecot LDA/LMTP vs postfix virtual delivery agent and the x-original-to header
On 2012-04-05 4:18 AM, Thomas Leuxner t...@leuxner.net wrote: Also with 2.x you may want to use LMTP rather than the LDA Piping. http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I am preparing to convert my main client's postfix_courier-imap setup to dovecot 2.1, which currently just uses the postfix virtual delivery agent... Does anyone know if the use of LMTP (or even the dovecot LDA) still loses the x-original-to header that the postfix vda adds and that I rely heavily on (since I use a lot of aliases), and if it does, is there any solution to get the original recipient added back in before final delivery? Everything I'm reading says that LMTP is better, but I really do need this header (or one like it) to be there so I know who the original recipient was (for filtering and other purposes). Thanks, -- Best regards, Charles
[Dovecot] Dovecot LDA breaking .qmail forwarding?
Good morning all, I've a problem, I'm using the Dovecot LDA in my .qmail file: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER However when I add a forward, such as: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER mailto:wou...@vdschagt.com wou...@vdschagt.com The mail isn't forwarded and stays in the queue on the mail server, the same is the case when I reverse the lines. The error in the log file is: @40004f5de5f7033bc434 delivery 824026: deferral: qmail-inject:_fatal:_qq_trouble_creating_files_in_queue_(#4.3.0)/system_erro r_calling_qmail-inject/ When using another LDA, for example when specifying the Maildir, it works, but then i cannot use Sieve scripts. Any ideas? Am I doing anything wrong? Sincerely, -Wouter van der Schagt
[Dovecot] Dovecot lda parameters
hi all I have the following scheme. Postfix with virtual users with dovecot LDA. AD as database. Dovecot and Postfix get the following Idap attributes from AD: sAMAccountName, mail and mail_alias. The problem is that I can’t make dovecot lda move the user’s mail to the folder with the name from sAMAccountName attribute, as mail always moves to folder with e-mail address name. Is it posible to delivery e-mail to folder with name from ldap attributes sAMAccountName? --
[Dovecot] Dovecot LDA and address extensions - folders flood
Hi list, This post is slightly OT, I hope no one will take offense. I was following the wiki on using dovecot LDA with postfix and implemented, for our future mail server, the address extensions mechanism: an email sent to validuser+foldern...@mydomain.com will have dovecot-lda automagically create and subscribe the foldername folder. With some basic scripting I was able to create hundreds of folders in a few seconds. So my question is how do you implement this great feature in a secure way so that funny random people out there cant flood your mailbox with gigatons of folder. Thanks, kfx
Re: [Dovecot] Dovecot LDA and address extensions - folders flood
On 2012-01-11 1:00 PM, huret deffgok kada...@gmail.com wrote: Hi list, This post is slightly OT, I hope no one will take offense. I was following the wiki on using dovecot LDA with postfix and implemented, for our future mail server, the address extensions mechanism: an email sent to validuser+foldern...@mydomain.com will have dovecot-lda automagically create and subscribe the foldername folder. With some basic scripting I was able to create hundreds of folders in a few seconds. So my question is how do you implement this great feature in a secure way so that funny random people out there cant flood your mailbox with gigatons of folder. Don't have it autocreate the folder... Seriously, there is no way to provide that functionality and have the system determine when it is *you* doing it or someone else... But I think it is a non problem... how often do you receive plus-addressed spam?? -- Best regards, Charles
Re: [Dovecot] Dovecot LDA and address extensions - folders flood
On Wed, Jan 11, 2012 at 7:04 PM, Charles Marcus cmar...@media-brokers.comwrote: On 2012-01-11 1:00 PM, huret deffgok kada...@gmail.com wrote: Hi list, This post is slightly OT, I hope no one will take offense. I was following the wiki on using dovecot LDA with postfix and implemented, for our future mail server, the address extensions mechanism: an email sent to validUser+foldername@**mydomain.comvaliduser%2bfoldern...@mydomain.com will have dovecot-lda automagically create and subscribe the foldername folder. With some basic scripting I was able to create hundreds of folders in a few seconds. So my question is how do you implement this great feature in a secure way so that funny random people out there cant flood your mailbox with gigatons of folder. Don't have it autocreate the folder... Seriously, there is no way to provide that functionality and have the system determine when it is *you* doing it or someone else... But I think it is a non problem... how often do you receive plus-addressed spam?? None from now. But I was thinking about something like malice rather than spamming. For me it's an open door to DOS the service. What about a functionality that would throttle the rate of creation of folders from one IP address, with a ban in case of abuse ? Or maybe should I look at the file system level.
Re: [Dovecot] Dovecot LDA and address extensions - folders flood
On 2012-01-11 2:05 PM, huret deffgok wrote: On Wed, Jan 11, 2012 at 7:04 PM, Charles Marcus wrote: On 2012-01-11 1:00 PM, huret deffgok wrote: This post is slightly OT, I hope no one will take offense. I was following the wiki on using dovecot LDA with postfix and implemented, for our future mail server, the address extensions mechanism: an email sent to validUser+foldername@**mydomain.comvaliduser%2bfoldern...@mydomain.com will have dovecot-lda automagically create and subscribe the foldername folder. With some basic scripting I was able to create hundreds of folders in a few seconds. So my question is how do you implement this great feature in a secure way so that funny random people out there cant flood your mailbox with gigatons of folder. Don't have it autocreate the folder... Seriously, there is no way to provide that functionality and have the system determine when it is *you* doing it or someone else... But I think it is a non problem... how often do you receive plus-addressed spam?? None from now. But I was thinking about something like malice rather than spamming. For me it's an open door to DOS the service. What about a functionality that would throttle the rate of creation of folders from one IP address, with a ban in case of abuse ? Or maybe should I look at the file system level. Again - and no offense - but I think you are tilting at windmills... If you get hit by this, you will not only have thousands or millions of folders, you'll have one email for each folder. So, the question is, how do you prevent being flooded with spam... and the answer is, decent anti-spam measures. I prefer ASSP, but I just wish you could use it as an after queue content filter (for its most excellent content filtering and more importantly quarantine management/block reporting features/functionality). That said, postfix, with sane anti-spam measures, along with the most excellent new postscreen (available in 2.8+ I believe) is good enough to stop most anything like this that you may be worried about. Like I said, set up postfix (or your smtp server) right, and this is a non-issue. -- Best regards, Charles
Re: [Dovecot] dovecot-lda error
On 05.01.2012 08:45, wrote Wesley M.:
Hi,
Hi,
I use Dovecot 2.0.13 on OpenBSD 5.0
When i try to send emails i
have the following error in /var/log/maillog
Jan 5 11:23:49 mail50
postfix/pipe[29423]: D951842244C: to=, relay=dovecot, delay=0.02,
delays=0.01/0/0/0.01, dsn=5.3.0, status=bounced (command line usage error.
Command output: deliver: unknown option -- n Usage: dovecot-lda [-c ] [-a ]
Look at the bottom of this page:
http://wiki2.dovecot.org/Upgrading/2.0
[-d ] [-p ] [-f ] [-m ] [-e] [-k] )
Jan 5 11:23:49 mail50
postfix/qmgr[13787]: D951842244C: removed
In my /etc/postfix/master.cf
:
# Dovecot LDA
dovecot unix - n n - - pipe
flags=ODR
user=_dovecot:_dovecot argv=/usr/local/libexec/dovecot/deliver -f
${
sender} -d ${user}@${nexthop} -n -m ${extension}
How can i resolve that
?
Thank you very much for your replies.
Cheers,
Wesley.
[Dovecot] dovecot-lda error
Hi,
I use Dovecot 2.0.13 on OpenBSD 5.0
When i try to send emails i
have the following error in /var/log/maillog
Jan 5 11:23:49 mail50
postfix/pipe[29423]: D951842244C: to=, relay=dovecot, delay=0.02,
delays=0.01/0/0/0.01, dsn=5.3.0, status=bounced (command line usage error.
Command output: deliver: unknown option -- n Usage: dovecot-lda [-c ] [-a ]
[-d ] [-p ] [-f ] [-m ] [-e] [-k] )
Jan 5 11:23:49 mail50
postfix/qmgr[13787]: D951842244C: removed
In my /etc/postfix/master.cf
:
# Dovecot LDA
dovecot unix - n n - - pipe
flags=ODR
user=_dovecot:_dovecot argv=/usr/local/libexec/dovecot/deliver -f
${
sender} -d ${user}@${nexthop} -n -m ${extension}
How can i resolve that
?
Thank you very much for your replies.
Cheers,
Wesley.
Re: [Dovecot] dovecot-lda quota rule
micah anderson mi...@riseup.net writes:
On Wed, 16 Nov 2011 11:09:12 -0500, micah anderson mi...@riseup.net wrote:
On Tue, 15 Nov 2011 22:27:20 +0200, Timo Sirainen t...@iki.fi wrote:
On Thu, 2011-11-10 at 13:59 -0500, Micah Anderson wrote:
I really like the feature where you can define quota rules with percents
which trigger off of the default values[0] (so you can set the Trash to
allow for 10% more of the user's quota for example).
What I would really love in dovecot would be for the ability to
configure a quota rule for dovecot-lda. I would like to configure things
so we don't bounce emails for users until they are well over quota, the
IMAP quota plugin is a really great way to notify people that they are
over quota because it fails to write to other folders that should be
enough to get people's attention that they need to deal with things, but
bouncing is harsh.
You can give LDA-specific quota settings. Like maybe:
protocol lda {
plugin {
quota_rule2 = INBOX:storage=200%
}
}
I just tried doing this, and I started bouncing mail for everyone
because they were over quota (even when they arent), so I am clearly
missing something in how I have it configured. This is what I have:
Solved, thanks to tss on irc... My problem was the dovecot-lda
invocation was not passing the -d parameter, so no userdb quota rules
were being applied.
micah
Re: [Dovecot] dovecot-lda quota rule
On Wed, 16 Nov 2011 11:09:12 -0500, micah anderson mi...@riseup.net wrote:
On Tue, 15 Nov 2011 22:27:20 +0200, Timo Sirainen t...@iki.fi wrote:
On Thu, 2011-11-10 at 13:59 -0500, Micah Anderson wrote:
I really like the feature where you can define quota rules with percents
which trigger off of the default values[0] (so you can set the Trash to
allow for 10% more of the user's quota for example).
What I would really love in dovecot would be for the ability to
configure a quota rule for dovecot-lda. I would like to configure things
so we don't bounce emails for users until they are well over quota, the
IMAP quota plugin is a really great way to notify people that they are
over quota because it fails to write to other folders that should be
enough to get people's attention that they need to deal with things, but
bouncing is harsh.
You can give LDA-specific quota settings. Like maybe:
protocol lda {
plugin {
quota_rule2 = INBOX:storage=200%
}
}
I just tried doing this, and I started bouncing mail for everyone
because they were over quota (even when they arent), so I am clearly
missing something in how I have it configured. This is what I have:
namespace {
separator = .
prefix =
inbox = yes
}
namespace {
separator = .
prefix = INBOX.
inbox = no
hidden = yes
list = no
}
plugin {
quota = dict:Your mail quota::proxy::quota
}
dict {
quota = mysql:/etc/dovecot/dovecot-dict-sql.conf
}
plugin {
quota_exceeded_message = You are over quota. To avoid losing mail,
immediately empty your Trash and Sent folders and delete emails with large
attachments.
quota_rule = *:bytes=100663296 # in case someone doesn't have sql quota
quota_rule2 = Trash:bytes=+20%% # let trash be larger by 20%
quota_rule3 = Spam:bytes=+10%% # let spam be larger by 10%
quota_rule4 = INBOX.Trash:bytes=+20%% # repeat the above for namespaces
quota_rule5 = INBOX.Spam:bytes=+10%% # same
quota_rule6 = INBOX.restored:bytes=+500%% # allow for temporary folder
}
...
protocol lda {
# Space separated list of plugins to load (default is global mail_plugins).
mail_plugins = $mail_plugins
plugin {
quota_rule7 = INBOX:bytes=+10%%
}
}
Maybe I should have that quota_rule7 be *:bytes=+10%% ?
thanks for any suggestions for what I am missing here!
micah
pgp0AMtVVmc58.pgp
Description: PGP signature
Re: [Dovecot] dovecot-lda quota rule
On Tue, 15 Nov 2011 22:27:20 +0200, Timo Sirainen t...@iki.fi wrote:
On Thu, 2011-11-10 at 13:59 -0500, Micah Anderson wrote:
I really like the feature where you can define quota rules with percents
which trigger off of the default values[0] (so you can set the Trash to
allow for 10% more of the user's quota for example).
What I would really love in dovecot would be for the ability to
configure a quota rule for dovecot-lda. I would like to configure things
so we don't bounce emails for users until they are well over quota, the
IMAP quota plugin is a really great way to notify people that they are
over quota because it fails to write to other folders that should be
enough to get people's attention that they need to deal with things, but
bouncing is harsh.
You can give LDA-specific quota settings. Like maybe:
protocol lda {
plugin {
quota_rule2 = INBOX:storage=200%
}
}
Aha! Just what I was looking for. I presume the number following
'quota_rule' must be an unique number across all quota_rules in my
config?
or even not enforcing quota at all:
protocol lda {
plugin {
quota = maildir:User quota:noenforcing
}
}
I was not aware of the noenforcing option, that answered another
question I had not asked yet, so thanks for that! :)
micah
pgpcuI0ivRtaB.pgp
Description: PGP signature
Re: [Dovecot] dovecot-lda quota rule
On Wed, 2011-11-16 at 11:09 -0500, micah anderson wrote:
protocol lda {
plugin {
quota_rule2 = INBOX:storage=200%
}
}
Aha! Just what I was looking for. I presume the number following
'quota_rule' must be an unique number across all quota_rules in my
config?
No only unique, but all of the numbers must exist. For example
quota_rule2 isn't used if quota_rule doesn't exist. Or quota_rule10
isn't used, unless quota_rule2..9 also exist.
Re: [Dovecot] dovecot-lda quota rule
On Wed, 16 Nov 2011 18:27:20 +0200, Timo Sirainen t...@iki.fi wrote:
On Wed, 2011-11-16 at 11:09 -0500, micah anderson wrote:
protocol lda {
plugin {
quota_rule2 = INBOX:storage=200%
}
}
Aha! Just what I was looking for. I presume the number following
'quota_rule' must be an unique number across all quota_rules in my
config?
No only unique, but all of the numbers must exist. For example
quota_rule2 isn't used if quota_rule doesn't exist. Or quota_rule10
isn't used, unless quota_rule2..9 also exist.
Ah, interesting, good to know. I presume that 'quota_rule' stands in for
'quota_rule1' and one does not need to specify a quota_rule1 if one has
a 'quota_rule'.
micah
pgp86Wcne4iz6.pgp
Description: PGP signature
Re: [Dovecot] dovecot-lda quota rule
On Thu, 2011-11-10 at 13:59 -0500, Micah Anderson wrote:
I really like the feature where you can define quota rules with percents
which trigger off of the default values[0] (so you can set the Trash to
allow for 10% more of the user's quota for example).
What I would really love in dovecot would be for the ability to
configure a quota rule for dovecot-lda. I would like to configure things
so we don't bounce emails for users until they are well over quota, the
IMAP quota plugin is a really great way to notify people that they are
over quota because it fails to write to other folders that should be
enough to get people's attention that they need to deal with things, but
bouncing is harsh.
You can give LDA-specific quota settings. Like maybe:
protocol lda {
plugin {
quota_rule2 = INBOX:storage=200%
}
}
or even not enforcing quota at all:
protocol lda {
plugin {
quota = maildir:User quota:noenforcing
}
}
[Dovecot] dovecot-lda quota rule
I really like the feature where you can define quota rules with percents which trigger off of the default values[0] (so you can set the Trash to allow for 10% more of the user's quota for example). What I would really love in dovecot would be for the ability to configure a quota rule for dovecot-lda. I would like to configure things so we don't bounce emails for users until they are well over quota, the IMAP quota plugin is a really great way to notify people that they are over quota because it fails to write to other folders that should be enough to get people's attention that they need to deal with things, but bouncing is harsh. Is there a way to do this now that I haven't seen? thanks! micah 0. http://wiki2.dovecot.org/Quota/Configuration -- pgpaJaa1mOJFt.pgp Description: PGP signature
[Dovecot] DoveCot LDA prefetch fails with LDA, works with POP client
Hi there,
I am using DoveCot 1.0.7. I know it is real old, but we have to work
with it. I have configured LDAP lookup with password prefetch in
DoveCot. I can successfully receive emails through DoveCot, thus proving
my password prefetch and user authentication are good.
The problem is when I use Postfix to deliver message to DoveCot via LDA.
My postfix master.cf looks like this:
dovecot unix - n n - - pipe
flags=Rhu user=hubdirect null_sender=
argv=/usr/libexec/dovecot/deliver -e -f ${sender} -d ${user}
Given a message, Postfix looks up LDAP and find the user associated with
the recipient address and delivers the message using LDA. LDAP logs
indicates that Postfix is returning the right user.
The problem is that DoveCot complains passdb did not return userdb
entries, but I do not know which entries passdb failed to return. Here
is what I have in dovecot-ldap.conf. I have tried different things in
user_attrs, DoveCot keeps complaining the same thing.
user_attrs = username=user
user_filter =
((objectClass=DirectUser)(username=%u)(roles=*ROLE_EDGE_EMAIL*))
pass_attrs =
username=user,password=password,username=userdb_user,usermaildirectory=u
serdb_mail,userhomedirectory=userdb_home,825=userdb_uid,825=userdb_gid
pass_filter =
((objectClass=DirectUser)(username=%u)(roles=*ROLE_EDGE_EMAIL*))
The documentation says LDA does not use prefetch, but the log seems to
indicate otherwise. I clearly see the service=deliver is
authenticating the user first, thus using password prefetch. Can someone
clarify this?
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): Loading modules from
directory: /usr/lib64/dovecot/lda
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): Module loaded:
/usr/lib64/dovecot/lda/lib10_quota_plugin.so
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default): master in: USER
1 emailspool service=deliver
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default):
prefetch(emailspool): passdb didn't return userdb entries
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default): ldap(emailspool):
user search: base=dc=hubdirect,dc=dev,dc=medplus,dc=com scope=subtree
filter=((objectClass=DirectUser)(username=emailspool)(roles=*ROLE_EDGE_
EMAIL*)) fields=username
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default): master out: USER
1 emailspool user=emailspool uid=825 gid=825
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input:
emailspool
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input:
user=emailspool
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input: uid=825
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input: gid=825
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): maildir:
data=/home/hubdirect/emailspool/Maildir
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): maildir:
root=/home/hubdirect/emailspool/Maildir,
index=/home/hubdirect/emailspool/Maildir, control=, inbox=
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool):
msgid=12097075.28.1312571545112.JavaMail.zhou_y@yzhou-lp2: saved mail
to INBOX
Thanks,
Yan
Confidentiality Notice: The information contained in this electronic
transmission is confidential and may be legally privileged. It is intended only
for the addressee(s) named above. If you are not an intended recipient, be
aware that any disclosure, copying, distribution or use of the information
contained in this transmission is prohibited and may be unlawful. If you have
received this transmission in error, please notify us by telephone (513)
229-5500 or by email (postmas...@medplus.com). After replying, please erase it
from your computer system.
Re: [Dovecot] DoveCot LDA prefetch fails with LDA, works with POP client
-Original Message-
From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org]
On Behalf Of Zhou, Yan
Sent: Friday, August 05, 2011 4:24 PM
To: dovecot@dovecot.org
Subject: [Dovecot] DoveCot LDA prefetch fails with LDA, works with POP
client
Hi there,
I am using DoveCot 1.0.7. I know it is real old, but we have to work
with it. I have configured LDAP lookup with password prefetch in
DoveCot. I can successfully receive emails through DoveCot, thus
proving
my password prefetch and user authentication are good.
The problem is when I use Postfix to deliver message to DoveCot via
LDA.
My postfix master.cf looks like this:
dovecot unix - n n - - pipe
flags=Rhu user=hubdirect null_sender=
argv=/usr/libexec/dovecot/deliver -e -f ${sender} -d ${user}
Given a message, Postfix looks up LDAP and find the user associated
with
the recipient address and delivers the message using LDA. LDAP logs
indicates that Postfix is returning the right user.
The problem is that DoveCot complains passdb did not return userdb
entries, but I do not know which entries passdb failed to return.
Here
is what I have in dovecot-ldap.conf. I have tried different things in
user_attrs, DoveCot keeps complaining the same thing.
user_attrs = username=user
user_filter =
((objectClass=DirectUser)(username=%u)(roles=*ROLE_EDGE_EMAIL*))
pass_attrs =
username=user,password=password,username=userdb_user,usermaildirectory=
u
serdb_mail,userhomedirectory=userdb_home,825=userdb_uid,825=userdb_gid
pass_filter =
((objectClass=DirectUser)(username=%u)(roles=*ROLE_EDGE_EMAIL*))
The documentation says LDA does not use prefetch, but the log seems to
indicate otherwise. I clearly see the service=deliver is
authenticating the user first, thus using password prefetch. Can
someone
clarify this?
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): Loading modules
from
directory: /usr/lib64/dovecot/lda
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): Module loaded:
/usr/lib64/dovecot/lda/lib10_quota_plugin.so
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default): master in: USER
1 emailspool service=deliver
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default):
prefetch(emailspool): passdb didn't return userdb entries
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default):
ldap(emailspool):
user search: base=dc=hubdirect,dc=dev,dc=medplus,dc=com scope=subtree
filter=((objectClass=DirectUser)(username=emailspool)(roles=*ROLE_EDGE
_
EMAIL*)) fields=username
Aug 5 15:12:25 dir-dev-pop01 dovecot: auth(default): master out: USER
1 emailspool user=emailspool uid=825 gid=825
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input:
emailspool
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input:
user=emailspool
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input: uid=825
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): auth input: gid=825
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): maildir:
data=/home/hubdirect/emailspool/Maildir
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool): maildir:
root=/home/hubdirect/emailspool/Maildir,
index=/home/hubdirect/emailspool/Maildir, control=, inbox=
Aug 5 15:12:25 dir-dev-pop01 deliver(emailspool):
msgid=12097075.28.1312571545112.JavaMail.zhou_y@yzhou-lp2: saved
mail
to INBOX
Thanks,
Yan
I was able to get this working by the following attributes.
user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid
Thanks!
Yan
Confidentiality Notice: The information contained in this electronic
transmission is confidential and may be legally privileged. It is intended only
for the addressee(s) named above. If you are not an intended recipient, be
aware that any disclosure, copying, distribution or use of the information
contained in this transmission is prohibited and may be unlawful. If you have
received this transmission in error, please notify us by telephone (513)
229-5500 or by email (postmas...@medplus.com). After replying, please erase it
from your computer system.
[Dovecot] DoveCot LDA/Postfix deliver by address
Hi there, I am using DoveCot 1.0.7 and virtual users. We want to integrate with Postfix 2.3.3 to use DoveCot LDA to deliver messages to user mailbox. All users are stored in LDAP. DoveCot looks up user by LDAP access. Our user name is not necessarily part of the address. For instance, address zhouy@ may be with user yzhou, thus all messages to zhouy@ should go to /home/vmail/yzhou/Maildir I do not see how LDA can support a two-step lookup: 1. Look up user from the given address, 2. Lookup user mail directory from the user in step 1. My understanding is that /etc/dove-ldap.conf is a one-step lookup, it only does user lookup (without password lookup). Any suggestions? Thanks, Yan Confidentiality Notice: The information contained in this electronic transmission is confidential and may be legally privileged. It is intended only for the addressee(s) named above. If you are not an intended recipient, be aware that any disclosure, copying, distribution or use of the information contained in this transmission is prohibited and may be unlawful. If you have received this transmission in error, please notify us by telephone (513) 229-5500 or by email (postmas...@medplus.com). After replying, please erase it from your computer system.
[Dovecot] DoveCot LDA/Postfix get address rather than user from messages
Hi there,
We are using Postfix and DoveCot 1.0.7, using DoveCot LDA/Postfix to
deliver messages to mailboxes via LDAP lookup.
My Postfix 2.3.3 /etc/postfix/master.cf reads like this
dovecot unix - n n - - pipe
flags=Rhu user=hubdirect argv=/usr/libexec/dovecot/deliver -f
${sender} -d ${recipient}
And my /etc/dovecot-ldap.conf reads like this:
user_filter = ((objectClass=DirectUser)(username=%n))
user_attrs =
userreference=user,usermaildirectory=mail,userhomedirectory=home
I find the above %n value in user_filter I am getting is always the
address, not user part in user@domain as the documentation says. Did I
miss anything?
Thanks,
Yan
Confidentiality Notice: The information contained in this electronic
transmission is confidential and may be legally privileged. It is intended only
for the addressee(s) named above. If you are not an intended recipient, be
aware that any disclosure, copying, distribution or use of the information
contained in this transmission is prohibited and may be unlawful. If you have
received this transmission in error, please notify us by telephone (513)
229-5500 or by email (postmas...@medplus.com). After replying, please erase it
from your computer system.
Re: [Dovecot] DoveCot LDA/Postfix deliver by address
On 2011-06-21 1:34 PM, Zhou, Yan wrote: I am using DoveCot 1.0.7 snip Any suggestions? Upgrade first... -- Best regards, Charles
Re: [Dovecot] DoveCot LDA/Postfix deliver by address
On Tue, 21 Jun 2011 13:53:31 -0400 Charles Marcus articulated: On 2011-06-21 1:34 PM, Zhou, Yan wrote: I am using DoveCot 1.0.7 snip Any suggestions? Upgrade first... Both Dovecot and Postfix. Postfix =2.4 are no longer supported. -- Jerry ✌ dovecot.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __
