Index: [Article Count Order] [Thread]

Date:  Tue, 10 Oct 2006 16:13:05 +0100
From:  "Vapor" <bluequartz (at mark) vaporised.com>
Subject:  [coba-e:07512] dovecot oddness + vsite creation error
To:  coba-e (at mark) bluequartz.org
Message-Id:  <20061010143242.M54106 (at mark) vaporised.com>
In-Reply-To:  <44E222AD.4010708 (at mark) schneiderheim.com>
References:  <002a01c6764c$f6132640$6400a8c0 (at mark) COMPUTER8SD7ER2> <054b01c6bfba$500672e0$010510ac (at mark) gregg> <200608141128.56624.lesmith (at mark) ecsis.net> <018901c6c099$9c6b12f0$010510ac (at mark) gregg> <44E222AD.4010708 (at mark) schneiderheim.com>
X-Mail-Count: 07512

I had a real weirdy earlier on a yum updated box running 4.2 (somewhere about there).

This box is setup to run a single domain only, and subs of that domain only (ns's/www/
tld).

Email to subdomains worked fine, but email to anything (at mark) tld.com went straight to /root/
mbox -  literally. I checked this list, triple checked every post, nothing, no matter 
what I tried it went straight there, did not pass go or collect £200.

Also, I have no additional admin users on that box, just the default "admin" user. 
Email is set to forward to an external email address, this also never worked and also 
arrived firmly in /root/mbox.

So I was on my merry way uninstalling dovecot to revert to previous email server 
(qpopper?) when on doing a "yum remove dovecot" it picked up and selected for uninstall 
a batch of dependences:

base-bluequartz-capstone
base-user-capstone
base-bluequartz-glue
base-vsite-capstone
base-email-capstone

This rang an immediate bell regarding the issue of the error I got when (first time 
only) creating a vsite (see other thread).

To cut a long story short, I reinstalled dovecot via yum and then the above dependences 
(some installed themselves with dovecot, but not all, oddly, can't remember which, as 
always I was rushing by then). Restarted sendmail + dovecot, then rebooted the box at 
that point.

Past this point email is arriving where it should and the creating vsite error has gone.

No idea whether this sheds any light for folks, or will even help - worth mentioning 
though I thought just in case.

Brett