inconsistent SPF warning

[Julian Field]

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Matt Kettler wrote:

> At 04:33 AM 12/9/2004, Julian Field wrote:
>
>> >> Yes.  After which SA apparently sometimes chooses to use an
>> address form
>> >> some other header instead.
>> >
>> > Something worth testing might be to move the envelope_sender_header
>> setting
>> > out of spam.assassin.prefs.conf and into local.cf.
>> >
>> > It could be that some of the new spamd semantics that reset the
>> user_prefs
>> > after each message might be tripping up MailScanner. If it
>> happened,the
>> > result would be that a given MailScanner child only uses the
>> > spam.assassin.prefs.conf for the first message it handles, then
>> reverts to
>> > local.cf only until it was killed and respawned.
>>
>> But MailScanner doesn't use spamd...
>
>
> This is true, and I'm well aware of it. I chose poor wording.
>
> The problem I'm speaking to would not affect anyone actually using spamd,
> it only affects those using the perl API. ie: MailScanner.
>
> MailScanner does not use spamd, however, MailScanner uses the SA Perl
> API.
> That API is also used by spamd, and there are aspects of the API which
> are
> intentionally designed to support the needs of spamd. These
> spamd-specific
> semantics of the API can impact MailScanner when they change.
>
> I was specifically referring to semantics in the perl API that
> accommodate
> spamd's need to have the user_prefs unloaded after each message. I've not
> studied how they are implemented in SA 3.0, but they are in fact new
> to 3.0
> (older spamd's didn't prefork thus didn't need clearing, 3.0 does prefork
> and re-use children.) If MailScanner doesn't reload
> spam.assassin.prefs.conf each time a message is fed to the API, those
> settings could be unloaded automaticaly by the APIs internals.
>
> Of course, this is all speculation, I've not checked the code, but it's
> based on a reasonably good knowledge of how spamd and MailScanner work.

How, in the SA 3.0 API, do I stop it from unloading
spam.assassin.prefs.conf after each message? Or, if I can't do that, how
do I make it re-read it? I would obviously rather do the former.

--
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!