<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
On Mon, 2013-06-03 at 17:52 +1000, David Hughes wrote:
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
So your SPAM filtering is tagging valid list emails as spam just because they are coming from an EC2 instance? That sounds more like a problem with the SPAM filter than the mailing list. Not sure what we can do to fix that but happy to hear suggestions (off list probably).
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
0.7 FH_HOST_EQ_D_D_D_D Host starts with d-d-d-d<BR>
1.4 FH_HELO_EQ_D_D_D_D Helo is d-d-d-d<BR>
0.6 NONAL_IN_SUB Non std punctuation chars in subject<BR>
0.2 FREEMAIL_FROM Sender email is freemail (clanlaw[at]googlemail.com)<BR>
(plot.lost[at]gmail.com)<BR>
(march.tim[at]gmail.com)<BR>
0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is<BR>
CUSTOM_MED<BR>
2.0 FM_DDDD_TIMES_2 Dual helo + host eq d_d_d_d<BR>
0.3 L_FAKE_GMAIL Message claims to have come from gmail, but may not have<BR>
0.4 RDNS_DYNAMIC Delivered to internal network by host with<BR>
dynamic-looking rDNS<BR>
1.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid<BR>
3.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr<BR>
1)<BR>
0.5 TO_NO_BRKTS_FREEMAIL To: misformatted and free email service<BR>
<BR>
<BR>
given the helo and host it uses, I'd say anti spam rules are doing exactly what they are supposed to do.<BR>
<BR>
<BR>
<BR>
</BODY>
</HTML>