Dovecot Log Missing re Email with Postfix, Dovecot and MySQL
I have been working through the tutorial "Email with Postfix, Dovecot and MySQL on Debian 6 (Squeeze)" I have reached the section for "Check Your Logs"
and I have no file for "/home/vmail/dovecot-deliver.log". There's nothing there. If i skip ahead to the next section, I am asked to cd to "/home/vmail/example.com/sales/Maildir" but I only have an empty "/home/vmail/". I've searched to see if I can figure out how to figure this out from logs but I do not see anything useful in terms of where to look. Without any error message, it's a mystery!
What I may have done wrong:
1. I followed all directions not as root but as a user with acces to sudo, using it when necesary
2. When I got to using mailx, mailx was not installed. I installed mailutils via apt-get.
Would appreciate any insight or even clues on where to look for clues.
Thanks,
atrowbri
2 Replies
1) sudo su - vmail
2) cd /home/vmail
3) touch filetest.txt
Can you create the file in step 3)?
I have all this working with MySQL and I think I had to create the directories manually like /home/vmail/example1.com, example2.com.
Is dovecot running? "sudo service dovecot status"
Check the logs at /var/log.
@jebblue:
Try this:
1) sudo su - vmail
2) cd /home/vmail
3) touch filetest.txt
Can you create the file in step 3)?
I have all this working with MySQL and I think I had to create the directories manually like /home/vmail/example1.com, example2.com.
This worked and I went ahead and created the directories.
> Is dovecot running? "sudo service dovecot status"
Yes, it was.
> Check the logs at /var/log.
I found this error message in mail.warn:
postfix/trivial-rewrite[914]: warning: do not list domain arrayproject.com in BOTH mydestination and virtualmailboxdomains
So I deleted the listing in mydestination and ended up getting the mail in the vmail directory, where it should be! Not sure whether I needed to create the directories by hand or not but I'll experiment with the next email address I add and see. I had not seen the logs in /var/logs though, so your heads up lead to the fix that seems to have fixed it, thanks!