Bug 7070

Summary:	My SMTP server rejects Busybox SENDMAIL request
Product:	Busybox	Reporter:	Dev Ashis Negi <devashish.negi>
Component:	Networking	Assignee:	unassigned
Status:	NEW ---
Severity:	normal	CC:	busybox-cvs, devashish.negi
Priority:	P5
Version:	1.15.x
Target Milestone:	---
Hardware:	All
OS:	Linux
Host:		Target:
Build:

Description Dev Ashis Negi 2014-05-05 22:21:46 UTC

I am using busybox sendmail version v1.15.3. Using sendmail After the SYN-ACK-ACK TCP handshake, the first message busybox sendmail issues is "NOOP". This appears to be against RFC 2821 section 3.2

3.2 Client Initiation

   Once the server has sent the welcoming message and the client has
   received it, the client normally sends the EHLO command to the
   server, indicating the client's identity.
   
For my customer, his SMTP server rejects the busybox sendmail client request, as it does not want the client to send anything per section 3.2.   Please let me know if it is a RFC violation and if there is any workaround for this problem.

The packet capture logs are attached.

Comment 1 Dev Ashis Negi 2014-05-05 22:31:39 UTC

The packet capture file can be accessed from below link. 
Please note the 4rth packet after SYN-ACK-ACK is NOOP and is before EHLO. 

https://www.dropbox.com/sh/460gu07nscbh6nu/L9ySg0fU9X

Comment 2 Dev Ashis Negi 2014-05-08 18:44:47 UTC

Can someone confirm if it is a deliberate behavior by sendmail to send NOOP after TCP handshake?

Also if someone could please confirm if busybox bugzilla is operational. I see no activity here. Then I wouldn't wait to check its status. 

Thanks.