Al,
Don't give me to much credit ;-). I found all this on the following link:
DSpam POSTFIX INTEGRATION - LedHed's Wiki
<https://wiki.ledhed.net/index.php/DSpam_POSTFIX_INTEGRATION>
As far as Procmail is concerned you're only checking for a header
inserted by the Content filter call (Postfix->Dspam->Postfix). If you
check the source of an email you should find this header which Procmail
is only checking for, below:
X-DSPAM-Result: Spam
X-DSPAM-Processed: Fri Dec 5 08:25:22 2025
X-DSPAM-Confidence: 0.9928
X-DSPAM-Improbability: 1 in 13789 chance of being ham
X-DSPAM-Probability: 1.0000
X-DSPAM-Signature: 15,6932f9623786159238293068
I think your correction to the Procmail filter looks good if I understand
Procmail correctly.
You could also run Dspam in your procmail script then check the header tag:
another option.
Eric
On 12/5/2025 9:29 AM, Al wrote:
On Thu, 4 Dec 2025, Eric Broch wrote:
Right off the bat change
DeliveryProto LMTP
to
DeliveryProto SMTP
And
ChangeUserOnParse on
to
ChangeUserOnParse full
I made these changes and it is working now. I can't believe that I had
worked on this for days and you seen the problem with the first email.
Also when running procmail I've never seen these settings for dspam
(what is -p and -e flags) :
| /usr/local/bin/dspam -p -e
I don't know what they mean either. I copied this from another mail
server that at one time was using dspam. It is not working, I am
considering using something like:
:0 * ^X-DSPAM-Result: Spam {
:0
* ^X-DSPAM-Confidence: 0\.(9|8[5-9])
superspam/
:0
spam/
}
Kind Regards,
Al
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
