[Dovecot] How to log POP3 events
Hello all,
Thanks for your help getting me started. I have Dovecot running now.
When I troubleshoot customer email problems, I need to be able to see the number of emails they popped.
In /var/log/maillog, Dovecot just tells me that they authenticated, but not what happened after they authenticated. With pop3d, I saw how many emails they popped. Can I set that in Dovecot? I checked the documentation and couldn't find anything. I also turned on the "auth_verbose = yes" and "auth_debug = yes" -- but as the name implies, I only got more authentication info. Nothing about files tranferred.
Thanks,
Cliff
Cliff Hayes wrote:
With pop3d, I saw how many emails they popped. Can I set that in Dovecot? I checked the documentation and couldn't find anything.
Yes, there's some very detailed POP3 logging options, but you need the Dovecot-1.0 series (Dovecot-1.0-alpha4 is the latest, and is pretty stable).
Mind you, I'd quite like the same sort of logging for IMAP (I may have a go at a patch sometime, if Timo doesn't beat me to it!).
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Chris,
My policy has always been not to use alphas or betas on production systems.
What's the projection for Dovecot coming out of beta?
Cliff
---------- Original Message ----------- From: Chris Wakelin c.d.wakelin@reading.ac.uk To: Cliff Hayes chayes@afo.net Cc: dovecot@dovecot.org Sent: Thu, 03 Nov 2005 00:35:59 +0000 Subject: Re: [Dovecot] How to log POP3 events
Cliff Hayes wrote:
With pop3d, I saw how many emails they popped. Can I set that in Dovecot? I checked the documentation and couldn't find anything.
Yes, there's some very detailed POP3 logging options, but you need the Dovecot-1.0 series (Dovecot-1.0-alpha4 is the latest, and is pretty stable).
Mind you, I'd quite like the same sort of logging for IMAP (I may have a go at a patch sometime, if Timo doesn't beat me to it!).
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- -+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 ------- End of Original Message -------
I'd tend to agree, but Timo is quite conservative with version numbers.
We're running "Dovecot-1.0-stable" in production, which was a "frozen" version of "Dovecot-1.0-testXX" series with important bugfixes backported.
In practice, Dovecot-1.0-alpha4 has less bugs, and is probably now the most "stable" 1.0 version (I'd consider it at least a beta, or even a release candidate). There are lots of bugs in 0.99.x that probably aren't going to get fixed.
Best Wishes, Chris
chayes@afo.net wrote:
Chris,
My policy has always been not to use alphas or betas on production systems.
What's the projection for Dovecot coming out of beta?Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Ok, I'm going to go for it then. From what I read in the docs, I don't think I need to change anything in the Dovecot.conf
However, the problem I always have with using binaries on my Fedora systems is when I start out using an integrated product (like Dovecot, which comes with Fedora and all I have to do is type "chkconfig dovecot on" and all the initial configuration is done for me). And then I upgrade using a binary (instead of the Fedora preferred update path using YUM or an RPM) and end up with two versions of the same program on the computer in two different locations--many times both are started during boot up.
Should I "chkconfig dovecot off" then load the binary? Or will the binary put the software where Fedora expects it and overwrite what I have now?
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 4:05 AM To: chayes@afo.net Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
I'd tend to agree, but Timo is quite conservative with version numbers.
We're running "Dovecot-1.0-stable" in production, which was a "frozen" version of "Dovecot-1.0-testXX" series with important bugfixes backported.
In practice, Dovecot-1.0-alpha4 has less bugs, and is probably now the most "stable" 1.0 version (I'd consider it at least a beta, or even a release candidate). There are lots of bugs in 0.99.x that probably aren't going to get fixed.
Best Wishes, Chris
chayes@afo.net wrote:
Chris,
My policy has always been not to use alphas or betas on production systems. What's the projection for Dovecot coming out of beta?
Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Chris,
I loaded Alpha 4 and now I'm back to square one. Can't authenticate.
I've turned off Dovecot .99 (chkconfig dovecot off, service dovecot stop), and am using the /usr/local/sbin/dovecot to start
I know I'm editing the correct config file (/usr/local/etc/dovecot.conf) because I changed the name and dovecot noticed.
I've made the following changes to dovecot.conf
protocols = pop3 ssl_disable = yes default_mail_env = default_mail_env = mbox:/tmp:INBOX=/var/spool/mail/%u:INDEX=MEMORY mail_extra_groups = mail passdb shadow
When I try to pop from Outlook Express, it keeps prompting me for a password.
HELP!
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 4:05 AM To: chayes@afo.net Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
I'd tend to agree, but Timo is quite conservative with version numbers.
We're running "Dovecot-1.0-stable" in production, which was a "frozen" version of "Dovecot-1.0-testXX" series with important bugfixes backported.
In practice, Dovecot-1.0-alpha4 has less bugs, and is probably now the most "stable" 1.0 version (I'd consider it at least a beta, or even a release candidate). There are lots of bugs in 0.99.x that probably aren't going to get fixed.
Best Wishes, Chris
chayes@afo.net wrote:
Chris,
My policy has always been not to use alphas or betas on production systems. What's the projection for Dovecot coming out of beta?
Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
You need to change more than that! See the Wiki for details
http://wiki.dovecot.org/moin.cgi/UpgradingDovecot
In particular, the syntax for authdb and passwd has changed, so start with dovecot-example.conf as it suggests and make the equivalent changes to those you made for 0.99.x
Chris
Cliff Hayes wrote:
Chris,
I loaded Alpha 4 and now I'm back to square one. Can't authenticate.
I've turned off Dovecot .99 (chkconfig dovecot off, service dovecot stop), and am using the /usr/local/sbin/dovecot to start
I know I'm editing the correct config file (/usr/local/etc/dovecot.conf) because I changed the name and dovecot noticed.
I've made the following changes to dovecot.conf
protocols = pop3 ssl_disable = yes default_mail_env = default_mail_env = mbox:/tmp:INBOX=/var/spool/mail/%u:INDEX=MEMORY mail_extra_groups = mail passdb shadow
When I try to pop from Outlook Express, it keeps prompting me for a password.
HELP!
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 4:05 AM To: chayes@afo.net Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
I'd tend to agree, but Timo is quite conservative with version numbers.
We're running "Dovecot-1.0-stable" in production, which was a "frozen" version of "Dovecot-1.0-testXX" series with important bugfixes backported.
In practice, Dovecot-1.0-alpha4 has less bugs, and is probably now the most "stable" 1.0 version (I'd consider it at least a beta, or even a release candidate). There are lots of bugs in 0.99.x that probably aren't going to get fixed.
Best Wishes, Chris
chayes@afo.net wrote:
Chris,
My policy has always been not to use alphas or betas on production
systems.
What's the projection for Dovecot coming out of beta?
Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Chris,
Believe it or not, I did all that. I read the upgrading doc. There really isn't anything there that applies to me. Also, before I even emailed you, I did as instructed and used the sample file as a base, altering it based on my previous conf file.
Furthermore, I looked in the conf file itself for help. Did everything that I thought applied to me (changes shown in original email below).
Pardon my frustration, but the front page of dovecot.org says this...
Dovecot is easy to set up and doesn't require special maintenance. Only thing you need is to get the authentication working properly - if your users are in /etc/passwd there's hardly anything you have to do.
...which is exactly what I have. Yet I have had enormous problems with set up the first time, now I get to start all over again. I couldn't get it to work the first time until you gave me this for the .conf file:
default_mail_env = mbox:/tmp:INBOX=/var/spool/mail/%u:INDEX=MEMORY
Now, with the new version, does that change?
Oh, by the way, here's my ./configure options:
./configure --with-pop3d --with-passwd --with-shadow
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 10:27 AM To: Cliff Hayes Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
You need to change more than that! See the Wiki for details
http://wiki.dovecot.org/moin.cgi/UpgradingDovecot
In particular, the syntax for authdb and passwd has changed, so start with dovecot-example.conf as it suggests and make the equivalent changes to those you made for 0.99.x
Chris
Cliff Hayes wrote:
Chris,
I loaded Alpha 4 and now I'm back to square one. Can't authenticate.
I've turned off Dovecot .99 (chkconfig dovecot off, service dovecot stop), and am using the /usr/local/sbin/dovecot to start
I know I'm editing the correct config file (/usr/local/etc/dovecot.conf) because I changed the name and dovecot noticed.
I've made the following changes to dovecot.conf
protocols = pop3 ssl_disable = yes default_mail_env = default_mail_env = mbox:/tmp:INBOX=/var/spool/mail/%u:INDEX=MEMORY mail_extra_groups = mail passdb shadow
When I try to pop from Outlook Express, it keeps prompting me for a password.
HELP!
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 4:05 AM To: chayes@afo.net Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
I'd tend to agree, but Timo is quite conservative with version numbers.
We're running "Dovecot-1.0-stable" in production, which was a "frozen" version of "Dovecot-1.0-testXX" series with important bugfixes backported.
In practice, Dovecot-1.0-alpha4 has less bugs, and is probably now the most "stable" 1.0 version (I'd consider it at least a beta, or even a release candidate). There are lots of bugs in 0.99.x that probably aren't going to get fixed.
Best Wishes, Chris
chayes@afo.net wrote:
Chris,
My policy has always been not to use alphas or betas on production
systems.
What's the projection for Dovecot coming out of beta?
Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
So what do you have for passdb and userdb?
They should look something like
auth default { mechanisms = plain
passdb shadow { }
userdb passwd { }
...
(Earlier versions of 1.0, e.g. 1.0-stable, have just
passdb shadow userdb passwd
)
Chris Cliff Hayes wrote:
Chris,
Believe it or not, I did all that. I read the upgrading doc. There really isn't anything there that applies to me. Also, before I even emailed you, I did as instructed and used the sample file as a base, altering it based on my previous conf file.
Furthermore, I looked in the conf file itself for help. Did everything that I thought applied to me (changes shown in original email below).
Pardon my frustration, but the front page of dovecot.org says this...
Dovecot is easy to set up and doesn't require special maintenance. Only thing you need is to get the authentication working properly - if your users are in /etc/passwd there's hardly anything you have to do.
...which is exactly what I have. Yet I have had enormous problems with set up the first time, now I get to start all over again. I couldn't get it to work the first time until you gave me this for the .conf file:
default_mail_env = mbox:/tmp:INBOX=/var/spool/mail/%u:INDEX=MEMORY
Now, with the new version, does that change?
Oh, by the way, here's my ./configure options:
./configure --with-pop3d --with-passwd --with-shadow
Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Yes, that's what I have. I also found this:
userdb prefetch { }
I must have missed that, so I commented that out and still had the same problem.
There is also this
user = root
in the auth default section.
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 11:27 AM To: Cliff Hayes Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
So what do you have for passdb and userdb?
They should look something like
auth default { mechanisms = plain
passdb shadow { }
userdb passwd { }
...
(Earlier versions of 1.0, e.g. 1.0-stable, have just
passdb shadow userdb passwd
)
Chris,
Believe it or not, I did all that. I read the upgrading doc. There really isn't anything there that applies to me. Also, before I even emailed you, I did as instructed and used the sample file as a base, altering it based on my previous conf file.
Furthermore, I looked in the conf file itself for help. Did everything
Chris Cliff Hayes wrote: that
I thought applied to me (changes shown in original email below).
Pardon my frustration, but the front page of dovecot.org says this...
Dovecot is easy to set up and doesn't require special maintenance. Only thing you need is to get the authentication working properly - if your users are in /etc/passwd there's hardly anything you have to do.
...which is exactly what I have. Yet I have had enormous problems with set up the first time, now I get to start all over again. I couldn't get it to work the first time until you gave me this for the .conf file:
default_mail_env = mbox:/tmp:INBOX=/var/spool/mail/%u:INDEX=MEMORY
Now, with the new version, does that change?
Oh, by the way, here's my ./configure options:
./configure --with-pop3d --with-passwd --with-shadow
Cliff
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Hmm, so what appears in the logs when you fail to authenticate? Have you tried the "debug" POP client :) ?
telnet server 110
+OK University of Reading POP3 Server USER chris +OK PASS chrispassword +OK Logged in LIST 1 +OK 1 1234 QUIT +OK Logging out.
Chris
Cliff Hayes wrote:
Yes, that's what I have. I also found this:
userdb prefetch { }
I must have missed that, so I commented that out and still had the same problem.
There is also this
user = root
in the auth default section.
Cliff
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 11:27 AM To: Cliff Hayes Cc: dovecot@dovecot.org Subject: Re: [Dovecot] How to log POP3 events
So what do you have for passdb and userdb?
They should look something like
auth default { mechanisms = plain
passdb shadow { }
userdb passwd { }
...
(Earlier versions of 1.0, e.g. 1.0-stable, have just
passdb shadow userdb passwd
)
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
participants (3)
-
chayes＠afo.net
-
Chris Wakelin
-
Cliff Hayes