Bug 689085 - pop3(roman): Error: user roman: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/roman
Summary: pop3(roman): Error: user roman: Initialization failed: mail_location not set ...
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dovecot
Version: 14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-19 08:02 UTC by Roman Melihhov
Modified: 2011-03-21 20:54 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2011-03-21 20:54:14 UTC


Attachments (Terms of Use)

Description Roman Melihhov 2011-03-19 08:02:54 UTC
Description of problem:

Can't read POP3 mail. Mail files locations set in dovecot.conf 
Authentication works but mail read failed with error in logfile


Version-Release number of selected component (if applicable):

dovecot-2.0.11-1.fc14.x86_64

How reproducible:

repeated

Steps to Reproduce:
1. dovecot.conf 
mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=MEMORY

2. access mail from evolution with SSL on
3. authentication succeeded but mail fetch failed with following in logfile
  
Actual results:

in maillog
-------------
pop3-login: Login: user=<roman>, method=PLAIN, rip=, lip=, mpid=2771, TLS
dovecot: pop3(roman): Error: user roman: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/roman
dovecot: pop3(roman): Error: Invalid user settings. Refer to server log for more information.
--------------

Expected results:

reading POP3 mail

Additional info:

Comment 1 Roman Melihhov 2011-03-21 20:54:14 UTC
I'd solved this one. It appears webmin dovecot module was writing settings at /etc/dovecot.conf while dovecot v 2.0.11 was trying to read  settings from /etc/dovecot/dovecot.conf

run 

dovecot -n 

to see the settings. Hope this helps many others too...


Note You need to log in before you can comment on or make changes to this bug.