Ivan Kurmanov writes
The only this is: it looks like the SPF record which includes ip4:65.89.18.160 needs to be added to the DNS records of nebka.stlouisfed.org. Here is what google mail says about the mail that is sent by the new server now (a header added by google to an incomming mail):
Received-SPF: neutral (google.com: 65.89.18.160 is neither permitted nor denied by best guess record for domain of aras@nebka.stlouisfed.org) client-ip=65.89.18.160;
Yes, and there does not appear to be a reverse DNS record for the box, a big no-no with some spam filters krichel@sahure:~$ nslookup 65.89.18.160 Server: 213.133.98.98 Address: 213.133.98.98#53 ** server can't find 160.18.89.65.in-addr.arpa.: NXDOMAIN krichel@sahure:~$ nslookup nebka.stlouisfed.org Server: 213.133.98.98 Address: 213.133.98.98#53 Non-authoritative answer: Name: nebka.stlouisfed.org Address: 65.89.18.160 stlouisfed will have to deal with this, not us. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorprofile.org/pkr1 skype: thomaskrichel