<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Hi Joh,</p>
<p>SPF records should <em>always</em> be implemented for an email domain. There's large freemail providers that won't accept your email if you don't have SPF, read point 4 below as an example:</p>
<p><a href="https://blu171.mail.live.com/mail/policies.aspx">https://blu171.mail.live.com/mail/policies.aspx</a></p>
<p> </p>
<p>On 2013-02-18 20:50, Johannes Graumann wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>Hello,
I have been testing a kolab3/Debian wheezy set up using
<a href="http://www.allaboutspam.com/email-server-test">http://www.allaboutspam.com/email-server-test</a>One of the comments that comes back is:</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">.org> does not have any SPF records set. Using SPF minimizes the chances of your Email being rejected or be classified as SPAM. Ideally, the SPF records for must return 'pass' for your Email server IP . For more details on publishing SPF records for your domain, please refer to <a href="http://old.openspf.org/wizard.html">http://old.openspf.org/wizard.html</a></blockquote>
<pre>Aside from the fact that the facility referred to is dead ... is this worth
implementing? And if so: what might an implementation (preferably on Debian)
look like and consist from?
Thanks for your input.
Sincerely, Joh
_______________________________________________
Kolab-users mailing list
<a href="mailto:Kolab-users@kolab.org">Kolab-users@kolab.org</a>
<a href="https://www.intevation.de/mailman/listinfo/kolab-users">https://www.intevation.de/mailman/listinfo/kolab-users</a>
</pre>
</blockquote>
<div>
<pre>--
Thanks,
Michael.</pre>
</div>
</body></html>