hi all.
we've had a toaster up and running for quite some time now, just handling three domains.
we are trying to move to a system where all mail will be handled by the
ISP and it will then be forwarded to our current qmail install. in
trying to prep for this, the rcpthost and local file was modified. in
doing so, no mail is getting delivered and the /var/log/qmail/current
file has stopped getting updated.
before i tear down the entire setup and reinstall from scratch, i was hoping to get some guidance on the current mess.
here is the (mangled) setup:
[EMAIL PROTECTED] control]# more locals mail.domain-1.com domain-2.com
[EMAIL PROTECTED] control]# more rcpthosts domain-3.com domain-2.com mail.domain-1.com domain-1.com
[EMAIL PROTECTED] control]# more defaultdomain domain-1.com
[EMAIL PROTECTED] control]# more me mail.domain-1.com
[EMAIL PROTECTED] control]# more defaultdelivery ./Maildir/
the machine itself is mail.domain-1.com. it needs to be able to receive mail addressed to mail.domain-1.com and domain-1.com. that's it.
in order to do this, i did the following:
rcpthosts and locals/ mail.domain-1.com domain-1.com
defaultdomain mail.domain-1.com
me mail.domain-1.com
all permissions are set correctly - they have not been chnaged since the system was working properly. however qmail stat:
[EMAIL PROTECTED] control]# qmailctl stat /service/qmail-send: up (pid 31811) 8695 seconds /service/qmail-send/log: up (pid 3650) 0 seconds /service/qmail-smtpd: up (pid 3028) 76 seconds /service/qmail-smtpd/log: up (pid 3647) 0 seconds messages in queue: 133 messages in queue but not yet preprocessed: 24
none of the logging mechanisms are staying up, nor is the "current" file getting any updates. before this died, every message getting delivered was showing " Unable_to_chdir_to_maildir._(#4.2.1)/" for all users at domain-1.com and mail.domain-1.com.
is there something glaringly incorrect with the setup? is there somehting i can check to get the logs running again?
thanks much, and my apologies for this long email.
ps axwwwwf | grep read
That should tell you what readproctitle says, which should explain the log problem. Sure looks like a permissions issue to me, though.
Bill
