On 8/2/2013 3:25 AM, Nigel Smith wrote: >> Probably a namespace issue. The imap daemon is telling you there's not >> new mail. So wherever it's looking it sees no mail. So either it's >> looking in the wrong place, and the configuration isn't correct. Error >> logs will inform you about the latter, 'dovecot -n' about the former. >> Show dovecot client connection and error logging, and dovecot -n. > > Hi Stan, > > Unfortunatley not.
Unfortunately you failed to provide 'dovecot -n' output which makes assisting you much more difficult. Providing this is standard operating procedure. > As demonstrated in my initial post, I can do : > > #cat > /srv/mail/ops.example.com/test/new/1375430267.M868397P2192.ukc-vm02-mx01\,S\=477\,W\=486 > > And the debug shows the MUA looking in the same place (forgot to include the > Dovecot MUA debug earlier) : > > Aug 2 09:01:09 ukc-vm02-mx01 postfix/anvil[2642]: statistics: max connection > rate 1/60s for (smtp:192.168.198.199) at Aug 2 08:57:17 > Aug 2 09:01:09 ukc-vm02-mx01 postfix/anvil[2642]: statistics: max connection > count 1 for (smtp:192.168.198.199) at Aug 2 08:57:17 > Aug 2 09:01:09 ukc-vm02-mx01 postfix/anvil[2642]: statistics: max cache size > 1 at Aug 2 08:57:17 > Aug 2 09:03:38 ukc-vm02-mx01 dovecot: imap-login: Login: > user=<t...@ops.example.com>, method=PLAIN, rip=192.168.198.199, > lip=79.170.177.71, mpid=2667, TLS > Aug 2 09:03:38 ukc-vm02-mx01 dovecot: imap(t...@ops.example.com): Debug: > Effective uid=1001, gid=1001, home=/ > Aug 2 09:03:38 ukc-vm02-mx01 dovecot: imap(t...@ops.example.com): Debug: > maildir++: root=/srv/mail/ops.example.com/test, index=, control=, > inbox=/srv/mail/ops.example.com/test, alt= > Aug 2 09:03:51 ukc-vm02-mx01 dovecot: imap(t...@ops.example.com): > Disconnected: Logged out bytes=26/599 All of this logging isn't telling us anything. Seeing your configuration should. Given that Dovecot relies on indexes for everything it does, including listing of INBOX and mailbox contents, the fact that you're not seeing new mail is likely due to an index problem of some sort, either misconfiguration or corrupion, etc. Unfortunately all I can do is make general educated guesses about your problem because you refuse to provide your 'dovecot -n' output. -- Stan
