After upgrading from Ubuntu 12.04 to 14.04 when I log into dovecot with the web interface, Thunderbird, or my blackberry phone I am unable to see mail or folders that are supposed to be there. I can see Postfix receiving mail, SpamAssassin filters it, and then everything is done. Just no mail in my inbox. Logging into Dovecot does not generate any errors.
After the upgrade, I am running Dovecot V2.2.9
I have gone through the logs and the only error(s) that pop up are: in /var/mail/mail.err: Jul 2 20:36:18 cerberus dovecot: imap-login: Error: read(anvil) failed: EOF Jul 2 22:14:50 cerberus dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Jul 2 22:14:50 cerberus dovecot: message repeated 4 times: [ auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory]
The read(anvil) error only appeared twice, the others will repead as long as SMB password synchronization in 'pam-auth-update' is enabled. This will also appear in mail.log.
I am not currently seeing any other errors. I can include any log / conf files you like. I would include a bunch now, but fear plugging this up with unnecessary files.
Any help would be greatly appreciated.
Comments
Submitted by andreychek on Thu, 07/02/2015 - 23:31 Comment #1
Howdy -- what is the output of this command:
dovecot -n
Also, the error that you mentioned above -- does that error occur when a user is trying to log in? Or is that just an error that you noticed in the logs, but not at the exact time of the attempted login?
Submitted by tripkin on Thu, 07/02/2015 - 23:48 Comment #2
Thanks!
dovecot -n produces this:
2.2.9: /etc/dovecot/dovecot.conf OS: Linux 3.13.0-55-generic i686 Ubuntu 14.04.2 LTSlog_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = 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 = } passdb { driver = pam } passdb { driver = pam } protocols = imap pop3 service auth { user = root } ssl_ca = </etc/dovecot/dovecot.ca.pem ssl_cert = </etc/dovecot/dovecot.cert.pem ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/dovecot/dovecot.key.pem userdb { driver = passwd } userdb { driver = passwd } protocol imap { imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDP LUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS mail_max_userip_connections = 20 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }
Testing reveals that if I have SMB password synchronization enabled, then those errors show up during user logins. I am the only user and I have multiple email accounts that I monitor from my phone and Thunderbird, so when either of the devices connects they login for each account.
Submitted by andreychek on Fri, 07/03/2015 - 00:33 Comment #3
Ah, it looks like the Dovecot config may have been overwritten during the upgrade.
You'd want to make sure that the mail_location line within Dovecot reads as follows:
mail_location = maildir:~/Maildir
It looks like currently, it's set to look for mbox mail folders, rather than the Maildir ones setup by default.
After changing that setting, you'd want to restart Dovecot, which you can do with this command:
service dovecot restart
Submitted by tripkin on Fri, 07/03/2015 - 01:01 Comment #4
That is weird, because the only uncommented mail_location line in dovecot.conf is the one you gave - so I am going to look through all the .conf files to see where the other line comes up that supersedes the correct one.
EDIT: Found it in 10-mail.conf. Which conf file should I use for the declaration, or does it matter? For now I will comment out the entry in 10-mail.conf.
EDIT: Whew! Thank you for your help, got all my mail back and all is right with the world again!
Submitted by tripkin on Fri, 07/03/2015 - 01:02 Comment #5
I am closing this as solved, thankfully simple once I knew what to look for. I was sooooo close!
Thank you for your assistance!
Submitted by andreychek on Fri, 07/03/2015 - 09:16 Comment #6
Great, I'm glad you were able to get that working! Feel free to let us know if you have any additional questions.