[Kolab-devel] Does anybody actually have a log file from lmtp on his server?

Gunnar Wrobel wrobel at pardus.de
Mon Feb 18 13:48:37 CET 2008


Bernhard Reiter <bernhard at intevation.de> writes:

> On Tuesday 13 November 2007 15:41, Gunnar Wrobel wrote:
>>  grep lmtp /kolab/etc/imapd/cyrus.conf
>
> grep lmtp /local-vol1/kolab-2.*/etc/imapd/cyrus.conf 
> /local-vol1/kolab-2.0/etc/imapd/cyrus.conf:  lmtpunix   cmd="lmtpd" 
> listen="/kolab/var/kolab/lmtp" prefork=0
> /local-vol1/kolab-2.0/etc/imapd/cyrus.conf:  lmtp          cmd="lmtpd -a" 
> listen="127.0.0.1:2003"
> /local-vol1/kolab-2.1/etc/imapd/cyrus.conf:  lmtpunix   cmd="lmtpd" 
> listen="/kolab/var/kolab/lmtp" prefork=0
> /local-vol1/kolab-2.1/etc/imapd/cyrus.conf:  lmtp          cmd="lmtpd -a" 
> listen="127.0.0.1:2003"
> /local-vol1/kolab-2.2/etc/imapd/cyrus.conf:  lmtpunix   cmd="lmtpd" 
> listen="/kolab/var/kolab/lmtp" prefork=0
> /local-vol1/kolab-2.2/etc/imapd/cyrus.conf:  lmtp          cmd="lmtpd -a" 
> listen="127.0.0.1:2003"
>
>>  grep lmtp /kolab/etc/fsl/fsl.imapd
>
> grep lmtp /local-vol1/kolab-2.*/etc/fsl/fsl.imapd
> /local-vol1/kolab-2.0/etc/fsl/fsl.imapd:ident (lmtpd)/.+ q{
> /local-vol1/kolab-2.0/etc/fsl/fsl.imapd:            
> path="/kolab/var/imapd/log/lmtpd.log",
> /local-vol1/kolab-2.0/etc/fsl/fsl.imapd:ident (lmtpunix|squatter)/.+ q{
> /local-vol1/kolab-2.1/etc/fsl/fsl.imapd:ident (lmtpd)/.+ q{
> /local-vol1/kolab-2.1/etc/fsl/fsl.imapd:            
> path="/kolab/var/imapd/log/lmtpd.log",
> /local-vol1/kolab-2.1/etc/fsl/fsl.imapd:ident (lmtpunix|squatter)/.+ q{
> /local-vol1/kolab-2.2/etc/fsl/fsl.imapd:ident (lmtpd)/.+ q{
> /local-vol1/kolab-2.2/etc/fsl/fsl.imapd:            
> path="/kolab/var/imapd/log/lmtpd.log",
> /local-vol1/kolab-2.2/etc/fsl/fsl.imapd:ident (lmtpunix|squatter)/.+ q{
>
> I upgraded those systems in place, 
> so maybe an old configuration got transfered or so.

Hm, weird. If the service is named "lmtp" then fsl should not match it
with "lmtpd" and I would expect no log file.

In any case I think that the new config cannot hurt since it always
uses "lmtp" which would also match "lmtpd".

On my current RC2 test installation everything looks fine. But if
anybody does have no /kolab/var/imapd/log/lmtpd.log on a server >=RC1,
please let me know.

Cheers,

Gunnar

>
> -- 
> Managing Director - Owner: www.intevation.net       (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
> Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




More information about the devel mailing list