Spam detection software, running on the system "snarked.org",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
http://www.snarked.org/spam for details.

Content preview:  config: devtmpfs: Allow mount parameters to be set in kernel
   configuration Why? To limit the size of the file system to prevent runaway
   dynamic device creation. Even a "udev" rescue kernel takes a small size (e.g.
   slackware 14.2 uses 52kB and 2,666 inodes). Setting reasonable size limits
   (e.g. 64k and 3,072 inodes) will accommodate most setups. Although a remount
   during an initialization script can also solve this problem, why not do it
   correctly the first time? [...] 

Content analysis details:   (3.2 points, 7.5 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 0.2 STOX_REPLY_TYPE        No description available.
 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
 2.1 DATE_IN_PAST_96_XX     Date: is 96 hours or more before Received: date
 0.1 RCVD_IN_DNSWL_NO       Sender *not* listed at http://www.dnswl.org/
 1.9 STOX_REPLY_TYPE_WITHOUT_QUOTES No description available.

SAV: 3.4.1-snarked_ec212 (2015-04-28)
ASN:  () _RELAYCOUNTRY_
CIP:  
DCC: snarked.org 104; Body=2 Fuz1=2 Fuz2=2 (x.dcc-servers) 
PYZ: 
BAY: 0.5 (no autolearn_force=no) 
<dns:snarked.org?type=MX> [90 mx.fakemx.net., 20 mail.snarked.net., 10 mail.snarked.org., 80 tarbaby.junkemailfilter.com.]