[SA-exim] "Couldn't get Connecting IP header X-SA-Exim-Connect-IP" error message

Matt Bostock matt at mattbostock.com
Sun Dec 10 21:54:50 PST 2006


Marc,

I ran spamassassin -t -D on a temporarily reject messaged in /var/spool/exim/SAtempreject and got:

[5256] dbg: plugin: loading Greylisting from /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Plugin/Greylisting.pm
[5256] dbg: plugin: registered Greylisting=HASH(0x8b63f64)
... and then ...
[5256] dbg: plugin: registering glue method for greylisting (Greylisting=HASH(0x8b63f64))
[5256] dbg: GREYLISTING: called function
[5256] dbg: GREYLISTING: running greylisting on <zio4me.squirrel at 213.239.xxx.xxx>, since score is too low (13.387) and you configured greyl
isting to greylist anything under 9999
[5256] dbg: GREYLISTING: computed greylisting on tuplet, saved info in /var/spool/sa-exim/tuplets/91/76/88/anne at evilspammerdomain.com/anne
@example.com and whitelist status is 0

Now here's an interesting bit - the tuplets *aren't* being written to during normal operation, but they are when I run the 'spamassassin -t D' command. I have the tuplets directory chowned to spamd:spamd and chmod 770. Should the tuplets dir be chowned to the exim user and group?

Many thanks,
Matt




More information about the SA-Exim mailing list