Testing new list configuration

Dave Bucklin dave.bucklin at gmail.com
Wed Sep 19 07:52:50 CDT 2018


On Wed, Sep 19, 2018 at 01:34:01AM -0500, Joe Nelson wrote:
> > Should work better now.
> 
> Great, that message passed DMARC for begriffs.com. There are still some issues we may be able to improve for deliverability though:
> 
> X-Spam-score: 2.8
> X-Spam-hits: HEADER_FROM_DIFFERENT_DOMAINS 0.248, HELO_DYNAMIC_IPADDR 3.243,
>   MAILING_LIST_MULTI -1, RDNS_DYNAMIC 0.363, LANGUAGES en, BAYES_USED none,
>   SA_VERSION 3.4.0
> X-Spam-source: IP='18.221.180.137',
>   Host='ec2-18-221-180-137.us-east-2.compute.amazonaws.com', 
> 
> The biggest spam signal appears to be the way our MTA says HELO. Perhaps it's identifying by IP address rather than fully qualified domain name. For example, in postfix, the config has a "myhostname" configuration variable which should be set to lists.frostbyte.cc. By default the variable uses the hostname of the relay machine in question as it appears inside the OS. Either that or the PTR DNS record might look sketchy:
> 
> $ dig -x 18.221.180.137
> 137.180.221.18.in-addr.arpa. 300 IN	PTR	ec2-18-221-180-137.us-east-2.compute.amazonaws.com.
> 
> Should also be pointing at lists.frostbyte.cc
> 
> (CC'ing you directly Dave, in case gmail is choosing to send the mailing list message to spam.)

I'll take a look at it tonight. I have a few domains pointing at that
VPS, but I should be able to change the hostname in Postfix with no ill
effects. We should look into migrating the lists to the OpenBSD VPS.
This would be a good project and will give the group better control over
the lists.


More information about the discuss mailing list