Dan White schrieb: > On 23/06/11 22:12 +0200, Klemens Puritscher wrote: > >Hello, > > > >I'm using cyrus-imapd(currently 2.3.16) for many years and I'm quiet > happy with it. > >Now I'm testing the new 2.4.9 version - SRPMS from Simon Matter. > > > >Based on historical reasons the lmtpd should run on port 26. > >...but the lmtpd didn't start. > >Only when I use the standard port 24 it will work. > > > >My "/etc/cyrus.conf": > > > >That works: (lmtpd processes starts an listen on port 24) > > lmtp cmd="lmtpd -a" listen=24 prefork=5 maxchild=200 > > > >that not: (no lmtpd starts...) > > lmtp cmd="lmtpd -a" listen=26 prefork=5 maxchild=200 > > > >The same with pop3d (for testing...): > >That works: > > pop3 cmd="pop3d" listen=110 prefork=3 > > > >That works not: (no pop3d starts...) > > pop3 cmd="pop3d" listen=110 prefork=3 > > What error are you seeing in syslog with this configuration? > Try running master with '-D'. > > Do you see port 26 open in the output of: > > netstat -an | grep LISTEN No. > Do you experience the same problem if you use: > > lmtp cmd="lmtpd -a" listen="lmtp" prefork=5 maxchild=200 > > and then update your /etc/services with an lmtp entry for port 26? Yes, that was my "normal" configuration. I've changed the lmtp port from 24 to 26 in /etc/services and uses the service-name. Now, I've already found the bug. The init.d script by Simon Matter makes the problem. When I use `/usr/lib/cyrus-imapd/cyrus-master -C /etc/imapd.conf -M /etc/cyrus.conf -p /var/run/cyrus-master.pid -d` at the CLI, then is no problem: the lmtpd listen on port 26. Now I must check the init-script... thanks for you reply. kr Klemens > -- > Dan White ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
