These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for dovecote setup error on the new forum.
Web Hosting and Cloud Computing Control Panels
Hey Dan,
I'm not sure where you're setting the configuration options you mention.
By default, we don't use mbox format mail spools at all (they're slower with large volumes of mail, can throw quotas off, make it difficult to use @ in usernames, and make backups and restores more of a challenge). Maildir is the preferred format, and what we setup by default (and Dovecot should automatically know this).
So, where are you seeing a "no inbox" error?
--
Check out the forum guidelines!
Oh, the noinbox error is when I try to do a remote pop3 login
Hi Joe,
I'm trying a restored yirtual server from the slackware server, and the references to mbox, Maildir, mail etc always throw me as I've never really gotten it straight.
mbox is standard sendmail as far as I know, and unfortunately I really don't know the diff. I can probably go with Maildir and /var/spool/mail ( with some directions) as Usermin has matured to finding the folders other than inbox. Though the Dovecot wiki warns about the dot lock files as possible trouble ( again more ignorance here).
Sorry, I was more worried about getting the slave records to fly that I forgot to make sure the mail would fly before the T3 dropped.
We should be able to get this fast with identical boxes on identical OS.
thanks,
Hey Dan,
Oh, OK, it's a migration we're talking about. In that case, you can stick with mbox. /var/spool/mail is the normal location for mbox mail spools.
There are scripts to convert between mbox and Maildir, but it's not all that important. There are solutions to all of the issues with mbox except performance on large spools and having @ in usernames under Postfix (but you use Sendmail, I seem to recall? So that one won't come up).
BTW-The mail spool format is independent of the MTA. It can be limited by the delivery agent, but most folks use procmail for delivery with Sendmail, and it supports both mbox and Maildir spool types.
What's in the maillog when this trouble occurs?
I suspect Dovecot is trying to find mail in /var/spool/mail and not finding it, or possibly trying to find it in ~/Maildir (this is one of the benefits of Maildir...it lives in the users home directory).
--
Check out the forum guidelines!
Hi Joe,
Still haven't got this one figured, yet and outside of re-entering all users by hand I'm in a pickle. I'm still ending up with pop attempts failing due to no INBOX
First off, Dovecot won't allow changes to the mail files module. It's set to automatic and every attempt to change fails (even when I had changed the mail location in the script). Read the wiki.dovecot and that left me even more confused. THe only time I can get it to work is if I delete the migrated user and re-enter the user.
I'm migrating from virtualmin GPL backup and wondered if that had anythign to do with it. The "homes" dir ended up in publc_html and the contents never made it to the new "homes" dir
Itried inserting some mail log here but it won't take.
Actually I'm beginning to see the whole migration process was screwy, as I tried to login a virtual server admin and it won't take the password.
A long night of hand grinding toniight :-(
Hi Dan,
It sounds like the cause may be a mismatch between the mail file location on the old system, and the location on the new server.
If you create a domain on the new system and add a mailbox to it, does its mail file get created under /var/mail or at ~newmailboxuser/Maildir ?
--
Check out the forum guidelines!
Hi,
Okay,
still no go on the POP. Dovecot does login then leave, finding no mail. So I deleted the server altogether and beginning from scratch.
sendmail is set up for delivery to /var/spool/mail
mailfile directory is Maildir
mail is delivered to /var/spool/mail/username and can be usermin and readmail but dovecot does find it.
the home directory structure is:
/homes/user/Maildir
/cur
/dovecot.index
/dovecot.index.cache
/dovecot.index.log
/new
/temp
I need to underscore that dovecot won't let me change the locations but stays at automatic discovery.
Help please, the wolves are at the door after 4 days without mail :-(
Dan
If you have mail delivered to /var/spool/mail/$user, then Dovecot can be configured to use this path by editing /etc/doveconf.conf and changing the default_mail_env line to :
default_mail_env = mbox:/var/spool/mail/%u
Then restart it with /etc/init.d/dovecot restart
--
Check out the forum guidelines!