| Current Path : /home/ift/mails/33/ |
Linux ift1.ift-informatik.de 5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC 2025 x86_64 |
| Current File : //home/ift/mails/33/1533242278.zrspam.336551_2018_08_02 |
From 36284-37385-4808-7247-christian.gabriel=ift-informatik.de@mail.helthgo.us Thu Aug 2 22:37:58 2018
Return-Path: <36284-37385-4808-7247-christian.gabriel=ift-informatik.de@mail.helthgo.us>
X-Original-To: cgabriel@ift-informatik.de
Delivered-To: cgabriel@ift-informatik.de
Received: by ift-informatik.de (Postfix, from userid 5555)
id 55DEE3D200D7C; Thu, 2 Aug 2018 22:37:58 +0200 (CEST)
Received: from localhost by h2486555.stratoserver.net
with SpamAssassin (version 3.4.0);
Thu, 02 Aug 2018 22:37:58 +0200
From: "**6 Critical Tools In One Tiny Box**" <support@helthgo.us>
To: <christian.gabriel@ift-informatik.de>
Subject: *****SPAM***** F R E E SOS Pocket Survival Kit Today
Date: Thu, 2 Aug 2018 16:37:24 -0400
Message-Id: <ecg7p6lnt27x207n-4390695ucttbozp6-9209-12c8@helthgo.us>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
h2486555.stratoserver.net
X-Spam-Flag: YES
X-Spam-Level: *****
X-Spam-Status: Yes, score=6.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
GAPPY_SUBJECT,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,RAZOR2_CF_RANGE_51_100,
RAZOR2_CF_RANGE_E8_51_100,RAZOR2_CHECK,RDNS_NONE,T_DKIM_INVALID,T_FRT_FREE,
T_REMOTE_IMAGE,URIBL_BLOCKED,URIBL_DBL_SPAM autolearn=no autolearn_force=no
version=3.4.0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_5B636BA6.3C5562CF"
This is a multi-part message in MIME format.
------------=_5B636BA6.3C5562CF
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Spam detection software, running on the system "h2486555.stratoserver.net",
has identified this incoming email as possible 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
@@CONTACT_ADDRESS@@ for details.
Content preview: F R E E SOS Pocket Survival Kit Today http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300
http://helthgo.us/QsTPGamBx8S5sXzg6uPjuQ9URXjgZkj9bHXWPk7h16u63p2D_4808_9209_344149cd_0300
[...]
Content analysis details: (6.0 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: helthgo.us]
1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist
[URIs: helthgo.us]
0.0 T_FRT_FREE BODY: ReplaceTags: Free
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 HTML_MESSAGE BODY: HTML included in message
0.0 HTML_FONT_LOW_CONTRAST BODY: HTML font color similar or identical to
background
0.9 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
1.9 RAZOR2_CF_RANGE_E8_51_100 Razor2 gives engine 8 confidence level
above 50%
[cf: 100]
0.5 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50%
[cf: 100]
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
2.0 GAPPY_SUBJECT Subject: contains G.a.p.p.y-T.e.x.t
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
0.0 T_REMOTE_IMAGE Message contains an external image
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.
------------=_5B636BA6.3C5562CF
Content-Type: message/rfc822; x-spam-type=original
Content-Description: original message before SpamAssassin
Content-Disposition: attachment
Content-Transfer-Encoding: 8bit
Received: from green.helthgo.us (unknown [72.11.132.70])
by ift-informatik.de (Postfix) with ESMTP id 1E3DE3D200039
for <christian.gabriel@ift-informatik.de>; Thu, 2 Aug 2018 22:37:56 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=k1; d=helthgo.us;
h=Mime-Version:Content-Type:Date:From:Reply-To:Subject:To:Message-ID; i=support@helthgo.us;
bh=M0KnzrkYyNlGEQPBnFkMZVkxC4s=;
b=IH4JBvDwemTyirMElSIi5ZlNMkC5BLdTi84Jew3XR1oxPauJCVDVxXcwvY6VET0h9QOuecnxpoMD
qpsY0APVe4/JnDnznpWXgcrlo45XfC+0AhyqDv1MSx91iyihwLJbB4tye9TwfovC/MwR/MQydvif
MnIwTSdz/xsXgSWt7bs=
DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=k1; d=helthgo.us;
b=MR9x6UFgTULGfRKVhnFwO4YEjCFyFheKvfreHwmK21ShgnP9tmKqH1lGK5y9hQCc/6gjzwYCgD5q
35EXtosNLT9ig6I8emHrU/PxUTDFpX2g+FsBljMzDCKqj8JtjDEhMAR23kn2Indu4QyrHkgJwPDn
S8anw12m8N0HJZQ8d9U=;
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="2dca5e6cd34ce671e9785b1f78446c2e_9209_12c8"
Date: Thu, 2 Aug 2018 16:37:24 -0400
From: "**6 Critical Tools In One Tiny Box**" <support@helthgo.us>
Reply-To: "**6 Critical Tools In One Tiny Box**" <info@helthgo.us>
Subject: F R E E SOS Pocket Survival Kit Today
To: <christian.gabriel@ift-informatik.de>
Message-ID: <ecg7p6lnt27x207n-4390695ucttbozp6-9209-12c8@helthgo.us>
--2dca5e6cd34ce671e9785b1f78446c2e_9209_12c8
Content-Type: text/plain;
Content-Transfer-Encoding: 8bit
F R E E SOS Pocket Survival Kit Today
http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300
http://helthgo.us/QsTPGamBx8S5sXzg6uPjuQ9URXjgZkj9bHXWPk7h16u63p2D_4808_9209_344149cd_0300
ome filesystems, such as FAT, store filenames as upper-case regardless of the letter case used to create them. For example, a file created with the name "MyName.Txt" or "myname.txt" would be stored with the filename "MYNAME.TXT". Any variation of upper and lower case can be used to refer to the same file. These kinds of file systems are called case-insensitive and are not case-preserving. Some filesystems prohibit the use of lower case letters in filenames altogether.
Some file systems store filenames in the form that they were originally created; these are referred to as case-retentive or case-preserving. Such a file system can be case-sensitive or case-insensitive. If case-sensitive, then "MyName.Txt" and "myname.txt" may refer to two different files in the same directory, and each file must be referenced by the exact capitalization by which it is named. On a case-insensitive, case-preserving file system, on the other hand, only one of "MyName.Txt", "myname.txt" and "Myname.TXT" can be the name of a file in a given directory at a given time, and a file with one of these names can be referenced by any capitalization of the name.
From its original inception, Unix and its derivative systems were case-preserving. However, not all Unix-like file systems are case-sensitive; by default, HFS+ in macOS is case-insensitive, and SMB servers usually provide case-insensitive behavior (even when the underlying file system is case-sensitive, e.g. Samba on most Unix-like systems), and SMB client file systems provide case-insensitive behavior. File system case sensitivity is a considerable challenge for software such as Samba and Wine, which must interoperate efficiently with both systems that treat uppercase and lowercase files as different and with systems that treat them the same.
Reserved characters and words
--2dca5e6cd34ce671e9785b1f78446c2e_9209_12c8
Content-Type: text/html;
Content-Transfer-Encoding: 8bit
<html>
<head>
<title></title>
</head>
<body><a href="http://helthgo.us/oRhn4rNdmPHCSxEmtWNOfNu96uVnrEy5qTCn45R4aje7fS1m_4808_9209_b5643390_0300"><img src="http://helthgo.us/d13b16bff7ff8dacf8.jpg" /><img height="1" src="http://www.helthgo.us/m_yloNKPd-Lg6fKnMwF-QbPvgGbs_2b_NX7HLb3ACjOg4-36_4808_9209_be0193d9_0300" width="1" /></a><br />
<center>
<table align="" width="610px">
<tbody>
<tr>
<td>
<table align="center" style="border:2px solid black; padding:6px" width="610">
<tbody>
<tr>
<td align="left" style="font-size:18px"><strong><a href="http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300" style="text-decoration:none;font-size:30px;color:red;"><span style="color:#808080;">Can</span> I <span style="color:#FF0000;">Rush Ship</span> You<span style="color:#808080;"> A FREE SOS Pocket</span> Survival Kit Today? </a></strong>
<hr /><br />
6 Critical Tools In One Tiny Box, <strong>EVERYTHING YOU'LL NEED TO HANDLE JUST ABOUT <a href="http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300">ANY SITUATION</a></strong><br />
<center><a href="http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300"><img alt=" " src="http://helthgo.us/717ebf9fabb2d60a05.jpg" /></a></center>
<br />
<br />
<a href="http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300"><span style="color:#0000FF;"><strong>Please Rush My FREE SOS Pocket Survival Kit To My Doorstep Today</strong></span></a><br />
<center><a href="http://helthgo.us/5BkEQoxm501dAaic7B6c-L-Y0dAH3os9P7bYZxto9c5lmDf__4808_9209_838da1a0_0300"><img alt=" " src="http://helthgo.us/8d36bd8f132af5286c.jpg" /></a></center>
</td>
</tr>
</tbody>
</table>
<br />
<br />
<br />
<br />
<br />
<center><a href="http://helthgo.us/ulsft_BK315xRdoJBdFUnw3jZSnKSl5ds6rawfxk52TYEip1_4808_9209_4fad1b2a_0300"><img alt=" " src="http://helthgo.us/09f84839d1f933805a.jpg" /></a></center>
</td>
</tr>
</tbody>
</table>
<table align="center" width="600">
<tbody>
<tr>
<td>
<p style="font-size:6px;color:#FFFFFF">ome filesystems, such as FAT, store filenames as upper-case regardless of the letter case used to create them. For example, a file created with the name "MyName.Txt" or "myname.txt" would be stored with the filename "MYNAME.TXT". Any variation of upper and lower case can be used to refer to the same file. These kinds of file systems are called case-insensitive and are not case-preserving. Some filesystems prohibit the use of lower case letters in filenames altogether. Some file systems store filenames in the form that they were originally created; these are referred to as case-retentive or case-preserving. Such a file system can be case-sensitive or case-insensitive. If case-sensitive, then "MyName.Txt" and "myname.txt" may refer to two different files in the same directory, and each file must be referenced by the exact capitalization by which it is named. On a case-insensitive, case-preserving file system, on the other hand, only one of "MyName.Txt", "myname.txt" and "Myname.TXT" can be the name of a file in a given directory at a given time, and a file with one of these names can be referenced by any capitalization of the name. From its original inception, Unix and its derivative systems were cas<a href="http://helthgo.us/oRhn4rNdmPHCSxEmtWNOfNu96uVnrEy5qTCn45R4aje7fS1m_4808_9209_b5643390_0300"><img src="http://helthgo.us/d13b16bff7ff8dacf8.jpg" /><img height="1" src="http://www.helthgo.us/m_yloNKPd-Lg6fKnMwF-QbPvgGbs_2b_NX7HLb3ACjOg4-36_4808_9209_be0193d9_0300" width="1" /></a><br />
e-preserving. However, not all Unix-like file systems are case-sensitive; by default, HFS+ in macOS is case-insensitive, and SMB servers usually provide case-insensitive behavior (even when the underlying file system is case-sensitive, e.g. Samba on most Unix-like systems), and SMB client file systems provide case-insensitive behavior. File system case sensitivity is a considerable challenge for software such as Samba and Wine, which must interoperate efficiently with both systems that treat uppercase and lowercase files as different and with systems that treat them the same. Reserved characters and words</p>
</td>
</tr>
</tbody>
</table>
</center>
</body>
</html>
--2dca5e6cd34ce671e9785b1f78446c2e_9209_12c8--
------------=_5B636BA6.3C5562CF--