Created attachment 4244 [details]
blackberry message example

This is an example of what mail from blackberry senders looks like.

Hi,

IMO, it's unlikely this is an SA issue, since SA doesn't modify the message content, but ...  Can you upload 
a pre-SA message and post-SA message showing the problem, in text/plain format (4244 is a word doc)?

Created attachment 4245 [details]
txt file of before and after SA

Here is a text version of the mail.  Of course we use outlook here to view
emails so some of the "characters" will not translate to ascci.  But, most of
the conversion is there (toward the bottom of the email).

I am not the only site using SA to experience this NEW problem.  Frugal
Brothers Software in Indiana is experiencing the same thing.  Just with
Blackberry mail though same as here.

Mike Bradley

We need the original "as seen by SA" mails.  4245 looks like saved messages from the MUA which isn't 
useful.

Also, how are you calling SA?

Here is how to get the full text of the email in a form that might help us, if
you are using Outlook:

1. Click on (highlight) the message title line (not the preview window).
2. Click on "File."
3. Click on "Properties."
4. Click the "Details" tab.

Copy and paste that into a text file and attach that to this bug report.

That still is unlikely to be enough information, but at least it will give us a
start at seeing what the problem really looks like. What we really need is the
raw source of the mail before SpamAssassin ever ses it, and right after
SpamAssassin has processed it. To get that information you will probably have to
talk to someone in your IT who understands how your mail server is set up to
receive mail and how it invokes SpamAssassin.

SpamAssassin does not process the mail all by itself. You have something that
receives mail, sends it through SpamAssassin, then sends the processed result on
to your mailbox. For example, if you have an Exchange server, you might be
running Exchange SpamAssassin Sink to process emails through SpamAssassin.

In order to be able to figure out if your problem is with SpamAssassin or has
something to do with the way you are processing mail to get it through
SpamAssassin we need to know what kind of mail server you are using and how it
is running SpamAssassin.

We also need to see what the Blackberry email looks like, with all of its
headers intact, before it is run through SpamAssassin and after it is run
through SpamAssassin.

We have been postulating that the problem may actually be in the Postfix 
program which is not really a part of SA.  The strange part is that we have 
seen evidence that even when we receive a forwarded mail that contains a 
blackberry message, the blackberry part is garbled but the rest of the non 
blackberry message is fine. ????  The impression is that it is the SA that is 
causing the problem and that IS a problem for SA.

> We have been postulating that the problem may actually be in the Postfix 
> program which is not really a part of SA.  The strange part is that we have 
> seen evidence that even when we receive a forwarded mail that contains a 
> blackberry message, the blackberry part is garbled but the rest of the non 
> blackberry message is fine. ????  The impression is that it is the SA that is 
> causing the problem and that IS a problem for SA.

You still haven't answered how you are calling SpamAssassin.

Without seeing evidence (raw message before it reaches SA, and afterwards),
there is not much we can do here to help. If messages are coming in
through Postfix, and you spot such message still in a MTA queue (e.g. by
stalling content filtering), you may use a 'postcat -q queueid >0.msg'
command to obtain a readable raw copy of a message.

The bug is not with SA but with the postfix part of mailscanner.  My supplier 
is re-inventing his appliance to fix the issue.  Thanks for your responses.

For future reference, when using MailScanner, SpamAssassin never touches the
copy of the message that gets delivered to your mailbox. MailScanner calls SA to
generate scores, but then performs its own markups on the original message.