URIBL FP-- better example

[Ken A]

heh..
host auth.info.multi.uribl.com
auth.info.multi.uribl.com has address 127.0.0.2

That's funny.
blacklisted syslog config!
Ken A.
Pacific.Net



Jay Chandler wrote:
> Here's a better example-- I checked all the URLs I could find by hand...
> 
> 
> -------- Original Message --------
> 
> 
> Return-Path: <owner-toasters at mathworks.com>
> X-Original-To: redacted at chapman.edu
> Delivered-To: redacted at chapman.edu
> Received: from smtp2.mathworks.com (smtp2.mathworks.com [144.212.95.218])
>     by spacecowboy.chapman.edu (Postfix) with ESMTP id 1E5F15C13F;
>     Wed, 28 Feb 2007 10:56:08 -0800 (PST)
> Received: from mail-vif.mathworks.com (fred-ce0.mathworks.com
> [144.212.95.18])
>     by smtp2.mathworks.com (8.13.8/8.12.11) with ESMTP id
> l1SInvOG009769;
>     Wed, 28 Feb 2007 13:52:10 -0500 (EST)
> Received: from fred-ce0.mathworks.com (mail-vif [144.212.95.101])
>     by mail-vif.mathworks.com (8.11.7/8.11.7) with ESMTP id
> l1SIeXd09937;
>     Wed, 28 Feb 2007 13:40:33 -0500 (EST)
> Received: (from majordom at localhost)
>     by fred-ce0.mathworks.com (8.11.7/8.11.6) id l1SIeX709933;
>     Wed, 28 Feb 2007 13:40:33 -0500 (EST)
> X-Authentication-Warning: fred.mathworks.com: majordom set sender to
> owner-toasters at mathworks.com using -f
> Received: from smtp.mathworks.com (ginger [144.212.95.28])
>     by mail-vif.mathworks.com (8.11.7/8.11.7) with ESMTP id l1SIeQd09821
>     for <toasters at mathworks.com>; Wed, 28 Feb 2007 13:40:26 -0500 (EST)
> Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37])
>     by smtp.mathworks.com (8.13.8/8.12.11) with SMTP id l1SIeO8o006090
>     for <toasters at mathworks.com>; Wed, 28 Feb 2007 13:40:25 -0500 (EST)
> Received: from smtp2.corp.netapp.com ([10.57.159.114])
>  by mx2.netapp.com with ESMTP; 28 Feb 2007 10:37:10 -0800
> X-IronPort-AV: i="4.14,231,1170662400";   d="scan'208"; 
> a="37155937:sNHT30089311"
> Received: from svlexc02.hq.netapp.com (svlexc02.corp.netapp.com
> [10.57.157.136])
>     by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id
> l1SIb9PL008173;
>     Wed, 28 Feb 2007 10:37:09 -0800 (PST)
> Received: from SACEXMV01.hq.netapp.com ([10.99.190.107]) by
> svlexc02.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.6713);
>      Wed, 28 Feb 2007 10:38:17 -0800
> x-mimeole: Produced By Microsoft Exchange V6.5
> Content-class: urn:content-classes:message
> MIME-Version: 1.0
> Content-Type: text/plain;
>     charset="us-ascii"
> Date: Wed, 28 Feb 2007 10:37:08 -0800
> Message-ID:
> <C5817D4E914A99478E1B6D2E5112F85D02C5D758 at SACEXMV01.hq.netapp.com>
> In-Reply-To:
> <33A166465FC5A042A53EDA8EB7681610014FD74D at satladmdlmb37.delta.rl.delta.com>
> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: autosupport stops 
> functioning Thread-Index: 
> AcdadAYGFBWHqExdTu+usTKdpoxkzwAL57RAAC4/reAAAgU/QA==
> References:
> <33A166465FC5A042A53EDA8EB7681610014FD74D at satladmdlmb37.delta.rl.delta.com>
> From: "Learmonth, Peter" <Peter.Learmonth at netapp.com>
> To: "Bender, Marilee" <Marilee.Bender at delta.com>, <toasters at mathworks.com>
> X-OriginalArrivalTime: 28 Feb 2007 18:38:17.0279 (UTC)
> FILETIME=[9CBDC4F0:01C75B67]
> X-Greylist: Delayed for 00:03:14 by milter-greylist-2.0.2
> (smtp.mathworks.com [144.212.95.12]); Wed, 28 Feb 2007 13:40:25 -0500 (EST)
> X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data:
> 2007.2.28.100436
> X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT
> 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0,
> __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
> Content-Transfer-Encoding: 8bit
> X-MIME-Autoconverted: from quoted-printable to 8bit by
> mail-vif.mathworks.com id l1SIeUd09880
> Sender: owner-toasters at mathworks.com
> Precedence: bulk
> X-Chapman-MailScanner-Information: Please contact the ISP for more
> information
> X-Chapman-MailScanner: Found to be clean
> X-Chapman-MailScanner-SpamCheck: spam, SpamAssassin (not cached, score=6.7,
>     required 6, BAYES_50 0.10, J_CHICKENPOX_21 0.60, URIBL_BLACK 6.00)
> X-Chapman-MailScanner-SpamScore: ssssss
> X-Chapman-MailScanner-From: owner-toasters at mathworks.com
> Subject: *****SPAM***** RE: autosupport stops functioning
> X-Spam-Status: Yes
> 
> 
> -----Original Message-----
> From: owner-toasters at mathworks.com [mailto:owner-toasters at mathworks.com] On
> Behalf Of Learmonth, Peter
> Sent: Wednesday, February 28, 2007 10:37 AM
> To: Bender, Marilee; toasters at mathworks.com
> Subject: *****SPAM***** RE: autosupport stops functioning
> 
> Hi There
> I realize some of you may know this, but just in case...
> 
> Asup to NetApp, as of around 6.4 or 6.5, has the option of sending to
> NetApp via HTTP or HTTPS.  This was implemented because of issues Mike
> Sphar mentioned (SMTP relays not being configured to allow the filer to
> send to netapp.com or the config changing).  Unless you block HTTP out
> of your datacenter, you should really use this transport.  If you block
> direct HTTP, but have a proxy, there's an option for that too.
> 
> autosupport.support.enable   on
> autosupport.support.proxy
> autosupport.support.to       autosupport at netapp.com    <<<< Only used
> for SMTP
> autosupport.support.transport https
> autosupport.support.url
> support.netapp.com/asupprod/post/1.0/postAsup
> (url is hard-coded)
> 
> HTTPS is the default for new installs.  Systems that have been installed
> since before this option existed, or have been upgraded from an install
> that predates this may still be set to their original SMTP settings.  I
> don't know off top of my head if any ONTAP upgrades change this at all.
> 
> HTTP does not have the same message size limits that SMTP usually does.
> 
> These options must be set from the CLI (console or telnet/SSH), since
> they're not exposed in FilerView.
> 
> If you want to check if asup is working at all, when you might not be
> getting messages, ask support or your SE to check for asups at our end.
> The filer also syslogs errors encountered by asup, by default in
> /etc/messages and on the console, if connected when the problem occurs.
> 
> The other reason I bring this up is that even if your filer is not under
> support, NetApp will still receive the asup messages.  We just won't
> open or act on cases automatically if there is no support in place.  The
> messages are still useful in many ways, including if you ever decide to
> reactivate support, we have history we can use to help you.  Also, if
> you want to upgrade (add-on or head swap), your NetApp SE can give you
> advice based on the asup info.
> 
> Share and enjoy!
> 
> Peter
> 
> -----Original Message-----
> From: Bender, Marilee [mailto:Marilee.Bender at delta.com] Sent: Wednesday, 
> February 28, 2007 9:26 AM
> To: toasters at mathworks.com
> Subject: FW: autosupport stops functioning
> We had this issue too.  I agree with the post below that it could be
> message size.  However, if it's just past asups that were too large
> because of the messages file (or one of the other attachments), you can
> set the autosupport.content size to minimal to delete all the queued
> asups, then "doit" to generate one without the attachments to see if you
> receive it, then put the content back to complete.  It cleared the issue
> on one of our NearStores....the other one appears to have a "corrupt"
> character in the data chunk as viewed from the smtp server logs.
> 
> -----Original Message-----
> From: owner-toasters at mathworks.com [mailto:owner-toasters at mathworks.com]
> On Behalf Of Sphar, Mike
> Sent: Tuesday, February 27, 2007 2:19 PM
> To: toasters at mathworks.com
> Subject: RE: autosupport stops functioning
> I don't think this is the same problem as the one originally posted, but
> we once had a similar problem here where autosupport messages stopped
> being received by netapp because our mail gateway was rejecting all
> messages larger than a certain size.  We didn't even know they were
> bouncing (we weren't getting the bounces) until one of the mail admins
> finally said something about it.
> 
> 
> -- 
> Michael W. Sphar - IS&T - Lead Systems Administrator SMBU Engineering
> Support Services, BMC Software
> 
> 
> -----Original Message-----
> From: owner-toasters at mathworks.com [mailto:owner-toasters at mathworks.com]
> On Behalf Of Stephen C. Losen
> Sent: Tuesday, February 27, 2007 6:55 AM
> To: Leeds, Daniel
> Cc: toasters at mathworks.com
> Subject: Re: autosupport stops functioning
>>
>> anyone else have this happen?
>>
>> suddenly one of our filers stops generating autosupport messages.
>  both autosupport.enable and autosupport.support.enable are on.  if
> i generate a test email with the autosupport.doit option nothing
> happens.
>  not even a failed message, the console just sits there as if i never
> generated one.
>>
>> needless to say neither netapp or our email server gets anything from
> this filer and nothing hits the console about generating any
> autosupport
> emails.
>>
>>
> 
> One of our filers stopped sending weekly autosupports because
> the /etc/messages file was huge (170MB).  It gets sent to netapp
> as part of the autosupport.  I got an automatic email
> from Netapp support telling me that they hadn't received an
> autosupport for two weeks.  Buried in my huge /etc/messages
> file was an error indicating that autosupport had failed, but
> no reason why.
> 
> This particular filer holds our home directories and gets a lot of
> CIFS logins, which we want to log.  We have enabled CIFS login
> tracing, which is very verbose.
> 
> I used /etc/syslog.conf to divert the CIFS auth messages to another
> file:
> 
> *.warning;auth.none   /dev/console
> *.info;auth.none      /etc/messages
> auth.info             /etc/cifs_auth_log
> 
> I rotate the cifs_auth_log with a cron job because I think ONTAP
> will only rotate /etc/messages.
> 
> Now /etc/messages only grows to about 200K and autosupport is working
> again.
> 
> 
> Steve Losen   scl at virginia.edu    phone: 434-924-0640
> 
> University of Virginia               ITC Unix Support
> 
>