On 2008-10-20 13:18:03 -0400, Chris Lewis wrote:
> Hanno Hecker wrote:
> > On Mon, 20 Oct 2008 10:42:17 -0400
> > "Chris Lewis" <[EMAIL PROTECTED]> wrote:
> >
> >> For some reason, SpamAssassin insists on inserting its headers at the
> >> _beginning_ of the header block, whereas all the others ins
Hanno Hecker wrote:
> On Mon, 20 Oct 2008 10:42:17 -0400
> "Chris Lewis" <[EMAIL PROTECTED]> wrote:
>
>> For some reason, SpamAssassin insists on inserting its headers at the
>> _beginning_ of the header block, whereas all the others insert theirs at
>> the end. Obviously, I'd prefer they all did
On Mon, 20 Oct 2008 10:42:17 -0400
"Chris Lewis" <[EMAIL PROTECTED]> wrote:
> For some reason, SpamAssassin insists on inserting its headers at the
> _beginning_ of the header block, whereas all the others insert theirs at
> the end. Obviously, I'd prefer they all did it at the end.
Only the spam
I'm running qpsmtpd head (or thereabouts) async. Both Linux and Solaris.
The behaviour I am reporting has _always_ been present through many
previous iterations of qpsmtpd and "stock" spamassassin plugin. I'm
only now trying to figure out how to get it swatted.
I'm not sure at this point where
