[Dovecot] POP3 says no new mail.
Hi Let's list some files in user homedir:
dog:/home/domain/users/username# ls autoresponse dovecot.index.log dovecot-uidvalidity.4be1e480 saved trash config dovecot-uidlist new sent cur dovecot-uidvalidity tmp dog:/home/domain/users/username# ls cur 1273093948.30793.dog:2 dog:/home/domain/users/username# ls new 1273097763.13545.dog 1273118766.1674.dog
As you can see one mail is in cur and two new mails are in new folder. Let's fetch them via pop3:
dog:/home/domain/users/username# nc -v localhost 110 localhost.localdomain [127.0.0.1] 110 (pop3) open +OK Dovecot ready. user username@domain.pl +OK pass secret +OK Logged in. stat +OK 1 7824 quit +OK Logging out. dog:/home/domain/users/username#
It said there is only one mail. Where are my new mails? Let's check log file:
May 6 07:42:46 dog dovecot: POP3(username@domain.pl): Effective uid=1002, gid=1002, home=/home/domain/./users/username May 6 07:42:46 dog dovecot: POP3(username@domain.pl): maildir: data=/home/domain/./users/username May 6 07:42:46 dog dovecot: POP3(username@domain.pl): maildir++: root=/home/domain/./users/username, index=, control=, inbox=/home/domain/./users/username May 6 07:42:46 dog dovecot: POP3(username@domain.pl): Namespace : Using permissions from /home/domain/./users/username: mode=0700 gid=-1 May 6 07:42:46 dog dovecot: pop3-login: Login: user=username@domain.pl, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 6 07:42:52 dog dovecot: POP3(username@domain.pl): Disconnected: Logged out top=0/0, retr=0/0, del=0/1, size=7824
No error logged looking at the good dir. Permissions OK. When I remove dovecot.index.log new messages appears:
dog:/home/domain/users/username# rm dovecot.index.log dog:/home/domain/users/username# nc -v localhost 110 localhost.localdomain [127.0.0.1] 110 (pop3) open +OK Dovecot ready. user username@domain.pl +OK pass secret +OK Logged in. stat +OK 3 76974 quit +OK Logging out. dog:/home/domain/users/username#
Any clue what can it be?
dovecot -n # 1.2.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.22 i686 Debian 5.0.4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_process_per_connection: no mail_privileged_group: mail mail_location: maildir:%h mail_debug: yes mmap_disable: yes mail_nfs_index: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %f auth default: passdb: driver: checkpassword args: /usr/local/bin/checkvpw-dovecot-wrapper userdb: driver: prefetch
On Thu, 2010-05-06 at 08:42 +0200, Hubert Jastrzębski wrote:
No error logged looking at the good dir. Permissions OK. When I remove dovecot.index.log new messages appears:
Did you solve this? Sounds like new/ directory's mtime doesn't change when new files are added there.
On Thu, 2010-05-06 at 08:42 +0200, Hubert Jastrzębski wrote:
No error logged looking at the good dir. Permissions OK. When I remove dovecot.index.log new messages appears:
Did you solve this? Sounds like new/ directory's mtime doesn't change when new files are added there.
I putted index in memory: mail_location = maildir:%h:INDEX=MEMORY And heard no complains from sers. But you are right - files in new/ are sometimes newer than new/ directory itself. I have to investigate why is that. Thanks for clue.
Hubert Jastrzębski
On Thu, 2010-05-27 at 10:09 +0200, Hubert Jastrzębski wrote:
But you are right - files in new/ are sometimes newer than new/ directory itself. I have to investigate why is that. Thanks for clue.
Linux JFS at least used to have such bug. If you find out the cause, I'd be interested in knowing what others have it.
participants (2)
-
Hubert Jastrzębski
-
Timo Sirainen