Re: "Couldn't get Connecting IP header X-SA-Exim-Connect-IP" error message

> Off hand, I'm not too sure then.
> Your best bet is to put some debugging prints around the 
> error in the perl module.
> You could also take one mail you received, make sure it has 
> the headers, save it to disk, and run it through spamassassin 
> -t -D < /tmp/mail and see what happens

Hi Marc,

The plot thickens...

I've done some debugging in greylisting.pm and have it set to print out
*all* headers to the logs just before it looks for X-SA-Exim-Connect-IP.
After checking the logs, it appears that the X-SA-Exim-* headers aren't
being added by the local_scan patch by the time greylisting.pm is
called. Oddly enough, although greylisting (and tuplets) aren't working,
the emails are being saved to /var/spool/exim/SA* and *do* have the
X-SA-Exim-* headers there.

Does that make sense?

Many thanks,
Matt

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.26/597 - Release Date:
21/12/2006