You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by David Jones <dj...@ena.com> on 2018/02/22 21:27:49 UTC
ENCRYPTED_MESSAGE rule
My SA filters just received 45 unsolicited junk emails from Office 365
that hit ENCRYPTED_MESSAGE which subtracted a point. Looking at
72_active.cf, the description for this rule is:
"Message is encrypted, not likely to be spam"
The body of the email was a MIME attachment of application/pkcs7-mime so
SA didn't have access to it for body content rules.
I am seriously thinking about changing the score on this rule locally to
1.0 or 2.0 to add points if SA can't do any body checks. Outlook and
Outlook Web was able to display the email automatically. This may be a
new feature that we are about to see more often to hide spam from SA.
It also hit BAYES_00 (not much can be done to change that), DCC_CHECK,
PYZOR_CHECK, and FSL_BULK_SIG to score 2.88.
I reported this to SpamCop/Office 365 and blocked the sending domain.
Seems like more and more junk is coming out of Office 365 every week.
The majority of new/zero-hour spam that I am not able to block with SA
is now coming from O365.
--
David Jones
Re: ENCRYPTED_MESSAGE rule
Posted by RW <rw...@googlemail.com>.
On Fri, 23 Feb 2018 07:18:52 -0600
David Jones wrote:
> On 02/23/2018 06:29 AM, RW wrote:
> > On Thu, 22 Feb 2018 19:33:29 -0700
> > @lbutlr wrote:
> >
> >> On 2018-02-22 (17:39 MST), RW <rw...@googlemail.com> wrote:
> >>>
> >>> Is it genuinely encrypted though? I'm wondering if it's just
> >>> base64 encoded, and possibly signed.
> >>
> >> application/pkcs7-mime is S/MIME
> >
> > I know, but does that mean it's necessarily encrypted and not simply
> > signed?
> >
>
> Outlook Web says across the top of the message:
>
> This message has a digital signature, but it wasn't verified because
> the S/MIME control isn't currently supported for your browser or
> platform.
>
> Outlook client on a Mac says it was an encrypted email.
>
> https://pastebin.com/Kf9KJKyh
>
It's just signed, if you change the type to text/plain you can see the
raw mime message.
It has:
Content-Type: application/pkcs7-mime; smime-type=signed-data;
name="smime.p7m"
From a quick look at rfc5751 it looks like a purely encrypted email
would have "smime-type=enveloped-data", but I doubt that's common. With
a signed and encrypted email the two types are nested in either order.
It comes down to usage, if the norm is for emails to be signed and
then encrypted, then this sort of email can easily be excluded from
ENCRYPTED_MESSAGE, but the other way around requires support for
S/MIME.
Re: ENCRYPTED_MESSAGE rule
Posted by David Jones <dj...@ena.com>.
On 02/23/2018 06:29 AM, RW wrote:
> On Thu, 22 Feb 2018 19:33:29 -0700
> @lbutlr wrote:
>
>> On 2018-02-22 (17:39 MST), RW <rw...@googlemail.com> wrote:
>>>
>>> Is it genuinely encrypted though? I'm wondering if it's just base64
>>> encoded, and possibly signed.
>>
>> application/pkcs7-mime is S/MIME
>
> I know, but does that mean it's necessarily encrypted and not simply
> signed?
>
Outlook Web says across the top of the message:
This message has a digital signature, but it wasn't verified because the
S/MIME control isn't currently supported for your browser or platform.
Outlook client on a Mac says it was an encrypted email.
https://pastebin.com/Kf9KJKyh
The spample above now has this sender as blacklisted so you may want to
run it through your own spamassassin configs to see what it hits.
--
David Jones
Re: ENCRYPTED_MESSAGE rule
Posted by RW <rw...@googlemail.com>.
On Thu, 22 Feb 2018 19:33:29 -0700
@lbutlr wrote:
> On 2018-02-22 (17:39 MST), RW <rw...@googlemail.com> wrote:
> >
> > Is it genuinely encrypted though? I'm wondering if it's just base64
> > encoded, and possibly signed.
>
> application/pkcs7-mime is S/MIME
I know, but does that mean it's necessarily encrypted and not simply
signed?
Re: ENCRYPTED_MESSAGE rule
Posted by "@lbutlr" <kr...@kreme.com>.
On 2018-02-22 (17:39 MST), RW <rw...@googlemail.com> wrote:
>
> Is it genuinely encrypted though? I'm wondering if it's just base64
> encoded, and possibly signed.
application/pkcs7-mime is S/MIME
--
Vi Veri Veniversum Vivus Vici
Re: ENCRYPTED_MESSAGE rule
Posted by RW <rw...@googlemail.com>.
On Thu, 22 Feb 2018 17:40:56 -0600
David Jones wrote:
> Sometimes the passing of time with new spam techniques from software
> changes (i.e. Office 365 now auto handling of encrypted email) can
> allow this to be abused and need changing. I am just trying to bring
> this up in case others may be seeing the same thing in their logs and
> not noticed it yet.
Is it genuinely encrypted though? I'm wondering if it's just base64
encoded, and possibly signed.
RCVD_OFFICE365 was ENCRYPTED_MESSAGE rule
Posted by David Jones <dj...@ena.com>.
On 02/22/2018 06:10 PM, John Hardin wrote:
> I was just referring to the OFFICE365 subrule, as there isn't one like
> that yet - hotmail, sure, outlook, sure, but not office365. We should
> have added that back when O365 started up.
>
I had already added a generic rule for this in my sandbox so you can see
it at http://ruleqa.spamassassin.org now:
__RCVD_OFFICE365
Hotmail and Office 365 tenants come from this so it's not a direct
relationship to spam but can be used in meta rules to amplify other
spammy rules.
__RCVD_OFFICE365_PROXY
This is interesting because often when there is a true compromised
account on O365, spammers will use authenticated SMTP to blast out spam
not using the Outlook Web interface or an Outlook client. This will hit
on normal mail clients like Thunderbird or Apple Mail so it too is not a
direct indication of spam.
My local __RCVD_OFFICE365 rule that combines sources of freemail like
O365 in with FREEMAIL_* rules is already working well the past 24 hours.
I am offsetting my BAYES_00 score of -3.2 by adding back 2.0 when for
email from O365. It has helped to blocked a bogus file sharing email
using a URL shortener that would have scored just below the MailScanner
default threshold of 6.0.
--
David Jones
Re: ENCRYPTED_MESSAGE rule
Posted by John Hardin <jh...@impsec.org>.
On Thu, 22 Feb 2018, David Jones wrote:
> On 02/22/2018 04:40 PM, John Hardin wrote:
>> On Thu, 22 Feb 2018, David Jones wrote:
>>
>>> On 02/22/2018 03:49 PM, John Hardin wrote:
>>>> On Thu, 22 Feb 2018, David Jones wrote:
>>>>
>>>>> My SA filters just received 45 unsolicited junk emails from Office 365
>>>>> that hit ENCRYPTED_MESSAGE which subtracted a point. Looking at
>>>>> 72_active.cf, the description for this rule is:
>>>>>
>>>>> "Message is encrypted, not likely to be spam"
>>>>>
>>>>> The body of the email was a MIME attachment of application/pkcs7-mime so
>>>>> SA didn't have access to it for body content rules.
>>>>>
>>>>> I am seriously thinking about changing the score on this rule locally to
>>>>> 1.0 or 2.0 to add points if SA can't do any body checks.
>>>>
>>>> I'd recommend against that. It would be better to do offsetting scores in
>>>> a meta rule...
>>>>
>>>
>>> Good idea.
>>>
>>>>> Outlook and Outlook Web was able to display the email automatically.
>>>>> This may be a new feature that we are about to see more often to hide
>>>>> spam from SA.
>>>>>
>>>>> It also hit BAYES_00 (not much can be done to change that), DCC_CHECK,
>>>>> PYZOR_CHECK, and FSL_BULK_SIG to score 2.88.
>>>>
>>>> ...e.g. ENCRYPTED_MESSAGE && (DCC_CHECK || PYZOR_CHECK || FSL_BULK_SIG)
>>>> as bulk encrypted mail seems unlikely
>>>>
>>>> ...or possibly ENCRYPTED_MESSAGE && FREEMAIL_FROM
>>>
>>> This is not hitting FREEMAIL* rules but I have started treating anything
>>> coming from Google and Office 365 with local meta rules like this:
>>>
>>> header __RCVD_GOOGLE Received =~ /\.google\.com \[/
>>
>> Is that accurately freemail? Wouldn't that also hit Google corporate
>> emails?
>>
>>> header __RCVD_OFFICE365 Received =~ /\.outbound\.protection\.outlook\.com
>>> \[/
>>
>> You might want to drop that in your sandbox so that it gets published...
>>
>>> meta __RCVD_FREEMAIL (__RCVD_GOOGLE || __RCVD_OFFICE365)
>>>
>>> meta ENA_FREEMAIL (FREEMAIL_FROM || FREEMAIL_REPLYTO ||
>>> FREEMAIL_FORGED_REPLYTO || __RCVD_FREEMAIL)
>>>
>>> meta ENA_FREEMAIL_ENCRYPTED_MESSAGE ENCRYPTED_MESSAGE && ENA_FREEMAIL
>>> score ENA_FREEMAIL_ENCRYPTED_MESSAGE 3.0
>>>
>>>
>>> That above would end up being a net score of +2.0 for freemail sources of
>>> email.
>>
>> That sounds a lot safer. The rule *was* added with a negative score for a
>> specific reason, after all...
>
> Sure. The description doesn't sound like a very solid reason to assume that
> most encrypted email is ham when we can't do any body checks. :)
I that description was primarily from an assumption that spammers wouldn't
be encrypting email as that would probably *reduce* the likelihood it
would get viewed. But that may be changing.
It's also there to somewhat offset FPs due to unexpected matches in the
encrypted gibberish.
> Sometimes the passing of time with new spam techniques from software changes
> (i.e. Office 365 now auto handling of encrypted email) can allow this to be
> abused and need changing.
Exactly.
I'd be open to adding !__RCVD_OFFICE365 to ENCRYPTED_MESSAGE if they are
making it *that* easy to abuse.
> I am just trying to bring this up in case others
> may be seeing the same thing in their logs and not noticed it yet.
>
> I will put it in my sandbox and see how it goes. Thanks
I was just referring to the OFFICE365 subrule, as there isn't one like
that yet - hotmail, sure, outlook, sure, but not office365. We should have
added that back when O365 started up.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
...have you noticed how the people sniveling over Trump are
the same people slobbering over Fidel? They accuse Trump of wanting
to put gays and minorities in camps, then post paeans
to a guy who did just that. -- Toastrider @ TSM
-----------------------------------------------------------------------
Today: George Washington's 286th Birthday
Re: ENCRYPTED_MESSAGE rule
Posted by David Jones <dj...@ena.com>.
On 02/22/2018 04:40 PM, John Hardin wrote:
> On Thu, 22 Feb 2018, David Jones wrote:
>
>> On 02/22/2018 03:49 PM, John Hardin wrote:
>>> On Thu, 22 Feb 2018, David Jones wrote:
>>>
>>>> My SA filters just received 45 unsolicited junk emails from Office
>>>> 365 that hit ENCRYPTED_MESSAGE which subtracted a point. Looking at
>>>> 72_active.cf, the description for this rule is:
>>>>
>>>> "Message is encrypted, not likely to be spam"
>>>>
>>>> The body of the email was a MIME attachment of
>>>> application/pkcs7-mime so SA didn't have access to it for body
>>>> content rules.
>>>>
>>>> I am seriously thinking about changing the score on this rule
>>>> locally to 1.0 or 2.0 to add points if SA can't do any body checks.
>>>
>>> I'd recommend against that. It would be better to do offsetting
>>> scores in a meta rule...
>>>
>>
>> Good idea.
>>
>>>> Outlook and Outlook Web was able to display the email
>>>> automatically. This may be a new feature that we are about to see
>>>> more often to hide spam from SA.
>>>>
>>>> It also hit BAYES_00 (not much can be done to change that),
>>>> DCC_CHECK, PYZOR_CHECK, and FSL_BULK_SIG to score 2.88.
>>>
>>> ...e.g. ENCRYPTED_MESSAGE && (DCC_CHECK || PYZOR_CHECK ||
>>> FSL_BULK_SIG) as bulk encrypted mail seems unlikely
>>>
>>> ...or possibly ENCRYPTED_MESSAGE && FREEMAIL_FROM
>>
>> This is not hitting FREEMAIL* rules but I have started treating
>> anything coming from Google and Office 365 with local meta rules like
>> this:
>>
>> header __RCVD_GOOGLE Received =~ /\.google\.com \[/
>
> Is that accurately freemail? Wouldn't that also hit Google corporate
> emails?
>
>> header __RCVD_OFFICE365 Received =~
>> /\.outbound\.protection\.outlook\.com \[/
>
> You might want to drop that in your sandbox so that it gets published...
>
>> meta __RCVD_FREEMAIL (__RCVD_GOOGLE || __RCVD_OFFICE365)
>>
>> meta ENA_FREEMAIL (FREEMAIL_FROM || FREEMAIL_REPLYTO ||
>> FREEMAIL_FORGED_REPLYTO || __RCVD_FREEMAIL)
>>
>> meta ENA_FREEMAIL_ENCRYPTED_MESSAGE ENCRYPTED_MESSAGE && ENA_FREEMAIL
>> score ENA_FREEMAIL_ENCRYPTED_MESSAGE 3.0
>>
>>
>> That above would end up being a net score of +2.0 for freemail sources
>> of email.
>
> That sounds a lot safer. The rule *was* added with a negative score for
> a specific reason, after all...
>
Sure. The description doesn't sound like a very solid reason to assume
that most encrypted email is ham when we can't do any body checks. :)
Sometimes the passing of time with new spam techniques from software
changes (i.e. Office 365 now auto handling of encrypted email) can allow
this to be abused and need changing. I am just trying to bring this up
in case others may be seeing the same thing in their logs and not
noticed it yet.
I will put it in my sandbox and see how it goes. Thanks
--
David Jones
Re: ENCRYPTED_MESSAGE rule
Posted by John Hardin <jh...@impsec.org>.
On Thu, 22 Feb 2018, David Jones wrote:
> On 02/22/2018 03:49 PM, John Hardin wrote:
>> On Thu, 22 Feb 2018, David Jones wrote:
>>
>>> My SA filters just received 45 unsolicited junk emails from Office 365
>>> that hit ENCRYPTED_MESSAGE which subtracted a point. Looking at
>>> 72_active.cf, the description for this rule is:
>>>
>>> "Message is encrypted, not likely to be spam"
>>>
>>> The body of the email was a MIME attachment of application/pkcs7-mime so
>>> SA didn't have access to it for body content rules.
>>>
>>> I am seriously thinking about changing the score on this rule locally to
>>> 1.0 or 2.0 to add points if SA can't do any body checks.
>>
>> I'd recommend against that. It would be better to do offsetting scores in a
>> meta rule...
>>
>
> Good idea.
>
>>> Outlook and Outlook Web was able to display the email automatically.
>>> This may be a new feature that we are about to see more often to hide spam
>>> from SA.
>>>
>>> It also hit BAYES_00 (not much can be done to change that), DCC_CHECK,
>>> PYZOR_CHECK, and FSL_BULK_SIG to score 2.88.
>>
>> ...e.g. ENCRYPTED_MESSAGE && (DCC_CHECK || PYZOR_CHECK || FSL_BULK_SIG) as
>> bulk encrypted mail seems unlikely
>>
>> ...or possibly ENCRYPTED_MESSAGE && FREEMAIL_FROM
>
> This is not hitting FREEMAIL* rules but I have started treating anything
> coming from Google and Office 365 with local meta rules like this:
>
> header __RCVD_GOOGLE Received =~ /\.google\.com \[/
Is that accurately freemail? Wouldn't that also hit Google corporate
emails?
> header __RCVD_OFFICE365 Received =~ /\.outbound\.protection\.outlook\.com \[/
You might want to drop that in your sandbox so that it gets published...
> meta __RCVD_FREEMAIL (__RCVD_GOOGLE || __RCVD_OFFICE365)
>
> meta ENA_FREEMAIL (FREEMAIL_FROM || FREEMAIL_REPLYTO ||
> FREEMAIL_FORGED_REPLYTO || __RCVD_FREEMAIL)
>
> meta ENA_FREEMAIL_ENCRYPTED_MESSAGE ENCRYPTED_MESSAGE && ENA_FREEMAIL
> score ENA_FREEMAIL_ENCRYPTED_MESSAGE 3.0
>
>
> That above would end up being a net score of +2.0 for freemail sources of
> email.
That sounds a lot safer. The rule *was* added with a negative score for a
specific reason, after all...
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Vista is at best mildly annoying and at worst makes you want to
rush to Redmond, Wash. and rip somebody's liver out. -- Forbes
-----------------------------------------------------------------------
Today: George Washington's 286th Birthday
Re: ENCRYPTED_MESSAGE rule
Posted by David Jones <dj...@ena.com>.
On 02/22/2018 03:49 PM, John Hardin wrote:
> On Thu, 22 Feb 2018, David Jones wrote:
>
>> My SA filters just received 45 unsolicited junk emails from Office 365
>> that hit ENCRYPTED_MESSAGE which subtracted a point. Looking at
>> 72_active.cf, the description for this rule is:
>>
>> "Message is encrypted, not likely to be spam"
>>
>> The body of the email was a MIME attachment of application/pkcs7-mime
>> so SA didn't have access to it for body content rules.
>>
>> I am seriously thinking about changing the score on this rule locally
>> to 1.0 or 2.0 to add points if SA can't do any body checks.
>
> I'd recommend against that. It would be better to do offsetting scores
> in a meta rule...
>
Good idea.
>> Outlook and Outlook Web was able to display the email automatically.
>> This may be a new feature that we are about to see more often to hide
>> spam from SA.
>>
>> It also hit BAYES_00 (not much can be done to change that), DCC_CHECK,
>> PYZOR_CHECK, and FSL_BULK_SIG to score 2.88.
>
> ...e.g. ENCRYPTED_MESSAGE && (DCC_CHECK || PYZOR_CHECK || FSL_BULK_SIG)
> as bulk encrypted mail seems unlikely
>
> ...or possibly ENCRYPTED_MESSAGE && FREEMAIL_FROM
>
>
This is not hitting FREEMAIL* rules but I have started treating anything
coming from Google and Office 365 with local meta rules like this:
header __RCVD_GOOGLE Received =~ /\.google\.com \[/
header __RCVD_OFFICE365 Received =~
/\.outbound\.protection\.outlook\.com \[/
meta __RCVD_FREEMAIL (__RCVD_GOOGLE || __RCVD_OFFICE365)
meta ENA_FREEMAIL (FREEMAIL_FROM || FREEMAIL_REPLYTO ||
FREEMAIL_FORGED_REPLYTO || __RCVD_FREEMAIL)
meta ENA_FREEMAIL_ENCRYPTED_MESSAGE ENCRYPTED_MESSAGE && ENA_FREEMAIL
score ENA_FREEMAIL_ENCRYPTED_MESSAGE 3.0
That above would end up being a net score of +2.0 for freemail sources
of email.
--
David Jones
Re: ENCRYPTED_MESSAGE rule
Posted by John Hardin <jh...@impsec.org>.
On Thu, 22 Feb 2018, David Jones wrote:
> My SA filters just received 45 unsolicited junk emails from Office 365 that
> hit ENCRYPTED_MESSAGE which subtracted a point. Looking at 72_active.cf, the
> description for this rule is:
>
> "Message is encrypted, not likely to be spam"
>
> The body of the email was a MIME attachment of application/pkcs7-mime so SA
> didn't have access to it for body content rules.
>
> I am seriously thinking about changing the score on this rule locally to 1.0
> or 2.0 to add points if SA can't do any body checks.
I'd recommend against that. It would be better to do offsetting scores in
a meta rule...
> Outlook and Outlook Web
> was able to display the email automatically. This may be a new feature that
> we are about to see more often to hide spam from SA.
>
> It also hit BAYES_00 (not much can be done to change that), DCC_CHECK,
> PYZOR_CHECK, and FSL_BULK_SIG to score 2.88.
...e.g. ENCRYPTED_MESSAGE && (DCC_CHECK || PYZOR_CHECK || FSL_BULK_SIG) as
bulk encrypted mail seems unlikely
...or possibly ENCRYPTED_MESSAGE && FREEMAIL_FROM
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Christian martyrs don't explode. -- Marisol
-----------------------------------------------------------------------
Today: George Washington's 286th Birthday