in reply to Re: Socket weirdness
in thread Socket weirdness

After some more testing, this seems to be the problem.

If I print "250 QUEUED - 123"

or "250 QUEUED(250) - 1084263071 qp 4221"

then everything works, but if I send:

"250 QUEUED(250) - 8c3d931926ca4e8a9dfea84f06dbdc1a"

then the client won't receive the above 250 response line. The 32 hexacharacter part is a GUID which I produce randomly using 16 bytes retrieved everytime from /dev/urandom. Now why would a proxy or a firewall regard a random 32 hexadecimal character as suspicious and block/filter it?

Replies are listed 'Best First'.
Re: Re: Re: Socket weirdness
by traveler (Parson) on May 20, 2004 at 15:12 UTC
    There may be a length limit. RFC2822 says the limit should be 998 chars, but I dunno about the actual software. Of course, 2822 does not really apply. The issue is 821. Check RFC821 appendix E for a discussion of replies...