Read: Re: Moving Forward

From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs156129fan; Wed, 19 Jan 2011 17:12:24 -0800 (PST) Received: by 10.90.25.9 with SMTP id 9mr1847441agy.3.1295485942941; Wed, 19 Jan 2011 17:12:22 -0800 (PST) Return-Path: Received: from mail-yw0-f45.google.com (mail-yw0-f45.google.com [209.85.213.45]) by mx.google.com with ESMTPS id i25si16793766anh.150.2011.01.19.17.12.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 17:12:22 -0800 (PST) Received-SPF: neutral (google.com: 209.85.213.45 is neither permitted nor denied by best guess record for domain of jtubbs@unveillance.com) client-ip=209.85.213.45; Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.213.45 is neither permitted nor denied by best guess record for domain of jtubbs@unveillance.com) smtp.mail=jtubbs@unveillance.com Received: by ywl5 with SMTP id 5so17487ywl.4 for ; Wed, 19 Jan 2011 17:12:21 -0800 (PST) Received: by 10.151.88.3 with SMTP id q3mr1611959ybl.348.1295485941654; Wed, 19 Jan 2011 17:12:21 -0800 (PST) Return-Path: Received: from [192.168.0.10] ([69.198.76.73]) by mx.google.com with ESMTPS id u5sm830431yba.22.2011.01.19.17.12.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 17:12:20 -0800 (PST) Subject: @InformationWeek, 1/19/11 15:18 From: "J. Tubbs" Content-Type: multipart/alternative; boundary=Apple-Mail-1--648842791 Message-Id: <6EEEDDE4-80E0-461B-A0DB-413E03F3B4BD@unveillance.com> Date: Wed, 19 Jan 2011 20:12:16 -0500 To: Karim Hijazi Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (iPad Mail 8C148) X-Mailer: iPad Mail (8C148) --Apple-Mail-1--648842791 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii InformationWeek (@InformationWeek) 1/19/11 15:18 Malware Volume Doubled In 2010 http://twb.io/hLaeRw -J. --Apple-Mail-1--648842791 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=utf-8

InformationWeek (@InformationWeek)
1/19/11 15:18
Malware Volume Doubled In 2010 http://twb.io/hLaeRw

-J.

--Apple-Mail-1--648842791-- From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs156708fan; Wed, 19 Jan 2011 17:29:45 -0800 (PST) Received: by 10.150.199.19 with SMTP id w19mr1739247ybf.151.1295486984319; Wed, 19 Jan 2011 17:29:44 -0800 (PST) Return-Path: Received: from p3plsmtpa01-05.prod.phx3.secureserver.net (p3plsmtpa01-05.prod.phx3.secureserver.net [72.167.82.85]) by mx.google.com with SMTP id p33si2998308ybk.20.2011.01.19.17.29.43; Wed, 19 Jan 2011 17:29:44 -0800 (PST) Received-SPF: neutral (google.com: 72.167.82.85 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) client-ip=72.167.82.85; Authentication-Results: mx.google.com; spf=neutral (google.com: 72.167.82.85 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) smtp.mail=jeff@grayconsultingco.com Received: (qmail 1657 invoked from network); 20 Jan 2011 01:29:41 -0000 Received: from unknown (174.49.68.158) by p3plsmtpa01-05.prod.phx3.secureserver.net (72.167.82.85) with ESMTP; 20 Jan 2011 01:29:41 -0000 From: "Jeff Gray" To: "'Karim Hijazi Unveillance Email'" In-Reply-To: <4D372E4A.6040600@unveillance.com> Subject: Read: Re: Moving Forward Date: Wed, 19 Jan 2011 20:29:37 -0500 Message-ID: <003b01cbb841$80e38310$82aa8930$@com> MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_NextPart_000_003C_01CBB817.980D7B10" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acu4B0YRb2dtHBB1Sh62cnqEH2SnDgAOi2Nj This is a multi-part message in MIME format. ------=_NextPart_000_003C_01CBB817.980D7B10 Content-Type: multipart/alternative; boundary="----=_NextPart_001_003D_01CBB817.980D7B10" ------=_NextPart_001_003D_01CBB817.980D7B10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Your message To: Jeff Gray Subject: Fwd: Re: Moving Forward Sent: 1/19/2011 1:32 PM was read on 1/19/2011 8:29 PM. ------=_NextPart_001_003D_01CBB817.980D7B10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Read: Re: Moving Forward

Your message

    To: Jeff Gray
    Subject: Fwd: Re: Moving Forward
    Sent: 1/19/2011 1:32 PM

was read on 1/19/2011 8:29 PM.

------=_NextPart_001_003D_01CBB817.980D7B10-- ------=_NextPart_000_003C_01CBB817.980D7B10 Content-Type: message/disposition-notification Content-Transfer-Encoding: 7bit Reporting-UA: grayconsultingco.com; Microsoft Office Outlook 12.0 Final-Recipient: rfc822;jeff@grayconsultingco.com Original-Message-ID: <4D372E4A.6040600@unveillance.com> Disposition: manual-action/MDN-sent-automatically; displayed ------=_NextPart_000_003C_01CBB817.980D7B10-- From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs156709fan; Wed, 19 Jan 2011 17:29:45 -0800 (PST) Received: by 10.151.82.14 with SMTP id j14mr1731981ybl.39.1295486984681; Wed, 19 Jan 2011 17:29:44 -0800 (PST) Return-Path: Received: from p3plsmtpa01-05.prod.phx3.secureserver.net (p3plsmtpa01-05.prod.phx3.secureserver.net [72.167.82.85]) by mx.google.com with SMTP id u5si16865264yba.43.2011.01.19.17.29.43; Wed, 19 Jan 2011 17:29:44 -0800 (PST) Received-SPF: neutral (google.com: 72.167.82.85 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) client-ip=72.167.82.85; Authentication-Results: mx.google.com; spf=neutral (google.com: 72.167.82.85 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) smtp.mail=jeff@grayconsultingco.com Received: (qmail 1714 invoked from network); 20 Jan 2011 01:29:43 -0000 Received: from unknown (174.49.68.158) by p3plsmtpa01-05.prod.phx3.secureserver.net (72.167.82.85) with ESMTP; 20 Jan 2011 01:29:43 -0000 From: "Jeff Gray" To: "'Karim Hijazi Unveillance Email'" In-Reply-To: <4D372EA1.6050809@unveillance.com> Subject: Read: Mark Lag Date: Wed, 19 Jan 2011 20:29:37 -0500 Message-ID: <004201cbb841$81e4c670$85ae5350$@com> MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_NextPart_000_0043_01CBB817.990EBE70" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acu4B4B6SXUbXPGbSECLkDWDYkBN9AAOe6jV This is a multi-part message in MIME format. ------=_NextPart_000_0043_01CBB817.990EBE70 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0044_01CBB817.990EBE70" ------=_NextPart_001_0044_01CBB817.990EBE70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Your message To: Jeff Gray Subject: Mark Lag Sent: 1/19/2011 1:34 PM was read on 1/19/2011 8:29 PM. ------=_NextPart_001_0044_01CBB817.990EBE70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Read: Mark Lag

