Date: Tue, 11 Dec 2007 00:27:37 GMT From: Mark <admin@asarian-host.net> To: <questions@freebsd.org> Subject: RE: FreeBSD mail forwarder and SPF Message-ID: <200712110027.lBB0Ratn004398@asarian-host.net> In-Reply-To: <475DCB8F.40600@foster.cc> References: <20071210161905.O20625@prime.gushi.org> <475DCB8F.40600@foster.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Mark D. Foster Sent: dinsdag 11 december 2007 0:40 To: Dan Mahoney, System Admin Cc: questions@freebsd.org Subject: Re: FreeBSD mail forwarder and SPF > The solution is @ http://www.openspf.org/FAQ/Forwarding > If garga@ isn't following the recommended practice of whitelisting > freebsd.org's MX servers then breakage results. That said, > mx2.freebsd.org is NOT LISTED as an MX of freebsd.org, so maybe that > is contributing to the problem. Like you said, if he wants to send mail through the FreeBSD server, using his prime.gushi.org domain, he should add "ip4:69.147.83.53" to his SPF records for that domain (or do some SRS forward rewriting). But what's mx2.freebsd.org not being listed as an MX of freebsd.org got to do with SPF?? There's no requirement, whatsoever, for mx2.freebsd.org to be an official FreeBSD MX record. Who cares? FreeBSD includes "ip4:69.147.83.53" in its SPF records (which is mx2.freebsd.org). That's all SPF needs to know. - Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200712110027.lBB0Ratn004398>