Mike is 100% correct.   EMail only. 
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "MikeB" <[email protected]>
Date: Wed, 21 Oct 2009 07:45:58 
To: RBASE-L Mailing List<[email protected]>
Subject: [RBASE-L] - Re: Spam Mail Stopped

Only to the email containing links to a NON-RBase site...

----- Original Message ----- 
From: "cfgrimes" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, October 21, 2009 4:16 AM
Subject: [RBASE-L] - Re: Spam Mail Stopped


> Now I'm concerned.  Are you referring only to R-List E-Mail account, or 
> also other "update" links for R:Base?
>
> I DID download RB76 update files (but haven't run .exe files yet).  I 
> received password email for all these from webmas...@rbase, so assumed all 
> were legitimate.  Just want to very that those were ok before I run .exe 
> files.
>
> Cathy Grimes
> Huntington Beach, Ca
>
> ----- Original Message ----- 
> From: "Paul" <[email protected]>
> To: "RBASE-L Mailing List" <[email protected]>
> Sent: Tuesday, October 20, 2009 5:44 PM
> Subject: [RBASE-L] - Re: Spam Mail Stopped
>
>
>>I saw a recent post in the past month and it was about a "Spam" and if 
>>they
>> should response to a request from rbase.com regarding a update to RBase
>> R-List E-Mail account.
>> I just wanted to say I received the same in my blocked email account.  It
>> was stopped so ISP and Vipre one or the other I thank them.
>> My apologies to RBase IF they are sending out a update to Email, but I 
>> also
>> missed that announcement.
>>
>> Be careful, if you receive a email asking to "Click" and update. Unless 
>> we
>> here from John or Razzak, as far as I am concerned I elect not to.
>>
>>
>> Paul D
>>
>> Ps. Just one of those days.
>>
>>
>> Below is the source that was in the email:
>>
>> Received: (ISPmail 5720 invoked from network); 20 Oct 2009 02:48:35 -0000
>> Received: from unknown (HELO m1pismtp01-010.prod.mesa1.secureserver.net)
>> ([10.8.12.10])
>>          (envelope-sender <[email protected]>)
>>          by smtp34.prod.mesa1.secureserver.net (qmail-1.03) with SMTP
>>          for <[email protected]>; 20 Oct 2009 02:48:35 -0000
>> X-IP-SPAM: Confirmed
>> Received: from mail.rbase.com (HELO rbase.com) ([162.39.22.27])
>>  by m1pismtp01-010.prod.mesa1.secureserver.net with ESMTP; 19 Oct 2009
>> 19:48:35 -0700
>> Received: from rbase.com by rbase.com (MDaemon PRO v9.6.4)
>> with ESMTP id md50000397038.msg
>> for <[email protected]>; Mon, 19 Oct 2009 22:45:58 -0400
>> X-Spam-Processed: rbase.com, Mon, 19 Oct 2009 22:45:58 -0400
>> (not processed: message from valid local sender)
>> X-MDHeloLookup-Result: pass smtp.helo=rbase.com (ip=127.0.0.1) 
>> (rbase.com)
>> X-MDMailLookup-Result: pass [email protected] (ip=127.0.0.1)
>> (rbase.com)
>> X-Return-Path: [email protected]
>> X-Envelope-From: [email protected]
>> X-MDaemon-Deliver-To: [email protected]
>> X-Spam-Flag: YES
>> X-Spam-Level: ***********
>> X-Spam-Status: Yes, score=11.50 required=5.0
>> X-Spam-Report:
>> *  3.8 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname
>> (IP addr  *       2)
>> *  3.0 MDAEMON_DNSBL MDaemon: marked by MDaemon's DNSBL
>> *  0.5 ADDRESS_IN_SUBJECT To: address appears in Subject
>> *  2.5 SPOOF_COM2COM URI: URI contains ".com" in middle and end
>> *  0.0 HTML_MESSAGE BODY: HTML included in message
>> *  1.6 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
>> *      [score: 0.5000]
>> X-MDDNSBL-Result: rbase.com, Mon, 19 Oct 2009 22:45:08 -0400
>> zen.spamhaus.org returned result of 127.0.0.11
>> From: "[email protected]" <[email protected]>
>> To: [email protected] (RBASE-L Mailing List)
>> Subject: [RBASE-L] - [***SPAM*** Score/Req: 11.50/5.0] A new settings 
>> file
>> for the [email protected]
>> Date: Mon, 19 Oct 2009 19:46:00 -0800
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="----=_NextPart_000_0007_01CA512F.754C06F0"
>> X-Priority: 3
>> X-MSMail-Priority: Normal
>> X-Mailer: Microsoft Outlook Express 6.00.2900.2180
>> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>> Reply-To: [email protected]
>> Sender: [email protected]
>> Errors-To: [email protected]
>> Precedence: bulk
>> X-Nonspam: None
>>
>>
>
> 


Reply via email to