I'm using dnsfq because I'm using /etc/rc.d/init.d/qmail-pop3d.init. I'm
using /etc/rc.d/init.d/qmail-pop3d.init because that's what README.qmail-run
said. I'm using README.qmail-run because I had no other instructions that
referenced starting qmail-pop3d.
If something's wrong with my DNS, I'm not aware of what exactly it is.
"Hard error" doesn't give any clues. Is there source to dnsfq? Perhaps by
examining what it considers a "Hard error" I can discover what it might
think is wrong with my DNS.
----- Original Message -----
From: Jon Rust <[EMAIL PROTECTED]>
To: Shawn P. Stanley <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, December 03, 1999 11:47 AM
Subject: Re: starting qmail-pop3d
> At 9:39 PM -0600 12/2/99, Shawn P. Stanley wrote:
> >It's definately /var/qmail/bin/dnsfq giving the "Hard error" message, in
> >response to:
> >
> > /var/qmail/bin/dnsfq spigot.nbs-inc.com
> >
> >I can't find any help on dnsfq. Any ideas?
>
> Why are you using dnsfq? Just hard code your FQDN into your start
> script. My pop3d daemon is started using svscan (daemtools 0.63) with
> this run script:
>
> mail:/var/qmail/supervise/pop3d{53} # cat run
> #!/bin/sh
>
> QMAILDUID=`id -u qmaild`
> NOFILESGID=`id -g qmaild`
>
> exec tcpserver -R -x/etc/tcp.pop3d.cdb 0 pop3
/var/qmail/bin/qmail-popup
> mail.vcnet.com /var/qmail/bin/checkpoppasswd
/var/qmail/sbin/relay-ctrl-allow
> /var/qmail/bin/qmail-pop3d Maildir
>
>
> (That last part is all one line)
>
> Although, the fact that dnsfq can't establish your FQDN tells me
> something's wrong with DNS on your system.
>
> Jon
