Hey John,
is your mail client and What's Up Gold on the same machine?
If not, your tcpserver might not be open to relaying from the What's
Up Gold machine. If they are both on the same machine and the email
client works, then I'm going to guess that What's Up Gold tries
to send email with lines or blank lines that are not terminated
with <carriage return><line feed> which qmail dumps off for whatever
reason. I had some cgi scripts that just did a carriage return
after each line while building the header of the email message and
they resulted in a status=256 from tcpserver when trying to send.
Fortunately they were perl so I just edited them and fixed the
problem, you might not have such luck with What's Up Gold. You
might be able to request a fix for that from IPSwitch though if
that is the problem because the <cr><lf> is a reasonable request.
Any chance you have some type of packet sniffer to watch what it's
sending?
Good luck,
Dave
-----Original Message-----
From: John Steniger [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 21, 2000 4:40 PM
To: '[EMAIL PROTECTED]'
Subject: tcpserver return codes
I'm having an issue which I believe is tcpserver; I've searched the archives
and haven't found anything.
I have qmail up and running under tcpserver, and using a client like Outlook
I am able to both send mail and recieve mail (using pop3 protocol).
However, I have a network monitoring tool (What's Up Gold) which can be
configured to send email messages. When I specify my qmail server as the
SMTP server, and attempt to test, I get immediate failure.
The fact that it fails immediately without logging any information into my
mail log at all pointed me to tcpserver and not qmail as the culprit. I did
a tail -f on the /var/qmail/log/qmail-smtp/current log during a couple
tests: I sent a normal email message through outlook and then tested the
monitoring tool's email configuration. The first email went through
successfully, while the second test of the configuration failed (as
expected). The only difference in the current log was the return code that
tcpserver output: for the first generic email test, I got a return code of
0, whereas for the second test of the monitoring tool, I got a return of
256. Both the email and the monitoring tool email originated from the same
machine.
Has anyone had this issue, with qmail interacting differently with an
application other than a mail client? I'd appreciate any help.
Thanks
