My switch from SpiritOne to Frontier FiOS has been an education because I once again have a static IP address and am seeing a bunch of issues not before encountered. Most I've resolved, two remain.
When I tried sending a response to John yesterday it was rejected by gmx.net because of a failed reverse DNS lookup; the PTR record points to ..bvtn.or.frontiernet.net rather than ..mail.appl-ecosys.com because Frontier assumed I have a a mail account with them. After a half-hour on the phone with their service rep yesterday he learned that the folks who can change the PTR record don't work weekends. Sigh. I'll take care of this tomorrow. My DNS records are now fully SPF-compliant, thanks to help from an IT mail openSPF expert in Dublin. Mail sent from both my domains to check-a...@verifier.port25.com pass the SPF test. The remaining issue is getting openDKIM to pass the port25.com verification. Yesterday I installed it (using a SlackBuilds.org package) and ran through the setup of keys, known hosts, etc. following a blog page based on CentOS. When I start opendkim it does so and tells me it's running. But, when I send messages to port25.com it does not see DKIM. I still cannot load lists.opendkim.org; traceroute fails at 13 hops: be2095.rcr21.b001848-1.sjc01.atlas.cogentco.com (154.54.3.138) 25.898 ms be2063.rcr21.b001848-1.sjc01.atlas.cogentco.com (154.54.1.162) 24.978 ms 25.118 ms This is all terra incognita for me and I would like help checking configuration and everything else to find why it starts but is not seen by a mail recipient. If you understand opendkim and will help me get it going, please contact me off the list. Rich _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug