<div dir="ltr">Same thing happens with DKIM/DMARC by the way, not just SPF.</div><div class="gmail_extra"><br><div class="gmail_quote">2017-02-21 13:15 GMT+01:00 Nerk Nerk <span dir="ltr"><<a href="mailto:donnerk@gmail.com" target="_blank">donnerk@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thank you for your answers.<div><br></div><div>The problem is, that the people that use my filters, don't own the server that their email is hosted on. So they can't always decide to turn something off.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-02-21 12:56 GMT+01:00 Antony Stone <span dir="ltr"><<a href="mailto:Antony.Stone@mailscanner.open.source.it" target="_blank">Antony.Stone@mailscanner.<wbr>open.source.it</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Tuesday 21 February 2017 at 12:48:18, Nerk Nerk wrote:<br>
<br>
> Dear MailScanner-fanatics,<br>
><br>
> Currently I am facing some issues using MailScanner. Mostly, when the<br>
> following situation is current:<br>
><br>
> - Some domain using SPF, for example Paypal, sends a mail to a domain that<br>
> I filter for<br>
<br>
</span>So, you are the destination of the MX records...<br>
<span><br>
> - The domain is filtered through Mailscanner<br>
> - The e-mail is forwarded to the destination<br>
<br>
</span>How does that happen?<br>
<span><br>
> - The destination server is not under my control. They do SPF checking and<br>
> reject the mail because the sending domain does not list my mailscanner IP<br>
> as a valid sender<br>
><br>
> Ofcourse I have thought of some solutions:<br>
> 1- They need to whitelist the IP of my mailscanner<br>
<br>
</span>That would be good, considering that they've bought (?) a filtering service<br>
from you, and expect mail to pass through your servers on the way to theirs.<br>
<span><br>
> 2- They need to turn off the SPF checks at the destination<br>
<br>
</span>Do they receive any direct (ie: not filtered through your servers) email?<br>
<span><br>
> Both solutions however, require actions from a hosting party that I don't<br>
> know and that is probably not willing.<br>
<br>
</span>So, why have they pointed their MX records at your server, if they're not<br>
wiling to adjust their server to match this?<br>
<span><br>
> A third option:<br>
> 3- I need to rewrite the sending domain somehow<br>
<br>
</span>Yes, like manay mailing lists do.<br>
<span><br>
> Has anyone else come across this problem? How did you solve it?<br>
><br>
> I am really wondering what solution commercial spam filtering services,<br>
> such as SpamExperts for example, are using.<br>
<br>
</span>I can't speak for them.<br>
<br>
<br>
Antony.<br>
<span class="m_1160542198176852286HOEnZb"><font color="#888888"><br>
--<br>
Never automate fully anything that does not have a manual override capability.<br>
Never design anything that cannot work under degraded conditions in emergency.<br>
<br>
Please reply to the list;<br>
please *don't* CC me.<br>
<br>
<br>
--<br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info" target="_blank">mailscanner@lists.mailscanner.<wbr>info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" rel="noreferrer" target="_blank">http://lists.mailscanner.info/<wbr>mailman/listinfo/mailscanner</a><br>
<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>