Your message

    To: Jeff Gray
    Subject: Mark Lag
    Sent: 1/19/2011 1:34 PM

was read on 1/19/2011 8:29 PM.

------=_NextPart_001_0044_01CBB817.990EBE70-- ------=_NextPart_000_0043_01CBB817.990EBE70 Content-Type: message/disposition-notification Content-Transfer-Encoding: 7bit Reporting-UA: grayconsultingco.com; Microsoft Office Outlook 12.0 Final-Recipient: rfc822;jeff@grayconsultingco.com Original-Message-ID: <4D372EA1.6050809@unveillance.com> Disposition: manual-action/MDN-sent-automatically; displayed ------=_NextPart_000_0043_01CBB817.990EBE70-- From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs156848fan; Wed, 19 Jan 2011 17:33:55 -0800 (PST) Received: by 10.100.178.4 with SMTP id a4mr993667anf.187.1295487233895; Wed, 19 Jan 2011 17:33:53 -0800 (PST) Return-Path: Received: from smtpout04.prod.mesa1.secureserver.net (smtpout04-01.prod.mesa1.secureserver.net [64.202.165.196]) by mx.google.com with SMTP id 10si16843060anw.131.2011.01.19.17.33.53; Wed, 19 Jan 2011 17:33:53 -0800 (PST) Received-SPF: neutral (google.com: 64.202.165.196 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) client-ip=64.202.165.196; Authentication-Results: mx.google.com; spf=neutral (google.com: 64.202.165.196 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) smtp.mail=jeff@grayconsultingco.com Received: (qmail 770 invoked from network); 20 Jan 2011 01:33:53 -0000 Received: from unknown (174.49.68.158) by smtpout04.prod.mesa1.secureserver.net (64.202.165.196) with ESMTP; 20 Jan 2011 01:33:52 -0000 From: "Jeff Gray" To: "'Karim Hijazi Unveillance Email'" In-Reply-To: <4D372D16.9050603@unveillance.com> Subject: Read: Jim Hunt - MOU Date: Wed, 19 Jan 2011 20:33:47 -0500 Message-ID: <005001cbb842$1693ac00$43bb0400$@com> MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_NextPart_000_0051_01CBB818.2DBDA400" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acu4BpbUr4P1G436QyabOY9I1wqlMwAO2545 This is a multi-part message in MIME format. ------=_NextPart_000_0051_01CBB818.2DBDA400 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0052_01CBB818.2DBDA400" ------=_NextPart_001_0052_01CBB818.2DBDA400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Your message To: Jeff Gray Subject: Jim Hunt - MOU Sent: 1/19/2011 1:27 PM was read on 1/19/2011 8:33 PM. ------=_NextPart_001_0052_01CBB818.2DBDA400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Read: Jim Hunt - MOU

Your message

    To: Jeff Gray
    Subject: Jim Hunt - MOU
    Sent: 1/19/2011 1:27 PM

was read on 1/19/2011 8:33 PM.

------=_NextPart_001_0052_01CBB818.2DBDA400-- ------=_NextPart_000_0051_01CBB818.2DBDA400 Content-Type: message/disposition-notification Content-Transfer-Encoding: 7bit Reporting-UA: grayconsultingco.com; Microsoft Office Outlook 12.0 Final-Recipient: rfc822;jeff@grayconsultingco.com Original-Message-ID: <4D372D16.9050603@unveillance.com> Disposition: manual-action/MDN-sent-automatically; displayed ------=_NextPart_000_0051_01CBB818.2DBDA400-- From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs156849fan; Wed, 19 Jan 2011 17:33:55 -0800 (PST) Received: by 10.229.236.196 with SMTP id kl4mr1234559qcb.69.1295487233377; Wed, 19 Jan 2011 17:33:53 -0800 (PST) Return-Path: Received: from smtpout04.prod.mesa1.secureserver.net (smtpout04-01.prod.mesa1.secureserver.net [64.202.165.196]) by mx.google.com with SMTP id q4si16873254ybk.40.2011.01.19.17.33.52; Wed, 19 Jan 2011 17:33:53 -0800 (PST) Received-SPF: neutral (google.com: 64.202.165.196 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) client-ip=64.202.165.196; Authentication-Results: mx.google.com; spf=neutral (google.com: 64.202.165.196 is neither permitted nor denied by best guess record for domain of jeff@grayconsultingco.com) smtp.mail=jeff@grayconsultingco.com Received: (qmail 762 invoked from network); 20 Jan 2011 01:33:52 -0000 Received: from unknown (174.49.68.158) by smtpout04.prod.mesa1.secureserver.net (64.202.165.196) with ESMTP; 20 Jan 2011 01:33:52 -0000 From: "Jeff Gray" To: "'Karim Hijazi Unveillance Email'" In-Reply-To: <4D3724C6.9060303@unveillance.com> Subject: Read: Trip to DC Date: Wed, 19 Jan 2011 20:33:47 -0500 Message-ID: <004901cbb842$162c1090$428431b0$@com> MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_NextPart_000_004A_01CBB818.2D560890" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acu4Abrhjb1cmhSKQaigLyLRj+8BfgAQEwPj This is a multi-part message in MIME format. ------=_NextPart_000_004A_01CBB818.2D560890 Content-Type: multipart/alternative; boundary="----=_NextPart_001_004B_01CBB818.2D560890" ------=_NextPart_001_004B_01CBB818.2D560890 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Your message To: Jeff Gray Subject: Re: Trip to DC Sent: 1/19/2011 12:52 PM was read on 1/19/2011 8:33 PM. ------=_NextPart_001_004B_01CBB818.2D560890 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Read: Trip to DC

Your message

    To: Jeff Gray
    Subject: Re: Trip to DC
    Sent: 1/19/2011 12:52 PM

was read on 1/19/2011 8:33 PM.

