> > I tried to do that earlier but postfix says:
> >
> > Feb 5 07:40:35 trinity postfix/lmtp[602]: D8D9F43E8D: to=<[EMAIL PROTECTED]>,
> > orig_to=<test>, relay=none, delay=1, status=deferred (connect to
> > /var/run/cyrus/socket/lmtp[/var/run/cyrus/socket/lmtp]: Permission denied)
> >
> > I look at the lmtp socket and :
> > rwxrwxrwx 1 root root 0 Feb 5 07:39 /var/run/cyrus/socket/lmtp
>
> Chances are your postfix is configured to run within a chroot jail. For
> example, I have postfix in a chroot jail then set the following in my
> Cyrus imapd.conf file:
>
> lmtpsocket: /var/spool/postfix/socket/lmtp
Actually, I don't think I've ever seen Postfix's lmtp configured to run chroot. I think with 'lmtpunix' you need to make sure that 'prefork' is set to at least 1 in cyrus.conf, otherwise the socket doesn't get created. (Someone please tell me if this is wrong.)
I've been able to get lmtp to work in a chrooted environment. Took a lot of troubleshooting and use of 'truss' to figure out what was going on, but I did get it to work.
Here is a good link to check out:
http://www.comedia.it/~bluca/postfix/CYRUS_README
I dont think you need to have the lmtp process run chrooted, especially after reading the article above.
What I would do is trace your smtpd process using a trace program (You said you use Debian...strace or ktrace should be available via apt-get I believe). Do that, check the output. That is how I was able to find out my initial problems when I was working with cyrus and postfix.
Hope that helps.
Jason
--- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
