Spamassassin Catching Encrypted Emails?

[ztrauq]

This is a weird one...

 

I use a form-mailer script on my site called SouperMail. One of the features of this mailer is the ability to encrypt messages to a PGP key before sending them. From there, they are sent to an email account on my domain that I check through POP.

 

Recently, one of the emails was flagged by SpamAssassin as possible spam. Here are the spam values that it listed:

 

pts rule name description

---- ---------------------- --------------------------------------------------

0.3 NO_REAL_NAME From: does not include a real name

0.7 ADDR_NUMS_AT_BIGSITE Uses an address with lots of numbers, at a big ISP

0.9 FROM_ENDS_IN_NUMS From: ends in numbers

0.5 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers

3.3 MSGID_FROM_MTA_SHORT Message-Id was added by a relay

 

NO_REAL_NAME is becase everything, including the name, is encrypted in the body of the message.

 

ADDR_NUMS_AT_BIGSITE seems to be because the email was sent from a big ISP (i.e. TCH?)

 

FROM_ENDS_IN_NUMS is unrelated to this, the person's email had numbers in it

 

FORGED_YAHOO_RCVD seems to be due to the fact that the email address entered into the form is from Yahoo, but the message is actually sent from my site.

 

MSGID_FROM_MTA_SHORT because it's sent from TCH servers but is actually from my domain? (not sure how this one works)

 

I'd like for this not to happen, but I don't want to turn off SpamAssassin as it seems to be doing a good job so far with catching a lot of other spam. A lot of these spam flags seem to be generated from a message being sent from my website on TCH's computers (addr_nums_at_bigsite, msgid_from_mta_short, forged_yahoo_rcvd) - is there any way to fix this so that I don't miss people who contact me from my website, or do I just have to turn SpamAssassin off altogether?

[Guest schussat]

Have you tried adding your own server to spamassassin's "whitelist from" setting (via cpanel)? I don't know what headers SouperMail sets, but according to spamassassin's user prefs document, spamassassin checks all of these:

>Envelope-Sender
Resent-Sender
X-Envelope-From
From

I bet that if SouperMail can be made to set one of those to your own server, then whitelisting it might work.

 

-Alan