On Tue, 4 Oct 2011, Frank Leonhardt wrote:
On 04/10/2011 14:41, John Hardin wrote:
On Tue, 4 Oct 2011, Frank Leonhardt wrote:
So, doing this using the actual rule and an actual header it *does*
work. It's only
when its run through the milter that it fails to match
Frank Leonhardt wrote:
So, doing this using the actual rule and an actual header it *does*
work. It's only when its run through the milter that it fails to match.
Yep. The Received: header on a milter-using system is added *after* the
milter processing is complete.
Any processing that wants
On 04/10/2011 14:41, John Hardin wrote:
On Tue, 4 Oct 2011, Frank Leonhardt wrote:
So, doing this using the actual rule and an actual header it *does*
work. It's only when its run through the milter that it fails to match.
Are you attempting to match the Received: header added by your MTA?
Y
On Tue, 4 Oct 2011, Frank Leonhardt wrote:
So, doing this using the actual rule and an actual header it *does* work.
It's only when its run through the milter that it fails to match.
Are you attempting to match the Received: header added by your MTA?
Your MTA may not have added the Received:
On 04/10/2011 01:58, RW wrote:
On Mon, 03 Oct 2011 23:12:57 +0100
Frank Leonhardt wrote:
I'm having a great deal of trouble writing a rule to match something
in a Received: header. The problem is that sendmail(?) is whitespace
wrapping the header. In other words, instead of:
Headers are conver
On Mon, 03 Oct 2011 23:12:57 +0100
Frank Leonhardt wrote:
> I'm having a great deal of trouble writing a rule to match something
> in a Received: header. The problem is that sendmail(?) is whitespace
> wrapping the header. In other words, instead of:
Headers are converted into a single line befo
I'm having a great deal of trouble writing a rule to match something in
a Received: header. The problem is that sendmail(?) is whitespace
wrapping the header. In other words, instead of:
Received: from [192.168.1.31] (mux.example.com [1.2.3.4]) by
mail.example.com (8.14.4/8.14.4) with ESMTP id
