DontKnow Posted August 27, 2013 Share Posted August 27, 2013 I'm getting a banner in spamcop.net saying that my mailhost bounced e-mail from spamcop. It looks like spamcop added a new outbound mail server: 184.94.240.88. The SPF record is: spamcop.net text = "v=spf1 ip4:184.94.240.89 ip4:184.94.240.112 ip4:204.15.80.0/22 ip4:216.154.195.32/27 ip4:64.88.168.64/27 ?all" My maillog says that the IP 184.94.240.88 was rejected. So, I think that it isn't my problem that e-mail from spamcop to me bounced, but instead it is spamcop's problem. Let me know when this is fixed so that I can clicked the "Problem resolved" button. Link to comment Share on other sites More sharing options...
alvarnell Posted August 27, 2013 Share Posted August 27, 2013 That's clearly something you need to discuss with your mailhost. Link to comment Share on other sites More sharing options...
DontKnow Posted August 27, 2013 Author Share Posted August 27, 2013 That's clearly something you need to discuss with your mailhost. *My* mailhost? SPF records are defined by the mail server (via DNS records), in this case spamcop.net. My mailhost simply enforces SPF record validity so that there are fewer e-mails with forged from addresses. Link to comment Share on other sites More sharing options...
SpamCopAdmin Posted August 27, 2013 Share Posted August 27, 2013 184.94.240.88 is a new server. It may not be properly configured. Please EMAIL me your login username so I can review the details. Do NOT post your username in this forum. Thanks! - Don D'Minion - SpamCop Admin - - Service[at]Admin.SpamCop.net - Link to comment Share on other sites More sharing options...
techie Posted August 28, 2013 Share Posted August 28, 2013 I've been seeing the same problem.. It looks like a couple of new servers were put online before DNS was updated. My server has rejected several emails in the last 24 hours from 184.94.240.89 for lack of valid PTR records, leading to the the same bounce warning. Sorry folks, if you don't have a valid PTR record, have mismatched A and PTR records, or have PTR records pointing at invalid domains, my server won't be talking to you. email was sent to deputies[at]spamcop.net early this morning.. no response yet. Link to comment Share on other sites More sharing options...
gnarlymarley Posted August 28, 2013 Share Posted August 28, 2013 my messages usually come from [at]spam.spamcop.net, which has not DNS record. I imagine this should be fixed by now as all is working for me. Link to comment Share on other sites More sharing options...
techie Posted September 2, 2013 Share Posted September 2, 2013 my messages usually come from [at]spam.spamcop.net, which has not DNS record. Actually, spam.spamcop.net does have an MX record. It does not have an A record, which is not required. >host spam.spamcop.net spam.spamcop.net mail is handled by 5 vmx.spamcop.net. 184.94.240.88 and .89, on the other hand, have no PTR records. > host 184.94.240.89 Host 89.240.94.184.in-addr.arpa. not found: 3(NXDOMAIN) > host 184.94.240.88 Host 88.240.94.184.in-addr.arpa. not found: 3(NXDOMAIN) Link to comment Share on other sites More sharing options...
gnarlymarley Posted September 2, 2013 Share Posted September 2, 2013 Actually, spam.spamcop.net does have an MX record. It does not have an A record, which is not required. >host spam.spamcop.net spam.spamcop.net mail is handled by 5 vmx.spamcop.net. 184.94.240.88 and .89, on the other hand, have no PTR records. > host 184.94.240.89 Host 89.240.94.184.in-addr.arpa. not found: 3(NXDOMAIN) > host 184.94.240.88 Host 88.240.94.184.in-addr.arpa. not found: 3(NXDOMAIN) right, I mean [at]spam.spamcop.net does not have SPF record. It does have the valid MX records that are sufficient to get into my mail server. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.