Investigating an instance of SPF rejection by postfix. The postfix SPF module receiving mail for @michaelsnet.us is rejecting email from @michaelrpdx.com
Relevant log message: Jul 24 09:36:58 rumpus postfix/smtpd[3844]: NOQUEUE: reject: RCPT from cave.michaelrpdx.com[167.88.112.146]: 550 5.7.1 <[email protected]>: Recipient address rejected: Message rejected due to: SPF fail - not authorized. Please see http://www.openspf.net/Why?s=mfrom;[email protected];ip=167.88.112.146;[email protected]; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<cave.michaelrpdx.com> Jul 24 09:36:59 rumpus postfix/smtpd[3844]: disconnect from cave.michaelrpdx.com[167.88.112.146] What openspf.net reports: [email protected] rejected a message that claimed an envelope sender address of [email protected]. [email protected] received a message from cave.michaelsnet.us (167.88.112.146) that claimed an envelope sender address of [email protected]. The domain michaelrpdx.com has authorized cave.michaelsnet.us (167.88.112.146) to send mail on its behalf, so the message should have been accepted. It is impossible for us to say why it was rejected. And a bit of DNS validations: $) host cave.michaelsnet.us Host cave.michaelsnet.us not found: 3(NXDOMAIN) $) host 167.88.112.146 146.112.88.167.in-addr.arpa domain name pointer cave.michaelrpdx.com. In short, postfix's SPF checker is the only entity that associates 167.88.112.146 with cave.michaelsnet.us Having beat my head against the wall attempting to resolve this I'm pretty sure I'm missing something simple. What is, or may be, causing this? -- Michael Rasmussen, Portland Oregon Be Appropriate && Follow Your Curiosity Even a gulag has a certain romance to it. ~ Renee Russell _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
