[Tickets #6739] Re: Allow email address in an admin-defined header field to be added to Whitelist/Blacklist

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6739
------------------------------------------------------------------------------
  Ticket             | 6739
  Updated By         | ryan at lsit.ucsb.edu
  Summary            | Allow email address in an admin-defined header field to
                     | be added to Whitelist/Blacklist
  Queue              | IMP
  Version            | 4.2-RC4
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
+New Attachment     | custom_header_session.patch
------------------------------------------------------------------------------


ryan at lsit.ucsb.edu (2008-07-02 18:26) wrote:

Chuck - Attached patch which uses $_SESSION instead of a loop.

Matt - Well, it's for any case where the SMTP envelope sender (which  
ends up in the Return-Path header) differs from the From header value.  
In order of prevalence, our users seem to use message blacklisting  
mostly for semi-spam bulk mailings, then for actual spam messages that  
slip through Spamassassin for whatever reason, then for pesky humans  
using poorly configured MTAs or doing other ill-advised things.

The current system is almost entirely useless for us right now as bulk  
mailings and spam seem to rarely have the same SMTP envelope sender &  
from.