Re: [Dovecot] v2.0.beta3 released
On Sun, 2010-02-21 at 07:26 +0100, Thomas Leuxner wrote:
Am 21.02.2010 um 07:16 schrieb Timo Sirainen:
Yes, that's intentional. imaps isn't a protocol.
Thanks Timo. Has the specific logging option for the LDA been dropped? I see
it logging to 'info_log_path=' only.
What specific logging option for LDA?.. Seems to work exactly the same
as in v1.2:
protocol lda {
info_log_path = /tmp/deliver.log
}
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] v2.0.beta3 released
Am 22.02.2010 um 16:29 schrieb Timo Sirainen:
What specific logging option for LDA?.. Seems to work exactly the same
as in v1.2:
protocol lda {
info_log_path = /tmp/deliver.log
}
Ah ok. Thought all logging ought to be configured in 'logging.conf' as there
was no example in 'lda.conf'. Since I switched to lmtp delivery yesterday,
would it also be possible to have a different logging path for that?
Thanks
Thomas
Re: [Dovecot] v2.0.beta3 released
On 22.2.2010, at 19.49, Thomas Leuxner wrote:
Am 22.02.2010 um 16:29 schrieb Timo Sirainen:
What specific logging option for LDA?.. Seems to work exactly the same
as in v1.2:
protocol lda {
info_log_path = /tmp/deliver.log
}
Ah ok. Thought all logging ought to be configured in 'logging.conf' as there
was no example in 'lda.conf'.
No, the config files were split only to hopefully make them easier to manage.
You can put any settings anywhere you want.
Since I switched to lmtp delivery yesterday, would it also be possible to
have a different logging path for that?
Nope. It would be now much simpler to implement it though. log daemon would
just need to support reading/using separate config for each service. Maybe it
could even be implemented in less than 50 lines of code..
Re: [Dovecot] v2.0.beta3 released
Am 22.02.2010 um 18:53 schrieb Timo Sirainen: Since I switched to lmtp delivery yesterday, would it also be possible to have a different logging path for that? Nope. It would be now much simpler to implement it though. log daemon would just need to support reading/using separate config for each service. Maybe it could even be implemented in less than 50 lines of code.. Maybe an option going forward. Thanks
Re: [Dovecot] v2.0.beta3 released
On 22.2.2010, at 19.53, Timo Sirainen wrote: Nope. It would be now much simpler to implement it though. log daemon would just need to support reading/using separate config for each service. Maybe it could even be implemented in less than 50 lines of code.. Oh, actually not. The difficult part is that Dovecot just doesn't support logging to multiple files (with same severity) in a same process. The logging code would have to be abstracted out before that would be possible.
Re: [Dovecot] v2.0.beta3 released
Am 22.02.2010 um 18:59 schrieb Timo Sirainen: Oh, actually not. The difficult part is that Dovecot just doesn't support logging to multiple files (with same severity) in a same process. The logging code would have to be abstracted out before that would be possible. Actually I like the idea of having a separate delivery log with lmtp. Any idea?
Re: [Dovecot] v2.0.beta3 released
On 22.2.2010, at 20.19, Thomas Leuxner wrote: Am 22.02.2010 um 18:59 schrieb Timo Sirainen: Oh, actually not. The difficult part is that Dovecot just doesn't support logging to multiple files (with same severity) in a same process. The logging code would have to be abstracted out before that would be possible. Actually I like the idea of having a separate delivery log with lmtp. Any idea? Some syslog could do that.
Re: [Dovecot] v2.0.beta3 released
Hi,
this is the first 2.0 build I tested, and I haven't been following the 2.0
threads very closely. This said I'm puzzled whether 'protocols = imap' does
what it should. It also enables a listener for IMAPS on port 993, different to
what 1.2 series did. I had to manually disable the IMAPS part by setting its
port to 0.
# 2.0.beta3: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
mail_location = maildir:~/maildir
namespace {
hidden = no
inbox = yes
location =
prefix =
separator = /
type = private
}
namespace {
list = yes
location =
maildir:/var/vmail/public:CONTROL=~/maildir/public:INDEX=~/maildir/public
prefix = Public/
separator = /
subscriptions = no
type = public
}
passdb {
args = username_format=%u /var/vmail/conf.d/%d/passwd
deny = no
driver = passwd-file
master = no
pass = no
}
plugin {
acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300
quota = dict:user::file:%h/maildir/dovecot-quota
quota_rule = *:storage=1GB
quota_rule2 = Trash:storage=10%%
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_global_dir = /var/vmail/conf.d/%d/sieve-scripts
}
postmaster_address = postmas...@leuxner.net
protocols = imap
service auth {
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
}
service imap-login {
inet_listener imap {
address = xxx.xxx.xxx.xxx
port = 143
}
inet_listener imaps {
port = 0
}
}
ssl_cert = /etc/ssl/certs/spectre_leuxner_net_2009.crt
ssl_key = /etc/ssl/private/spectre_leuxner_net_2009.key
userdb {
args = username_format=%u /var/vmail/conf.d/%d/passwd
driver = passwd-file
}
verbose_proctitle = yes
Regards
Thomas
Re: [Dovecot] v2.0.beta3 released
On Sat, 2010-02-20 at 23:41 +0100, Thomas Leuxner wrote: this is the first 2.0 build I tested, and I haven't been following the 2.0 threads very closely. This said I'm puzzled whether 'protocols = imap' does what it should. It also enables a listener for IMAPS on port 993, different to what 1.2 series did. I had to manually disable the IMAPS part by setting its port to 0. Yes, that's intentional. imaps isn't a protocol. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v2.0.beta3 released
Am 21.02.2010 um 07:16 schrieb Timo Sirainen: Yes, that's intentional. imaps isn't a protocol. Thanks Timo. Has the specific logging option for the LDA been dropped? I see it logging to 'info_log_path=' only. Regards Thomas
