| Summary | Procmail Driver doesn't support special "TO_" header |
| Queue | Ingo |
| Queue Version | 1.0.1 |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | ben (at) |
| Requester | derek (at) battams (dot) ca |
| Created | 02/25/2005 (7455 days ago) |
| Due | |
| Updated | 05/08/2005 (7383 days ago) |
| Assigned | 02/27/2005 (7453 days ago) |
| Resolved | 05/08/2005 (7383 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
I also added support for "special" headers like this on a per-driver
basis. That way, 'Destination' shows up in the list for procmail
rules, but not for others.
State ⇒ Assigned
New Attachment: procmail_dest.patch.txt
decided not to add the "Destination" header as an option in
config/fields.php since I wasn't sure of the impact it would have on
the other backends. Therefore my patch relies on the user specifying
a user defined header called "Destination", which will implement the
TO_ header syntax in the generated procmailrc file. An ideal patch
would actually include this Destination header as part of the listed
options and act accodingly.
State ⇒ Accepted
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Procmail Driver doesn't support special "TO_" header
Queue ⇒ Ingo
MISCELLANEOUS
If the regular expression contains `^TO_' it will be substituted by
`(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope
|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)', which should catch
all destination specifications containing a specific address.
My procmailrc files (and those of some users of mine) rely on this
feature. Perhaps an option can be added to the drop down list of
fields called "Destination" or something that makes use of this
special header expression?