Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.2.2.20010306111913.00aaf260@nexus> X-Sender: cygwin AT nexus X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 06 Mar 2001 11:26:45 -0500 To: "Malcolm Boekhoff" , "Cygwin News Group" From: Scott Steeves Subject: Re: Does "syslogd" work? In-Reply-To: <016901c0a647$02e56210$275c100a@actfs.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed >I thought I could use the syslogd daemon to get some idea of what >ssmtp is >doing, but when I type "syslogd&" at the bash prompt, the command >starts and >exits immediately! Have you tried strace to see exactly what ssmtp is doing? How about some kind of sniffer, like WinDump? Are you talking to an Exchange server? (You mentioned MS...) If so, do they have POP3 enabled? Can you telnet to the server on port 110 and see what you get? And again on port 25? (If either connects just type "help" to verify the connection and then "quit" to exit.) There's a lot of things that could be happening here, and in my experience syslog/event logs are the worst place to look to see what is happening. strace is great, but might be difficult to interpret and outputs a lot of data. It will tell you if ssmtp can't find a config file or something, or can't resolve the address, and all sorts of "underneath" things you generally can't see. Verifying connectivity to the services is easiest with telnet. Packet sniffing might not really tell you anything, but it will let you know if data is coming back from the server. Scott -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple