On 09/03/15 18:32, Viktor Dukhovni wrote: > On Thu, Sep 03, 2015 at 04:07:09PM -0400, Phil Stracchino wrote: > >>>> /^Content-Transfer-Encoding:/i PREPEND X-Clacks-Overhead: GNU Terry >>>> Pratchett >>>> PREPEND X-Clacks-Overhead: GNU Iain M. Banks >>> >>> That won't work either. >> >> I didn't think so. So my only option is to combine both into a single >> header and figure out the best way to format it, I assume. > > Why must you use "Content-Transfer-Encoding" as the prepend point? > What if that header is not present? A content-filter or milter > can insert multiple headeres more easily.
Well, I don't have to, I suppose. That was the header used in the minimal configuration example suggested. I assumed someone had put some thought into why that particular header. I suppose if it were important that X-Clacks-Overhead actually be added to every message, I could go look up the RFCs and trigger it off one of the headers that is required to always be present. But it isn't that important. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: 603.293.8485
