> > I was using diald on another client machine (which I no longer have
> > access to) that came from an rpm. I'm not sure of it's origin, but I
> > was able to use the debug 31 command to see what triggers were in
> > effect and what actual filter rule they were due to. I could also send
> > a customer kill sig (usr1 or usr2 I think) and I was able to dump the
> > current rule table. This also doesn't work. Can any one tell me what
> > the differences between version and debugging are and if I'm using the
> > right version?
>
> Check that /etc/syslogd.conf is set to write debug messages
> somewhere. Current diald writes most debug messages to syslog
> with a level of "debug" (possibly occasionally "info"). This
> may not have been the case in the past?
ding!
That sounds quite plausible, I'll look into it!
> > My actual problem (which I'm unable to solve as I have no useful
> > debugging info) is that diald brings up the link when an internal
> > machine pops email off the server via ethernet (which is the diald
> > machine also)
>
> This is probably because the pop/imap server does a reverse
> look up on the client's address. Configure one or both of
> your /etc/hosts and local name server correctly. (Possibly
> also NIS and LDAP servers for the truely advanced :-) )
Okies, I'm running a /etc/hosts file on that machine.
> > If I put a specific `ignore tcp.smtp` for source and
> > dest then pop stops working
>
> This doesn't make sense. SMTP and POP are completely separate
> protocols operating on different ports. Preventing SMTP from
> bringing the link up *can't* just stop POP!
Sorry, typo. I meant pop3! twas late!
Cheers
Alex!
--
Alex Garner <[EMAIL PROTECTED]>
NetCraft Australia
Phone (08) 8370 3650
http://www.netcraft.com.au
...I should have taken the blue pill.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
