[PD] ..a bit off topics

Fri Aug 25 00:18:26 CEST 2006

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I tried to add as a "trusted_network" the ip for the iem.whatever.at
server which appears in all messages, but i found again another message
from the PD in the spam directory (it might be that the two operations
overlapped for a second, so i'll see later if it really worked).

One thing the spamassasin seems not to like at all (which is a very
fixable detail, by the sender of course),it  is when the sender
computer has a wrong time, usually in the future, compared with the *real*
universal time (considering the obvious adjustment with different
timezones) at the moment of sending it.

Anyway here there is the header and the reason that made spamassasin unhappy...
[below this message another one with some different explanation]

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;

+b=U/qpFi08VRC+TlG87re84z6qZ5iHBSgRPoeSGS/1qrm9T2XBFb/biTUX8U3ZL8MNRpMvmrK6nHGbR6xZqTDfMWI51fdBHOAGjfmd8jRu/y
+rJ9GOZuhHDEF2H52+joFDut+fZx1dMSGg6gt4CJttd727GTYZkj0N1B3YxP4mWOZo=
Received: by 10.35.111.14 with SMTP id o14mr567830pym;
        Wed, 23 Aug 2006 06:40:31 -0700 (PDT)

Content analysis details:   (6.6 points, 3.0 required)

 pts rule name              description
- ---- ----------------------
- --------------------------------------------------
 0.1 FORGED_RCVD_HELO       Received: contains a forged HELO
 1.4 SPF_SOFTFAIL           SPF: sender does not match SPF record
 (softfail)
                            [SPF failed: ]
 2.4 SPF_HELO_SOFTFAIL      SPF: HELO does not match SPF record
 (softfail)
                            [SPF failed: ]
 1.3 INFO_TLD               URI: Contains an URL in the INFO top-level
 domain
 0.0 HTML_MESSAGE           BODY: HTML included in message
 0.0 BAYES_50               BODY: Bayesian spam probability is 40 to
 60%
                            [score: 0.4671]
 1.4 HTML_10_20             BODY: Message is 10% to 20% HTML

****************************THIS IS THE SECOND MESSAGE****************

- -------------------------------------------------------------------------
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on amarone
X-Spam-Level: ****
X-Spam-Status: Yes, score=4.4 required=3.0 tests=AWL,BAYES_50,
        DATE_IN_FUTURE_12_24,FORGED_RCVD_HELO,INFO_TLD,SPF_PASS
	autolearn=no
        version=3.1.4

Content analysis details:   (4.4 points, 3.0 required)

 pts rule name              description
- ---- ----------------------
- --------------------------------------------------
 0.1 FORGED_RCVD_HELO       Received: contains a forged HELO
- -0.0 SPF_PASS               SPF: sender matches SPF record
 2.8 DATE_IN_FUTURE_12_24   Date: is 12 to 24 hours after Received:
 date
 1.3 INFO_TLD               URI: Contains an URL in the INFO top-level
 domain
 0.0 BAYES_50               BODY: Bayesian spam probability is 40 to
 60%
                            [score: 0.5000]
 0.3 AWL                    AWL: From: address is in the auto
 white-list

 24/08/2006 alle 21:34:40, +0200, zmoelnig at iem.at [AKA zmoelnig] ha scritto/escribió/wrote:
| Zitat von carmen <_ at whats-your.name>:
| 
| >On Thu Aug 24, 2006 at 10:59:08AM -0400, Marco Trevisani wrote:
| >>
| >>Dear all,
| >>
| >>recently happened that my mailer in "collaboration" with spamassassin
| >>decided to classify some of the messages to the PD list as "spam" and,
| >>weird, not even as "maybe-spam" , simply and directly as spam. Of course
| >>none of them were spam, they were really messages to the list.
| >>I'm wondering if i'm the only one having this problem here...
| 
| it would be good to know which spamassassin-tests have added enough 
| points to classify which emails as spam.
| the only problem i recently had, was thunderbird thinking hcs's 
| autobuild info mails being scam, due to the direct use of IP-addresses.
| 
| >
| >procmail rules seem to follow the 'first match' rule. so just put 
| >your PD match above your spam matches. like this:
| >
| 
| they don't "seem to" follow.
| you tell a procmail rule whether processing should stop when a certain 
| rule matches or whether it should go on.
| ~> man procmailrc
| 
| mfg.asd.r
| IOhannes

Content-Description: Öffentlicher PGP-Schlüssel
| pub  1024D/FEB276F4 2006-02-06 IOhannes m zmoelnig (gpg-key at iem) <zmoelnig at iem.at>
| sub  2048g/9B4C4D62 2006-02-06 [expires: 2011-02-05]

| _______________________________________________
| PD-list at iem.at mailing list
| UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

thanks,
	marco

- -- 
************************************************************************
* marco trevisani                                                      *
* http://marco.trevisani.net       marco at trevisani.net                 *
* Neither MS-Word nor MS-PowerPoint attachments please:                *
* See http://www.fsf.org/philosophy/no-word-attachments.html           *
* Gpg Fingerprint = A9CD 12D6 B658 A545 9BD1  77E9 47AD 8753 8110 7070 *
************************************************************************
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE7iWyU43HxvPN1+QRAoHZAJ42qvKAC2MafdIc/bnvZDvKJ0mOOwCglBHj
YoNpNpIY9eMCidg7K2NL8mw=
=ScAd
-----END PGP SIGNATURE-----