[Tickets #13453] Re: IMP Hooks pre_sent

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13453
------------------------------------------------------------------------------
  Ticket             | 13453
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | IMP Hooks pre_sent
  Queue              | IMP
-Version            | 6.2.1
+Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-08-18 17:47) wrote:

This was intentional, because the hook is called AFTER recipient  
checks are done.  So adding additional recipients could possibly  
exceed those limits.  (The hook was originally designed as a way to  
add headers, rather than alter existing headers).

That being said... I guess it should be up to the admin to determine  
if they want to exceed the various resource limits by adding  
addresses/attachments/etc.

This is going to take a bit of work though, since the address parsing  
code is separate from the code where the hook is called - we are going  
to have to reparse the address headers if the hook exists in order to  
pick up the correct list of recipients.  (Note that this has nothing  
to do with the Bcc header - any address header will not pick up any  
changes made in the hook).