FreeBSD Mail Server
peter at circlesquared.com
Thu Feb 17 20:06:52 GMT 2005
On Thu, 2005-02-17 at 11:59 -0800, Joshua Lewis wrote:
> What if there is a problem starting one of the servers? Should I look at
> /var/dmesg ? Or is there a different log to look at?
> Thank you,
> Joshua Lewis
> Peter Risdon
> > On Thu, 2005-02-17 at 10:48 -0800, Joshua Lewis wrote:
> >> Do I need to have a *_enable="YES" line in my rc.conf in order to start
> >> my
> >> courier-imap-pop3 and courier-imap-imap servers? Or do I have to enable
> >> inetd?
> > Yup. The full set, if you include the secure versions too is:
> > courier_imap_imapd_ssl_enable="YES"
> > courier_imap_imapd_enable="YES"
> > courier_imap_pop3d_ssl_enable="YES"
> > courier_imap_pop3d_enable="YES"
> > It's worth reading /usr/local/etc/rc.d/blah.sh for any port you install.
> > inetd is not the right way to start these ports.
> > Then to start them up without a reboot, do
> > /usr/local/etc/rc.d/blah.sh start
> > But you do need the rc.conf entries first.
> >> I have been pulling my hair out for weeks trying to setup my first mail
> >> server using how toos from high5.net and workaround.org.
> >> I have tried to look in /var/log for any log files that could indicate
> >> why
> >> I can not pick up mail. But I don't see any log files at all so I
> >> suspect
> >> they are not running. The server accepts mail fine I just can't pick it
> >> up. I donÿt know if it matters but I am trying to setup virtual domains
> >> with no local system accounts.
> > How? You might also need:
> > courier_authdaemond_enable="YES"
> > in /etc/rc.conf
> >> Including the domain of the computer itÿs
> >> self. Does that affect anything? Again I can accept e-mail fine so I
> >> donÿt
> >> expect it does.
> >> I can't figure out if courier is running. I recall a command like "ps
> >> -aw
> >> |grep imap" but I don't think I am using the correct switches because I
> >> am
> >> not getting what I am expecting.
> > $ ps xa | grep courier
> > 19223 p2 S+ 0:00.00 grep courier
> > 526 con I 0:00.00 /usr/local/sbin/courierlogger
> > -pid=/usr/local/var/spool/authdaemon/pid -st
> > 527 con I 0:00.06 /usr/local/libexec/courier-authlib/authdaemond
> > 535 con I 0:00.03 /usr/local/libexec/courier-authlib/authdaemond
> > 536 con I 0:00.03 /usr/local/libexec/courier-authlib/authdaemond
> > 537 con I 0:00.03 /usr/local/libexec/courier-authlib/authdaemond
> > 538 con I 0:00.02 /usr/local/libexec/courier-authlib/authdaemond
> > 539 con I 0:00.03 /usr/local/libexec/courier-authlib/authdaemond
> > 548 con I 0:00.01 [couriertcpd]
> > 552 con I 0:00.00 /usr/local/sbin/courierlogger imapd-ssl
> > 561 con I 0:00.01 [couriertcpd]
> > 565 con I 0:00.00 /usr/local/sbin/courierlogger imapd
> > 573 con I 0:00.01 [couriertcpd]
> > 576 con I 0:00.00 /usr/local/sbin/courierlogger pop3d-ssl
> > 585 con I 0:00.01 [couriertcpd]
> > 588 con I 0:00.00 /usr/local/sbin/courierlogger pop3d
> > Also try
> > #telnet localhost 110
> > and so on for all the pop3 and imap ports. If courier is running, you'll
> > get something like:
> > #telnet localhost 110
> > Trying ::1...
> > Connected to your.host.name.com.
> > Escape character is '^]'.
> > +OK Hello there.
> > Telnetting to the port is good because you can then talk pop/imap and
> > diagnose any other probs.
> > Peter.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions