[Tickets #12659] Re: Horde SMTP sends empty EMail if PIPELINING is used...

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12659
------------------------------------------------------------------------------
  Ticket             | 12659
  Updated By         | Git Commit <commits at lists.horde.org>
  Summary            | Horde SMTP sends empty EMail if PIPELINING is used...
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Git Commit <commits at lists.horde.org> (2013-09-05 16:55) wrote:

Changes have been made in Git (master):

commit aca52bf6d1e07b04ec77d6bb61af8e5a6111c192
Author: Michael M Slusarz <slusarz at horde.org>
Date:   Thu Sep 5 10:41:43 2013 -0600

     [mms] Fix aborting a pipelined DATA command if only a subset of  
recipients were rejected (Bug #12659).

     See: http://www.imc.org/ietf-smtp/mail-archive/msg02687.html

     The RFC 2920 text is a bit vague.  Servers must issue a 554 if ALL
     recipients are rejected.  This might not happen until after the DATA
     command is sent though (which is why we were sending empty DATA data).
     Unfortunately, *partial* rejection of recipients will NOT abort the DATA
     command. Since we don't pre-verify mail recipients, we want to catch the
     case if ANY recipients are bad, since the user generally is expecting
     that all e-mail addresses provided will have the message sent to.  This
     means we can't pipeline DATA.

  framework/Smtp/lib/Horde/Smtp.php |   49  
++++++++++++++++++-------------------
  framework/Smtp/package.xml        |    2 +
  2 files changed, 26 insertions(+), 25 deletions(-)

http://git.horde.org/horde-git/-/commit/aca52bf6d1e07b04ec77d6bb61af8e5a6111c192