------=_NextPart_001_004B_01CBB818.2D560890-- ------=_NextPart_000_004A_01CBB818.2D560890 Content-Type: message/disposition-notification Content-Transfer-Encoding: 7bit Reporting-UA: grayconsultingco.com; Microsoft Office Outlook 12.0 Final-Recipient: rfc822;jeff@grayconsultingco.com Original-Message-ID: <4D3724C6.9060303@unveillance.com> Disposition: manual-action/MDN-sent-automatically; displayed ------=_NextPart_000_004A_01CBB818.2D560890-- From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs162988fan; Wed, 19 Jan 2011 20:22:33 -0800 (PST) Received: by 10.229.217.133 with SMTP id hm5mr1351656qcb.40.1295497351960; Wed, 19 Jan 2011 20:22:31 -0800 (PST) Return-Path: Received: from mta09.aeroplan.thindata.net (mta09.aeroplan.thindata.net [64.34.54.197]) by mx.google.com with ESMTPS id w38si7696624vcr.128.2011.01.19.20.22.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 20:22:31 -0800 (PST) Received-SPF: pass (google.com: domain of Aeroplan@ems2.aeroplan.com designates 64.34.54.197 as permitted sender) client-ip=64.34.54.197; Authentication-Results: mx.google.com; spf=pass (google.com: domain of Aeroplan@ems2.aeroplan.com designates 64.34.54.197 as permitted sender) smtp.mail=Aeroplan@ems2.aeroplan.com Received: from TDWDA04 (tdwda04.thindata.net [64.34.54.234]) by mta09.aeroplan.thindata.net (8.14.4/8.13.4) with ESMTP id p0K4KQKX009325 for ; Thu, 20 Jan 2011 04:22:30 GMT Date: Thu, 20 Jan 2011 04:22:30 GMT To: khijazi@unveillance.com From: "Aeroplan.com" Subject: KARIM HIJAZI, your Aeroplan newsletter, January 2011 Reply-To: Aeroplan@ems2.aeroplan.com Message-Id: <112229 PM.ichokcflmonghognbbglcffoegbbfo@ems02.com> X-TDHeader: X-TDMSToken: X-EMSVersion: X-Mailer: ThinData EMS v30 MIME-Version: 1.0 Content-Type: text/HTML;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: Normal KARIM HIJAZI, your Aeroplan newsletter, January 2011

Dear KARIM,

2011 is already shaping up to be a very exciting year at Aeroplan—with plans to pack lots of amazing surprises, great offers and new, unforgettable rewards into the New Year. Make sure your online profile is up–to–date, so you don't miss out on any opportunities.

Your Aeroplan Team

Earn miles faster!


	Apply for an Aeroplan World MasterCard^� credit card and earn 15,000 bonus miles after your first qualifying transaction. > Apply now


	Discover Air Canada Sun Passes and earn miles every time you escape winter to your favorite sun destination. > Learn more


	With a Star Alliance Europe Airpass, experience the old and new, the great and grand. Up to 10 flights on just one ticket. > Purchase now


	You've hit the JACKPOT with this offer from Avis! Drive away with up to 9,999 Bonus Aeroplan Miles—until March 31! > Get details & reserve


	Shop online via eStore and earn 3X the miles for over 10,000 in–stock items at The Shopping Channel—until February 14! > Start shopping now


	Earn Triple Miles with Marriott Rewards^� MegaMiles between February 1 and April 30, 2011 beginning with your second stay. > Register & stay now

Reward Yourself

Need a car rental?
Starting at 5,000
Redeem with AVIS or Hertz and enjoy the ride.
> Redeem now

Visiting Canada?
Starting at 5,500
Reserve your calendar for these great show tickets!
> Redeem now

Aeroplan News

Soar with our improved flight reward calendar

Now view all your Air Canada and Star Alliance flight reward options—on one new and improved calendar—at a glance.
> Learn more

Congratulations on the big wins, Air Canada.

Our partner, Air Canada, has recently won several industry awards including Best Airline in North America.
> Learn more

Find an Aeroplan Retail Partner near you

Mileage Balance: 1,739
Aeroplan Number: 770 195 824
Statement Date: January 17, 2011

Air Canada Status
Status Miles: 0
Flight Segments: 0

Let's help the Earth mile upon mile...together
If you and other members cumulatively donate 250,000 miles or more, Aeroplan will additionally donate up to 6,000,000 miles.
> Find out how


	Air Canada Insight Looking for great travel deals? With webSaver, choose your favorite destinations and get exclusive offers from Air Canada right in your inbox: seat sale fares, vacation packages, car and hotel deals, travel tips, and more. Join webSaver today! aircanada.com says thank you! Bonus Aeroplan Miles offered by Air Canada for every dollar spent at aircanada.com will no longer be offered for flight bookings or Flight Pass purchases made as of February 16, 2011. However, you will continue to earn up to 150% of the miles you fly with Air Canada. Thank you for your support over the years in making aircanada.com a world–class shopping experience all in one window. Learn more.

Your Aeroplan Earn Miles Use Your Miles Promotions

Stay active with Aeroplan.
��
You have been sent this e-mail because you have opted to receive Aeroplan Newsletter. If you no longer wish to receive Aeroplan Newsletter via e-mail, you can unsubscribe.
Do you want to change your e-mail address?
Do you wish to read the Aeroplan Privacy Policy?
��
Please do not reply to this e-mail.
��
Mailing address: Aeroplan Centre, P.O. Box 7737 Station Terminal, Vancouver, BC Canada V6B 5W9
��
� Aeroplan is a registered trademark of Aeroplan Canada Inc.
��
In case of a discrepancy between the mileage redemption amount shown in the Aeroplan Newsletter and the amount displayed on aeroplan.com, the aeroplan.com mileage redemption amount shall apply. All rewards shown in the Aeroplan Newsletter Reward Yourself section are subject to availability.
��

