[JAMES-375] RFC 1854 - Command Pipelining support

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.3.0, 3.0.0
• Fix Version/s: 2.3.0
• Component/s: SMTPServer
• Environment: james-trunk
• Assignee: Unassigned
• Reporter: Stefano Bagnara
• Created: 19/May/05 02:15
• Updated: 21/Nov/07 08:31
• Resolved: 05/Jun/05 01:03

Description

James currently does not ANNOUNCE RFC 1854 - Command Pipelining.

I also does not support PIPELINING after the DATA command. By RFC this is not an issue because DATA should be the last command in a pipeline but I preferred to fix the double buffering issue in the stream pipeline by changing the CRLFTerminatedReader to not buffer (the InputStream we read is already buffering).

ANNOUNCE support is easy (one line of code) once you apply my smtpserver patch for the AUTH support. I didn't add the patch here because it was conflicting.

Issue Links

• is part of: JAMES-380 ESMTP Compliance fix
• is related to: JAMES-72 SMTP Handler DATA buffering issue