<div class="gmail_quote">
<div> </div>
<div> </div>
<div>It did help, thanks Andrew. Found out reading Postfix's <a href="http://main.cf">main.cf</a> that the use of lmtp is encouraged instead of the cyrus agent</div>
<div> </div>
<div>
<div>Guess the tcp socket is just usefull in a case like yours with multiple MTAs, right ?</div></div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> # at least one LMTP is required for delivery<br> lmtp cmd="/usr/local/cyrus/bin/lmtpd" listen="lmtp" prefork=1 maxchild=100<br>
lmtpunix cmd="/usr/local/cyrus/bin/lmtpd" listen="/var/run/cyrus/socket/lmtp" prefork=1<br><br></blockquote>
<div> </div>
<div> </div>
<div>So, to make it short. Postfix and Cyrus comunicate via lmtp and lmtpd (cyrus) is responsible for mailbox delivery.</div>
<div> </div>
<div>Thanks again</div>
<div>Diego</div>
<div> </div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">This provides an lmtpd listening on a local unix socket and an lmtpd listening on the lmtp tcp socket. You can also specify that lmtpd listen on a tcp socket on localhost only.<br>
<br>Depending on your mail architecture, you may be running an MTA (Postfix, Sendmail, etc) on 1 or more remote hosts to spread the load and provide redundancy. That's how we do it at OSU. Those MTAs then make LMTP connections to the Cyrus server(s) to deliver mail to the message store. By the way, lmtpd is also responsible for Sieve mail filter processing on message delivery.<br>
<br>I hope this helps!<br><br> Andy<br></blockquote></div><br>