From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Received: from [192.168.0.191] (184-77-43-130.gar.clearwire-wmx.net [184.77.43.130]) by mx.google.com with ESMTPS id c30sm8785454anc.20.2011.01.19.10.34.10 (version=SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 10:34:12 -0800 (PST) Message-ID: <4D372EA1.6050809@unveillance.com> Disposition-Notification-To: Karim Hijazi Unveillance Email Date: Wed, 19 Jan 2011 13:34:09 -0500 From: Karim Hijazi Unveillance Email Reply-To: khijazi@unveillance.com Organization: Unveillance User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jeff Gray Subject: Mark Lag X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -- All the best, Karim Hijazi CEO | President Unveillance O. (404) 585-7487 M. (561) 542-5704 www.unveillance.com khijazi@unveillance.com ******************************************** CONFIDENTIAL & PRIVILEGED COMMUNICATION This message is for the named person's use only. The information contained in this communication is confidential and/or privileged, proprietary information that is transmitted solely for the purpose of the intended recipient(s). No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender or any of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. ******************************************** -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJNNy6hAAoJEIk0Dw4U/G3l860H/jAEABu/V9usj9trUWRgGFB5 YrtYqEIFaiC+NmFgC2JWuoOBNxozy3m4fdtVO5s0sHOqYSxxwgA7B3RfxJ3v9h1f r51aNPbHBuvp7w8WVJ/ISkHQR97eQpNHmkqglmk1VwdtlREVdyKKLNmYFrs9zRlS cG2jEgtO7uRpQEcEtiaf4JIsm4LzWdgHJoRrhjyOURT4A0HiOcDt8vc00bciTHlI Abq5hGgJrO192kJnHhaZP7Wdai/hmXLov0X9m4mE5ucxKT7uAE45TblZtHTzXHva ZEtF0tkaSa9vc9p35gvh/TgVBS7V1IuEZfHp98nDH6pDbEKKffqlI8R7JqMYGlQ= =SQxR -----END PGP SIGNATURE----- From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs142768fan; Wed, 19 Jan 2011 11:10:03 -0800 (PST) Received: by 10.204.56.194 with SMTP id z2mr1069019bkg.81.1295464202023; Wed, 19 Jan 2011 11:10:02 -0800 (PST) Return-Path: Received: from tllod.com (174.37.79.228-static.reverse.softlayer.com [174.37.79.228]) by mx.google.com with ESMTPS id j10si7157396vcs.199.2011.01.19.11.10.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 11:10:01 -0800 (PST) Received-SPF: neutral (google.com: 174.37.79.228 is neither permitted nor denied by best guess record for domain of kolbitsch@tllod.com) client-ip=174.37.79.228; Authentication-Results: mx.google.com; spf=neutral (google.com: 174.37.79.228 is neither permitted nor denied by best guess record for domain of kolbitsch@tllod.com) smtp.mail=kolbitsch@tllod.com Received: from yoghurt.localnet (yoghurt.seclab.tuwien.ac.at [128.130.60.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tllod.com (Postfix) with ESMTPSA id BB2FB60041; Wed, 19 Jan 2011 11:01:16 -0800 (PST) From: Clemens Kolbitsch Organization: TLLOD To: "J. Tubbs" Subject: Re: Datafeed Purchase/Acquisition Date: Wed, 19 Jan 2011 20:09:58 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.35-24-generic; KDE/4.5.1; x86_64; ; ) Cc: Karim Hijazi References: <201101031102.50320.kolbitsch@tllod.com> <201101181704.41931.kolbitsch@tllod.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201101192009.58300.kolbitsch@tllod.com> Hi, thank you for the exact command, now I was able to reproduce the error and fix it. Thanks for letting me know about the issue and sorry for the inconvenience. We have also improved our monitoring infrastructure to catch these bugs in the future more quickly/avoid them in general. --Clemens On Tuesday, January 18, 2011 09:36:47 pm J. Tubbs wrote: > Clemens, > Thank you for getting back to me so quickly. > > This is the command syntax I am running: > wget -q -Ooutput --user=unveillance --password=Pohqu0oo > 'http://tllod.com/feed/index.php?format=json&mapping=full' > > This is the output from running it in my environment: > { > "entries" : [ > > ], > "revision_info" : { > "current" : 44820, > "diff" : 0 > }, > "feed_info" : { > "entries_added" : 0, > "entries_removed" : 0 > } > } > > J. Tubbs > CTO > Unveillance, LLC > O. (404) 482-3557 > www.unveillance.com > jtubbs@unveillance.com > > ******************************************** > CONFIDENTIAL & PRIVILEGED COMMUNICATION This message is for the named > person's use only. The information contained in this communication is > confidential and/or privileged, proprietary information that is > transmitted solely for the purpose of the intended recipient(s). No > confidentiality or privilege is waived or lost by any mistransmission. > If you receive this message in error, please immediately delete it and > all copies of it from your system, destroy any hard copies of it and > notify the sender. You must not, directly or indirectly, use, disclose, > distribute, print, or copy any part of this message if you are not the > intended recipient. The sender or any of its subsidiaries each reserve > the right to monitor all e-mail communications through its networks. > ******************************************** > > On Jan 18, 2011, at 11:04 AM, Clemens Kolbitsch wrote: > > Hi, > > > > I'm currently looking into the problem. A few quick questions, since I > > cannot reproduce the error: > > > > * Do you happen to know if this is a problem with the JSON format (and > > did not occur when downloading a different format, e.g. XML)? > > > > * Could you tell me, what the current revision was when downloading the > > feed (the "revision_info.current" field)? > > > > * Did you use the "diff" option, or did you download the entire list? If > > you fetched a diff, what was the version you diffed against (the diff > > parameter of the get command or "revision_info.diff" field). > > > > With the last two points, I should be able to reproduce the error exactly > > and fix the issue. > > > > Thanks! > > --Clemens > > > > On Monday, January 17, 2011 07:20:39 pm J. Tubbs wrote: > >> Heya Clemens, > >> Just a quick question regarding the new json feed. I noticed it is no > >> longer responding for us with any data in the "entries" block. > >> > >> It seems to have started returning empty "entries" mid-day on the 14th. > >> Logs of the pulls since that time (apologies for the long snippet of > >> logs) As you can see the logs that are about ~155-170K in size are the > >> ones with entries but the ~249 byte files are empty entries. > >> > >> 155K Jan 13 11:50 PARSER-LLODBL.1294941001.7z > >> 155K Jan 13 12:50 PARSER-LLODBL.1294944601.7z > >> 155K Jan 13 13:50 PARSER-LLODBL.1294948201.7z > >> 155K Jan 13 14:50 PARSER-LLODBL.1294951801.7z > >> 155K Jan 13 15:50 PARSER-LLODBL.1294955401.7z > >> 155K Jan 13 16:50 PARSER-LLODBL.1294959001.7z > >> 156K Jan 13 17:50 PARSER-LLODBL.1294962601.7z > >> 162K Jan 13 18:50 PARSER-LLODBL.1294966201.7z > >> 162K Jan 13 19:50 PARSER-LLODBL.1294969801.7z > >> 162K Jan 13 20:50 PARSER-LLODBL.1294973401.7z > >> 162K Jan 13 21:50 PARSER-LLODBL.1294977001.7z > >> 162K Jan 13 22:50 PARSER-LLODBL.1294980604.7z > >> 162K Jan 13 23:50 PARSER-LLODBL.1294984201.7z > >> 162K Jan 14 00:50 PARSER-LLODBL.1294987801.7z > >> 162K Jan 14 01:50 PARSER-LLODBL.1294991401.7z > >> 156K Jan 14 02:50 PARSER-LLODBL.1294995001.7z > >> 156K Jan 14 03:50 PARSER-LLODBL.1294998601.7z > >> 156K Jan 14 04:50 PARSER-LLODBL.1295002202.7z > >> 156K Jan 14 05:50 PARSER-LLODBL.1295005801.7z > >> 155K Jan 14 06:50 PARSER-LLODBL.1295009401.7z > >> 155K Jan 14 07:50 PARSER-LLODBL.1295013001.7z > >> 155K Jan 14 08:50 PARSER-LLODBL.1295016601.7z > >> 155K Jan 14 09:50 PARSER-LLODBL.1295020201.7z > >> 155K Jan 14 10:50 PARSER-LLODBL.1295023801.7z > >> 155K Jan 14 11:50 PARSER-LLODBL.1295027402.7z > >> 155K Jan 14 12:50 PARSER-LLODBL.1295031001.7z > >> 248 Jan 14 13:50 PARSER-LLODBL.1295034601.7z > >> 249 Jan 14 14:50 PARSER-LLODBL.1295038201.7z > >> 249 Jan 14 15:50 PARSER-LLODBL.1295041801.7z > >> 249 Jan 14 16:50 PARSER-LLODBL.1295045401.7z > >> 249 Jan 14 17:50 PARSER-LLODBL.1295049001.7z > >> 248 Jan 14 18:50 PARSER-LLODBL.1295052601.7z > >> 249 Jan 14 19:50 PARSER-LLODBL.1295056201.7z > >> 248 Jan 14 20:50 PARSER-LLODBL.1295059801.7z > >> 248 Jan 14 21:50 PARSER-LLODBL.1295063401.7z > >> 249 Jan 14 22:50 PARSER-LLODBL.1295067003.7z > >> 248 Jan 14 23:50 PARSER-LLODBL.1295070602.7z > >> 249 Jan 15 00:50 PARSER-LLODBL.1295074201.7z > >> 249 Jan 15 01:50 PARSER-LLODBL.1295077801.7z > >> 249 Jan 15 02:50 PARSER-LLODBL.1295081402.7z > >> 249 Jan 15 03:50 PARSER-LLODBL.1295085001.7z > >> 248 Jan 15 04:50 PARSER-LLODBL.1295088602.7z > >> 249 Jan 15 05:50 PARSER-LLODBL.1295092202.7z > >> 249 Jan 15 06:50 PARSER-LLODBL.1295095802.7z > >> 248 Jan 15 07:50 PARSER-LLODBL.1295099401.7z > >> 249 Jan 15 08:50 PARSER-LLODBL.1295103001.7z > >> 249 Jan 15 09:50 PARSER-LLODBL.1295106602.7z > >> 249 Jan 15 10:50 PARSER-LLODBL.1295110201.7z > >> 249 Jan 15 11:50 PARSER-LLODBL.1295113802.7z > >> 249 Jan 15 12:50 PARSER-LLODBL.1295117401.7z > >> 249 Jan 15 13:50 PARSER-LLODBL.1295121002.7z > >> 249 Jan 15 14:50 PARSER-LLODBL.1295124602.7z > >> 249 Jan 15 15:50 PARSER-LLODBL.1295128201.7z > >> 249 Jan 15 16:50 PARSER-LLODBL.1295131801.7z > >> 249 Jan 15 17:50 PARSER-LLODBL.1295135401.7z > >> 249 Jan 15 18:50 PARSER-LLODBL.1295139002.7z > >> 249 Jan 15 19:50 PARSER-LLODBL.1295142602.7z > >> 249 Jan 15 20:50 PARSER-LLODBL.1295146202.7z > >> 249 Jan 15 21:50 PARSER-LLODBL.1295149801.7z > >> 249 Jan 15 22:50 PARSER-LLODBL.1295153403.7z > >> 249 Jan 15 23:50 PARSER-LLODBL.1295157002.7z > >> 249 Jan 16 00:50 PARSER-LLODBL.1295160601.7z > >> 249 Jan 16 01:50 PARSER-LLODBL.1295164201.7z > >> 249 Jan 16 02:50 PARSER-LLODBL.1295167802.7z > >> 249 Jan 16 03:50 PARSER-LLODBL.1295171401.7z > >> 249 Jan 16 04:50 PARSER-LLODBL.1295175002.7z > >> 249 Jan 16 05:50 PARSER-LLODBL.1295178601.7z > >> 249 Jan 16 06:50 PARSER-LLODBL.1295182201.7z > >> 249 Jan 16 07:50 PARSER-LLODBL.1295185802.7z > >> 249 Jan 16 08:50 PARSER-LLODBL.1295189402.7z > >> 249 Jan 16 09:50 PARSER-LLODBL.1295193002.7z > >> 249 Jan 16 10:50 PARSER-LLODBL.1295196602.7z > >> 249 Jan 16 11:50 PARSER-LLODBL.1295200202.7z > >> 249 Jan 16 12:50 PARSER-LLODBL.1295203801.7z > >> 249 Jan 16 13:50 PARSER-LLODBL.1295207402.7z > >> 249 Jan 16 14:50 PARSER-LLODBL.1295211002.7z > >> 249 Jan 16 15:50 PARSER-LLODBL.1295214601.7z > >> 249 Jan 16 16:50 PARSER-LLODBL.1295218201.7z > >> 249 Jan 16 17:50 PARSER-LLODBL.1295221801.7z > >> 249 Jan 16 18:50 PARSER-LLODBL.1295225401.7z > >> 249 Jan 16 19:50 PARSER-LLODBL.1295229002.7z > >> 249 Jan 16 20:50 PARSER-LLODBL.1295232602.7z > >> 249 Jan 16 21:50 PARSER-LLODBL.1295236202.7z > >> 249 Jan 16 22:50 PARSER-LLODBL.1295239803.7z > >> 249 Jan 16 23:50 PARSER-LLODBL.1295243402.7z > >> 248 Jan 17 00:50 PARSER-LLODBL.1295247001.7z > >> 249 Jan 17 01:50 PARSER-LLODBL.1295250601.7z > >> 249 Jan 17 02:50 PARSER-LLODBL.1295254201.7z > >> 249 Jan 17 03:50 PARSER-LLODBL.1295257802.7z > >> 249 Jan 17 04:50 PARSER-LLODBL.1295261402.7z > >> 249 Jan 17 05:50 PARSER-LLODBL.1295265002.7z > >> 249 Jan 17 06:50 PARSER-LLODBL.1295268601.7z > >> 249 Jan 17 07:50 PARSER-LLODBL.1295272201.7z > >> 249 Jan 17 08:50 PARSER-LLODBL.1295275802.7z > >> 249 Jan 17 09:50 PARSER-LLODBL.1295279401.7z > >> 249 Jan 17 10:50 PARSER-LLODBL.1295283001.7z > >> 249 Jan 17 11:50 PARSER-LLODBL.1295286602.7z > >> > >> J. Tubbs > >> CTO > >> Unveillance, LLC > >> O. (404) 482-3557 > >> www.unveillance.com > >> jtubbs@unveillance.com > >> > >> ******************************************** > >> CONFIDENTIAL & PRIVILEGED COMMUNICATION This message is for the named > >> person's use only. The information contained in this communication is > >> confidential and/or privileged, proprietary information that is > >> transmitted solely for the purpose of the intended recipient(s). No > >> confidentiality or privilege is waived or lost by any mistransmission. > >> If you receive this message in error, please immediately delete it and > >> all copies of it from your system, destroy any hard copies of it and > >> notify the sender. You must not, directly or indirectly, use, disclose, > >> distribute, print, or copy any part of this message if you are not the > >> intended recipient. The sender or any of its subsidiaries each reserve > >> the right to monitor all e-mail communications through its networks. > >> ******************************************** > >> > >> On Jan 5, 2011, at 1:31 PM, Clemens Kolbitsch wrote: > >>> Hello, > >>> > >>> we have extended the blacklist feed for you to include all domain-to-IP > >>> mappings that we see during up-time checks. > >>> > >>> The URL and credentials to the feed have not changed, all you need to > >>> do in order to receive the new list is to change the "mapping" > >>> parameter as follows: > >>> > >>> OPTION: mapping = [ 0 | "no" | 1 | "yes" | "full" ] > >>> > >>> mapping = 0 | "no" : no mapping between domains and IPs (identical to > >>> previous feed version) > >>> > >>> mapping = 1 | "yes" : mappings between domains and IPs, without IPs > >>> that might lead to inclusion of shared hosting, etc (identical to > >>> previous feed version) > >>> > >>> mapping = "full" : complete mapping between domains and IPs without any > >>> kind of filtering. Do NOT use this option if you intend to find > >>> malicious activity or block connections based on the content of the > >>> blacklist feed. > >>> > >>> ============================ > >>> Examples: > >>> > >>> (i) Download current version of blacklist (in CSV format) into file > >>> blacklist including full domain-to-IP mappings (without filtering of > >>> shared hosts, etc.) wget -q -Oblacklist --user=yourUser > >>> --password=yourPasswd > >>> 'https://tllod.com/feed/index.php?format=csv&diff=0&mapping=full' > >>> > >>> > >>> Again, let me remind you that some domains might still lack IPs > >>> associated with the domain. In these cases, you will need to resolve > >>> the domains yourself because, depending on the source we obtain > >>> information from, we might not use the IP as part of our > >>> processing/feed creation. > >>> > >>> Please let me know if you have any questions or comments. > >>> > >>> Best, > >>> Clemens From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs143973fan; Wed, 19 Jan 2011 11:30:33 -0800 (PST) Received: by 10.147.137.15 with SMTP id p15mr1485346yan.26.1295465432463; Wed, 19 Jan 2011 11:30:32 -0800 (PST) Return-Path: Received: from mail-gy0-f173.google.com (mail-gy0-f173.google.com [209.85.160.173]) by mx.google.com with ESMTPS id k9si16061589anh.113.2011.01.19.11.30.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 11:30:32 -0800 (PST) Received-SPF: neutral (google.com: 209.85.160.173 is neither permitted nor denied by best guess record for domain of jtubbs@unveillance.com) client-ip=209.85.160.173; Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.160.173 is neither permitted nor denied by best guess record for domain of jtubbs@unveillance.com) smtp.mail=jtubbs@unveillance.com Received: by gye5 with SMTP id 5so494898gye.4 for ; Wed, 19 Jan 2011 11:30:31 -0800 (PST) Received: by 10.90.52.17 with SMTP id z17mr1413410agz.95.1295465431540; Wed, 19 Jan 2011 11:30:31 -0800 (PST) Return-Path: Received: from [10.23.37.195] ([166.137.13.197]) by mx.google.com with ESMTPS id t23sm8840450ano.26.2011.01.19.11.30.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 11:30:30 -0800 (PST) References: <201101031102.50320.kolbitsch@tllod.com> <201101181704.41931.kolbitsch@tllod.com> <201101192009.58300.kolbitsch@tllod.com> In-Reply-To: <201101192009.58300.kolbitsch@tllod.com> Mime-Version: 1.0 (iPad Mail 8C148) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <715F2BE1-7902-48E4-AE13-F0C47C400271@unveillance.com> Cc: Karim Hijazi X-Mailer: iPad Mail (8C148) From: "J. Tubbs" Subject: Re: Datafeed Purchase/Acquisition Date: Wed, 19 Jan 2011 14:30:17 -0500 To: Clemens Kolbitsch Not a problem at all, Clemens. I am glad that i was able to give ya somethi= ng that helped. :) -J. On Jan 19, 2011, at 14:09, Clemens Kolbitsch wrote: > Hi, >=20 > thank you for the exact command, now I was able to reproduce the error and= fix=20 > it. Thanks for letting me know about the issue and sorry for the=20 > inconvenience. >=20 > We have also improved our monitoring infrastructure to catch these bugs in= the=20 > future more quickly/avoid them in general. >=20 > --Clemens >=20 > On Tuesday, January 18, 2011 09:36:47 pm J. Tubbs wrote: >> Clemens, >> Thank you for getting back to me so quickly. >>=20 >> This is the command syntax I am running: >> wget -q -Ooutput --user=3Dunveillance --password=3DPohqu0oo >> 'http://tllod.com/feed/index.php?format=3Djson&mapping=3Dfull' >>=20 >> This is the output from running it in my environment: >> { >> "entries" : [ >>=20 >> ], >> "revision_info" : { >> "current" : 44820, >> "diff" : 0 >> }, >> "feed_info" : { >> "entries_added" : 0, >> "entries_removed" : 0 >> } >> } >>=20 >> J. Tubbs >> CTO >> Unveillance, LLC >> O. (404) 482-3557 >> www.unveillance.com >> jtubbs@unveillance.com >>=20 >> ******************************************** >> CONFIDENTIAL & PRIVILEGED COMMUNICATION This message is for the named >> person's use only. The information contained in this communication is >> confidential and/or privileged, proprietary information that is >> transmitted solely for the purpose of the intended recipient(s). No >> confidentiality or privilege is waived or lost by any mistransmission. >> If you receive this message in error, please immediately delete it and >> all copies of it from your system, destroy any hard copies of it and >> notify the sender. You must not, directly or indirectly, use, disclose, >> distribute, print, or copy any part of this message if you are not the >> intended recipient. The sender or any of its subsidiaries each reserve >> the right to monitor all e-mail communications through its networks. >> ******************************************** >>=20 >> On Jan 18, 2011, at 11:04 AM, Clemens Kolbitsch wrote: >>> Hi, >>>=20 >>> I'm currently looking into the problem. A few quick questions, since I >>> cannot reproduce the error: >>>=20 >>> * Do you happen to know if this is a problem with the JSON format (and >>> did not occur when downloading a different format, e.g. XML)? >>>=20 >>> * Could you tell me, what the current revision was when downloading the >>> feed (the "revision_info.current" field)? >>>=20 >>> * Did you use the "diff" option, or did you download the entire list? If= >>> you fetched a diff, what was the version you diffed against (the diff >>> parameter of the get command or "revision_info.diff" field). >>>=20 >>> With the last two points, I should be able to reproduce the error exactl= y >>> and fix the issue. >>>=20 >>> Thanks! >>> --Clemens >>>=20 >>> On Monday, January 17, 2011 07:20:39 pm J. Tubbs wrote: >>>> Heya Clemens, >>>> Just a quick question regarding the new json feed. I noticed it is no >>>> longer responding for us with any data in the "entries" block. >>>>=20 >>>> It seems to have started returning empty "entries" mid-day on the 14th.= >>>> Logs of the pulls since that time (apologies for the long snippet of >>>> logs) As you can see the logs that are about ~155-170K in size are the >>>> ones with entries but the ~249 byte files are empty entries. >>>>=20 >>>> 155K Jan 13 11:50 PARSER-LLODBL.1294941001.7z >>>> 155K Jan 13 12:50 PARSER-LLODBL.1294944601.7z >>>> 155K Jan 13 13:50 PARSER-LLODBL.1294948201.7z >>>> 155K Jan 13 14:50 PARSER-LLODBL.1294951801.7z >>>> 155K Jan 13 15:50 PARSER-LLODBL.1294955401.7z >>>> 155K Jan 13 16:50 PARSER-LLODBL.1294959001.7z >>>> 156K Jan 13 17:50 PARSER-LLODBL.1294962601.7z >>>> 162K Jan 13 18:50 PARSER-LLODBL.1294966201.7z >>>> 162K Jan 13 19:50 PARSER-LLODBL.1294969801.7z >>>> 162K Jan 13 20:50 PARSER-LLODBL.1294973401.7z >>>> 162K Jan 13 21:50 PARSER-LLODBL.1294977001.7z >>>> 162K Jan 13 22:50 PARSER-LLODBL.1294980604.7z >>>> 162K Jan 13 23:50 PARSER-LLODBL.1294984201.7z >>>> 162K Jan 14 00:50 PARSER-LLODBL.1294987801.7z >>>> 162K Jan 14 01:50 PARSER-LLODBL.1294991401.7z >>>> 156K Jan 14 02:50 PARSER-LLODBL.1294995001.7z >>>> 156K Jan 14 03:50 PARSER-LLODBL.1294998601.7z >>>> 156K Jan 14 04:50 PARSER-LLODBL.1295002202.7z >>>> 156K Jan 14 05:50 PARSER-LLODBL.1295005801.7z >>>> 155K Jan 14 06:50 PARSER-LLODBL.1295009401.7z >>>> 155K Jan 14 07:50 PARSER-LLODBL.1295013001.7z >>>> 155K Jan 14 08:50 PARSER-LLODBL.1295016601.7z >>>> 155K Jan 14 09:50 PARSER-LLODBL.1295020201.7z >>>> 155K Jan 14 10:50 PARSER-LLODBL.1295023801.7z >>>> 155K Jan 14 11:50 PARSER-LLODBL.1295027402.7z >>>> 155K Jan 14 12:50 PARSER-LLODBL.1295031001.7z >>>> 248 Jan 14 13:50 PARSER-LLODBL.1295034601.7z >>>> 249 Jan 14 14:50 PARSER-LLODBL.1295038201.7z >>>> 249 Jan 14 15:50 PARSER-LLODBL.1295041801.7z >>>> 249 Jan 14 16:50 PARSER-LLODBL.1295045401.7z >>>> 249 Jan 14 17:50 PARSER-LLODBL.1295049001.7z >>>> 248 Jan 14 18:50 PARSER-LLODBL.1295052601.7z >>>> 249 Jan 14 19:50 PARSER-LLODBL.1295056201.7z >>>> 248 Jan 14 20:50 PARSER-LLODBL.1295059801.7z >>>> 248 Jan 14 21:50 PARSER-LLODBL.1295063401.7z >>>> 249 Jan 14 22:50 PARSER-LLODBL.1295067003.7z >>>> 248 Jan 14 23:50 PARSER-LLODBL.1295070602.7z >>>> 249 Jan 15 00:50 PARSER-LLODBL.1295074201.7z >>>> 249 Jan 15 01:50 PARSER-LLODBL.1295077801.7z >>>> 249 Jan 15 02:50 PARSER-LLODBL.1295081402.7z >>>> 249 Jan 15 03:50 PARSER-LLODBL.1295085001.7z >>>> 248 Jan 15 04:50 PARSER-LLODBL.1295088602.7z >>>> 249 Jan 15 05:50 PARSER-LLODBL.1295092202.7z >>>> 249 Jan 15 06:50 PARSER-LLODBL.1295095802.7z >>>> 248 Jan 15 07:50 PARSER-LLODBL.1295099401.7z >>>> 249 Jan 15 08:50 PARSER-LLODBL.1295103001.7z >>>> 249 Jan 15 09:50 PARSER-LLODBL.1295106602.7z >>>> 249 Jan 15 10:50 PARSER-LLODBL.1295110201.7z >>>> 249 Jan 15 11:50 PARSER-LLODBL.1295113802.7z >>>> 249 Jan 15 12:50 PARSER-LLODBL.1295117401.7z >>>> 249 Jan 15 13:50 PARSER-LLODBL.1295121002.7z >>>> 249 Jan 15 14:50 PARSER-LLODBL.1295124602.7z >>>> 249 Jan 15 15:50 PARSER-LLODBL.1295128201.7z >>>> 249 Jan 15 16:50 PARSER-LLODBL.1295131801.7z >>>> 249 Jan 15 17:50 PARSER-LLODBL.1295135401.7z >>>> 249 Jan 15 18:50 PARSER-LLODBL.1295139002.7z >>>> 249 Jan 15 19:50 PARSER-LLODBL.1295142602.7z >>>> 249 Jan 15 20:50 PARSER-LLODBL.1295146202.7z >>>> 249 Jan 15 21:50 PARSER-LLODBL.1295149801.7z >>>> 249 Jan 15 22:50 PARSER-LLODBL.1295153403.7z >>>> 249 Jan 15 23:50 PARSER-LLODBL.1295157002.7z >>>> 249 Jan 16 00:50 PARSER-LLODBL.1295160601.7z >>>> 249 Jan 16 01:50 PARSER-LLODBL.1295164201.7z >>>> 249 Jan 16 02:50 PARSER-LLODBL.1295167802.7z >>>> 249 Jan 16 03:50 PARSER-LLODBL.1295171401.7z >>>> 249 Jan 16 04:50 PARSER-LLODBL.1295175002.7z >>>> 249 Jan 16 05:50 PARSER-LLODBL.1295178601.7z >>>> 249 Jan 16 06:50 PARSER-LLODBL.1295182201.7z >>>> 249 Jan 16 07:50 PARSER-LLODBL.1295185802.7z >>>> 249 Jan 16 08:50 PARSER-LLODBL.1295189402.7z >>>> 249 Jan 16 09:50 PARSER-LLODBL.1295193002.7z >>>> 249 Jan 16 10:50 PARSER-LLODBL.1295196602.7z >>>> 249 Jan 16 11:50 PARSER-LLODBL.1295200202.7z >>>> 249 Jan 16 12:50 PARSER-LLODBL.1295203801.7z >>>> 249 Jan 16 13:50 PARSER-LLODBL.1295207402.7z >>>> 249 Jan 16 14:50 PARSER-LLODBL.1295211002.7z >>>> 249 Jan 16 15:50 PARSER-LLODBL.1295214601.7z >>>> 249 Jan 16 16:50 PARSER-LLODBL.1295218201.7z >>>> 249 Jan 16 17:50 PARSER-LLODBL.1295221801.7z >>>> 249 Jan 16 18:50 PARSER-LLODBL.1295225401.7z >>>> 249 Jan 16 19:50 PARSER-LLODBL.1295229002.7z >>>> 249 Jan 16 20:50 PARSER-LLODBL.1295232602.7z >>>> 249 Jan 16 21:50 PARSER-LLODBL.1295236202.7z >>>> 249 Jan 16 22:50 PARSER-LLODBL.1295239803.7z >>>> 249 Jan 16 23:50 PARSER-LLODBL.1295243402.7z >>>> 248 Jan 17 00:50 PARSER-LLODBL.1295247001.7z >>>> 249 Jan 17 01:50 PARSER-LLODBL.1295250601.7z >>>> 249 Jan 17 02:50 PARSER-LLODBL.1295254201.7z >>>> 249 Jan 17 03:50 PARSER-LLODBL.1295257802.7z >>>> 249 Jan 17 04:50 PARSER-LLODBL.1295261402.7z >>>> 249 Jan 17 05:50 PARSER-LLODBL.1295265002.7z >>>> 249 Jan 17 06:50 PARSER-LLODBL.1295268601.7z >>>> 249 Jan 17 07:50 PARSER-LLODBL.1295272201.7z >>>> 249 Jan 17 08:50 PARSER-LLODBL.1295275802.7z >>>> 249 Jan 17 09:50 PARSER-LLODBL.1295279401.7z >>>> 249 Jan 17 10:50 PARSER-LLODBL.1295283001.7z >>>> 249 Jan 17 11:50 PARSER-LLODBL.1295286602.7z >>>>=20 >>>> J. Tubbs >>>> CTO >>>> Unveillance, LLC >>>> O. (404) 482-3557 >>>> www.unveillance.com >>>> jtubbs@unveillance.com >>>>=20 >>>> ******************************************** >>>> CONFIDENTIAL & PRIVILEGED COMMUNICATION This message is for the named >>>> person's use only. The information contained in this communication is >>>> confidential and/or privileged, proprietary information that is >>>> transmitted solely for the purpose of the intended recipient(s). No >>>> confidentiality or privilege is waived or lost by any mistransmission. >>>> If you receive this message in error, please immediately delete it and >>>> all copies of it from your system, destroy any hard copies of it and >>>> notify the sender. You must not, directly or indirectly, use, disclose,= >>>> distribute, print, or copy any part of this message if you are not the >>>> intended recipient. The sender or any of its subsidiaries each reserve >>>> the right to monitor all e-mail communications through its networks. >>>> ******************************************** >>>>=20 >>>> On Jan 5, 2011, at 1:31 PM, Clemens Kolbitsch wrote: >>>>> Hello, >>>>>=20 >>>>> we have extended the blacklist feed for you to include all domain-to-I= P >>>>> mappings that we see during up-time checks. >>>>>=20 >>>>> The URL and credentials to the feed have not changed, all you need to >>>>> do in order to receive the new list is to change the "mapping" >>>>> parameter as follows: >>>>>=20 >>>>> OPTION: mapping =3D [ 0 | "no" | 1 | "yes" | "full" ] >>>>>=20 >>>>> mapping =3D 0 | "no" : no mapping between domains and IPs (identical t= o >>>>> previous feed version) >>>>>=20 >>>>> mapping =3D 1 | "yes" : mappings between domains and IPs, without IPs >>>>> that might lead to inclusion of shared hosting, etc (identical to >>>>> previous feed version) >>>>>=20 >>>>> mapping =3D "full" : complete mapping between domains and IPs without a= ny >>>>> kind of filtering. Do NOT use this option if you intend to find >>>>> malicious activity or block connections based on the content of the >>>>> blacklist feed. >>>>>=20 >>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >>>>> Examples: >>>>>=20 >>>>> (i) Download current version of blacklist (in CSV format) into file >>>>> blacklist including full domain-to-IP mappings (without filtering of >>>>> shared hosts, etc.) wget -q -Oblacklist --user=3DyourUser >>>>> --password=3DyourPasswd >>>>> 'https://tllod.com/feed/index.php?format=3Dcsv&diff=3D0&mapping=3Dfull= ' >>>>>=20 >>>>>=20 >>>>> Again, let me remind you that some domains might still lack IPs >>>>> associated with the domain. In these cases, you will need to resolve >>>>> the domains yourself because, depending on the source we obtain >>>>> information from, we might not use the IP as part of our >>>>> processing/feed creation. >>>>>=20 >>>>> Please let me know if you have any questions or comments. >>>>>=20 >>>>> Best, >>>>> Clemens From - Sat May 21 19:26:24 2011 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: khijazi@unveillance.com Received: by 10.223.97.65 with SMTP id k1cs144599fan; Wed, 19 Jan 2011 11:42:10 -0800 (PST) Received: by 10.42.230.66 with SMTP id jl2mr1230155icb.99.1295466129115; Wed, 19 Jan 2011 11:42:09 -0800 (PST) Return-Path: Received: from mail-gx0-f173.google.com (mail-gx0-f173.google.com [209.85.161.173]) by mx.google.com with ESMTPS id q31si16108522ybk.56.2011.01.19.11.42.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 11:42:09 -0800 (PST) Received-SPF: neutral (google.com: 209.85.161.173 is neither permitted nor denied by best guess record for domain of jtubbs@unveillance.com) client-ip=209.85.161.173; Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.161.173 is neither permitted nor denied by best guess record for domain of jtubbs@unveillance.com) smtp.mail=jtubbs@unveillance.com Received: by gxk28 with SMTP id 28so18973gxk.4 for ; Wed, 19 Jan 2011 11:42:08 -0800 (PST) Received: by 10.150.147.3 with SMTP id u3mr1380021ybd.24.1295466128076; Wed, 19 Jan 2011 11:42:08 -0800 (PST) Return-Path: Received: from [10.23.37.195] ([166.137.13.197]) by mx.google.com with ESMTPS id v7sm635003ybe.15.2011.01.19.11.42.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 11:42:06 -0800 (PST) Subject: @SecurityWeek, 1/19/11 11:18 From: "J. Tubbs" Content-Type: multipart/alternative; boundary=Apple-Mail-1--668665762 Message-Id: <7F488D7E-7C03-4581-91E3-D21A0DD14EA4@unveillance.com> Date: Wed, 19 Jan 2011 14:41:53 -0500 To: Karim Hijazi Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (iPad Mail 8C148) X-Mailer: iPad Mail (8C148) --Apple-Mail-1--668665762 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii SecurityWeek (@SecurityWeek) 1/19/11 11:18 Why we need to Share Threat Data - http://bit.ly/fR2bY4 #cybercrime -J. --Apple-Mail-1--668665762 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=utf-8

SecurityWeek (@SecurityWeek)
1/19/11 11:18
Why we need to Share Threat Data - http://bit.ly/fR2bY4 #cybercrime

-J.

--Apple-Mail-1--668665762--