This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SPF & DynDNS/MailHop proxy conflict

I'm not certain but I think I have a problem with the SPF check of the Astaro box and the DynDNS/MailHop system. Here;s a bit of the log from my firewall.

2007:09:11-00:18:49 (none) exim [15829]: 2007-09-11 00:18:49 H=mhb-02-pao.mailhop.org [208.78.69.72]:57352 F= rejected RCPT : 208.78.69.72 is not allowed to send mail from connect.match.com

2007:09:11-00:18:49 (none) exim[15829]: 2007-09-11 00:18:49 SMTP connection from mhb-02-pao.mailhop.org [208.78.69.72]:57352 closed by QUIT

I'm getting mail from Match.com [yes, I'm single] but the firewall sees the IP address of the DynDNS-Mailhop system then rejects it because the mailhop server is not registered in the SPF database to send mail from match.com.

It seems to me that either this implementation is somehow wrong or I'll never receive any mail from a domain that actually has an SPF registration.

Can someone help me understand this?

This thread was automatically locked due to age.

0 drees over 18 years ago

The problem lies with either SPF or the MailHop system, depending on how you look at it.

Assuming you want to continue using SPF and MailHop, either the MailHop systems should be added to the SPF records for the domain that email is being relayed for, and/or the MailHop systems should be rewriting the From: envelope to note that the email is being forwarded using SRS.

In this specific example, which MailHop service are you using? The Forwarding service?

If so, you can could add mx:mailhop.org to your domain's SPF record, but this would mean that anyone sending mail through mailhop.org's servers could joejob your domain.

Here are some additional notes regarding forwarding and SPF in case you haven't seen them already:
http://www.openspf.org/Best_Practices/Forwarding
Cancel
Vote Up 0 Vote Down

Cancel