You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Bill Cole <sa...@billmail.scconsult.com> on 2016/03/30 01:20:45 UTC
HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
This is true for 8.14.7 in FreeBSD 8.4-RELEASE-p27 (a.k.a. "Update your
damn boxes, Bill!") and I see nothing in later release notes indicating
a relevant change in Sendmail, which is formally within spec by putting
no MIME headers in the human-readable first part of a DSN (Seriously,
all MIME headers are formally optional... text/plain charset=us-ascii is
default). If, like me, you have a bunch of old machines that
occasionally generate mail that is required/forced to use local sendmail
submission, which is configured to send bounces for just about anything
to some elsewhere that actually gets read, this matters.
Since MIME_NO_TEXT is pegged to its limit in the current ruleset (1.999)
there's likely a lot of backscatter out of Sendmail feeding the score,
making it harder for me to form an opinion on the right sort of global
fix, if one exists.
(I'll probably write a bug on this when my brain has rested adequately
to do so cogently, can't say when that might be.)
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Tue, 29 Mar 2016, Bill Cole wrote:
> On 29 Mar 2016, at 19:36, John Hardin wrote:
>
>> Can you send me some samples?
>
>
> OR: if you can submit mail through a Sendmail instance, send mail to any bad
> address anywhere on any machine running any MTA, all it has to do is say '5yz
> blah blah we hate you' to some part of your attempt to send mail.
That I can do. Thanks.
--
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
-----------------------------------------------------------------------
You are in a maze of twisty little protocols,
all written by Microsoft.
----------------------------------------------------------------------
3 days until April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 30 Mar 2016, at 21:22, John Hardin wrote:
>> So, overall, I've got 8 carefully and not excessively redacted slight
>> variants of one bounce now with CT and MV headers inserted in various
>> ways and if anyone wants the entire collector's set, they're free for
>> the asking as a 30k tarball, I'll even compress it if you like.
>
>
> Do some still hit the rule?
Sure, exactly as described in my rant.
> If so, drop it on me so I can test exclusion methods on more than just
> local fakery.
Coming shortly directly to the address you use here.
> The fix will *probably* consist of adding && !__BOUNCE_CTYPE to the
> exclusion list for that rule.
Yeah, after sending my frothing rant about the quirkiness of VBounce.pm
& its affiliated scored rules I realized that the wrongness of only
visibly identifying bounces if they don't come from trusted bounce
relays is mitigated by there being those non-scored rules. Clearly not
written for a sysadmin who needs to know when things are bouncing but
for normal humans trying to evade backscatter.
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Thu, 31 Mar 2016, RW wrote:
> On Thu, 31 Mar 2016 08:12:10 -0700 (PDT)
> John Hardin wrote:
>>
>> I don't follow what you're saying, can you provide an example?
>
> They have something like:
>
> Content-Type: text; charset="utf-8"
>
> rather than
>
> Content-Type: text/plain; charset="utf-8"
>
> It's probably a rare mistake, but I was thinking of a rule like:
>
>
> header __MISSING_SUBTYPE_1 Content-Type =~ /^\w+[;\s]/
> mimeheader __MISSING_SUBTYPE_2 Content-Type =~ /^\w+[;\s]/
>
> meta MISSING_SUBTYPE __MISSING_SUBTYPE_1 || __MISSING_SUBTYPE_2
Seems reasonable, but if it *is* a rare mistake there may not be enough in
the masscheck corpus to get it scored and published.
--
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
-----------------------------------------------------------------------
Pork (n): (political) The manifestation of the principle that it is
a felony to bribe a legislator, unless you are also a legislator.
-----------------------------------------------------------------------
Tomorrow: April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 3/31/2016 6:33 PM, RW wrote:
> On Thu, 31 Mar 2016 17:56:21 -0400
> Kevin A. McGrail wrote:
>
>> On 3/31/2016 1:34 PM, RW wrote:
>>> They have something like:
>>>
>>> Content-Type: text; charset="utf-8"
>>>
>>> rather than
>>>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>> I think you found a bug in sendmail (or something munging things
>> along the way.)
> No, this is in spam.
>
> The FPs from sendmail are caused by it relying on its visible text
> being implicitly text/plain rather that having a Content-Type header.
Sorry, I didn't realize you were describing two issues.
But I'd also interpret the behavior you describe from RFC 2405 since
US-ASCII would be the default Charset. I'm not sure the details of the
problem but if it is missing the header or syntactically invalid,
assuming it's plain US-ASCII looks right.
5.2. Content-Type Defaults
Default RFC 822 messages without a MIME Content-Type header are taken
by this protocol to be plain text in the US-ASCII character set,
which can be explicitly specified as:
Content-type: text/plain; charset=us-ascii
This default is assumed if no Content-Type header field is specified.
It is also recommend that this default be assumed when a
syntactically invalid Content-Type header field is encountered. In
the presence of a MIME-Version header field and the absence of any
Content-Type header field, a receiving User Agent can also assume
that plain US-ASCII text was the sender's intent. Plain US-ASCII
text may still be assumed in the absence of a MIME-Version or the
presence of an syntactically invalid Content-Type header field, but
the sender's intent might have been otherwise.
Regards,
KAM
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Thu, 31 Mar 2016, RW wrote:
> On Thu, 31 Mar 2016 17:56:21 -0400
> Kevin A. McGrail wrote:
>
>> On 3/31/2016 1:34 PM, RW wrote:
>>>
>>> They have something like:
>>>
>>> Content-Type: text; charset="utf-8"
>>>
>>> rather than
>>>
>>> Content-Type: text/plain; charset="utf-8"
>>
>> I think you found a bug in sendmail (or something munging things
>> along the way.)
>
> No, this is in spam.
>
> The FPs from sendmail are caused by it relying on its visible text
> being implicitly text/plain rather that having a Content-Type header.
How many other point do those messages score? Would having another point
or two from this standards violation push them over the top, or are they
already obviously spammy?
--
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: because the audio experience is *far* more important than
network throughput.
-----------------------------------------------------------------------
Tomorrow: April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by RW <rw...@googlemail.com>.
On Thu, 31 Mar 2016 17:56:21 -0400
Kevin A. McGrail wrote:
> On 3/31/2016 1:34 PM, RW wrote:
> >
> > They have something like:
> >
> > Content-Type: text; charset="utf-8"
> >
> > rather than
> >
> > Content-Type: text/plain; charset="utf-8"
> >
>
> I think you found a bug in sendmail (or something munging things
> along the way.)
No, this is in spam.
The FPs from sendmail are caused by it relying on its visible text
being implicitly text/plain rather that having a Content-Type header.
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 3/31/2016 1:34 PM, RW wrote:
>
> They have something like:
>
> Content-Type: text; charset="utf-8"
>
> rather than
>
> Content-Type: text/plain; charset="utf-8"
>
> It's probably a rare mistake, but I was thinking of a rule like:
>
>
> header __MISSING_SUBTYPE_1 Content-Type =~ /^\w+[;\s]/
> mimeheader __MISSING_SUBTYPE_2 Content-Type =~ /^\w+[;\s]/
>
> meta MISSING_SUBTYPE __MISSING_SUBTYPE_1 || __MISSING_SUBTYPE_2
Definitely sounds odd. I think the relevant spec is RFC 2045 which is
clear that the subtype is expected. There are references as well that
the subtype is mandatory with no defaults.
I would consider this an invalid header though I believe that should
then be treated as Application/octet-stream
and "a subtype specification is MANDATORY. There are no default subtypes. "
https://www.ietf.org/rfc/rfc2045.txt for those who want to dig deeper.
I think you found a bug in sendmail (or something munging things along
the way.)
Does this need a rule?
Regards,
KAM
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by RW <rw...@googlemail.com>.
On Thu, 31 Mar 2016 08:12:10 -0700 (PDT)
John Hardin wrote:
> On Thu, 31 Mar 2016, RW wrote:
>
> > On Wed, 30 Mar 2016 18:22:21 -0700 (PDT)
> > John Hardin wrote:
> >
> >> MIME_NO_TEXT is a *very* simple rule: "has a content-type:
> >> multipart/* header in the main message headers" and "has no
> >> content-type: text/* MIME header anywhere."
> >
> > I've only 3 hits on this in the last 4k spam, but FWIW all of them
> > are due to the CT missing the subtype plain. This is a significant
> > RFC violation; it might be worth creating a separate, general
> > MISSING_SUBTYPE rule and adding it as an exclusion to
> > MIME_NO_TEXT.
>
> I don't follow what you're saying, can you provide an example?
They have something like:
Content-Type: text; charset="utf-8"
rather than
Content-Type: text/plain; charset="utf-8"
It's probably a rare mistake, but I was thinking of a rule like:
header __MISSING_SUBTYPE_1 Content-Type =~ /^\w+[;\s]/
mimeheader __MISSING_SUBTYPE_2 Content-Type =~ /^\w+[;\s]/
meta MISSING_SUBTYPE __MISSING_SUBTYPE_1 || __MISSING_SUBTYPE_2
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Thu, 31 Mar 2016, RW wrote:
> On Wed, 30 Mar 2016 18:22:21 -0700 (PDT)
> John Hardin wrote:
>
>> MIME_NO_TEXT is a *very* simple rule: "has a content-type:
>> multipart/* header in the main message headers" and "has no
>> content-type: text/* MIME header anywhere."
>
> I've only 3 hits on this in the last 4k spam, but FWIW all of them
> are due to the CT missing the subtype plain. This is a significant
> RFC violation; it might be worth creating a separate, general
> MISSING_SUBTYPE rule and adding it as an exclusion to MIME_NO_TEXT.
I don't follow what you're saying, can you provide an example?
--
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
-----------------------------------------------------------------------
USMC Rules of Gunfighting #6: If you can choose what to bring to a
gunfight, bring a long gun and a friend with a long gun.
-----------------------------------------------------------------------
Tomorrow: April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by RW <rw...@googlemail.com>.
On Wed, 30 Mar 2016 18:22:21 -0700 (PDT)
John Hardin wrote:
> MIME_NO_TEXT is a *very* simple rule: "has a content-type:
> multipart/* header in the main message headers" and "has no
> content-type: text/* MIME header anywhere."
I've only 3 hits on this in the last 4k spam, but FWIW all of them
are due to the CT missing the subtype plain. This is a significant
RFC violation; it might be worth creating a separate, general
MISSING_SUBTYPE rule and adding it as an exclusion to MIME_NO_TEXT.
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Thu, 31 Mar 2016, Bill Cole wrote:
> On 30 Mar 2016, at 21:22, John Hardin wrote:
>
>> Not sure what you mean by "in the original message body" because it seems
>> having a CT:t/* header in the original message suppresses that rule in my
>> and David's testing.
>
> randomly added into the body, i.e. text in the format of a header where it's
> not logically a header.
OK. If it's not immediately following a MIME boundary string (including
nested ones) then it should be ignored by the MIME header parser.
--
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
-----------------------------------------------------------------------
USMC Rules of Gunfighting #6: If you can choose what to bring to a
gunfight, bring a long gun and a friend with a long gun.
-----------------------------------------------------------------------
Tomorrow: April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 30 Mar 2016, at 21:22, John Hardin wrote:
> Not sure what you mean by "in the original message body" because it
> seems having a CT:t/* header in the original message suppresses that
> rule in my and David's testing.
randomly added into the body, i.e. text in the format of a header where
it's not logically a header.
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Wed, 30 Mar 2016, Bill Cole wrote:
> On 30 Mar 2016, at 11:20, John Hardin wrote:
>
>> On Tue, 29 Mar 2016, David B Funk wrote:
>>
>> > Now my original message was a CT: text/plain. Maybe if the original
>> > message had no textural components at all it might fire as you
>> > describe but I think it would be an unusual message to have no text,
>> > html, etc at all.
>>
>> Same here. I think that's the situation: the message that bounced has
>> to not have any text/plain parts.
>
> OTOH: If it's got no MIME-Version header and therefore is not a MIME
> object, a Content-Type: text/* header makes MIME_NO_TEXT happy for
> (technically) no sound reason...
That would seem to point up a problem in MIME message parsing and/or the
MIMEHeader plugin.
MIME_NO_TEXT is a *very* simple rule: "has a content-type: multipart/*
header in the main message headers" and "has no content-type: text/* MIME
header anywhere."
> ALSO: MIME_NO_TEXT is not at all picky. If I add just a CT:t/p header up top
> where Sendmail doesn't bother doing so, no match on MIME_NO_TEXT *OR*
> T_TVD_MIME_NO_HEADERS:
See above. :) It's not meant to be really picky.
> AND FINALLY: MIME_NO_TEXT isn't entirely unpicky about finding a CT:t/*
> header. It won't find one in the epilog (after the last MIME boundary) or in
> the original message body.
Again, that's based on the behavior of the MIMEHeader plugin. I expect it
stops looking for MIME headers after the last boundary. Not sure what you
mean by "in the original message body" because it seems having a CT:t/*
header in the original message suppresses that rule in my and David's
testing.
> So, overall, I've got 8 carefully and not excessively redacted slight
> variants of one bounce now with CT and MV headers inserted in various ways
> and if anyone wants the entire collector's set, they're free for the asking
> as a 30k tarball, I'll even compress it if you like.
Do some still hit the rule?
If so, drop it on me so I can test exclusion methods on more than just
local fakery. The fix will *probably* consist of adding && !__BOUNCE_CTYPE
to the exclusion list for that rule.
--
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
-----------------------------------------------------------------------
North Korea: the only country in the world where people would risk
execution to flee to communist China. -- Ride Fast
-----------------------------------------------------------------------
2 days until April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 30 Mar 2016, at 11:20, John Hardin wrote:
> On Tue, 29 Mar 2016, David B Funk wrote:
>
>> On Tue, 29 Mar 2016, Bill Cole wrote:
>>
>>> On 29 Mar 2016, at 19:36, John Hardin wrote:
>>>
>>> > Can you send me some samples?
>>>
>>> Probably. Tomorrow. Afternoon. When I can spin up a bullshit VM
>>> (what
>>> still uses sendmail with a default workingish config?) or sanitize
>>> examples made via real stuff.
>>>
>>> OR: if you can submit mail through a Sendmail instance, send mail
>>> to any
>>> bad address anywhere on any machine running any MTA, all it has to
>>> do is
>>> say '5yz blah blah we hate you' to some part of your attempt to
>>> send mail.
>>> On any machine with a working classical Sendmail-managed mail
>>> subsystem
>>> you can just do 'echo "foo" |mailx -s 'any subject'
>>> nonexistent@non-local.but.existing.domain' and get one of your very
>>> own
>>> for a bogus address of your choice delivered to
>>> /var/spool/mail/yournamehere or somewhere like that. Unless your
>>> Sendmail
>>> is configured to not send MIME DSNs. In that case, fire your
>>> sysadmin.
>>
>> I tried your experiment (sent mail to "no-such-user213@hotmail.com"
>> ), got the DSN, fed it to SA and didn't see any hits on MIME_NO_TEXT.
>> Saw a hit on T_TVD_MIME_NO_HEADERS but that has no score.
>>
>> Now my original message was a CT: text/plain. Maybe if the original
>> message had no textural components at all it might fire as you
>> describe but I think it would be an unusual message to have no text,
>> html, etc at all.
>
> Same here. I think that's the situation: the message that bounced has
> to not have any text/plain parts.
>
> I'll edit the bounce I generated and see if that will cause it to hit.
Ewww.
Yes. My bounced messages whose bounces hit MIME_NO_TEXT are all entirely
devoid of MIME headers: they are in fact plain text, but they have no
MIME-Version or Content-Type headers. A bit of experimentation shows
that the MIME_NO_TEXT matches if the original message being bounced
lacks a Content-Type header, even if it HAS a MIME-Version header, in
which case *formally* it is text/plain by default, just as Sendmail's
initial descriptive part is *formally* text/plain by default because it
has no CT header saying otherwise. OTOH: If it's got no MIME-Version
header and therefore is not a MIME object, a Content-Type: text/* header
makes MIME_NO_TEXT happy for (technically) no sound reason...
ALSO: MIME_NO_TEXT is not at all picky. If I add just a CT:t/p header up
top where Sendmail doesn't bother doing so, no match on MIME_NO_TEXT
*OR* T_TVD_MIME_NO_HEADERS:
bcole@sirius:$ diff -uw nonmimemsg smct+nonmimemsg
--- nonmimemsg 2016-03-30 20:52:25.137123397 +0000
+++ smct+nonmimemsg 2016-03-30 21:14:26.854310233 +0000
@@ -19,6 +19,7 @@
This is a MIME-encapsulated message
--u2TNd89e080242.1459294748/ungoliant.RED.ACT.DOM.AIN.net
+Content-Type: text/plain
The original message was received at Tue, 29 Mar 2016 23:39:01 GMT
from ungoliant.RED.ACT.DOM.AIN.net [1.2.3.4]
bcole@sirius:$ spamassassin < nonmimemsg |grep -m1 -A2 X-Spam-Status
X-Spam-Status: No, score=1.6 required=4.5
tests=AWL,CIPH_DEBUG,MIME_NO_TEXT,
T_TVD_MIME_NO_HEADERS shortcircuit=no autolearn=no autolearn_force=no
version=3.4.1
bcole@sirius:$ spamassassin < smct+nonmimemsg |grep -m1 -A2
X-Spam-Status
X-Spam-Status: No, score=0.6 required=4.5 tests=AWL,CIPH_DEBUG
shortcircuit=no
autolearn=no autolearn_force=no version=3.4.1
Received: from ungoliant.RED.ACT.DOM.AIN.net ([1.2.3.4] verified)
AND ALSO ALSO: T_TVD_MIME_NO_HEADERS is only complaining about the
untyped initial description part. If I add a "MIME-Version: 1.0" header
to the original message AND a "Content-Type: text/plain" to the initial
description part, T_TVD_MIME_NO_HEADERS doesn't notice that there's a
self-declared MIME object down there without any explicit MIME headers.
AND FINALLY: MIME_NO_TEXT isn't entirely unpicky about finding a CT:t/*
header. It won't find one in the epilog (after the last MIME boundary)
or in the original message body.
So, overall, I've got 8 carefully and not excessively redacted slight
variants of one bounce now with CT and MV headers inserted in various
ways and if anyone wants the entire collector's set, they're free for
the asking as a 30k tarball, I'll even compress it if you like.
I am still not sure what the right fix is, because as I was writing this
I realized that the cleanest fix would involve recognizing bounces, and
that must be useful enough to exist somewhere in SA already AND IT DOES:
but WOW, isn't THAT design broken! So I did the magic only revealed in
the comments of
/var/db/spamassassin/3.004001/updates_spamassassin_org/20_vbounce.cf
(yay, where I look for key functional facts all the time!) and set
whitelist_bounce_relays correctly and lo: the unredacted pristine
original bounce IS NOT recognized as a bounce but the set of 8 variants
with hostnames and IP's carefully redacted, they all match
BOUNCE_MESSAGE and ANY_BOUNCE_MESSAGE. If I add the redacted form of the
host that is passing back the bounce to me to whitelist_bounce_relays,
the redacted messages no longer match BOUNCE_MESSAGE and
ANY_BOUNCE_MESSAGE, which is positively perverse. Maybe I need to set
whitelist_bounce_relays to afklhfhfasfj so it won't match anything but
will magically activate bounce detection?
In my case the workaround is (in redacted form) this added to local.cf:
whitelist_from_rcvd mailer-daemon@*.RED.ACT.DOM.AIN.net [1.2]
But that sucks almost as bad as the design of
Mail::SpamAssassin::Plugin::VBounce & 20_vbounce.cf.
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Tue, 29 Mar 2016, David B Funk wrote:
> On Tue, 29 Mar 2016, Bill Cole wrote:
>
>> On 29 Mar 2016, at 19:36, John Hardin wrote:
>>
>> > Can you send me some samples?
>>
>> Probably. Tomorrow. Afternoon. When I can spin up a bullshit VM (what
>> still uses sendmail with a default workingish config?) or sanitize
>> examples made via real stuff.
>>
>> OR: if you can submit mail through a Sendmail instance, send mail to any
>> bad address anywhere on any machine running any MTA, all it has to do is
>> say '5yz blah blah we hate you' to some part of your attempt to send mail.
>> On any machine with a working classical Sendmail-managed mail subsystem
>> you can just do 'echo "foo" |mailx -s 'any subject'
>> nonexistent@non-local.but.existing.domain' and get one of your very own
>> for a bogus address of your choice delivered to
>> /var/spool/mail/yournamehere or somewhere like that. Unless your Sendmail
>> is configured to not send MIME DSNs. In that case, fire your sysadmin.
>
> I tried your experiment (sent mail to "no-such-user213@hotmail.com" ),
> got the DSN, fed it to SA and didn't see any hits on MIME_NO_TEXT. Saw a
> hit on T_TVD_MIME_NO_HEADERS but that has no score.
>
> Now my original message was a CT: text/plain. Maybe if the original
> message had no textural components at all it might fire as you describe
> but I think it would be an unusual message to have no text, html, etc at
> all.
Same here. I think that's the situation: the message that bounced has to
not have any text/plain parts.
I'll edit the bounce I generated and see if that will cause it to hit.
--
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
-----------------------------------------------------------------------
A government is a lot like a gun: It's always loaded,
and it's stupid and dangerous to point it at anything
you don't intend to hurt. -- GOF at TSM
-----------------------------------------------------------------------
2 days until April Fools' day
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by David B Funk <db...@engineering.uiowa.edu>.
On Tue, 29 Mar 2016, Bill Cole wrote:
> On 29 Mar 2016, at 19:36, John Hardin wrote:
>
>> So, a message that's explicitly multipart MIME but which has only one part?
>> Or does it actually have multiple parts, just none are marked as
>> text/plain?
>
> multipart/report; type=delivery-status. The standard MIME delivery status
> notification structure. 2 very similar RFCs on it. Has 3 (or 4?) parts. All
> except the first part (which IS text/plain; charset=us-ascii but in
> Sendmail's case has no Content-Type header saying so) have proper
> message/[thisandthat] CT headers.
>
>> Can you send me some samples?
>
> Probably. Tomorrow. Afternoon. When I can spin up a bullshit VM (what still
> uses sendmail with a default workingish config?) or sanitize examples made
> via real stuff.
>
> OR: if you can submit mail through a Sendmail instance, send mail to any bad
> address anywhere on any machine running any MTA, all it has to do is say '5yz
> blah blah we hate you' to some part of your attempt to send mail. On any
> machine with a working classical Sendmail-managed mail subsystem you can just
> do 'echo "foo" |mailx -s 'any subject'
> nonexistent@non-local.but.existing.domain' and get one of your very own for a
> bogus address of your choice delivered to /var/spool/mail/yournamehere or
> somewhere like that. Unless your Sendmail is configured to not send MIME
> DSNs. In that case, fire your sysadmin.
I tried your experiment (sent mail to "no-such-user213@hotmail.com" ), got the
DSN, fed it to SA and didn't see any hits on MIME_NO_TEXT. Saw a hit on
T_TVD_MIME_NO_HEADERS but that has no score.
Now my original message was a CT: text/plain.
Maybe if the original message had no textural components at all it might fire as
you describe but I think it would be an unusual message to have no text, html, etc
at all.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by Bill Cole <sa...@billmail.scconsult.com>.
On 29 Mar 2016, at 19:36, John Hardin wrote:
> So, a message that's explicitly multipart MIME but which has only one
> part? Or does it actually have multiple parts, just none are marked as
> text/plain?
multipart/report; type=delivery-status. The standard MIME delivery
status notification structure. 2 very similar RFCs on it. Has 3 (or 4?)
parts. All except the first part (which IS text/plain; charset=us-ascii
but in Sendmail's case has no Content-Type header saying so) have proper
message/[thisandthat] CT headers.
> Can you send me some samples?
Probably. Tomorrow. Afternoon. When I can spin up a bullshit VM (what
still uses sendmail with a default workingish config?) or sanitize
examples made via real stuff.
OR: if you can submit mail through a Sendmail instance, send mail to any
bad address anywhere on any machine running any MTA, all it has to do is
say '5yz blah blah we hate you' to some part of your attempt to send
mail. On any machine with a working classical Sendmail-managed mail
subsystem you can just do 'echo "foo" |mailx -s 'any subject'
nonexistent@non-local.but.existing.domain' and get one of your very own
for a bogus address of your choice delivered to
/var/spool/mail/yournamehere or somewhere like that. Unless your
Sendmail is configured to not send MIME DSNs. In that case, fire your
sysadmin.
sorry if that's incoherent babbling, I can't tell. not awake. typed and
randomly abridged but not really proofread
--
Bill Cole
Not here right now.
Re: HEADS-UP: MIME_NO_TEXT matches Sendmail MIME DSNs
Posted by John Hardin <jh...@impsec.org>.
On Tue, 29 Mar 2016, Bill Cole wrote:
> This is true for 8.14.7 in FreeBSD 8.4-RELEASE-p27 (a.k.a. "Update your damn
> boxes, Bill!") and I see nothing in later release notes indicating a relevant
> change in Sendmail, which is formally within spec by putting no MIME headers
> in the human-readable first part of a DSN (Seriously, all MIME headers are
> formally optional... text/plain charset=us-ascii is default).
So, a message that's explicitly multipart MIME but which has only one
part? Or does it actually have multiple parts, just none are marked as
text/plain?
> Since MIME_NO_TEXT is pegged to its limit in the current ruleset (1.999)
> there's likely a lot of backscatter out of Sendmail feeding the score, making
> it harder for me to form an opinion on the right sort of global fix, if one
> exists.
Can you send me some samples? Suppressing it for something that looks like
a DSN might be reasonable; we can at least see how that plays in
masscheck.
> (I'll probably write a bug on this when my brain has rested adequately to do
> so cogently, can't say when that might be.)
Not sure it's worthy of a bug. Discuss it here and if any changes seem
justified I'll make them.
--
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
-----------------------------------------------------------------------
3 days until April Fools' day