[Fedora-infrastructure-list] fp.org email addresses coming up as spam

[Max Spevack]

Anyone else seen complaints of things like this?  I have my settings quite 
low, and we're still getting flagged.

  2.7 HELO_DYNAMIC_DHCP      Relay HELO'd using suspicious hostname (DHCP)
  3.3 HELO_DYNAMIC_HCC       Relay HELO'd using suspicious hostname (HCC)

http://www.google.com/search?q=HELO_DYNAMIC_DHCP

Thought I'd throw this out there for anyone who's interested in doing some 
digging, see under what circumstances fp.o emails are triggering these 
flags.

--Max

---------- Forwarded message ----------
Received: from localhost by mspevack.rdu.redhat.com
     with SpamAssassin (version 3.1.3);
     Wed, 23 Aug 2006 15:20:47 -0400
From: Jack Aboutboul <jaboutboul at fedoraproject.org>
To: Markster at digium.com
Subject: *****SPAM***** Fedora and Asterisk
Date: Wed, 23 Aug 2006 15:19:38 -0400
Message-Id: <1156360778.23913.8.camel at deepfort>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on
     mspevack.rdu.redhat.com
X-Spam-Level: *****
X-Spam-Status: Yes, score=5.9 required=5.0 tests=HELO_DYNAMIC_DHCP,
     HELO_DYNAMIC_HCC,UNPARSEABLE_RELAY autolearn=no version=3.1.3
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_44ECAA8F.C1433263"

Spam detection software, running on the system "mspevack.rdu.redhat.com", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Hey Mark, I am at Red Hat HQ for the week and part of
   our Fedora meetings have been regarding how we can help make Fedora a
   viable platform for innovation for certain key technologies which have
   the most potential. Naturally, voip came up and a number of people spoke
   about Asterisk and how we can work together with you guys. [...]

Content analysis details:   (5.9 points, 5.0 required)

  pts rule name              description
---- ---------------------- --------------------------------------------------
  2.7 HELO_DYNAMIC_DHCP      Relay HELO'd using suspicious hostname (DHCP)
  3.3 HELO_DYNAMIC_HCC       Relay HELO'd using suspicious hostname (HCC)
  0.0 UNPARSEABLE_RELAY      Informational: message has unparseable relay lines