Hello Rick, RB> No errors. Of course, no response either. Nothing happening... I'm RB> looking into xinetd for a moment.
Well, we would have gotten to asking about xinetd when we got to the POP problem... B-) If xinetd is a problem, though, you'll see an error when dbmail-pop3d tries to start - something about unable to bind to the port, because something else (xinetd) has control of it already. Same for dbmail-imapd, because the default setting for xinetd is to hang onto both ports 110 and 143. RB> Alas... Let me go find a Postfix forum and read up. If you're seeing no error messages from postfix when it starts up, but the Windows box can't connect to port 25, make sure that the Windows box doesn't have some form of firewall running, or virus scanner. Both Norton and Trend (and presumably others) have scanners that will silently wedge themselves as proxies between Outlook/Outlook Express and POP/IMAP servers, redirecting the connections to 127.0.0.1, and then making the "real" connection to the server themselves... And they're sometimes REALLY DUMB about how to log in properly. Outlook will think it has a valid connection, but won't reach the server. -- Jeff Brenton Vice President, Engineered Software Products, Inc http://espi.com Questionable web page: http://dididahdahdidit.com Liberalism grants you the freedom to advocate any idea*. * Please see http://www.dididahdahdidit.com/except.php for a current list of exceptions
