Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Mathias Tausig (mathias.tausiga-cert.at)
Date: Fri Sep 11 2009 - 08:29:26 CDT
Am Freitag, den 11.09.2009, 08:38 -0400 schrieb Wietse Venema:
> Mathias Tausig:
> > Am Donnerstag, den 10.09.2009, 10:18 -0400 schrieb Wietse Venema:
> > [...]
> > > This is an output buffering problem. You need to flush output
> > > after each reply, perhaps by calling the flush() function.
> > >
> > Hy!
> > No, I am afraid that this is not the problem.
> > I am sendig you a few details of my setup
> > Here is my php script test.php:
> > <?php
> > error_reporting(E_ALL);
> > fprintf(STDOUT, "220 localhost SMTP foo test\n");
> According to the SMTP protocol spec (RFC 5321), SMTP terminates
> lines with <CR><LF>, not with newline characters. And it has other
> features, such as multi-line replies, and magical handling of lines
> beginning with the "." character, that you should be aware of when
> before writing SMTP software.
I just tried to replace the "\n" with "\r\l", but to no avail. The same
I also watched the exact reply given by my (working) c++ program, and
that terminates its linex with 0xa, a new line.
Apart from that, you are probably right, I should read the RFC. I hoped
I could soare the hassle, since I am not planning to right something